Critical: Cerbo GX (Venus OS 3.62) Cannot Connect to Outback Mate3s via Modbus TCP (TCP level issues

Hello Victron Community and especially @Kevin Windrem,

I am experiencing an extremely baffling and persistent issue trying to get my Cerbo GX (running Venus OS 3.62) to communicate with an Outback Mate3s (which serves Modbus TCP data from FM60 charge controllers) on port 502.

I have systematically troubleshooted this for a considerable amount of time, and the current state of my system presents contradictory and illogical facts, which points to a deeper problem than standard configuration.

My Setup:

  • Device: Victron Cerbo GX (hardware, not a Raspberry Pi Venus OS)
  • Firmware: Venus OS 3.62 (clean re-install, confirmed just today)
  • Target Device: Outback Mate3s (IP: 192.168.8.102, serves Modbus TCP on port 502 for FM60s)
  • Cerbo GX IP: 192.168.8.171
  • Goal: Integrate FM60 data from Mate3s into Venus OS, ideally via dbus-modbus-client and displayed with Dashboard Widgets.

Problem Evolution & Contradictory Facts:

Initially, the problem was that the Cerbo GX simply could not establish a TCP connection to the Mate3s on port 502, despite extensive checks.

  1. Ping Works: The Cerbo GX (192.168.8.171) could successfully ping the Mate3s (192.168.8.102). This confirms basic Layer 3 network connectivity.
  2. Mate3s is Serving: Another Linux device (Raspberry Pi, 192.168.8.1) could successfully connect to the Mate3s on port 502 (e.g., using nc or a Modbus client), and it could read Modbus data. This confirmed the Mate3s itself was properly serving Modbus TCP.
  3. Cerbo Outbound TCP Works Generally: The Cerbo GX could make outgoing TCP connections to other devices (e.g., SSH from Cerbo to the test Raspberry Pi on port 22).
  4. Initial Cerbo-Mate3s TCP Failure: Crucially, the Cerbo GX could not connect to the Mate3s on port 502. A nc 192.168.8.102 502 command from the Cerbo would fail, indicating a problem at the TCP connection establishment level. This was the “1+1=3” scenario where all logical checks pointed to success, but connection failed. Firewall on Cerbo was temporarily disabled to rule it out.

Recent Development (and new, critical problem):

I performed a tcpdump on the Cerbo GX (192.168.8.171) to capture traffic between it and the Mate3s (192.168.8.102) on port 502. To my surprise, the tcpdump output showed perfectly successful TCP handshakes, data exchange (PSH-ACK packets), and graceful connection teardowns. This indicates that the TCP connection is in fact working and data is being exchanged.

  • (Optional, you can paste a small relevant snippet from your tcpdump here if it’s not too long, showing the SYN/SYN-ACK/ACK and PSH-ACKs)

However, after performing a clean re-install of Venus OS 3.62 firmware, I’ve hit an even more fundamental issue:

  • I am logged in as root via SSH.
  • When attempting to use systemctl or journalctl (even with their full paths /bin/systemctl and /bin/journalctl), I receive -sh: ...: No such file or directory.
  • Running ls -l /bin | grep systemctl, ls -l /bin | grep journalctl, ls -l /usr/bin | grep systemctl, ls -l /usr/bin | grep journalctl, and even find / -name systemctl 2>/dev/null and find / -name journalctl 2>/dev/null yields no output.

This indicates that the core systemd binaries (systemctl and journalctl) are missing entirely from my Venus OS installation, even after a clean re-flash.

Questions/Seeking Expert Advice:

  1. Given the tcpdump now shows successful TCP communication, what would cause the dbus-modbus-client (or the underlying mechanism) to still not integrate/display the Mate3s data? (assuming the systemctl issue can be resolved).
  2. More urgently, what could cause systemctl and journalctl to be completely missing after a clean firmware re-flash to Venus OS 3.62? Is this a known issue, or does it point to a deeper problem with the Cerbo GX hardware or the firmware file itself?
  3. Regarding GuiMods: I understand Venus OS 3.62 uses GUI v2, and the classic GuiMods is incompatible. I plan to use Dashboard Widgets once the core system is stable and dbus-modbus-client is functioning.

I am at a loss as to why these core binaries would be missing after a fresh install, and why the TCP connection issue seemingly resolved itself without clear action, only to reveal this deeper problem. Any insights or guidance, especially from @Kevin Windrem or other Victron developers, would be immensely appreciated.

Thank you for your time and assistance.

That’s normal, VenusOS doesn’t use systemd.

Is there a way to get the Cerbo GX to read the Mobus data from my Mate3s and display it on a widget?

Regards,

Gilles Beaulieu, Master Electrician
Beau’s Electrical Services Inc.
beauselectrical@gmail.com

Tel: 705-929-8365