USB HID Joystick & PPM-In program

I will look at it once I can be in front of my Tx again

Hmm...Well, I loaded you tx.ini, model6.ini, and devo8.dfu onto my devo8 and it works fine.
So this indicates there may be some sort of timing problem that is tx specific. It might explain the issues victzh was seeing as well.
It works ok on my Devo8 and devo10. I will check my devo12 as well and see if I see any issue there.
Also:
Does it continue to happen if your Tx is not plugged in to the PC? What OS do you run on your PC? I doubt the answers matter, but I'm grasping at straws.

I have the same problem, Devo8 reboots with USB HID protocol. Default model setup, Tx not connected to PC, firmware compiled from source (f2266ea), Windows XP.

If you start with a normal protocol, and switch to USBHID and then 're-init' does it work?

A couple things to try:
in protocol/usbhid.c:
Change:
CLOCK_StartTimer(1000, usbhid_cb);
to
CLOCK_StartTimer(20000, usbhid_cb);

change:
return 50000;
to
return 60000;

In target/common_devo/hid/hid_devo.c
uncomment:
//PrevXferComplete = 0;

do each one at a time and in order, and see if it changes anything before moving on. The changes should be made cumulatively (don't take out one before adding the other). The last is the most likely to change the behavior, but it very well may disable HID altogether.

PhracturedBlue wrote: If you start with a normal protocol, and switch to USBHID and then 're-init' does it work?

No, 're-init' button freeze in pressed state, then Tx reboot.

Well, even though neither devo8 and devo10 see this issue, my devo12 does. So I can reproduce, and can confirm that none of the 3 ideas I posted above actually work. I'll spend some time working on it and see if i can fix it.

I believe I located the bug and I've checked in a fix. The problem was that I wasn't waiting until a connection from the PC before sending data which resulted in writing to uninitialized memory pointers.

Please let me know if it works now.

Now it works. Right now I cann't test it with simulator, but 'Deviation GamePad' at 'Control Panel'->'Game Controllers' responds to inputs.

Good to hear. I can change the input types however it is most useful to have them. I could also define the device as a 'Flight control' instead of as a 'GamePad' easily. Since I don't have much use for this feature, I'd like feedback on what the most useful configuration is.

I checked out the Clearview demo, and all channels seem to be available