Discussions

2.0 APM_Config.h ???

Posted by Joe on March 12, 2011 at 5:17pm

Just loaded the 2.0.

Unless I installed the 2.0 APM software incorrectly, I see some significant changes have been made that are not making sense. Where are all of the variables that can be changed or enabled/disabled such as type of gps, airspeed sensor etc. as in the previous APM versions. 

This does not correlate with anything in the APM manual/wiki. 

I have read the instructions in the new APM_config.h but can make no sense of it. Where are the various items that can be selected and or modifed.

For example how to change the gps type or enable the airspeed sensor.

The previous  APM_config.h in the previous versions seemed fairly straight forward, add or delete //, chose enable or disable.

What am I missing?

--------------------------------------------------------------------------------------------------------------------------------------------------

// -*- tab-width: 4; Mode: C++; c-basic-offset: 4; indent-tabs-mode: t -*-


// This file is just a placeholder for your configuration file.  If you wish to change any of the setup parameters from
// their default values, place the appropriate #define statements here.

// For example if you wanted the Port 3 baud rate to be 38400 you would add a statement like the one below (uncommented)
//#define SERIAL3_BAUD        38400


// You may also put an include statement here to point at another configuration file.  This is convenient if you maintain
// different configuration files for different aircraft or HIL simulation.  See the examples below
//#include "APM_Config_mavlink_hil.h"
//#include "Skywalker.h"

// If you want to do a hardware-in-the-loop (HIL) simulation with a flight simulator, such as Xplane, uncomment the following lines by removing the "/*" and "*/"

/*
#define HIL_PROTOCOL        HIL_PROTOCOL_MAVLINK
#define HIL_MODE            HIL_MODE_ATTITUDE
#define HIL_PORT            0
#define GCS_PROTOCOL        GCS_PROTOCOL_MAVLINK
#define GCS_PORT            3
*/

---------------------------------------------------------------------------------------------------------------------------------------------------

 

 

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –
Follow

Replies

  • 3D Robotics
    Chris Anderson March 12, 2011 at 5:50pm
    As I said in the APM 2.0 announcement post, this is beta software and the manual will not be fully updated until we release the final version. All that stuff in the old APM_Config.h file is now no longer necessary. GPS is now autodetected, and all GCS functions are now handled by MAVLink. Most other variables can be set through the CLI (such as enabling magnetometer or airspeed sensor) or GCS.

    If you want to put #defines in the APM_Config.h file, you still can. But it's no longer required.

    Please see my announcement post for more on this: http://www.diydrones.com/profiles/blogs/apm-20-beta-released

    If you're not comfortable using the beta software before it's fully documented, please don't use it and stick with APM 1.02 instead. Remember, 2.0 is just for beta testers!
  • Ken March 12, 2011 at 5:47pm

    Read APM_Config.h.reference

    It explains the defaults, gives options if you wish to change something.

This reply was deleted.

Activity