开云体育

Mick N3OJP I have never encountered a “run time error” so have no advice, other than to keep asking folks more familiar with operating systems. I will copy your concern to folks who are pretty solid with FLDIGI. I would not complain if a Win 7 machine fails. Update! But my three Win10 computers (two desktops, one laptop) have never encountered a RUN TIME ERROR. Keep us in the loop. I would delete the PREFS file first, and start all over with FLDIGI. Barry Why am I getting a runtime error? Runtime errors can occur if you are running two software programs that are not compatible, if your computer has memory problems, or if the computer has been infected with malicious software. Therefore, I suggest you to check if there are any latest updates available for the program from the manufacturer's site.Aug 30, 2011 Barry On Dec 10, 2024, at 6:05 PM, MICHAEL PYZOHA <pyzoham@...> wrote: ? Hi Barry I need some guidance from you as VARA on my Win 10 machine using Winlink or VacAC is giving me Run Time Error and used to work just fine. I use a Win 7 machine and I have no trouble with VARA, Winlink or VarAC. I have deleted from the Win 10 machine Winlink, VarAC and VARA and reinstalled same problem. The Run Time Error appeared out of no where and if I can resolve that I may have luck with the Win 10 machine. I did check the VarAC forums and VARA support and I find nothing on the Run Time Error so must be a Win 10 computer issue and VARA. I have done research on the Run Time Error, tried some suggestions and no change. There is also a Com Port issue with VarAC. This Win 10 laptop used to work with VarAC and Winlink and something changed and I do not have a restore point. Any advise is appreciated Barry and don't spend much time as I think I will deinstall the programs and start fresh again. BTW Fldigi works ok on this Win 10 machine and I will download the version that uses THOR 25 as I read your groups.io postings. I like to use the Win 10 machine in my travels to Western NY home with 71' wire and EFHW. I have attached 3 screenshots showing the problems I see. See what you think Barry....thanks Mick Pyzoha N3OJP Using Winlink I always get this error on the Win 10 machine when VARA opens. If I click on ok VARA closes and does not restart. I have to close Winlink, start up Winlink, VARA starts up and I get the error. When using VarAC in Settings the Com port number will not save. I can enter Com 3 which is correct, PTT ON test works, Save and Exit and reopen VarAC Setting and Port is blank. The Com port will not save. VARA does not open automatically in VarAC even though in Settings in the VARA tab I have the correct path. I open VARA manually and get the Run Time Error.

Hi all, I'm EA3FH just joined the group while trying to fix an issue with FLRIG which I'm experiencing since my last setup change. I've been using FLRIG with an emulated K3 from Remotehams since years ago. With my old setup I used to have one remote computer and one local dedicated computer for radio related, but finally I will just keep the remote computer and my needs now are not to use Remotehams for now. So, I configured FLRIG and I am able to connect my 706MK2G wihout issues; I was able also to use keyers, wsjt-x, ptt... all ok. The issue comes now that the SPLIT button that it's suposed to be in the FLRIG Application is not there. In the FLRIG help webpage it states that button should be there: But in my case, this is how I see it, without the Split button. How can this be fixed? FLRIG version used is 2.0.05 Thank you! Julio EA3FH

http://www.w1hkj.com/alpha/fldigi/ fldigi-4.2.06.14.tar.gz fldigi-4.2.06.14_SO.dmg fldigi-4.2.06.14_setup.exe 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 Thor-25 signal showing RsID and 200 msec rise time at start of data stream. 73, David W1HKJ

http://w1hkj.com/alpha/fldigi/readme.txt suggestion - let’s try thor25 for traffic over next few weeks on PA NBEMS (3583 kHz at 0730 hr EST) and MidAtlantic nbems net (7068 kHz at 1000 hr est) on Sunday mornings Barry k3eui readme Text Document · 895 KB

RF SPECTRA of the THOR speeds on HF SSB There is a new (alpha) THOR mode with the designation THOR 25 We tried THOR25 after the PA NBEMS net (Sunday 0730 hr on 3583.0 kHz) and it worked well as a traffic mode, compared to THOR32 which we have been using (as well as MFSK32). I wanted to compare the RF SPECTUM of each of the THOR speeds, so I used a SDR (RSP play hardware) and RSP Spectrum Analyzer (software) and set it on 3585.5 kHz center frequency with a very high resolution bandwidth. Transmitter was an Icom 7610 (built in sound card) with VFO set to 3585.0 kHz Here are the results, showing the "peak" bandwidth of the THOR speeds, as well as the BW at 30dB below the peak. I think the present definition of "bandwidth" is that width at -26dB below the peak, so -30dB is close to that standard and easy to see. I think the other definition of BW is that signal containing 99% (or was it 99.9%) of the energy. THOR25 is still in testing (alpha) and does not yet have an assigned TXID/RXID identifier. But you can manually go to OP MODE on top menu and select THOR25. The goal of the 80m and 40m NBEMS nets is to use one mode for taking check-ins (usually THOR22) and to send the call sign twice, then the name, location (county if in Pa) and traffic/no traffic or QTC/QRU, and many send a S/N of the net control. THOR vs. MFSK THOR modes are far easier to tune in on SSB compared to MFSK modes. I find if I mistune a MFSK32 signal by about 15 Hz then I lose all copy. THOR can be badly mistuned and still get full print. THOR also uses the "difference in pitch" from one tone to the next tone as the character, not the absolute pitch. There are other reasons I prefer THOR on HF NBEMS nets. So take a look at the RF spectra (not the audio spectra) and see for yourself the pros/cons of each speed. As FLDIGI develops the THOR 25 mode, we will have more data to report back to W1HKJ. de k3eui Barry Kennett Square PA (near Phila) Dec 08 2024

Tobias, Please test both MFSK and THOR (especially new modem type THOR-25) added to 06.12 test version at http://www.w1hkj.com/alpha/fldigi/ commit db6798876a79e5087a69017c2a6c5c32712c05b6 Author: dave-w1hkj <w1hkj@...> Date: Wed Dec 4 06:31:43 2024 -0600 THOR25 * add new thor modem with following characteristics . symlen = 320 . samplerate = 8000 . flushlength = 40 . bandwidth = 460 Also increased the flush length on all THOR modem types. David On 12/1/24 09:22, T? via groups.io wrote: Hello David, I found the respective information mentioned in my last e-mail, that the bandwidth is restricted to 500 Hz: it's in the IARU Region 1 Bandplan (attached) for the 80 m DigiMode frequencies between 3580 and 3600 kHz, denominated 'Narrow band modes'. While wider modes are accepted above 3600 kHz, these parts of the band are usually full of SSB communication and thus not used (and suited) for DigiMode traffic, except the area around 3733 kHz, which is frequently used for short SSTV (analog and digital) image QSOs here in Europe. Similar 500 Hz bandwidth restrictions apply in many other HF bands. - - - - - - If I may ask, is there a technical necessity to define the THOR32 mode a bit wider (vs. the MFSK32 definition) than the above-mentioned 500 Hz limit? In other words, would it be possible to define a THOR32-500 mode. e.g. by reducing the tone spacing to the 31.25 Hz used in MFSK32, which Hams could then use within the 500 Hz limits of the bandplan? I am aware that not all signals on the air do comply with the requirements, and some Hams actually use wider modes in these bands (against the rules), but at least all members of the German DARC club are required to adhere to the official bandplan definitions, and they do risk losing their membership, I was told, if they don't. So there's no practical way to replace MFSK32 with THOR32 for the DL0BS QTC and the QSL traffic, as I had recently described. - - - - - - By the way, based on your recent feedback about THOR32, I got curious and made a first comparative PathSim evaluation between MFSK32 and THOR32 with signals directly created in fldigi ver4.2.06.11, using an old (yet typical) DL0BS intro text, dating back to the Ol4/500 times and Wednesday schedule (today, it's every Monday evening at 2100 CET = 2000z in MFSK32 on 3590.75 kHz). - FLdigi @ 1500 Hz: TX generate MFSK32 and then THOR32 -> 2 separate WAV files. - Level normalized to 5% amplitude (both files) and 1 second pauses (leading and trailing) were added, this helps runs the simulations correctly. - PathSim set to 'Mid-Latitude Disturbed NVIS' with path 1 (1 Hz frequency spread), path 2 (1 Hz frequency spread, delay 7 ms), plus AWGN noise set for 0 dB SNR. - FLdigi Audio Playback (both files), again set to 1500 Hz (no center offset). - Rx text (both files) separately copied into the prepared spreadsheet. - The spreadsheet compares each line vs. the original TX Text, auto-highlighting all deviating text lines in yellow. The plain result is, that MFSK32 produced 2 errors (one of which was the missing SOT sign), and THOR32 produced 18 errors (one of which was the missing SOT sign, too). I don't know what has caused this unexpected difference, but it is clearly too significant to be just a random effect. There may be other signal conditions where THOR32 is more stable than MFSK32 (certainly in case of RX mistuning), but I have intentionally chosen a test case known to be borderline, where MFSK32 started producing first errors in a simulation run back in 2023, in the wake of the intended Ol4/500 to MFSK32 transition (Olivia did a lot worse by the way). While THOR32 has decoded parts of the text perfectly fine, others deviate considerably. Could this be an effect of the built-in wide frequency range compatibility (a bit similar to the discussed AFC issues in MFSK32 - AFC was OFF here!), so that instead of keeping the theoretically best signal (staying put @ 1500 Hz audio in this case), when the signal blurs in weak conditions, it starts going astray 'sideways' temporarily, and thus decodes worse than what is is ideally capable of

I am helping a fellow ham, Tom, get setup to run the several modes available in fldigi. The issue we are having is related to HIS fldigi software displaying incoming RsID in the window that normally opens when the RsID signal is received. That window does not display on his machine. When I initiate a call HE can hear the RsID tones at the beginning of my transmission through the radio speaker. No window opens to display the mode and frequency nor the button to select that signal. I have also listened to his received audio over the telephone and am sure the RsID is present at his receiver. I am sure that I am transmitting valid RsID signals. This is shown with two other operators that have verified that I open the RsID window on their computers. Further, Tom and I can conduct a digital contact both ways with the content printed out correctly on the computer that will not show the RsID window. His setup includes a Windows 10 computer and fldigi version 4.2.03 He has all the modes selected in "Receive RsID" choices as well as all the "Transmit RsID" choices selected. When he transmits to me I display the RsID window on my computer for the signal he transmits. That part is working. The two RsID buttons in the upper right corner of the fldigi window on Tom's machine are "colored" which we believe indicates those modes are turned on. We have looked and the RsID window is not opening behind the main fldigi window or any other window. Is it possible that it is opening somewhere off the screen in some "never never land" or maybe on a "second monitor" that he doesn't have? Can anyone provide information that will help us find the missing window and get this feature working on Tom's computer? Thanks, Bob K8EAC

Hi I can receive CW in Fldigi, but can not transmit. I have tested using another radio, and while FLdigi does transmit, there is no audio, just a carrier. I've checked my settings and have the correct sound card selected. To make matters harder, I can transmit and receive on Olivia. Any help appreciated!

fldigi-4.2.06.10 posted at http://www.w1hkj.com/alpha/fldigi/ fldigi-4.2.06.10.tar.gz fldigi-4.2.06.10_LI.dmg fldigi-4.2.06.10_SO.dmg fldigi-4.2.06.10_setup.exe fldigi-dark-scheme.png readme.dmg.txt readme.txt You should be able to change the LPM setting during reception. Please test and report results. 73, David, W1HKJ On 11/26/24 02:07, Asbesto, IW9HGS via groups.io wrote: Hello! Meanwhile, I did some research... First I found this: https://www.sstv-handbook.com/download/sstv_11.pdf in which the WEFAX settings are described as any kind of combination between 288/576 and 30,60,120,240 lpm... at page 7 of the pdf, Kyodo news is quoted as requiring 60 and 120 lpm / 576 IOC setting: "Next Tokyo station is JJC, it is Kyodo News Agency. Transmission speed is 60 lpm and IOC 576, sometimes 120 lpm when weather charts are posted." I also wrote to the owner of the internet site https://kyodonewsradiofax.wordpress.com/about-kyodo-news/ and reached to me, indeed confirming that the setting for 576/120 and 60 are needed in order to receive this station... quoting his email: "Yes, for Kyodo one needs 576/60. Fldigi removed the line setting from its interface at some point, quite a long time ago. What I did, was that I created a copy of Fldigi source code and changed hardcoded 120 to 60. So for Kyodo decoding I would simply run a second altered Fldigi. So yes, I can confirm this behavior of a removed lines dropdown, as it really was there before." I think the best course of action is to permit changing the combination of all those parameter as it was before, also as it is described in the wefax standard in the PDF i linked before - I will do it myself but I'm not a skilled programmer anymore (I was a programmer in the late '90 :) ) I will try to receive some transmission to test them asap! TY 73 de IW9HGS Gabriele On Sun, Nov 24, 2024 at 3:14 PM Dave, W1HKJ via groups.io <w1hkj@...> wrote: Can you please create a sound file recording of the KYODO NEWS wefax broadcast. Send it direct to w1hkj@... Thank you. David On 11/24/24 05:31, Asbesto, IW9HGS via groups.io wrote: I see, but those changes broke the reception of a very interesting radio station (KYODO NEWS). For what I see, this is a bug - something that was working before, now it isn't. :( On Fri, Nov 22, 2024 at 2:15 PM Dave, W1HKJ via groups.io <w1hkj@...> wrote: Those changes were made over 4 years ago. If you need to reinstall an older version of the software these are available at http://www.w1hkj.com/files/archives/ 73, David, W1HKJ On 11/22/24 01:01, Asbesto, IW9HGS via groups.io wrote: Hello, In FLDigi 4.1.9 that I had on my old computer I was able to set some things about WEFAX that now are disappeared in the newer versions... I have a new laptop, I installed the recent version of my GNU/Linux OS, and some options are missing. I don't have anymore the "LPM" setting, the FIR setting nor the 4 bargraph showing START, PHASE, IMAGE... and I think also the "skip phase" is missing. The main problem is the "LPM" setting, because I can't set it correctly to receive Kyodo News from Japan. Kyodo News require IOC576 with 60LPM and I can't set it What I receive now is basically a half page, the other half is cut away and I can't solve this problem. Is there some way to get back those settings for WeFax? I think now it's unusable for KYODO NEWS decoding. Thank you --

j’utilise le logiciel FLDIGI qui ai très bon depuis un temps sous win 10 64 bits , pour décoder des images fax en HF et le logiciel au bout de deux heures il s'arrête complètement ! es-que ces normale ? dans la version gratuite merci pour des infos sur ce sujet 73 a tous

This is rather strange. I have Fldigi working logged in as admin on windows 11. It is version 4.2.06 and an ICOM 7300. Using the same configuration as a standard nonadmin user PTT does not work. If I click on tune nothing happens but if I am logged in as admin tune works fine. I did have a problem during the install as COM4 did not appear on the list but I entered manually and then it worked. I have tried rebooting and restarting the radio but it is 100% reproducible that I can not get it working other than as admin. I was also wondering where does the configuration get stored?

http://www.w1hkj.com/alpha/fldigi fldigi-4.2.06.07.tar.gz fldigi-4.2.06.07_LI.dmg fldigi-4.2.06.07_VN.dmg fldigi-4.2.06.07_setup.exe fldigi-dark-scheme.png readme.dmg.txt readme.txt Note: - added SCAMP mode - added additional time scales to fmt mode; 4, 8, 16, 24 and 48 hour - MacOS users on MacOS > 13.x.x will have to ignore the "malicious" software warning during first execution. Should only require a single response to the "use microphone" dialog.