Sorry about the typos above. I guess you can 'decode' my sloppy typing.
Looking back over the posts, I see that you say the frequency has changed. This leads me to bet that this has affected the fsk width. I find them intimately connected. Move the frequency and the fsk width changes, especially if fitted with a gps I think - at least I never saw it in the days before my gps was fitted.
Look on Argo and my bet is your fsk is a wiggly line. If so, just experiment with the values of fsk.adj to get the optimum as described in section 9 of the kit instructions. Mine is very sensitive to that value and changes in the base frequency.
73s
toggle quoted message
Show quoted text
--- In
[email protected], "g4sfs" <g4sfs@...> wrote:
Hi All
First can I just thank Steve and Hans for the kits and all the work they have done. Experimenting with QRSS and WSPR with their various kits has got me back into construction etc after a long break - it's almost addictive!!
I have been running the ultimate QRSS kit on 30m WSPR with the v1.0 chip and all was fine except for the known problems. I upgraded to v1.04 last Sunday and everything worked really well until the early hours of yesterday (Saturday) morning when I realised that my own monitored signals were not being decoded and I was not getting any reports. This continued throughout yesterday and I have been unable to resolve the problem. I have checked all the settings and confirmed that the tx is transmitting and I have even adjusted some of the settings but still no decodes and no reports! If I ask the tx to send a cw ident it does that just fine but still no WSPR decodes. I have also reset the frequency as that had changed but still nothing! I'm now wondering if I have somehow managed to corrupt the microcontroller.
Any thoughts or suggestions etc much appreciated as I've run out of ideas!
By the way, I had to change C5 to 10pf to get the osc to tune the right part of the band.
73 de Peter
G4SFS
