Safety Warning

what stick mode is your tx setup on? i fly on mode3 which puts the throttle on the right stick, if the deviation is set to mode 2 i get the same warning until i set it to mode3...

Hi Vlad, i have the same litlle problem with my blade Nano on devitation 3.0.0 and Devo 8.

You can set the safety value in the model config. Normally in the section [safety] there are one or more values: ch3=min, ch1=min, auto=min...
auto=min takes the standard throttle channel depending on the chosen protocol: devo=ch3, dsm=ch1.
You should look which value is set and set it to auto=min to get rid of the safety warning.

Thx a lot RBE. Worked like a Dream. Note:This is configured by accessing model setup on a PC. BR/ Lars

8S - tx startup with Flight Mode switch on stunt position !

Is there a way to get a warning (like on 2801 etc.) when Flight Mode switch is on Stunt or Stunt 2 at tx switched on ?
Happened yesterday, luckyli with an Blade 450 3D which has Soft Start . . .

Thx PhracturedBlue

Again : FM Switch on Stunt Mode

As I too suffered with the "Channel3=0% . . ." warning I set
"Ch1=min"under "Safety" as advised which also helped with the Stunt Mode issue, because when FlightMode=1 (Stunt Mode 1) I get the warning "Ch1 is 75% etc."
But:
How can I get a warning which mentions the Flight Mode switch instead of Ch1 (or both FMSwitch and Ch1)?
Or in other words :
What would be the proper syntax under [safety] ?
What would be the parameters ?

Thx again !
You thought right !
That's exactly what I wanted to see.
But I still wonder where to get the right words (what I meant with Syntax) . . .
Trial and error ?
Anyway - thx a lot !

You can look into our work here: modelconfig-docu-work-in-progress
You will find most of the easier parameters documented, but esp. the mixer stuff is still missing. I personally regret that I do not have more time for this important theme topic (all my spare time goes into the coding actually).

Thx a lot rbe2012 anyway !
I assure You that I (and all the others out there) do appreciate Your work !

I also had the same Safety Warning "Ch3 is 0%, safe value = -100%" for the Blade models I made and posted on this site.
I used "auto=min" that rbe2012 recommended to use and it works great. Thanks rbe2012.

Hello, I find not the solution or I does not understand(include) (it is very possible)

I copy you my INI to the which I have an alarm of safety(security) on the CH3.

Thank you for your help(assistant)!

name=qav250devo fpv
mixermode=Advanced
icon=F450LI~1.BMP
[radio]
protocol=DEVO
num_channels=8
fixed_id=420606
tx_power=150mW

[protocol_opts]
Telemetry=On

[channel1]
reverse=1
failsafe=-100
template=simple
[mixer]
src=AIL
dest=Ch1
curvetype=expo
points=45,45

[channel2]
reverse=1
failsafe=-100
template=simple
[mixer]
src=THR
dest=Ch2
scalar=120
curvetype=expo
points=46,46

[channel3]
failsafe=-100
template=simple
[mixer]
src=ELE
dest=Ch3
curvetype=expo
points=45,45

[channel4]
reverse=1
failsafe=-100
template=simple
[mixer]
src=RUD
dest=Ch4
curvetype=expo
points=0,0

[channel5]
failsafe=55
template=expo_dr
[mixer]
src=FMODE0
dest=Ch5
scalar=-25
curvetype=expo
points=0,0
[mixer]
src=FMODE0
dest=Ch5
switch=FMODE1
scalar=-91
curvetype=expo
points=0,0
[mixer]
src=FMODE0
dest=Ch5
switch=FMODE2
scalar=110
curvetype=expo
points=0,0

[channel6]
template=simple
[mixer]
src=HOLD0
dest=Ch6
scalar=90

[channel7]
template=simple
[mixer]
src=GEAR1
dest=Ch7

[channel8]
failsafe=0
template=simple
[mixer]
src=!MIX1
dest=Ch8

[virtchan1]
name=RTH
[trim1]
src=LEFT_V
pos=TRIMLV+
neg=TRIMLV-
[trim2]
src=RIGHT_V
pos=TRIMRV+
neg=TRIMRV-
value=-1,0,0
[trim3]
src=LEFT_H
pos=TRIMLH+
neg=TRIMLH-
value=39,0,0
[trim4]
src=RIGHT_H
pos=TRIMRH+
neg=TRIMRH-
value=18,0,0
[trim5]
src=AUX4
pos=TRIM_L+
neg=TRIM_L-
switch=Ch7
step=8
value=64,0,0
[timer1]
src=THR
[telemalarm1]
source=Volt1
above=1
value=45
[telemalarm2]
source=Volt2
above=1
value=109
[telemalarm3]
source=Temp1
value=60
[telemalarm4]
source=Temp2
value=60
[telemalarm5]
source=Temp3
value=60
[telemalarm6]
source=Temp4
value=60
[datalog]
switch=None
rate=1 sec
[safety]
Auto=min
[gui-480x272]
V-trim=213,91,1
H-trim=86,236,3
V-trim=263,91,2
H-trim=271,236,4
Small-box=89,182,TelemT3
Small-box=89,209,TelemT4
Bargraph=285,175,Ch1
Bargraph=300,175,Ch2
Bargraph=315,175,Ch3
Bargraph=330,175,Ch4
Model=286,32
Toggle=210,54,1,64,128,FMODE
Toggle=248,54,72,7,0,HOLD
Toggle=227,92,0,66,0,RUD DR
Toggle=227,131,0,67,0,None
Toggle=227,169,70,68,0,GEAR
Toggle=227,208,8,71,0,None
Bargraph=345,175,Ch5
Bargraph=359,175,Ch6
Bargraph=373,175,Ch7
Small-box=89,33,Ch1
Small-box=89,100,Timer1
Big-box=286,131,TelemV2
Small-box=89,155,TelemT2
Small-box=89,128,TelemT1
quickpage1=Model setup
quickpage2=Telemetry config
quickpage3=Transmitter config
quickpage4=Main page config

If you look through this, you'll find a one-line section labelled "[safety]". That's the source of the problem. The line is "Auto=min", which is the default. That checks the output channel that is the throttle for your protocol, which is channel 3 so often that it will use that if there's nothing better to use. It wants it to be at -100 or lower. The idea is to keep the blades from spinning up when it connects, causing the model to fly away or possibly damage to nearby objects or people.

So what's going on is whichever stick your model is using for the throttle channel 3 isn't at -100 when you turn it on. That could be that the throttle stick is sprung to center if your transmitter is in the wrong mode, or it could be that you're not using channel 3 for the throttle for some reason. Either it's not supposed to be and deviation is wrong about it, or your model is unusual. Or it could be that your mix isn't lowering the throttle to -100 when it's all the way down for some reason.

If the issue is that it shouldn't be testing channel 3 or that channel 3 needs to be tested for a different value, you can edit the .ini file on the USB drive and change the setting yourself. It's documented in the manuals on the left under "Safety System". Those are for the nightly build, but are correct for 4.0.1 as well. Don't use Notepad on Windows for this - some if not all versions break things. Notepad++ works fine, though.