#Nbems fldigi manual#
It can be a good idea to study the FT-991 CAT Operation Reference Manual also. Put it where you can find it and link to it from FLDIGI Config - Rig Control - RigCAT. Mine FT-991-v2.xml is enchanced, on my radio page. Put it in the folder C:\Users\ yourusername\AppData\Roaming\Afreet\Products\OmniRig\ FLDIGI can not use OmniRig, so a COM port Splitter such as VSPE is needed for FLDIGI cooperation with "omnirig programs", and then you can config FLDIGI with e.g RigCAT and a FT-991 xml config file. You will be mostly fine if you use the OmniRig FT-991 ini files fresh downloaded from, otherwise use mine FT-991-SA7CND.ini on somewhat updated by me. OmniRig itself will be called in the background when you have configured CAT in e.g WSJT-X, JS8Call or HDSDR ("Omnirig Rig 1"). OmniRig is a CAT software from and its config program is sort of a small box on the screen, much higher than wide.
Also, stop VSPE on the Stop button (or shut down Windows) before turning your rig off. You could look at my FT-991 and FLDIGI settings at If you use the VSPE Splitter, remember to turn on the rig first so USB/COM activates and then VSPE. The more Win apps that use OmniRig, the better. My FLDIGI uses RigCAT and AClog it own scheme, and the rest OmniRig, so there are 3 users of the COM port. As a precaution I use specific startup orders, e.g one or more of FLDIGI, N3FJP AClog, HDSDR/CW Skimmer or WSJT-X/JS8Call, all the latter using OmniRig (which is safe for sharing a COM port). However, with a Splitter (VSPE free 32-bit) it works fine, at least for me all the time, even if it shouldn't. As you mention OmniRig, I suspect with FLDIGI you've run into the problem that 2 different programs (FLDIGI and OmniRig) can not share a COM port. I have an FT-991 with just a USB cable to a Windows 7 laptop, and use CAT with FLDIGI and many more programs.
0 kommentar(er)
