ESC calibration with Qgroundcontrol: "calibration failed timeout waiting for bat"

#1

Hi

I am working with a pixracer and a Qbrain 4x25A ESC. I tried doing the ESC calibration through QGroundControl but got the message “calibration failed timeout waiting for bat”. I measured the voltage across the battery pack and it seems ok.

I haven’t configured the RC because I don’t have the receiver yet. Should I configure first the RC? Or should I be able to do the ESC calibration right now?

Thanks in advance and apologies for opening two threads in such a short timeframe.

#2

are you powering the pixracer with a power module which has voltage and current sensors?

#3

I’m using an ACSP5 power supply and this battery http://www.aliexpress.com/store/product/new-KingMax-1500mah-25C-11-1V-3S-RC-lipo-battery-for-RC-airplane-helicopter-1223765/704742_470292636.html

But it is working now. I added more memory and processing power to the virtual machine and it seems to work better overall.

Now the issue I have is that when using Qgroundcontrol to bind the RC receiver I get a ‘bind command not supported message’.

#4

You need to update the software on the autopilot. Try the latest beta of PX4.

#5

I tried the beta last Thursday. Should there be a change since then?

#6

I have the same problem: the ESC’s calibrate fine when I connect them to a CC3D flight controller, but the Pixracer + ACSP4 power board result in the “calibration timeout waiting for bat” error. Using QGroundcontrol 3.0, flashed the pixracer with standard, beta and master firmwares, same result.

#7

Anyway, could anyone explain to me what this error means? Is my power distribution board shot? Or the pixracer?

#8

Do you mean qgroundcontrol by virtual machine?If yes how you added more memory and processing power to it?

#10

When i am calibrating ESC in Qgroundcontrol, I am getting error in Octo cox airframe "calibration failed timeout waiting for bat”,
My Qgroundcontrol version is v3.2 and Firmware is 1.7.

Help me
Thank you.

#11

Hey guys. This has happened with my grouup as well with our Pixhawk, and it was a silly thing but if you are just powering the Pixhawk through USB instead of through the power port on it with the Power Module that comes with the Pixhawk, it will give you this issue. So the “waiting for bat” is referring to power coming into the power port of the Pixhawk. I suppose then if you are doing this and still facing issues, then perhaps you start at testing out the port and such before moving on to trying other firmware or different ESCs or debugging your PDB (like we did).