![]() ![]() I've not dug any further as to why RCForb has requires this but hey there's a work around. Note: The only hassle I had is that RCForb needs to be started first, after that any and all applications work running at the same.This tool appears to take care of the "exclusive serial port locking" by creating a "virtual serial port split" from the source serial port. The tool is free to download, and use but you will be reminded to purchase a "64-bit License" which I highly recommend for such a great little tool. So a little more googling, I saw reference to using to a little gem off a tool by Eterlogic called VSPE which offers " virtual serial port splitting". However I was to quickly learn N1MM did not integrate with Omnirig nor did many of my other applications (PC-ALE, RCForb, MRP40 (CW RX/TX) etc) so back to square one kinda!. As a bonus now that Omnirig was running a contest logging software I use " VK Contest Logger - VKCL" was able to also integrate with it too!. ![]() Next looking round the web for a new Logging application I came across " Log4OM" which also natively integrates with Omnirig and its a slick and easy to use UI as well as all the external logging (eSQL, QRZ.com, LoTW, ClubBook, HamQTH, etc). So I remembered a little tools called " Omnirig" which I installed and quickly had WSTJ-X configured as it could natively integrate with it. But it always annoyed me that I was not able to run RCForb (server) while DXCommander was running due to the serial port being exclusively locked. FLDigi was able to access DXCommander via a nice little bridging tool developed by N2AMG called " Fldigi-DxLabs Gateway". WSJT-X was able to natively talk to "DXLab Commander" and setting up virtual "cat" under DxLab Commander N1MM was able to also access VFO etc. software-flrig, baofeng-gt-5r, baofeng-uv-5r. Start both FLDIGI and FLRIG, make sure that FLDIGI is set. Since the rig is controlled by OmniRIG, I cannot get rig control to work within FLDIGI. FLDIGI then you do have some other interface options, explained in the main FLDIGI on-line help. I would think VarAC should work properly without having to use OmniRig. I am reluctant to download OmniRig because it might screw up what is all ready working. ![]() The gibberish characters appear with and without the radio on. I am currently using WinLink, JS8 Call, FLDIGI. In reality, I only need Omnirig when using phone and CW. For my other digimodes, I use Fldigi and that setup passes the frequency to the log. With JTDX, the rig control is by the latest hamlib that is included with it. Nothing appears in the FLDIGI waterfall and the output screen is just a string of gibberish characters. Luckily, I do not need it for any digi modes at all. I have not been able to get the IN/OUT Services to start on the Settings/Services tab.Until yesterday, when I finally decided to do a little review of my logging and rig control software, I'd been using DXLab Suite for Logging (DXKeeper), Rig Control (DXLab Commander). For reasons unknown, I cannot get anything into FLDIGI. I was able to go into Log4OM Communicator and turn all the lights green on the Interface tab. I am presently using Rigcat to connect to the Flex radio. FLDigi seems to allow EITHER Rigcat or XML-RPC connections, not both. Pay attention to the checked Use RigCat, checked CAT command for PTT and the unchecked RTS/CTS flow control. You will see the following: Here the device is set to COM14 from a previously created COM14-COM15 virtual pair. Should clicking different spots on the FLDigi passband waterfall change the QSO frequency in Log4OM to the actual receive frequency?Ģ. Select Configure, Rig Control from the FLDIGI screen. I will provide all the port information, but a couple of basic questions first to make sure I am setting things up correctly.ġ. I have it setup to use xml-rpc, I get green in the commander window on all three lights and when I try to transmit, PTT is keyed, but no sound. The problem is in the F1 Logger QSO Window. Change bands and the VFO readouts follow. Both the CAT VFO readouts in LOG4OM work perfect, turn the dial and the readouts follow. Using Omnirig with the FTDX-101D Omnirig ini file dated 10-07-19. Norton Antivirus is installed, the Norton Firewall is not installed. I have log40m, omnirig and WSJT-X working great. I had been using the modified file, to be sure I re-downloaded. The SDR, FLDigi, and Log4OM are correctly passing the VFO 'base' frequency between themselves.Īll the software in question is running under Win7 in a Parallels 10.1.1 VM on an iMac running Yosemite. I’m talking about likes of Omnirig (free), Flrig (free), Hamlib (free), Ham Radio Deluxe (paid), etc. I am using the FlexRadio SmartSDR program, along with SmartSDR CAT and OmniRig (SmartSDR CAT generates the serial ports similarly to VSP). Wait, what I may be coining a new term here. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |