Nemesisghost wrote:You define the reports in the HID Descriptor. I know there are some limitations on how large each report can be, which is one of the reasons I didn't group the axes(something that's not entirely necessary, but is ascetically pleasing in the joystick properties screen). I didn't do multiple reports just because 1 was enough to do what I needed. But it was something I was looking into so I could group my axes.
Here's a good tutorial on how to build HID descriptors & how to align the bits to match. It has a link to the official USB HID documentation, which itself has an HID writing app. That app is what I used to build mine.
Thanks!
I am still going to be 2 months before I can start on my throttle thanks to shipping to my shitty ass country...
So I started to design a joystick to pair it with! Let's face it - self made is better when you can make sure that the parts are what you want. Though finding nice integrated HAT switches is a pain.
I did find a nice 8-way on mouser but I wanted to make sure I could actually set up all the buttons before I actually went and did it... 2 8-ways, 2 4-ways with centre push and I am already out of space if I want to have a 16-bit axis. 3 axis in one report and buttons in the other is my plan.
Figuring out how to do twist on the joystick was quite an interesting problem though! Thrust bearings are my friend for that.
I decided to put twist inside the handle as to minimise the gimbal size though. Now I am waiting on the x-ref update for fusion 360 before I continue. X-refs are really important for my workflow.
Getting further OT: Should I shove the files onto github when done? i.e. Would anyone like a joystick to go with the throttle?