- Joined
- Mar 12, 2016
- Messages
- 3,920
- Reaction score
- 2,626
They are cumulative. You only need to do the most recent "current release:"I have never did of any of the firmware updates.
is 1.5.2 the only update that I need to do?
They are cumulative. You only need to do the most recent "current release:"I have never did of any of the firmware updates.
is 1.5.2 the only update that I need to do?
I have no seen any reason it would be considered unsafe. And it isn't fundamentally changing the way the solo works. The green cube is really a totally different topic, not to be compared. The green cube is experimental, and not for the inexperienced faint of heart.
Note: Do not program a mission to go 40mph into a stiff headwind. I wanted to test what I thought was a new feature in this firmware. I believed it would prioritize altitude and reduce speed to maintain altitude. It did not. This also shows how much work that gimbal does!
PMSLLOL. I didn't. I added them from my old MS Flight Simulator files while editing the video. Not heard on the video, is me running across the field yelling *@&#$*(@ PULL UP!! PULL UP!! ()&$*(@&
P2p,
Hoping you could answer....
Reposting this statement.....
As a newbie, so with regards to firmware release 1.5.2 or 1.5.3..........when does 3Dr officially roll this out to the consumer........????
Or is it left up to the user community to find out & update their own Solo's thru WinSCP or other means ???
Just curious......
Others on here have tried to get internal replacement parts from 3DR with very little success. Think about it... many consumers may (and many more, likely will) do more harm than good inside. 3DR just has no way to judge the competency of the user - and then that becomes a liabilty risk....They may balk at the fact that you already replaced the pixhawk yourself though. I suspect they do not have spare pixhawks lying around to send you as a replacement. They might say "congrats, you fixed it yourself, bye"
Yes, the px4 file is the one you want. Clicking on the blue heading with the version # just takes you to the same files on it's own page. Here is a tip though that helps.. After you have DL'd the file, rename it to the version; ie: Arducopter-v2.px4 rename to Arducopter v1.5.3.px4. That helps to ID it later as they are all named the same. You still put it in the firmware folder as usual and the new names will work fine. The Solo is only looking for a .px4 file, and the full name before the extender is irrelevant. Renaming will also help you in that after Solo does the upgrade, it moves it to a folder with previous FW upgrades. You can have new ones and old ones stored in this folder. Then if you ever want to change back, just move the version you want back up one directory to the firmware folder.P2P,
Thank you much appreciated on the answers.
I pretty much understand the update process from post #1 in this thread & read your take on this update in thread #2 & thank you for your insight....
So on github.com it shows....for the latest release
Downloads
Also, one can click on the big blue numbers that say solo -1.5.3 or just to the left of it says
- ArduCopter-v2.px4 I guess this is the file for D/L & installing to Solo using WinSCP
- Source code (zip) I guess this file is for source code geeks
- Source code (tar.gz) I guess this file is for source code geeks as well - just diff format
solo-1.5.3
-o-05a123b
Can one explain what these links are for.........in particular
SOLO - 1.5.3 ??????
solo- 1.5.3 ???????
-o-05a123b This appears to be what they changed in the source code.
We use essential cookies to make this site work, and optional cookies to enhance your experience.