That’s strange, indeed. – I just installed ser2net from git, expanded ser2net.yaml withconnection: &con00
accepter: tcp,6000
enable: on
connector: serialdev,
/dev/ttyAMA0,
921600n81,local
connection: &con01
accepter: tcp,6001
enable: on
connector: serialdev,
/dev/ttyAMA0,
38400n81,local
connection: &con02
accepter: tcp,6002
enable: on
connector: serialdev,
/dev/ttyAMA0,
115200n81,local
so that I have the serial output in different speeds on ports 6000ff., made sure that no firewall is blocking, stopped gspd etc., did my sudo systemctl start ser2net, and then simply chose tcp://my.ip.adress:6000 (or whichever port serves the hat’s baud rate) in 2nd most recent u-center (the brand new one appears to not like IP connections (yet?).
Speed is chosen correctly on your setup?
Best regards, Michael
P.S.: I’m using a u-blox ZED-F9P hat on my Raspberry PI4 with Raspbian/Debian.
On 02/10/2021 12:21, Michael Byczkowski wrote: Indeed, David, that would be so great to have!
With regards to ser2net, everything works much smoother with version 4.3.3.
Best regards,
Michael
I've now tried two approaches, and while both /may/ be sending data (how to test?), neither stream is seen by u-center. Of course, it's most likely my errors! I tried to broadcast UDP, and then to send TCP. Perhaps I have the client/server relation the wrong way round as I would expect simply to make a TCP stream available rather than having to specify the device in "nc". I have less experience of UDP, except within the context of NTP offering a service, and needing to have a firewall entry allowing incoming connections. Anyway, here's what I tried: UDP method: gpspipe -r | nc -u -b 192.168.0.255 12101 TCP method: gpspipe -r | nc 192.168.0.8 12101 So if anyone has any bright ideas... Cheers, David -- SatSignal Software - Quality software for you Web: https://www.satsignal.euEmail: david-taylor@blueyonder.co.ukTwitter: @gm8arv
|