we have to do same test (remove the SD) because we assembly another unit all exactly the same, and it works Ok with dhost. we thought it would be something from that pixhawk unit, but it has not too much sense.
Hi Peter,
I tried the following with no success.
- formatted sd card
- removed sd card
- changed blheli32 from 32.6 to 32.4
- tried different blheli suite
- tried changing from auto to fixed timing 16 and 23 degrees
To me looks like something between AC and blheli. As soon as I connect to BL suite I get many warning messages from AC. If a motor does not spin I have to connect it via usb to blheli suite and then they all spin. The motor is not spinning because it has no power, after 10 min beacon is activated on that motor only and there is no way to make it spin even at 100% throttle. It does not seem this affects flight performance at all but it is indeed annoying and very strange that it worked smoothly for 2 weeks and then it started to show this behavior.
I am using tekko32 holybro escs with dshot150, blheli 32.6, AC 3.6.8 on Pixahawk 1.
Thank you!
Edit: From these experiments I conclude that this is probably not a hardware problem because if it was, then I cannot explain why simply connecting the board to the computer makes all motors spin. The strange messages from AC when I connect via blheli passthrough might indicate some conflicts between AC and blheli?
The problem persists. I noticed that even when I connect the copter to blheli suite and then I disconnect it, I am not able to fly because I have many warnings from AC such as bad AHRS, gyros still setting, etc. Initially I disconnected the batteries in order to reboot the pixhawk, but this does not work. Mostly one but sometimes 2 motors do not spin. When I perform the motor test in blheli suite all motors always run perfectly. I am running dshot150 on brand new tekko32 escs and I am using a pixhawk 1 with AC 3.6.8 installed. On my copter I have long range mavlink telemetry, frsky passthrough telemetry, FPV equipment with OSD and a cooling fan. IMU load durning flight is 50%, maybe the motor start problem is due to the fact that the board is overloaded?
I also noticed that I have to use an old version of blheli suite in order to connect my escs and read the blheli settings but I do not know if this is related directly to the motor start problem.
My last option is just to reboot the pixhawk from mission planner (after connecting all escs to blheli suite) without having to unplug the batteries. Keeping current to the escs while rebooting AC might solve the issue temporarily.
This is annoying because dshot150 really improved flight time and vibrations on my copter especially under high velocities, and having the telemetry is a great thing that allow to monitor escs health in real time.
Any help is appreciated!
I tested again and it seems that if I reboot the pixhawk from Mission Planner without unplugging the battery then the motors always start. So maybe it could be related to the fact that when I plug the battery some escs start slightly after the pixhawk sends the dshot frames. If I keep the battery plugged in then all escs are powered and when the pixhawk is rebooted there is no chance that all 4 escs will not receive the frames.
thats weird! because I did also similar test but the reverse, It you reset the ESC also works, i mean, if you keep the Pixhawk powered (connected to USB) and you do a power reset to the ESCs (disconnect the XT60 and re.plug) then always works.
To me plugging and unplugging does not always work. I was think so but then it happen and I found out that rebooting the pixhawk while keeping plugged the battery works always (until now). It might be a problem related to some escs that are powered slightly after the pixhawk send shot frames to them but I am not 100% sure.
It seems like with the new 3.6.10 version this problem is solved. I noticed that as soon as I power on the copter, the ESC make the power-on tone immediately. This was not the case with 3.6.8 version. I did some flights and there is no need to reboot anymore, all 4 motors spin perfectly.
ok i was having the same issue the best reference was the mission planner video explaining the blheli passthrough i watched it 3 times and it kinda clicked im flying a CUBE with f45a ESC - to be honest its been more than 3 months and i still haven’t flown, main reason i couldn’t get my motors to work when i did they were not in sync - i went back to blheli_32 suit - and my motors are working im doing my due diligence like everybody else before flying -now i can arm- run my throttle up to about 50%
and if i rudder right all the way on my TX transmitter all 4 motors lock and stop- CRASH:SHOWS ON MY HUD. im happy to be where i am no joke. i havent even put rotors on yet.
If anyone has any direction with how to properly get my motors to work so i can tune normally, and MAYBE A LITTLE BIT OF CONFIDENCE WITH THAT PLS?
thanks to everyone contributing and making this community possible.
i came a long way and i keep learning by the minute.
- i actually started yesterday to read how the data logs work.
so excuse me on not posting any physical claim