If you are using CW keying, using windows, you need to check and maybe, a little fix for everything to work correctly. When you are up and running, let me know. I use mac, but fldigi and flrig are the same. Also, in sound settings, please make sure to move any defaults from Digirig components to your computer’s internal mic/speaker. Only the CW keying must be set on fldigi as in the following photo:ĭon't pay attention to the different graphics. Before trying FlRig, let’s configure your G90 with the rig control directly from WSJT-X. ATTENTION: Everything must be set on flrig for the conversation with the radio. It is sufficient that the same setting is on the radio and on FLdigi. However, the configuration is very simple: CAT via USB Baudrate: 38400 DTR or RTS for usb keying of your choice (I use DTR). I'll give you two screenshots of the 101. If you also need to know how to set up the radio, just let me know. Here are the settings for FLRig and FLDigi: This takes care of acting as a link between any radio (including 101) and fldigi. I was having similar concerns in the past, and with his settings everything works FB. I encourage you to email him direct and he will send you images of what settings he has on the radio as well as his computer. On Tue, at 07:17 PM, Joe KI5O wrote: Very good. He was right, no problems after the fan was installed to run RTTY. Then I got a call from Drake repairman, saying if we install a factory fan in the rig, none of this would be happening. Then every few months the rig had to sent to the shops for repair due to blown resistors. Every thing seem to be setup right and it worked flawless. Reminds me back in 1983 when I had a new Drake TR5 setup for Kantronics RTTY. So, I stopped experimenting with HRD and now on Fldigi. When I tried to installed HRD (30 day trial) and press tune it would shut down the whole rig, Found out later the connection cable picks up too much RF and shuts it down. I really don't want to experiment on setup using a new rig on unproven setup procedure for digital. The advertisements for the 101D sounded like the rig was easy to setup for digital than most on the market, LOL. I will work on the settings he has given in the next couple of days. He does answer a few of the question I have on setup. Until someone fixes this bug I will either continue as above without OmniRig or will find another pgm to act as "Radio", such as HRD, N3FJP or as W9MDB suggests.Thanks, just found it, It looks like there are a lot of hams having the same problems in setup, too. Of course if wsjt Radio> 7610 then Log4OM cannot share the USB connection (no VFO indication) but can still receive QSO info from wsjt for auto-logging purposes. Under wsjt 2.5.3, everything worked 100%. Switch wsjt Radio dropdown to 7610 and of course error goes away. The error is the same, whether or not OmniRig is even PRESENT on the PC. As a precaution I use specific startup orders, e. However, with a Splitter (VSPE free 32-bit) it works fine, at least for me all the time, even if it shouldnt. It is clear from the wsjt error, that for some reason, as soon as wsjt 2.5.3 opens, it fails to FIND or SEE OmniRig. As you mention OmniRig, I suspect with FLDIGI youve run into the problem that 2 different programs (FLDIGI and OmniRig) can not share a COM port. Since you have a new Windows 11 installation, it is likely that OmniRig (if it is started by Log4OM) run with elevated privileges, Privilege level (*NOT* "run as administrator")? If Log4OM and The error is the same, whether or not OmniRig is even PRESENT on the PC.Are Log4OM, WSJTX and OmniRig *all* configured to run at the same It is clear from the wsjt error, that for some reason, as soon as wsjt 2.5.3 opens, it fails to FIND or SEE OmniRig. A file search for “wsjt” yielded nothing. One other detail- there were still 2 prior wsjt versions listed in Apps but clicking Uninstall returned a “Couldn’t locate the exe” error. Like FLdigi also does not support OmniRig. Ive looked at N3FJP and it seems it does not support OmniRig, at least I dont see it listed on the CAT settings. Rebooted PC multiple times in between above. Now, your question regarding N3FJP OmniRig is a 'middleware', the only thing it does is sharing the CAT connection between applications that support OmniRig and the radio. Tried running wsjt as administrator, after which rebooted and confirmed Log4OM, OmniRig, wsjt-x no longer running as admin. Upon opening, immediately got rig control error “Couldn’t Open OmniRig Server COM”. Initially installed without first deleting prev version. 2.5.4 to take advantage of crash elimination which I had been experiencing. Running Log4OM2 simultaneously (same USB cable) On Win11/64, wsjtx v 2.5.3 (FT8) with RADIO set to OmniRig 1, Data/Pkt, Split Have been using the following wsjt-x/Icom 7610 configuration with zero rig control issues:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |