Dongle hangs when application doesn't do a clean exit

[bitcraze-issue-importer]

The dongle will hang if the application using it doesn't do a clean exit like if you Ctrl-C the headless client or the Kinect client. This has also been reported to happen more frequently on Mac OSX in the forums (link).

The error message is:

#!

Dongle communication error
(ackStatus==None)

---

• Bitbucket: https://bitbucket.org/bitcraze/crazyradio-firmware/issue/11
• Originally Reported By: Marcus Eliasson
• Originally Created At: 2013-08-28T23:41:29.000

[bitcraze-issue-importer]

It seems that this doesn't only happen on exit, it also happens during normal use on Mac OSX.

---

Original Comment By: Marcus Eliasson

[Gregorsharpe]

Currently experiencing this bug with a brand-new dongle, crazyflie 2.0 in the VirtualBox image on both a windows and mac host. Seemed okay when I first got the quad up and running, but by the end of the night it couldn't hold a stable connection with the dongle. Very frustrating.

[ataffanel]

What behaviour are you observing? Does the dongle hangs completely to the point that you have to disconnect it from the computer or is do you 'just' loose connection and have to reconnect the copter?

[Gregorsharpe]

The dongle seems to be hanging completely. The desktop application reports success when I ask it to reconnect and I occasionally can spin up the props, only to have it error out soon after.

I tried using the radio with the android app over USB OTG directly after one of these crashes and it worked a treat. Perhaps I've got something funky going on with my VMs.

[ataffanel]

If you can reconnect without removing the dongle from the PC then the dongle is not hanging.

The PC client will consider the copter to be disconnected after a certain amount of packet lost. If there is a lot of radio noise on the channel you use it is possible to get disconnected because the noise is blocking too many packet in a row.

Can you try to set another radio channel and change the datarate to 2Mbps?

[Gregorsharpe]

I changed the channel from 80 to 15, and the datarate up to 2Mbps. Initially this made it difficult to connect to the crazyflie (I moved it right beside the radio to scan successfully) and then managed to get a decent flight (~20 seconds) before the dongle failed again.

The exact message I'm recieving is as follows.

Communication failure

Connection lost to radio://0/15/2M: Dongle communication error (ackStatus==None)

[adjavaherian]

I think when I had this issue, I accidentally flashed the CrazyRadio PA with the CrazyRadio(non PA) radio firmware. Hope that helps!

Sent from my iPony

On Aug 16, 2016, at 8:03 PM, Gregor Sharpe notifications@github.com wrote:

I changed the channel from 80 to 15, and the datarate up to 2Mbps. Initially this made it difficult to connect to the crazyflie (I moved it right beside the radio to scan successfully) and then managed to get a decent flight (~20 seconds) before the dongle failed again.

The exact message I'm recieving is as follows.

Communication failure

Connection lost to radio://0/15/2M: Dongle communication error (ackStatus==None)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[Gregorsharpe]

Could this be an issue if I haven't messed around with the firmware? The dongle should be on stock AFAIK.

[ataffanel]

This is the second report of this problem in a week so something is going on. The other report is also coming from someone using the VM. I created a ticket for this issue #28. Can you tell me, in the ticket #28, what operating system you are running, what version of the VM and what version of virtualbox you are using? This way I can try to reproduce the problem.

[adjavaherian]

Ya, probably not an issue if you didn’t try to re-flash.

ad

On Aug 16, 2016, at 9:44 PM, Gregor Sharpe notifications@github.com wrote:

Could this be an issue if I haven't messed around with the firmware? The dongle should be on stock AFAIK.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub #11 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/ADezkKOnPz3WxZ-i3VcPHTZLWLu5osCqks5qgmeIgaJpZM4Bg8r_.

[Gregorsharpe]

I've been running Virtualbox 5.1.2 on Windows 10 and 5.1.4 on El Capitan, both using the 2016-06 image.

[adjavaherian]

FWIW, I've had issues with Virtual Box 5.x and my MacBook Air. Is VirtualBox running hot? terminal top -o cpu should show you. I've had Virtual Box running > 95% cpu. Something to do with the network drivers, but not sure if its related.

Sent from my iPony

On Aug 17, 2016, at 8:32 PM, Gregor Sharpe notifications@github.com wrote:

I've been running Virtualbox 5.1.2 on Windows 10 and 5.1.4 on El Capitan, both using the 2016-06 image.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[ataffanel]

Thanks for the info @Gregorsharpe, I am continuing on #28.
@adjavaherian I have never seen that but this seems to be a VirtualBox related issue, AFAIK the VM is not using a lot of CPU. If you find a problem with the VM please create an issue in the VM repos.