Copter-4.6.1 released!

Copter-4.6.1 has been released as the official/stable version for multicopters and helicopters.

The changes vs 4.6.0 are in the release notes and copied below

  1. Bug Fixes
  • Prevent firmware erasure on boards using flash for parameter storage
  • bootloaders rebuilt for H7 boards using flash for parameter storage

So there is really just one fix which is to do with occasional firmware wipes on boards the store parameters in flash memory.

Most users will not see any functional difference between 4.6.1 and 4.6.0.

Thanks for those who helped us investigate this problem and we will begin 4.6.2 beta testing early next week!

Randy san

We have verified the operation using the latest ArduCopter firmware.
There are no significant issues; however, when connecting via USB to a computer to download the logs, it takes a considerable amount of time.
Could this be a bug?

ArduPilot V4.6.1 - Google スプレッドシート

1 Like

1 1970-01-01 9-00-00.bin (64.0 KB)

Yeah I am seeing this, but I am not sure why.

2 Likes

MP still shows 4.6.0 but when you upgrade it’s 4.6.1
and yes i know it is a minor detail.

1 Like

Update MP to latest Beta. Mine shows V4.6.1 and it’s likely the reason.

1 Like

Last I did that was a week ago. I’ll try it.

Hi @tomo_waga,

Thanks very much for testing!

I’ve added this to the 4.6 issues list so we will discuss it at tomorrow morning’s meeting.

1 Like

Apologies if this is a dumb question - I’m running Arduplane for a VTOL winged hexacopter. I’m being prompted by MP to upgrade to 4.6.1 with a link to this thread, but does this upgrade apply to plane as well as Copter?

One thing I think I’ve noticed with new builds is that they seem to come up with SLCAN enabled, so each FC has 2x USB ports that show up when you connect to a PC.

This means that if you accidentally select the “wrong” USB port you get something that will work but very slowly.

I realized this when I tried downloading logs from a new plane, and they were very slow on my ZealotH743 that I know can do > 300kbps. I stopped the download and selected the other USB port that showed up for the board and then I got the 300kbps I was expecting.

Note that I usually download with QGroundControl. Just now I tried with Mission Planner and I noticed that if I download using MAVFtp (from the Config page), it’s significantly slower than using the DataFlash Log tab on the Data page.

1 Like

Hi @jp62,

yes, we release new versions for Copter, Plane, Rover and Antenna Tracker all at the same time so 4.6.1 is available for all of them now.

Thanks for using AP!

1 Like

Hello. I’m glad to see the release of 4.6.1. However, when you released 4.6.0, you mentioned that version 4.6.1 would improve the issue of incorrect data from LD06 caused by sunlight exposure outdoors. I have downloaded version 4.6.1 and tested it outdoors, but while LD06 data is relatively accurate indoors, all distance readings become incorrect once outdoors. I hope you can address this issue in the next version. Thank you.

Hi @bcom,

Yes, the fix is included in 4.6.2-beta1 which will hopefully be released for beta testing within a couple of days.

Thank you very much. I’m looking forward to its arrival.

Hi, since upgrading from arduplane 4.6.0 to 4.6.1 I’m no longer able to detect and connect to mission planner app on my android phone via usb c type. Where as it was fine before, it was even able to select the board make and model. I’m still able to power the board via the phone usb c but no connection or detection. Thanks in advance

Hi @dolphin360uk,

Thanks for the report. Could you clarify which autopilot you’re using?

Also I wonder if you could try downgrading to 4.6.0 to confirm you are again able to re-connect? If using Mission Planner to install, there’s an “All Options” link that allows installing older versions of AP.

Thanks again!

Hi @bcom,

4.6.2-beta1 is available for beta testing now so any feedback on the LD06/LD19 is greatly appreciated!

Hello, @rmackay9. I just tested the 4.6.2 beta firmware. However, the LD06 is still performing the same as before. It works really well indoors or at night, but once it’s daytime, it’s back to its old ways—the distance readings become very inaccurate.
This is the effect in the daytime. There is no obstruction in front or behind.

Hi @bcom,

I suspect this is just a weakness of the lidar that we can’t do anything about. Could you go back and try 4.5.7 to see if it is any better? Remember of course that the conditions are important so if possible, back-to-back tests would tell us the most..

Just started getting this message today (that I know of), I had 4.6.0 version installed saw the error and upgraded to 4.6.1 and it remained.

1 Like