My project is a UWP app communicating to a Teensy 3.2 and a 3.6, each doing different things. I have their tasks separated because of mission creep, and I've run out of ports on the 3.6 so I included the 3.2 to run some lasers. My UWP app won't accurately differentiate between the two of them. When programmed as serial devices, both uC's VID and PID are always 0x16C0 and 0x0483, respectively.
From the IDE, I can change their type, to any of the following:
When they're both programmed as serial devices, they show up in the UWP serial sample app like so:
You'd think this would allow me to differentiate between the two based on everything after the PID, however, they seem to switch places every other time I start the app or unplug/replug. It's frustrating. Furthermore, when I connect to either of them, the part in braces is always the same:
I've tried changing the type to various things, and I'm mostly able to talk to both devices but they show up in device manager as whatever I make them, and I'm concerned that this might cause conflicts with the rest of my system. For example, setting it as an "All of the Above" device allows my computer to see it as audio, which caused Hulu to crash when it tried to send digital audio to a microcontroller. I'd like to have them both as serial devices, if possible?
Is there anyway to change the built in identifiers so I can programmatically differentiate between two serial devices? Any guidance would be appreciated.
From the IDE, I can change their type, to any of the following:
When they're both programmed as serial devices, they show up in the UWP serial sample app like so:
You'd think this would allow me to differentiate between the two based on everything after the PID, however, they seem to switch places every other time I start the app or unplug/replug. It's frustrating. Furthermore, when I connect to either of them, the part in braces is always the same:
I've tried changing the type to various things, and I'm mostly able to talk to both devices but they show up in device manager as whatever I make them, and I'm concerned that this might cause conflicts with the rest of my system. For example, setting it as an "All of the Above" device allows my computer to see it as audio, which caused Hulu to crash when it tried to send digital audio to a microcontroller. I'd like to have them both as serial devices, if possible?
Is there anyway to change the built in identifiers so I can programmatically differentiate between two serial devices? Any guidance would be appreciated.