I am a registered user and have the lastest version of VirtualVP. When I run VirtualVP I set the COM port for the physical station to COM-1. And I set Virtual Port 1 to COM6. It showed that it was communicating with the station. And, both the physical port and virtual port had green bars indicating communication. But when I tried to set WeatherLink’s software to COM6, it repeatedly reported that COM6 was already open. When I changed it to another, intentionally incorrect port, it would have a long delay and report that it timed out listening to the port. Any ideas why it thinks the port is already open? I tried using a number of pairs of ports, all with the same results of “port is already open.”
It’s a bit of a strange thing to set up, but if you’re using N8VBvCOM driver,
for virtual serial ports, it defines what the logical port connections are:
N8VBvcom on my system connects
com5 to com15
com6 to com16
com7 to com17
com8 to com18
I use Virtual VP to connect on COM2 (but your com1 connection is also ok) to the VP Console itself. VirtualVP then has defined:
WeatherLink on COM15
WeatherDisplay on COM16
VPLive on COM17
The individual software packages are configured for:
weatherLink to connect on COM5
WeatherDisplay on COM6
VPLive on COM7
VirtualVP talks to the high numbered port of a port pair offered by N8VBvCON and the weather software talks to the low numbered port of the pair.