Gyroscope Response Slow

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Plug in copter to computer and look at flight data

What is the expected output? What do you see instead?
In the Primary Flight Data panel under Flight Data the leveling is really slow.

What version of the product are you using? On what operating system?
1.0.79 on Windows 7

Please provide any additional information below.
When looking at the status of gx and gy they are always 0.

Original issue reported on code.google.com by MRP2...@gmail.com on 8 Oct 2011 at 1:35

[GoogleCodeExporter]

you will need to provide more info.
what firmware have you loaded?
has it worked before?
are you in flight mode or cli mode?

Original comment by Meee...@gmail.com on 11 Oct 2011 at 8:45

• Changed state: Accepted

[GoogleCodeExporter]

I am using firmware version 2.0.47 in the mission planner 1.0.79 
It has worked before but it is not consistent. I am in flight mode directly 
connected to the mission planner. I pick up the helicopter and physically move 
it to test how the senors are working. The flight data that shows yaw and pitch 
will respond very slowly. I believe that the Gyroscope is not sending 
information fast enough. When I do a test flight this shows when the helicopter 
violently leans from one side and will take a while for it to attempt to level 
off. I was wondering if any one has seen this before or how to make it more 
consistent. 

The weird thing is that it will not work and then will work with out changing 
any software. This makes me believe that its a hardware problem. I have been 
testing how I plug things in like the battery and the battery monitor but I 
haven't gotten anything consistent yet. 

Original comment by MRP2...@gmail.com on 11 Oct 2011 at 2:26

[GoogleCodeExporter]

Plugging the battery monitor in before you plug in main lipo power causes the 
gyros to respond real slow or no response at all. If you power up your apm 
BEFORE you plug in battery monitor then you will not have any problems.  I have 
a tlog of this happening from mission planner.  It happens every time I plug in 
battery monitor first.  Now I power up my bec that feeds apm first then I 
plugin battery monitor--no more slow gyros!

Original comment by stevenha...@gmail.com on 28 Oct 2011 at 4:24

[GoogleCodeExporter]

This works. Thank you for your response. Is there anything I can do to fix this 
so I can plug in the battery monitor and power in any order? 

Original comment by MRP2...@gmail.com on 28 Oct 2011 at 4:54

[GoogleCodeExporter]

Plug in main power first then connect your battery monitor cable. That works 
without problems everytime.

Original comment by stevenha...@gmail.com on 28 Oct 2011 at 4:26

[GoogleCodeExporter]

I can confirm plugging in the monitor cable first causes the gyro's to lag 
horribly about 75% of the time.  Plugging in the normal battery power cable 
first seems to correct the issue.  Tested on 2.0.50.

Original comment by rzt...@gmail.com on 23 Nov 2011 at 8:10

[GoogleCodeExporter]

When you guys say "battery monitor cable" what do you mean? The cable to the 
!LiPo balancing plug that uses the onboard voltage divider circuit? The 
Attopilot current/voltage sensor? Something else?

Original comment by analogue...@gmail.com on 23 Nov 2011 at 5:46

[GoogleCodeExporter]

The onboard voltage divider circuit.

Original comment by rzt...@gmail.com on 23 Nov 2011 at 8:00

[GoogleCodeExporter]

Original comment by Meee...@gmail.com on 1 Dec 2011 at 1:31

[GoogleCodeExporter]

I have just experienced this precise symptom with APM1 (2560) + latest 
ArduPlane code ( 2.5 ) + latest mission planner.    I do not have a separate 
battery monitor, and I do not have any non-standard voltage dividers soldered 
onto my board/s ( the boards are stock).

> What is the expected output? What do you see instead?
> In the Primary Flight Data panel under Flight Data the leveling is really 
slow.

I have a single power connection to the APM ( from the BEC to one of the servo 
pins ) , so I cannot connect power in different order. ? 

I ( conveniently) had a spare APM2 handy, and tested it in the same plane, with 
the same firmware version, and all other things plugged identically ( except 
pitot, as my apm2 has no pitot header), and the APM2 operated perfectly. 

My summary:   it's either something specific to the APM1 software that's not 
triggered on an APM2, or its a hardware fault.?   

I am borrowing two other APM1's from friends to see if they all behave the same 
way, and will update if I can determine where the fault lies.   :-( 

Original comment by davidb...@gmail.com on 1 Aug 2012 at 5:37

[GoogleCodeExporter]

related posts, just as a FYI: 
http://diydrones.com/forum/topics/apm-mission-planner-responsiveness
http://diydrones.com/group/arducopter-traditional-heli-user-group/forum/topics/a
rtificial-horizon-sluggish-when-using-voltage-dividers

Original comment by davidb...@gmail.com on 1 Aug 2012 at 6:01