Multiple COM ports not displayed next to the device name on Windows client

Submitted by apchandr on #1

Hello,

I am trying to connect a TI IWR6843ISK board using the VirtualHere client (v5.6.1) on Windows. When the board is connected, 2 UART ports are displayed on the device manager as a Virtual COM Ports (enhanced COM port and the standard COM port). However, only one COM port appears beside the device name in the VirtualHere client and in the API output. Can you please help?

Refer v5.2.5 changes, https://www.virtualhere.com/node/955#:~:text=5.2.5%20(14th%20Dec%202021)

Submitted by Michael on Sat, 2024/04/27 - 07:39

#2

Actually this is expected, at the moment the virtualhere client will display just one com port per USB device. The COM port(s) are still passed through correctly (check Windows Device Manager) but only one will show in the client next to the device.

Submitted by apchandr on Mon, 2024/04/29 - 23:17

#3

Thank you for the quick response! Do you have any plans to modify this? Currently, We are using VirtualHere client output to parse COM ports. It will be really helpful if ports can match with Device Manager.

Submitted by Michael on Tue, 2024/04/30 - 08:26

#4

OK let me see what i can do now... it might be an easy change..

Submitted by apchandr on Wed, 2024/05/01 - 02:29

#5

Ok, thanks. 

Submitted by Michael on Wed, 2024/05/01 - 10:26

#6

Download and run this beta build, (ill roll these changes into the main version)

Submitted by apchandr on Wed, 2024/05/01 - 23:00

#7

Thanks, Michael. I see multiple ports listed now in client and API. However, within the GUI, I notice that ports continue to accumulate each time I connect, disconnect, and then reconnect (same for devices with single COM port as well).

For example:

## Multiple COM port device:

After 1st time use,

 --> (COM3,COM4) tiiwr6843iskusb (myserverglnxa64.11) (In-use by you)

After 2nd time use,
--> (COM3,COM4,COM3,COM4) tiiwr6843iskusb (myserverglnxa64.11) (In-use by you)

After 3rd time use,
--> (COM3,COM4,COM3,COM4,COM3,COM4) tiiwr6843iskusb (myserverglnxa64.11) (In-use by you)

 

## One COM port device:

After 1st time use,

 --> (COM6) RS232loopbackUSB1 (myserverglnxa64.12) (In-use by you)

After 2nd time use,
--> (COM6,COM6) RS232loopbackUSB1 (myserverglnxa64.12) (In-use by you)

...

 

Submitted by Michael on Thu, 2024/05/02 - 09:18

#8

Sorry i see the bug, download again from that link above and test this new version

 

Submitted by Michael on Thu, 2024/05/09 - 09:23

#11

Sure, this is now in version 5.6.2 of the client available now on this website.

Submitted by apchandr on Tue, 2024/05/21 - 11:36

#12

Hi Michael,

On Linux when using client API, i see only (/dev/ttyACM) ports displayed next to the device but doesn't display (/dev/ttyUSB) ports. Is this expected?

For example: When using Arduino Uno/Due and USB serial loopback device,

$ /usr/sbin/vhclientx86_64 -t "LIST"
VirtualHere Client IPC, below are the available devices:
(Value in brackets = address, * = Auto-Use)

myserver-01(myserver-01:7575) 

 --> (/dev/ttyACM0) Arduino Due Prog. Port (myserver-01.123) (In-use by you)

 --> RS232loopback (myserver-01.456) (In-use by you)


Auto-Find currently on
Auto-Use All currently off
Reverse Lookup currently off
Reverse SSL Lookup currently off
VirtualHere Client is running as a service

###

$ ls /dev/ttyUSB*
/dev/ttyUSB0

$ ls /dev/ttyACM*
/dev/ttyACM0

 

Submitted by Michael on Tue, 2024/05/21 - 12:40

#13

Yes that is expected, virtualhere will list the ACM devices rather than the ttyUSB. They are the same device just represented with a different driver. ACM is standardized, whereas ttyUSB is not.