List of Contributions

Late reply, thought I'd share an update. We finally had down time to re-load the program. I added a pair of EN2TR cards into the redundant chassis, reorganized the IO devices, fixing the unsupported bridge connection. My initial problem, the inability to add an analog card, went away. ...

The 10 Slot chassis is full. One thought I had: The EN2TR in slot 3 has 4 additional RIO racks and 20ish VFDs. The main redundant chassis have one open slot. Should I, could I, move the slot 3 EN2TR card to the open spot in the main redundant chassis, (yes, I would need one more), then ...

I didn't design it, I inherited responsibility for this system. Is it possible my unsupported bridged RIO be causing my issues with adding one more analog module? If so, if I increased the RPI on everything in that rack, might my issue go away?

Slot 0, Eth_Node56 has an RPI of 10 ms. Slot 3, vlan_21Net RPI is grayed out. The EN2TR in slot 3 connects 4 additional EN2TRs (remote I/O chassis) and 20 PF525s. Is using an RIO chassis to connect to more RIO chassis acceptable?

Nothing is set to unicast, as per redundant system requirements. CPU seems fine. Multicast Producers is maxxed out. Is that my underlying issue? Is there a way to reduce that, or increase the max supported?

We've got a large system, 2 - L71's, ver24, running redundant. It has a 10 slot chassis for remote I/O. Slot 7 was empty, so we added a IF16. When active, it faults out, "(16#0002) Resources Unavailable". I read something that pointed me towards the 1756-EN2TR card that connects this RIO to the PLC ...