Hi ... I checked a SB16 ISA card running JVComm32 against 1pps from WWV and a OEM Furuno GPS and, in both cases, when applying correction, software told a value = 11024,80450540374 . A long number b
Is it a coincidence I wonder, that the 'standard' Soundcard / CD sampling rate is a multiple of the squares of the small prime numbers. ie: 44100 = 2 * 2 * 3 * 3 * 5 * 5 * 7 * 7 Spooky ! [snip] Hmm,
Hello Alberto, hello group, Concering the accuracy of the soundcard's crystal referency: There has been a discussion about this before, and I do not want to trigger that again. Here are the results
[snip] I did try and store jpegs through the night but, although I entered a value of 3600 seconds, nothing was stored until I pressed "Capture" manually. [snip] I forgot to comment on this. Dave, a
[snip] By the way... Thanks Alberto for a really easy QRSS viewing program! Argo has worked no trouble on every PC i've tried. More than can be said for some of the others.... [snip] Dave, thanks. I
Alberto - How easy would it be to include a facility for storing the exact measured sampling rate in a .INI file that can be called up when the software is run. [snip] Shouldn't be too difficult. Ma
[snip] Could have been longer but Argo crashed soon after, probably because of the way it fills up the hard disk with photos taken every 1 minute, despite the fact that at the dot width of 30sec, it
[snip] Since 3s/dot slow CW has not been good enough for this so far, I suggest we do something like this: As many European stations as possible transmit very long dashes (90seconds for example), wi
[snip] But that is maybe a useful thought , you could set the default dependent upon the mode setting, as that defines the screen width. A value slightly less than a screen width would allow accurat
I had too much haste in uploading build 117 of Argo. It contains a couple of errors : the first shows when you set the 30s dots mode, and the 120s dots mode scale is displayed instead. The second err
Today I had planned to go out with my family, but something went wrong and suddenly I found myself with some hours to spend. Then I decided to implement a suggestion by Larry, VA3LK, who had asked fo
[snip] I am however finding some problems with the autosave on Argo. (Sorry Alberto, would normally have sent this direct but I havent resurrected my address-book yet.) I find the timed capture is c
Hi Alberto, VE1ZZ was on 136.5, so you must have seen MM0ALM, and as Dave YXM has told me, MM0ALM was close to 136. It seems he was 40Hz higher than OK1FIG, which would put him on 135.995. 73, John,
Mike, G3XDV On which freq. was Jack sending MM0ALM ? With my very poor antenna, I received several times 'MM0ALM', just about 40 Hz above the strong OK1FIG signal, but I thought it was MM0ALM calling
[snip] Speculatively of course, this would be at a frequency in the 60 - 170Hz region - which makes even amateur 9kHz experiments seem tame. It is stated that in the US there are lines looking like
Mike, thanks for your nice words. What you call 'frequency error', and which I would call 'frequency uncertainty', is caused by the relative values of the sampling rate and the FFT size. In the full
[snip] Anyway, direct zero IF conversion will still need extensive input filtering for anti-alliassing and in this case will be even more stringent unless an artificially high sampling rate is emplo
[snip] IF filtering will be a 300Hz bandwidth mechanical filter at 455kHz. Very extensive front end filtering is needed to remove the image response which sits in the MF broadcast band at 910 - 1070
