[SOLVED] WARNING:cflib.crazyflie:Got packet on header (15,3) but no callback to handle it

[TheYoyoFreak]

Let me start off by mentioning that I'm using a Macbook Pro. I am able to get my Crazyflie 2.0 connected to the Crazyradio PA dongle. However, after connecting I get this persistent warning dialogue like so:

Warning

I'm a beginner to all this and would really appreciate some assistance with this problem, That's only 1 of my many problems. I'll post the other problems soon.

[chad]

Hi,

Welcome to the forum. To help troubleshoot we'll need a bit more info. How about the following:

1) What are you running the client on (VM or native on Mac)
1a) If you're using the VM, what version are you using (ie. 0.6)?
2) How are you starting the client?
3) What version of the client are you running?
4) Have you updated the Crazyflie 2 firmware?
5) What controller are you using?
6) Is the Crazyflie flying even though you're getting the warning?

Also, you can run the client directly on your Mac if you want. I'm happy to link you to the instructions and help you through it if you wish.

[TheYoyoFreak]

Thank you for answering me so soon.
1) I am using VirtualBox
1a) Bitcraze VM 0.6
2) I just start the Bitcraze VM after I turn on Virtualbox
3) I'm not quite clear on what the client is
4) I used the bootloader window and updated firmware
5) The manufacturer of my controller is Holtek, it's a third party xbox 360 USB controller
6) Yes, my Crazyflie is flying, its just seems a tad slow in some ways when using the controller. That persistent warning keeps popping up in the terminal....of course.

Also, I think some dialogue about packet loss popped up? It was probably because my Crazyflie ran out of battery.

I though that the virtual machine was the only way of flying it? I am willing to try anything to get this situation resolved. Talk with you soon, thanks.

[chad]

The "client" is the application you are running to fly the Crazyflie. Since you're using the VM, I'm guessing you're launching it by double-clicking the icon on the desktop.

Another icon on the desktop is the "Update all projects" icon. Double click this so you can update the client source files. Then try running the client again and connecting to the Crazyflie. Let us know what the console output is.

The third-party controller you're using may or may not have as fine grained control as Microsoft controllers. Others have found mixed results with third-party controllers. If it is a high-quality controller it may have good fidelity but if not it might make it harder to fly. The only good way to know is a direct comparison between third-party and genuine controllers.

What firmware did you flash to the Crazyflie? Did you download it from the GitHub firmware releases page?

Finally, it is good to find a clear channel in the Wifi spectrum, especially if you're in a WiFi saturated area. Fortunately, Mac has a good way to do this. Once you've got the ideal channel, you can change it using the "Configure 2.0" menu item in the "Connect" menu of the Crazyflie client after you've connected to the Crazyflie. Once you change the settings, restart the Crazyflie and reconnect to on the new channel.

[TheYoyoFreak]

I did update all projects, I also flashed the firmware from: https://github.com/bitcraze/crazyflie-release/releases
If i read correctly the .zip file is the correct one to flash.

I don't know how to find a clear wifi channel. I'm still getting the Warning dialogue when connecting, I'm assuming that isn't how it should be. Also, the "Actual" Yaw value keeps climbing.

[chad]

I did update all projects, I also flashed the firmware from: https://github.com/bitcraze/crazyflie-release/releases
If i read correctly the .zip file is the correct one to flash.

I don't know how to find a clear wifi channel. I'm still getting the Warning dialogue when connecting, I'm assuming that isn't how it should be. Also, the "Actual" Yaw value keeps climbing.

Screen Shot 2016-01-24 at 11.41.47 AM.png

Good that you updated the projects!
The correct file to flash ends in .bin, not .zip.
Yaw value will keep climbing, that's normal, it's called yaw drift.
I offered a link in my last post to my blog that describes how to use your Mac to find a good WiFi channel (http://blog.crazyflie.net/archives/22-M ... annel.html)
Yes, you should not be getting a the warning. This is what I'm working to diagnose with you right now.
Can you post the information that gets printed to the Console tab in the client after your connect?

[TheYoyoFreak]

I flashed the .bin file at the link you mentioned. I used the Mac Wireless Diagnostic Tool and selected one of the best 2.4 GHz connections. The information on the console was this:

[lgenzelis]

Hi! I'm having the exact same problem. This warning keeps popping in the console of the client.

I'm using a linux pc (ubuntu 14.04), and I'm running the client from the official VM, version 0.6 (a fresh install). I'm running the client by double-clicking the desktop icon. But if I run an example (e.g., basicparam.py) from a console, the same happens. I updated all the proyects and the Crazyflie 2 firmware (to crazyflie2-2015.08.1). I'm using a logitech controller, but that seems to be completely unrelated. The crazyflie flies just fine (well, it drifts too much to my taste, and I can't get it to stay on the air for more than a couple of seconds, but that's probably my lack of expertise..).

Ask me anything you need to know to troubleshoot this.

[arnaud]

Hi,

This is my fault and it has been fixed in the develop branch of the client. This warning is not important so much that my fix was just to remove it: https://github.com/bitcraze/crazyflie-c ... 5dc420L394

The origin of the problem is that I added a packet to return the signal strength from the copter, I piggy packed the signal strength on a NULL packet (the packet (15,3)). This should just be ignored by the client until we use it but instead a warning was printed.

The curious thing is that if you run the last released Crazyflie firmware (the .zip from github https://github.com/bitcraze/crazyflie-r ... /2015.08.1) with the latest released client (the master banch) you should not see this.

If you use the trunk firmware for stm32 and nrf with the client from the develop branch you will not see this warning either.

[chad]

Thanks arnaud! Now I'm not so perplexed.

The curious thing is that if you run the last released Crazyflie firmware (the .zip from github https://github.com/bitcraze/crazyflie-r ... /2015.08.1) with the latest released client (the master banch) you should not see this.

If you use the trunk firmware for stm32 and nrf with the client from the develop branch you will not see this warning either.

Ahh! This explains why I was not able to reproduce the warning. I was first using master for firmware and develop branch for the client but I also tried the 2015.08.1 firmware with latest client on master.

@TheYoYoFreak and @lgenzelis are you sure you truly have the latest source for the cfclient on the master branch?