TheWaterboy
Lifetime Supporting Member + Moderator
Anyone seen a logix v32 or v33 get a stuck EN bit on a MSG? (also an L61 v20 oddly enough)
I can put an AFI in front of it and still can't get the .EN to clear.
I got into the MGS tag itself and I can clear the .EN but not the .ST, it sets right back to true.
I replace the MSG in logic with a new one with et same UDT and that one does the same thing.
The original MSG that is now unused but still has the ST bit set and will still not allow me to clear it in the tag editor.
The MSG uses a UDT (BOOL[64] BOOL[64]DINT[64]) that has been working fine for many months, yet now seems to be the reason this occurs.
This started when I stored the recipient PLC's program to EEProm which I have done several dozen times before yesterday. This obviously would have caused the MSG to fail but also has created this condition.
RA Support found a note that said this happens when the remote comms are interrupted which is likely to be what happened but said it was fixed in v33.
I updated to v33 and the problem remains. As a test I created a similar MSG in an L61 and that does the same thing! Again these have been working fine for months on V32
Additionally I can't edit the existing MSG since the ST bit is set and the PLC thinks its in a active state, so I have to create a new MSG to try new things leaving dead MSG tags in the DB with bits I can't clear.
I created one to read DINTs from the same endpoint and that works fine. But I have 3 MSG's tags in the tag list that have the ST bit set.
To make this worse... Since the PLC considers the MSG active, I can't change the PLC state from Run to Program... at all. I have to cycle power to regain control.
And how is YOUR day going?
.
I can put an AFI in front of it and still can't get the .EN to clear.
I got into the MGS tag itself and I can clear the .EN but not the .ST, it sets right back to true.
I replace the MSG in logic with a new one with et same UDT and that one does the same thing.
The original MSG that is now unused but still has the ST bit set and will still not allow me to clear it in the tag editor.
The MSG uses a UDT (BOOL[64] BOOL[64]DINT[64]) that has been working fine for many months, yet now seems to be the reason this occurs.
This started when I stored the recipient PLC's program to EEProm which I have done several dozen times before yesterday. This obviously would have caused the MSG to fail but also has created this condition.
RA Support found a note that said this happens when the remote comms are interrupted which is likely to be what happened but said it was fixed in v33.
I updated to v33 and the problem remains. As a test I created a similar MSG in an L61 and that does the same thing! Again these have been working fine for months on V32
Additionally I can't edit the existing MSG since the ST bit is set and the PLC thinks its in a active state, so I have to create a new MSG to try new things leaving dead MSG tags in the DB with bits I can't clear.
I created one to read DINTs from the same endpoint and that works fine. But I have 3 MSG's tags in the tag list that have the ST bit set.
To make this worse... Since the PLC considers the MSG active, I can't change the PLC state from Run to Program... at all. I have to cycle power to regain control.
And how is YOUR day going?
.