Airplane mode

This forum is dedicated to software development related to MultiWii.
It is not the right place to submit a setup problem.
Software download
PatrikE
Posts: 1976
Joined: Tue Apr 12, 2011 6:35 pm
Location: Sweden
Contact:

Re: Airplane mode

Post by PatrikE »

It should be possible to run without PPM.
Non of the rx-in pins is used for servos.

Reaktor?.. the small EPP?..
I think it will be qite heavy with the Wii stuff on.

But start with low PIID's on gyro ex. P=1 & D=(15-20)
The gyro compenstions should be qite small to avoid wobble.

Take off in passthrumode and test gyro on safe heigt.
Acc can be tested after gyromode is ok :!:

Always be ready to swich to passthrumode to complety take over the control :!:

PatrikE
Posts: 1976
Joined: Tue Apr 12, 2011 6:35 pm
Location: Sweden
Contact:

Re: Airplane mode

Post by PatrikE »

One thing to think of!...

If you fly with throttle all way down.. (Idle or off)
If you give rudder or ail full left it will disarm the card!!!! :?

If possible use a ARM switch in gui!

I will make a change there and only disarm the engine.

User avatar
UndCon
Posts: 293
Joined: Mon Feb 21, 2011 2:10 pm

Re: Airplane mode

Post by UndCon »

Sounds safer to use a killswitch :)

I used it with Spektrum (No PPM) and it was OK

User avatar
Gartenflieger
Posts: 65
Joined: Sat Oct 01, 2011 10:07 pm
Location: Dortmund, Germany

Re: Airplane mode

Post by Gartenflieger »

PatrikE wrote:Reaktor?.. the small EPP?..
I think it will be qite heavy with the Wii stuff on.


I'd think a Promini w/ WMP and connectors should end up < 10 g. With a total weight of maybe 250 g I consider that acceptable.
I use a small Beast 3D, and the gyro makes itusable in moderate gusts. I hope the same of the Reaktor with the MultiWiiPlane.

As to the arming, I think as long as the Throttle is passthrough, no arming procedure is required at all.
Regards
Christoph

PatrikE
Posts: 1976
Joined: Tue Apr 12, 2011 6:35 pm
Location: Sweden
Contact:

Re: Airplane mode

Post by PatrikE »

Iw'e done the first flight test.. :D

Oboy!
Rock steady in wind in gyromode. And Supersmooth Stalls
Accmode was not trimmed but kept a nice left cirkel on 100meters for me.

My settings to start with.
Gyro P=2.0
Acc P=5.0

I utdated respitory with.
Changed Flying wing sevos to match.
Removed ARM for the servos.

Tom
Posts: 5
Joined: Fri Jan 27, 2012 1:59 pm
Location: Chicago US

Re: Airplane mode

Post by Tom »

Thanks Again Patrik !!!
Tom

User avatar
Gartenflieger
Posts: 65
Joined: Sat Oct 01, 2011 10:07 pm
Location: Dortmund, Germany

Re: Airplane mode

Post by Gartenflieger »

Hi Patrik,

I have thrown the parts of the Reaktor together with some glue and a minimalistic MultiWii.
After lengthy setup of the gyro orientation (item is sticking to the side of the plane in an upright orientation) stabilization works fine on the bench.
Everything is moving to the right direction. What's left to do is the servo midpoints and limits.

Only problem is the ESC won't arm, although MWC arming procedure is completed and GUI throttle values move fine. Have to double-check the pinout.
Unfortunately it is -8°C now, too cold for me to go flying.

I was thinking about making the correction decrease with increasing throttle. Then I thought: hmmmm, the software comes with this feature from the first version already: It is the "Throttle PID attenuation".

Best regards an lots of thanks for your contribution
Christoph

P.S. ended up with 320g instead of 250-290g(manual), so more on the heavy side indeed. But I use a 3s 850 and then there is the lights and the bigger-than-in-the-manual servos and the MultiWii. We'll see what it does in the air.

PatrikE
Posts: 1976
Joined: Tue Apr 12, 2011 6:35 pm
Location: Sweden
Contact:

Re: Airplane mode

Post by PatrikE »

Throttle should work on D9 on a ProMini.

You can also connect throttle direct to the RX .
It can be the easiest way.. ;)

I did my testflight in -10°C and wind from Sibiria..
Spain would be nice to live in right now!. 8-)

Small update has been made in resp.

/Patrik

User avatar
Gartenflieger
Posts: 65
Joined: Sat Oct 01, 2011 10:07 pm
Location: Dortmund, Germany

Re: Airplane mode

Post by Gartenflieger »

OK, fixed D9,had a short in my Promini-WMP package.
I have added a set of defines for the servo min,Max,mid,reverse and a function mapping the full input range to the constrained output range.
I had a lot of gyro noise on roll, added a low pass and balanced the prop, but have to test the result yet.

Ready to fly, more or less...
Christoph

User avatar
Gartenflieger
Posts: 65
Joined: Sat Oct 01, 2011 10:07 pm
Location: Dortmund, Germany

Re: Airplane mode

Post by Gartenflieger »

SUCCESS !! :D

Temperatures climbed to -5°C today and I dared make a test flight. As it was the first flight for the plane, I flew around in passthrough mode first, some trimming, etc. It is a crisp day, not much wind, but as the site is surrounded by trees, there is almost always turbulence.

Then the moment of truth: after activating the stabilization: Well, rock solid, very relaxed flying 8-) , I am very happy with it.
There is some work left to do: I have to increase the rc rates in the GUI to make it more responsive, and I suspect the expo is not applied in the passthrough mode. It should be the same for passthrough and stabilized mode. However, I could also set it to 0 in the GUI and use the transmitter expo.

Conclusion: A capable and versatile stabilization for small aircraft.
Cost: Promini clone and a crappy WMP clone (used the ziss_dm mod), so 18 USD total (shipping included) plus some connectors.

small airplane stabilizer
small airplane stabilizer


Regards
Christoph

PatrikE
Posts: 1976
Joined: Tue Apr 12, 2011 6:35 pm
Location: Sweden
Contact:

Re: Airplane mode

Post by PatrikE »

Hi Christoph,

Nice to hear that not only i had sucsess with it... 8-)

Your right about Expo.. Passthru sends RX-in direct to the mixer.
What you give is what you get!... :lol:

Expo in the radio is a god idé you may want different settings in different flightmodes.

I have some changes comming for easier setup of the servos.( Not finnished yet)
It will look like this..

Code: Select all

/*  Servosettings Test  */
static int16_t      servoMid[8] = {1500,1500,1500,1500,1500,1500,1500,1500}; // Midpoint on servo
static int16_t   servotravel[8] = {100,100,100,100,100,100,100,100};         // Servotravel in 0% to 100%
static int8_t   servoreverse[8] = {1,1,1,1,-1,1,1,1};                        // Reverse servos by setting -1 
int Save_To_EEprom = 0;

I want to be able to change the config from the Gui.
The serial part is ready and works.
But think i may need help making the graphics.(Type PID settings.)

/Patrik

User avatar
UndCon
Posts: 293
Joined: Mon Feb 21, 2011 2:10 pm

Re: Airplane mode

Post by UndCon »

Very nice!

I finally pressed buy on the Bixler and a few things around it. Target is MultiWii of course
When Properly tested I will add Light weight FPV gear as well.

//UndCon

PatrikE
Posts: 1976
Joined: Tue Apr 12, 2011 6:35 pm
Location: Sweden
Contact:

Re: Airplane mode

Post by PatrikE »

Updated the project in svn.
http://code.google.com/p/multiwii/source/browse/#svn%2Fbranches%2FPatrikE

Added
- Servo mixing for a simple GIMBAL By Bledy http://youtu.be/zKGr6iR54vM
- I2C_GPS

/Patrik

User avatar
Bledi
Posts: 187
Joined: Sat Sep 10, 2011 6:36 pm

Re: Airplane mode

Post by Bledi »

@PatrickE :
You shoud add the Alex's correction :
On sensor.pde :

Code: Select all

   
    magCal[ROLL]  =  1000.0 / abs(magADC[ROLL]);
    magCal[PITCH] =  1000.0 / abs(magADC[PITCH]);
    magCal[YAW]   =  1000.0 / abs(magADC[YAW]);

PatrikE
Posts: 1976
Joined: Tue Apr 12, 2011 6:35 pm
Location: Sweden
Contact:

Re: Airplane mode

Post by PatrikE »

Ok i missed that one.
It's now corrected.

User avatar
Gartenflieger
Posts: 65
Joined: Sat Oct 01, 2011 10:07 pm
Location: Dortmund, Germany

Re: Airplane mode

Post by Gartenflieger »

PatrikE wrote:I have some changes comming for easier setup of the servos.( Not finnished yet)
It will look like this..

Code: Select all

/*  Servosettings Test  */
static int16_t      servoMid[8] = {1500,1500,1500,1500,1500,1500,1500,1500}; // Midpoint on servo
static int16_t   servotravel[8] = {100,100,100,100,100,100,100,100};         // Servotravel in 0% to 100%
static int8_t   servoreverse[8] = {1,1,1,1,-1,1,1,1};                        // Reverse servos by setting -1 
int Save_To_EEprom = 0;

I want to be able to change the config from the Gui.
The serial part is ready and works.
But think i may need help making the graphics.(Type PID settings.)

/Patrik


Yeah, certainly good to set it from the GUI. However, I suggest to use Min and Max values instead of servotravel.
I have implemented that as #defines and it is easy to use:
- Move control surface to extreme point, take note of servo value shown in GUI
- Enter the noted value as extreme point in #define
- upload sketch with modified extremes

I'm not so familiar with the GUI code, maybe we can use a different method:
- use new serial code letter for new function: set_servo_travel
- in the GUI (preferreably a kind of "tab", as there is no room for much more now, set the extreme points using sliders, while the servo travels in real time to the selected position. In other words: move the servo to the desired position with the slider.
- after setting all values, use new GUI button "write extents" to commit values to eeprom.
- so a datagram GUI->MWC would look like "T 3 m 1850" to set servo[3] max to 1850

Have to close, runing out of battery...
Regards
Chistoph

User avatar
Hamburger
Posts: 2578
Joined: Tue Mar 01, 2011 2:14 pm
Location: air
Contact:

Re: Airplane mode

Post by Hamburger »

Gartenflieger wrote:I'm not so familiar with the GUI code, maybe we can use a different method:
- use new serial code letter for new function: set_servo_travel

no inflational use of command chars, please.
If you intend to read/write presets (like PID values), just extend the existing mechanism.

msev
Posts: 186
Joined: Thu Apr 14, 2011 11:49 am

Re: Airplane mode

Post by msev »

Nice job guys... Patrik what kind of hardware are you using? Has someone already tried how autolevel works?

PatrikE
Posts: 1976
Joined: Tue Apr 12, 2011 6:35 pm
Location: Sweden
Contact:

Re: Airplane mode

Post by PatrikE »

Hi msev,

Promini.
WMP
NB

And yes The autolevel works after Acctrim.

User avatar
Gartenflieger
Posts: 65
Joined: Sat Oct 01, 2011 10:07 pm
Location: Dortmund, Germany

Re: Airplane mode

Post by Gartenflieger »

Hi Patrik,
has the Airplane Mod actually made it into the "official" branch?
If yes, I would not want to put any effort into any GUI changes now, as the new pretty GUI is being launched (soon?). Once that is available we could set up a general purpose servo mid and travel setup in it, also for the tri-tail and any camera servos.

I am still a big fan of the stabilization and I am actively acquiring new fans in the neighbourhood and the club. Ordered parts for 3 more stabilizers.
A few days ago I have flown my 300g Reaktor in a wind so strong I needed half throttle (little more is sufficient to hover) just to stay in place - rock solid!

regards
Christoph

bigbudz
Posts: 5
Joined: Fri Mar 02, 2012 12:11 pm

Re: Airplane mode

Post by bigbudz »

I'm going to try this on my Bigwing Ez this weekend. (http://www.electrickery.info/my-new-ap-platform-bigwingez.php)

Just wondering have people been playing with PID setting? Has it been necessary?

If so, with the code the way it is at the moment, will the serial LCD code still work correctly so I can update in the field??

Cheers

User avatar
Hamburger
Posts: 2578
Joined: Tue Mar 01, 2011 2:14 pm
Location: air
Contact:

Re: Airplane mode

Post by Hamburger »

Yes. Lcd works. Also via bluetooth. Use maybe smaller pid values. Start with p=2. Use passthru to switch back to unassisted flying.
Good luck.

PatrikE
Posts: 1976
Joined: Tue Apr 12, 2011 6:35 pm
Location: Sweden
Contact:

Re: Airplane mode

Post by PatrikE »

P=2 for Gyro is what seems to be enough.
I & D have been left at default.
Increasing P will give bigger throw.

If your gyro feels to sensitive you can activate
GyroSmoothing in the code.

Code: Select all

/* GYRO_SMOOTHING. In case you cannot reduce vibrations _and_ _after_ you have tried the low pass filter options.
 * Option if gyro feels to agressive with servos
 * may try this gyro smoothing via averaging. Disabled for multicopters!
 * Good results for helicopter, airplanes and flying wings (faomies) with lots of vibrations.
 */
//#define GYRO_SMOOTHING {20, 20, 3}    // separate averaging ranges for roll, pitch, yaw


/Patrik

bigbudz
Posts: 5
Joined: Fri Mar 02, 2012 12:11 pm

Re: Airplane mode

Post by bigbudz »

Fantastic, Thanks guys!

Hope the weather holds out!

I'll let you know how I get on :)

bigbudz
Posts: 5
Joined: Fri Mar 02, 2012 12:11 pm

Re: Airplane mode

Post by bigbudz »

OK...Things are not going well :(

I put my platform together and wired everything up. Im using this board: http://www.cadtomotion.co.uk/xcopter.html

I have a Tri and a Quad with these boards and both work with 1.8patch2 and 1.9 firmware fine.

If I load your code onto the board and open the GUI I get GYRO data which is all over the place, the graph is going crazy (right out of the graph box).

I have an ITG3200 connected and no ACC (as yet).

conf.h is below, have I missed somthing really simple ?!?...it's the kid of thing I'd do!!

Code: Select all

 
/* GYRO_SMOOTHING. In case you cannot reduce vibrations _and_ _after_ you have tried the low pass filter options, you
 * Option if gyro feels to agressive with servos
 * may try this gyro smoothing via averaging. Disabled for multicopters!
 * Good results for helicopter, airplanes and flying wings (faomies) with lots of vibrations.
 */
//#define GYRO_SMOOTHING {20, 20, 3}    // separate averaging ranges for roll, pitch, yaw


/* Set the minimum throttle command sent to the ESC (Electronic Speed Controller)
   This is the minimum value that allow motors to run at a idle speed  */
//#define MINTHROTTLE 1300 // for Turnigy Plush ESCs 10A
//#define MINTHROTTLE 1120 // for Super Simple ESCs 10A
//#define MINTHROTTLE 1220
#define MINTHROTTLE 1150

/* The type of multicopter */
//#define GIMBAL
//#define BI
//#define TRI
//#define QUADP
//#define QUADX
//#define Y4
//#define Y6
//#define HEX6
//#define HEX6X
//#define OCTOX8
//#define OCTOFLATP
//#define OCTOFLATX
//#define FLYING_WING
//#define VTAIL4      //experimental The mix is a modified Y4 Mix.

//***********************************//
//**** !!!!   BETATSEST   !!!! ******//
//***********************************//
// Use EXPO in the TX!  EPXO In GUI dont work in PassthruMode.
#define AIRPLANE    // PatrikE Experimental

#define NUM_MOTRORS 0        // Only for use with 490Hz ESC's on Airplane & Heli

//#define HELI_120_CCPM    // PatrikE Experimental
//#define HELI_90_DEG    // PatrikE Experimental
#define CollectivePitch THROTTLE  //  ROLL,PITCH,THROTTLE,YAW,AUX1,AUX2,AUX3,AUX4
//*******************************************************

#define YAW_DIRECTION 1 // if you want to reverse the yaw correction direction
//#define YAW_DIRECTION -1

#define I2C_SPEED 100000L     //100kHz normal mode, this value must be used for a genuine WMP
//#define I2C_SPEED 400000L   //400kHz fast mode, it works only with some WMP clones

//enable internal I2C pull ups
#define INTERNAL_I2C_PULLUPS


//****** advanced users settings   *************
/* I2C DFRobot LED RING communication */
//#define LED_RING

/* This option should be uncommented if ACC Z is accurate enough when motors are running*/
/* should now be ok with BMA020 and BMA180 ACC */
//#define TRUSTED_ACCZ

/* This will activate the ACC-Inflight calibration if unchecked */ 
//#define InflightAccCalibration

/* PIN A0 and A1 instead of PIN D5 & D6 for 6 motors config and promini config
   This mod allow the use of a standard receiver on a pro mini
   (no need to use a PPM sum receiver)
*/
//#define A0_A1_PIN_HEX

/* possibility to use PIN8 or PIN12 as the AUX2 RC input
   it deactivates in this case the POWER PIN (pin 12) or the BUZZER PIN (pin 8)
*/
//#define RCAUXPIN8
//#define RCAUXPIN12



/* Settings for ProMicro, Leonardo and other Atmega32u4 Boards (BETA) */

// activate this for a better pinlayout if all pins can be used => not possible on ProMicro!
//#define A32U4ALLPINS

// activate all 6 hardware PWM outputs Motor 5 = D11 and 6 = D13. => not possible on ProMicro! (untested!)
// if activated:
// Motor 1-6 = 10-bit hardware PWM
// Motor 7-8 = 8-bit Software PWM
// Servos    = 8-bit Software PWM
// if deactivated:
// Motor 1-4 = 10-bit hardware PWM
// Motor 5-8 = 10-bit Software PWM
// Servos    = 10-bit Software PWM
//#define HWPWM6

// aux2 pin on pin RXO
//#define RCAUX2PINRXO

// aux2 pin on pin D17 (RXLED)
//#define RCAUX2PIND17

// this moves the Buzzer pin from TXO to D8 for use with ppm sum or spectrum sat. RX (not needed if A32U4ALLPINS is active)
//#define D8BUZZER

// Inverted status LED for Promicro ver 10.
//#define PROMICRO10

/* end of Settings for ProMicro, Leonardo and other Atmega32u4 Boards */



/* This option is here if you want to use the old level code from the verison 1.7
   It's just to have some feedback. This will be removed in the future */
//#define STAB_OLD_17

/* GPS using a SERIAL port
   only available on MEGA boards (this might be possible on 328 based boards in the future)
   if enabled, define here the Arduino Serial port number and the UART speed
   note: only the RX PIN is used, the GPS is not configured by multiwii
   the GPS must be configured to output NMEA sentences (which is generally the default conf for most GPS devices)
   uncomment the first line to select the GPS serial port of the arduino */
//#define GPS_SERIAL 2 // should be 2 for flyduino v2. It's the serial port number on arduino MEGA
#define GPS_BAUD   115200

/* I2C GPS device made with an independant arduino + GPS device
   including some navigation functions
   contribution from EOSBandi
   http://code.google.com/p/i2c-gps-nav/ */
//#define I2C_GPS

/* Pseudo-derivative conrtroller for level mode (experimental)
   Additional information: http://www.multiwii.com/forum/viewtopic.php?f=8&t=503 */
//#define LEVEL_PDF

/* introduce a deadband around the stick center
   Must be greater than zero, comment if you dont want a deadband on roll, pitch and yaw */
//#define DEADBAND 6

/* if you use a specific sensor board:
   please submit any correction to this list.
     Note from Alex: I only own some boards
                     for other boards, I'm not sure, the info was gathered via rc forums, be cautious */
//#define FFIMUv1         // first 9DOF+baro board from Jussi, with HMC5843                   <- confirmed by Alex
//#define FFIMUv2         // second version of 9DOF+baro board from Jussi, with HMC5883       <- confirmed by Alex
//#define FREEIMUv1       // v0.1 & v0.2 & v0.3 version of 9DOF board from Fabio
//#define FREEIMUv03      // FreeIMU v0.3 and v0.3.1
//#define FREEIMUv035     // FreeIMU v0.3.5 no baro
//#define FREEIMUv035_MS  // FreeIMU v0.3.5_MS                                                <- confirmed by Alex
//#define FREEIMUv035_BMP // FreeIMU v0.3.5_BMP
//#define FREEIMUv04      // FreeIMU v0.4 with MPU6050, HMC5883L, MS561101BA                  <- confirmed by Alex
//#define PIPO            // 9DOF board from erazz
//#define QUADRINO        // full FC board 9DOF+baro board from witespy  with BMP085 baro     <- confirmed by Alex
//#define QUADRINO_ZOOM   // full FC board 9DOF+baro board from witespy  second edition       <- confirmed by Alex
//#define ALLINONE        // full FC board or standalone 9DOF+baro board from CSG_EU
//#define AEROQUADSHIELDv2
//#define ATAVRSBIN1      // Atmel 9DOF (Contribution by EOSBandi). requires 3.3V power.
//#define SIRIUS          // Sirius Navigator IMU                                             <- confirmed by Alex
//#define SIRIUS600       // Sirius Navigator IMU  using the WMP for the gyro
//#define MINIWII         // Jussi's MiniWii Flight Controller
//#define CITRUSv1_0      // CITRUSv1 from qcrc.ca
//#define DROTEK_IMU10DOF
//#define DROTEK_IMU10DOF_MS
//#define DROTEK_IMU6DOFv2
//#define MONGOOSE1_0     // full FC board or standalone 9DOF+baro  http://www.fuzzydrone.org/  <- verified by matbogdan
//#define CRIUS_LITE      // Crius MultiWii Lite
//#define CRIUS_SE        // Crius MultiWii SE

//if you use independent sensors
//leave it commented it you already checked a specific board above
/* I2C gyroscope */
#define ITG3200
//#define L3G4200D

/* I2C accelerometer */
//#define MMA745
//#define ADXL345
//#define BMA020
//#define BMA180
//#define NUNCHACK  // if you want to use the nunckuk as a standalone I2C ACC without WMP
//#define LIS3LV02
//#define LSM303DLx_ACC

/* I2C barometer */
//#define BMP085
//#define MS561101BA

/* I2C magnetometer */
//#define HMC5843
//#define HMC5883
//#define AK8975

/* ADC accelerometer */ // for 5DOF from sparkfun, uses analog PIN A1/A2/A3
//#define ADCACC

/* ITG3200 & ITG3205 Low pass filter setting. In case you cannot eliminate all vibrations to the Gyro, you can try
   to decrease the LPF frequency, only one step per try. As soon as twitching gone, stick with that setting.
   It will not help on feedback wobbles, so change only when copter is randomly twiching and all dampening and
   balancing options ran out. Uncomment only one option!
   IMPORTANT! Change low pass filter setting changes PID behaviour, so retune your PID's after changing LPF.*/
//#define ITG3200_LPF_256HZ     // This is the default setting, no need to uncomment, just for reference
//#define ITG3200_LPF_188HZ
//#define ITG3200_LPF_98HZ
//#define ITG3200_LPF_42HZ
//#define ITG3200_LPF_20HZ
//#define ITG3200_LPF_10HZ      // Use this only in extreme cases, rather change motors and/or props

/* MPU6050 Low pass filter setting. In case you cannot eliminate all vibrations to the Gyro, you can try
   to decrease the LPF frequency, only one step per try. As soon as twitching gone, stick with that setting.
   It will not help on feedback wobbles, so change only when copter is randomly twiching and all dampening and
   balancing options ran out. Uncomment only one option!
   IMPORTANT! Change low pass filter setting changes PID behaviour, so retune your PID's after changing LPF.*/
//#define MPU6050_LPF_256HZ     // This is the default setting, no need to uncomment, just for reference
//#define MPU6050_LPF_188HZ
//#define MPU6050_LPF_98HZ
//#define MPU6050_LPF_42HZ
//#define MPU6050_LPF_20HZ
//#define MPU6050_LPF_10HZ      // Use this only in extreme cases, rather change motors and/or props

/* The following lines apply only for specific receiver with only one PPM sum signal, on digital PIN 2
   IF YOUR RECEIVER IS NOT CONCERNED, DON'T UNCOMMENT ANYTHING. Note this is mandatory for a Y6 setup on a promini
   Select the right line depending on your radio brand. Feel free to modify the order in your PPM order is different */
//#define SERIAL_SUM_PPM         PITCH,YAW,THROTTLE,ROLL,AUX1,AUX2,AUX3,AUX4 //For Graupner/Spektrum
//#define SERIAL_SUM_PPM         ROLL,PITCH,THROTTLE,YAW,AUX1,AUX2,AUX3,AUX4 //For Robe/Hitec/Futaba
//#define SERIAL_SUM_PPM         PITCH,ROLL,THROTTLE,YAW,AUX1,AUX2,AUX3,AUX4 //For some Hitec/Sanwa/Others

/* The following lines apply only for Spektrum Satellite Receiver
   Spektrum Satellites are 3V devices.  DO NOT connect to 5V!
   For MEGA boards, attach sat grey wire to RX1, pin 19. Sat black wire to ground. Sat orange wire to Mega board's 3.3V (or any other 3V to 3.3V source).
   For PROMINI, attach sat grey to RX0.  Attach sat black to ground. 
     There is no 3.3V source on a pro mini; you can either use a different 3V source, or attach orange to 5V with a 3V regulator in-line (such as http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=MCP1700-3002E/TO-ND)
     If you use an inline-regulator, a standard 3-pin servo connector can connect to ground, +5V, and RX0; solder the correct wires (and the 3V regulator!) to a Spektrum baseRX-to-Sat cable that has been cut in half.
     NOTE: Because there is only one serial port on the Pro Mini, using a Spektrum Satellite implies you CANNOT use the PC based configuration tool. Further, you cannot use on-aircraft serial LCD as the baud rates are incompatible. You can configure by one of two methods:
       1) Use an on-aircraft i2c LCD (such as Eagle Tree or LCD03) for setting gains, reading sensors, etc.
       2) Available now: Comment out the Spektrum definition, upload, plug in PC, configure; uncomment the Spektrum definition, upload, plug in RX, and fly.  Repeat as required to configure.
   (Contribution by Danal) */
//#define SPEKTRUM 1024
//#define SPEKTRUM 2048


/* EXPERIMENTAL !!
   contribution from Captain IxI and Zaggo
   cf http://www.multiwii.com/forum/viewtopic.php?f=7&t=289
   The following line apply only for Futaba S-Bus Receiver on MEGA boards at RX1 only (Serial 1).
   You have to invert the S-Bus-Serial Signal e.g. with a Hex-Inverter like IC SN74 LS 04 */
//#define SBUS

/* Failsave settings - added by MIS
   Failsafe check pulse on THROTTLE channel. If the pulse is OFF (on only THROTTLE or on all channels) the failsafe procedure is initiated.
   After FAILSAVE_DELAY time of pulse absence, the level mode is on (if ACC or nunchuk is avaliable), PITCH, ROLL and YAW is centered
   and THROTTLE is set to FAILSAVE_THR0TTLE value. You must set this value to descending about 1m/s or so for best results.
   This value is depended from your configuration, AUW and some other params.
   Next, afrer FAILSAVE_OFF_DELAY the copter is disarmed, and motors is stopped.
   If RC pulse coming back before reached FAILSAVE_OFF_DELAY time, after the small quard time the RC control is returned to normal.
   If you use serial sum PPM, the sum converter must completly turn off the PPM SUM pusles for this FailSafe functionality.*/
#define FAILSAFE                                  // Alex: comment this line if you want to deactivate the failsafe function
#define FAILSAVE_DELAY     10                     // Guard time for failsafe activation after signal lost. 1 step = 0.1sec - 1sec in example
#define FAILSAVE_OFF_DELAY 200                    // Time for Landing before motors stop in 0.1sec. 1 step = 0.1sec - 20sec in example
#define FAILSAVE_THR0TTLE  (MINTHROTTLE + 200)    // Throttle level used for landing - may be relative to MINTHROTTLE - as in this case

/* EXPERIMENTAL !!
  contribution from Luis Correia
  see http://www.multiwii.com/forum/viewtopic.php?f=18&t=828
  It uses a Bluetooth Serial module as the input for controlling the device via an Android application
  As with the SPEKTRUM option, is not possible to use the configuration tool on a mini or promini. */
//#define BTSERIAL

/* The following lines apply only for a pitch/roll tilt stabilization system
   Uncomment the first line to activate it */
//#define SERVO_TILT                //  Simple CameraGimbal By Bledy http://youtu.be/zKGr6iR54vM
//#define SERVO_MIX_TILT            //special simple gimbal by mixing 2 servos By Bledi
#define TILT_PITCH_MIN    1020    //servo travel min, don't set it below 1020
#define TILT_PITCH_MAX    2000    //servo travel max, max value=2000
#define TILT_PITCH_MIDDLE 1500    //servo neutral value
#define TILT_PITCH_PROP   10      //servo proportional (tied to angle) ; can be negative to invert movement
#define TILT_ROLL_MIN     1020
#define TILT_ROLL_MAX     2000
#define TILT_ROLL_MIDDLE  1500
#define TILT_ROLL_PROP    10

/* interleaving delay in micro seconds between 2 readings WMP/NK in a WMP+NK config
   if the ACC calibration time is very long (20 or 30s), try to increase this delay up to 4000
   it is relevent only for a conf with NK */
#define INTERLEAVING_DELAY 3000

/* for V BAT monitoring
   after the resistor divisor we should get [0V;5V]->[0;1023] on analog V_BATPIN
   with R1=33k and R2=51k
   vbat = [0;1023]*16/VBATSCALE */
#define VBAT              // comment this line to suppress the vbat code
#define VBATSCALE     131 // change this value if readed Battery voltage is different than real voltage
#define VBATLEVEL1_3S 107 // 10,7V
#define VBATLEVEL2_3S 103 // 10,3V
#define VBATLEVEL3_3S 99  // 9.9V
#define NO_VBAT       16 // Avoid beeping without any battery

/* when there is an error on I2C bus, we neutralize the values during a short time. expressed in microseconds
   it is relevent only for a conf with at least a WMP */
#define NEUTRALIZE_DELAY 100000

/* this is the value for the ESCs when they are not armed
   in some cases, this value must be lowered down to 900 for some specific ESCs */
#define MINCOMMAND 1000

/* this is the maximum value for the ESCs at full power
   this value can be increased up to 2000 */
#if defined(AIRPLANE)|| defined(HELICOPTER)
#define MAXTHROTTLE  2000        // range must be inside [1020;2000]
#else
#define MAXTHROTTLE 1850
#endif


/* This is the speed of the serial interface. 115200 kbit/s is the best option for a USB connection.*/
#define SERIAL_COM_SPEED 115200

/* In order to save space, it's possibile to desactivate the LCD configuration functions
   comment this line only if you don't plan to used a LCD */
#define LCD_CONF
/* to include setting the aux switches for AUX1 and AUX2 via LCD */
//#define LCD_CONF_AUX_12
/* to include setting the aux switches for AUX1, AUX2, AUX3 and AUX4 via LCD */
//#define LCD_CONF_AUX_1234
/* Use this to trigger LCD configuration without a TX - only for debugging - do NOT fly with this activated */
//#define LCD_CONF_DEBUG

/* choice of LCD attached for configuration and telemetry, see notes below */
#define LCD_SERIAL3W    // Alex' initial variant with 3 wires, using rx-pin for transmission @9600 baud fixed
/* serial (wired or wireless via BT etc.) */
//#define LCD_TEXTSTAR    // Cat's Whisker LCD_TEXTSTAR Module CW-LCD-02 (Which has 4 input keys for selecting menus)
//#define LCD_VT100        // vt100 compatible terminal emulation (blueterm, putty, etc.)
/* i2c devices */
//#define LCD_ETPP        // Eagle Tree Power Panel LCD, which is i2c (not serial)
//#define LCD_LCD03       // LCD03, which is i2c

/* keys to navigate the LCD menu (preset to LCD_TEXTSTAR key-depress codes)*/
#define LCD_MENU_PREV 'a'
#define LCD_MENU_NEXT 'c'
#define LCD_VALUE_UP 'd'
#define LCD_VALUE_DOWN 'b'

/* To use an LCD03 for configuration:
 http://www.robot-electronics.co.uk/htm/Lcd03tech.htm
 Remove the jumper on its back to set i2c control.
 VCC to +5V VCC (pin1 from top)
 SDA - Pin A4 Mini Pro - Pin 20 Mega (pin2 from top)
 SCL - Pin A5 Mini Pro - Pin 21 Mega (pin3 from top)
 GND to Ground (pin4 from top)
 (by Th0rsten) */

/* To use an Eagle Tree Power Panel LCD for configuration:
 White wire  to Ground
 Red wire    to +5V VCC (or to the WMP power pin, if you prefer to reset everything on the bus when WMP resets)
 Yellow wire to SDA - Pin A4 Mini Pro - Pin 20 Mega
 Brown wire  to SCL - Pin A5 Mini Pro - Pin 21 Mega
 (Contribution by Danal) */

/* Cat's whisker LCD_TEXTSTAR LCD
   Pleae note this display needs a full 4 wire connection to (+5V, Gnd, RXD, TXD )
   Configure display as follows: 115K baud, and TTL levels for RXD and TXD, terminal mode
   NO rx / tx line reconfiguration, use natural pins */


/* motors will not spin when the throttle command is in low position
   this is an alternative method to stop immediately the motors */
//#define MOTOR_STOP

/* some radios have not a neutral point centered on 1500. can be changed here */
#define MIDRC 1500

/* experimental
   camera trigger function : activated via Rc Options in the GUI, servo output=A2 on promini */
//#define CAMTRIG
#define CAM_SERVO_HIGH 2000  // the position of HIGH state servo
#define CAM_SERVO_LOW 1020   // the position of LOW state servo
#define CAM_TIME_HIGH 1000   // the duration of HIGH state servo expressed in ms
#define CAM_TIME_LOW 1000    // the duration of LOW state servo expressed in ms

/* you can change the Heli Tail servo travel here */
/* you can change the tricopter servo travel here */
#define TRI_YAW_CONSTRAINT_MIN 1020
#define TRI_YAW_CONSTRAINT_MAX 2000
#define TRI_YAW_MIDDLE 1500 // tail servo center pos. - use this for initial trim; later trim midpoint via LCD

/* Flying Wing: you can change change servo orientation and servo min/max values here */
/* valid for all flight modes, even passThrough mode */
/* need to setup servo directions here; no need to swap servos amongst channels at rx */
#define PITCH_DIRECTION_L 1 // left servo - pitch orientation
#define PITCH_DIRECTION_R -1  // right servo - pitch orientation (opposite sign to PITCH_DIRECTION_L, if servos are mounted in mirrored orientation)
#define ROLL_DIRECTION_L 1 // left servo - roll orientation
#define ROLL_DIRECTION_R 1  // right servo - roll orientation  (same sign as ROLL_DIRECTION_L, if servos are mounted in mirrored orientation)
#define WING_LEFT_MID  1500 // left servo center pos. - use this for initial trim; later trim midpoint via LCD
#define WING_RIGHT_MID 1500 // right servo center pos. - use this for initial trim; later trim midpoint via LCD
#define WING_LEFT_MIN  1020 // limit servo travel range must be inside [1020;2000]
#define WING_LEFT_MAX  2000 // limit servo travel range must be inside [1020;2000]
#define WING_RIGHT_MIN 1020 // limit servo travel range must be inside [1020;2000]
#define WING_RIGHT_MAX 2000 // limit servo travel range must be inside [1020;2000]

/* enable monitoring of the power consumption from battery (think of mAh) */
/* allows to set alarm value in GUI or via LCD */
/* Two options: */
/* 1 - soft: - (good results +-5% for plush and mystery ESCs @ 2S and 3S, not good with SuperSimple ESC */
/*      00. relies on your combo of battery type (Voltage, cpacity), ESC, ESC settings, motors, props and multiwii cycle time */
/*      01. set POWERMETER soft. Uses PLEVELSCALE = 50, PLEVELDIV = PLEVELDIVSOFT = 5000 */
/*      0. output is a value that linearily scales to power (mAh) */
/*      1. get voltage reading right first */
/*      2. start with freshly charged battery */
/*      3. go fly your typical flight (routine and duration) */
/*      4. at end connect to GUI or LCD and read the power value; write it down (example 4711)*/
/*      5. charge battery, write down amount of energy needed (example 722 mAh) */
/*      6. compute alarm value for desired power threshold (example 750 mAh : alarm = 4711 / 722 * 750) */
/*      7. set alarm value in GUI or LCD */
/*      8. enjoy your new battery alarm - possibly repeat steps 2 .. 7 */
/*      9. if you want the numbers to represent your mAh value, you must change PLEVELDIV */
/* 2 - hard: - (uses hardware sensor, after configuration gives reasonable results */
/*      00. uses analog pin 2 to read voltage output from sensor. */
/*      01. set POWERMETER hard. Uses PLEVELSCALE = 50 */
/*      02. install low path filter for 25 Hz to sensor input */
/*      03. check your average cycle time. If not close to 3ms, then you must change PLEVELDIV accordingly */
/*      1. compute PLEVELDIV for your sensor (see below for insturctions) */
/*      2. set PLEVELDIVSOFT to 5000 ( to use LOG_VALUES for individual motor comparison) */
/*      3. attach, set PSENSORNULL and  PINT2mA */
/*      4. configure, compile, upload, set alarm value in GUI or LCD */
/*      3. enjoy true readings of mAh consumed */
/* set POWERMETER to "soft" (1) or "hard" (2) depending on sensor you want to utilize */
//#define POWERMETER_SOFT
//#define POWERMETER_HARD
/* the sum of all powermeters ranges from [0:60000 e4] theoretically. */
/* the alarm level from eeprom is out of [0:255], so we multipy alarm level with PLEVELSCALE and with 1e4 before comparing */
/* PLEVELSCALE is the step size you can use to set alarm */
#define PLEVELSCALE 50 // if you change this value for other granularity, you must search for comments in code to change accordingly
/* larger PLEVELDIV will get you smaller value for power (mAh equivalent) */
#define PLEVELDIV 5000 // default for soft - if you lower PLEVELDIV, beware of overrun in uint32 pMeter
#define PLEVELDIVSOFT PLEVELDIV // for soft always equal to PLEVELDIV; for hard set to 5000
//#define PLEVELDIV 1361L // to convert the sum into mAh divide by this value
/* amploc 25A sensor has 37mV/A */
/* arduino analog resolution is 4.9mV per unit; units from [0..1023] */
/* sampling rate 20ms, approx 19977 micro seconds */
/* PLEVELDIV = 37 / 4.9  * 10e6 / 18000  * 3600 / 1000  = 1361L */
/* set to analogRead() value for zero current */
#define PSENSORNULL 510 // for I=0A my sensor gives 1/2 Vss; that is approx 2.49Volt
#define PINT2mA 13 // for telemtry display: one integer step on arduino analog translates to mA (example 4.9 / 37 * 100



/* to monitor system values (battery level, loop time etc. with LCD enable this */
/* note: for now you must send single characters 'A', 'B', 'C', 'D' to request 4 different pages */
/* Buttons toggle request for page on/off */
/* The active page on the LCD does get updated automatically */
/* Easy to use with Terminal application or display like LCD - uses the 4 buttons are preconfigured to send 'A', 'B', 'C', 'D' */
//#define LCD_TELEMETRY
/* to enable automatic hopping between a choice of telemetry pages uncomment this. */
/* This may be useful if your LCD has no buttons or the sending is broken */
/* hopping is activated and deactivated in unarmed mode with throttle=low & roll=left & pitch=forward */
/* set it to the sequence of telemetry pages you want to see */
//#define LCD_TELEMETRY_AUTO "12345267" // pages 1 to 7 in ascending order
//#define LCD_TELEMETRY_AUTO  "2122324252627" // strong emphasis on page 2
/* Use this to trigger telemetry without a TX - only for debugging - do NOT fly with this activated */
//#define LCD_TELEMETRY_DEBUG  //This form rolls between all screens, LCD_TELEMETRY_AUTO must also be defined.
//#define LCD_TELEMETRY_DEBUG 6  //This form stays on the screen specified.

/* on telemetry page B it gives a bar graph which shows how much voltage battery has left. Range from 0 to 12 Volt is not very informative */
/* so we try do define a meaningful part. For a 3S battery we define full=12,6V and calculate how much it is above first warning level */
/* Example: 12.6V - VBATLEVEL1_3S  (for me = 126 - 102 = 24) */
#define VBATREF 24

/* to log values like max loop time and others to come */
/* logging values are visible via LCD config */
/* set to 2, if you want powerconsumption on a per motor basis (this uses the big array and is a memory hog, if POWERMETER <> PM_SOFT) */
//#define LOG_VALUES 1

/* to add debugging code */
/* not needed and not recommended for normal operation */
/* will add extra code that may slow down the main loop or make copter non-flyable */
//#define DEBUG

//****** end of advanced users settings *************

//if you want to change to orientation of individual sensor
//#define ACC_ORIENTATION(X, Y, Z)  {accADC[ROLL]  =  Y; accADC[PITCH]  = -X; accADC[YAW]  = Z;}
//#define GYRO_ORIENTATION(X, Y, Z) {gyroADC[ROLL] = -Y; gyroADC[PITCH] =  X; gyroADC[YAW] = Z;}
//#define MAG_ORIENTATION(X, Y, Z)  {magADC[ROLL]  = X; magADC[PITCH]  = Y; magADC[YAW]  = Z;}

 
/* frequenies for rare cyclic actions in the main loop, depend on cycle time! */
/* time base is main loop cycle time - a value of 6 means to trigger the action every 6th run through the main loop */
/* example: with cycle time of approx 3ms, do action every 6*3ms=18ms */
/* value must be [1; 65535] */
#define LCD_TELEMETRY_FREQ 23       // to send telemetry data over serial 23 <=> 60ms <=> 16Hz (only sending interlaced, so 8Hz update rate)
#define LCD_TELEMETRY_AUTO_FREQ 667 // to step to next telemetry page 667 <=> 2s
#define PSENSORFREQ 6               // to read hardware powermeter sensor 6 <=> 18ms
#define VBATFREQ PSENSORFREQ        // to read battery voltage - keep equal to PSENSORFREQ unless you know what you are doing
/**************************************/
/****END OF CONFIGURABLE PARAMETERS****/
/**************************************/

PatrikE
Posts: 1976
Joined: Tue Apr 12, 2011 6:35 pm
Location: Sweden
Contact:

Re: Airplane mode

Post by PatrikE »

How are you powering the gyro?
D12 is a servo output in airplane mode and is NOT suitable to power sensors with.
You should use 5V from esc's.

bigbudz
Posts: 5
Joined: Fri Mar 02, 2012 12:11 pm

Re: Airplane mode

Post by bigbudz »

Of course...I should have seen that :oops:

I would have to build a new board to fix this with the hardware...bugger!

As it stands, I don't use the D12 servo as I have a Y-Harness connected to D11. Is there any way of changing the D12 pin back to powering the sensors or am I resigned to building a board from scratch?!?

PatrikE
Posts: 1976
Joined: Tue Apr 12, 2011 6:35 pm
Location: Sweden
Contact:

Re: Airplane mode

Post by PatrikE »

It takes a few changes in the def file..
Remove the pinMapping for servo4 on D12.

Code: Select all

  #define SERVO_4_PINMODE            ; 
  #define SERVO_4_PIN_HIGH           ;
  #define SERVO_4_PIN_LOW            ;


And comment or remove this part

Code: Select all

#if defined (AIRPLANE) || defined(HELICOPTER) && defined(PROMINI)
  #define POWERPIN_PINMODE           ;
  #define POWERPIN_ON                ;
  #define POWERPIN_OFF               ;
#endif


It should work and D12 will be powerPin again.

/Patrik

User avatar
Hamburger
Posts: 2578
Joined: Tue Mar 01, 2011 2:14 pm
Location: air
Contact:

Re: Airplane mode

Post by Hamburger »

Maybe it might help to compile a short list of hints for using Airplane/Helicopter/FlyingWing modes?

Here is what I found so far (from using Flying Wing either for Flying Wing or Pitcheron airlplanes)
  • after physical setup, trim servo midpoints not on TX but via the configuration menu (works for FlyingWing 2 servos, at least. Others?) (if you do not have an LCD, you can use the terminal program from within the Arduino IDE)
  • set rc-expo in MWii to 0 (off). Use expo of your TX instead. Then expo is same for passthrough and assisted flying.
  • not sure about rc-rate, rate seems to differ anyway between passthrough and assisted mode.
  • how to increase the minimum/maximum servo throw for assisted modes (large P, high rc-rate?)

bigbudz
Posts: 5
Joined: Fri Mar 02, 2012 12:11 pm

Re: Airplane mode

Post by bigbudz »

Thanks for the guys...Patrick, you're a gent!

I have everything built, programmed and apparently working!

The only strange behaviour I can see is if I have the plane on the ground, GYROs enabled and I spin up the motor, the ailerons slowly bank to the left and then stay there.

This only happens with the motor running, any ideas?? I would expect a vibration issue to cause erratic behaviour rather than this constant banking?!?

Thanks again!
Kieran

PatrikE
Posts: 1976
Joined: Tue Apr 12, 2011 6:35 pm
Location: Sweden
Contact:

Re: Airplane mode

Post by PatrikE »

Vibrations is a mystery... :?
You can try gyro smoothing and see it it helps.

God luck with the testflight.. 8-)

Noctaro
Posts: 280
Joined: Thu Sep 08, 2011 11:15 am
Contact:

Re: Airplane mode

Post by Noctaro »

is it the same behaviour if motor is disconnected? if so i would tip on some strange mixing of your rc or fc.

greetz Noc

PatrikE
Posts: 1976
Joined: Tue Apr 12, 2011 6:35 pm
Location: Sweden
Contact:

Re: Airplane mode

Post by PatrikE »

I made a small Howto guide for MultiWii Plane.
http://fotoflygarn.blogspot.com/2012/03/how-to-setup-multiwii-airplane-same.html

Is something misseing in it?..

/Patrik

User avatar
UndCon
Posts: 293
Joined: Mon Feb 21, 2011 2:10 pm

Re: Airplane mode

Post by UndCon »

Nice tutorial Patrik.

I will follow this when I get all parts for my Bixler (a few items still missing)
I found a few typos but it looks good.

//UndCon

PatrikE
Posts: 1976
Joined: Tue Apr 12, 2011 6:35 pm
Location: Sweden
Contact:

Re: Airplane mode

Post by PatrikE »

I added the AirplaneMix to shared trunk as it's been tested and behaving well .

Here's a video from a Gyro stabilased AXI .
http://youtu.be/EEEzVf3LQBo

To be able to use D12 as powerpin.
I also added.

Code: Select all

//#define D12_POWER    // Use D12 on PROMINI to power sensors. Will disable servo[4] on D12 


And the Howto is available at
http://fotoflygarn.blogspot.com/2012/03/how-to-setup-multiwii-airplane-same.html

/Patrik

darlofranco
Posts: 13
Joined: Sat Jun 18, 2011 4:16 pm

Re: Airplane mode

Post by darlofranco »

Thanks for the "howto" Patrik

Nice flight ;)

/Frank

msev
Posts: 186
Joined: Thu Apr 14, 2011 11:49 am

Re: Airplane mode

Post by msev »

If flying in a fairly straight line, like for example when flying point to point, distance fpv, could a magneto be used for a crude solution for "return to general direction you came from"? because most of the time when there are problems with video or rc signal you probably just need to fly 500m back from where you came and its all good then..Or is it totally useless on a plane..

PatrikE
Posts: 1976
Joined: Tue Apr 12, 2011 6:35 pm
Location: Sweden
Contact:

Re: Airplane mode

Post by PatrikE »

Just a wild idé..
If you use magMode function and activate with a switch tosave currant direction as magHold-180

Code: Select all

      if (rcOptions[BOXMAG]) {
        if (magMode == 0) {
          magMode = 1;
          magHold = heading-180;
      if (magHold <= - 180) magHold += 360;
      if (magHold >= + 180) magHold -= 360;
        }


Let magMode for multirotors controll the rudder.

Code: Select all

 if (abs(rcCommand[YAW]) <70 && magMode) {
      int16_t dif = heading - magHold;
      if (dif <= - 180) dif += 360;
      if (dif >= + 180) dif -= 360;
      if ( smallAngle25 ) rcCommand[YAW] -= dif*P8[PIDMAG]/30;  // 18 deg
    } else magHold = heading;

Then i think it would then turn back to the direction it came from.?

It could work..

/Patrik


} else magMode = 0;

User avatar
UndCon
Posts: 293
Joined: Mon Feb 21, 2011 2:10 pm

Re: Airplane mode

Post by UndCon »

return in 180 degrees sounds useful

//UndCon

msev
Posts: 186
Joined: Thu Apr 14, 2011 11:49 am

Re: Airplane mode

Post by msev »

So when it would save the position - when on ground? Or in flight? And then if one would flick a switch, or if the board would recognize rc failsafe it could start returning 180 degress back.


One noob question about i2c gps...do you connect it like this...GPS tx->arduino rx, GPS rx->arduino tx; secondary arduino sda->primary arduino sda, secondary arduino scl->primary arduino scl?
Last edited by msev on Mon Mar 19, 2012 9:50 am, edited 1 time in total.

PatrikE
Posts: 1976
Joined: Tue Apr 12, 2011 6:35 pm
Location: Sweden
Contact:

Re: Airplane mode

Post by PatrikE »

It should use the directiton at the moment you switch and return 180 degress back.
Or if failsafe is detected.

Alternative implement GPS-RTH for Airplane.
Use direction to home as "magHold ".

But i have problem with trimming the Acc om my plane.
It banks slightly in to a long turn.
It's Ok for failsafe but not for Poit to point flying.

User avatar
Hamburger
Posts: 2578
Joined: Tue Mar 01, 2011 2:14 pm
Location: air
Contact:

Re: Airplane mode

Post by Hamburger »

addon for the howto:
if for level mode users wants same servo travel min/max upon stick input as in gyro-mode, then level-P must be >=9.0.

PatrikE
Posts: 1976
Joined: Tue Apr 12, 2011 6:35 pm
Location: Sweden
Contact:

Re: Airplane mode

Post by PatrikE »

@Hamburger
Something like this?..
Level-P value will reduce the maximum throws in Level-Mode.
P=9 will give same throws as in gyro-mode


/Patrik

User avatar
Hamburger
Posts: 2578
Joined: Tue Mar 01, 2011 2:14 pm
Location: air
Contact:

Re: Airplane mode

Post by Hamburger »

yes, sounds good to me.
Or wait, are you quoting from the howto and the info was already there? Did I spend time to dig this info out of the code unneccessarily? It was not in the initial version, was it?

PatrikE
Posts: 1976
Joined: Tue Apr 12, 2011 6:35 pm
Location: Sweden
Contact:

Re: Airplane mode

Post by PatrikE »

Nope it's not in the howto yet....
But it will be tomorrow...;)

Any more ide's to put in the guide?

User avatar
Hamburger
Posts: 2578
Joined: Tue Mar 01, 2011 2:14 pm
Location: air
Contact:

Re: Airplane mode

Post by Hamburger »

Only after more flying...

PatrikE
Posts: 1976
Joined: Tue Apr 12, 2011 6:35 pm
Location: Sweden
Contact:

Re: Airplane mode

Post by PatrikE »

Keep'em comming...;)

It will only be a better guide.
Right now it's quite basic.
A summary from a thread in a Swedish forum.

User avatar
Hamburger
Posts: 2578
Joined: Tue Mar 01, 2011 2:14 pm
Location: air
Contact:

Re: Airplane mode

Post by Hamburger »

maybe
- you should copy the howto to your branch of the google rep, and
- we should put the link to the howto in the config.h next to the FLYING_WING and AIRPLANE model defines

So all our hard work will not be lost :)

msev
Posts: 186
Joined: Thu Apr 14, 2011 11:49 am

Re: Airplane mode

Post by msev »

Patrik would it be possible that the mwii arduino would sense the rssi voltage of another duino or of a rc receiver and when the voltage would be reduced to some value initiate the "mag rth"...

Is it a problem if the rc receivers rssi voltage range is a bit small,...lets say from 1.11-0.91V measured with a multimeter...so the cut-off value would be lets say around 0.99V.

PatrikE
Posts: 1976
Joined: Tue Apr 12, 2011 6:35 pm
Location: Sweden
Contact:

Re: Airplane mode

Post by PatrikE »

There's 3 analog I/O free on the MWii ardu.
A0,A1,A2
Plus A3 who is meant to read the battery voltage.

Arduino uses the rane 0 - 5 volts in 1024 units.
1024/5V=85,33 units/Volt.
So it should be possible.
http://arduino.cc/en/Reference/AnalogRead

But the falisafe routine can be modified to RTH if TX signal is lost..

/Patrik

Post Reply