[karla]

Got it. Thanks. Will for sure try this.

[karla]

Now ready to try the new fix code but need some help on the procedure please.
I think I need first to get the Revo firmware source code from Next 589.

I am using my MS pc machine for this using wiki: https://librepilot.atlassian.net/wiki/spaces/LPDOC/pages/14876735/Windows+Building+and+Packaging
this is the command to check out the "next" source code branch

Code: [Select]

cd librepilot
git checkout next
But what command to get the next 589?

[TheOtherCliff]

Been a while since I did it, but I'm pretty sure you just change 'next' to the git hash number of the version (r589?) you want.  Find the hash number like this:

GCS "Help About" or the popup from mismatch firmware/GCS will tell you the git hash.

If git hash is 123456789876.....

then just "git checkout 12345678"

if the first 8 digits uniquely identify the exact version then that is all you need.

If you are already running r589 then there is no need to do anything but build the Revo firmware and flash it.

Then "make revolution_clean" and something like "make -j4 revolution" will clean and build just the part you need.

For Windows, use the backward slash \ everywhere instead of the forward slash / I have typed.

Are you running r589 from an installation of a build that someone else did?  You can just flash the firmware from there.  You will find the new firmware at: /your_r589_build_dir/build/firmware/fw_revolution/fw_revolution.opfw after you do the build.

Or you can build GCS with something like "make gcs_clean" and something like "make -j4 gcs"
and the new GCS exe is found somewhere like:
./build/librepilot-gcs_release/bin/librepilot-gcs

[karla]

Thanks Cliff,

This is the screen when hitting about in the GCS,
not sure what number to use in the Git command.
Can you please advise?



I am running a Windows version of LP next that was an executable, i did not make it locally. Any chance someone else did make the excutable with this fix? That would be a shortcut

[f5soh]

You can simply download the Librepilot GCS r711

[TheOtherCliff]

looks like its: 4c9c3c20
I should have described the exact wording.

Its a good thing to know that you can build it yourself, but as @f5soh says, there is a more recent 'next' version.  It looks like this fix was recently merged into latest next.

[karla]

Fantastic! 

[TheOtherCliff]

Of course be aware that you will be basically starting over with configuration if you go with the latest next, and probably again with later nexts and future releases.

Make sure to export uav settings, and it is helpful to make screen captures of all important GCS settings pages ... from r589 before updating anything.

[f5soh]

A config file from r589 can be imported to a running r711 board without any issues.
No UAVO changes except a new UAVO into r711, but not used by normal user.

[karla]

f5soh, can you confirm I do not need to redo the thermo calibration and the gyro/accel calibration, if I import my old uav-setting file to the new version?

[f5soh]

If worked before with previous r589 the r711 will work the same.
If you redo gyro/acc calibration, they will be a little better.

[karla]

Okay, that's an incentive to re do it 
Thanks

[karla]

Hello again and Thanks

Implemented LP r711 and re-did all calibrations except thermo.
Did fly it last weekend.
(+) The shift to AltitudeHold from Attitude is now smooth and as before the Altitude is held very good.
(+) Shift to PosHold from Attitude also smooth.
(- ) In Pos Hold, the Toilet-bowl effect is less but still there (AttEstAlgo=INS13+CF).
(- ) Mag have some +- 10 degrees difference from my iphone, intermittently.

Just today, i discovered that the settings in GCS, Configuration, Mag, Mag type = has always been 'GPSV9'
However, it should be 'DJI' since thats the HW on the heli.

My question: Does this really matter? Can I expect other readings/performance after correcting it to DJI?

It will take some time before I can test in the field...

[TheOtherCliff]

I imagine your GPS health is not green if you have the wrong GPS type configured.  Select correct GPS type, recalibrate mags, and see if toilet bowl goes away.

If it were me, I would then disconnect the GPS/mag and fly again.  If toilet bowl comes back it sounds like an issue in INS13+CF in that it does not work correctly if GPS fails.

[karla]

The GPS type is correctly set.
Its the Mag type that is wrongly set.
I was not aware that the mag also has to be set, when changing to a dji/naza gps/mag unit.



I realize it should be some difference, my question is if I can expect a significantly better result or not.
Not so important, I think I have an opportunity this weekend to test it in the field, then I will know