question

marcus-spranger avatar image
marcus-spranger asked

Enabling Modbus TCP in Cerbo GX triggers error due to access of address 40000

This has been asked before here:
https://community.victronenergy.com/questions/106749/victron-integration-with-home-assistant-using-modb.html

but there has been no real answer unfortunately so I am trying again.

I would like to use the Modbus TCP interface to read out and monitor various values of the system, which consists of:

  • 2x MultiPlus II 5000
  • Cerbo GX (firmware version 2.84)
  • 2x Freedom Won batteries
  • Fronius Primo 8.2
  • BlueSolar Charger MPPT 150/35

As soon as I enable the Modbus TCP service, there seems to be a device making a query for address 40000, which doesn't exist:

modbus-2.png

This request seems to happen about once per minute. Not sure which device has unit ID 126, but the IP address 192.168.1.9 is the address of the Cerbo GX.

How can I turn off those invalid queries resulting in that error?

Thank you.

Modbus TCP
modbus-2.png (28.3 KiB)
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

1 Answer
lifeingalicia avatar image
lifeingalicia answered ·

ID126 is usually an external device Check des devicelist on your vm portal.

Something is trying to read 2 registers starting at 40000 - Any homeautomation software trying comunication?

You have to hit the right devid and the registers according to victron spred sheet

1 comment
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

marcus-spranger avatar image marcus-spranger commented ·

Unfortunately I missed your reply but thank you for that. Let me investigate further.

0 Likes 0 ·

Related Resources

Modbus TCP Basics