double2double / ardupilot-mega

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

Cruise airspeed not initialized correctly #184

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Set AIRSPEED_CRUISE to 10 as in config.h
2. Run factory setup
3. Observe that cruise airspeed is too low in operation

What is the expected output? What do you see instead?
airspeed_cruise is set to 10 rather than 1000

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

Please provide any additional information below.
Please confirm that this is indeed an error and I can correct it.  The line
  airspeed_cruise                = AIRSPEED_CRUISE;
in setup.pde would be changed to
  airspeed_cruise                = AIRSPEED_CRUISE*100;

Original issue reported on code.google.com by bjpcalt...@gmail.com on 12 Oct 2010 at 12:34

GoogleCodeExporter commented 8 years ago
Thanks,  I noticed this issue as well just before I left town on a trip.  I 
will get it corrected.

Doug

Original comment by dewei...@gmail.com on 12 Oct 2010 at 2:29

GoogleCodeExporter commented 8 years ago
This issue was closed by revision r1247.

Original comment by bjpcalt...@gmail.com on 12 Oct 2010 at 7:21

GoogleCodeExporter commented 8 years ago
I did this modification with no success
eeprom.pde write a byte and it is bigger than a byte now
eeprom_write_byte((byte *)      EE_AIRSPEED_CRUISE,         airspeed_cruise);

Original comment by mbada...@gmail.com on 12 Oct 2010 at 8:48

GoogleCodeExporter commented 8 years ago
I did this modification with no success
eeprom.pde write a byte and it is bigger than a byte now
eeprom_write_byte((byte *)      EE_AIRSPEED_CRUISE,         airspeed_cruise);

Original comment by mbada...@gmail.com on 12 Oct 2010 at 8:48

GoogleCodeExporter commented 8 years ago
Thanks for the update -- what you've listed is a separate issue due to 
airspeed_cruise not being converted back into m/s before being written to the 
EEPROM.  I'll fix it in the next 10 minutes.

Original comment by bjpcalt...@gmail.com on 12 Oct 2010 at 9:18