Hi , I have followed your instructions to install latest APM , i see it comes up as 3.4 dev
if you change latest to beta in the firmware path you get 3.3 rc10
ie sudo wget http://firmware.diydrones.com/Copter/beta/navio-quad/ArduCopter.elf --output-document=ArduCopter-quad
I noticed in both versions that my current measurement shows negative for current (amps) and battery is always at 100%, (update if i arm and run motors it shows a positive while they are running).
Also i noticed Compass/Motor MOT is not working, i was able to run it with original release, but with 3.3rc 10 and 3.4 dev it fails.
I am unable to use Auto Analysis with mission planner lastest beta. and the Log Review does not show Vibes and vibes is not shown on Mission planner
I guess i should be using the beta 3.3 RC10 rather then the 3.4 Dev
Anyone else had problems with Compass/MOT ?
I also tried connecting a second GPS and compass (NEO7M) but the compass made the system run slow probably a conflict, the 2nd gps worked on its own if i unplugged the 2nd compass.
Anyone managed to get a 2nd GPS / compass working ?
I’m running beta 3.3 rc10, very well performance.
About second GPS, I don’t know for Navio+ board, I already test 2 GPSs with Pixhawk, but I Strong recommend you use only one GPS… look my post from diydrones, without answer.
But if you want go ahead, tests are good anyway, and help a lot the evolution.
about the current measument did you change the paremeters ? I have a strange baterry fail safe alert in pre-arm check, but the current measumnt is ok.
@DAS62 Thanks for the info I will also change my script to use the beta path then, not latest.
@robertb It seems like DIY Drones already split their development streams, I guess new features in 3.4 only, and 3.3 is just for fixes until it’s ready for release (it’s taking a long long time).
Shame because we need 3.3 before us Navio users can document/use a “stable” link with hardware support. I wonder why 3.3 is taking so long to release, I thought it was all very well tested (even simulated).
yes, Tonny, I agree.
So for now, I think is better one GPS
just in case someone is interested. I was testing RC9 with Pi2 and after updating the libc execution worked.
Today, I tested RC11 with Pi1 and it is not executable with the libc6 version :D.
I think downloading executables in linux is not a good strategy.
Additionally, pigpiod is running by default. I don’t know whether this is dangerous together with the new version of AP
Maybe not, as one of my copters was flying a while with it… But it takes a bunch of CPU time.
Shouldn’t it be a package manager source URL/package in the world of Linux? Installation and updates would be even easier then.
I don’t mean going back to a separate Emlid build, just some kind of standard wrapper which helps with installation and updates.
If it doesn’t require a lot of infrastructure and can be duplicated to support the different flavours of Linux package managers, then DIY Drones should set it up on their web server which hosts the master files.
Isn’t a package repository simply some configuration files hosted on a server? i.e. possible to host statically and update (the internal source file URLs, dependency and version numbers) in their build script?
hi, here is a video with APM 3.3 rc9, my Y6 is in loiter mode
the GPS lock is pretty good, just noticed some variation in altitude
tomorrow i will test the rc11
It appears 3.3 is officially stable since 9th September on firmware.diydrones.com (build 29th September):
Author: Randy Mackay firstname.lastname@example.org
Date: Tue Sep 29 08:45:56 2015 +0900
Copter: version to 3.3
APMVERSION: APM:Copter V3.3
So now Navio has an official APM production release
I’ve also updated the download script in this thread. Maybe it should go into the documentation?
@CodeChief We have new .deb ready, will post it today and update all the download links.
I wonder what the “normal” way should be. Now Navio is in the DIY Drones official build, why continue to maintain separate DEB files? Perhaps there is some technical reason I’m not aware of (still a Linux newbie), e.g. does it deal with the dependencies better?
The only outstanding issue with the direct build I am aware of is that we still need to use the “testing” branch of APT package manager, because DIY Drones use a newer C library. I guess we need a new Emlid real-time image/higher RasPi kernel to get that?
We have compiled our binaries with correct libc version, so that everyone does not have to use testing branch. Deb also combines all vehicles in one file and adds corrects symlinks to them.
I think it is a very bad habit to distribute raw executables for linux, like DIY Drones do.
Thanks for the information, that makes sense. I’ve removed the depreciated/“old” references from my script comments to avoid confusion.
Does anyone have a patch to build the official source on the RPI 2 real time image? I always get compile errors and I don’t have the time to debug. Has anyone else built the source on the emlid image?
Hi. Should I remove/purge my current APM install (installed using
sudo dpkg -i apm.deb) before I install this new deb? Or can I have them installed in parallel?
Or should I create a clean build from scratch? (Not preferred)
You can take a look at our repo which contains a step-by-step instruction how to compile and boot the patched kernel. If you come across any compilation errors, please let us know and we’ll help you figure oout what the problem is.
If you’re concerned about the parameters you’d been adjusting, don’t worry. They are compatible across different versions.
You can proceed with the installation. The only way it could lead to problems of any kind is if you compiled a custom binary from master branch.
Either way, the backup is always a good practice. That’s why I encourage you to download parameter list using a GCS of choice before upgrading.
Thank you for your response.
My question is: should I uninstall my current version of APM before I install the new one? Or can I just proceed with the installation of this new version?
Will it overwrite the previous version?
Or will it be installed in parallel?
You can proceed. The installation will overwrite old binaries and let parameters stay as the were.
But, I want to make it clear one more time: please, make a backup just in case something goes awry.