ricardo-reis

These links seem to provide some info, but they implement something different. They're both on the RX side, which I'm leaving untouched. Might be the same addresses for the data, though.. I'll have to test that. Thanks

The closest I have to that is this link, but it's not a datasheet.. https://www.expresslrs.org/quick-start/transmitters/tx-prep/ helps understanding pinout, bauds and a few other configs that should be set up on the radio controller. I have a...

Hello! Not finding much about the exact thing I'd like to do, so, opening a new thread to see if there's anyone around here who has done something on this.. Basically, I'd like to use a Radiomaster Ranger Micro (TX) to send data to a receiver...

Finally got a display delivered and some time to come back to this.. Had a few little hickups to integrate the usbhost with the display (ili9341 3.2" with touch), but got around to have it working. Tested your lib for the display, @KurtE -...

Oh, nice. Thanks! I'll have a look.

This file is part of the Teensy 4 core. That is it is in the ...\cores\teensy4 directory. This report descriptor and the corresponding code usb_joystick.c (and .h) in the same directory are also included in those builds when the USB type...

That's good info. Thanks! Is the usb_desc.c from the Joystick library? I haven't looked into that lib as, in this project, i'm aimed at using the joystick as a standalone controller - no pc.. The HIDDumper.cpp is what i modified slightly to...

The format of the data is dictated by the report descriptor that the device returns to us. For example, if you build a teensy as a USB type that includes Joystick, it will return back a descriptor that looks something like: (From usb_desc.c) #if...

Ah, that makes sense. Thanks for the response! As I got around it with the second example, I'll keep the separated buttons/axis data in arrays, which, to me, keeps logic a little more straight forward and doesn't add much to the existing code.

It's not a sum, it's a bitmask. Each bit position in the value represents a separate button. You can use logical AND operations to easily check the state of individual buttons.

Today in the morning I started modifying the HIDDeviceInfo.ino example, to fit better the use case I have in mind. Mapped the 15 buttons my joystick has and have all 4 axis working too.