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\ dbtnkppzeg0hb2lys0fpx serial connection or tcp connection to a modbus device modbus ascii docid\ oeohqibxp46l0dwtp xmz modbus ascii (gen1) docid\ xhv tpwiacyqhapzofoia modbus ascii advanced docid\ dggp6kmsuj7b3cqj6lkp8 serial connection to a device using modbus ascii modbus rtu docid\ clmeyaokmeszsj9gmplb modbus rtu (gen1) docid\ ufdsdcj0htv8fkv2ybetm modbus rtu advanced docid\ vo594n1omayqaztcnfxr modbus rtu offset (gen1) docid\ lruq4f sopiyuhzdmguw3 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\ i6fv1behsy qnwxc fls tcp connection to a modbus server which has one or more modbus rtu connections modbus tcp docid\ nber6llrzwtlko50 hv3v modbus tcp (gen1) docid\ qip9f4qgcya63nm3owawm modbus tcp offset (gen1) docid ec6me 3t4rl91uo8cz8t 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 2tsq h8tueu mt9d zgs modbus udp (gen1) docid\ jz6slfj9p6g2la9kstwmv udp connection to a modbus device