kekrahulik
Member
Just sharing an experience with a weird one that had 3 EE's scratching our heads for a bit...
A PLC5 program was converted to CLX, version 20 in an L71 processor. With the conversion, PLC5 Data File N15 (used for HMI display values) was converted to a 250 INT array N15[xx].
The CLX program worked. A panelmate (not a panelview) displayed everything correctly. Wonderware did not display things right and had us rather baffled.
At first, it seemed like Wonderware wasn't talking to the CLX, but when we looked at the diagnostics of the DASABCIP server we could see that tags were actively being read from the CLX. For example, if we looked at the WW Tagname "Servo_Alarm" (read-only) that looks at the bit N15[53].9 we could see in the DASABCIP server that this bit was toggling on and off. However, this bit was not ever changing in the CLX program.
After some stumbling around, we found and proved that even though the DASABCIP server showed it is reading N15[53].9, it was actually reading the CLX tag N15[51].9. In fact, it was reading 2 values off throughout the entire N15[xx] array. So N15[xx] was actually reading N15[xx-2] (we didn't figure out what it was trying to read for N15[0] or N15[1]). Wonderware was sucessfully reading other tagnames in this CLX, but this was the only array that it was trying to read.
Solution: We updated the WonderWare DASABCIP server to the latest version and all was good. (not sure what the old version was).
Just an FYI for anyone it may help.
A PLC5 program was converted to CLX, version 20 in an L71 processor. With the conversion, PLC5 Data File N15 (used for HMI display values) was converted to a 250 INT array N15[xx].
The CLX program worked. A panelmate (not a panelview) displayed everything correctly. Wonderware did not display things right and had us rather baffled.
At first, it seemed like Wonderware wasn't talking to the CLX, but when we looked at the diagnostics of the DASABCIP server we could see that tags were actively being read from the CLX. For example, if we looked at the WW Tagname "Servo_Alarm" (read-only) that looks at the bit N15[53].9 we could see in the DASABCIP server that this bit was toggling on and off. However, this bit was not ever changing in the CLX program.
After some stumbling around, we found and proved that even though the DASABCIP server showed it is reading N15[53].9, it was actually reading the CLX tag N15[51].9. In fact, it was reading 2 values off throughout the entire N15[xx] array. So N15[xx] was actually reading N15[xx-2] (we didn't figure out what it was trying to read for N15[0] or N15[1]). Wonderware was sucessfully reading other tagnames in this CLX, but this was the only array that it was trying to read.
Solution: We updated the WonderWare DASABCIP server to the latest version and all was good. (not sure what the old version was).
Just an FYI for anyone it may help.