search

smashyanand / ardupilot-mega

Automatically exported from code.google.com/p/ardupilot-mega
0 stars 0 forks source link

CLI - setup - show: All of the gain values and cross track values show up wrong #140

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Use the CLI to go into setup mode
2.Do "factoryreset", then "show"
3.

What is the expected output? What do you see instead?
Expect to see gain values as they are in the config file.  Instead they are a 
mess.  See example below

Gains:
P,I,D,iMax: -26214, 16281, 0, 0
P,I,D,iMax: 0, 16384, 0, 0
P,I,D,iMax: 0, 0, 0, 16672
P,I,D,iMax: -13107, 16076, 0, 0
P,I,D,iMax: 26214, 16166, 0, 0
P,I,D,iMax: 0, 16256, 0, 0
P,I,D,iMax: 0, 16128, 0, 0
P,I,D,iMax: -10486, 16035, -10486, 15651
kff: -13107, 15948, 0
XTRACK_GAIN: 0
XTRACK_ENTRY_ANGLE: -27600

What version of the product are you using? On what operating system?
R944

Please provide any additional information below.

Original issue reported on code.google.com by dewei...@gmail.com on 27 Sep 2010 at 5:16

GoogleCodeExporter commented 9 years ago 
Those values are only to debug the output, which seems to be broken for you.
I don't think we need to add more text or feedback as it makes the code heavier 
than it needs to be. I would rather it not have any feedback. Let the GCS 
handle that.

Original comment by jasonshort on 27 Sep 2010 at 5:27

GoogleCodeExporter commented 9 years ago 
No, wasn't suggesting more text or feedback, but I was expecting that if the 
values in the config file for case_servo_roll are 1, 0, 0, 0, then shouldn't 
the values dispayed when you select show (after doing factoryreset) match that? 
 Isn't this just a formatting error or type conversion error?

I'll poke into it later if you don't get to it.  Today I'm just trying to go 
through everything from scratch like a noob and see everything that comes up 
unexpected.

Original comment by dewei...@gmail.com on 27 Sep 2010 at 5:37

GoogleCodeExporter commented 9 years ago 
Somethings wrong. Are you using Arduino 19? those could be floats mis-printed. 
I'll check the code again, but it was working for me saturday.

Original comment by jasonshort on 27 Sep 2010 at 5:40

GoogleCodeExporter commented 9 years ago 
Yes, using Arduino 19

"Somethings wrong." - yes, that's why I entered an issue - LOL ;)

Original comment by dewei...@gmail.com on 27 Sep 2010 at 5:43

GoogleCodeExporter commented 9 years ago 
printf_P was setup by Arduino without float printing capability.

Original comment by jasonshort on 28 Sep 2010 at 6:42