Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  1. ZABBIX FEATURE REQUESTS
  2. ZBXNEXT-6090

MODBUS support Go agent plugin

XMLWordPrintable

    • Sprint 66 (Jul 2020), Sprint 67 (Aug 2020), Sprint 68 (Sep 2020)
    • 3

      1. Zabbix must be able to work with Modbus out-of-box.
      2. Support Modbus modes (protocols):
        1. TCP
        2. Serial (RTU, ASCII)
      3. Bulk data collection support (responses should be JSON-formatted).
      4. Zabbix must be able to poll data from slave devices.
      5. Two or more Zabbix pollers must not poll the same serial port at the same time.
      6. Support of 16bit, 32bit, 64bit datatypes like unsigned integers, signed integers, floats, and doubles must be implemented.
      7. The item key might look like "modbus.get[<endpoint>,<slave id>,<function>,<address>[,<type>][,<count>][,<endianess>][,<first register>]]". Where:
        1. <endpoint> is an endpoint defining protocol and address. Like "rtu://COM1" or "tcp://192.168.6.1:511".
        2. <slave id> slave id.
        3. <function> modbus function (like "04" to read input register).
        4. <address> registry address.
        5. <type> data type (like "uint16").
        6. <count> number of records to read.
        7. <endianess> endianess configuration.
        8. <first register> address of first register to read.
      8. This functionality must be supported for Zabbix Agent and Zabbix Agent 2 at least for Linux and Windows platforms

        1.
        		 Modbus support for Agent1 Specification change (Sub-task) Closed Aleksejs Sestakovs

            MVekslers Michael Veksler
            palivoda Rostislav Palivoda
            Team C
            Votes:
            2 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: