Do I need to buy VID/PID USB identifiers when using virtual COM port through usbser.sys driver on Windows or is the device being tied to a unique COM port sufficient?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Do I need to buy VID/PID USB identifiers when using virtual COM port through usbser.sys driver on Windows or is the device being tied to a unique COM port sufficient?
The only real advantage to having your own VID and PID is that your device is more identifiable as your product, rather than something generic. Also, you can never guarantee you will be on a certain COM port, as something else may have taken that port number, no matter how obscure.
I would say that unless you are really bothered about your device coming up as something generic in device manager (and you have installed the drivers in a set-up program, so you don’t get generic device installed messages on first plug-in) it’s not worth bothering. The best bet to find your device is send a quick ID string down each port you can open (starting with your ‘unique’ one) to identify your COM port by the response.
There may even be some driver-signing woes to get involved with if you have your own PID and VID too (dependent on the USB-chipset vendor).