-
Notifications
You must be signed in to change notification settings - Fork 17.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pixhawk and EMAX ESC #2094
Comments
This is not an APM software issue, nor is it an issue with the Pixhawk hardware. This is an issue with the Emax ESC. |
I've reopened this issue at least as a place holder. The issue appears to be that the Emax ESC gets confused by the high signal that the Pixhawk outputs at startup. The APM2 for example outputs a low signal on startup. I'm afraid it's a fairly low level change in the PX4Firmware layer which I'm not personally going to be able to resolve I think. Perhaps another developer can look into it or maybe the EMAX ESC people can resolve the issue on their side. There's a related issue to the Parachute here. |
The two components in your circle look like a resistor and a capacitor, not On Tue, Jul 28, 2015 at 2:23 AM, Aldo Vargas notifications@github.com
|
Yes, remove those two components... |
Solved, and also a duplicate of #2033 |
Hi, I thought I should follow up on this issue as it seems quite a few people are modifying their EMax ESCs... I have modified mine and they run fine now - I removed the resistor and capacitor after finding the signal level was very low and getting the meter out. After making this modification however I would now suggest an extra step/improvement to the solution as this modification makes the ESCs no longer work with the EMax program card. To make the program card work again, it is necessary to add a 10k pull down resistor to the signal so that the bidirectional serial communication can work with the program card. Also, just an observation but possibly important, without the pull down resistor the signal line is left electrically floating if the signal lead is unplugged and is only connected to the pin of the MCU in the ESC. The best solution to this is: |
Interesting update on the EMAX ESC issue with Pixhawk: The issue is apparently resolved in the new generation of EMAX Simon ESCs! I was making a new quadrotor and again decided to use Emax Simon ESCs despite their compatibility issue with Pixhawk (as they are by far the cheapest and most available ESC in the local stores here). Before ripping the heat shrink on the ESCs to remove the resistor and capacitor as I had done before, I decided to test them. So I attached them to Pixhawk and the motors started spinning right away! I think EMAX has modified the ESCs to resolve this problem finally, but maybe it's still too soon to jump to this conclusion. I have tested Emax Simon 20A ESCs with Pixhawk, Copter Firmware V3.2 & 3.3 both worked fine. |
I want to use the Emax BLHeli Series 30A ESC(https://emaxmodel.com/catalog/product/view/id/101/s/blheli-series-30a-esc/) with the Pixhawk. Any help would be appreciated. |
@9friday, It seems that the underlying issue is with the ESC itself. I don't think we know for sure if the manufacturer has fixed the issue. If you do buy them please tell us if they seem to work or not. |
Just for information, I can confirm that ESCs called "Emax Formula 45A BLHeli32 32Bit" work quite well with Pixhawk. |
Hi Mbuzdalov, |
@mateoc6, maybe the safety switch is on? Try setting BRD_SAFETYENABLE = 0. Just a random guess.. |
I will check that option, that's a good possibility. Thank you |
I took a look at the setting and it was already set to 0. I will probably search the ardupilot page to see if anyone has posted this before, if not start a new post about it. |
I've faced similar issue with another ESCs. This is due to low resistance on esc signal pin lead to PWM amplitude lowering so ESC couldn't recognise it |
I wonder the need of raising an issue...about Emax ESC and the Pixhawk:
So, please here any one had come over this can share the solution?
Best regards,
The text was updated successfully, but these errors were encountered: