|
Hans Summers
Hi Eddie Many thanks for all your efforts in helping to collect evidence to track down this problem. I know it might be a little frustrating but thanks for persisting!
I suspect that there might be some arithmetic issue in my code which reduces the accuracy of the calculation when the frequency is high. More specifically, when the shift frequency becomes smaller relative to the baseline output frequency.
If you have time, I think that a very useful test might be a ramp from 0 to 5,5Hz shift (say), at 0.5Hz increments. A staircase, really. This would show very clearly any issues with inaccuracies of the steps, and clarify immediately on what bands and frequencies they started to become a problem.?
I am referring to the stuff in section 8 of the manual (page 28). A customised message to produce a staircase of shifts from 0 to 5.5 Hz, with 5 seconds spent on each stair. The staircase will take 1 minute. This will make it much easier to see what is going on than images of WSPR, which spends only a short time on each frequency so looks messy on the Argo (etc) display.
The required mode should be FSK/CW, and the Message string contains the speed and the shifts, with an asterix ' * ' character to start and end it. So it should be *050123456789AB* for the described ramp.
73 Hans G0UPL On Sat, May 18, 2013 at 11:33 PM, g3zjo <g3zjo@...> wrote:
|
