NTP GPS
-
New to this. Have unit attached via serial. How do I know the GPS receiver is working?
Jun 14 11:30:56 ntpd 19597 ntpd exiting on signal 15 (Terminated)
Jun 14 11:30:56 ntpd 19597 PPS(0) 8012 82 demobilize assoc 52311
Jun 14 11:30:56 ntpd 19597 127.127.22.0 local addr 127.0.0.1 -> <null>Jun 14 11:30:56 ntpd 19597 GPS_NMEA(0) 8012 82 demobilize assoc 52312
Jun 14 11:30:56 ntpd 19597 127.127.20.0 local addr 127.0.0.1 -> <null>Jun 14 11:30:56 ntpd 19597 216.229.0.49 9612 82 demobilize assoc 52313
Jun 14 11:30:56 ntpd 19597 216.229.0.49 local addr 10.20.30.158 -> <null>Jun 14 11:30:56 ntpd 74734 ntpd 4.2.8p10@1.3728-o Wed May 3 18:47:55 UTC 2017 (1): Starting
Jun 14 11:30:56 ntpd 74734 Command line: /usr/local/sbin/ntpd -g -c /var/etc/ntpd.conf -p /var/run/ntpd.pid
Jun 14 11:30:56 ntpd 74811 proto: precision = 0.296 usec (-22)
Jun 14 11:30:56 ntpd 74811 Listen and drop on 0 v6wildcard [::]:123
Jun 14 11:30:56 ntpd 74811 Listen and drop on 1 v4wildcard 0.0.0.0:123
Jun 14 11:30:56 ntpd 74811 Listen normally on 2 igb0 [fe80::20d:b9ff:fe44:6f24%1]:123
Jun 14 11:30:56 ntpd 74811 Listen normally on 3 igb0 10.20.30.158:123
Jun 14 11:30:56 ntpd 74811 Listen normally on 4 igb1 192.168.1.1:123
Jun 14 11:30:56 ntpd 74811 Listen normally on 5 igb1 [fe80::1:1%2]:123
Jun 14 11:30:56 ntpd 74811 Listen normally on 6 lo0 127.0.0.1:123
Jun 14 11:30:56 ntpd 74811 Listen normally on 7 lo0 [::1]:123
Jun 14 11:30:56 ntpd 74811 Listen normally on 8 lo0 [fe80::1%7]:123
Jun 14 11:30:56 ntpd 74811 Listen normally on 9 ppp0 22.112.206.78:123
Jun 14 11:30:56 ntpd 74811 Listen normally on 10 ppp0 [fe80::20d:b9ff:fe44:6f24%8]:123
Jun 14 11:30:56 ntpd 74811 Listening on routing socket on fd #31 for interface updates
Jun 14 11:30:56 ntpd 74811 PPS(0) 8011 81 mobilize assoc 31745
Jun 14 11:30:56 ntpd 74811 GPS_NMEA(0) serial /dev/gps0 open at 9600 bps
Jun 14 11:30:56 ntpd 74811 GPS_NMEA(0) 8011 81 mobilize assoc 31746
Jun 14 11:30:56 ntpd 74811 69.10.161.7 8011 81 mobilize assoc 31747
Jun 14 11:30:58 ntpd 74811 GPS_NMEA(0) 801b 8b clock_event clk_no_reply
Jun 14 11:30:58 ntpd 74811 69.10.161.7 8014 84 reachable
Jun 14 11:31:04 ntpd 74811 69.10.161.7 901a 8a sys_peer
Jun 14 11:31:13 ntpd 74811 PPS(0) 801b 8b clock_event clk_no_replyPicture with GPS not active is on cuau1 9600
Picture with active gps in on cuau0 9600
</null></null></null>
-
System Logs
Jun 14 11:41:15 php-fpm 19467 /services_ntpd_pps.php: The command 'cat /tmp/gps.init > /dev/cuau0' returned exit code '2', the output was ''
Jun 14 11:41:15 php-fpm 19467 /services_ntpd_pps.php: NTPD is starting up.
Jun 14 11:41:40 php-fpm 26958 /status_services.php: The command 'cat /tmp/gps.init > /dev/cuau0' returned exit code '2', the output was ''
Jun 14 11:41:40 php-fpm 26958 /status_services.php: NTPD is starting up.
Jun 14 11:41:42 php-fpm 29803 /status_services.php: The command 'cat /tmp/gps.init > /dev/cuau0' returned exit code '2', the output was ''
Jun 14 11:41:42 php-fpm 29803 /status_services.php: NTPD is starting up.
Jun 14 11:41:49 php-fpm 45417 /status_services.php: The command 'cat /tmp/gps.init > /dev/cuau0' returned exit code '2', the output was ''
Jun 14 11:41:49 php-fpm 45417 /status_services.php: NTPD is starting up.
Jun 14 11:41:53 php-fpm 59786 /status_services.php: The command 'cat /tmp/gps.init > /dev/cuau0' returned exit code '2', the output was ''
Jun 14 11:41:53 php-fpm 59786 /status_services.php: NTPD is starting up.
Jun 14 11:41:57 php-fpm 63784 /status_services.php: The command 'cat /tmp/gps.init > /dev/cuau0' returned exit code '2', the output was ''
Jun 14 11:41:57 php-fpm 63784 /status_services.php: NTPD is starting up.
Jun 14 11:42:50 php-fpm 76627 /status_services.php: The command 'cat /tmp/gps.init > /dev/cuau0' returned exit code '2', the output was ''
Jun 14 11:42:50 php-fpm 76627 /status_services.php: NTPD is starting up.NTP Logs
Jun 14 11:41:57 ntpd 63605 ntpd exiting on signal 15 (Terminated)
Jun 14 11:41:57 ntpd 63605 74.117.214.3 9012 82 demobilize assoc 48195
Jun 14 11:41:57 ntpd 63605 74.117.214.3 local addr 10.20.30.158 -> <null>Jun 14 11:41:57 ntpd 66960 ntpd 4.2.8p10@1.3728-o Wed May 3 18:47:55 UTC 2017 (1): Starting
Jun 14 11:41:57 ntpd 66960 Command line: /usr/local/sbin/ntpd -g -c /var/etc/ntpd.conf -p /var/run/ntpd.pid
Jun 14 11:41:57 ntpd 67253 proto: precision = 0.299 usec (-22)
Jun 14 11:41:57 ntpd 67253 Listen and drop on 0 v6wildcard [::]:123
Jun 14 11:41:57 ntpd 67253 Listen and drop on 1 v4wildcard 0.0.0.0:123
Jun 14 11:41:57 ntpd 67253 Listen normally on 2 igb0 [fe80::20d:b9ff:fe44:6f24%1]:123
Jun 14 11:41:57 ntpd 67253 Listen normally on 3 igb0 10.20.30.158:123
Jun 14 11:41:57 ntpd 67253 Listen normally on 4 igb1 192.168.1.1:123
Jun 14 11:41:57 ntpd 67253 Listen normally on 5 igb1 [fe80::1:1%2]:123
Jun 14 11:41:57 ntpd 67253 Listen normally on 6 lo0 127.0.0.1:123
Jun 14 11:41:57 ntpd 67253 Listen normally on 7 lo0 [::1]:123
Jun 14 11:41:57 ntpd 67253 Listen normally on 8 lo0 [fe80::1%7]:123
Jun 14 11:41:57 ntpd 67253 Listen normally on 9 ppp0 22.112.206.78:123
Jun 14 11:41:57 ntpd 67253 Listen normally on 10 ppp0 [fe80::20d:b9ff:fe44:6f24%8]:123
Jun 14 11:41:57 ntpd 67253 Listening on routing socket on fd #31 for interface updates
Jun 14 11:41:57 ntpd 67253 refclock_atom: /dev/pps0: Device busy
Jun 14 11:41:57 ntpd 67253 127.127.22.0 local addr 127.0.0.1 -> <null>Jun 14 11:41:57 ntpd 67253 refclock_open /dev/gps0: Device busy
Jun 14 11:41:57 ntpd 67253 127.127.20.0 local addr 127.0.0.1 -> <null>Jun 14 11:41:57 ntpd 67253 74.117.214.3 8011 81 mobilize assoc 55501
Jun 14 11:42:00 ntpd 67253 74.117.214.3 8014 84 reachable
Jun 14 11:42:06 ntpd 67253 74.117.214.3 901a 8a sys_peer
Jun 14 11:42:50 ntpd 67253 ntpd exiting on signal 15 (Terminated)
Jun 14 11:42:50 ntpd 67253 74.117.214.3 9612 82 demobilize assoc 55501
Jun 14 11:42:50 ntpd 67253 74.117.214.3 local addr 10.20.30.158 -> <null>Jun 14 11:42:50 ntpd 6841 ntpd 4.2.8p10@1.3728-o Wed May 3 18:47:55 UTC 2017 (1): Starting
Jun 14 11:42:50 ntpd 6841 Command line: /usr/local/sbin/ntpd -g -c /var/etc/ntpd.conf -p /var/run/ntpd.pid
Jun 14 11:42:50 ntpd 6928 proto: precision = 0.300 usec (-22)
Jun 14 11:42:50 ntpd 6928 Listen and drop on 0 v6wildcard [::]:123
Jun 14 11:42:50 ntpd 6928 Listen and drop on 1 v4wildcard 0.0.0.0:123
Jun 14 11:42:50 ntpd 6928 Listen normally on 2 igb0 [fe80::20d:b9ff:fe44:6f24%1]:123
Jun 14 11:42:50 ntpd 6928 Listen normally on 3 igb0 10.20.30.158:123
Jun 14 11:42:50 ntpd 6928 Listen normally on 4 igb1 192.168.1.1:123
Jun 14 11:42:50 ntpd 6928 Listen normally on 5 igb1 [fe80::1:1%2]:123
Jun 14 11:42:50 ntpd 6928 Listen normally on 6 lo0 127.0.0.1:123
Jun 14 11:42:50 ntpd 6928 Listen normally on 7 lo0 [::1]:123
Jun 14 11:42:50 ntpd 6928 Listen normally on 8 lo0 [fe80::1%7]:123
Jun 14 11:42:50 ntpd 6928 Listen normally on 9 ppp0 22.112.206.78:123
Jun 14 11:42:50 ntpd 6928 Listen normally on 10 ppp0 [fe80::20d:b9ff:fe44:6f24%8]:123
Jun 14 11:42:50 ntpd 6928 Listening on routing socket on fd #31 for interface updates
Jun 14 11:42:50 ntpd 6928 refclock_atom: /dev/pps0: Device busy
Jun 14 11:42:50 ntpd 6928 127.127.22.0 local addr 127.0.0.1 -> <null>Jun 14 11:42:50 ntpd 6928 refclock_open /dev/gps0: Device busy
Jun 14 11:42:50 ntpd 6928 127.127.20.0 local addr 127.0.0.1 -> <null>Jun 14 11:42:50 ntpd 6928 74.117.214.3 8011 81 mobilize assoc 35600
Jun 14 11:42:53 ntpd 6928 74.117.214.3 8014 84 reachable
Jun 14 11:42:59 ntpd 6928 74.117.214.3 901a 8a sys_peer</null></null></null></null></null></null> -
Now new results. Very inconsistent!
-
Looks bad. Disabled LTE and ethernet and no results.
-
What gps are you using - doesn't look like your getting any pps signal even.
-
bought off aliexpress serial unit using ublox chip.
https://www.aliexpress.com/item/Industrial-control-applications-RS232-protocol-output-UBLOX-6010-GPS-chip-design-DB9-connector-STOTON-GPS-receiver/32747390533.html?spm=2114.13010608.0.0.D1Jb8r
I am using a pcengines APU2 and using the single com port. in pfsense under advanced it has the com port set to 115200. do I need to change that? Am I not able to use the same port for managing the pfsense? Do I need to make a change so I can use the single come port on the APU2?
-
I am using a pcengines APU2 and using the single com port.
APU2s have more than one COM-Port, they are just not extended to the outside.
See schematics page 12: http://pcengines.ch/schema/apu2c.pdfBetter use Com1 (the externally available) for serial console and the internal pin-header for your GPS receiver.
-
I am using a pcengines APU2 and using the single com port.
APU2s have more than one COM-Port, they are just not extended to the outside.
See schematics page 12: http://pcengines.ch/schema/apu2c.pdfBetter use Com1 (the externally available) for serial console and the internal pin-header for your GPS receiver.
Thanks for the quick response. Since I do not want to have to begin cutting holes in case I think it is better I use the MC7700 GPS connection instead. I will still check this out just don't know how to get it connected!
-
Possibly if I use this. not sure if I can punch the front panel though. Wish they had a case for 2 COM ports.
http://www.greenlee.com/products/PUNCH-UNIT%2540dCONNECTOR-9-PIN-(229).html?product_id=15349
-
How many units do you want to build? A punch out tool only makes sense for dozens of devices to modify.
Just drill a hole and use a regular, round 3-conductor cable for your serial port. All you need is Gnd, TX & RX anyway. 1m of regular microphone cable from your local music store will do (AES cable does slightly better) and is durable and solid. If you don't use the antenna holes then you wouldn't even have to drill.
Even a 3,5mm headphone jack would do, btw. Then you wouldn't have a cable dangeling out of your case… -
Ok going to do some research. Thanks!
-
https://www.aliexpress.com/item/Nice-cheap-car-DVR-track-record-with-the-recorder-with-GPS-antenna-module-receiver-3-5/32625133402.html?spm=2114.10010108.100009.4.YjBy1j&traffic_analysisId=recommend_2037_null_null_null&scm=1007.13482.37805.0&pvid=f6a81637-dd5a-4773-af80-26306710e773&tpp=1
like this…..
-
How many units do you want to build? A punch out tool only makes sense for dozens of devices to modify.
Just drill a hole and use a regular, round 3-conductor cable for your serial port. All you need is Gnd, TX & RX anyway. 1m of regular microphone cable from your local music store will do (AES cable does slightly better) and is durable and solid. If you don't use the antenna holes then you wouldn't even have to drill.
Even a 3,5mm headphone jack would do, btw. Then you wouldn't have a cable dangeling out of your case…What about voltage? Unit requires 3 volts for antenna
-
The receiver you linked requires 3.3V to 5V DC, which is easily available within an APU.
Which APU configuration do you actually use, btw?In the board's picture you see the white 12 o'clock pin header which is Com2.
The white 2-pin header at 10 o'clock position most likely is 5V power but I can't read it from the picture.
Next to that is a USB header which has 5V for sure.Since you're only "listening" to your GPS receiver all you need on the APU side is +5V, RX and GND.
-
So I tried connecting to my MC7700 Wireless which has GPS. I set autostart on the unit and I am unable to get any other the ports to work. NMEA COM7 worked on my PC and spit out lots of data so I would think the pfsense could see this also.
Do I need to restart after selecting a different com port on the NTP GPS settings?
-
Got this fixed. Now just cannot seem to get GPS data for NTP to work. Also not sure what GPS is used in the sierra wireless. I tried the following interfaces…
Not sure if I have to wait or restart NTP after evey try?
-
That's out of my scope, sorry.
-
So I reached out to pcengines and they are telling me even that port will not work (COM2).
pcengines:
The DB9 connector of the serial port does not have any power pins. It's a regular RS232.
COM2 is on the 5 pin header J3. The part number of the 5 pin header is 640456-5, see https://www.digikey.ch/product-detail/de/te-connectivity-amp-connectors/640456-5/A19471-ND/259011 and it's mating counter parts.Me:
So Com 2 has power pin? Pin 5 5V and pin 1 3v?
pcengines:
Correct, J3 has 5V and 3.3V. Please be aware the RX/TX expect TTL level signals, not +/-12V RS232 signal levels.
Me:
I am looking at this for a serial connected GPS unit which requires 3v or 5v
https://www.aliexpress.com/item/Industrial-control-applications-RS232-protocol-output-UBLOX-6010-GPS-chip-design-DB9-connector-STOTON-GPS-receiver/32747390533.html
Will this work with that?
pcengines:
No, this will not work. It will not work on the DB9 connector COM1, because pin 9 has no power and it will not work on COM2, because the signal levels do not correspond.
I guess you want GPS for for getting position data? Other need the GPS signal for the exact timing signal it provides, but that is not possible with the module you suggested.
For positioning I would try one or more of these modules:
https://www.aliexpress.com/item/Free-Shipping-USB-GPS-Receiver-Ublox-7020-gps-chip-GPS-Antenna-G-Mouse-replace-globalsat-BU/32816622596.html
https://www.aliexpress.com/item/GPS-receiver-USB-driver-ublox-G7020-waterproof-built-in-FLASH-BT-708-replace-globalsat-BU-353S4/32818403478.html
https://www.aliexpress.com/item/NEW-UB-702-GPS-receiver-USB-module-antenna-ublox7020-CHIP-magnetic-waterproof-replace-globalsat-BU-353S4/32815397287.html
Me:
I need GPS for NTP Timing. I don't need milisecond accuracy though. What do you mean by signal levels do not correspond? Thanks! I am also using pfsense on the board.
pcengines:
The voltage of RS232 signals is +/-12V. The voltage of TTL signals is 0V/3V. COM1 is RS232 and has +/-12V levels, COM2 has 0V/3V levels.
Is is capable of any baud rate up to 1M.
For NTP you need a different module. -
That's easy. Take a max232 and convert the levels.
But I don't know how good you are at soldering. Would be a 10min task for me…PS: I don't know if those USB receivers are supported in FreeBSD. Next problem.
-
Last time I soldered something was….never ;D Maybe time to learn!
