Keyboard Shortcuts
Likes
- Linuxham
- Messages
Search
fldigi 4.2.06.15 developmen t version availabe for testing
开云体育Posted atMost recent three changes to the program: commit
ad817413f9d517a88b9156d48cc28f3a0b53c92c commit
8aa6a3ea07596d0c61e57462c8ffe1bae939339b 73, David |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: FLrig Remotely Accessed Scanning Script
开云体育Hi Charles I have used flrig-shell and/or fldigi-shell for this. Am pretty sure they are on Dave's site. From (say) bash, something like flrig-shell -c "rig.set_vfoA 14074000" or fldigi-shell -c "rig.set_frequency 14074000" There are a heap of other commands that might find useful. (like
modem choice and audio centre in fldigi-shell) Just launch without
arguments and type help for a list. If you want to also have a
GUI/manual fldigi macro set for your QSY choices, it is also
possible to externally launch same with (say) fldigi-shell -c
"main.run_macro 46". Cheers Bob VK2YQA
On 12/12/24 02:42, Charles Hargrove
wrote:
I am trying to help out someone who is looking to use the JNOS bbs with |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bug or "Feature"? Re: fldigi 4.2.06.14 development test version posted at
开云体育Hi. Built without errors on LMDE 6 / Cinnamon on Intel based PC.? Runs well, but... Bug or "feature"?? The AFC button is permanently "greyed out" in all modes, but AFC is actually active (ON) all the time! This was not the case with 4.2.06 (release version) or the 4.2.06.07 alpha, though I see is also an issue with 4.2.06.09. So what changed between alphas '.07 and '.09 ? It is especially problematic when Fldigi is left monitoring
unattended in MFSK32 for such things as the weekly SW Radiogram
broadcast, as it wanders off frequency when noise, or other non
digital audio, voice or music, opens the digital squelch.? (That
does have a hair trigger it seems...) OK, so if full bw RxID is enabled, it comes back when that is
seen, but it can also wander off frequency during active reception
of MFSK images!? Resulting in lost or mangled text or images etc
that follow.? (The image being received when it wanders,
is NOT affected!) As above, with 4.2.06 (Release) or 4.2.06.07 Alpha, this was not an issue, the AFC button was not "greyed out" and one could turn freely select the AFC ON/OFF setting as desired. Seasons Greetings etc. 73 Dave G0WBX.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
FLrig Remotely Accessed Scanning Script
I am trying to help out someone who is looking to use the JNOS bbs with
FLrig/FLdigi and have the HF radio scan groups of frequencies waiting for connections. The group of frequencies will change based on time of day for propagation changes. For example, 80 meters during evening or overnight and 40 meters during daylight. The FLdigi would be the modem and the FLrig would do all of the radio control functions. We can set up scripting with JNOS and have it communicate with FLrig/FLdigi via TCP/IP. Is this doable and where can I find the commands needed to make it happen to build out the script? Thanks. -- Charles J. Hargrove - N2NOV NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord. NYC-ARECS/RACES Nets 441.100/136.5 PL ARnewsline Broadcast Mon. @ 8:00PM NYC-ARECS Weekly Net Mon. @ 8:30PM NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32 "Information is the oxygen of the modern age. It seeps through the walls topped by barbed wire, it wafts across the electrified borders." - Ronald Reagan "The more corrupt the state, the more it legislates." - Tacitus "Molann an obair an fear" - Irish Saying (The work praises the man.) "No matter how big and powerful government gets, and the many services it provides, it can never take the place of volunteers." - Ronald Reagan |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: #wefax parsing filenames
#wefax
Have a look through the source code, for that level of detail. It is very informative. Here is a snippet of results from searching for the word "phasing" in CXX files:
?
./src/wefax/wefax.cxx:void fax_implementation::skip_phasing_to_image_save(const std::string & comment) ./src/wefax/wefax.cxx: ? ? ? ?/// Maybe we were still reading an image when the phasing band was detected. ./src/wefax/wefax.cxx: ? ? ? ? ? ?LOG_VERBOSE("Detected phasing when in image state."); ./src/wefax/wefax.cxx: ? ? ? ? ? ?save_automatic("phasing",comment); ./src/wefax/wefax.cxx: ? ? ? ? ? ?LOG_ERROR(_("Should be in phasing or image state. State = %s"), state_rx_str()); ./src/wefax/wefax.cxx: ? ? ? ?case RXPHASING: ./src/wefax/wefax.cxx: ? ?/// Because we might find a phasing band when reading an image. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#wefax parsing filenames
#wefax
What do the different fields in a WEFAX image file mean?? For example,
wefax_20241210_161517_9108100_apt
?
20241210 and 161517 are date and time, that much is clear.? It seems that 9108100 = Boston, and 8502000 = New Orleans, but why?? And finally, instead of "apt" I also see "phasing" and "nocorr" in some filenames.? What do these mean?
?
Thanks much,
Eric |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: [winfldigi] fldigi 4.2.06.14 development test version posted at
开云体育Tobias,A quick response to your testing. 1. End of signal wave shaping will be a little more difficult, but I'll see what can be done. 2. Each change in signal encoding/decoding necessarily not be backward compatible.? The result of using different different Viterbi polynomials and interleave depth.? No free lunch however, since increased interleave depth and more complex Viterbi means more demands on CPU performance. 3. Slow versus Fast CPU.? For anything other than an old P3 I recomment using Fast CPU setting.? Slow CPU setting tries to compensate by reducing the number of simultaneous path evaluations. 4. SNR evaluation is heuristic and the algorithms always have "factors" in the equations.? I'll do some additional testing with pure AWGN created with linsim.? Linsim is a PathSim replacement available for Win, Linux, and MacOS.? See comptext and comptty allow one to measure the CER and BER associated with ASCII text and RTTY text files respectively.
See attached files for jabberwocky.txt and jabberwocky_errors.txt
5.? AFC has no meaning for Thor.? I will disable the button. 6.? I will increase the AFC low pass filter coefficient to a maximum of 500. Vielen Dank fürs Testen. Die Ergebnisse sind sehr gut. 73, David |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[winfldigi] fldigi 4.2.06.14 development test version posted at
开云体育FYI
-------- Forwarded Message --------
Hello David, First of all many thanks for the updated FLdigi test version! Here are the results and observations on THOR25 in brief. Please refer to the attached updated spreadsheet for details, if necessary. 1. Raised Cosine Signal Shaping: Excellent! - Tested and confirmed OK: no more clicking when signing on using a Shape factor of e.g. 100 or more, while the setting '0' reproduces the previous state (non-shaped). - Not sure whether the removed end of signal shaping might be an issue, since it clearly creates a 'click'. => This could be avoided, if the same (user-set) yet reverfsed raised cosine shaping was applied there, too. 2. New Thor-25 DigiMode Definition: Major Improvement! - Compatibility with previous alpha test Thor-25 DigiMode Definition: NO (just for information). - RSID (TX and RX incl. the new secondary RsID code 691): OK. - Speed: similar to previous Thor-25 test version. OK. - File Audio Playback (original FLdigi created THOR-25 stream): Text reproduced 100% OK (Columns H+I in the spreadsheet referred to below). OK. - The signal decoding bandwidth ranges about +/- 250 Hz around the true center frequency (+/- 130 Hz with 'Slow CPU'). OK. - Not shown in the spreadsheet: the SNR is stuck around +5 dB (3 dB with 'Slow CPU') when decoding the original (perfect) audio. => This is certainly not realistic and should be corrected before a final release. 3. PathSim Mid-Latitude Disturbed NVIS AWGN SNR 0dB resulting audio: RX text with 4 line errors (the previous test version had produced 10 errors)! * See sheet 'PathSim NVIS THOR25A v4.2.06.14' see RUN #1 Columns B+C, RUN #2 Columns D+E, RUN #3 Columns F+G (Slow CPU). All previous sheets are unchanged: - I also attach a gently filtered flac audio file (smaller size but keeping the entire relevant bandwidth unchanged) just for your information. - Initially, for 38 consecutive lines or about 4 minutes, the decode was perfect! - Thereafter, in a few lines, there were 1 or 2 decoding errors, leaving part of the text scrambled. Note that if a linefeed was missing (error at the end of a line), I have corrected it manually to avoid auto-marking all lines below as errors. - A repeat using the exact same audio a 2nd time has reproduced the same fair result, interspersed with the few errors described above. Repeatability OK! - When checking [x] Slow CPU, the error rate increased to 14. Hopefully this might provide a hint as to where the remaining decoding issues may come from...? * See sheet 'SNR PathSim NVIS THOR25 v.06.14': - The FLdigi FEC log shows, that the signal is rated between error-free, yet still quite frequently at 50%, and once at 75% error, thus still a bit variable. - The average SNR on this disturbed signal is rated at -2.3 dB (unchanged), and it varies quite a bit along the way, yet probably in phase with the simulation conds. 4. Questions: - To find out about the remaining decoding issues, and possible further improvements: => Is there a way (e.g. using the existing log protocol - upon request?) to continuously track / log the current de-facto decoder frequency offset, SNR, and FEC? => In other words, could these values be added to the daily log file tags, e.g. current definition: RX 1500 : THOR25 (2024-12-09 18:16Z): <...RX TEXT...> extended definition: RX 1500 (1497): THOR25 -2.3 dB 75% (2024-12-09 18:16Z): <...RX TEXT...> => I thought about maybe 'seeing' whether the decoder does stay stuck on the 'correct' signal center frequency, or whether (and how) it starts sliding sideways? => Since decoding works so well over long stretches, maybe this might explain the short dropouts, and a slower 'AFC' in the THOR sense might stabilize the result...? - The AFC Button is still active. Better deactivate it or does it have any function in THOR? I have not seen a difference when activated. - On a related note, for MFSK AFC, if possible, I'd prefer allowing an even higher maximum low-pass filter setting, so far it's limited at 200 (quite helpful!). Bottom line, this has been yet another amazing leap ahead in the new THOR-25 DigiMode definition! Thank you, David! 73s Tobias .-.-. Am Montag, 9. Dezember 2024 um 15:37:32 MEZ hat Dave
<w1hkj@...> Folgendes geschrieben:
Most recent change: commit
0169172527f33938496aa6672adf7b0947922def Thor-25 signal showing RsID and 200 msec rise time at start of data stream. 73, David |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: FLDIGI MAC RTTY crashing
toggle quoted message
Show quoted text
On Dec 7, 2024, at 9:13?AM, Mike Adams, AG7AB via groups.io <mbadamsaz@...> wrote:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
On Dec 9, 2024, at 9:37?AM, Dave, W1HKJ via groups.io <w1hkj@...> wrote:
Most recent change:
commit 0169172527f33938496aa6672adf7b0947922def
Author: dave-w1hkj <w1hkj@...>
Date:?? Sun Dec 8 17:20:08 2024 -0600
??? THOR25
?? ?
????? * add new thor modem with following characteristics
??????? . symlen = 320
??????? . samplerate = 8000
??????? . flushlength = 20
??????? . bandwidth = 460
??????? . IEEE coefficients for viterbi encode/decode algorithms
????????? THOR_K15? 15
????????? K15_POLY1 044735
????????? K15_POLY2 063057
????? * increased flush length for all baud rates
????? * added configurable start of signal shaping to these modem types:
??????? . psk
??????? . mfsk
??????? . rtty
??????? . thor
????? * removed end of signal shaping
????? * assigned secondary RsID code 691
<wea2zKMvIbefQko3.png>
<5PQl4U6BlcpXb8ry.png>
Thor-25 signal showing RsID and 200 msec rise time at start of data stream.
73, David
W1HKJ