AC3.1-rc5, issue maybe?

I have just installed the beta release AC3.1-rc5 through MP (1.2.85).

I loaded my 3.0.1 parameter file, had a quick check, re calibrated radio, accel, compass.

Now when I first tried to arm, I couldn't even though I had GPS lock. I have the arming check enabled.

I went back to the MP, connected through USB, with RC on (no battery connected to aircraft), tried to manually arm, but got the msg saying "PreArm: Check FS_thr_Value"

After a bit of twiddling around I disabled arming check, then tried another flight.

Without any props on, I armed the copter, but the motors were spinning straight away, only about 10% throttle. OK, this is not so bad, so I put the props on, armed it and had a fly. I must say it is very very stable in stable mode and altitude hold.

So my questions are:

Are the motors meant to spin  once armed?

If so, how can I keep the pre-arm check enabled?

If not, how can I fix it?

Im running a TBS discovery frame with:

APM2.5 with external compass

F30A simonK

Tiger MT2216-11 900KV

4S 3300mAh

RCTimer C&V sensor, calibrated.

My new parameter file is attached.

If this has been covered elsewhere, im sorry, but can you please point me in the right direction.

Cheers, Nicholas

Discovery (AC3.1-rc5) 01.11.13.param

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • OK, so I have my copter connected to MP with USB, my battery connected (don't worry, I disconnected the UBEC that normally goes to the FC), Radio on and MP connected.

    When I hold the throttle stick down and to the right the message that is coming up in MP is "PreArm: Bad GPS Pos" or I also get "PreArm: Check FS_THR_VALUE".

    I do have a GPS fix, as it says so in the HUD on MP. my FS_Thr is set to 975, and my throttle min value is around 983.

    I have LEDs for GPS and Arm, and my LED setting at 11. my GPS LED is solid.

    OK, I have just adjusted my FS_THR_VALUE from 975 to 920 (the value my PWM goes to when  turn off my radio is 900), I tried to arm and success. yay for me.

    My guess is that the new firmware doesn't like having the failsafe PWM level so close to the minimum normal value.

    Cheers, and I hope this helps someone else.

  • T3
    Prop spin when armed is normal for the new release. It may change in 3.1 as a default value of no spin. With the mission planner connected and per-arm check enabled you should see why it's failing in the display. From what you mentioned earlier it may be a throttle error in failsafe you may need to recalibrate your radio.
This reply was deleted.

Activity

Neville Rodrigues liked Neville Rodrigues's profile
Jun 30
Santiago Perez liked Santiago Perez's profile
Jun 21
More…