Re: Eltima Virtual Serial Port Driver 7.2 Registration 101
Eliane Lebouf
Serial Port is a serial communication interface that has been the backbone of industrial data transfer and even embedded computers (MCUs, SBC, SoC and Others) still provide support for it in one way or the other way. Although you might not be seeing the traditional RS-232 serial port again, the serial port still get used along with USB to Serial converters using things like FTDI chip.
Virtual serial ports are great when access to serial ports is not available, and a software application needs a connection to a serial device but cannot connect to it due to a physical lack of serial ports. Here, the computer will be reconfigured to send serial port data over LAN (local area network) or some other interface and then send data back to itself. This is basically is a virtual serial port. So how do you create one? Use a virtual serial port software, they are several of them and the Virtual COM Port Driver from Eltima is one I have tried out that seems interesting.
The Virtual COM Port Driver allows anyone to create virtual serial ports and connect them via a virtual null modern cable. The serial port emulator by Etima seems to emulate a serial port behavior quite well if not entirely. The software provides flexible port creation, management, and removal of ports. With it, applications can exchange data on the virtual ports and this is a great way of testing embedded system communication without necessary having the device physically available .
All these features combined make the Virtual COM Port Driver a compelling software for serial ports manipulation but what about the price tag? I must say the price tag is high, especially for someone looking for some virtual ports to play around but still, it provides functionality beyond what you will ever get from free software.
The Virtual COM port driver is great for industries and bushiness applications and especially if you work with a lot of legacy tools, it might as well be better off than free tools but if you do basic serial port stuff it might just be overkill.
Hi, I'm software, a hardware guy, and a technical writer. Have had a stint with the EdTech industries, but mostly interested in the space of deploying AI for edge computing. Otherwise, I am writing or coding about some technology pieces covering IoT, GPU computing, LoraWAN, PCB, Machine Learning, Precision Agriculture, Open Electronics, and related fields. Got a tip, freebies, launch, gig or leak? Contact me on Twitter, or via email: charlesayibiowuAThotmail.com. I don't bite.
Hello,
Could you try connecting the wires like what is shown in this link:
File:Straight crossed rs232 cable pinout v2.png - Teltonika Networks Wiki (teltonika-networks.com)
Regarding the usage of virtual serial port drivers, we don't have data about this. But usually, the connection scheme that we are using is the one found in the link above.
Regards,
In this article, we will investigate how various Contest programs (Win-Test, N1MM, and CW-Skimmer) communicate with the FT1000MP shortwave transceiver over the serial port. We will see what happens when multiple programs try to talk to the transceiver at the same time, what problems appear and how we can successfully monitor and debug them.
A couple of weeks ago I modified my Yaesu FT1000MP short wave transceiver to be able to use it with an external software defined radio (SDR). For decoding morse code (CW), Alex Shovkoplyas, VE3NEA wrote the neat software CW-Skimmer which can decode up to 700 CW stations in conjunction with a wideband receiver.
But nobody is wondering, that in the golden days of Computer Virtualization also virtual COM-Port drivers became available. Several companies offer a variety of virtual COM port/splitter/router applications. This is a list of the ones I found:
Tracing the connection with N1MM and CW-Skimmer (modified communication pattern) shows better answers. At least there seem to be no more clashed packages. Please note that FT1000MP seems to respond by repeating twice the requested information. Luckily, both applications can handle this without any problem.
We have seen how it is possible to analyze and investigate a problem. In detail, we have investigated the behavior of various programs with a non-standard configuration by allowing these programs to talk simultaneously over the same serial port with an HF transceiver. By using serial analyzing software we found out that there is indeed a difference in how to obtain the same data from the transceiver. In the end, we finally verified how an optimum data request should look in a virtual com port environment.
External equipment legacy software requires two free serial ports (COMx & COMy) in your PC (or two virtual ports) for serial-port communications. See www.eltima.com or com0com.sourceforge.net for virtual port drivers for your PC.
As shown in Figure 40 above, DavLink re-routes legacy software communications through the communication channel it uses to communicate with the Davicom. This channel could be another COM port, a modem or TCP/IP link.
To set up the COMx serial port in your computer, go to the DavLink Setup menu, select Communications and in the Reach-Through Communications section, select the computer COM port that DavLink will use to connect with the external equipment legacy software. In the image below, COMx has been set to COM5 as an example.
Note: When communicating through a modem, as soon as the communications port is released, the modem will hang up at the DTR drop. To make the modem insensitive to the DTR, use the AT command: AT &D0.
Configure your external equipment legacy software to use a second COM port in the computer, i.e. COMy in image below. As an example, if the legacy software is HyperTerminal, COM3 will be set as follows:
Important: Users must ensure that every COM port is assigned a different Interrupt Request (IRQ) number. Otherwise, communications with external equipment will not work. To validate your IRQ settings using Windows XP, right-click the My Computer icon, select Properties, then the Hardware tab and click the Device Manager button. Look for ports, double-click the COM port (COMx, then COMy), select the Resources tab and verify the IRQ assigned to the port. If both COMx and COMy have the same IRQ number, we recommend you try a different COM port combination instead of changing the IRQ assignment.
To configure a specific reach-through serial port, select the port # (click the number) in the upper section of the dialog box set the following parameters in the lower part and then click Change.
Default Description: Long Unicode description for each of the Davicom reach-through serial ports. The description should include the external equipment to which the port is connected. (Maximum 30 alphanumerical Unicode characters). Refer to this article for more details.
Alternate Description: Short ASCII description for each of the Davicom reach-through serial ports. The description should include the external equipment to which the port is connected. (Maximum 18 alphanumerical ASCII characters).
Disable IP Encryption in MIP: Check this box to disable packet encryption during reach-through serial communications. This prevents data padding, normally used for data encryption, from adding unwanted delays that can hinder reach-through communications.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
Installation of DavLink 5.56.29025 requires a Microsoft Visual C++ 2010 Redistributable x86 32 bit package. If your PC does not already have it, you can get it below, or from Microsoft. Note that it is required to use the 32-bit version of the package even if the PC is running a 64-bit version of Windows, and it must also be installed before installing DavLink.
Installation of DavLink 6 requires a Microsoft Visual C++ 2010 Redistributable x86 32 bit package. If your PC does not already have it, you can get it below, or from Microsoft. Note that it is required to use the 32-bit version of the package even if the PC is running a 64-bit version of Windows, and it must also be installed before installing DavLink.
It is a simple kernel module - a small source file. I don't know why it only got thumbs down on sourceforge, but it works well for me. The best thing about it is that is also emulates the hardware pins (RTC/CTS DSR/DTR). It even implements TIOCMGET/TIOCMSET and TIOCMIWAIT iotcl commands!
When the module is loaded, it creates 4 pairs of serial ports. The devices are /dev/tnt0 to /dev/tnt7 where tnt0 is connected to tnt1, tnt2 is connected to tnt3, etc.You may need to fix the file permissions to be able to use the devices.
I guess I was a little quick with my enthusiasm. While the driver looks promising, it seems unstable. I don't know for sure but I think it crashed a machine in the office I was working on from home. I can't check until I'm back in the office on monday.
The second thing is that TIOCMIWAIT does not work. The code seems to be copied from some "tiny tty" example code. The handling of TIOCMIWAIT seems in place, but it never wakes up because the corresponding call to wake_up_interruptible() is missing.
I spent yesterday and today rewriting the driver. There were a lot of issues, but now it works well for me. There's still code missing for hardware flow control managed by the driver, but I don't need it because I'll be managing the pins myself using TIOCMGET/TIOCMSET/TIOCMIWAIT from user mode code.
7fc3f7cf58