Ad Widget

Collapse

Zabbix 5.2 and modbus

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • brych
    Junior Member
    • Nov 2020
    • 1

    #1

    Zabbix 5.2 and modbus

    Hi everyone

    I just installed the latest zabbix and I have a problem with modbus.get - I get the message "not supported by zabbix agent". I am using agent version 5.2. Could I ask for any tips on how to deal with this? Query below:

    modbus.get[tcp://192.x.x.x,2,,0,,,,]


    Edit: on zabbix agent 2 its works BUT, now i get message:


    Unsupported endpoint format:

    modbus.get[192.x.x.x,1,3,0,,float,,]

    Last edited by brych; 04-11-2020, 12:24.
  • tim.mooney
    Senior Member
    • Dec 2012
    • 1427

    #2
    Modbus support in Zabbix is pretty new. There may not be very many people here that have experimented with it yet.

    I don't currently have a way to test the modbus support, but I am curious why your second example of the item you're using doesn't include the protocol (tcp://), like your first one did? As I read the modbus.get[] item, it seems like protocol should always be specified?

    Since you are using the agent2, you may want to enable debugging on the agent and see if there's anything useful that's written to the agent log.

    Comment


    • brych
      brych commented
      Editing a comment
      thanks! ofc i miss tcp prefix
  • Atsushi
    Senior Member
    • Aug 2013
    • 2028

    #3
    The examples listed in the materials at the recent summit are as follows.

    modbus.get["tcp://192.168.6.1:511"]
    modbus.get["rtu://COM1:9600:8n"]

    Comment


    • brych
      brych commented
      Editing a comment
      thanks! ofc i miss tcp prefix
  • HarryRink
    Junior Member
    • Dec 2021
    • 1

    #4
    Dear people, I am busy with ModBus-TCP too. One of my items contain modbus.get[{$IF.NAME},1,3,180,,float,,] This works fine already for several month. I build items and triggers, which I display as graphics and send them by mail and Telegram.

    Comment

    Working...