I have a Micrologix 1400 BXBA that is set up in my Ignition gateway. I can browse to the input (I) and output (O) locations through the OPC browser. For the most part all works as expected. I decided to set up all the embedded I/O in my SQLTag tree for use with some testing I am going to be doing. This is where I uncovered a bit of a head-scratcher…
On the input side, I pulled in the 16 bits in word 0 (I:0.0/00 - I:0.0/15). These all work fine as I actuate the inputs on the PLC. However, when I pulled in the 4 bits in word 1 (I:0.1/00 - I:0.1/03), they did not work as expected. What’s more, is that it seemed to make some of the other bits act funny as I watched my tag tree in the Designer (e.g. bits turning on and off unrelated to the specific input I was manipulating). As soon as I removed these 4 bits from the tag tree, everything was fine again. Then I added the 4 words representing the analog inputs (I:0.4,.5,.6,.7). The subscription to any or all of these words yielded equally anomalous behavior. And likewise, dumping them returned things to normal.
On the output side, this came up again in similar fashion. Now all the outputs on this model fit in word 0 (I:0.0/00 - I:0.0/11) so the digital outputs were all fine. Then adding the 2 analog inputs (O:0.4,.5) made things act weird. In RSLogix, I can see it try to set the word to the correct value (it did) but then after the gateway polled the tag again (1 second scan class) it reset to a value of 1.
Is there a limitation to the built-in ML1400 driver that would cause these issues when accessing anything outside word 0?!