MultiWii

timecop

april 14??????????????????????????????????????????????????????????????????????????????????????????

timecop

Yes, flex could do PPM (theoretically) since it has a timer AF on it.

timecop

Why don't you spend like 10 fucking seconds searching the thread, to find the reasons why there is absolutely no chance eurohype will be implemented? what's next, you're gonna ask when afroesc/simonk will support "active freewheeling"??? edit: i'll do the work for you: http://www.multiwii....

timecop

acroboard will always drift yaw, there's no temperature or bias calibration in firmware.
if you reconnect it after letting it warm up, the drift will be lessened.

timecop

@Kaysee OK, I see that you are using NAZE32... I removed the BOXNAMES from the code, that´s probably why... some functions will not be available until a new NAZE code review We are only using BOXIDS on the HUD also. Sorry for the inconvenient -KV latest firmware build I uploaded does "same&quo...

timecop

No, plugging in USB doesn't power receiver.

timecop

OK, I got rid of flash size register shit as it seems to be useless anyway as your C8 still has 128k flash.
Also fixed makefile to include compass driver and added -CJMCU target to keil workspace - and made sure it builds.

timecop

... ? it has supported brushed motors since several months ago.
just set motor_pwm_rate to > 500, like 8000 (noisy) or 16000 (less noisy) or 32000 (amazing) etc, and make your own brushed drivers. there was a pic of some guy who fit them all into the motor pads breakout area, very neatly.

timecop

move to something less ancient.

timecop

um, it would be same?
you're losing 2 RC inputs on PWM receiver, but servotilt + quad will work.

timecop

Huh? I have no fucking idea what that means.
My code implements MSP_BOXIDS and MSP_STATUS stuff (correctly): https://github.com/multiwii/baseflight/ ... ial.c#L377

timecop

You're not missing anything - and gcc target is generally tested by others, so it should build and work.
The only supported config tho is gcc-arm-embedded, other crap like codesourcery, yagarto, gnuwinarm or whatever, all those things have had problems, mostly libc/nanolib related.

timecop

They also don't come with any wires, require soldering, and as you said, here's the real problem:

as good as advertised

timecop

I guess i still need to get the debugger up and running. I added the patch file for the changes i have done. thanks, merged what was possible. you missed a 4-space tab in the patch -> all tabs must be converted to spaces. also I redid inverter stuff as #define INVERTER and test is same as LEDx, to ...

timecop

I think the 2nd option is probably better, but I'd have to see how it works. I don't wanna have multiwii-level sea of defines, either

timecop

overpriced european esc is NOT allowed to be used with naze, period.
connect it at your own risk.

timecop

I committed some stuff, mainly rearranging board.h to add new target and minimize drivers/etc inclusion in Makefile. As a side effect, this probably doesn't build at all - try it out and see how much effort it would be to make it build. PPM maps are correct (I think). I also enabled brushed PWM by d...

timecop

brewski wrote:Crazy thing is flight controller was just a $250 Nasa & the rest you could buy from HK for less than $500!

A fool and his money are soon parted.
Never been more true with "RTF" segment.

timecop

Can you post schematic? I can try to add it as another brushed target, sure.

timecop

I don't remember either - when GPS is enabled in PWM mode, those 2 channels are dropped during initialization (and reserved for GPS), so you will have only 6 RC inputs - which means map AETR1234 will only give you AETR12 and 34 will be gone. I think the shift is automatic - but its trivial to test a...

timecop

Pretty sure everyone read your post the first time you posted it.

timecop

Patches to make GPS actually work are welcome.

timecop

Hey 'Frank', I think I know you who are (monkey avatar on rcg, right?), this isn't about 32bit or github, its about alex (and other avr-8bit-project-maintainers) having a much easier way to review, accept, and merge patches from other developers INTO THE CURRENT 8BIT MULTIWII BRANCH. Right now shit ...

timecop

Correct.
And replacing it is easy w/hot air but it will make a freaking mess out of the pin headers if you got some soldered.

timecop

Can we make a real step forward to the future of Multiwii and move to github, there are so many forks and branches of mw development that we're unable to follow them all properly. Nor we are able to properly submit bugs or code merge requests. We all know mw is only possible due to the work of volu...

timecop

so, it has nothing to do with naze hardware then?

timecop

Correct

timecop

Plüschi wrote:I also have a walkera qr350 which is total crap firmware. Unusable shit.

I heard rumors the firmware in that runs on (surprise) atmega2560 and can actually be made to run multiwii.

timecop

No misleading points. Just stating the facts, but yes, arguing about it is pointless.

timecop

Why.move to newer faster boards? I used to specialise in speed optimisation for games. Eventually you find you are spending.much.more time optimising code than actually writing it it gets dull. Secondly speed.optimised code is usually much.larger (enrolled loops, longevity boundary, optimised data ...

timecop

markusb wrote:Does anyone know where I can find rev5 schematic?
I have a bunch of Naze32 rewv5 boards here for fault finding.

Nothing is significantly different from r4 that you would need it.
Fault finding on naze boards: MCU is fried by 5V, so remove it and replace. done.

timecop

Hardware is not the problem. It can be made in a day.
The problem is, who's going to be writing firmware? If you just copypaste MultiWii lcd.cpp, well,,, yeah...

timecop

Also ... there is no IPR issue to make a smarter KK2 alike board, with LCD + buttons + 10DOF + 644 cpu.

The only "issue" would be doing a new design with absolutely dead atmega644. That just makes absolutely no sense at all.

timecop

its all automatic for ublox.
you dont need to do anything.

timecop

Firmware initializes GPS on connect anyway...............................

timecop

Dunno why we're discussing this stuff in this thread, but since PID is dependent on loop time (again, due to over-optimization and removing things), changing it rescales PID values up or down.

timecop

Right. Many people don't realize that driving leds with PC13.14.15 is a bad idea. I don't know why

Unfortunately I don't have much idea for your flash fail problem.
I guess best bet is to get debugging going so you can see where it crashes after reboot.

timecop

You shouldn't need to remap. Just don't enable timers you aren't using. Motor1 Pin45 PB8 TIM4_CH3 Motor2 Pin46 PB9 TIM4_CH4 Motor3 Pin18 PB0 TIM3_CH3 Motor4 Pin19 PB1 TIM3_CH4 Your PWM map should ONLY include those, and you can just trash everything else unrelated. If you don't enable a pin as timer...

timecop

ezio, what do you have in mind? promini is full, so there's nothing else to add.
next step would be rewriting everything in ASM to free up some more flash space.

timecop

Did you check manual, and make sure your RC inputs are at 1500 (using subtrim) or at 1520+subtrim if using futaba?

timecop

What do you think clonespy and flyjewino have been doing? But it's ok, one can easily tell their stuff from the original, theirs looks like shit

timecop

I'm assembling minis tomorrow.
I have an assembly queue for fulls as well, I hope I can get them done tomorrow also. But no promises, as I have lots of other crap to do lately.

timecop

Check here: http://boltrc.com/

timecop

hmm... interesting.
not sure eihter.
can you run it once, then connect to it wiht st flash loader, and instead of uploading a hex, read back what's in flash.
then look at hex and see if there's some crap getting erased in the middle of flash area.

timecop

Some other places have them in stock. I'm keeping them out mostly due to 1) too lazy to pack shit

timecop

No, you can still choose 128k flash map in usart bootloader and it works. I *know* it does, because I still have 2-3 years old boards (and including the original 'FreeFlight' board with C8 MCU on it, and I've flashed both of them over usart bootloader. However, it seems recently made chips physicall...

timecop

You can try dropping all the "legacy" sensors like ADXL,MPU3xxx,MMA, etc, and undefine GPS, which should bring your code below 64k even with GCC. I'm not sure what the deal is with C8 chips - old ones DID have 128k of flash even tho flash size register reported 64k. HOWEVER, with my curren...

timecop

I just pushed code that makes I2C setup generic. All you need to do is change i2cInit() in drv_system to use I2CDEV_1.
So there is less code for you to edit. Maybe at some point we can do platform define to fix PWM maps and leds etc.

timecop

I would add a diode - acro vregs are 5.5V max...

timecop

You are right, its not a remap, just different peripheral (1 vs 2) I2C device isn't hardcoded (I think there's a I2Cx pointer at the top of the file for the peripheral), but I see that dummy clockout stuff is - I should probably fix that. Other than that, its just the PWM and led mapping. Can't be d...

Search found 1880 matches