Wondering if anyone else has run into this problem.
Processor: 1756-L73S GuardLogix
Following steps:
1. Create a UDT online that consists of BOOL, DINT, STRING.
2. Create a tag which is an array of those UDTs.
3. Delete the tag, so that nothing references the UDT
4. Change BOOL to DINT.
5. Recreate tag array
6. Watch processor behave funny including completely locking up and shutting off ethernet connections.
What happens is the RSLogix5000 program correctly sees the new UDT variable as a DINT, but the processor still treats it as a BOOL. You can verify this by looking at it in FactoryTalk view, shows datatype as a BOOL even though it's a DINT now. So if you try do to anything with the tag in program, it starts writing to memory outside the UDT and doing funky things.
I've not tried it on a non-safety processor so wondering if it has something to do with tag memory being stored in both redundant processors?
Processor: 1756-L73S GuardLogix
Following steps:
1. Create a UDT online that consists of BOOL, DINT, STRING.
2. Create a tag which is an array of those UDTs.
3. Delete the tag, so that nothing references the UDT
4. Change BOOL to DINT.
5. Recreate tag array
6. Watch processor behave funny including completely locking up and shutting off ethernet connections.
What happens is the RSLogix5000 program correctly sees the new UDT variable as a DINT, but the processor still treats it as a BOOL. You can verify this by looking at it in FactoryTalk view, shows datatype as a BOOL even though it's a DINT now. So if you try do to anything with the tag in program, it starts writing to memory outside the UDT and doing funky things.
I've not tried it on a non-safety processor so wondering if it has something to do with tag memory being stored in both redundant processors?