Virtual COM port (VCP) drivers cause the USB device to appear as an additional COM port available to the PC. Application software can access the USB device in the This page contains the VCP drivers currently available for FTDI devices.
Eltima Virtual Serial Port Driver Registration 17
Virtual COM port (VCP) drivers cause the USB device to appear as an additional COM port available to the PC. Application software can access the USB device in the same way as it would access a standard COM port.
COM Port Data Emulator is a software application that enables users to emulate an entity, such as an Ethernet device or COM port, that transmits data as a serial stream. The program takes the data stream and converts it to data packets using serial protocols like RS232, TCP/IP or UDP. Then it forwards the packets over the network.
This serial port emulator can randomly generate test data or read it from text or binary files. The data can then be sent to test a port as many times as necessary to achieve the desired results. The app can fill the role of a server or client over an IP-based network. It supports full-duplex mode as well as flow control for serial and RS232 ports.
You can perform serial port emulation with any serial devices that use the RS232/RS485/RS422 protocols. This includes a wide range of industrial controllers and monitoring devices. You can even use z-modem cables and emulate serial data transmission to another computer.
Many of the computers that manufactured today are not equipped with any serial ports at all. Some machines take it a step further and do not have ports of any type, relying on wireless connectivity to peripheral devices.
The reduction in reliance on COM ports in machines and devices used for general purposes has not eliminated the requirement for serial connectivity. Many special-purpose devices still make use of serial interfaces to communicate with computers. Some examples are industrial automation monitoring devices, medical monitoring equipment, and specialized laboratory equipment.
If you have a serial monitoring device in an industrial production facility, it may be transmitting data used as input for several different applications. Creating virtual serial ports from a single port lets all of your applications receive their data at the same time.
So on these occasions, the best choice is virtual serial port emulator software. A benefit of a paid solution is that you receive regular program updates and customer support for your money. This can be a determining factor if you are doing serious development and want the most up-to-date null-modem emulator application available.
These are just a few ways that virtual ports can be used. If you work with serial devices or applications, a serial port emulator like Virtual Serial Port Driver can be an essential component of your software toolbox.
NexRemote connects to my CGEM but that is it. Every time I start NR I get the ActiveX virtual port warning. This is the same issue reported in previous posts. I was hopeful that previously solutions of running in Win7 compatibility mode would work. But that does not seem to be the case.
I have Win10 Home 20H2. NexRemote 1.7.24. Installed latest Celestron unified ASCOM driver 6.1.7350. My old laptop is running Win7, NexRemote 1.7.23 and has no problems with the virtual port. No matter what I do, starting NexRemote always prompts me with the ActiveX warning.1. Tried running NR 1.7.24 in Win7 compatibility mode2. Uninstall, reinstall, run in compatibility mode3. Uninstall, install NR 1.7.23, run in compatibility mode4. Install TrippLite/Keyspan drivers
The one thing I see is that most of the earlier comments and resolutions were running earlier Win 10 versions. I also see that Win10 is now at 21H1 (May 2021). I will try updating Win10 but I seriously doubt that will change anything. It seems that perhaps MS has permanently closed the ActiveX virtual com port door.
I took both my Win10 Home and Win7 Home laptops with me. I had CPWI installed on both. I also downloaded two different virtual serial port programs. One from HHD Software and the one from Eltima Software that the initial warning links to.
I verified than NexRemote was indeed set for Win7 compatibility. I tried run NR and got the expected warning. Continued with just the real COM5 port, it connected with mount. Communication verified. Next tried CPWI, really don't want to use it but this "seems" like the easy way out. Tried connecting via USB, no connection, huh? Went to house and dug up the old hand controller (it is older NexStar+ with RJ11 connector), tried connecting via hand controller, no connection. There was a CFM bootloader message on the HC. Went back to NR using the HC. Got the expected warning but at least it connected. So on the Win10 laptop I am able to connect to the CGEM with NexRemote but I am never able to get past the virtual com port warning so I can't connect the mount to APT and PHD2 via ASCOM.
Tried the virtual serial port programs. The one from HHD is *WORTHLESS*, it was free but totally non-usable. Every time I clicked on something there was a message that basically said "that option is not supported in the free version, please purchase full program". It's not possible to evaluate the functionality of the program and I'm not about to pay for something that is unknown if it will work. Next tried the Eltima software. This was a fully functioning program with 14 day trial. I tried every single possible combination then had, nothing worked. Once I created a bundle with COM5 and COM15 (the virtual port I wanted to use in NR) the virtual port COM15 was never available in the dropdown list in NR for the virtual com port. I sent a support request to Eltima. I'm glad they have an actual fully functioning program for trial. It's looking more and more like I'm going to wind up needing a solution that is likely to cost money, so I'd pay the price if I knew it worked.
I'm a bit confused by "Went back to the USB programming cable that I made, this has worked flawlessly with NexRemote since I made it two years ago. It is a very neat installation and eliminates the HC, Keyspan USB-Serial and cables." What, exactly, does that cable involve? Is it a USB-to-serial converter with TTL buffer circuit hard wired to an RJ connector that plugs into an Aux port to talk directly on the communication bus?
I have no idea what the Virtual Serial Port ActiveX Control is or where that message is is originating. Is that part of NR? It's still on my old laptop (I think...) and I think it did offer a virtual serial port so that others apps could connect to it, but I never really used that and I haven't even started it in the better part of a decade. Windows 10 is much pickier about comms hardware (and software emulation of) for security reasons, so it wouldn't surprise me if some formerly-handy feature like that no longer works, by design.
The problem is, that NexRemote uses the virtual port to connect to ASCOM and other programs like Stellarium. Without the ability to connect with ASCOM, I can't do guiding and scope control/goto with APT.
I'm currently using a Pegasus Ultimate Power Box (original version). I chose the UPB because in addition a USB hub and power distribution it also had the focus motor controller built into the UPB. Prior to the UPB I was using generic USB hub and my own power distribution. I'm on a pier mounted observatory, +/-300ft from my house, wifi doesn't quite reach. I really don't need the wifi so the UPB option is better than using one of the mini/stick PC's. But even so, any mini/stick PC you would find today would only have Win10 installed so I'd be right back to the issue of needed the virtual com port. I suppose I could move away from ASCOM but that is one aspect that has never given me any problems...the problems have always been getting new hardware (on in this case new OS) to communicate with ASCOM. Everything else I have, ASI2600MC-pro main imaging camera, ZWO EFW, Pegasus focus motor, Pegasus UPB and ASI120MM-mini guide cam all successfully connect to ASCOM. If NexRemote would connect via virtual port like it is supposed to I'd back imaging.
I had the same issues with Win7 communicating too. Typically it is not necessary to configure the port for data rate, the OS typically figures it out. But it is something that I did not do so I'll give it a try. You are correct, is should be 19200 bps. Per my comments to rboe, I really can't ignore the virtual port. The virtual port is how NewRemote connects to ASCOM and any other outside devices. The PC port is only for connecting NexRemote to the CGEM. But setting the COM5 port to 19200 bps could very well be the issue with not connecting to CPWI. I took the main control board and the USB programming cable off the CGEM into the house. If I can get a connection to CPWI on the workbench, than it should work on the mount too. With the motors not connected I might get the dreaded "no response" error codes but it would be expected as the motors are, at this point, not connected.
I can understand preferring a more elegant solution than CPWI, but at the end of the day, does it really matter whether CPWI is "bloated" or not? I'm afraid you may just be SOL trying to get NR's virtual port to work, and CPWI provides an ASCOM driver for connectivity with other software, so it may be time to move on.
@Mark, I did some more testing yesterday and found that my programming cable works with NexRemote on both Win7 and Win10 laptops. The issue is not being able to select a virtual com port. As Noah4x4 pointed out, Win10 is not natively supporting serial/RS232 so even with the most most recent FTDI drivers, it's looking like the NR option is going to be dead. I also confirmed that the kluge of works using NexRemote but I get the CFM Bootloader message when trying to run CWPI on either machine. I'm getting ready to have a quick go at running the CFM and updating the HC as needed.
MOD_RSSIM is a Windows-based Modbus PLC Simulator (and basis of ModRSsim2 above). It is free and open-source, and started as a test program for a SCADA/HMI with Modbus RTU and TCP/IP. Typical uses are to verify device configuration, support development of Modbus master and slave drivers for embedded and desktop platforms, and as an educational tool to learn Modbus protocols. 2ff7e9595c
Comments