You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the most recent version of canboat.
Have an Actisense serial NGT-1, not USB.
Running actisense-serial /dev/ttyS1 | analyzer -json | n2kd to try to debug why n2kd_monitor was restarting constantly.
When connecting to the caching server on port 2597, n2kd exits with the below. This can be reproduced every time I try to connect to the caching server. I suspect it's a device on my network (very busy) that is throwing crappy data, but I can't be 100% sure:
Can you check whether the latest commit d0a4c4a fixes this? I couldn't find the issue exactly, but there was some fishy stuff going on in closeStream. Also, if it does still happen, run n2kd in debug mode and check the output.
Well things are more stable with the checkin above, but now port 2597 is completely blank when I request any data from it. I get a TCP connect, and then the session is closed.
Using the most recent version of canboat.
Have an Actisense serial NGT-1, not USB.
Running
actisense-serial /dev/ttyS1 | analyzer -json | n2kd
to try to debug why n2kd_monitor was restarting constantly.When connecting to the caching server on port 2597, n2kd exits with the below. This can be reproduced every time I try to connect to the caching server. I suspect it's a device on my network (very busy) that is throwing crappy data, but I can't be 100% sure:
Connecting to the non-caching json server on 2598, and the NMEA0183 server on 2599 work fine for long periods of time.
The text was updated successfully, but these errors were encountered: