How to Test Connection?

Hello Everyone,

I am having problems connecting.

My Setup
Server: COM->USB->Raspberry Pi 4 [ VHServer WORKS ]
Client: Win 10 64bit ->Virtual USB (COM1) [ VHClient WORKS ]

Server RPi4
# lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port <----- 1st Connected Device Bus 001 Device 005: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port <----- 2nd Connected Device Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

# dmesg [90842.855426] usb 1-1.2: new full-speed USB device number 6 using xhci_hcd [90842.991445] usb 1-1.2: New USB device found, idVendor=067b, idProduct=2303, bcdDevice= 3.00 [90842.991464] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [90842.991508] usb 1-1.2: Product: USB-Serial Controller [90842.991524] usb 1-1.2: Manufacturer: Prolific Technology Inc. [90843.105646] usb 1-1.2: reset full-speed USB device number 6 using xhci_hcd

# ls /dev/ drwxrwxrwt 2 root root 40 Dec 31 1969 mqueue drwxr-xr-x 2 root root 60 Dec 31 1969 raw drwxr-xr-x 2 root root 80 Dec 31 1969 dma_heap drwxr-xr-x 3 root root 60 Dec 31 1969 bus drwxr-xr-x 2 root root 60 Dec 31 1969 input drwxrwxrwt 2 root root 40 Feb 14 2019 shm drwxr-xr-x 2 root root 0 Feb 14 2019 pts lrwxrwxrwx 1 root root 15 Feb 14 2019 stdout -> /proc/self/fd/1 lrwxrwxrwx 1 root root 15 Feb 14 2019 stdin -> /proc/self/fd/0 lrwxrwxrwx 1 root root 15 Feb 14 2019 stderr -> /proc/self/fd/2 lrwxrwxrwx 1 root root 13 Feb 14 2019 fd -> /proc/self/fd lrwxrwxrwx 1 root root 28 Feb 14 2019 log -> /run/systemd/journal/dev-log lrwxrwxrwx 1 root root 12 Feb 14 2019 initctl -> /run/initctl crw------- 1 root root 10, 137 Aug 6 10:17 vhci crw------- 1 root root 10, 223 Aug 6 10:17 uinput crw------- 1 root root 10, 239 Aug 6 10:17 uhid crw------- 1 root root 108, 0 Aug 6 10:17 ppp drwxr-xr-x 2 root root 60 Aug 6 10:17 net drwxr-xr-x 2 root root 60 Aug 6 10:17 mapper crw------- 1 root root 10, 203 Aug 6 10:17 cuse crw------- 1 root root 10, 234 Aug 6 10:17 btrfs-control crw-rw-rw- 1 root root 10, 229 Aug 6 10:17 fuse brw-rw---- 1 root disk 179, 0 Aug 6 10:17 mmcblk0 crw-rw---- 1 root video 243, 0 Aug 6 10:17 vchiq brw-rw---- 1 root disk 179, 2 Aug 6 10:17 mmcblk0p2 drwxr-xr-x 7 root root 140 Aug 6 10:17 disk crw------- 1 root root 10, 130 Aug 6 10:17 watchdog crw------- 1 root root 250, 0 Aug 6 10:17 watchdog0 lrwxrwxrwx 1 root root 7 Aug 6 10:17 serial1 -> ttyAMA0 crw-rw---- 1 root video 247, 0 Aug 6 10:17 vcio crw-rw---- 1 root gpio 246, 0 Aug 6 10:17 gpiomem crw-rw---- 1 root gpio 254, 1 Aug 6 10:17 gpiochip1 crw-rw---- 1 root gpio 254, 0 Aug 6 10:17 gpiochip0 brw-rw---- 1 root disk 7, 0 Aug 6 10:17 loop0 brw-rw---- 1 root disk 1, 10 Aug 6 10:17 ram10 brw-rw---- 1 root disk 7, 3 Aug 6 10:17 loop3 brw-rw---- 1 root disk 7, 2 Aug 6 10:17 loop2 brw-rw---- 1 root disk 1, 13 Aug 6 10:17 ram13 brw-rw---- 1 root disk 1, 12 Aug 6 10:17 ram12 brw-rw---- 1 root disk 7, 6 Aug 6 10:17 loop6 brw-rw---- 1 root disk 7, 4 Aug 6 10:17 loop4 brw-rw---- 1 root disk 1, 4 Aug 6 10:17 ram4 brw-rw---- 1 root disk 1, 15 Aug 6 10:17 ram15 brw-rw---- 1 root disk 1, 11 Aug 6 10:17 ram11 brw-rw---- 1 root disk 1, 0 Aug 6 10:17 ram0 brw-rw---- 1 root disk 7, 7 Aug 6 10:17 loop7 brw-rw---- 1 root disk 7, 5 Aug 6 10:17 loop5 brw-rw---- 1 root disk 7, 1 Aug 6 10:17 loop1 brw-rw---- 1 root disk 1, 9 Aug 6 10:17 ram9 brw-rw---- 1 root disk 1, 8 Aug 6 10:17 ram8 brw-rw---- 1 root disk 1, 5 Aug 6 10:17 ram5 brw-rw---- 1 root disk 1, 2 Aug 6 10:17 ram2 brw-rw---- 1 root disk 1, 14 Aug 6 10:17 ram14 crw-rw-rw- 1 root root 1, 8 Aug 6 10:17 random brw-rw---- 1 root disk 1, 7 Aug 6 10:17 ram7 brw-rw---- 1 root disk 1, 6 Aug 6 10:17 ram6 brw-rw---- 1 root disk 1, 3 Aug 6 10:17 ram3 brw-rw---- 1 root disk 1, 1 Aug 6 10:17 ram1 crw-r--r-- 1 root root 1, 11 Aug 6 10:17 kmsg drwxr-xr-x 2 root root 580 Aug 6 10:17 block crw-rw-rw- 1 root root 1, 3 Aug 6 10:17 null crw------- 1 root root 10, 61 Aug 6 10:17 cpu_dma_latency crw------- 1 root root 10, 62 Aug 6 10:17 cachefiles crw-r--r-- 1 root root 10, 235 Aug 6 10:17 autofs crw-rw-rw- 1 root root 1, 9 Aug 6 10:17 urandom crw-r----- 1 root kmem 1, 1 Aug 6 10:17 mem crw-rw---- 1 root disk 10, 237 Aug 6 10:17 loop-control crw------- 1 root root 10, 183 Aug 6 10:17 hwrng crw-rw-rw- 1 root root 1, 7 Aug 6 10:17 full crw-rw-rw- 1 root root 1, 5 Aug 6 10:17 zero crw--w---- 1 root tty 4, 0 Aug 6 10:17 tty0 crw-rw-rw- 1 root tty 5, 0 Aug 6 10:17 tty crw-r----- 1 root kmem 1, 4 Aug 6 10:17 port crw------- 1 root root 10, 63 Aug 6 10:17 vga_arbiter crw--w---- 1 root tty 4, 12 Aug 6 10:17 tty12 crw--w---- 1 root tty 4, 2 Aug 6 10:17 tty2 crw--w---- 1 root tty 4, 18 Aug 6 10:17 tty18 crw--w---- 1 root tty 4, 17 Aug 6 10:17 tty17 crw--w---- 1 root tty 4, 15 Aug 6 10:17 tty15 crw--w---- 1 root tty 4, 13 Aug 6 10:17 tty13 crw--w---- 1 root tty 4, 11 Aug 6 10:17 tty11 crw--w---- 1 root tty 4, 10 Aug 6 10:17 tty10 crw--w---- 1 root tty 4, 28 Aug 6 10:17 tty28 crw--w---- 1 root tty 4, 26 Aug 6 10:17 tty26 crw--w---- 1 root tty 4, 24 Aug 6 10:17 tty24 crw--w---- 1 root tty 4, 22 Aug 6 10:17 tty22 crw--w---- 1 root tty 4, 21 Aug 6 10:17 tty21 crw--w---- 1 root tty 4, 19 Aug 6 10:17 tty19 crw--w---- 1 root tty 4, 32 Aug 6 10:17 tty32 crw--w---- 1 root tty 4, 30 Aug 6 10:17 tty30 crw--w---- 1 root tty 4, 27 Aug 6 10:17 tty27 crw--w---- 1 root tty 4, 25 Aug 6 10:17 tty25 crw--w---- 1 root tty 4, 23 Aug 6 10:17 tty23 crw--w---- 1 root tty 4, 20 Aug 6 10:17 tty20 crw--w---- 1 root tty 4, 16 Aug 6 10:17 tty16 crw--w---- 1 root tty 4, 14 Aug 6 10:17 tty14 crw--w---- 1 root tty 4, 38 Aug 6 10:17 tty38 crw--w---- 1 root tty 4, 37 Aug 6 10:17 tty37 crw--w---- 1 root tty 4, 35 Aug 6 10:17 tty35 crw--w---- 1 root tty 4, 34 Aug 6 10:17 tty34 crw--w---- 1 root tty 4, 31 Aug 6 10:17 tty31 crw--w---- 1 root tty 4, 3 Aug 6 10:17 tty3 crw--w---- 1 root tty 4, 29 Aug 6 10:17 tty29 crw--w---- 1 root tty 4, 43 Aug 6 10:17 tty43 crw--w---- 1 root tty 4, 42 Aug 6 10:17 tty42 crw--w---- 1 root tty 4, 41 Aug 6 10:17 tty41 crw--w---- 1 root tty 4, 4 Aug 6 10:17 tty4 crw--w---- 1 root tty 4, 39 Aug 6 10:17 tty39 crw--w---- 1 root tty 4, 36 Aug 6 10:17 tty36 crw--w---- 1 root tty 4, 33 Aug 6 10:17 tty33 crw--w---- 1 root tty 4, 50 Aug 6 10:17 tty50 crw--w---- 1 root tty 4, 5 Aug 6 10:17 tty5 crw--w---- 1 root tty 4, 49 Aug 6 10:17 tty49 crw--w---- 1 root tty 4, 48 Aug 6 10:17 tty48 crw--w---- 1 root tty 4, 46 Aug 6 10:17 tty46 crw--w---- 1 root tty 4, 55 Aug 6 10:17 tty55 crw--w---- 1 root tty 4, 53 Aug 6 10:17 tty53 crw--w---- 1 root tty 4, 52 Aug 6 10:17 tty52 crw--w---- 1 root tty 4, 51 Aug 6 10:17 tty51 crw--w---- 1 root tty 4, 47 Aug 6 10:17 tty47 crw--w---- 1 root tty 4, 45 Aug 6 10:17 tty45 crw--w---- 1 root tty 4, 44 Aug 6 10:17 tty44 crw--w---- 1 root tty 4, 40 Aug 6 10:17 tty40 crw-rw---- 1 root tty 7, 0 Aug 6 10:17 vcs crw------- 1 root root 5, 3 Aug 6 10:17 ttyprintk crw--w---- 1 root tty 4, 63 Aug 6 10:17 tty63 crw--w---- 1 root tty 4, 62 Aug 6 10:17 tty62 crw--w---- 1 root tty 4, 6 Aug 6 10:17 tty6 crw--w---- 1 root tty 4, 59 Aug 6 10:17 tty59 crw--w---- 1 root tty 4, 56 Aug 6 10:17 tty56 crw-rw---- 1 root tty 7, 6 Aug 6 10:17 vcs6 crw-rw---- 1 root tty 7, 4 Aug 6 10:17 vcs4 crw-rw---- 1 root tty 7, 3 Aug 6 10:17 vcs3 crw-rw---- 1 root tty 7, 2 Aug 6 10:17 vcs2 crw-rw---- 1 root tty 7, 1 Aug 6 10:17 vcs1 crw--w---- 1 root tty 4, 9 Aug 6 10:17 tty9 crw-rw---- 1 root tty 7, 131 Aug 6 10:17 vcsa3 crw-rw---- 1 root tty 7, 130 Aug 6 10:17 vcsa2 crw-rw---- 1 root tty 7, 128 Aug 6 10:17 vcsa crw------- 1 root root 248, 0 Aug 6 10:17 vc-mem crw--w---- 1 root tty 4, 7 Aug 6 10:17 tty7 crw-rw---- 1 root tty 7, 69 Aug 6 10:17 vcsu5 crw-rw---- 1 root tty 7, 68 Aug 6 10:17 vcsu4 crw-rw---- 1 root tty 7, 66 Aug 6 10:17 vcsu2 crw-rw---- 1 root tty 7, 65 Aug 6 10:17 vcsu1 crw-rw---- 1 root tty 7, 64 Aug 6 10:17 vcsu crw-rw---- 1 root tty 7, 132 Aug 6 10:17 vcsa4 crw-rw---- 1 root tty 7, 129 Aug 6 10:17 vcsa1 crw-rw---- 1 root tty 7, 70 Aug 6 10:17 vcsu6 crw-rw---- 1 root tty 7, 67 Aug 6 10:17 vcsu3 crw-rw---- 1 root tty 7, 133 Aug 6 10:17 vcsa5 crw-rw---- 1 root tty 7, 5 Aug 6 10:17 vcs5 crw--w---- 1 root tty 4, 60 Aug 6 10:17 tty60 crw--w---- 1 root tty 4, 58 Aug 6 10:17 tty58 crw--w---- 1 root tty 4, 57 Aug 6 10:17 tty57 crw--w---- 1 root tty 4, 54 Aug 6 10:17 tty54 crw-rw---- 1 root video 240, 0 Aug 6 10:17 rpivid-intcmem crw--w---- 1 root tty 4, 61 Aug 6 10:17 tty61 crw-rw---- 1 root video 239, 0 Aug 6 10:17 rpivid-h264mem crw-rw---- 1 root tty 7, 134 Aug 6 10:17 vcsa6 crw-rw---- 1 root video 241, 0 Aug 6 10:17 rpivid-hevcmem crw-rw---- 1 root video 238, 0 Aug 6 10:17 rpivid-vp9mem drwxr-xr-x 3 root root 140 Aug 6 10:17 snd crw-rw-r-- 1 root netdev 10, 242 Aug 6 10:17 rfkill drwxr-xr-x 3 root root 120 Aug 6 10:17 dri brw-rw---- 1 root disk 179, 1 Aug 6 10:17 mmcblk0p1 crw-rw---- 1 root dialout 204, 64 Aug 6 10:33 ttyAMA0 crw--w---- 1 root tty 4, 1 Aug 6 10:33 tty1 crw------- 1 root root 5, 1 Aug 6 10:33 console crw-rw---- 1 root tty 7, 72 Aug 7 11:39 vcsu8 crw-rw---- 1 root tty 7, 8 Aug 7 11:39 vcs8 crw-rw---- 1 root tty 7, 136 Aug 7 11:39 vcsa8 crw--w---- 1 root tty 4, 8 Aug 7 11:39 tty8 drwxr-xr-x 2 root root 2740 Aug 7 12:01 char -rw-r--r-- 1 root root 23 Aug 7 12:14 pymx crw-rw-rw- 1 root tty 5, 2 Aug 11 09:57 ptmx

Client Win10
Device manager shows connection from USB->COM1

Problem
The Server and Client are not communicating data.

I am not sure if it is the COM port on the Machine (Server Side) that is failing or something else

Question
How can I TEST COMMUNICATIONS from the USB COM on the Raspberry Pi server TO the Win10 Client?

Tried
Send and echo command from the SERVER like this. But i am unsure of which device connection to use (ttyAMA0 or ptmx?)
echo "TEST DATA" > /dev/ptmx ???

Tried to listen on SERVER with no success
minicom -> /dev/ptmx??? -> bps 115200 8N1

What can I use as a Serial Communication client on the Win10 Machine?

.

Firstly make sure you are not using fake 2303 https://www.trishtech.com/2018/02/how-to-check-if-prolific-usb-to-uart-…

Next just use putty on Windows and connect to com1 and see if it will open ( https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html )

Thanks Michael. I'm gonna

Thanks Michael. I'm gonna check that this morning. (Eastern Time)

Status:

Status:
Prolific Chip tested on USB->Serial Cable and Authenticated
Connect to COM1 via Putty on the Win10 VH Client: Successful (blank screen)

Sending data/ascii chars with minicom fails with the following settings from the RPI4 Server
minicom -> bps 9600 8N1 /dev/serial1 - NO DATA read on Win10 client (putty), but minicom hangs/freezes on RPI4
minicom -> bps 9600 8N1 /dev/ttyAMA0 - NO DATA read onWin10 client (putty), but minicom hangs/freezes on RPI4

Question
How can I send test data from the RPI4 VirtualHere Server?
Do I have the right devices? (/dev/serial1 ??? or /dev/ttyAMA0 sym link from serial1)

.

See Screen Shot on Win10 Client

Raspberry Pi 4 Host /usr/sbin/config.ini

It=1596421845 EasyFindId=QW6ooYbmmJJoUFxx8txxxx EasyFindPin=nnxoy License=100xxxxedd4,0,MCACDjj+Phzhr9+W5foxxxxxxoag== ServerName=PiMedia Hub DeviceNicknames=Huvitz COM1,067b,2303,112

Systemd Service Status

systemctl status virtualhere.service ● virtualhere.service - VirtualHere USB Sharing Loaded: loaded (/etc/systemd/system/virtualhere.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-08-12 16:05:56 EDT; 28min ago Process: 17807 ExecStartPre=/bin/sh -c logger VirtualHere settling...;sleep 1s;logger VirtualHere settled (code=exited, status=0/SUCC Main PID: 17812 (vhusbdarm) Tasks: 18 (limit: 3980) CGroup: /system.slice/virtualhere.service └─17812 /usr/sbin/vhusbdarm Aug 12 16:05:57 eyestyle-valcaron.pimedia.ca root[17811]: VirtualHere settled Aug 12 16:05:57 eyestyle-valcaron.pimedia.ca vhusbdarmpi4[17812]: >>> Starting VirtualHere USB Server v4.2.0 (Built: Jul 27 2020, 11:37 Aug 12 16:05:57 eyestyle-valcaron.pimedia.ca vhusbdarmpi4[17812]: Using configuration /usr/sbin/config.ini Aug 12 16:05:57 eyestyle-valcaron.pimedia.ca vhusbdarmpi4[17812]: Server licensed to=100000003eb5edd4 max_devices=unlimited Aug 12 16:05:57 eyestyle-valcaron.pimedia.ca vhusbdarmpi4[17812]: Using large URB's Aug 12 16:05:57 eyestyle-valcaron.pimedia.ca vhusbdarmpi4[17812]: Listening on all network interfaces at TCP port 7575 Aug 12 16:05:57 eyestyle-valcaron.pimedia.ca vhusbdarmpi4[17812]: Found Full speed device [067b:2303] "Prolific Technology Inc., USB-Se Aug 12 16:05:57 eyestyle-valcaron.pimedia.ca vhusbdarm[17812]: VirtualHere USB Server is running...press CTRL-C to stop Aug 12 16:06:04 eyestyle-valcaron.pimedia.ca vhusbdarmpi4[17812]: 192.168.50.14 connected as connection 1 Aug 12 16:06:04 eyestyle-valcaron.pimedia.ca vhusbdarmpi4[17812]: Device 112 [067b:2303] BOUND to connection 1

Putty Connection on COM1 on Win10 VH Client shows NO DATA after RPi4 attached device data transmission

Question
How can I send test data from the Server USB to the Client COM1 (USB) to test that thge conneciton is working fine?

.

OK i think i see the problem. You are trying to open /dev/serial1 on the pi while simultaneously using the serial device remotely via virtualhere.

That is impossible , once the serial device is used by the virtualhere client it is not available on the server locally.

If you want to send serial data from the pi at the same time as using the prolific adapter you will need to wire some UART pins from the pi header to the tx/rx/gnd of the prolific adapter. Then open the pi UART and write to that and it will then appear on the remote client when you use the prolific chip via virtualhere

.

Thank you.

Test with only ONE device
Client connected with PUTTY only on COM1 : NO DATA Transmitted from Server

Question
Is it possible to specify NULL MODEM cable on the server/client side for the Serial to USB connection?

.

I ordered Null Modem adapters from Amazon... I will let you know how those tests go.

Thanks again for all your help Michael