Discussions

Issues with AltHold jumping in 3.1.5 and im unable to read my datalogs to work out whats going wrong...

Posted by Luke Hogden on July 1, 2014 at 2:24am

So im working on a new build and its flying great.

However i have an issue with AltHold and Loiter when the quad will jump/twitch around on the Z axis.

The board is running 3.1.5 using mission planner 1.3.5

The board in is a case with foam over baro, mounted to the frame with foam tape. the quad is pretty well balanced.

After reading around a bit i thought i would look at logs to work out what it might be.

However when i try and download logs as described on the wiki they seem to start and then freeze and i cant open them to view data.

i have attached some screenshots to show whats happening in mission planner.

3691133168?profile=original3691133255?profile=original3691133238?profile=original3691133187?profile=original3691133309?profile=original

Anyone have any ideas

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

Join diydrones

Email me when people reply –
Follow

Replies

  • Luke Hogden July 2, 2014 at 2:55am

    Ok so i was doing some more thinking and i had a faint memory about someone saying that prop wash on TBS discovery style frames is pretty bad and it was affecting their baro, so i moved my APM back over to a different frame to test it and it works fine again...

    still cant get logs to work however...

  • Luke Hogden July 1, 2014 at 2:37am

    Reverted back to 3.1 and im having the same problems both with baro and with datalogs.

    i have had this board and AltHold running 3.1 no issues in the past. i have never tryed logs on it until now.

    Is my board stuffed?

    • Gustav Kuhn > Luke Hogden July 1, 2014 at 3:00am

      Hah, and I thought I was the only one.

      With 3.1.1, I had perfect Alt Hold, Loiter,  Auto, and RTL.

      Not much change after Auto Tune.

      I installed 3.1.5, and while it flies great in manual, hopeless in Alt Hold, Loiter, RTL, and Auto.

      I did an Auto Tune, made no difference.

      I reinstalled 3.1.1, and still just as bad ????

      I now used the Wizard to set up the quad, and guess what, we are in for a week long storm, so no testing, Aaargh!

      • Luke Hogden > Gustav Kuhn July 1, 2014 at 3:19am

        The althold issue im sure there is a good explanation, but for me not being able to access datalogs is a pain because i cant work out the issue.

        are you able to export datalogs?

        • Gustav Kuhn > Luke Hogden July 2, 2014 at 3:18am

          Regulator seems ok, data flash logs only downloadable via "Terminal"

        • Gustav Kuhn > Luke Hogden July 1, 2014 at 9:32am

          Haven't tried data logs, will tomorrow.

          I've also been told to check the 3V3 regulator.....

          • Gustav Kuhn > Gustav Kuhn July 2, 2014 at 2:52am

            Ok, regulator measures 3.321V on the I2C port...

            • Luke Hogden > Gustav Kuhn July 2, 2014 at 2:56am

              that sounds about right, how is your board mounted/baro covered?

              • Gustav Kuhn > Luke Hogden July 2, 2014 at 4:32am

                My original 3DR casing has a block of foam that shields the baro.......

                Point is, it flew perfectly, before JUST the code upgrade????

This reply was deleted.

Activity