You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using Teensy 4.1 and setting the Serial/Mouse/Keyboard/Joystick option in the Tools menu.
The Joystick does not activate if it is plugged in on power up. Requires a un-plug / plug cycle. Then it works.
on Windows joy.cpl doesn't see the Teensy Joystick without the unplug/plug cycle
Raspberry Pi Linux doesn't see it either until the unplug/plug cycle
I've tried adding Joystick.begin() into the sketch setup() section (why is this not always needed?) Also adding a delay and trying to force a message with Joystick.sendNow() neither changes the behavior.
The text was updated successfully, but these errors were encountered:
Actually the joystick is visible in the system but no messages are received from it if it is plugged in at power up until it is unplugged/plugged. So no response in the host system to movements or button presses on the Teensy side.
Also on the Raspberry Pi side >>3x<< joysticks are enumerated to the system according to jstest-gtk. A joypad type (2 axis 8 buttons), the requested 7 axis/32 button standard one and the 12 axis 73 button one. All are visible to the system for some reason. However, messages are only ever sent from the 7 axis one once it starts working.
Also just a comment: I don't understand why no joystick object is created nor a joystick.begin() method is needed and no #include <joystick.h> is called. I assume the tools menu selection does all of that but it seems odd for the system to do that for you, under the covers as it were, in this one case rather than explicitly like just about every other Arduino library.
Using Teensy 4.1 and setting the Serial/Mouse/Keyboard/Joystick option in the Tools menu.
The Joystick does not activate if it is plugged in on power up. Requires a un-plug / plug cycle. Then it works.
on Windows joy.cpl doesn't see the Teensy Joystick without the unplug/plug cycle
Raspberry Pi Linux doesn't see it either until the unplug/plug cycle
I've tried adding Joystick.begin() into the sketch setup() section (why is this not always needed?) Also adding a delay and trying to force a message with Joystick.sendNow() neither changes the behavior.
The text was updated successfully, but these errors were encountered: