Allowing Multiple Applications To Control your Rig(s) - Dealing with "Exclusive Serial Port Locking"

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).  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.  FLDigi was able to access DXCommander via a nice little bridging tool developed by N2AMG called "Fldigi-DxLabs Gateway". 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.

So I remembered a little tools called "Omnirig" which I installed and quickly had WSTJ-X configured as it could natively integrate with it.  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).  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!.  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!.

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".  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.

This tool appears to take care of the "exclusive serial port locking" by creating a "virtual serial port split" from the source serial port.

• 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. I've not dug any further as to why RCForb has requires this but hey there's a work around.

Here is overview of my serial port topology / application integration:

Here is my VSPE config - "vpse_ft991a_virtual_split.vspe" which has both my FT-991A's serial ports (Enhanced / Standard) configured as "Virtual split".  Your ports may and will mostly differ but, the port settings will most likely be the same......

That's All Folks!   I hope this post helps you out to get all your applications that all want to talk and control the rigs working in harmony :)

73
Mark (de VK4TMZ)

Setting up ALE^Stat to work with PCALE

ALE^Stat is a great tool that can monitor PC-ALE / MARS-ALES activity and will post events (ie "soundings" received) upto HFLink or relevant web portal.

Head over the PC ALE Support Site and download the latest version of "ALE^Stat".   Install was easy and the documentation and configuration is fairly straight forward.

What had me initially stumped, was where was the "telnet" config option under PC-ALE ?  Well I found it but for some reason its not document under the "PC-ALE User Manual" or even ALE^Stat documentation.

Open  PC-ALE and under "Configuration->SWALE"  put in your PC IP and port number (63023) and check the "Interace Enabled".  If "ALE^Stat" was running you will see that it will "connection".  Then any activity decoded my PCALE will be reported to HFLink assuming you have enabled HFLink Reporting and entered you HFLink details correctly.

Load the same QRG file you have used for PCALE under ALE^Stats "frequency" menu.  Then ensure you have ticked the frequency under HFLink column that you wish to report / upload events to HFLink.

Not much more to say here! Have fun

73!!
de VK4TMZ