Revision 7.10
2/28/2012
Appendix I: Glider login_script_syntax.txt
This content is also available at:
http://www.gliderdoco.webbresearch.com/howtooperate/login_script_syntax.txt
login_script_syntax.txt ===================================================
This file discusses how to control the Iridium login process.
Table of Contents =========================================================
- Overview
- Example
- Error handling details
- How to change a script
- Revision history
= Overview ================================================================
The Iridium modem can automatically dial, connect, and log into a host
system.
Dialing and connecting are controlled by sensors (c_iridium_phone_num,
c_iridium_lead_zeros, c_iridium_on). Logging in is controlled by a
user-defined script stored in
c:\config\loginexp.<n>
where <n> depends on which "phone number" is being dialed.
There's a "dummy" example script in
persistor-prebuilt-binaries\config\loginexp.xxx
The loginexp.<n> script can handle 2 simplified "Expect" commands:
send timeout_secs "string"
sends a string to iridium uart ringbuffer. Proceeds to next instruction
as soon as they're actually transmitted (ringbuffer empty). If ringbuffer
not drained by timeout_secs seconds then automatically hang up and call
back.
expect timeout_secs "string"
waits up to timeout_secs seconds to get a string from the remote system.
Proceeds to next instruction as soon as they're received. Timeout causes
automatic hang up and call back.
Blank lines are ignored, and anything following a "#" character is a comment.
Any number of send/expect strings can be accomodated until memory runs out.
= Example ================================================================
Page 219 of 228
