Comm conflict

Modifications
,
1

I’ve had intermittent issues with the #153 ‘No route to host’ errors and losing connections to VRM and occasionally the firmware online updates would fault out. It would come back after a reboot or I tried a few things but, I could never trace it down to anything solid.

I think I’ve narrowed it down to a conflict between the Wifi and the Ethernet port. WiFi is static at 10.0.0.200 and the Ethernet is 192.168.128.100 to align with a modbus TCP/IP I/O module.

It appears the Cerbo occasional tries to use the Ethernet port connected to a relay module for internet access and fails. Possibly based on signal strength? I found early on that both ports can’t share a subnet or it always tries to use the Ethernet port and won’t do anything if there isn’t internet available there. Splitting them up worked great on the bench, now that it’s in the vehicle I’m starting to see random issues.

Any ideas?

2

In this case, I would try to make sure that there is no gateway or DNS ip specified for the Ethernet port in the cerbo.

1 Like
3

Thanks Mike, I tried that already. Today I was poking around with some interface tools and it appears a missing eth0 gateway config gets pulled from WiFi0 gateway value?

I switched the Ethernet & relay device IP to something in the 169.254.1.x range, a link-local address which the interface defaults to when switching from auto to manual IP config. Interestingly, the routing table doesn’t show the gateway entered in the Ethernet port or the WiFi port.

So far both VRM and the modbus-TCP device are working well, hopefully it will continue.

Update:
24 hours later and no issues with VRM and the modbus-TCP device. I haven’t seen a GX device overload message either.

4

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.