Hello everybody!
I've searched through the forum for a bit and haven't found a clear-cut answer, so I'm going to post a clear cut question...
Background: I'm basically making a video game controller out of a Teensy 3.6, but I keep having trouble with the microUSB getting RIPPED off the board from carelessness. The fix for this will never happen and is outside the scope of this discussion. For the same reasons, it's also important that I can have the Teensy in a socketed configuration, because....that's right... carelessness.
My motivation is that I want to use a more robust USB connector on my own board, but I don't like the idea of pogo pins for reliability reasons. Maybe I'm wrong here. I know I could use the D+ and D- pads, but it just gives me the heebie jeebies, because if that connection fails, my phone starts ringing late at night and that's not my idea of a good time, because then the same dummies that broke it in the first place are in there wiggling things.
Programming the Teensy over the MicroUSB is just fine, and in fact, probably can't be done any other way. This is OK, and perhaps even a good thing!
Question:
I want to be able to use my Teensy 3.6 as a keyboard/serial/joystick etc device connected to a computer, but using the 'host' port instead, since it's accessible by through-hole pins, which I'm much more comfortable with. To be clear, I don't want the teensy to host a USB device. it IS the device, hosted by the computer. Over the other port.
Can I do this? Do I need to make very serious changes to lower-level teensy libraries? This would be OK.
Any ideas on this port switch would be appreciated, or alternatively, pogo pin pep talks and helpful suggestions.
Thanks!
Andy
I've searched through the forum for a bit and haven't found a clear-cut answer, so I'm going to post a clear cut question...
Background: I'm basically making a video game controller out of a Teensy 3.6, but I keep having trouble with the microUSB getting RIPPED off the board from carelessness. The fix for this will never happen and is outside the scope of this discussion. For the same reasons, it's also important that I can have the Teensy in a socketed configuration, because....that's right... carelessness.
My motivation is that I want to use a more robust USB connector on my own board, but I don't like the idea of pogo pins for reliability reasons. Maybe I'm wrong here. I know I could use the D+ and D- pads, but it just gives me the heebie jeebies, because if that connection fails, my phone starts ringing late at night and that's not my idea of a good time, because then the same dummies that broke it in the first place are in there wiggling things.
Programming the Teensy over the MicroUSB is just fine, and in fact, probably can't be done any other way. This is OK, and perhaps even a good thing!
Question:
I want to be able to use my Teensy 3.6 as a keyboard/serial/joystick etc device connected to a computer, but using the 'host' port instead, since it's accessible by through-hole pins, which I'm much more comfortable with. To be clear, I don't want the teensy to host a USB device. it IS the device, hosted by the computer. Over the other port.
Can I do this? Do I need to make very serious changes to lower-level teensy libraries? This would be OK.
Any ideas on this port switch would be appreciated, or alternatively, pogo pin pep talks and helpful suggestions.
Thanks!
Andy