[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


From: rhowitt
Subject: RE: GPSD - NTRIP Client
Date: Thu, 9 Jan 2020 16:10:40 -0500

Th email I received from NYS CORS  is below, it shows the URL to use.  My UserName and Password do not contain any special characters ( e.g. ‘@’ ).


I will update to version 3.20


I will also try using the programs Greg recommended to see if that gives me further clues.


Rick Howitt



>>>Dear Richard Howitt

>>>Thank you for activating your registration at NYSNet.

>>>You are now allowed to log in at >>>with user name  NNNNNNN.


>>>This login is valid for your Spider Business Center account and all your >>>NYSNet subscribed real-time Ntrip and SpiderWeb services.

>>>Please Note: The URL for the RTN is: Please refer to the >>>website for appropriate Ports and NTRIP

>>>Mount Points.



-----Original Message-----
From: gpsd-users <gpsd-users-bounces+rhowitt=address@hidden> On Behalf Of Gary E. Miller
Sent: Thursday, January 9, 2020 3:23 PM
To: address@hidden
Subject: Re: GPSD - NTRIP Client


Yo address@hidden!


On Thu, 9 Jan 2020 12:57:05 -0500

<address@hidden> wrote:


> I have been using GPSD for the past 5 year with a u-blox GPS and have

> been pleased with the performance.




> GPSD (Version 3.17 )  was installed from app-get


A bit long in the tooth.  3.20 is current.  3.17 is before the F9P was a thing, so support for newer features of the F9P do not exist.


> We are using the F9P so that the system can get to RTK accuracy.


Consumer RTK has been around for well over a decade.  My experience with the F9P accuracy is a bit disappointing.  Good, but does not match the hype.


> For RTK base-station reference the project will be using NTRIP

> casters. Since we are in NewYork the initial testing is using the NYS

> CORS network.


That will be a problem.  the F9P needs proprietary RTCM messages that are not part of CORS.


> I have been able to use the U-Center application  (

> ublox software)   and connect to the CORS network and push this data

> to the F9P.


No need for u-center with gpsd 3.20.


> gpsd:ERROR: initial GPS device

> ntrip://UUUUUUUUU:address@hidden:8082/NYPF open failed


Just as it says: "open failed".  Either your URL is wrong, or the handshake is wrong.  That URL does not look right to me.  gpsd needs a full ntrip URL, not an autonegotiate URL.


> gpsd -n /dev/ttyACM0

> ntrip://UUUUUUUUUUUU:address@hidden:8082/NYPF -N -D 5     (

> username and password are filled out correctly )


The URL still looks short to me, and without a working u/p, no way we can test independently.


> How can I get gpsd to use the NTRIP data from NYS CORS?


Figure out the full URL.


> If you need more information let me know.


The u/p would help.





Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703

               address@hidden  Tel:+1 541 382 8588


                   Veritas liberabit vos. -- Quid est veritas?

    "If you can't measure it, you can't improve it." - Lord Kelvin

reply via email to

[Prev in Thread] Current Thread [Next in Thread]