[backyard]

Trying to get altitude hold working on an original Revo that I bought on the RCG forum. There is a red flash on the LED and hopefully the screen shots tell the rest of the story.

Yes, this is the OP firmware.  I am testing the LP on my CC3D and haven't transitioned the Revo yet.

Is there any way to diagnose whether the baro is simply non-functional? Have I missed something in the setup?

Thanks for any hints.

[f5soh]

Rcinput warning is here because Rx is not powered or Rctransmitter is no on

See also this page :
https://librepilot.atlassian.net/wiki/display/LPDOC/SystemHealth

If you want to use Altitude hold you should set AltitudeHold or AltitudeVario in the flightmode tab, right "Thrust" column.

If i remember there is some restrictions, try for Atttitude / Rattitude stabilization modes.

[f5soh]

Hi and welcome here !

[xpantz]

Depending on your version of GCS you might also check Settings>VtolPathFollwerSettings>ThrustControl is set to Auto.

You can see the Baro output on the Scopes tab.  Might need to change one of the scopes.

[f5soh]

Depending on your version of GCS you might also check Settings>VtolPathFollwerSettings>ThrustControl is set to Auto.

Looks like backyard do not use Ins13 : No GPS, no baro. Mag sorry

Baro altitude is displayed in PFD (the right vertical scale), firmware tab or uavo browser

[backyard]

Thanks very much.  I will try again tomorrow.

[cato]

a bit off topic: how is the Altitude dial computed?

GPS->Altitude shows 548 (which looks very reasonable, as ground level is around 530m N.N., and I am on 5th level)
System->Sensors->Baro->Altitude shows 435m
the Altitude dial shows 455 to 460m

[TheOtherCliff]

If you have a GPS and it is configured to be used for this, it is both baro and GPS.

Baro alone is not good long term.  A storm can change it a lot.

GPS alone is not good short term.  It can vary many meters in just one minute.

Think of it as GPS is initial altitude and long term and baro is short term.

[backyard]

I found and changed the altitude hold settings and it looks like the baro is working.  The alarm was indeed the rx and tx not on.  Thanks for all the help.

When I went to test fly the motors wouldn't start.  I reloaded the firmware and reset everything (including arming).  Still no motors.  This quad has flown prior to this.

The Revo red LED still flashes.  The attached video shows the boot sequence and flashing LEDs.  I found an OP wiki description of the LED indications but don't understand it enough to diagnose the problem.

Any hints would be greatly appreciated.

https://www.youtube.com/watch?v=RBM6EAQfwFs&feature=youtu.be

[f5soh]

Update to LP15.09 is not done yet.

Post your config file here:
File > Export UAV settings.

Alarm status > SystemHealth ?

[backyard]

Upgraded to latest LP firmware.
System status on GCS shows no alarm issues.
Motors still will not start.

[f5soh]

Your config file looks ok.

Go into Config > Input tab

While quad is powered, monitor Rcinput channels move yaw stick > Yaw slider move.
Be sure your Throttle is bellow neutral for arming.

If something weird, redo transmitter wizard.

[m_thread]

Have you managed to get the motors running using the manual output test? Check connections between controller and ESC's.
/Fredrik

[f5soh]

Found :

You can't arm while a FlightMode using AltHold is active.

Arm, hover and go to flight mode with Althold

[backyard]

SOLVED!!!

Thanks very much for the help.

The red led still flashes alternately with the blue but I'll try to fly her.