Thank you Jaka that helps me a lot. But I have right now a diffrent problem. I am trying to make a NTP server. I am using PocketBeagle and GPS module - UART GPS NEO-7M-C . I have connected it like that: PB_UART4-Tx(P2.07)- GPS NEO-7M-C Rx PB_UART4-Rx(P2.05) - GPS NEO-7M-C Tx
After running gpsd with /dev/ttyS4 I'm getting normal GPS data (NMEA) using cgps but when I run chrony It is not giving me any result from my GPS source. In dmesg I can see that gpsd is forces my device (/dev/ttyS4) as new pps source: [ 385.668490] pps_ldisc: PPS line discipline registered [ 385.670656] pps pps1: new PPS source serial4 [ 385.670761] pps pps1: source "/dev/ttyS4" added Does anyone know how to turn off pps support in gpsd. So I can get only GPS time in chrony? poniedziałek, 15 marca 2021 o 14:02:39 UTC+1 Jaka Koren napisał(a): > To Jack, > you cannot run gpsd separately because operating system is trying to run > it as a service process. It fails, but the process still seems to be > "running" in some way. > Stop it first with service gpsd stop, then you should be able to run gpsd > from userspace normally. > > sobota, 13. marec 2021 ob 20:00:50 UTC+1 je oseba Jack Czerkawski napisala: > >> Hello, >> >> I am trying to run NTP server on my PocketBeagle with GPS and PPS time >> source. To establish that I am following your notes. >> >> However when I try to run gpsd it is giving me output like this: >> >> :$ gpsd -D 5 -n -N /dev/ttyO4 /dev/pps0 >> gpsd:INFO: launching (Version 3.17) >> gpsd:IO: opening IPv4 socket >> gpsd:ERROR: can't bind to IPv4 port gpsd, Address already in use >> gpsd:ERROR: maybe gpsd is already running! >> gpsd:IO: opening IPv6 socket >> gpsd:ERROR: can't bind to IPv6 port gpsd, Address already in use >> gpsd:ERROR: maybe gpsd is already running! >> gpsd:INFO: command sockets creation failed, netlib errors -1, -1 >> >> Deep-dive into systemctl shows: >> >> systemctl status gpsd.service >> ● gpsd.service - GPS (Global Positioning System) Daemon >> Loaded: loaded (/lib/systemd/system/gpsd.service; disabled; vendor >> preset: enabled) >> Active: failed (Result: timeout) since Tue 2021-03-09 18:48:39 UTC; >> 28min ago >> >> Mar 09 18:47:09 beaglebone systemd[1]: Starting GPS (Global Positioning >> System) Daemon... >> Mar 09 18:47:31 beaglebone systemd[1]: gpsd.service: Current command >> vanished from the unit file, execution of the command list won't be resumed. >> Mar 09 18:48:39 beaglebone systemd[1]: gpsd.service: Start operation >> timed out. Terminating. >> Mar 09 18:48:39 beaglebone systemd[1]: gpsd.service: Failed with result >> 'timeout'. >> Mar 09 18:48:39 beaglebone systemd[1]: Failed to start GPS (Global >> Positioning System) Daemon. >> >> Running cgps is giving normal output but when I start chrony it is >> updating only PPS. >> >> Could you please help me with that? >> >> >> >> środa, 17 października 2018 o 13:50:47 UTC+2 [email protected] >> napisał(a): >> >>> Hi, >>> I have gps with pps and signal level is measured in scope and is ok. The >>> problem is that when ppstest command is run the pps output is displayed as >>> ok but after arround 180 to 230 seconds i get error connection timed out >>> error. I have gpsd amd chrony installed. >>> Strangely when i restart gpsd then ppstest gives correct output but then >>> it shows connection timed out error again. >> >> -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/c433d052-4ad8-4f40-ac73-ed740fb70ab7n%40googlegroups.com.
