spin7ion / multiwii Goto Github PK

Make SBUS working again

Added Vtail

Branch name:

Purpose of code changes on this branch:
I wanted to introduce a easy way of hearing which alarm is present


When reviewing my code changes, please focus on:

is the code too coplicated or does it use to much cpu time or memory

After the review, I'll merge this branch into:
/trunk

For Spektrum DX5e the range of the sticks is limited.
I recommend values 1200 and 1800 instead of 1100 and 1900 for MIN- and MAXCHECK

Could be nice to have this with an explanation in config.h (instead of in 
MultiWii.cpp) 

What steps will reproduce the problem?
1. Send an MSP_PRIVATE request to the FC
2.
3.

What is the expected output? What do you see instead?
A valid response is expected; as MW does not use MSP_PRIVATE, it should return 
an error ($M! etc).
Instead, there is no response.


What version of the product are you using? On what operating system?
2.4.0 r1729 Mega2560

Please provide any additional information below.

Not replying at all is in violation of the MSP specification. It also makes 
auto-detection of the firmware (c.f. cleanflight) more complex than need be.

Please consider applying the attached/

What steps will reproduce the problem?
1. Fit / enable buzzer
2. Power up board with GPS but no fix
3.

What is the expected output? What do you see instead?
Expected: LED indicates no fix, buzzer is silent
Actual: buzzer sounds continuously

What version of the product are you using? On what operating system?
2.4.0r1729 on mega2560

Please provide any additional information below.

Incorrect assignment of enum compared to MW-NAV-b7. In Alarm.h, c. line 79 
currently sets ALRM_LVL_GPS_NOFIX  = 1, the fix is:

#if GPS
  enum alrm_lvl_gps {
   ALRM_LVL_GPS_NOFIX  = 2,
  };
#endif

This restores expected behaviour.

exchanged a portName for shortName in the shortifyPortName(...). otherwise 
there were string-length issues in the creation of the shortName.
This fixes it.

Added correct I2C address for BMA180 on ALLINONE sensor board

My Spektrum DX5e seems to change MIDRC values from time to time (in range of 
+-50), but different for each axe. (It's not a problem of trimming - ok 
possible to trim against it, but it's kind of not perfect solution :))

I think it could be nice to have a setting to automatically calibrate MIDRC 
during startup. So it will read roll, yaw and pitch during initialisation and 
then store each value in an array and use that instead of MIDRC constant.

Added beta support for accelerometer MMA7455L, based on
MultiWii 1.6Pre 

What steps will reproduce the problem?
1. rcCommand[THROTTLE] = initialThrottleHold + BaroPIDBaroPID;
2. BaroPid is either 1 or 0.  Not sure what this line of code will do without 
any kind of operator between the two.  It could be a don't care.
3.

What is the expected output? What do you see instead?


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


Please provide any additional information below.

Added VTail

[email protected]

What steps will reproduce the problem?
1. Create a mission with SET_HEAD
2. Fly the mission
3.

What is the expected output? What do you see instead?
For SET HEAD, the vehicle will point in the direct set by SET_HEAD, instead it 
points in the reciprocal direction.

What version of the product are you using? On what operating system?
2.4.0 r1729 on Mega2560

Please provide any additional information below.
See attached patch. Flight tested.

What steps will reproduce the problem?
1. Take advantage of improved control code of other flight control software 
that takes more memory that the smaller processors.
2.
3.

What is the expected output? What do you see instead?
Improved control capability.  


What version of the product are you using? On what operating system?
I am using MultiWii 2.2 on Windows 7.

Please provide any additional information below.
I would probably go to the MegapirateNG but I really like the ability to 
communicate with the fc board with bluetooth.  The ability to make changes 
without having to physically connect to the board is really great.
I also believe that there will be a lot more of the 2560 based boards which 
have even more sensors available and the easy connection of gps.

[deleted issue]