开云体育

John VK2ETA, Recently a new situation arose which is troublesome when transmitting from the wonderful AndFlmsg phone app. When I click "TX OVER RADIO," the media volume setting of the Android phone drops from 100% to about 10%. Although I can quickly reset the volume level to 100%, the beginning of the transmission occurs at too low a volume setting. This new situation started a few weeks ago. Perhaps there was a Samsung Android software update which now causes the phone media volume setting to battle the AndFlmsg output? I am looking for suggestions to block the automatic volume drop. Is there an Android setting I should change? Thank you for all you do. 73 de . . . Rob K6RJF

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 http://www.nyc-arecs.org 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

FYI -------- Forwarded Message -------- Subject: Re: [winfldigi] fldigi 4.2.06.14 development test version posted at Resent-Date: Mon, 09 Dec 2024 11:29:23 -0800 Resent-From: tsquare123@... Date: Mon, 9 Dec 2024 19:29:17 +0000 (UTC) From: T? via groups.io <tsquare123@...> Reply-To: [email protected] To: [email protected] 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 TH

I am going to suggest that the PA NBEMS (Sunday 0730 hr EST on 3583 kHz) and the Mid-Atlantic NBEMS net (Sunday 1000 hr EST on 7068 kHz) test THOR25 as the traffic mode (we use FLMSG and FLAMP) Our experience in early morning hours on 80m and mid-morning hours on 40m is that there are occasional deep fades (1 or 2 S units) which clobbers a second of data, hence the “bad file” designation of FLMSG We have been using THOR32 and MFSK32 and both work well as long as the S/N is in the positive range. I seem to get most (but not all) of the file if the S/N drops to -10dB. I encourage folks on this IO group who can copy the PA or Mid-Atlantic NBEMS (we usually get checkins from PA/MD/DE and many from NY/NJ and a few from New England stations, as far south as VA/NC and west to WV and sometimes OH) to try THOR25 A few of us can remain on the net frequency (3583 kHz or 7068 kHz) after the nets end for further testing. de k3eui. barry (Philadelphia region)

I am going to suggest that the PA NBEMS (Sunday 0730 hr EST on 3583 kHz) and the Mid-Atlantic NBEMS net (Sunday 1000 hr EST on 7068 kHz) test THOR25 as the traffic mode (we use FLMSG and FLAMP) Our experience in early morning hours on 80m and mid-morning hours on 40m is that there are occasional deep fades (1 or 2 S units) which clobbers a second of data, hence the “bad file” designation of FLMSG We have been using THOR32 and MFSK32 and both work well as long as the S/N is in the positive range. I seem to get most (but not all) of the file if the S/N drops to -10dB. I encourage folks on this IO group who can copy the PA or Mid-Atlantic NBEMS (we usually get checkins from PA/MD/DE and many from NY/NJ and a few from New England stations, as far south as VA/NC and west to WV and sometimes OH) to try THOR25 A few of us can remain on the net frequency (3583 kHz or 7068 kHz) after the nets end for further testing. de k3eui. barry (Philadelphia region)

at http://www.w1hkj.com/alpha/flrig/ flrig-2.0.05.85.tar.gz flrig-2.0.05.85_LI.dmg flrig-2.0.05.85_SO.dmg flrig-2.0.05.85_setup.exe flrig.png flrig_help.pdf readme.dmg.txt readme.txt See readme.txt for most recent changes. 73, David W1HKJ

Hello, All: I am using one of Kevin's DRA units with Fldigi, VARA-HF and Winlink Express in my daily traffic handling work. So far, it has proven to be the best digital interface I have ever used. I prefer to use the C-Media sound-chip's PTT function which is available with any of Kevin's (Masters Communications) DRA units as it is faster, more reliable, and is easier to contrtol than using VOX to key the transmitter. Fldigi has that funtion built into it, but it is apparently, only available to users of Linux. I have two computers here which can dual-boot either Win10, or FreeBSD ver 14.1. I much prefer to use FreeBSD over Win10 or any of the many distros of Linux. However, although I have "translated" the UDEV setup, listed in the PTT setup of Fldigi which is required for Linux to the correct settings of the UDEV-equivalent in FreeBSD (DEVD), I cannot get the C-Media PTT to work. My only solution to that issue here is to activate keying by VOX in the DRA unit when using FreeBSD. Although VOX can be acrivated in the DRA unit by moving one jumper, I am concerned that doing so will affect the use of PTT keying via the C-Media chip in Win10. So, my question to Dave and to anyone else here, what, exactly, are the commands in Fldigi which activate the C-Media chip's PTT function in Linux? I am hoping that by learning this, I MAY be able to "translate" those commands to FreeBSD. vy 73, Ken W7EKB -- This email has been checked for viruses by Avast antivirus software. www.avast.com

http://www.w1hkj.com/alpha/fllog/ Index of /alpha/fllog Parent Directory fllog-1.2.8.01.tar.gz fllog-1.2.8.01_LI.dmg fllog-1.2.8.01_VN.dmg fllog-1.2.8.01_setup.exe readme.dmg.txt readme.txt commit 04f7b0cc942612e5174594b2dab99cdce3a16aa2 Author: dave-w1hkj <w1hkj@...> Date: Sat Oct 19 20:47:41 2024 -0500 alpha commit f6928791bcd46949d13d745dc34dea14494d8661 Author: dave-w1hkj <w1hkj@...> Date: Sat Oct 19 20:47:23 2024 -0500 Hell modes * dup check all Hell submodes as a single mode commit c5766d56911ef79f5441740bfe5867ebe66493b0 Author: dave-w1hkj <w1hkj@...> Date: Tue Jan 16 20:00:00 2024 -0600 Version 1.2.8 ======================================================= and http://www.w1hkj.com/alpha/fldigi/ Index of /alpha/fldigi Parent Directory fldigi-4.2.06.02.tar.gz fldigi-4.2.06.02_LI.dmg fldigi-4.2.06.02_VN.dmg fldigi-4.2.06.02_setup.exe fldigi-dark-scheme.png readme.dmg.txt readme.txt commit 53d71ba5e6a32a0944398dfdb3af237a529e2201 Author: dave-w1hkj <w1hkj@...> Date: Sat Oct 19 19:51:00 2024 -0500 alpha commit 6eae131e98abb68c477f214bb87c3072ae42b1ee Author: dave-w1hkj <w1hkj@...> Date: Sat Oct 19 20:53:24 2024 -0500 Hell modes * Make all modes equal for duplicate test. Include mode designations prior to ADIF conformance code change. commit b4e763fe467d8067c4b420d53c4859327fed02c9 Author: dave-w1hkj <w1hkj@...> Date: Fri Oct 18 06:37:04 2024 -0500 ui_colors * fix bugs introduced by commit 9bd273df32722882f4761651 commit ea5302cfe740a469354f98f9a3300351ac3d3b64 Author: dave-w1hkj <w1hkj@...> Date: Fri Oct 11 08:51:29 2024 -0500 Version 4.2.06 73, David, W1HKJ