Page 1 of 1
Nano 2.0 dropping signal when flight data polled too quickly
Posted: Wed Feb 04, 2015 11:23 pm
by jasongd05
I've combined the ramp.py example with the logging example. When I set the logger to 1000ms the drone flies fine, but when I set it to 100ms the drone loses connectivity sporadically (failing on, which is fun...). It seems to happen when I try to vary a control relatively fast. We're trying to figure out how to give the drone a mission and write control loops to have it complete a flight plan, so which polling is important.
Thanks in advance.
Jason
Re: Nano 2.0 dropping signal when flight data polled too qui
Posted: Thu Feb 05, 2015 9:29 am
by tobias
Could you please share your python file so we can try to reproduce? In the cfclient there is no problem logging at 10ms intervals so it is difficult to guess where the problem lies.
Re: Nano 2.0 dropping signal when flight data polled too qui
Posted: Thu Feb 05, 2015 7:31 pm
by jasongd05
Alright. Here it goes! We are attempting to run the quad from the IPython Notebook with interactive widgets to start.
Here's a link to the notebook. The logging is happening at 100ms, and the control information is sent at 100ms.
If you see any other issues with this notebook, let me know. At the bottom we have some telemetry data that doesn't make a lot of sense. We've moved the quad in a straight line on the y-axis, the output from the accelerometer seems to show it moving diagonally in the x y plane...
http://nbviewer.ipython.org/gist/jgoad/ ... 4d4836c1ae
Re: Nano 2.0 dropping signal when flight data polled too qui
Posted: Tue Feb 10, 2015 11:02 am
by marcus
Hi,
I tried running the notebook, but the IPython I have doesn't support version 4. Any chance you could export it in a lower version so I can run it with ipython 2.3.0 (Ubuntu 14.10)?
When running the client there's a lot more logging going on and the commands are sent even quicker, so I would guess it has something to do with IPython. What's the CPU load like? Could it be that it's running too slow?