Need help with controller configuration

[ThomasC]

hmm, I never got that message. But I must admit, that in 5-channel mode I must assign throttle and pitch channels manually after calibration, as those channels work synchronously while calibrating and Heli-X cannot automatically determine which is which. Throttle channel can be identified in controller config main window (after calibration) by activating throttlehold on transmitter. While calibrating, does every channel react in calibration window "move all sticks to their maximum and minimum positions"? Throttle stick must be responded by two channels there, otherwise 5 channels are not calibrated (throttle hold must not be activated while calibrating for 5 channel operation)

[vmsda]

... I must admit, that in 5-channel mode I must assign throttle and pitch channels manually after calibration ...

Not sure what you mean.
1. Where do you "assign" those channels?
2. Does that imply that one could have two calibration xml files, one in 5-channel mode and the other not, and load either of them when needed?

... While calibrating, does every channel react in calibration window "move all sticks to their maximum and minimum positions"? ...

If the calibration is going to be successful, sure they do; if they don't react, you are gonna get the "channels not detected" message. This, at least, is consistent.

[ThomasC]

See attached screenshot. In my case "Collective Pitch" was assigned "Z-Achse" and "Engine Speed" was assigned "Z-Rotation" after calibration. I had to manually correct this, as "Collective Pitch" channel is "Z-Rotation" in my case (here: DeviationTX controller, Heli-X under Windows 7, shown configuration is after manually reassigning the named channels correctly)

controller config with five channels

clipbrd01.png (58.48 KiB) Viewed 39879 times

while calibration it looks like this when I assign collective pitch:

while calibrating pitch

clipbrd02.png (34.6 KiB) Viewed 39879 times

under Linux there's basically no difference, works the same way. But there you might need to use "jscal" to eliminate stick deadband, probably depends on the used Linux distribution.

You don't need different controller configuration files unless you use them under different OSes. I wrote two scripts (one for Linux, one for Windows) that move around the config files for that purpose. Once you have calibrated five channels, you are free to switch back to four channels, the fifth channel is ignored in that case.

[vmsda]

Thank you for your input, ThomasC.
But before going any further, I came across the following thread, in HELI-X in Linux: viewtopic.php?f=9&t=1617.
Since I am trying with exactly the same usb interface with which he failed, maybe it is not worth investing any more time. The problem is that I cannot buy the usb interface he ended up with, since the site is not fully functional.

[vmsda]

Hi again, ThomasC. In the meantime, I decided to make some calibration attempts in order to show you how different my output is from the one you get.
The first is the basic calibration without the 5 channel spec:


The second shows the output of the first, but I checked the 5 channel box before doing the next stick calibrations:


In the third screen, you can see that the output of the previous calibration is exactly equal to the first!


Can anyone make sense out of that?

[Musicista]

salve a tutti, non riesco piu a configurare la mia radio, su windows 11, con questa configurazione su pc qui : driver controller per " volante (gioco) Logitech G920 Driving force Racing Wheel Usb , e Pendrive per Frsky Simulator, con questi 2 driver , quando vado in configurazione Heli-x controller radio, non mi fa' decollare, ma se tolgo invece , il connettore "Logitech G920 Driving force Racing Wheel " dalla porta Usb, e rifaccio la configuraione degli sticks, questi iniziano a funzionare sui vari canali, e quindi alla fine salvo esco e mi fa volare, come se ci fosse un chiaro conflitto sui 2 driver delle 2 periferiche, ma che su gestione dispositivi di windows invece , è tutto perfettamente configurato, e con i driver giusti dei relativi costruttori, non vedo solo quello di FRsky Simulator , perche è un Bluethoot, e quindi lo trovo configurato nei dispositivi Bluethoot di win 11......quindi vi chiedo , io per ora devo ogni volta distaccare il connettore Usb, del gioco (Volante ,Logitech G920 Driving force Racing Wheel ) per poter volare su Heli-x, ma chiedo a voi se è capitato a qualcuno di voi, o se cè un modo per capire cosa altro possa fare per eliminare il problema di tale conflitti a monte, anche se windows 11, è tutto aggiornato, e non mi trova nessun errore.......

vi ringrazio in anticipo per chiunque mi aiuterà


Hi everyone, I can no longer configure my radio on Windows 11, with this configuration on PC here: controller driver for "wheel (game) Logitech G920 Driving force Racing Wheel Usb, and Pendrive for Frsky Simulator, with these 2 drivers, when I go into Heli-x radio controller configuration, it doesn't let me take off, but if I remove the "Logitech G920 Driving force Racing Wheel" connector from the USB port, and redo the stick configuration, these start to work on the various channels, and then in the end I save, exit and it makes me fly, as if there was a clear conflict on the 2 drivers of the 2 peripherals, but on Windows device manager instead, everything is perfectly configured, and with the right drivers from the relevant manufacturers, I only see the one for FRsky Simulator, because it is a Bluetooth, and therefore I find it configured in the Bluetooth devices of Win 11......so I ask you, for now I have to disconnect the USB connector of the game every time (Steering wheel, Logitech G920 Driving Force Racing Wheel) to be able to fly on Heli-x, but I'm wondering if this has happened to any of you, or if there's a way to figure out what else I can do to eliminate the problem of such conflicts at the source, even though Windows 11 is all up to date, and it doesn't give me any errors...

Thank you in advance for anyone who can help me.