Open Bunbury-Berlin opened 4 years ago
I use HW virtual Serial Port 3.1.2 and it works on Win 10
Thanks for your reply, but HW Virtual Serial Ports generate their own device class and will not be listed at standard "Ports (COM & LPT)" at the device manager, right?
So I can access the generated vCOM unsing Putty and it's working well, but Putty would have served for Telnet too, without the need of a VSP. Since it is not listed as available standard Com Port (as other VSPs like FTDI do) I can not select it in my legacy app.
But I'm wondering if I'm the only one who just wants to replace a existing COM-cable by an ESP-link solution, still using obsolete but well working PC software. I expected to find several well proven and tested open source projects for virtual COM-Ports via TCP/Telnet (adapting RFC2217 or similar) but I didn't. In most cases, my horrible lack of Internet-searching skills is the reason, so I still need help.
I used the Software with Standard Com port and ESP-Link
Thanks,
that's interesting:
...looks like new problems on my side...
Which Bluetooth serial devices you use ? Im looking for a device which allows to connect to a bluetooth car diagnostic ELM plug via Wlan / ESP-Link device to connect my EV to my network
Fixed the HW-Driver-Problem by modifying the driver install .inf so windows installer assigned device standard class "Port" instead of creating its own class.
But instead of this freeware workaround (which only supports one chanel at a time) it would be interesting to know if there are other (open source) solutions.
@roesl: client HC5 BT-board broadcast its services and almost any PC BT adapter will generate VSPs automatically
An alternative solution for this is virtualbox. You can install a virtual machine and create a comport that link through tcp, with build in settings available .
Nice catch, do you know from what version it is available?
I am using windows XP on a Virtualbox 6.1. After that you can use the COM port on the virtual machine as normal COM port
Great project and working well but... my client only. For some projects, it is still inevitable to create a virtual com port if legacy software offers neither ESP hardwaresupport nor Telnet-protocol but baudrate and portnumber only.
Standard solutions like com2com / com2tcp and others don't work @Win10 anymore and I've been searching for some days now without finding a working (and affordable) alternative.
The main problem is, that if you're searching for "ESP" "virtual com port" etc. you'll find thousands of issues dealing with flashing problems of ESP boards / onboard-USB and the second problem is dozens of commercial solutions beyond 100$ in between the results...
So if anyone knows a actual project (that was updated within the last years) or a non-commercial solution tha works on Win10, it would be great to find a hint right here, at the start of the project.
Thanks, Bunbury