START HERE |
|
Register | FAQ | PM | Events | Groups | Blogs | Calendar | Mark Forums Read |
Unregistered
|
Other R/C Flight Simulators Other R/C Flight Simulators |
|
LinkBack | Thread Tools | Display Modes |
06-11-2014, 03:07 PM | #1 (permalink) |
Registered Users
Join Date: Jun 2014
|
Using a WAILLY PPM with a K-7XII fails, and I don't know why
Hi people. I am new to RC in general, and my intro was thanks to inheriting a KDS-450SV a couple years ago. It came with the stock KDS transmitter, k-7xii. I have "ground tested" it a few times, but restrained myself from actually going airborne until i felt i had a good enough understanding of what i'm dealing with. Mostly, i was hoping to have some experience on sims - to learn how to operate my heli before destroying it Seeing that my k-7xii had a PPM port on the back, i went ahead and bought the cheapest PPM USB adapter on Amazon in the hopes that somehow it would just appear as a normal joystick with 4 or so axis and so forth. But it wasn't that simple. First i had to rewire the USB cord. After a week of figuring that out, and succeeding, only to find a new obstacle: the 4 axis are all cross-talking. In other words, when not moved, the controller looks solid and calibrated, BUT, say, moving the throttle will move one axis predominantly, but several other too. Likewise for rudder and swashplate axis. I am now thinking that the USB device is expecting a different sort of PPM signal than what my Tx is putting out.
I am a linux user, but also see the same problem testing it in windows. Linux informs me (via lsusb) that the adapter is: Code:
ID 06f7:0003 Wailly Technology Ltd USB->Din 4 Adaptor Code:
Driver version is 2.1.0. Joystick (WAILLY PPM) has 8 axes (X, Y, Z, Rx, Ry, Rz, Hat0X, Hat0Y) and 12 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3, BaseBtn4, BaseBtn5, BaseBtn6). |
Sponsored Links | |||
Advertisement |
|
12-30-2014, 08:27 PM | #2 (permalink) |
Registered Users
Thread Starter
Join Date: Jun 2014
|
Solved!
I solved this: the problem was simply that the transmitter was in HL3 ("CCPM 120°swash helicopter with 3 servos") mode, which is not understood by the USB adapter. To fix it: Go in to system setting mode (hold MENU button and turn on transmitter), then simply switch from HL3 to to A/P ("Normal aero plane") mode.
After doing that it worked great with HELI-X and Jstest-gtk. |
Thread Tools | |
Display Modes | |
|
|