Hello,
So i'm having a weird problem with Taranis, dragonlink, ppm, or pixhawk I'm not sure really what it is.
I'm using a Taranis controller, dragonlinlink TX/RX PPM to pixhawk. My quad flies great, tested in all modes. all channels operate correctly in the RC calibrate screen.
I'm using 6 channels, but gimbal tilt is mapped to channel 7, with channel 6 doing nothing.
My problem is, when I move the gimbal slider all the way in one direction, to make the gimbal look up... my pitch and roll stick become reversed. IE when i push the pitch stick forward, instead my quad rolls to the right. and when I pitch back, instead my quad rolls to the left.
Now if i move the gimbal slider back down so the gimbal looks down, the controlls return to normal, and pitch controls pitch, roll controls roll.
I tried to recreat the issue while the quad was disarmed. While lookling at my RC calibrate screen, i moved the throttle to mid stick to simulate hover, and moved the gimbal slider all the way up to make the gimbal look up. When i move my pitch stick forward, pitch moves as it should, not effecting roll at all on the RC Calibrate screen. But sure enough, when i try to actually fly again.... When I make the gimbal look up, my pitch stick starts making the quad roll instead.
I'm guessing this has to do with PPM framing or something with my PPM signal, but that's really just a guess and i'm not sure. My taranis PPM setting is set to CH 1-10, 26.5ms 300u +. I've tried changing it to CH 1-7, and also increasing my pulse legnth, but still the same problem.
Any ideas? I'm lost.
Replies
Well... just flew again... and i did find my real problem.
I was flying and it flew fine at first, then i started to fly around the yard and the controls got mixed up again..... then i flew back infront me and controls are fine. I fly away and controlls get screwy again... wait.... it's acting like it's in super simple mode!
Got my laptop out, checked PID page and sure enough..... ch 7 option is set to super simple! No wonder!!!!!!!
:) I am happy to have finally fixed this. Just a dumb mistake on my part...
Haha! Whew. Congrats on the fix!
Okay, just flew very shortly after Taranis FW update.... couldn't do a full flight bc i've been doing all these short test flights on the same battery but it works!!!!!
So far anyway... only flew about 3 min. It even let me go in position hold with the gimbal pot all the way up and have full control.
So maybe it was a firmware issue on the Taranis, hard to say... I don't want to say the problem is solved yet, because in some other test flights it flew fine shortly then the pitch/roll started to mix up. This was the only time ever I could switch to position hold, gimbal pot up, and still have full control though.
Thanks for your help, i'll post back after a longer flight.
Thanks! I just discovered openTX companion so i was messing with that and tried a firmware update on the taranis so I'll test fly shortly. Not to savvy when it comes to radio setup so yeahhh it's set up pretty simple lol.
The gimbal gets power from the flight pack, only signal and ground going to the gimbal controller from the RX. it's a brushless gimbal using martinez board.
So i had another test this morning, I re-binded my dragonlink rx/tx and i un-plugged the gimbal control cable from the gimbal controller, so when i command the gimbal to look up it doesn't actually do anything.
When i first take-off.... it flies fine, everything responds as it should.
Then during the flight, after about 1-2 min of flying, suddenly, the controls on my pitch/roll stick become reversed. pitch forward now makes the heli pitch back. Roll right and left is also reversed, but ONLY while i have the gimbal pot to the look up position. if i move the pot back down, it flies normal again. (good thing! IT's hard to fly with reversed pitch/roll!)
VERY confusing......... I'm still at a loss. It flew fine the first min of the flight even with the gimbal pot in the up position. Then suddenly the pitch/roll stick became reversed after a min of flying, gimbal pot down, and it flies normal again.
I've only ever tried sending 8 or 12 channels with the Dragonlink, not 7 or 10. I suggest you try one of those two. For 8 channels you want around 22.5mS frame length and for 12 channels you want 31.5mS.
Problems like you mention could definitely happen if your frame length is too short but it sounds like you already tried longer frames. Maybe you didn't rebind in that case though.
Well i just tried another test, I changed my PPM settings to 1-12ch, 30.5mS, 300u negative pulse. Re-bind TX/RX.
The problem is still there, but not as bad. Sticks are no longer reversed. Only when gimbal pot is pointing up, when I pitch forward stick, the quad will pitch forward and slightly to the right at the same time. And when I pitch back stick, it will pitch back and slightly to the left too.
I flew like that for a few min, then i decided to try alt-hold. Same thing. Okay, then i tried out position hold. I had no control of pitch/roll in position hold! and according to my groundstation, the quad remained in alt-hold, and never actually switched to position hold. If i tilt the gimbal pot down, the quad will switch to position hold and i have control of pitch/roll again.
Just noticed you said to try 31.5ms so i tried that, and same problem. sticks are messed up only when gimbal pot is up. I tried 1-8 channels with 22.5ms and same thing. I've memorized the re-bind procedure by now :)
I had another thought. Do you have any of your limits extended? Maybe you're trying to send PWM values which are too long or too short. Are any of your channels set to output more than 100% range, especially that gimbal channel?
I still think you're making a bad PPM stream somehow and causing the pulse train lose sync.
I agree it's got to be some setting or something with the PPM stream... Just checked all the channels and they are at 100% except my ch5 flight mode switch is only on 65%. Should I change that to 100% as well?
I tried using the PWM outputs on the dragonlink RX, going to pixhawk using the 3dr ppm encoder and same thing, just thinking maybe the dragonlink rx was outputting a bad signal.
-
1
-
2
of 2 Next