Modbus

note by default, the modbus drivers monitor holding address 0 for connection status if the modbus device does not have holding address 0, then it will not show the "connected" status you will still be able to read data from the device here are the major differences for the modbus drivers driver use enron modbus docid\ u6thmlsko9gqxunhtzoyu serial connection or tcp connection to a modbus device modbus ascii docid\ xjnzxfmvinivjw0uvrnk modbus ascii (gen1) docid 7vd8mms7cpyki464z24ow modbus ascii advanced docid\ g9zyaglbjlq 85rcm7zjz serial connection to a device using modbus ascii modbus rtu docid\ kkcoqyzr 5 u3jsjo5hmt modbus rtu (gen1) docid 0jvou1tyaoxh3jkgkynwh modbus rtu advanced docid\ rjn7aeez gnnefoekujv modbus rtu offset (gen1) docid 38hsfsb6ptswkdvvkvzgl serial connection to a device using modbus rtu the gen2 driver has an option for zero based addressing and therefore replaces both gen1 rtu drivers modbus rtu over tcp docid\ m31ipbtalamgrc2vcpqwc tcp connection to a modbus server which has one or more modbus rtu connections modbus tcp docid\ coklxyoo 4pvwy1pacak modbus tcp (gen1) docid\ lzacr7kdd6ei geqagum modbus tcp offset (gen1) docid\ fviqukkldvhrzh5avhpjl tcp connection to a modbus device the gen2 driver has an option for zero based addressing and therefore replaces both gen1 tcp drivers modbus udp docid\ s7finj 8mdcgg7jxhhei6 modbus udp (gen1) docid 29dgyxcb6hq2v67baqafa udp connection to a modbus device