User Manual Part 7

User Guide to Q4000/QPRO
Document Number 1135-4713 Rev G
THIS DOCUMENT CONTAINS CONFIDENTIAL AND PROPRIETARY INFORMATION OF QUAKE GLOBAL CORPORATION. IT MAY BE USED BY
RECIPIENT ONLY FOR THE PURPOSE FOR WHICH IT WAS TRANSMITTED AND WILL BE RETURNED UPON REQUEST OR WHEN NO LONGER NEEDED
BY RECIPIENT. DISCLOSURE TO UNAUTHORIZED THIRD PARTIES OR DUPLICATION WITHOUT THE EXPRESS WRITTEN PERMISSION OF QUAKE
GLOBAL IS PROHIBITED.
Page 135
CONFIDENTIAL
Information classified Confidential
-
Do not copy (See last page for obligations)
14 Event driven architecture
Event driven architecture is a significant element in the Q4000/QPRO user applications. Events
have been defined which correspond to significant internal and external signals and conditions
that are likely to appear. These events are then forwarded to the application.
Most actions the application takes in response to these events are handled by function calls.
Many of the calls represent high-level actions, such as “send this message,” which abstract the
low-level details. The Application Programming Interface (API) is set up so that these events are
mapped to the application developer's ‘C’ code. The following sections describe the supported
events and the circumstances under which they are posted.
The supported events of the Q4000/QPRO are:
• CAN_MSG
• CELL_NET_IN_VIEW
• CONTINUE
• COUNTER
• DIGITAL
• DIGITAL_ALARM
• GLSS_AVAILABLE
• MTS_DTR
• MSG_ACK
• MSG_ALERT,
• MSG_MID_CHANGED
• MSG_NAK
• MSG_RCVD
• MSG_SEND_NAK
• NET_CLEAR
• NMEA_SENTENCE
• NO_EVENT
• ORB_ANTENNA_VSWR
• POSITION_FIX
• POSITION_ALARM
• POWER_ON
• RX_MTS_PKT
• RX_SER_PKT
• SAT_IN_VIEW
• SHUTDOWN
• SPEED ALARM
• TIMER
• TIME_SYNC
• USER_CMD