We use a lot of A-B 1771-DA ASCII IO modules to get barcode data in a system recently converted from PLC-2/30's to Softlogix. Now that the programs are in a more readable format I've been going over them with an eye to cleaning up a lot of original logic inconsistencies and 'improving' things with the features available in SL5, ie. structures.
Anyhow, in my wanderings, I read up on the ASCII module and learned some things and got confused about others, namely, the module handshake setup. The manual states that the module toggles READ DATA AVAILABLE when new data is received (data from the device terminated by an end-of-string delimiter) or a change in module status occurs. Monitoring the program shows that READ DATA AVAILABLE is continually cycling, as is the corresponding READ DATA ACKNOWLEDGE sent in reponse by the program even with no new scanner data coming in.
Does anyone have any clues why the module status would change, assuming this is what is happening, without new data received? It's not a big deal, the programs work normally, it just seems like a lot of busywork to me.
Secondary question: What constitutes a change in module status?
Anyhow, in my wanderings, I read up on the ASCII module and learned some things and got confused about others, namely, the module handshake setup. The manual states that the module toggles READ DATA AVAILABLE when new data is received (data from the device terminated by an end-of-string delimiter) or a change in module status occurs. Monitoring the program shows that READ DATA AVAILABLE is continually cycling, as is the corresponding READ DATA ACKNOWLEDGE sent in reponse by the program even with no new scanner data coming in.
Does anyone have any clues why the module status would change, assuming this is what is happening, without new data received? It's not a big deal, the programs work normally, it just seems like a lot of busywork to me.
Secondary question: What constitutes a change in module status?