:)Thanks Greg. That is what I thought I was doing. I latched the error bit and had that turn on an output - that worked fine. The method of test/verification was to simply disconnect the data cable. However, I did not seem to be able to clear the latch when ever the the cable was reconnected. I will go back and enter in the sample rung examples and see what happens. Does it matter that I am using IBOX701 (RX) for multiple data?
Example: I am reading the slave TA0, a VMemory location that is incremented and also the VX0 slave input memory. The reads all come through with no problems. I am wondering if having multiple error bits due to the multiple IBOX instructions might have any bearing on this?
Another , but different subject: The manual indicates that the DL260 serial port#2 can only use the raw ASCII as either in or out but not both. I don't understand why that would be the case as when using DirectNet , both TXD and RXD or used? I am interested in incorporating an external micro based serial I/O to communicate with the PLC using only ASCII in/out.
Thanks
EDIT:: After doing a little more trial coding, I think the bottom line I am unable to use, as in you example above, the actual error bit (C0 example) except to latch it. It seems that I cannot use the bit to check for
-|/|- .
In other words, you can not use the error bit to clear a latched error bit using the scheme mentioned in your post.
Thanks
Update: Well. I wasn't using the 'success' bits to clear the latch, that worked fine.