-
Notifications
You must be signed in to change notification settings - Fork 16
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
NTP over wifi #2
Comments
Dear ra1nb0w, Thank you for your attention to the project! You've proposed an interesting direction of further development. Definitely, such way of time sync is good for WSPR sending schedule, but I'm afraid it is unsuitable for carrier frequency correction, which require more precise source such as PPS leg of GPS receiver. You might know that since release 1.0 the project covers frequency range up to ~32 MHz. Tests have shown that the frequency drift is often too large on these frequencies when running standalone, without GPS receiver, especially during the board heating up. Nevertheless, your proposal definitely deserves attention. I'll look at Pico W NTP solutions available here. Cheers, |
Hello and thanks for this great project. I had a question, I wanted to know if it is possible to use AC sinewave signal instead of GPS? thanks. |
Hi ErfanDL, Thank you for your question about the project. It is possible for majority of such external oscillator (TCXO) types. Fortunately I possess a number of obsolete TXO4080 TCXO's (Rakon, 10 MHz). I'll try to devise a frequency locked loop based on this TCXO signal, that's quite simple. However some schematic will be required to match TCXO output to Pico's GPIO input (I suppose two resistors will be sufficient). TCXO will be an additional option, the good one is often more valuable than GPS receiver. Cheers, |
Hi Roman, thanks for this neat work, I built and tried it, very nice. |
Hi Thomas, Thank you for the positive feedback. As you surmise, the USB interface is alive, but today is only for debugging purposes ( debug/logutils.c ). As an accurate (+-1 sec) time is essential for holding WSPR tx window properly, GPS UTC time stamp is used in today version. However, if we supersede GPS to TCXO, the user will have to set the time manually using minicom terminal and Pico USB interface for example. So, your idea definitely looks sound. Regards, |
thanks for reply. I had another question, is it possible to activate the output pin every 12 seconds for 100 milliseconds? |
Hi ErfanDL, It is possible, you can do that easily. Please read RP2040's https://datasheets.raspberrypi.com/rp2040/rp2040-datasheet.pdf , paragraph Regards, |
Will be very nice to use the TCXO as clock and the Wifi/NTP for the timing. Very compact solution for WSPR |
NTP as an alternative is an option, but i asume in that case you need to add the ntpd in the code to get the system in an optimal shape for correcting time drift. NTP as protocol seems to be suitable. In the past the servers i managed made use of the TIME beacon at the long wave if i remember richt, and later, when internet was no longer dial up based we started to step over to NTP. Using NTP could solve issues when you have not a clear skyview, some gps modules could become instable at in house situations. How does NTP handle time drift? |
I have added NTP + FT8 support @ https://github.com/kholia/Pico-FT8-TX/tree/free-beacon-ntp-pico-w. My drift correction technique -> Just reboot the Pico W using a cheap smart switch every day on a schedule. |
Thank you very much! Why not re-synching the clock from time to time? o rebooting the board with a timer/watchdog? |
Sure - that can be done too. Good ideas! I like the reboot-using-watchdog idea as that keeps the code simple. I also recommend checking out https://github.com/kholia/HF-PA-v10/tree/master - it is quite rugged and awesome :D In case the beacon system is deployed remotely, I recommend keeping it attached to a WiFi smart switch for "emergency remote power control". |
Thanks for sharing, I will check the PA. |
Hi,
first, thanks for this great work!
I have a pico with wifi and can be great to have a fully standalone version without any additional GPS module/antenna. Is it feasible?
The text was updated successfully, but these errors were encountered: