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\ flfml kevja2qjah8bzqy serial connection or tcp connection to a modbus device modbus ascii docid\ udqmlpblistopgir1oqq4 modbus ascii (gen1) docid\ crp5cyf8aotvtlsmr96sy modbus ascii advanced docid\ tklvy5et66zzm50tbwrwz serial connection to a device using modbus ascii modbus rtu docid 0zqahlthi5b7yl4jivkpe modbus rtu (gen1) docid 9vfszscm7ftythghvfq0j modbus rtu advanced docid 63wcqxtekwttbkhoilnqa modbus rtu offset (gen1) docid\ ol 0e7d7vwuxs0uobyc79 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\ e7tje7skztwbmpzcvo8vx tcp connection to a modbus server which has one or more modbus rtu connections modbus tcp docid 0mfihhpumlvdlpaf2cxrd modbus tcp (gen1) docid\ tzbyzs lzappducatmupx modbus tcp offset (gen1) docid\ nr3egr5m1kgx sokx4xc7 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\ ijfxxev4ls6mqrjnpw8zx modbus udp (gen1) docid\ awgziruh587utfpbt4q6d udp connection to a modbus device