Hello,
I just purchased a Snap Stick (SS200). The drivers included with Portal recognize it and can talk to it via USB.
However, I want to talk to the Snap Stick as a virtual com port. I see in Device Manager that Windows sees a virtual com port ("USB Serial Port"), however it cannot find a driver.
I tried the driver Jheath shared here, but they did not recognize the device. (Looking inside the synapseport.inf file I can see there is no line for the Snap Stick, which has PID 9090. There is only a line for it in synapsebus.inf, which is presumably for proprietary USB support rather than VCP.)
I have also read Barry's app note here, however I get the impression that this is outdated and I should be able to use the VCP feature without fiddling with the FTDI config.
Please share any suggestions for getting a Snap Stick to appear as a virtual comm port. I am hoping to use this as a nice-looking demo for a customer this Friday.
Thank You,
Chris
I just purchased a Snap Stick (SS200). The drivers included with Portal recognize it and can talk to it via USB.
However, I want to talk to the Snap Stick as a virtual com port. I see in Device Manager that Windows sees a virtual com port ("USB Serial Port"), however it cannot find a driver.
I tried the driver Jheath shared here, but they did not recognize the device. (Looking inside the synapseport.inf file I can see there is no line for the Snap Stick, which has PID 9090. There is only a line for it in synapsebus.inf, which is presumably for proprietary USB support rather than VCP.)
I have also read Barry's app note here, however I get the impression that this is outdated and I should be able to use the VCP feature without fiddling with the FTDI config.
Please share any suggestions for getting a Snap Stick to appear as a virtual comm port. I am hoping to use this as a nice-looking demo for a customer this Friday.
Thank You,
Chris
Comment