2018-03-12, 01:46 PM
(2018-03-11, 11:33 PM)wmrae Wrote: NMEA data is coming from the other computer via UDP, I set it up in the nmea0183 tab and it is working when the pi first starts
using the diagnostic window shows the stream when the pi first starts but after a while (roughly 10 min, going to time it this evening) it stops
restarting kplex (restart button on nmea0183 tab) doesn't restore the stream
when the stream is lost the wifi still works for pinging and web browser
i will try debugging mode next and see if the log provides any insight.
Hmm, sorry might be beyond me. Another thing you can try -
Ever used node red? It can be a really useful debug tool.
On the Pi look at 10.10.10.1:1880 then press control 'i' to insert and copy / paste the code below and press deploy. Hopefully that should give you a little piece of node-red which looks for UDP on a port and displays anything coming in it in a debug window, need to turn off kplex looking at the port in the nmea tab . Might let you see if any UDP messages are still coming in but just getting lost somewhere. When you deploy then new code if something else is reading that port you'll get an error message.
(node red will be faster on the laptop, you can see it there but finding the Openplotter IP address in the Wifi AP tab and using that IP address :1880)
Sorry , bit low on detail but lots node red help on the web, & you seem to know what you're talking about.
Code:
[
{
"id": "1808badf.4316d5",
"type": "udp in",
"z": "3f30ea31.da3756",
"name": "",
"iface": "",
"port": "55557",
"ipv": "udp4",
"multicast": "false",
"group": "",
"datatype": "utf8",
"x": 295,
"y": 892,
"wires": [
[
"b6f00441.812bd8"
]
]
},
{
"id": "b6f00441.812bd8",
"type": "debug",
"z": "3f30ea31.da3756",
"name": "",
"active": true,
"console": "false",
"complete": "false",
"x": 570,
"y": 880,
"wires": []
}
]