2017-05-30, 07:38 PM
(2017-05-30, 06:44 PM)Sailoog Wrote: We would need to isolate the problem.
What happens if you disable all settings (node-red, sensors, actions, NMEA 2K devices, GPIO, 1W...)? Are you generating NMEA 0183 from node-red or NMEA generator?
If there is still crash we would need to see what NMEA 0183 sentence is generating the error, try to open the NMEA 0183 inspector or the opencpn NMEA inspector.
Ok, I have erased all the stuff out of the OpenPlotter system other than what is under the USB manager tab and what is under the NMEA 0183 tab. If, under the NMEA 0183 tab, I highlight the line responsible for the NMEA 0183 feed from the chart plotter, and select 'diagnostic', I get a nice flow of 'stuff', no crashes and no errors in the debug window. If I go to the SignalK tab and open a diagnostic window I get nothing. If I then restart the signalk server, I get a bunch of data in the signalk diagnostic window and then I get the error messages in the console window that I used to start openplotter. The data feed to the signalk diagnostic window has stopped at this point.
Based on this, it would seem that nothing under NMEA 0183 is causing the crash but that the crash happens when signalK starts.
I should add that I go into the pi via another computer via VCN and wifi and interact with the pi that way.
Also, while all this is happening, the remote computer that is used to go into the pi also runs OpenCPN including a dashboard that shows the NMEA 0183 feed from the chart plotter - I see depth, speed and apparent wind angle and speed. This dashboard display has never crashed which also seems to suggest that the NMEA 0183 feed is getting to the pi just fine and the pi then distributes this information via wifi to any computer listening just fine.
I hope this makes sense and answers your question. Let me know if I can test anything else.