Hi,
I know this has not to do anything with Ardupilot but I hope that someone faced the same issue.
I was flying with a drone with the following hardware: X500 Frame, Pixhawk 6X, T-Motor F55A Pro III ESC and Hacker A20-22L motors, with 11 inch props. The drone flew nicely however, the ESC had a short circuit which i didnt know about caused by banana connectors touching each other so I crashed.
Thankfully the only unit needed to be changed was the ESC. I have bought the same exact ESC. Now I can not connect to BLHeli32 and its showing me the issues shown in the image. Ill be super grateful if anyone can help me out or give any suggestions!
which it specifically say that its BLHeli32. The configurator you shared can be applied only for other firmwares…
Quick question, does the other firmwares support rpm readings like BLHeli32? Can you recommend me which one could be the best in terms of rpm accurate readings?
What do you mean? It already have a BLHeli32 firmware in it. I just can not read the firmware for whatever the reason is
One last question: Would it be possible to flash AM32 on an ESC that already have BLHeli32?
if yes, is there any documentation or steps somewhere that I can follow?
It’s probably the same hardware, it just depends on when it left the factory what firmware it has. Old stock will have BlHeli32, new stock will have AM32. As pointed out BLHeli32 is dead so they may not have anything to exchange.
I’ve read it is possible to flash AM32 but it can be very difficult and a very good chance that things go bad.
Yes, if they claim they sell that ESC with BLHELI32.
They should be able to order one with BLHELI32 at T-Motor.
Holybro for example switched from BLHELI32 to AM32 because it was too complicated to flash AM32 onto BLHELI32 ESCs.
T-Motor should still have the firmware.
So after this discussion I have bought AM60 II from this store that claims it have AM32.
I have installed AM32 because I feel that I could not fully trust webserial connection. I managed to connect to ESC#3 but all the other ESC’s is not able to connect.
It seems that this issue is common with different flight controllers and not only with BLHeli32 but also other esc firmware. I will add to this post title AM32 up until someone have an idea about what im facing.
I was on Pixhawk 4.5.6 bdshot and updated to 4.5.7 stable release version but still I have the same issue.
I need to make sure that my motors are behaving all equally, and that i can log rpm data. I am not sure if the configurator would help me out for that or not. Ill be grateful for any suggestions.