I think the answer is a bit more complicated than just usb vs com port. Somehow you need to get the software to see the usb device or the usb device to present as a serial (com) port. Now the issue is your new device is present itself as a usb device and not as a com port. The usb device presents itself as a com port and then you configure your software to talk to a com port. This is typically how a usb to serial adapter works. Well what I see (guess) is that your software is talking to the device over a com port (com18) to be exact. I would appreciate any help, ideas to try, some software or companies to contact If we couldn't fix this problem, we have to change the whole key lock system for the whole Hotel of 700 Rooms !!! with cost of almost 100K ! That's why the software can detect the encoder, but since the new encoders are native USB, with no built in converter. However i got 2 devices for testing, but the problem now that the software is only detecting the encoders that are connected to the serial-com ports, it doesn't see any USB encoders, it is true that the original encoder is connected over USB cable, but inside the encoder itself they are using Silicon Labs CP210x Virtual serial port bridge, and it has a driver for that chip.Īnd the device appears under Com ports ( the same idea of USB to Serial adapter )
My only solution was to try to find a generic card encoder that (might) work.
In a hotel, we have key a legacy door lock system software that is talking to the its card encoder via a USB cable connected to the the card encoder, but our encoders are physically dead now and they don't do the cards, we contacted the manufacturer to provide us with additional encoders but they responded that they stopped manufacturing this kind of encoder, and the whole system become out of any support. Is there any software or hardware that emulate native USB device to serial-com ports, cuz the software only talk to devices connected to a Serial-com ports !
0 kommentar(er)
