Revision 7.10
2/28/2012
the successful match condition becomes true. If the countdown timer expires during
matching, then the match process is stopped and the timeout condition becomes true.
5. If any condition is true, then the state given in that condition’s corresponding
“toState” attribute becomes the current state, the match buffer is cleared up to and
including the matched glider output (if a timeout condition is true, the entire buffer is
cleared), and script interpretation continues with step 2.
If no condition is true, then glider output received during matching (step 4) is
appended to the match buffer and script interpretation continues with step 4.
The previous examples are taken from the following complete script.
<?xml version="1.0" encoding="UTF8"?>
<!
Date
Author
Comments
Nov 30, 2004
Created.
Dec 18, 2004
Add responding to commands that do not
verify.
Dec 21, 2004
Fixed Iridium "double" surface dialog
burst where two s *.sbd are sent
in response to two "...RESUME" triggers.
>
<!
Used during a mission to transfer sbd files to the dockserver and then resume
the mission. For use with dockserver version 1.2 and up.
>
<gliderScript>
<! Start state. When a glider surface dialog is seen, send the "s" command and
transition to verify that the command was received.
>
<initialState name="sendzModem">
<transitions>
<! If a surface dialog is seen, send "s" command and transition to
verify that command received.
>
<transition matchExpression="Hit ControlR to RESUME" toState="verifyzModem">
<action type="glider" command="s *.sbd">
Page 201 of 228
