MultiWii

I thought LSM303DLx was just HMC5883 chip inside same package with accel.
Wouldn't it be easier to reuse existing 5883 code?

The 'switch' part combined with read-onlyness of PINB is what threw me off.
Normally this is called "toggle".

Had some time to port this new code and try it out.
Flies as good as ever, and I don't notice any issues with autolevel.

Let's turn this thread into catch-all for asking stupid questions about the code. I've got doubts about this: #define LEDPIN_SWITCH PINB |= 1<<5; According to doc8025, all of PINB is read-only. 14.4.4 PINB – The Port B Input Pins Address ... Is there ANY reason this code exists, and if so, what exac...

I know I might be asking too much, but I've got a few code readability improvement requests. Things like LEDPIN_SWITCH, etc macros do not have a terminating semicolon after them. Yes, I realize it's in the config.h file, but it still makes it more difficult to read (and indent) the code. So instead ...

Before 1.9 release can someone (alex? whoever?) clean up byte -> uint8_t stuff please? Since the rest of the code uses uint8_t there seems to be no reason to use custom types, and it makes code harder to read. Looking at 20111029 dev it still uses byte.

OK, thanks for explanation. That's basically what I'm doing, and it seems to work. ( = rescaling gyro outputs)
500 dps was just an example anyway. Still haven't fly-tested this dev, but it seems to be working OK on the desk.

Well, I thought you said auto-level code depended on 2000dps as well at some point. Is this not the case anymore?
i.e. if I change to 500dps gyro and adjust things appropriately, nothing else needs to be changed?

Hmm.. I merged the changes, and something is messed up in accSmooth, pitch/roll values are all over the place (jumping between -1000/1000 type thing... So I went through line by line and didn't see any merge fail... Finally I thought "hey let's calibrate ACC". Hit that button and now all i...

Millions? You're kidding right. There aren't even millions of USERS of opensores code, never mind developers.... git was created to deal with the mess that is Linux, if it wasn't such a mess, git wouldn't be needed... I'll be needing to merge 1.8p2 with latest dev/1.9 soon for my STM8 port, please e...

Requesting configurable gyro dps that's not 2000 and not tied into the rest of the code? pretty-please?

Just more useless stuff to deal with for people who actually bother spending time to code.
Google code is fine, and SVN is fine. If you can't handle merging patches, you probably shouldn't be trying to submit code.

It would be cool if in next version, the gyro scalefactor could be implemented, so things like 500deg/sec gyros (or any other rate really) could be easily used. Right now I just lucked out (somehow?) by multiplying my 500deg/sec output by 5 to get the values mwii wanted, but it would be nice to have...

Well, something like powering up with say pitch + throttle at max would enter throttle calibration mode.
Just a guess. Since as you say, user needs to plug in escs after the board initializes... Could give some blink codes if you're really paranoid about safety.

Just a guess.

This might be silly but surely making a user reflash firmware just to calibrated escs is a bit extreme?

OK, thanks for advice. I will wait until there's a new-stable or until there's some feature in _dev that I'm required. I do have a 3.3V I2C header but I don't think I'm going to be using any other sensors. I might use it for motor control and make motor 1-6 as PWM inputs, but thats not a high priori...

Looks like the strange yaw activity must have been due to dodgy/faulty yaw gyro on my prototype board. I made a new smaller form factor PCB and loaded code with defaults, and yawing is (as good) as its going to get I guess. I've also merged all changes up to multiwii 1.8_p2. I guess I'll match them ...

Pretty cool idea, but how much more noise are you going to put on this slow bus? You are already reading i2c sensors etc... And I guess you want OSD to be slave, not mwii?
anyway I think you need to set TWAR register for address you want to listen on.

Because servo library sucks would be my guess.
Of course, if you had used MCU with proper hardware PWM this wouldn't be a problem at all...

One word,
PPM

If you notice rcTime is actually assigned right inside that if() statement.
Of course, its initial value is 0 due to it being static, so when currentTIme reaches > 20000 rcTime gets set to that.

static vars are initialized to zero. non-static are not.

Go for it.

Everything works, I declare victory

http://www.youtube.com/watch?v=phOtpMJZah8

Can be configured to either use onboard gyro+accel or external i2c sensor board at 3.3V (tested with atavrsbin1, but should work with other junk too).

Latest code here http://code.google.com/p/afrodevices/so ... %2Fafrowii

OK, I guess its working with ATAVRSBIN1, so the issue is there's some 2000dps-ness in the code somewhere that assumes high-rate gyros. Alex, any ideas? Test flight with my STM8 board + ATAVRSBIN1: m I had to turn RC_Rate WAY up after this video, and there's still some unexplained yaw that happens in...

The board itself isn't worth it. It's ATXMega, and currently no code exists for it to do anything. There's not enough headers on the board to use it as a multirotor controller, and its too big for that anyway. However, the sensor boards (Inertial one / pressure one / inertial two?) are a decent deal...

Moving right along. I2C code has been done, and I had ATAVRSBIN1 laying around from my XPlained board. I defined the proper stuff, and the GUI is showing it correctly. http://i.imgur.com/wQu4i.png However there's a strange unexplained dip sometimes - the sensor jumps to -5000 or so for readings. Is ...

OK, I ended up having GYRO_SCALE as this: #define GYRO_SCALE ((500.0f * PI)/((1024.0f) * 180.0f * 1000000.0f) * 3.0f) Without * 3.0 it was pretty laggy in rotation response, so I increased that until the angles were correct. So now that I had correct angles in GUI with high acc factor, I put acc bac...

Cool, thanks for replying to my email here, maybe the info can help others as well. I suspected /4 was happening somewhere but did not look much into it. I'm going to try (I need to make another devboard as I think I fried analog inputs on the one on my desk - they're consistently less amplitude tha...

I was bored and took 1.8p1 and ported it to STM8S -> m This is NOT related to AVR or any Atmel-cpu. I tried to keep most changes under #ifdef STM8, but maybe wasn't too careful in places. My STM8 board uses analog gyros and adxl345 on SPI bus, so a couple changes were needed for that. Gyros are 500d...