question

Update on this - the NMEA serial data is not being past from my router since a restart of the router. Looking into the cause of this.

Use this Script to run all in Background with restoring the Connection:

# get GPS from router
/usr/bin/socat tcp-connect:192.168.88.1:10000 pty,link=/dev/ttyTCP10000,raw,nonblock,b115200
while [ `ps|grep gps_dbus|grep -v grep|wc -l` -eq 0 ]
do
  sleep 1
  /opt/victronenergy/gps-dbus/gps_dbus -s /dev/ttyTCP10000 -b 115200 -t 0
done &

-> your "&" was on the wrong line - now it will recover.

Holger

Thanks Holger,

I see my error thanks. Ive changed my script however still have a problem not receiving any NMEA data on that port. Ive got a post on the mikrotik forums so hopefully will have some answers soon.

Kind regards, Mike.

Hello Miike

Here is my Script, using it for one Year to get the GPS data from another Server which sends it via UDP stream on Port 8500. I did not modify any other Script on the Venus. No Problems at all with the Victron Updates. Now at 2.90-large-beta20. Check if your Server sends the UDP Stream after rebooting.

nano /data/rcS.local

#!/bin/bash

# SetupHelper reinstall all Venus mods
nohup /data/SetupHelper/reinstallMods > /dev/null &

#
# get GPS from router
#
/usr/bin/socat UDP-RECV:8500 pty,link=/dev/ttyUDP8500,raw,nonblock,echo=0,b115200 &

while [ `ps|grep gps_dbus|grep -v grep|wc -l` -eq 0 ]
        do
sleep 1
        /opt/victronenergy/gps-dbus/gps_dbus -s /dev/ttyUDP8500 -b 115200 -t 0
done &

exit 0

Thanks, turns out my router (Mikrotik LTAP Mini) switches the serial0 port between a DB9 mounted externally and the GPS port and the only way to specify you want to "switch" to the internal GPS port seems to be to enable GPS on the router making the port unable to be forwarded to a port (TCP in my case). I did have it running possibly by tricking the router into switching over somehow but have not been able to replicate it.

My LTE card also has onboard GPS so im just working through forwarding this to the TCP port and getting a script working. I wish I could use UDP as I think it would be more reliable during a router reboot (I think TCP would fail in this case) however mikrotik does not seem to provide provision for this using the "remote access" tool.

Will update soon with a working solution.

I decided to do the same with the LtAP mini in my bus to feed the GPS to my house system. @nzmikec I updated the mikrotik forum with my solution to the GPS feed problem.

Mikrotik Forum: LTAP Mini serial port / GPS

As for the code running on the GX I have it split into two daemontools services, one for the virtual serial port and the other for gps_dbus. I prefer this approach as it blends well with the current services and handles the logging, restarting, etc... I also have a rc.local script that takes care of adding the services back after updates. If anybody is interested I can post the code here.

Thanks so much @Greg , would love to see your GX scripts. Mine currently won't survive a router reboot as the connection is dropped. I had been running a workaround on the latp using my LTE cards GPS.

Great work on the Mikrotik script and workaround of the serial port bug!

Hmm, I can't seem to get the remote access for the serial port working. It just says invalid when I attempt to enable it. When I run @Greg 's script it just says device is busy check \port

One thing that is different is I have the LTE version: LtAP mini LTE (R11e-LTE-US)