Support for PUMA X

[Rob G 62]

Hi folks. I am a brand new user of Axis and Ohs. I have started reading the documentation but haven't gotten that far yet. This morning I was playing around with trying to start allocating the axis and buttons on my new Pro Flight Trainer Puma X helicopter controller. When I opened the dialogue for a new axis and went to device, I only saw keyboard, mouse, and voice. I did not see the PUMA. Am I doing something wrong? How do I get the application to see that device? If it doesn't work with the Puma I will not be able to use it at all.

Thanks...... Rob

[Lorby_SI 2,072]

1 hour ago, Rob G said:

Am I doing something wrong?

Yes. This is not what the dropdown box is for. You don't pre-select a device, you just use it. As the manual says - just press a button on the device or move an axis.

Initially the drop down control contains only those devices that can't be actuated that way. When you operate the external device it will be added to the list though (so you can isolate or block it)

I'm sorry, but I have to ask - did you try the DEMO version before you bought the app? Like the product description in the shop tells you to? This is required to make sure that your hardware is supported by the app before you decide to buy it.

 

Edited June 23, 2023 by Lorby_SI

[Rob G 62]

9 minutes ago, Lorby_SI said:

Yes. This is not what the dropdown box is for. You don't pre-select a device, you just use it. As the manual says - just press a button on the device or move an axis.

Initially the drop down control contains only those devices that can't be actuated that way. When you operate the external device it will be added to the list though (so you can isolate or block it)

I'm sorry, but I have to ask - did you try the DEMO version before you bought the app? Like the product description in the shop tells you to? This is required to make sure that your hardware is supported by the app before you decide to buy it.

 

I did not try the demo version because I had already purchased the full product for use with my Honeycomb devices. I tried moving some axes and pushing some buttons but it appears your app knows nothing about this device. That's really too bad. Oh well.

[Lorby_SI 2,072]

What kind of controller is that? Joystick? Keyboard? HID? Does it have specialized drivers or software that may be interfering?

First check the Windows USB GameController dialog. Is this PUMA device displayed normally there? And does it work, could you calibrate it?

If it is there, check the Blacklist in AAO (Hardware menu). If an error is detected with a controller it is blacklisted automatically.

Edited June 23, 2023 by Lorby_SI

[Rob G 62]

4 minutes ago, Lorby_SI said:

What kind of controller is that? Joystick? Keyboard? HID? Does it have specialized drivers or software that may be interfering?

First check the Windows USB GameController dialog. Is this PUMA device displayed normally there?

If it is there, check the Blacklist in AAO (Hardware menu). If an error is detected with a controller it is blacklisted automatically.

Here is a link to the device:    https://pro-flight-trainer.com/5th-generation-puma-x-flight-control-solutions/

Windows recognizes the device and I used Windows 11 to calibrate it when I first got it.

The device is listed under active devices in the Hardware Blacklist menu.

UPDATE: OK, not sure what changed, but I rebooted my PC and when I brought everything back up, now the device is recognized and I can assign things. Go figure :-).

 Thanks for communicating with me about it. Seems all is well now.

[Lorby_SI 2,072]

While you are looking at the blacklist, make sure to move everything over to the right with the "Ignore" button that is not one of the game controllers that you want to use with AAO. That includes all mice and keyboard entries, and all HID etc. devices. Blacklist them all, leave only the actual controllers in the list on the left.

This avoids cross-compatibility troubles, there are a few devices out there that pretend to be a HID or game controller and that can clog up AAO with unusable data.

[Rob G 62]

8 minutes ago, Lorby_SI said:

While you are looking at the blacklist, make sure to move everything over to the right with the "Ignore" button that is not one of the game controllers that you want to use with AAO. That includes all mice and keyboard entries, and all HID etc. devices. Blacklist them all, leave only the actual controllers in the list on the left.

This avoids cross-compatibility troubles, there are a few devices out there that pretend to be a HID or game controller and that can clog up AAO with unusable data.

Got it! Thanks.