AM32 2.18 didnt work

ArduCopter Copter 4.6
1

Strange day. Used passthrough to configure my holybro tekko 60A esc. Just wanted to change the braking. After changing just the braking one motor reversed its self. I thought this would be a good time to flash from 2.16 to 2.18. Nothing worked. No motor spin at all with identical settings. Twice went back to 2.16 then 2.18. Didnt try 2.17.
Not sure why but ESC just dead with AM32_TEKKO32_F421_2.18
Using arduplane 4.6.0

3

Yeah, having a similar fight. Skystar Talon 40a. ā€œhey, since Iā€™m here Iā€™ll update itā€¦ā€ The flash failed at 50% and now itā€™s bricked. Iā€™ve got an ST-Link if anybody knows the pin outā€¦

AC4.6.1

Edit: Rolled back to 2.17 and things seem to be working again.

4

Are these the X500 ESCs supplied by Rotor Geeks that youā€™re testing on, @Allister ?

5

Ah, just saw your post here ESC.Err in AM32 - #6 by Allister as well, looks like youā€™ve been working with the new firmware on the class kits. Iā€™m interested to hear if the faster update rate resolves some issues.

6

Yup they are. Same ESCs on BLHeli32 have been flawless, but AM32 had had some surprises. That said I turned on extended telemetry on my bench tester and Iā€™m able to see voltage and temperature, along with the usual RPM. It was also reporting current data but it looked pretty flat line so I wonā€™t know till we fly it if thatā€™s any use.

Weā€™ve decided to run the Dshot rate at triple loop (1200hz). Weather permitting my colleague will be testing on Friday. Iā€™ll be gone on some holidays but Iā€™ll let you know how it goes when I hear back.

2 Likes
7

Iā€™m running triple loop also and havenā€™t had a desync yet. Mine are the holybro tekko singles.

1 Like
8

Seems I now have 2.18 installed and working.

Holybro Tech support said AM32_TEKKO32_4IN1_F421 was the correct firmware for my ESC even though The AM32 configurator did not offer AM32_TEKKO32_4IN1_F421 as suggested firmware and in fact, it issued warnings that it was wrong and would brick the unit. All previous firmwares were not 4in1 even though the unit was.
After a 2 hour struggle i now have the 3 connected ESCs (VTOL) with 2.18 and passing the motor test.
The configurator twice failed midway through firmware installing (I have ardu 4.6.1) and it looked for a while like 2 channels were bricked but after many reboots I got it to talk. It always failed with ā€˜onlineā€™ firmware and only worked with ā€˜localā€™ files.
This really is such a trauma, updating AM32.