Naze32 hardware discussion thread

zarkon · Post by **zarkon** » Sun Jan 20, 2013 4:48 pm

timecop wrote:PPM? And no, not possible.

yes ppm, if that not posible have to find figure out why it doing that, will do a test again with cppm rx, but will lose my led switch

Gaijin · Post by **Gaijin** » Sun Jan 20, 2013 5:24 pm

I finally got around to fitting my HC-SR04 Sonar sensor to my Hex, 5v supply from a spare esc's BEC and Trigger and echo (via 1k resistors) to pins 7&8, in the process I've finally used ALL the I/O's on my Naze32!

Anyhow, Sonar is highlighted in green via multiwiiconf and I assume it's adding an offset to the altitude reading BUT whats the simplest way to specifically tell if it's working correctly?

I know it's not really actively supported at present (maybe when 2.2 is merged?) but it was cheap and easy to add so why not, TC I know you aren't really fussed about sonar support but I have a spare I could possibly send to you?

P.S added a link to my multicopter photo album if anyone's interested

https://plus.google.com/photos/108235385012513539305/albums/5835563810778487569?authkey=CIK_pffOxYOP2QE

rocketray · Post by **rocketray** » Mon Jan 21, 2013 1:52 am

QuadHag wrote:Since I connected all motors the same way, they are all spinning in the same direction.
Can this be fixed by software, or do I have to change the wired connection?

This is standard Multiwii stuff so look here http://www.rcgroups.com/forums/showthread.php?t=1261382 . you will find that questions not related to Naze32 will probably get ignored, dont get offended its just this is a naze32 development thread and you should look elseware for normal quad and tri stuff. As im feeling good at the moment i will tell you that to change motors direction just swap any two of the three motor wires.

Ray

zarkon · Post by **zarkon** » Mon Jan 21, 2013 4:49 pm

zarkon wrote:
timecop wrote:PPM? And no, not possible.

yes ppm, if that not posible have to find figure out why it doing that, will do a test again with cppm rx, but will lose my led switch

root caused found, i was stupid enough to use my rangelink 12ch setting for my frsky modules which only have 8ch working fine now just need some pid tuning, cheers

teslahed · Post by **teslahed** » Mon Jan 21, 2013 8:38 pm

I recently updated my Naze32 with the current version of baseflight;

http://code.google.com/p/afrodevices/do ... p&can=2&q=

following the instructions in the manual and at the start of this thread. It updated without any obvious issues but since then it's not detecting the presence of the barometer in the Multiwii configuration GUI. I've reflashed the thing again since doing it the first time and it's not made any difference.

I'm at a bit of a lose as to what to try next. Anyone got any suggestions please?

ABL · Post by **ABL** » Mon Jan 21, 2013 9:01 pm

teslahed wrote:I recently updated my Naze32 with the current version of baseflight;
http://code.google.com/p/afrodevices/do ... p&can=2&q=

Do NOT use such old firmware files.
Use latest baseflight:
http://afrodevices.googlecode.com/svn/trunk/baseflight/obj/baseflight.hex

teslahed · Post by **teslahed** » Mon Jan 21, 2013 9:38 pm

That did the trick, thanks ABL.

It might be worth updating the manual and / or first post of this thread with this info. I thought i was playing it safe by installing the 'baseflight latest stable version' but it seems anyone with one of the latest boards needs to install a newer version than that or else the barometer doesn't work.

teslahed · Post by **teslahed** » Mon Jan 21, 2013 9:57 pm

I'm wondering if anyone has a decent guide (or just a post) that explains how to get GPS working with the naze32. So far i have done the following;

Plugged the crius V1 into channels 3 and 4 for TX and RX. The manual states pin 3 is TX and 4 RX. As RX plugs to TX and vice versa i have plugged the RX of my GPS into pin 3 and the TX into pin 4. I presume this is right? I've tried it the other way around just in case and that didn't seem to help...

Plugged the 5V power from the GPS into a spare motor pin out from the Naze32 to get power from the ESC - I'm flying a quadcopter so i have 2 spare anyway.

Read a bunch of posts in this thread and set the following settings using the hercules terminal;

Code: Select all

feature GPS
set gps_type = 1
set gps_baudrate = 38400
set nav_controls_heading = 0

When i plug everything together the light goes on on the GPS unit itself, but in the multiwii GUI it doesn't show the GPS light lit in green - I only have ACC, BARO and MAG lit up at the moment. Also i don't get any activity anwhere else in the GUI you'd expect to see it.

The GPS unit definitely works - I had it running on the crius all in one V1 the other day fine.

Any suggestions / links / comments most welcome, thanks!

teslahed · Post by **teslahed** » Mon Jan 21, 2013 10:06 pm

I feel a bit silly - but i am now going to have to answer my own question. I gave it 'one more go' after i thought i'd given up (and posted the above) and now it works!

All i did was change set gps_baudrate = 38400 to 57600 and now I'm getting the GPS light on and blinking in the GUI. I'll have to leave it plugged in somewhere near a window to see if i get any satellites now.

Also;

Plugged the crius V1 into channels 3 and 4 for TX and RX. The manual states pin 3 is TX and 4 RX. As RX plugs to TX and vice versa i have plugged the RX of my GPS into pin 3 and the TX into pin 4. I presume this is right? I've tried it the other way around just in case and that didn't seem to help...

Pin 3 which is marked as 'TX' in the manual definitely plugs into the GPS 'RX' as you'd expect.

Another issue which may be confusing some people - there appears to be a bug with the GPS I'm using where 50% of the time you turn it on it doesn't work. If you turn the quadcopter of and on again it starts up fine! But if you are trying to get it working and going through all the different settings sequentially there is a 50% chance it wont be responding when you try the correct setting - you have to try every setting twice if you want to be sure. This could be quite frustrating for some people.

hkubota · Post by **hkubota** » Mon Jan 21, 2013 11:15 pm

ABL wrote:
teslahed wrote:I recently updated my Naze32 with the current version of baseflight;
http://code.google.com/p/afrodevices/do ... p&can=2&q=

Do NOT use such old firmware files.
Use latest baseflight:
http://afrodevices.googlecode.com/svn/trunk/baseflight/obj/baseflight.hex

TC,

is it possible to remove that old firmware and replace it with either nothing or a file with the correct location of the current firmware or with a halfway recent known working and stable firmware?

Harald

ABL · Post by **ABL** » Mon Jan 21, 2013 11:24 pm

teslahed wrote:It might be worth updating the manual and / or first post of this thread with this info. I thought i was playing it safe by installing the 'baseflight latest stable version' but it seems anyone with one of the latest boards needs to install a newer version than that or else the barometer doesn't work.

From PDF manual:

Code: Select all

Hardware is shipped with the most current firmware at the time of assembly. It is
recommended to upgrade to latest stable or development firmware for new features.
<...>
3. Latest baseflight firmware (development)
http://code.google.com/p/afrodevices/source/browse/trunk/baseflight/obj/baseflight.hex

So, you downgraded your version... Just read manual ;-)

teslahed wrote:I feel a bit silly - but i am now going to have to answer my own question. I gave it 'one more go' after i thought i'd given up (and posted the above) and now it works!

You probably still need 'feature gps'.

teslahed · Post by **teslahed** » Tue Jan 22, 2013 12:29 am

It's true the information is there - i just missed that particular part unfortunately.

Although i imagine other people will make the same basic assumption / mistake that i did - thinking the latest stable version linked to is going to work with the latest naze32 hardware, and be a safer bet than the 'development' version. Obviously the 'development' version is better developed than usual for these things - often with hardware like this it's best not to mess about with the latest version of the code until you have the basics working properly, but with the Naze 32 the dev version is pretty much necessary if you want the barometer on your flight controller to work.

You probably still need 'feature gps'.

I did specific in my first post on the subject that i used the feature so could take the opportunity to say something like RTFP if i wanted, but i wont, that would be mean (and hypocritical) ;-)

. I've had 6 satellites connected with the board just sitting on my windowsill, i guess it must be working ok now so I will have to take it out for a test flight when the weather improves.

zarkon · Post by **zarkon** » Tue Jan 22, 2013 10:24 am

now having flip of problem,

- board orientation correct
- motor sequence all correct
- re-do esc calibration
- update to lastest restore default

hand held test indicated board over correcting, motor output a bit jumping around instead of constan, none of those above step work, tested with 2 different frame with different electronic setup symptoms are the same, in acro it fli side way in autolevel if flip forward, both frame work fine with my IOI MINI 10DOF multiwii board, posible hardware faulty?

timecop · Post by **timecop** » Tue Jan 22, 2013 11:02 am

hardware doesn't break this way.

cGiesen · Post by **cGiesen** » Tue Jan 22, 2013 11:35 am

zarkon wrote:now having flip of problem,

Check the wiring of the motors!
The order is different from MWii I think.
When my Copter flip, my motors are wrong ordered!

zarkon · Post by **zarkon** » Wed Jan 23, 2013 1:04 am

cGiesen wrote:
zarkon wrote:now having flip of problem,

Check the wiring of the motors!
The order is different from MWii I think.
When my Copter flip, my motors are wrong ordered!

checked and verified a few time still the same

jef79m · Post by **jef79m** » Wed Jan 23, 2013 1:07 am

zarkon, can you post a pic of your setup?

zarkon · Post by **zarkon** » Wed Jan 23, 2013 11:20 am

jef79m wrote:zarkon, can you post a pic of your setup?

i'll post itnone i got home, will try to update the firmware to the latest from svn trunk

timecop · Post by **timecop** » Wed Jan 23, 2013 11:24 am

This is not something that would be broken by a firmware revision.

zarkon · Post by **zarkon** » Wed Jan 23, 2013 11:46 am

timecop wrote:This is not something that would be broken by a firmware revision.

well as for now i have no idea why it doing that, hand held test gyro correction are jumpy and sometime over correcting, would assuming updating the board wod restore it back to factory defaults and clear up the epprom no?

my electronic setup just incase, posting the whole setup pictures later when i get back from work

- turnigy d2812 1100kv
- 12a blue series with simonk

thanks

timecop · Post by **timecop** » Wed Jan 23, 2013 11:54 am

Does everything properly respond on the graphs?
Pitch forward and the gyro pitch numbers should go positive (up on the graph).
Pitch back and the gyro pitch numbers should go negative (down on the graph)
Roll right and the gyro roll numbers should go positive (up on the graph)
Roll left and the gyro roll numbers should go negative (down on the graph)
Yaw right and the yaw gyro numbers should go positive (up on the graph)
Yaw left and the yaw gyro numbers should go negative (down on the graph)

same for acc ^

do not attempt to fly with acc/horizon/etc on. hover in angle/rate mode first.
if youre shaking the stuff while plugging in battery, do gyro init stick sequence.
also note board "front" direction etc.

zarkon · Post by **zarkon** » Wed Jan 23, 2013 1:39 pm

timecop wrote:Does everything properly respond on the graphs?
Pitch forward and the gyro pitch numbers should go positive (up on the graph).
Pitch back and the gyro pitch numbers should go negative (down on the graph)
Roll right and the gyro roll numbers should go positive (up on the graph)
Roll left and the gyro roll numbers should go negative (down on the graph)
Yaw right and the yaw gyro numbers should go positive (up on the graph)
Yaw left and the yaw gyro numbers should go negative (down on the graph)

same for acc ^

do not attempt to fly with acc/horizon/etc on. hover in angle/rate mode first.
if youre shaking the stuff while plugging in battery, do gyro init stick sequence.
also note board "front" direction etc.

i'll double check those again, i'm using acro naze32 so only rate and angle mode here, will do another test one i have verified everything again

thanks

DennyR · Post by **DennyR** » Fri Jan 25, 2013 8:06 am

Hi Guys I'm new here, Just built a Turnigy Talon Tri. with Suppomotor BL2814/8's turning 10x5 Graupners. It's my first time with Multiwii but everything went ok in the 2.1 GUI. The model flew OK from the start, which is always a good sign. I do have an issue with the baro sensitivity it would seem, as it wanders up and down about six feet. Not using GPS yet but I do have some Tardu stuff kicking about that may do the job. Does anybody have some PID settings for a hot tri that they would care to share?

rcsnow · Post by **rcsnow** » Sun Jan 27, 2013 9:23 pm

Is your baro protected from winds with a piece of foam or something?

rcsnow · Post by **rcsnow** » Sun Jan 27, 2013 9:43 pm

I finally set my quad with naze32 that i bought .. half a year ago.
Made a 350mm wood frame (rosewhite style) prototype, with NTM2826 1200kv motors, 8x4.5 gemfan props, 12A esc, 3S 2200mah.
Default PID settings... flying smooth! Full carbon version next.

zarkon · Post by **zarkon** » Mon Jan 28, 2013 2:58 am

timecop wrote:Does everything properly respond on the graphs?
Pitch forward and the gyro pitch numbers should go positive (up on the graph).
Pitch back and the gyro pitch numbers should go negative (down on the graph)
Roll right and the gyro roll numbers should go positive (up on the graph)
Roll left and the gyro roll numbers should go negative (down on the graph)
Yaw right and the yaw gyro numbers should go positive (up on the graph)
Yaw left and the yaw gyro numbers should go negative (down on the graph)

same for acc ^

do not attempt to fly with acc/horizon/etc on. hover in angle/rate mode first.
if youre shaking the stuff while plugging in battery, do gyro init stick sequence.
also note board "front" direction etc.

did the test gyro & acc respond seem fine, in GUI when i arm and apply some throttle i can see all my motor respond are hectic bouncing everywhere, I manage to borrow a freeflight board gonna update it a baseflight software and try that one see what happen

timecop · Post by **timecop** » Mon Jan 28, 2013 3:11 am

Sounds like you're on a DJI frame.

zarkon · Post by **zarkon** » Mon Jan 28, 2013 3:14 am

timecop wrote:Sounds like you're on a DJI frame.

wrong

edited my post with my quad setup

ReadError · Post by **ReadError** » Mon Jan 28, 2013 3:16 am

Even worse...

ReadError · Post by **ReadError** » Mon Jan 28, 2013 3:17 am

Are there even supports for those arms? Take a side pic please.

zarkon · Post by **zarkon** » Mon Jan 28, 2013 3:22 am

ReadError wrote:Are there even supports for those arms? Take a side pic please.

hobbyking frame

http://www.hobbyking.com/hobbyking/stor ... _KIT_.html

frame was using my old 1 years+ IOI mini 10DOF multiwii before replaced with naze32, props and motor a balanced quite well as I "almost" have flat line on the graph, FC are mounted on a 3 layer double sided foam which i have been using same method for almost a year or so for all my FC, I prefer this fiber glass frame rather than those plastic DJI frame

timecop · Post by **timecop** » Mon Jan 28, 2013 3:32 am

dunno , setup looks legit. are you taking off in gyro-only? and all settings are at defaults (reset to defaults from console)?

zarkon · Post by **zarkon** » Mon Jan 28, 2013 4:22 am

timecop wrote:dunno , setup looks legit. are you taking off in gyro-only? and all settings are at defaults (reset to defaults from console)?

yes taking off gyro mode only, all setting are default out of the box only thing i changed is the min throttle for ESC init, i give another reset and give it another round after this as cc3d are on the frame now, going off to do some fpv'ing

garbungel · Post by **garbungel** » Mon Jan 28, 2013 2:02 pm

How can I change my servo travel to something else than default through the CLI. Is there something like minrc or maxrc command?

teslahed · Post by **teslahed** » Mon Jan 28, 2013 3:07 pm

Zarkon - are those rctimer motors / props and prop adapters? If so I found the motors work ok but the collet type prop adapters they come with are quite low quality and tend to produce excessive vibrations.

Also the rctimer plastic props are about the worse of the cheap props I've tried and wont be helping you. Have you balanced the props at all?

timecop · Post by **timecop** » Mon Jan 28, 2013 3:15 pm

garbungel wrote:How can I change my servo travel to something else than default through the CLI. Is there something like minrc or maxrc command?

well, there's servo min/max stuff for gimbal and tri servos, Ive been meaning to generalize all servos into a single array of stuff and make a proper command to configure them but for now this works. What do you need to change? I presume gimbal servos? thats servo_tilt_min/max/etc variables in cli.

garbungel · Post by **garbungel** » Mon Jan 28, 2013 4:18 pm

Thanks for quick answer. I don't mean for my gimbal. I actually mean my RC control values. Currently with R251 when looking to the range used I see I have to configure my TX at maximum to get 950-2050us range, while in the GUI it seems I still don't reach the maximum of what the GUI shows. I was wondering if I can change this for all my controls like throttle, pitch, roll and yaw ofcourse to the range I actually want.

zarkon · Post by **zarkon** » Tue Jan 29, 2013 3:26 am

teslahed wrote:Zarkon - are those rctimer motors / props and prop adapters? If so I found the motors work ok but the collet type prop adapters they come with are quite low quality and tend to produce excessive vibrations.

Also the rctimer plastic props are about the worse of the cheap props I've tried and wont be helping you. Have you balanced the props at all?

not RCtimer motor, turnigy d2812 1100kv prop are gemfan, yes as i stated in my previous post both motor and props are balanced to near perfection

jseyfert3 · Post by **jseyfert3** » Tue Jan 29, 2013 9:53 am

Hopefully these aren't too much of noobish questions. First time I've posted about the controller, anyway. First off, it's my first quad, and I just got done building it (scratchbuilt). I flew it for the first time yesterday afternoon. Here it is, not the first flight, but the first battery still. Before this, I've flown a few airplanes and a Blade CX2, but not for 3 years or so.
http://www.youtube.com/watch?v=tT4GtunipvA

I was surprised how stable it was from the go (piloting skills excluded). I didn't trim anything or touch the PID loop, it was using default settings. So, here we go:

I double checked proper rotation, yet my roll and yaw both operated backwards. Not an issue, as I did careful first "hops" and servo reversing on the TX fixed that right away, but I was curious why they were operating backward in the first place with default settings.
My transmitter is set to just under 1000 on the throttle, I believe, when all the way down. When armed, I noted that the motor outputs jump from 1000 to 1150, so I set the BLHeli firmware on the ESC lower throttle limit to 1152. This is the proper way to do it, right? Also, when level, the motor outputs were around 1830 when the throttle input was almost 1900. Tilting/moving the board could raise those higher, I saw 1860 or 1870, and by the bar graphs (I'm using MWC for this), it looks like they could go higher then the throttle setting, perhaps? What is the max output of the Naze32 to the ESC, i.e. what should I set the upper throttle range on the ESC too? I currently have it set at 1900.
Related to arming, are the stick illustrations in the manual for mode 1? I use mode 2, and I tried the stick combos for arm and disarm and they didn't work. So in the mean time I assigned the arming to AUX1, but as I currently only have a six channel radio, on which channels 5 and 6 are two, not three position switches, that limits extra functions like auto-level, carefree, etc, to one possible choice per flight. I have my eye on the upcoming 9 channel radio from FrSky coming out later this spring, so later it won't be a problem, but right now it uses 50% of my switch real estate just to arm.
During the initial power-up gyro calibration, does it have to be level? The manual just says don't move, and I didn't know if it had to be level for an accel calibration at the same time.
There are a number of you guys testing GPS, and I am interested in future use of GPS for position hold and hopefully RTH for later FPV use (signal loss). I'm not asking for a how too, but where do I look to start learning how to use it? I know the very basics of C through doing a couple Arduino projects, but that's practically nothing. I just want to start learning what I need to learn.

rcsnow · Post by **rcsnow** » Tue Jan 29, 2013 11:24 pm

jseyfert3 wrote:Hopefully these aren't too much of noobish questions. First time I've posted about the controller, anyway. First off, it's my first quad, and I just got done building it (scratchbuilt). I flew it for the first time yesterday afternoon. Here it is, not the first flight, but the first battery still. Before this, I've flown a few airplanes and a Blade CX2, but not for 3 years or so.
http://www.youtube.com/watch?v=tT4GtunipvA

I was surprised how stable it was from the go (piloting skills excluded). I didn't trim anything or touch the PID loop, it was using default settings. So, here we go:
I double checked proper rotation, yet my roll and yaw both operated backwards. Not an issue, as I did careful first "hops" and servo reversing on the TX fixed that right away, but I was curious why they were operating backward in the first place with default settings.
My transmitter is set to just under 1000 on the throttle, I believe, when all the way down. When armed, I noted that the motor outputs jump from 1000 to 1150, so I set the BLHeli firmware on the ESC lower throttle limit to 1152. This is the proper way to do it, right? Also, when level, the motor outputs were around 1830 when the throttle input was almost 1900. Tilting/moving the board could raise those higher, I saw 1860 or 1870, and by the bar graphs (I'm using MWC for this), it looks like they could go higher then the throttle setting, perhaps? What is the max output of the Naze32 to the ESC, i.e. what should I set the upper throttle range on the ESC too? I currently have it set at 1900.
Related to arming, are the stick illustrations in the manual for mode 1? I use mode 2, and I tried the stick combos for arm and disarm and they didn't work. So in the mean time I assigned the arming to AUX1, but as I currently only have a six channel radio, on which channels 5 and 6 are two, not three position switches, that limits extra functions like auto-level, carefree, etc, to one possible choice per flight. I have my eye on the upcoming 9 channel radio from FrSky coming out later this spring, so later it won't be a problem, but right now it uses 50% of my switch real estate just to arm.
During the initial power-up gyro calibration, does it have to be level? The manual just says don't move, and I didn't know if it had to be level for an accel calibration at the same time.
There are a number of you guys testing GPS, and I am interested in future use of GPS for position hold and hopefully RTH for later FPV use (signal loss). I'm not asking for a how too, but where do I look to start learning how to use it? I know the very basics of C through doing a couple Arduino projects, but that's practically nothing. I just want to start learning what I need to learn.

I use turnigy 9x (mode 2) and had to set yaw reverse on my commands and the stick commands work correctly as shown in the manual.
You might want to enable "MOTOR_STOP" via the CLI, so that your motors don't start after arming.
On power up there is only gyro calibration if you don't use gimbal. If you use gimbal, then there is also accel calibration. So no need for level, just still. Or stick calibration afterwards if unsure.
You could go learn C, by reading the baseflight code. Start with main.c. See that calibration settings you were asking about there.

rocketray · Post by **rocketray** » Wed Jan 30, 2013 4:56 pm

@ jseyfert3

Hi,

Love the simplicity of the build, well executed and clean, and judging by the video no real problems. I have to reverse several things in my tranny, its a Futaba ZAP9 with a FrSky module fitted so i think that is common and not really a problem if you can sort it via the tranny. Just a few suggestions to make things a little easier.

In the Cli

1. feature motor_stop (i personally find it very nerve wracking if this isnt enabled and its a good safety feature)
2. set looptime=350 ( or even 300, it makes it less twitchy )
3. set acc_lpf_factor=100 ( increases stability when in stable mode )

anyway you seem to be doing OK so good luck and all the best

Ray

zarkon · Post by **zarkon** » Thu Jan 31, 2013 3:21 pm

oknafyer reflashing the board with the latest build it fly now, not really sure what wrong before, the only thing i did was reflash and restore to defaults via cli, plugged everything back arm and it just works! time for some pid tuning

tedious · Post by **tedious** » Fri Feb 01, 2013 1:16 am

So after some rough attempts at my first quad, this is version 2, rebuilt from the wreckage and added some upgrades...
https://www.youtube.com/watch?feature=player_embedded&v=XaBWDn4AuU8

Currently:
I don't know AUW right now, can't find my postal scale (lil heavy though)
Controller: Naze32
Escs: HK Blue 30a flashed w/ SimonK firmware
Motors: iPower 2217q 880kv
Props: gemfan 10x4.5"
Battery: Turnigy Nano 2650mAh (need 4-5k mAh or maybe 4s)
Camera: Sony HDR-AS15 ActionCam

Frame: all custom built with a couple purchased parts
About 23" (580mm) motor center to motor centers
Arms are currently 1/2" square wood (may change these to avoid some mild twisting I see)
Frame plates and motor mounts to be CF soon, maybe arms too

Thanks again TC

(BTW, i think i'm going to have to order the adapter for the telemetry for frsky soon....)

ReadError · Post by **ReadError** » Fri Feb 01, 2013 1:26 am

https://www.youtube.com/watch?feature=p ... aBWDn4AuU8

(Proper link)

tedious · Post by **tedious** » Fri Feb 01, 2013 4:17 pm

ReadError wrote:https://www.youtube.com/watch?feature=player_embedded&v=XaBWDn4AuU8

(Proper link)

Thanks... I'm usually better about links, etc....

Going to work on a temp camera mount and some proper landing gear SOON....

irun4fundotca · Post by **irun4fundotca** » Sat Feb 02, 2013 10:10 am

Is there a gltch sometimes where you can't ARM with a switch but you can via the stick?
I have tried numerous channel mappings and can control ACC on aux1 or aux2 (and both) via my gear or flap switch but not ARM

Screenshots attached showing various attemps and min/max limits of switches

my thoughts on the problem.....
Because my throttle limit is strange and the throttles not at 0 theres a safety failsafe to prevent it from arming via the aux switch method while throttled
but by using the stick combo to arm bypasses the safety failsafe and allows it to activate

Is that possible ??
(I'm guessing of course)

Any help appreciated
Charles

nicog · Post by **nicog** » Sat Feb 02, 2013 10:21 am

charles, it's me, the coder, i see that you have an old switch list there. Should be level horizon in the first 2 rows. You need to have something like the image below.

Be sure that when starting the AIO you have the 1.1.11 version.

In theory the switch rows gets data from the board.

irun4fundotca · Post by **irun4fundotca** » Sat Feb 02, 2013 10:33 am

Thanks!!
Is the newer version listed on the first page?
my main problem has been java, I cant install it on my machine
and my user profile management has kept me from installing some non java related apps too (unsupported charicters in my username)
Up until recently I could'nt get anything other than mwiiwingui to run and firmware updates are impossible the version that I have has the cli program and update firmware built in and worked once..only once I now get an error when the update reaches 10 but I lost the arm abillity after the update

I have no problems starting over with the right tools that will work

nicog · Post by **nicog** » Sat Feb 02, 2013 10:38 am

the latest one is this: http://windows.naze32configurator.googl ... NAZE32AIO-[2012-10-20].rar

irun4fundotca · Post by **irun4fundotca** » Sat Feb 02, 2013 11:08 am

It worked thanks!!!!

I so did'nt want to revert to my kk5.5

Thanks again
Charles