Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WSPR Transceiver: verify correct operation of GPS interface #1019

Closed
dc1rdb opened this issue Oct 5, 2021 · 7 comments
Closed

WSPR Transceiver: verify correct operation of GPS interface #1019

dc1rdb opened this issue Oct 5, 2021 · 7 comments
Labels

Comments

@dc1rdb
Copy link

dc1rdb commented Oct 5, 2021

Hi Pavel,
this is just a question rather than an issue:
Is there any way via console to verify that a GPS module (connected via DIO3_N and UART) is operating correctly for the time synchronization and for the automatic measurement and correction of the frequency deviation?

Thanks in advance!
73 de Robert

@pavel-demin
Copy link
Owner

Hi Robert,

With the connected GPS UART interface, the following command enables the GPS time synchronization:

service gpsd start

The time synchronization can be checked using one of the chrony commands. If the GPS module is used for the time synchronization, the following command should show some information about the GPS time source:

chronyc sources

The following commands could be used to check the frequency correction:

cat apps/sdr_transceiver_wspr/sdr_transceiver_wspr.bit > /dev/xdevcfg
apps/common_tools/measure-corr 30

The returned value is the frequency deviation in ppm.

Best regards,

Pavel

@dc1rdb
Copy link
Author

dc1rdb commented Oct 6, 2021

Thanks for the quick response, Pavel.
Here are my results:

rp-f08971:~# service gpsd start
 * Bringing up network interface lo ...
ip: RTNETLINK answers: File exists                                        [ ok ]
 * Starting gpsd ...                                                      [ ok ]

rp-f08971:~# chronyc sources
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
#? PPS                           0   4     0     -     +0ns[   +0ns] +/-    0ns
^+ time.cloudflare.com           3   9   377   251   -257us[ -263us] +/-   12ms
^- pmg.jonasled.de               2   8   377   129   +350us[ +338us] +/-   33ms
^* mail.klausen.dk               2   9   377    66   +216us[ +200us] +/-   12ms
^- gromit.nocabal.de             2   9   377   263   +272us[ +267us] +/-   29ms
^+ wpad.fritz.box                3   6   377    17   +178us[ +178us] +/-   26ms

rp-f08971:~# apps/common_tools/measure-corr 122.88 30
3.99

It does not seem that GPS is being used for time sync, does it?
Frequency correction seems to be working, however.
Is it possible to include the service gpsd start into the start.sh script?

Thx and best regards
Robert

@dc1rdb
Copy link
Author

dc1rdb commented Oct 23, 2021

Pavel, on my StemLab 122-16 I just looked at /dev/shm/update-corr.log and found error messages like:

Sat Oct 23 13:29:01 UTC 2021
Usage: measure-corr freq time
 freq - frequency expressed in MHz (122.88 or 125),
 time - measurement time expressed in seconds (from 1 to 30).

After adding 122.88 in /apps/common_tools/update-corr.sh everything is fine.

CORR=$DIR/measure-corr 122.88 30 || exit

73
Robert

@pavel-demin
Copy link
Owner

Thank you for finding this problem. I think it is now fixed with this commit.

@dc1rdb
Copy link
Author

dc1rdb commented Oct 29, 2021

Sure. Thanks for the quick fix :-)

@pavel-demin
Copy link
Owner

The fixed version of the frequency correction scripts is now in the new release.

@pavel-demin
Copy link
Owner

It does not seem that GPS is being used for time sync, does it?

The fixed version of the gpsd configuration is now in the new release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants