Keyboard Shortcuts
Likes
Search
review of THOR speeds on HF SSB
开云体育
Here are the RF spectra of the?? THOR?? speeds from?? 11 ? to ? 56? sent today on 3585 kHz usb-data mode Rec'd on a SDR (RSP play) and SDR Spectrum Analyzer.
The new THOR 25? (alpha) mode seems to be working well (still in alpha stage) Now wish it appears soon on FLMSG optional
modes.
I see all of the THOR speeds now have a longer "tail" at the end of each transmission (a few seconds) and the tones are "shaped" as described in the READ ME files written on the W1HKJ.com/alpha I think this keeps the BW to a minimum? (like
shaping a CW signal).
On the PA NBEMS on Sunday mornings (0730 hr on 3583 kHz vfo) we typically use THOR 22 for checkins (about 500 Hz and 80 wpm) and then use?? MFSK 32?? and? THOR 32? for traffic with FLMSG or FLAMP. These are a bit faster and wider but seem to
work well for 1-3 kB files.
Prop was excellent today on 80m from all over the Mid-Atlantic area. QRP? stations were easily copied by me as net
control, well above my noise level. Here are the spectra of each THOR speed? - ? I show the peak BW and the BW at? 30dB? below the peak.
Not sure the current definition of "bandwidth"
but I think it is the width of the signal at -26 dB
below peak. We do find that?? THOR 11?? really cuts through the noise with longer duration tones, and is especially good as a checkin mode during RTTY contests. Thor 11 feels slow, but is still around 30 wpm.
de k3eui? Barry Philly Dec 22 2024
|
Hello Barry, Very nice THOR signals overview thanks a lot! The tone shaping is, as you have expressed, a means to keep the bandwidth ot a minimum. But it was requested for a quite specific reason: a sharp edge of the signal when starting a message does, based on experience, make the initial synchronization more difficult, leading to some lost characters at times. I assume this happens because the decoder does not get the intended single (idle) tone frequency as a first input, but an ambiguous mix of frequencies (which is of what such a transient 'step function' consists of). So it would be quite interesting to verify, while you run your nets, whether the initial text errors, whenever a station starts a message, have been reduced due to this short signal ramp. I had checked this effect and idea of a startup ramp when I had made off-air recordings of different MFSK signals that still had a sharp start and where the first bits of a message were not properly (or at least reliably) read. Adding a little ramp at the start (by editing the recorded audio) usually got FLdigi to decode the same message flawlessly from the beginning. So it's basically a recommendation to help facilitate initial synchronization. But of course, it only helps when transmitting stations actually use the latest FLdigi version (with the shaped signal startup and ending). Should you wish to try different options, you can adjust the length of the ramp from 0 ms (sharp = similar to previous FLdigi versions) up to 500 ms (very soft), with a default of 100, very well chosen by David. This user setting is at Menu - Config - Modem - General - 'Raised cosine startup shape' (it affects both signal startup and ending). If you make any on-air observations regarding this feature, please let us all know... Thanks and best regards Tobias .-.-. Am Sonntag, 22. Dezember 2024 um 15:26:55 MEZ hat K3EUI Barry via groups.io <k3euibarry@...> Folgendes geschrieben:
Here are the RF spectra of the?? THOR?? speeds from?? 11 ? to ? 56? sent today on 3585 kHz usb-data mode Rec'd on a SDR (RSP play) and SDR Spectrum Analyzer.
The new THOR 25? (alpha) mode seems to be working well (still in alpha stage) Now wish it appears soon on FLMSG optional modes.
I see all of the THOR speeds now have a longer "tail" at the end of each transmission (a few seconds) and the tones are "shaped" as described in the READ ME files written on the W1HKJ.com/alpha I think this keeps the BW to a minimum? (like shaping a CW signal).
On the PA NBEMS on Sunday mornings (0730 hr on 3583 kHz vfo) we typically use THOR 22 for checkins (about 500 Hz and 80 wpm) and then use?? MFSK 32?? and? THOR 32? for traffic with FLMSG or FLAMP. These are a bit faster and wider but seem to work well for 1-3 kB files.
Prop was excellent today on 80m from all over the Mid-Atlantic area. QRP? stations were easily copied by me as net control, well above my noise level. Here are the spectra of each THOR speed? - ? I show the peak BW and the BW at? 30dB? below the peak.
Not sure the current definition of "bandwidth" but I think it is the width of the signal at -26 dB below peak. We do find that?? THOR 11?? really cuts through the noise with longer duration tones, and is especially good as a checkin mode during RTTY contests. Thor 11 feels slow, but is still around 30 wpm.
de k3eui? Barry Philly Dec 22 2024
|