Hello ! New here

[DavideLentini]

Hi all ! I found this repository and I find it amazing !
U-center isn't a perfect software and it's Windows only , so double mess .
I surfed on internet for a practical solution to run on Ubuntu OS , because my idea is to run an NTRIP server with only a raspberry, and I found this .
I want to ask , is possible to start an NTRIP server directly from the console line ?
My idea is to schedule the NTRIP Server with a chrono-like tool on Ubuntu Server , so I would not use the GUI at all , but an .sh file. Thanks all

[semuadmin]

Hi @DavideLentini

In answer to your question, the PyGPSClient GUI uses the pygnssutils library at its core and this provides command line equivalents of much of its client/server functionality, including the gnssserver CLI utility which is capable of being run as a simple NTRIP server.

Have a look at https://github.com/semuconsulting/pygnssutils#gnssserver.

For help, type

gnssserver -h

[DavideLentini]

@semuadmin Hi! Thanks for the answer.
Ok ! This is perfect , is what I need. So if I understand well , I have to use gnsserver , in the mode 1 NTRIP . It's use port 2101 that's good to me . I saw that I have to define an user and password , but could I leave this blank ? So create an NTRIP Server/Caster on port 2101 , but without authentication?
Then another question , I saw in the guide that for first mode (0) I have to define the baudrate of my ublox base , but in the secondo mode (Ntrip) , i don't have to define that right ? So what's difference ? And how i define the MountPoint name ?
Thanks again for your patience :)

[DavideLentini]

@semuadmin
So a little update , I went ahead in my attempts to use the gnssserver in ntripmode 1 .
I own a ublox-base f9p , this one for short :
https://www.google.com/search?q=ublox+f9p+base&tbm=isch&source=lnms&sa=X&ved=0ahUKEwjexcK-kvz-AhVDl4sKHcZWApAQ_AUInQUoAQ&biw=1536&bih=750&dpr=1.25#imgrc=K4u2gKn39eDAHM
The base works , in fact by starting the GUI and connecting I can see all the information , as you can see from this picture :

I closed the GUI and then tried to start this command line :

gnssserver --inport "COM78" --hostip 192.168.1.87 --ntripmode 1 --outport 2101
With this output , then the server seems to have started correctly :
gnssserver --inport "COM78" --hostip 192.168.1.87 --ntripmode 1 --outport 2101
2023-05-17 12:31:39.320901: Starting server (type CTRL-C to stop)...
2023-05-17 12:31:39.320901: Starting input thread, reading from COM78...
2023-05-17 12:31:39.320901: Parsing GNSS data stream from: Serial<id=0x1bc3e1ed7b0, open=True>(port='COM78', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3, xonxoff=False, rtscts=False, dsrdtr=False)...
2023-05-17 12:31:39.823522: Starting output thread, broadcasting on 192.168.1.87:2101...

To answer my previous questions I think I understand that this is the default data of the server :

user=anon
password=password
mountpoint=pygnssutils

I tried connecting with another computer in the network with Mission Planner through the RTK/GPS Inject tool by entering the link :
ntrip://anon:password@192.168.1.87:2101/PYGNSSUTILS
But from Mission Planner I do not see any messages appear , I am able to see though from the server messages , that my computer has connected .

I then tried using u-center client , entering the same data and I am able to receive the mountpoint but then when I go to see the details , I see that some data are missing such as latitude and longitude and baud rate

Connected to the server created by pygpsclient :

Connected to the server created by u-center ntrip caster:

I believe that it is this missing data , that is not letting me connect with Mission Planner , am I doing something wrong ?

EDIT######################################
Ok , after restarting the computer the coordinates also appear from the server created by pygpsclient . But still from Mission Planner always with the same link I get no message ...

[DavideLentini]

@semuadmin
Hello , here I am again :) . I finally managed to get everything working ; I set fp9 as base station , rtcm messages and survey mode in .
First of all I tested everything on Windows , I kept having problems using the gnssserver mode Ntrip caster , in short it created the server but the clients connecting could not receive anything . So I tried the other mode "Socket Server" which sends its packets via TCP protocol , and it worked ! I'm not sure what changes other than the protocol , probably the fact that you don't have to use a mountpoint ; However with this mode I tested with the Mission Planner client and it worked .Having made everything work on Windows , I moved to the raspberry pi2 with Ubuntu Server on it , I installed pygpsclient without a few problems ( due to the outdated version of the raspberry ) but in the end I managed to get everything working on the Raspberry too .Thank you very much for your help

[semuadmin]

@DavideLentini,

Ok glad it's working for you but I'm unclear why you felt it necessary to use socket server mode (--ntripmode = 0)?

Here, for example, is the output from gnssserver running in NTRIP mode using an F9P basestation in FIXED Mode:

➜  ~ gnssserver -I /dev/tty.usbmodem2101 -N 1 -O 2101
2023-05-25 14:46:51.033209: Starting server (type CTRL-C to stop)...
2023-05-25 14:46:51.033236: Starting input thread, reading from /dev/tty.usbmodem2101...
2023-05-25 14:46:51.050261: Parsing GNSS data stream from: Serial<id=0x10189f250, open=True>(port='/dev/tty.usbmodem2101', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3, xonxoff=False, rtscts=False, dsrdtr=False)...

2023-05-25 14:46:51.538714: Starting output thread, broadcasting on 0.0.0.0:2101...
2023-05-25 14:48:34.977041: Client ('192.168.0.23', 65326) has connected. Total clients: 1
2023-05-25 14:48:37.997440: Client ('192.168.0.23', 65326) has disconnected. Total clients: 0
^C2023-05-25 14:49:04.283551: Stopping server...
2023-05-25 14:49:04.283681: Streaming terminated, 3,966 messages processed with 0 errors.

2023-05-25 14:49:04.539682: Server shutdown.

... and here's the corresponding gnssntripclient client log (password is redacted):

➜  ~ gnssntripclient -S 192.168.0.23 -M pygnssutils --user semuadmin --password xxxxxxxxxx
2023-05-25 14:48:34.995992: Using mountpoint pygnssutils

2023-05-25 14:48:34.996470: <RTCM(1084, DF002=1084, DF003=0, GNSSEpoch=597385912, DF393=1, DF409=0, DF001_7=0, DF411=0, DF412=0, DF417=0, DF418=0, DF394=217306378602020864, NSat=6, DF395=1073741824, NSig=1, DF396=63, NCell=6, DF397_01(007)=69, DF397_02(008)=70, DF397_03(014)=70, DF397_04(022)=73, DF397_05(023)=64, DF397_06(024)=71, DF398_01(007)=0.24023438, DF398_02(008)=0.91699219, DF398_03(014)=0.99316406, DF398_04(022)=0.25976562, DF398_05(023)=0.56152344, DF398_06(024)=0.16601562, DF400_01(007,1C)=0.00024521, DF400_02(008,1C)=0.00017905, DF400_03(014,1C)=-0.00045121, DF400_04(022,1C)=1.687e-05, DF400_05(023,1C)=8.684e-05, DF400_06(024,1C)=-2.813e-05, DF401_01(007,1C)=0.00019931, DF401_02(008,1C)=0.00017696, DF401_03(014,1C)=-0.00044412, DF401_04(022,1C)=1.89e-05, DF401_05(023,1C)=9.349e-05, DF401_06(024,1C)=-9.6e-06, DF402_01(007,1C)=12, DF402_02(008,1C)=9, DF402_03(014,1C)=14, DF402_04(022,1C)=11, DF402_05(023,1C)=11, DF402_06(024,1C)=14, DF420_01(007,1C)=0, DF420_02(008,1C)=0, DF420_03(014,1C)=0, DF420_04(022,1C)=0, DF420_05(023,1C)=0, DF420_06(024,1C)=0, DF403_01(007,1C)=32, DF403_02(008,1C)=28, DF403_03(014,1C)=38, DF403_04(022,1C)=30, DF403_05(023,1C)=27, DF403_06(024,1C)=37)>
2023-05-25 14:48:34.997399: <RTCM(1094, DF002=1094, DF003=0, GNSSEpoch=395333000, DF393=0, DF409=0, DF001_7=0, DF411=0, DF412=0, DF417=0, DF418=0, DF394=2814888279801856, NSat=4, DF395=1073872896, NSig=2, DF396=253, NCell=7, DF397_01(013)=86, DF397_02(015)=77, DF397_03(027)=83, DF397_04(034)=84, DF398_01(013)=0.16308594, DF398_02(015)=0.59863281, DF398_03(027)=0.38183594, DF398_04(034)=0.12402344, DF400_01(013,1C)=0.00030738, DF400_02(013,7Q)=0.00031459, DF400_03(015,1C)=0.00019163, DF400_04(015,7Q)=0.00018907, DF400_05(027,1C)=-0.00016314, DF400_06(027,7Q)=-0.00017345, DF400_07(034,7Q)=-3.403e-05, DF401_01(013,1C)=0.00030473, DF401_02(013,7Q)=0.00031033, DF401_03(015,1C)=0.00019399, DF401_04(015,7Q)=0.00018914, DF401_05(027,1C)=-0.00017232, DF401_06(027,7Q)=-0.00017776, DF401_07(034,7Q)=-3.557e-05, DF402_01(013,1C)=14, DF402_02(013,7Q)=13, DF402_03(015,1C)=14, DF402_04(015,7Q)=13, DF402_05(027,1C)=13, DF402_06(027,7Q)=13, DF402_07(034,7Q)=9, DF420_01(013,1C)=0, DF420_02(013,7Q)=0, DF420_03(015,1C)=0, DF420_04(015,7Q)=0, DF420_05(027,1C)=0, DF420_06(027,7Q)=0, DF420_07(034,7Q)=0, DF403_01(013,1C)=46, DF403_02(013,7Q)=43, DF403_03(015,1C)=41, DF403_04(015,7Q)=36, DF403_05(027,1C)=32, DF403_06(027,7Q)=39, DF403_07(034,7Q)=27)>
2023-05-25 14:48:34.997555: <RTCM(1230, DF002=1230, DF003=0, DF421=1, DF001_3=0, DF422=0, )>
etc ...

If you're using invalid credentials, you would typically see an error message like this:

➜  ~ gnssntripclient -S 192.168.0.23 -M pygnssutils --user semuadmin  --password notmypassword                   
HTTP/1.1 401 Unauthorized

If you're using an invalid or unknown mountpoint name, the caster will return the complete sourcetable:

➜  ~ gnssntripclient -S 192.168.0.23 -M notavalidmountpoint --user semuadmin --password xxxxxxxxxx
2023-05-25 15:07:45.922247: Closest mountpoint to reference location (0.0, 0.0) = None, 9999999 km

2023-05-25 15:07:45.922270: Complete sourcetable follows...

['pygnssutils', 'PYGNSSUTILS', 'RTCM 3.3', '1005(5),1077(1),1087(1),1097(1),1127(1),1230(1)', '0', 'GPS+GLO+GAL+BEI', 'SNIP', 'SRB', '', '', '1', '0', 'sNTRIP', 'none', 'N', 'N', '0', '']

If you're connecting but seeing no data, that's probably because your F9P is not configured as a basestation and is not actually outputting RTCM messages.

PS as for installing PyGPSClient on a Raspberry Pi 2, unless you have a compelling reason for using Ubuntu I would strongly recommend you use the stock Raspberry Pi 32-bit OS image - you'll find it runs a lot faster and smoother than Ubuntu, which is not yet fully optimised for the RPi. If you can stretch to a Raspberry Pi 4 with 8GB RAM, you can also run the 64-bit version. There's very little practical advantage in running Ubuntu Server on this platform.

[DavideLentini]

Hello @semuadmin ! The only reason I am not using NTRIP 1 mode is because with the clients I use I can connect to the server but I am not getting any RTCM message . The fp9 base is configured correctly , in fact when I set the Socket Server mode everything works perfectly and I can connect to the server created by pygpsclient . The thing is that with pygpsclient gnsssclient , I can connect to pygpsclient Ntrip server and receive messages , but with other clients it does not work . I will investigate the problem better , but I don't think it is a problem with pygpsclient as much as with the clients I am using .
Does it make any difference to use Socket Server mode or does it just change the communication protocol ( I have to connect remotely to the base ) ? Tomorrow I'll try again with Ntrip Mode 1 , to see if I can understand something . In while if you want to debug with me this problem , you can download Mission Planner from their site , and see if you can connect to your Ntrip server created by pygpsclient , it would be very helpful :)

As for the Raspberry Pi2 Model B , for now it is working fine , yesterday I tested it remotely and it stayed on with the server running all day without giving any problems . I will keep you updated though , unfortunately Raspberry Pi 4 are almost unavailable here where I am .

[semuadmin]

In terms of the difference between 'socket-server' mode and 'ntrip' mode - the NTRIP protocol defines basic authentication protocols and provides an API for downloading the source table (list of available mountpoints). Once you've authenticated into a given mountpoint, the RTCM messages are transmitted over a standard TCP socket, so in this sense the two modes operate in exactly the same way. But, while you can 'get away with this' using gnssserver because it doesn't force you to authenticate in socket server mode, you wouldn't be able to connect to a third party NTRIP caster in this way - you've have to use a proper NTRIP client.

Out of interest, which other NTRIP clients have you been using? gnsserver has been tested using quite a few and I've not come across any major problems to date.

[DavideLentini]

Sorry I edit the message . I'm using Mission Planner . In Mission Planner you have the option RTK/GPS Inject in Setup Tab where you can connect to an NTRIP Server or TCP Client .
If you could try to connect to your own Ntrip server created by pygpsclient , it would be most useful to see if I am doing something wrong .
Thanks for the clarification about the different protocols . Well personally for the project I want to do , which is very small , I am not interested in authentication or mountpoints list ( as long as it works :) ) .