I have a Cerbo GX running Signal K.
The connection (provider) interface in Signal K is set to the defaults: i.e. n2k-on-ve.can-socket using canboatjs on can0.
The system is mostly stable, but from time-to-time the CAN data stream in Signal K dries up. When this happens the Signal K dashboard reports 0 deltas per second against the usual 40 or so. Enabling logging on the CAN connection yields no useful information: the log just stops with no evidence of a causative event. Rebooting Signal K restores normal operation ... until the next time.
When the Signal K connection has died, CAN devices in Venus (like my fluid sensors) remain active, so the physical CAN interface and associated N2K data feed is obviously still available, but not being presented to / processed by Signal K.
Has anyone else noticed this issue? Any ideas on debugging from both the Venus OS and Signal K perspective would be helpful.
Paul