@thatsnailguy Why do I want a list of changes to 3.6.0 when I’m upgrading to 3.6.7???
What do you suggest?
An auto generated changelog given by mission planner after if compares your current firmware and your target firmware, is I guess what you are after here.
you can’t automatically generate a changelog… many times what is listed, for example in 3.6.0, is obsolete in 3.6.7… only a human can do the edits
That would require an ever increasing amount manually generated manual change logs. For every release they would have to produce a changelog for EVERY previous firmware. I do not think this is feasible or worth anyone’s time.
And by automatically, what I meant was: fetch the dev generated changelog and automatically truncate to the relevant firmwares.
I agree with you about things becoming obsolete in newer versions, but like I said previously, maintaining this list of obsolete changes for every previous firmware is, IMO, not worth it. I suggest the stable-release to be the “checkpoint” where prior to the previous stable release you do not check for changes that would be obsolete. Those potentially obsolete changes would be listed under that firmware’s changelog.
it’s very easy, all you do is add the changes from 3.6.0 to 3.6.1 to the end of the change log from 3.5.7 to 3.6.0… it’s literally one copy/paste
if a change in 3.6.1 is making an entry in 3.6.0 obsolete, you simply type over the obsolete line
i do it every day while coding, it’s not additional work
Arducopter 3.6.7 on ChiBios:
Mission Planner 1.3.63
Two air crafts tested: 670mm 15x5.5 props and 900 quads. 17x5.5 props
Arm and Take off initiated from Tx, followed by a small mission (Auto mode), RTL: no problem in: Alt hold, Loiter, Pos hold.
However same problem using:
[CTRL] [F] and arm and take off {For guided mode} Initiated from Mission planner
Immediate flip over on take off. Props damaged etc… That is on the same air crafts mentioned above.
It seems that a delay between ARM and Takeoff could be beneficial to let the motors come to speed after the arm and before take off.
Not really sure if this is Mission planner problem or AC 3.6.7…
Anyway beware of this strange behaviour.
Henri
Any chance of retrieving 3.6.6 out of somewhere ?
I’m still having issues with copter not disarming after land, and slowly going for a flip, now on two different machines.
And MP, both stable and beta offers only 3.5.7 as “older firmware”
1 Like
Anyone tested SRXL for Spectrum radio? I needed to use the developer build to get it to work a few days ago… As always thank you so much for the hard work.
Same for me, cotper didn’t detect landing
Detecting landings is tough but I’m not aware of any software changes that would have affected this so I think it’s environmental.
As suggested above, it would be good if people facing trouble did a series of tests with older and newer firmware to show there is or isn’t a difference. Copter-3.6.6 for example is available through the Beta MP’s “Pick Previous Firmware” link. I think the “AP 3.6.6” option is actually Copter 3.6.6. I’ve ping’d Michael Oborne about the typo.
For my little experience everytime i reflash 3.6.7 i restart getting flips on RTL when landing. Maybe just a coincidence but i settled back to 3.6.6 and not a prob anymore.
Corrado
I have the very similar experience of flipping just after auto-landing using copter 3.6.7.
The large octa-quad we built haven’t had this kind of problem with copter 3.5.7 and 3.6.4.
I hope your team can clear this issue very soon.
Thank you always for your continuous efforts of maintaining ardupilot firmwares.
Hi Jongmok,
I’ve heard a few reports like this but as far as I know we haven’t changed anything in this area compared with 3.5.7. Older versions of AP are available, I’m wondering if you would be willing to do some tests with the current and earlier versions to see if there is any difference? I suspect the difference is just environmental and actually not related to the software but I could be wrong of course.
Don’t know if what i experienced could be related to the latest problem on landing. I had a few flips on landing lately and never had any before. For other reasons i dropped one of the 2 gps i had on board on wich i had blemd enabled and all landing probs disapperead.
To me it looked like the Quad kept on try to move even when it was on the ground, as said, removing gps blend cured my prob. Don’t know if it is a coincidence or maybe in some way related.
1 Like
Two GPS with blending on my frame too.
You look like to have same issue as me.
Try using just one and see if the problem goes away as it did on mine.Hopefully i found something interesting for the devs to look at.
Corrado
1 Like
Thanks for that. It is interesting for sure especially if others can replicate it. The position estimate is certainly important for a good landing. If the position estimate (which comes partially from the GPS) is moving around a lot as the vehicle lands then this could cause the landing detection to fail.
As a side note, my standard development IRIS has two GPSs enabled and I haven’t noticed a problem on landing - but this doesn’t prove or disprove whether two GPSs is related.
Thank you very much for your reply. I tried to find if the landing problem occurs with copter 3.6.2 as well.
I haven’t experienced any landing problems at all with copter 3.6.2. All hardware configurations are the same.
Is there any change in the landing detection algorithm of 3.6.7 version?
After a small hiatus rebuilding for less vibes and stealing a Tallysman GPS RF-end off a derelict A2, I flew a couple of missions today on 3.6.6 and both auto-landings were detected correctly. I’ll try to clock in 4-5 more tomorrow, as the weather forecast looks nice, then come monday I’ll go back to .7
Hi,
I am using pixhawk 2.4.8 and i had updated my firmware with copter 3.6.7. While flying i faced the issue of continuous yaw movement.Even after switching to RTL, issue continues.I am trying to switch from 3.5.7 to chibios(3.6 +) but none of these updates are as good as 3.5.7. Lots of weird issues occurs due to which again and again i have to switch to 3.5.7.
Attaching the screenshot of log.
Also attaching the logs