Switch Options
Posted by wclark
|
January 07, 2023 07:02PM |
|
January 09, 2023 09:34AM |
Hi,
for co-readers or those interested, I provide more details
The reasoning becomes clearer when looking at the menus in VBar Control Classic. There you had
. Mandatory Switches (which all models require)
.. Motor -> phys. switch -> direction
.. Bank -> phys. switch -> direction
.. Buddy -> phys. switch -> direction (debatable but makes also sense)
These are hardwired to functions in the VBar NEO, which is the flight controller after all.
So whatever radio you use, Motor is Motor, no matter what physical switch is assigned.
These switches also work in case the software (user interface) would freeze or crash or shutdown (in case the back link, telemetry link, would fail).
They are kind of hard wired to the radio link layer which is running on a separate hardware and software layer. Basically, you could delete the user interface, format the radio's drive, during flight, but you could still control and land the model safely, because of that separate layer and it's parameters still stored. Of course, after setting up the radio again, you'd have to check and if need be assign switches and calibrate the sticks again.
. Local Switches
.. Parameter Lock -> phys. switch -> direction
.. Security -> phys. switch -> direction
These are switches used for radio functions, lock the possible change of parameters with e.g. rotary inputs, and add an additional switch to the Motor Logic, overriding the Motor Switch. The latter meant for pilots who are used to or prefer to have to flip two switches, to engage the drive, for security reasons.
. Optional Switches
.. Opt 1...3 -> phys. switch -> direction
These are meant to assign physical switches to optional functions.
In Apps adding optional functions like Rescue, Nitro, you assign those Optional Switches but not physical switches.
Indeed it's helpful if you bind different radios to the same model, with different switch assignments and stick modes: stick mode and switch assignments are stored in the radio, per pilot, so if your buddy e.g. has his Rescue Switch on Option 1 (but has assigned physical switch 6) and you have yours on Option 1 but assigned physical switch 1), the radio and the flybarless can negotiate it and you are both safe flying the model.
In Touch and EVO, the three separate menus have been integrated into one menu, also because it's clearer to see all the assignments in one place graphically, it's less likely you create doubles by mistake (think of Safety and Rescue -> Option 1 on one physical switch, where you missed that both are e.g. switch 1, and you'd cut your drive system when actuating Rescue).
Still, wenn sharing models the first time, or when binding different radios the first time, a pre-flight-check is mandatory, because you never know, and because you want to be sure.
Good airmanship
But you can always be sure that Motor, Bank (mandatory switches) are what they are, no matter what.
—Eddi
Born to fly ...
forced to work.
for co-readers or those interested, I provide more details
The reasoning becomes clearer when looking at the menus in VBar Control Classic. There you had
. Mandatory Switches (which all models require)
.. Motor -> phys. switch -> direction
.. Bank -> phys. switch -> direction
.. Buddy -> phys. switch -> direction (debatable but makes also sense)
These are hardwired to functions in the VBar NEO, which is the flight controller after all.
So whatever radio you use, Motor is Motor, no matter what physical switch is assigned.
These switches also work in case the software (user interface) would freeze or crash or shutdown (in case the back link, telemetry link, would fail).
They are kind of hard wired to the radio link layer which is running on a separate hardware and software layer. Basically, you could delete the user interface, format the radio's drive, during flight, but you could still control and land the model safely, because of that separate layer and it's parameters still stored. Of course, after setting up the radio again, you'd have to check and if need be assign switches and calibrate the sticks again.
. Local Switches
.. Parameter Lock -> phys. switch -> direction
.. Security -> phys. switch -> direction
These are switches used for radio functions, lock the possible change of parameters with e.g. rotary inputs, and add an additional switch to the Motor Logic, overriding the Motor Switch. The latter meant for pilots who are used to or prefer to have to flip two switches, to engage the drive, for security reasons.
. Optional Switches
.. Opt 1...3 -> phys. switch -> direction
These are meant to assign physical switches to optional functions.
In Apps adding optional functions like Rescue, Nitro, you assign those Optional Switches but not physical switches.
Indeed it's helpful if you bind different radios to the same model, with different switch assignments and stick modes: stick mode and switch assignments are stored in the radio, per pilot, so if your buddy e.g. has his Rescue Switch on Option 1 (but has assigned physical switch 6) and you have yours on Option 1 but assigned physical switch 1), the radio and the flybarless can negotiate it and you are both safe flying the model.
In Touch and EVO, the three separate menus have been integrated into one menu, also because it's clearer to see all the assignments in one place graphically, it's less likely you create doubles by mistake (think of Safety and Rescue -> Option 1 on one physical switch, where you missed that both are e.g. switch 1, and you'd cut your drive system when actuating Rescue).
Still, wenn sharing models the first time, or when binding different radios the first time, a pre-flight-check is mandatory, because you never know, and because you want to be sure.
Good airmanship
But you can always be sure that Motor, Bank (mandatory switches) are what they are, no matter what.
—Eddi
Born to fly ...
forced to work.
Sorry, only registered users may post in this forum.