Virtual Com-port in Win10
I want to set up a virtual Com-port in Win10 in order to be able to have a PTT-signal going from MSHV (generating FSK441, JT8 etc. signals) to SDR-Console to initiate Tx.
I do not want to use the VOX for switching from Rx to Tx when using an external PA to my Hermes board. BTW PTT via VOX switches OK but I am not positive that the RF is not present when the external TR-relay switches.
I tried com0com but I can not getting it to work in Win10. It installs fine in Win7 but in Win10 the Com-ports does not show up correctly in the Device Manager and can by that not be found by SDRC nor MSHV.
Any suggestions on how to transfer the PTT command from e.g. MSHV to SDRC in Win10?
BTW Does the RF-delay parameter (in the Tx-options) work as expected when using VOX? Will e.g. a 100 ms FR-delay, be 100 ms after the PTT-signal from SDRC to the Hermes-board before RF is present?
73 / Ingolf, SM6FHZ
I want to set up a virtual Com-port in Win10 in order to be able to have a PTT-signal going from MSHV (generating FSK441, JT8 etc. signals) to SDR-Console to initiate Tx.Ingolf
I suggest you persevere with the virtual com ports because when you get them going it makes life very simple.
I use VSP Manager from K5FR and it's always worked fine for me on both Win10 and now on Win11.
http://k5fr.com/DDUtilV3wiki/index.php/VSP_Manager
Just email K5FR with your callsign and he will email you a link to download it from him free.
I can't remember why but I seem to have set mine up (VSPMgr) in compatibility mode for Win7. Must have done that for some reason. Maybe Com0Com needs that as well? Perhaps try that first. before switching to VSP Manager.
Also I seem to remember (Joanne will know this as I know she uses it) that there are a couple of tick boxes in Com0Com that need either ticking or unticking when making the ports. Sorry I don't recall, but try with ticked and unticked. See what happens.
73
Max
I am using both com-0-com and Eterlogic VPSE in Win10.
Â
https://eterlogic.com/Products.VSPE.html
Â
I use virtual com ports for PTT with WSJT-X, MSHV, Thetis and of course various none SDR radios. I never use CAT for PTT because I use sequencers for the RX/TX transverters etc. I am completely paranoid about vaporising expensive relays. I also used virtual com ports with Elad FDM-Duo and SDRC in the past.
Â
Regards
Â
Conrad PA5Y
Â
Â
Sent: 15 January 2023 15:39
To: main@SDR-Radio.groups.io
Subject: [SDR-Radio] Virtual Com-port in Win10
Â
Hi all.
I want to set up a virtual Com-port in Win10 in order to be able to have a PTT-signal going from MSHV (generating FSK441, JT8 etc. signals) to SDR-Console to initiate Tx.
I do not want to use the VOX for switching from Rx to Tx when using an external PA to my Hermes board. BTW PTT via VOX switches OK but I am not positive that the RF is not present when the external TR-relay switches.
I tried com0com but I can not getting it to work in Win10. It installs fine in Win7 but in Win10 the Com-ports does not show up correctly in the Device Manager and can by that not be found by SDRC nor MSHV.
Any suggestions on how to transfer the PTT command from e.g. MSHV to SDRC in Win10?
BTW Does the RF-delay parameter (in the Tx-options) work as expected when using VOX? Will e.g. a 100 ms FR-delay, be 100 ms after the PTT-signal from SDRC to the Hermes-board before RF is present?
73 / Ingolf, SM6FHZ
Did you use signed version of com0com? Encouraged by Simon I recently installed com0com in my new Windows 11 machine and it works well.
Best regards,
Mauno
Hi all.
I want to set up a virtual Com-port in Win10 in order to be able to have a PTT-signal going from MSHV (generating FSK441, JT8 etc. signals) to SDR-Console to initiate Tx.
I do not want to use the VOX for switching from Rx to Tx when using an external PA to my Hermes board. BTW PTT via VOX switches OK but I am not positive that the RF is not present when the external TR-relay switches.
I tried com0com but I can not getting it to work in Win10. It installs fine in Win7 but in Win10 the Com-ports does not show up correctly in the Device Manager and can by that not be found by SDRC nor MSHV.
Any suggestions on how to transfer the PTT command from e.g. MSHV to SDRC in Win10?
BTW Does the RF-delay parameter (in the Tx-options) work as expected when using VOX? Will e.g. a 100 ms FR-delay, be 100 ms after the PTT-signal from SDRC to the Hermes-board before RF is present?
73 / Ingolf, SM6FHZ
Max, I have mailed K5FR and is hoping for a positive responceHe's usually pretty quick. Just for info I add com ports with the VSPMgr window set exactly as he shows it on the page I linked (neither box ticked).
Also once installed, before you add any ports, go to the VspMgr.exe file (my install is in "Program Files x86" folder) and in the Properties for the .exe I have these two boxes ticked. I'm not sure why but I seem to remember it does matter or I don't think I would have done it. I must have read it somewhere in the help files. Now I can't find that advice (typical).
Max
I installed 3.0 from here:
https://sourceforge.net/projects/signed-drivers/files/com0com/
and the pairs show like this in device manager:
Mauno
Hi Mauno.
I've tried both V3.0.0.0 and V2.2.2.0 with the same result.
V3.0.0.0 supposedly not being signed and V2.2.2.0 being signed.
None of them was able to set up virtual CUM-ports that showed up in the Device Manager together with the other COM-ports.
73 / Ingolf
Just a heads up...If I remember correctly you need to install
K5FR comm. program as Administrator when you get it. Used to be
anyway.
FWIW...Cal...W1HHO.
On Sun, Jan 15, 2023 at 03:39 PM, sm6fhz wrote:-- All the Best from the woods of Maine.
Max, I have mailed K5FR and is hoping for a positive responceHe's usually pretty quick. Just for info I add com ports with the VSPMgr window set exactly as he shows it on the page I linked (neither box ticked).
Also once installed, before you add any ports, go to the VspMgr.exe file (my install is in "Program Files x86" folder) and in the Properties for the .exe I have these two boxes ticked. I'm not sure why but I seem to remember it does matter or I don't think I would have done it. I must have read it somewhere in the help files. Now I can't find that advice (typical).
Max
You were correct Max, Steve answered very swiftly.
It is now installed and after some fiddling it is working as expected.
You need to set the flag "Emulate baud-rate" on both ports to get it working.
FWIW Calder, I did NOT install it as "Administrator" and it still works as expected in my Win10 environment.
But, as usual, every little piece need to be in place. Just that you have to find these small bits and pieces :-)
Thanks to all for the support !
I am now a happy user of VSP Manager Virtual COM-port Emulator and have a PTT function from MSHV to SDRC and on to my Hermes board.
Next step will be to hook-up the TR-switch to the Hermes so I can use one antenna for both Rx and Tx.
73 / Ingolf, SM6FHZ
Maybe Max has the answer to this one.
Is there a way to save the port set-up you have made with VSPM?
You have to run VSPM each time when you start your computer to define the virtual COM-ports, but VSPM does not remember the previous set-up so you have to do the full procedure each time you boot the PC.
Is there a way to do this a bit smarter?
Also I have noticed, you have to run VSPM first ting, then open SDRC, MSHV etc that uses the virtual COM-ports. Not a surprise, but you have to remember it at each boot.
73 / Ingolf, SM6FHZ
Go to startup->com0com->setupg.com
Create a COMn pair. Make sure "use Ports class" is checked on both sides.
Bob's your uncle. (I've never found a used for ports without
those two checkboxes checked.)
{^_^}
Hi all.
I want to set up a virtual Com-port in Win10 in order to be able to have a PTT-signal going from MSHV (generating FSK441, JT8 etc. signals) to SDR-Console to initiate Tx.
I do not want to use the VOX for switching from Rx to Tx when using an external PA to my Hermes board. BTW PTT via VOX switches OK but I am not positive that the RF is not present when the external TR-relay switches.
I tried com0com but I can not getting it to work in Win10. It installs fine in Win7 but in Win10 the Com-ports does not show up correctly in the Device Manager and can by that not be found by SDRC nor MSHV.
Any suggestions on how to transfer the PTT command from e.g. MSHV to SDRC in Win10?
BTW Does the RF-delay parameter (in the Tx-options) work as expected when using VOX? Will e.g. a 100 ms FR-delay, be 100 ms after the PTT-signal from SDRC to the Hermes-board before RF is present?
73 / Ingolf, SM6FHZ
(Suggestion for Simon included.)
By the way: For fast first line help with SDRC visit the place you got it. Then look at all those names with little arrows beside them at the top of the page. Marvelous decoration, aren't they. I wonder what happens if I click the Console menu. On look, it's menus.
Simon has gone to unusual trouble to create actually helpful tips. I highly recommend visiting them. So does google when you search for "com0com site:sdr-radio.com". It pointed to the "Serial Port" selection on the menu under "N-Z". The second item is com0com. Now, if Simon would add my helpful little picture to that and edit my notes for his style it would be a good thing.
The problem here is that Windows has at least 4 ways to enumerate
serial ports, some are bug slow and others don't find everything.
The com0com tool, which I've been using since it was an infant for
testing SONY VTR control software. I've NO idea why the author
does not preselect the "use Port class" checkboxes. But.... It is
nice and it is low overhead and low footprint on your system.
{^_^}
Hi all.
I want to set up a virtual Com-port in Win10 in order to be able to have a PTT-signal going from MSHV (generating FSK441, JT8 etc. signals) to SDR-Console to initiate Tx.
I do not want to use the VOX for switching from Rx to Tx when using an external PA to my Hermes board. BTW PTT via VOX switches OK but I am not positive that the RF is not present when the external TR-relay switches.
I tried com0com but I can not getting it to work in Win10. It installs fine in Win7 but in Win10 the Com-ports does not show up correctly in the Device Manager and can by that not be found by SDRC nor MSHV.
Any suggestions on how to transfer the PTT command from e.g. MSHV to SDRC in Win10?
BTW Does the RF-delay parameter (in the Tx-options) work as expected when using VOX? Will e.g. a 100 ms FR-delay, be 100 ms after the PTT-signal from SDRC to the Hermes-board before RF is present?
73 / Ingolf, SM6FHZ
(This didn't seem to make it the first time. So I am trying again.)
Go to startup->com0com->setupg.com
Create a COMn pair. Make sure "use Ports class" is checked on both sides.
Bob's your uncle. (I've never found a used for ports without
those two checkboxes checked.)
{^_^}
Hi all.
I want to set up a virtual Com-port in Win10 in order to be able to have a PTT-signal going from MSHV (generating FSK441, JT8 etc. signals) to SDR-Console to initiate Tx.
I do not want to use the VOX for switching from Rx to Tx when using an external PA to my Hermes board. BTW PTT via VOX switches OK but I am not positive that the RF is not present when the external TR-relay switches.
I tried com0com but I can not getting it to work in Win10. It installs fine in Win7 but in Win10 the Com-ports does not show up correctly in the Device Manager and can by that not be found by SDRC nor MSHV.
Any suggestions on how to transfer the PTT command from e.g. MSHV to SDRC in Win10?
BTW Does the RF-delay parameter (in the Tx-options) work as expected when using VOX? Will e.g. a 100 ms FR-delay, be 100 ms after the PTT-signal from SDRC to the Hermes-board before RF is present?
73 / Ingolf, SM6FHZ
One more question.
Maybe Max has the answer to this one.
Is there a way to save the port set-up you have made with VSPM?
You have to run VSPM each time when you start your computer to define the virtual COM-ports, but VSPM does not remember the previous set-up
There's something not right here Ingolf. I only run VspMgr when I need to add ports. Thereafter, the ports should always be there in the Windows Device Manager. You should not need to be running it to add the ports back each time. I'm not sure what's going on there?
Also, I checked and I don't have either of those tick boxes ticked to get it to work. Joanne does not seem to have "Emulate Baud Rate" ticked in Com0Com but reminds me of those two other boxes that need ticking in Com0Com (see her post). Maybe try Com0Com again with Joanne's advice?
FWIW, about a week ago I was trying to monitor COM CAT commands and installed a number of different so-called Com port monitors in the effort. Eventually I realised one of them had totally damaged my Com ports to the extent that I could not get them working again and in the end luckily I noted that Windows had created a Restore Point about a week before (not by any action I had taken). I rolled back and they all came back again. Phew!
My point is, I wonder if something in your Com ports setup in Windows has become corrupted? It does not seem to be behaving itself normally regarding installing these virtual com ports. Once you have installed them you should not need to run those progs (VSP or Com0Com) to do it again until you come to need another pair.
Also, just for info, here's what the Com ports look lie in my Device Manager:
73
Max
Do you run VSPM as Administrator?
Need help with SDR Console? If you have a problem:
Go to https://www.sdr-radio.com/support
Please follow instructions in that link.
===================================
Jim, Bournemouth, Dorset. IO90BR.
Elad FDM-S2, Airspy HF+, SDRPlay and Funcube Dongle SDR Recievers
8-element OP-DES for Band 2, 8-element LFA for 2m, 3-element LFA for 6m, 20m Windom for HF,. Wellbrook 1530 Loop for LF
One more question.
Maybe Max has the answer to this one.
Is there a way to save the port set-up you have made with VSPM?
You have to run VSPM each time when you start your computer to define the virtual COM-ports, but VSPM does not remember the previous set-up so you have to do the full procedure each time you boot the PC.
Is there a way to do this a bit smarter?
Also I have noticed, you have to run VSPM first ting, then open SDRC, MSHV etc that uses the virtual COM-ports. Not a surprise, but you have to remember it at each boot.
73 / Ingolf, SM6FHZ
Thanks for all information and hints !
This is truly a well of immense knowledge.
By some form of magic, the by VSPM created virtual COM-ports has glued themselves to the list of COM-port in the Device manager over night.
In spite of several re-boots last night without staying there, they were there this morning.
I have no idea what I might have done differently.
At first they showed up under a separate label (ELTIMA Virtual...), rather than under "COM-ports", but this morning they were under the expected label in the Device Manager.
Windows magic, far beyond my horizon :-)
No everything seems to be OK.
I hope others might benefit from this discussion as well.
73 / Ingolf, SM6FHZ
By some form of magic, the by VSPM created virtual COM-ports has glued themselves to the list of COM-port in the Device manager over night.Glad it's all sorted now Ingolf. Out of interest, in Device Manager, do yours show up in the COM ports list like the screengrab I sent in m last post, that is, I seem to have an entry for pair in both directions, so 9>10 and 10>9 (if you look at picture in last post you will see what I mean). In the past on Windows 10 (I'm now on WIn11) I'm sure I had just COM9, COM10 etc, although TBH if it worked I probably didn't analyse it that much so maybe they did. Just interested for future ref.
73
Max
https://freevirtualserialports.com/
https://freeserialportsplitter.com/
all two are freeware
73