Can anyone please point me in the correct direction. I have an old E-sky Belt CP to which I wish to add my APM 1280 board. I have downloaded the new mission planner and see that only 2560 boards are supported for the traditional heli types.
1. Does anyone have code compatible with the 1280 APM boards, or where can I find it?
2. Has anyone else tried it out on a Belt CP?
1. I'm not sure... It might be possible but you might have to go into the code, turn off a lot of functions like CLI and Logging, and then compile and upload. It's just not something we spend a lot of time trying to sort out.
Although... I think one of the not-too-old firmwares did fit on the 1280. Shortly after Tridge did his magic to shrink the code, it fit on a 1280. It may have bloated a bit since then however.
2. I don't think anybody has, but it should be possible? Anything unique about that thing? I see lots of pictures of "V2", not sure which you have or what V1 is. But V2 looks pretty standard other than the swash is backwards with a single servo up front. That might cause a headache.
Thanks for that info. In short it means that it is possible but with changes to the existing code. Does anyone keep versions of the previous code?
We keep older versions of the code in the downloads area but you will have some troubles like for example you will need to add some lines like this to the APM_Config.h.
#define FRAME_CONFIG HELI_FRAME
// DEFAULT PIDS
#define STABILIZE_ROLL_P 0.70
#define STABILIZE_ROLL_I 0.025
#define STABILIZE_ROLL_D 0.04
#define STABILIZE_ROLL_IMAX 2
#define STABILIZE_PITCH_P 0.70
#define STABILIZE_PITCH_I 0.025
#define STABILIZE_PITCH_D 0.04
#define STABILIZE_PITCH_IMAX 2
// yaw stabilise
#define STABILIZE_YAW_P 0.7
#define STABILIZE_YAW_I 0.02
#define STABILIZE_YAW_D 0.0
// yaw rate -- not used
#define RATE_YAW_P 0.135
#define RATE_YAW_I 0.0
#define RATE_YAW_D 0.0
// throttle - rate controller
#define THROTTLE_P 0.22
#define THROTTLE_I 0.1 // updated
#define THROTTLE_IMAX 300
// throttle - altitude controller
#define THR_HOLD_P 0.400
#define THR_HOLD_I 0.020
#define THR_HOLD_IMAX 300
Also I don't think the latest mission planner will work because we've changed some parameter names so you'll have to set-up the swash using the cli (command line interface). I think you'd be better of just buying a 2560 (or an APM2 without the attached GPS).
As a test, I tried compiling the code for the 1280 (you can select the board in Arduino) but it ran out of code space by about 6k..
Yes, if you can just buy a new board, that's the easiest. Unfortunately if you want to run the old board you'll be a little bit on your own. The developers are all busy working on future stuff and we can't always go back to ensure backwards compatibility.