Open thomasabbott opened 7 months ago
Dear Thomas,
Sorry for the belated answer.
I will check this case. Meanwhile, the previous version (w/o console & old pio dco which was up to 9.4M) worked correctly on 7 MHz band, transmitting WSPR. Unfortunately, I had no opportunity to test the new version closely due to starting a Christmas rally.
Thank you for this report, it is useful.
Cheers, Roman R2BDY
Thanks for the v1.1 .uf2, I tried it today.
I have connected a GPS but see no frequency correction.
SETFREQ 10000000 Frequency (measured) stays at 10 000 014.3 (error of 1.4 ppm) Slightly sensitive to temperature and/or touching the crystal. Even with some careful averaging, against an accurate reference, I can't see any frequency change from turning the GPS on and off. Stated frequency is always:
so it looks like the GPS correction is not being applied to the pio dco.
GPS NMEA is connected to Pico board pin 2, RP2040 GPIO1 (UART0 Rx) GPS PPS is connected to Pico board pin 5, RP2040 GPIO3. Both seem to be working, so I don't think it's related to this.
Could this come from a ppb / ppt mixup. STATUS reports
GPS frequency correction 1446430 ppb
is the correct figure, but in parts per trillion not billion.No, I think it's all correct except for the labelling of "ppb" in many places. piodco.c returns the correct 14465 mHz correction.
Perhaps this is not being applied correctly?
Some STATUS messages for reference: