Bitcraze Forums

Posted: **Thu Dec 22, 2016 12:09 pm**

I just assembled my new Crazyflie. The self test after assembling was exactly the same as in the getting started. Following the getting started I updated the firmware to version 2016.11. After restarting the flie M2 is burning blue and M1 and M4 are both burning red. It would return to this error state after reconnecting the battery. I then reflashed the device using an older firmware (2016.09) resulting in only the M2 burning blue and others off. I have now also reflashed the 2016.11 multiple times, but I still get the same result: only the blue light burns and no prop self test.

This is the output of the client when trying to connect to it:

Code: Select all

INFO:cflib.crazyflie:Callback->Connection initialized[radio://0/2/2M]
INFO:cflib.crazyflie:We are connected[radio://0/2/2M], request connection setup
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Callback->Connected to [radio://0/2/2M]
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Closing link
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Resending for pattern (93, 5)
INFO:cflib.crazyflie:Callback->Disconnected from [radio://0/2/2M]

I'm running the latest bitcraze VM. The only change I made was update the bitcraze software, I did not update/upgrade any Ubuntu packages.

Posted: **Thu Dec 22, 2016 12:24 pm**

After many times reflashing it has now succeeded. I enabled 3D acceleration for the VM after which the device was flashed successful. My guess is there is a performance or lag problem with the Crazyradio PA in the VM. After successfully flashing the device it would connect fine, but there is a lot of connection loss even though the the link quality is about 90%. I also still get loads of these

Code: Select all

INFO:cflib.crtp.radiodriver:Dongle reported ACK status == None

messages. Battery level is fine so that couldn't be the problem.

Posted: **Thu Dec 22, 2016 1:50 pm**

Hi,

Have you updated the client to the latest version using the update-all script? There used to be a similar bug with the VM but is has been fixed: https://github.com/bitcraze/crazyflie-l ... /issues/15

Also have you updated the Crazyflie with a recent zip release? The resending should not happen anymore with recent firmwares.

/Arnaud

Posted: **Thu Dec 22, 2016 2:25 pm**

Yes, I have updated everything and checked the git log. It's all up-to-date. I think the connection issues were due to faulty flash attempts. The trouble I'm now facing is that I still have packet loss at 2Mhz and a good link quality. I tried the https://github.com/bitcraze/crazyflie-l ... io-test.py program, but it seems to only return NaN values and a lot of warnings concerning incorrect usage of numpy. (medians of empty arrays etc)

Posted: **Tue Jan 03, 2017 12:32 pm**

I have seen some bug recently with the VM and USB. Are you on Windows? If so you can try a Windows build: https://ci.appveyor.com/project/bitcraz ... /artifacts. Please report if it works better, it would allow me to confirm if we have a problem with the VM.

/Arnaud

Posted: **Tue Jan 03, 2017 1:07 pm**

I hadn't had time to react, but I have problems in the VM and on windows with 2 machines, a desktop and a Surface Pro 3. I'll list the USB host controller names if you're interested.

It works fine on native linux on another thinkpad laptop.

Posted: **Tue Jan 03, 2017 1:19 pm**

You mean that the windows native client also has the same problem?

Posted: **Tue Jan 03, 2017 1:40 pm**

Yes that's what I meant

Posted: **Wed Jan 04, 2017 9:06 am**

OK, that I have never seen. What driver have you been installing with Zadig: libusb0 of libusbK? If you have installed one can you try with the other?

Bitcraze Forums

Can't connect after OTA firmware update

Can't connect after OTA firmware update

Re: Can't connect after OTA firmware update

Re: Can't connect after OTA firmware update

Re: Can't connect after OTA firmware update

Re: Can't connect after OTA firmware update

Re: Can't connect after OTA firmware update

Re: Can't connect after OTA firmware update

Re: Can't connect after OTA firmware update

Re: Can't connect after OTA firmware update