LibrePilot Forum
General Category => General Discussion => Topic started by: Jhinta on January 07, 2017, 04:49:39 pm
-
what i did is , arm(0/1) switch.
bootup flm1 selected
switch arm to 1
all oke ( switch still a1 1)
hover -> flm2 -> dead stop drop .
what i'm i doing wroing here , cant switch be used for arming?
-
Of course a switch can be used for arming.
Please post your config file.
-
Of course a switch can be used for arming.
Please post your config file.
here you go,
its not that i cant arm , but when flm2 is selected , direct dead stop / where i dont have when yaw-l is used
-
Be sure you don't have some mixing between channel 5 (flight mode) and channel 8 (used for arming) in your radio.
-
Your second flight mode uses GPS Assist.
Have you configured GPS?
It may be a bug in that it should give a arming or GCS error to stop you from flying a non GPS mode with GPS Assist (when GPS is not set up and calibrated) like it already does for the obvious GPS modes.
-
Have you configured GPS?
It may be a bug in that it should give a arming or GCS error to stop you from flying a non GPS mode with GPS Assist (when GPS is not set up and calibrated) like it already does for the obvious GPS modes.
Since the algorithm is INS13 i think the GPS is configured or he cannot arm at all.
-
gps enabled yes ,, but even if no gps setup still full drop
and gps is working have around 10+ sat's and i cant arm btw if it was bad.
also just tested basic
arm(1)-> idle spin (flm1) -> flm2 -> dead
arm(1) -> idle spin (flm1->arm/0->flm2) dead
using arm yaw or any all oke
-
You should consider you are using Next, sometimes there is issues.
Please do a log file that shows the disarm while switching to Fm2.
May not need flying, just on ground.
-
You should consider you are using Next, sometimes there is issues.
Please do a log file that shows the disarm while switching to Fm2.
May not need flying, just on ground.
i only use next
-
i think i have found my problem ( wrong key setup wen looking a tx monitor)
seems that when flight mode is anything but 1 , that key will be 0
-
yes that was the problem, wrong tx setup
my tx has key setup per flight mode, i only had it for the first
-
So issue resolved :D