Hi folks,
I have a few museum exhibits in place that use a Teensy 3.0. I programmed them with Teensyduino 1.16. I create a USB joystick, and I'm running into what appears to be a regression when using Teensyduino 1.17 and 1.18. (I haven't been able to try 1.19 yet.)
The issue I am encountering appears to happen even with the built-in examples.
Using Teensyduino 1.16, the joystick enumerates as /dev/input/js0 on a multitude of Ubuntu machines, even fresh installs. Using newer versions than that, namely anything that supports the 3.1, it enumerates as /dev/input/js1.
Does this happen to other people? I've been using 3.0s in the meantime for new installations, but I'd like to get this figured out. Is this something where I can copy the USB descriptors from 1.16 to the newer versions? A client physically broke a board, and all I have on hand are 3.1s--so figuring this out saves me a pretty penny in overnight shipping fees for 3.0s!
Thanks folks!
I have a few museum exhibits in place that use a Teensy 3.0. I programmed them with Teensyduino 1.16. I create a USB joystick, and I'm running into what appears to be a regression when using Teensyduino 1.17 and 1.18. (I haven't been able to try 1.19 yet.)
The issue I am encountering appears to happen even with the built-in examples.
Using Teensyduino 1.16, the joystick enumerates as /dev/input/js0 on a multitude of Ubuntu machines, even fresh installs. Using newer versions than that, namely anything that supports the 3.1, it enumerates as /dev/input/js1.
Does this happen to other people? I've been using 3.0s in the meantime for new installations, but I'd like to get this figured out. Is this something where I can copy the USB descriptors from 1.16 to the newer versions? A client physically broke a board, and all I have on hand are 3.1s--so figuring this out saves me a pretty penny in overnight shipping fees for 3.0s!
Thanks folks!