"No controller found" when using FrSky QX7S

[Michael]

... and maybe a virus program blocks the access to the USB device ... ?

[superhero]

Tried that edit, no luck.

Also tried the older version available for download, didn't work there either.

[superhero]

Disabled anti virus, no difference.

This is pretty annoying haha

[Michael]

... and quite unusual ...

HELI-X checks for the USB controller during startup and does not look for connections coming later. Thus it is important that the USB controller is ready during startup, and a loose connection might be a problem. Did you try another USB port?

[superhero]

I rebooted, connected my transmitter to a new USB port, made sure it is working, started heli-x.

no controller found

Working with other sims no problems (CRRC, RCDeskPilot, ClearView)

[superhero]

Reset to factory settings and had a look at the terminal.

It creates a few directories and there are some entires that are off perhaps:

Directory c:/heli-x7/files/lists created
Couldn't find tag "WindowSettings" in file

and

c:/heli-x7/files/application/applicationsettings.xml
Couldn't find tag "InfoWindow" in file

and

c:/heli-x7/files/application/applicationsettings.xml
Couldn't find tag "ChatWindow in file

and

c:/heli-x7/files/application/applicationsettings.xml
Couldn't find tag "TerminalWindow" in file


Is it possible java is having trouble writing to the configuration file (applicationsettings.xml?)?

*edit*

Just had a look, and there is no applicationsettings.xml file to write to. There is a NewsSettings.xml file in that directory.

Also another line:
c:/heli-x7/files/application/applicationsettings.xml
no joystick found

[superhero]

I was able to get the various .xml files to show up in the \files\Application directory. Still no controller.

Should the \controller directory have anything in it?

[Michael]

This looks correct. The controller directory is used as soon as a controller is found. Thus, it is correct that it is empty.

HELI-X looks for a device of type "Joystick". Maybe, the interface tells Windows that the device is of another type.

But I do not have a solution from here.

[superhero]

I am pretty sure it is listed as a gamepad in Windows. However, other people have had no problems getting their tx to work with heli-x, so I don't think that's it. Also I would suspect the developers would not so narrowly define what controller the software can use. Gamepads are perfectly legitimate (and undervalued/underestimated/misunderstood) ways of practicing RC flight and I can't imagine the devs would disallow that in heli-x.

I have checked with 4 different simluators now and my tx is working perfectly with them. No fiddling, it just works plug n' play. I think it's gotta be something in the heli-x software, especially considering it is built on Java.

Hopefully someone else can chime in with some suggestions or I'll have to buy AccuRC or something else even though I really wanted heli-x.

[virtualcrasher]

A few months old post. But i have the same problem or at least the same symptoms.
I try with Heli-x 7, Windows 8.1 and two USB remotes, E-sky simulator usb and
Taranis X9D with Open-tx 2.2. None of them work in Heli-X 7.

I do have the Heli-X 6 demo and there both controllers work without problems.
As the poster before mentions, I can clearly see the controllers in Windows Configure gamepad
control panel section, and they can be calibrated there.

It seems I tried with Heli-x 6.1 soma time ago and that didn't work and I can't make it work today.
Same problem as with the Heli-x 7.

When I start Heli-x 7 and have both controller connected, there is a startup screen asking
me to select controller ADC or Frsky controller. But the remotes don't work inside Heli-x 7.
When only one controller is connected Heli-X just starts but there is no control, no matter
which X/Y/Z axis/rotation is selected in the controller setup.