开云体育

Hi All, I use the Fldigi log when I'm net control. I have several duplicates of calls. I was wondering if there's an easy way to edit the .adi file that Fldigi creates so I can delete the duplicates and maybe change information or add information. If I use a text editor it just too hard to edit. 73, Ron NY3J

The ALPHA FLDIGI (4.2.06.19) as of Jan 05 2025 The THOR alpha (test) modes now have the OPTION to include "signal shaping" from 0-8 milliseconds. This is the rise/fall time of each tone change. It should operate in a similar way that the CW carrier shaping limits the CW bandwidth and reduces "key clicks" (older rigs). Can we "see" or hear the changes when THOR signal shaping is turned ON or OFF? Here is THOR TX tone rise/fall times signal shaping set to a 0 ms rise time (no signal shaping at all) in the Fldigi MENU Here are the OSCILLOSCOPE trace (on Fldigi WF) and the RF Spectra captured when I was sending a THOR25 signal without signal shaping. I can't hear the difference (in headphones) but the RF Spectra trace does show a cleaner skirt on the RF signal. The OSCILLOSCOPE trace has obvious differences in the tone change amplitudes. No signal shaping Oscilloscope Trace of THOR25 (signal amplitude vs. time) THOR 25 RF Spectra reveals an 800 Hz BW at -30 dB below the peaks. Now with an 8 millisecond signal shaping turned ON (TX tone rise time (milliseconds) Note: using THOR 25 (25 tones/second) EACH tone DURATION is 1/25 or 40 milliseconds. Oscilloscope Trace: each tone is about 40 milliseconds with an 8 ms rise/fall time The RF bandwidth of THOR 25 is reduced by about 100 Hz (@ -30dB down) from 800 Hz to 700 Hz due to the tone "shaping"

THOR 32 on HF SSB I was on the NY NBEMS net today (Jan 04 at 8 AM EST) on 3583.0 kHz (vfo) and caught the oscilloscope view (signal vs. time) on FLDIGI when an op was sending traffic with THOR 32 mode. Note the signal is not a constant amplitude, at least not as received by me near Philly. THOR32 (32 baud or 32 tones/second) results in a signal duration of 1/32 or 0.03125 seconds (31 milliseconds). A "tone shaping" (0 to 8 millisec) now available as an option in the "alpha" (test) Fldigi 4.2.06.16 will alter the rise/fall times of each tone. Here is the AUDIO spectrum of THOR32 as copied at k3eui on 3583.0 kHz Note the BW is about 600 Hz. Scale: 200 Hz per vertical bar THOR32 usually works well for traffic on 80m and 40m SSB - much easier to tune in properly than MFSK32 18 tones, sent one at a time

http://www.w1hkj.com/alpha/fldigi/ fldigi-4.2.06.18.dmg fldigi-4.2.06.18.tar.gz fldigi-4.2.06.18_setup.exe fldigi-dark-scheme.png readme.dmg.txt readme.txt Added configurable tone shaping. This is specifc to THOR. 0 msec risetime 4 msec risetime 4 msec leading/trailing edge is similar to a CW signal. David

http://www.w1hkj.com/alpha/fldigi/ fldigi-4.2.06.17.dmg fldigi-4.2.06.17.tar.gz fldigi-4.2.06.17_setup.exe Change to THOR-25 modem, increasing interleave depth to 1 second. NOT compatible with previous test releases. This change should improve the decoder under NVIS conditions, such as Mid-Latitue disturbed: THOR-25 * add new THOR modem with following characteristics . symlen = 320 . samplerate = 8000 . flushlength = 20 . bandwidth = 460 . interleave depth = 25, 1 second . IEEE coefficients for viterbi encode/decode algorithms THOR_K15 15 K15_POLY1 044735 K15_POLY2 063057 . objective to provide highest baud within 500 Hertz bandwidth for European amateurs .CPS test text: "0123456789 abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ" number chars: 66 overhead: 6.480000 sec xmt time: 10.280000 sec xmt samples: 134080 chars/sec: 6.42 * assigned secondary RsID code 691 to THOR-25 * increased flush length for all THOR baud rates * added configurable start and end of signal shaping to these modem types: . dominoEX . psk . mfsk . rtty . thor . selectable on configuration tab Modem/General * restored selectable paths to all THOR modem types Bench tests with the above test parameters produced 100% decode. 73, David W1HKJ

Here are the RF Spectra of THOR22 (sent on 40m SSB) when sent with 0 (milliseconds) signal shaping and 500 (millisec) signal shaping. The shaping value is now in the FLDIGI MENU under MODEM: GENERAL and can be set manually from 0 to 500 value. Shaping the signal amplitude tones in the FSK modes like THOR, MFSK, AFSK RTTY should tend to "soften" them - resulting in a smaller bandwidth (like shaping a CW carrier) On CW the shaping in milliseconds is typically 4-8 ms (turning the carrier on/off) which results in a narrow bandwidth CW signal. No shaping of a CW signal results in key clicks and a wide splatter type signal. I'm not sure what the units are in FLDIGI for tone "shaping" but it also looks like milliseconds. RF spectra captured with an SDR (RSP play) and RSP Spectrum Software de k3eui No Signal Shaping 500 ms Signal Shaping

Now the THOR modes (and all of the FSK modes) have "signal shaping" (set in CONFIG MENU: MODEM: GENERAL) I think this slowly builds up the amplitude of each tone, and slowly diminishes each tone, much like CW "shaping" of the amplitude of a CW carrier. My guess is that this might soften the tone changes (maybe how it sounds less abrupt) and result in a somewhat smaller bandwidth (just like in CW). This has obvious implications on HF SSB, rather than on FM bands. Here are some AUDIO SPECTRA captured using the FLDIGI audio spectrum option. Next I will try to capture the RF Spectra using a SDR and Spectrum Analyzer software. I sent a THOR22 signal (80m SSB) with signal shaping of 0 and again, signal shaping 500 (milliseconds). I don't really see much change, nor do I hear any change. So it must be very subtle. de k3eui ===================

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

Dave, Here is a curiosity question: I am running the current alpha code (4.2.06.15) now, but have seen this multiple line blurring effect going back a ways in previous versions. If I run fldigi on this Win 11 or my old Win 10 i7 boxen for a while, The display goes like: and the copy become erratic. If I close fldigi and immediately restart the display goes back to normal and copy is nominal: This appears to happen in all digital modes I commonly use (most often Thor, Olivia, FSQ - but also others). It also impacts all visible signals on the waterfall together. I notice it on the 7300 because it is my primary "digital" radio, but also have seen it on the 705 and 7610. At first I thought it was a propagation artifact, until I restarted the program and immediately the blurring was gone. Restarting the program always clears things up. Any clues what this might be? Something with the fourier algorithm associated with WF and decode? I am sure my cat did not walk on the keyboard... :) Note, those two birdies seem to be generated away from the QTH - they are periodic and don't bother me when there. They were convenient to show what happens to all signals. -- Jack Spitznagel KD4IZ FM19oo Pakton, MD

THOR 25 TEST RESULTS A test of the new mode THOR25 was achieved on the PANBEMS net (Sunday 0730 hr EST on 3583 kHz VFO) The new alpha version of Fldigi: 4.2.06.15 did work with TxID/RxID and THOR25 codes. Copy with THOR25 was excellent and prop on 80m at 0800 hr was very stable with strong signals from PA/NJ/NY/ and New England Here is the AUDIO spectrum of THOR25 on 3583 kHz (vfo) caught on my HF SSB receiver and sound card (Icom 7610)

THOR25 is a new (alpha) mode in FLDIGI THOR I am using version: 4.2.06.15 Here is an AUDIO SPECTRUM of THOR25 as I was sending a FLMSG on 80m NBEMS net. Note the sharp sides down to a BW of about 800 Hz @ 30dB below the peak Hope to try this new speed on the 80m and 40m NBEMS nets in the Pa region: PaNBEMS: Sunday 0730 hr EST on 3583.0 kHz (vfo) Mid-Atlantic NBEMS: Sunday 1000 hr EST on 7068.0 kHz (vfo) de k3eui Barry Philly =============================