The Null-modem emulator can be used to provide serial interface for COM port redirectors.For example, with the com2tcp (COM port to TCP redirector,part of the com0com project ) you can communicate via serial interface with the TCP/IP servers.If you feel that com2tcp is what you need but can't find some required features (for example RFC 2217 support) then try use hub4com instead.
With the hub4com (HUB for communications,part of the com0com project ) it is possible to handle data and signals from a single serial device by a number of differentapplications (for example, several applications can share data from one GPS device).It's also possible to use the real serial ports of remote computer like if they exist on a local computer.
In case anyone is referencing this, and interested in this topic, the 2.2.2.0 version of com0com is signed for 64-bit Windows. This removes the need to jump through the hoops of putting Windows in "test" mode.
What worked for me was running shutdown /r /o /t 00 as admin, then selecting Troubleshoot, then Advanced options, then Startup Settings. Click the Restart button to restart and enter the Startup Settings menu, then select option #7 (Disable driver signature enforcement). After restarting, Windows should now allow installation of the com0com drivers (though it shows big warning messages that the drivers are untrusted).
If this describes the thing you face then you would have to look into com0com as mentioned already. This software lets you create two virtual virtual COM ports that are connected together through the com0com driver. Your LabVIEW opens the USB virtual COM port AND one of the com0com virtual ports and translates the data between the two as needed. Your app connects to the other com0com virtual port instead of the USB virtual port and sees whatever your LabVIEW writes into the other side of the com0com link and anything that it sends will then be read by LabVIEW.
It's got a free demo you can use. It makes two COM ports that loop to each other and will be totally transparent to your computer. Your program than then read the actual device on a real COM port then shoot the sanitized data out the mirrored port. com0com may work too but I haven't tried that one myself.
Most commercial tools providing this feature are more or less based on the com0com code or its predecessor but cleaned up, with neat installers and scripts that make everything work more smoothly on different Windows versions, including newer ones.
2) COM0COM is shown as not working in the Windows Device Manager or the ports do not show up in Win4Icom.
If you have installed com0com version 3, then the com0com install program will not work with current Windows 10 and 11. However com0com version 2 does. The issue is, to install version 2 after you have installed version 3, you must uninstall version 3 the right way.
Use the com0com port emulator only if there is not already a com1 port present on the rmserver and you cannot install a hardware com port n the rmserver. The com0com null-modem emulator is an open source kernel-mode virtual serial port driver for Windows and is available freely under GPL license. You can create an unlimited number of virtual COM port pairs and use any pair to connect one application to another. Each COM port pair provides two COM ports with default names starting at CNCA0 and CNCB0. The output to one port is the input from the other port and vice versa. Usually one port of the pair is used by a Windows application that requires a COM port to communicate with a device. In the case of Vantiv Integrated Payments we will need only 1 port but because com0com installs two by default, you will have to configure both.
Some quick googling revealed com0com/com2tcp and socat should accomplish just that on Windows and Linux, respectively. It wasn't immediately obvious to me how to set up com0com so I made a detour over this other program also called COM2TCP. It was really easy to set up and worked right out of the box but unfortunately free usage is limited to 45 days so I went back and decided to figure out com0com.
As I've mentioned, it's hard to come by a PC with real COM ports these days. Although there are many USB to RS-232 adapters on the market, the simplest thing to do if all you have is a single computer is installing an emulator. One that I recommend is called com0com. It is simple to install and works pretty well.
So, download com0com and follow the installation instructions carefully to create two virtual COM ports which are connected to each other. For me com0com created ports named CNCA0 and CNCB0 - in future versions the names may be different, but it really doesn't matter.
Make sure to read the Q&A section in the README file of com0com. For instance, I had turned on buffer overrun emulation because I didn't want the sender to hang when no receiver is connected at the paired port.
I have been using HW Group's single virtual serial port software. It works well but only creates 1 vert serial port; they do have software that creates up to 255 vert serial ports, but you have to purchase their hardware for that software. I also tried com0com, but never was able to get it running on my Windows 10 machine. Thanks for your input.
The last com0com driver version signed available on SourceForge is the 2.2.2.0. A signed version of the latest com0com driver version 3.0.0.0 can be found at powersdr-iq/downloads (files: setup_com0com_W7_x86_signed.exe and setup_com0com_W7_x64_signed.exe).
com0com only create serial port pairs. You need another software to tunnel them over TCP/IP. The only free I've found is from commfront a hardware manufacturer who does not mind sharing the software for personal use.
giorgio, great to hear that you were able to connect with com0com. Did you have to disable any features under Windows (I'm assuming you are using Win 10)? With ASCOM driver connected to the com3 and the the com/tcp command using com4, which is the outgoing port and which is the incoming port?
Com0com does not allow multiple applications use of a single comm port, it creates virtual comm ports between applications. If I want program A and program B to BOTH share Comm 4, com0com will NOT do that. I know, I use com0com to connect 2 programs serially together for Air Force MARS programs.
The best way to approach configure this is to start with Win4Yaesu out of the picture. Connect directly to the radio and once you everything is working correctly, then just change the Serial port definition to correspond with the com0com pair as shown in the concept section. One can use Omni-rig as the rig or the actual HamLib rig configuration. As of the current update (July 2021), HamLib seems to finally work correctly.
There seems to be an issue with the most recent com0com v3.0.0.0 signed installer on Windows 10 or Windows 11.
Existing installations will continue to work, but new installations are not possible any more.
As a workaround, you can use the older V2.2.2.0 signed installer available on the com0com project website. We could successfully
install and use this version on Windows 10 and Windows 11 computers in 2022/08.
The Null-modem emulator (com0com) is a kernel-mode virtual serial port driver for Windows. You can create an unlimited number of virtual COM port pairs and use any pair to connect one COM port based application to another. The HUB for communications (hub4com) allows to receive data and signals from one COM or TCP port, modify and send it to a number of other COM or TCP ports and vice versa.
I used the following command in a WDK terminal on Win 7, "signtool sign /v /f myOwnCertificate.pfx /t " " ..\amd64\com0com.sys"
that command I found it in the official documentation of Microsoft, I do not know if you have other info about or where can I find it?
In the com0com setup tool on the Windows PC configure a Virtual Port Pair like this - make sure to tick "use Ports class" on the local com port, otherwise VEConfig won't detect the port. A reboot might be needed after you have configured the port pair:
com0com is a nice Windows tool to create virtual serial ports and to connect them together, simulating a cable link. It is then possible to run two programs, connected to the two virtual serial ports, that communicate with each other. You can develop your graphical user interface on one side, and a model of the device on the other side.
From this starting point, you can develop your own solution. Keep in mind that the behavior of this serial port emulation could differ from the behavior of the physical device you will attach because com0com does not emulate (for example) power problems, signal attenuation, interference and so on.
df19127ead