This is pretty explanatory… there’s a pull-down to select the channel that you want to test, then
you simply enter the 4-digit validation code and click on the TEST button. The channel settings
are inherited from the Global Settings page… for example, if you have a channel set to be used
in igniter mode with a 3-second firing time then that channel will fire for 3 seconds.
If you set a channel up for servo deployment, it will use the same servo direction and
direction/skew that you programmed into Global Settings, but you have the option to SET the
servo (rotate in the “on” direction) or RESET the servo (rotate the servo in the opposite
direction). The RESET function can be used when you’re at your worktable to close up the
deployment bay… typically, servo deployments use some kind of trapdoor system so you’ll
generally need to rotate the servo in the opposite direction to close it up after you pack the
parachute. You generally don’t want to do this by manually moving the servo’s output wheel,
since that can strip the gears.
After you enter the validation code and click on the TEST button, you’ll see a count down screen
from 5 to zero seconds, after which time it will trigger the deployment device. When it’s done, it
goes back to the Deployment Test page.
If for some reason you need to abort a test, all you need to do is to close your browser BEFORE
it counts down to zero. After you close it, you should open the Status Page; re-opening the test
page immediately after closing it may cause it to be resumed from that point, depending on how
your browser caches pages.
Note: NEVER do a deployment test with just a piece of bare wire, you need to have some kind
of resistive load such as an ematch, igniter, or small piece of fine nichrome wire (#36 or #40, for
example). We’ve designed the Quasar very conservatively, and drivers automatically provide
current limiting to help protect the circuitry and your battery. Nevertheless, it is still possible to
blow something up if you try hard enough.