I purchased an ArduCopter kit from DIY and I am having problems with sensor readings in the configurator. The initialization of the EEPROM and transmitter calibration was very easy though a little frustrating until I found out that if position hold or altitude hold are on you cannot calibrate the throttle. My problem, if one exists, is that when I look at the sensor readings, I get nothing when I move the boards. Am I doing something wrong or do I have bad gryos/ac? Even the artificial horizon is static. I do see the stick input when running the visual log but nothing else.
Thanks for the input.
Replies
I finally got it to compile. Here is the result of the test:
8,1,24,0,12,20,7,
ArduPilot Mega ADC library test
3,3,3,0,9,4,4,
5,4,3,0,6,6,7,
7,6,1,0,10,5,1,
8,4,0,0,6,8,11,
9,3,8,0,9,14,10,
5,4,4,0,10,5,10,
17,10,16,0,11,16,14,
8,8,8,0,18,13,22,
24,7,11,0,14,5,19,
24,8,18,0,15,9,14,
17,1,9,0,25,14,21,
4,13,15,0,13,4,26,
15,0,9,0,4,12,23,
22,12,17,0,5,12,12,
22,11,12,0,7,15,5,
24,2,9,0,13,5,17,
16,14,9,0,12,4,12,
16,9,12,0,27,9,11,
16,13,11,0,10,13,12,
10,8,12,0,20,10,19,
10,11,17,0,14,6,15,
13,6,16,0,19,12,17,
10,7,12,0,10,13,10,
6,8,11,0,10,16,18,
11,11,15,0,15,10,16,
11,8,10,0,15,5,11,
16,7,12,0,12,8,17,
10,10,8,0,14,12,10,
11,8,13,0,19,10,4,
12,8,16,0,18,19,14,
20,17,12,0,12,12,14,
11,9,12,0,9,15,15,
16,6,10,0,17,17,16,
15,15,22,0,9,8,14,
6,13,10,0,14,14,13,
8,0,9,0,8,14,16,
5,17,16,0,16,13,14,
0,8,12,0,19,13,13,
8,11,12,0,18,2,10,
6,10,10,0,19,10,20,
4,5,12,0,10,17,11,
16,6,5,0,22,17,20,
10,0,10,0,18,10,15,
19,5,22,0,10,13,2,
8,11,10,0,12,16,13,
14,10,12,0,0,20,14,
6,11,12,0,8,10,15,
10,12,17,0,19,15,12,
15,17,10,0,14,8,16,
18,8,7,0,16,12,16,
22,11,14,0,7,13,12,
9,9,12,0,17,15,12,
8,14,10,0,20,18,14,
20,16,7,0,19,14,14,
14,11,14,0,22,8,21,
0,8,12,0,8,9,20,
1,5,15,0,3,14,19,
11,9,13,0,10,10,8,
12,8,21,0,19,3,16,
13,9,0,0,14,16,14,
7,5,25,0,23,9,11,
18,15,5,0,12,9,20,
17,16,15,0,20,2,17,
12,4,14,0,11,4,12,
9,16,17,0,12,7,17,
3,0,21,0,16,18,8,
7,8,16,0,11,8,14,
13,16,16,0,10,15,13,
14,8,9,0,18,18,21,
17,13,14,0,16,8,19,
6,7,10,0,11,11,14,
4,4,12,0,10,5,15,
14,7,7,0,8,9,20,
9,8,15,0,14,4,11,
11,13,11,0,9,9,21,
8,17,10,0,20,12,5,
23,16,20,0,12,13,15,
14,17,16,0,8,3,17,
19,10,11,0,5,12,9,
23,6,11,0,13,7,12,
17,2,9,0,16,2,19,
15,3,14,0,19,2,13,
11,13,12,0,16,2,17,
6,10,22,0,7,3,15,
21,4,12,0,11,4,7,
16,16,4,0,11,8,19,
19,15,12,0,17,15,20,
13,11,11,0,14,6,19,
5,8,15,0,14,20,19,
7,10,10,0,19,15,12,
9,16,9,0,17,6,10,
10,5,8,0,15,10,9,
6,17,6,0,14,12,17,
15,8,12,0,22,11,12,
16,3,13,0,16,8,16,
16,11,13,0,14,14,19,
5,7,15,0,13,8,18,
14,5,19,0,10,5,17,
3,7,3,0,10,8,16,
18,9,15,0,14,8,9,
15,7,11,0,14,8,15,
6,7,10,0,18,12,14,
17,8,10,0,7,6,18,
12,9,18,0,13,8,15,
12,2,10,0,24,10,12,
12,12,7,0,8,10,10,
19,8,8,0,13,3,22,
10,6,12,0,3,2,19,
3,0,17,0,13,16,18,
22,8,7,0,12,9,6,
7,8,12,0,14,14,11,
7,15,13,0,17,15,9,
13,9,13,0,21,11,18,
18,7,14,0,11,11,22,
9,15,18,0,20,12,14,
18,8,18,0,13,5,13,
13,13,13,0,15,10,17,
7,6,18,0,16,9,13,
15,0,12,0,3,13,21,
19,15,11,0,17,13,8,
9,4,14,0,16,12,17,
5,8,4,0,18,15,21,
20,8,11,0,19,5,9,
10,11,19,0,6,10,18,
11,17,14,0,16,8,5,
0,15,12,0,10,2,16,
10,11,12,0,20,10,7,
15,7,14,0,8,8,9,
18,6,9,0,17,5,21,
14,10,14,0,8,11,22,
12,17,21,0,14,13,11,
Thanks Randy. Yes I am initializing the EEPROM. My pitch axis is at 12.000 and the Roll axis is at 16.00. When I put the artificial horizon on, the horizon moves but not what I would expect. When I look at the raw sensor data the auto level pitch level is at 0 and the pitch adjust is at 0 when the board is level. The auto level roll is at roll level 180 and the roll adjustment is -100. When I rotate the unit i can get the roll level to alternate between -180 and +180. It is very odd and I am not ready to sacrifice my AC to unrestricted flight until I can get it figured out. It has bee suggested that I try this with the motors armed which I will do this morning but I don't think that provide more information than the test flights that I did. I will report the results.
Ed,
sorry to ask an obvious question but of course you initialised the EEPROM using the configurator right?
if not, open up the configurator, change the top right drop-down to Initial Setup and then hit the initialise EEPROM setting.
that could explain why you're getting the weird roll values because the accelerometer offsets could be crazy values.
-Randy
Did you check the "Set RTS on Close" option in the advanced port settings?
Correct baud rate?
Does the top of the configurator say "Reading Flight Data" or give you a flight software version when you click Connect?