User Guide to Q4000/QPRO CONFIDENTIAL Information classified Confidential - Do not copy (See last page for obligations) 3. checkSerRxData() is called when serial data are available. It processes the data and sends a message to the foundation to notify it that these data belong to the application for processing.
User Guide to Q4000/QPRO Information classified Confidential - Do not copy (See last page for obligations) CONFIDENTIAL 4. The data are then sent out over the first available network in the call to NIMM_send(). Figure 12-33: DemoAppSERIAL - Call to NIMM_send() Document Number 1135-4713 Rev G Page 96 THIS DOCUMENT CONTAINS CONFIDENTIAL AND PROPRIETARY INFORMATION OF QUAKE GLOBAL CORPORATION.
User Guide to Q4000/QPRO CONFIDENTIAL Information classified Confidential - Do not copy (See last page for obligations) 5. Figure 12-34 (from the Logger port) shows that the message has been successfully transmitted with the line: Tx[TERR}123456789. Figure 12-34: DemoAppSERIAL - Logger output of sending serial message Document Number 1135-4713 Rev G Page 97 THIS DOCUMENT CONTAINS CONFIDENTIAL AND PROPRIETARY INFORMATION OF QUAKE GLOBAL CORPORATION.
User Guide to Q4000/QPRO 12.4.3 DemoAppREMOTE This application demonstrates sending remote messages via GSM/GPRS and POP email to the modem and the proper evaluation and operation of these message events. Message events include sending an email to the modem, setting a relay, and remotely downloading a file to the modem. In this example, you must have at least one valid email address for your modem. Note that this sample application uses network-specific calls.
User Guide to Q4000/QPRO 12.4.3.1 Remotely set a relay (via email) If the GSM/GPRS network is detected, DemoAppREMOTE checks for an incoming POP email message. You may send the email from any email program such as Microsoft Outlook. For an ORBCOMM modem, send an email to your modem with the words RELAY0=1 in the body of the message. The subject line of the email doesn’t matter. Figure 12-36 is an example of a Relay email to an ORBCOMM modem.
User Guide to Q4000/QPRO Information classified Confidential - Do not copy (See last page for obligations) CONFIDENTIAL Figure 12-38 shows a call to MSG_receiveTerr(), which checks for an incoming POP email on the GSM/GPRS network after receiving a TIMER_EVENT (that occurs every REMOTE_CONTROL_DEMO_CHECK_GSM_TIMER_DUR_SECS).
User Guide to Q4000/QPRO If a POP email message is received, it will trigger a MSG_RCVD event. Figure 12-39 shows the processing of the retrieved message. First, the event’s parameter is checked to determine if it is an SMS, POP or satellite incoming message. • When it is recognized as a POP message, ParseCommandMessage() is called to parse the incoming message into its constituent parts.
User Guide to Q4000/QPRO In Figure 12-40, ParseCommandMessage() does the following: An occurrence of the relayCmd, “RELAY” is sought. • If it is found, the relay number and value are extracted by the atoi() calls and the relay number is verified to be less than two. • Using the function, RELAY_writeChannel(), a command is sent to the RELAY module to set the appropriate relay.
User Guide to Q4000/QPRO CONFIDENTIAL Information classified Confidential - Do not copy (See last page for obligations) Figure 12-41 shows the Logger output at the time the message is received. Note the Logger output from the application: Set Relay 0 ON (Closed). This indicates that the message was received, parsed properly and that the relay has been closed.
User Guide to Q4000/QPRO 12.4.3.2 Remotely download a file to the modem (via email) The Q4000/QPRO API includes function calls that allow a user to download a file from a remote server to the modem’s file system. This allows you to update an application running on the modem. The DemoAppREMOTE application demonstrates the File Transfer Protocol (FTP) capability by processing an email to download a file to the modem.
User Guide to Q4000/QPRO Figure 12-43: DemoAppREMOTE - Parse incoming remote application update message Document Number 1135-4713 Rev G Page 105 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.
User Guide to Q4000/QPRO Figure 12-44: DemoAppREMOTE - Event for FTP Load Successful As the foundation code goes through the process of downloading the file, the various states are printed out to the Logger. Here are the examples of the states: FTP_STATE_READY, FTP_STATE_INITIALIZE, FTP_STATE_CONTEXT_ACTIVATED, FTP_STATE_CONNECTION_ACTIVATED, FTP_STATE_DOWNLOAD, FTP_STATE_CONNECTION_CLOSE, FTP_STATE_STOP // Initial state of the state machine // Request received state.
User Guide to Q4000/QPRO 12.4.4 DemoAppCAN The DemoAppCAN sample application demonstrates how the Q4000/QPRO receives Society of Automotive Engineers (SAE) J1939 messages on the CAN bus. SAE J1939 is the vehicle bus standard used for communication and diagnostics among vehicle components, originally by the car and heavy duty truck industry in the United States. Note that this sample application uses network-specific calls.
User Guide to Q4000/QPRO Figure 12-45: DemoAppCAN - Selecting the Workspace 2. Now build, load and execute DemoAppCAN. The instructions for building, loading and executing the code are the same as in Section 12, except that after building the application, the executable bin file is: …/DemoAppCAN/exe/xxx-DemoAppCAN.bin. 3. After startup, check the Logger output for the line APL DEMO: CAN/J1939. This indicates that the correct DemoApp is running.
User Guide to Q4000/QPRO Information classified Confidential - Do not copy (See last page for obligations) CONFIDENTIAL This application was tested at QUAKE by using two Q4000 modems connected together. Their CAN inputs and outputs each sent and received data from each other at the same time. They were configured to use Parameter Group Number (PGN) message 61444. Figure 12-46 shows the initialization of the J1939 stack.
User Guide to Q4000/QPRO Figure 12-47 shows the POWER_ON event. Note that the: buffer pointer in the J1939 message structure must be initialized to some allocated memory of sufficient size to hold the message data • buf_len member in the structure must be initialized as well • CAN timer is set to expire in CAN_INTERVAL_SECS.
User Guide to Q4000/QPRO CONFIDENTIAL Information classified Confidential - Do not copy (See last page for obligations) Figure 12-48 shows the TIMER event, which first checks for the CAN timer number, then sends the CAN message. Figure 12-48: DemoAppCAN - Transmit J1939 data Document Number 1135-4713 Rev G Page 111 THIS DOCUMENT CONTAINS CONFIDENTIAL AND PROPRIETARY INFORMATION OF QUAKE GLOBAL CORPORATION.
User Guide to Q4000/QPRO Information classified Confidential - Do not copy (See last page for obligations) CONFIDENTIAL In Figure 12-49, the TIMER event then reads the CAN data for this PGN from the other modem with the call J1939_getPgnMsg(). Figure 12-49: DemoAppCAN - Receive J1939 data Document Number 1135-4713 Rev G Page 112 THIS DOCUMENT CONTAINS CONFIDENTIAL AND PROPRIETARY INFORMATION OF QUAKE GLOBAL CORPORATION.
User Guide to Q4000/QPRO Figure 12-50 shows the output after the CAN timer has expired, with the printout of the RPMs from the PGN 61444 message: Information classified Confidential - Do not copy (See last page for obligations) CONFIDENTIAL Got CAN_MSG: pgn = 61444 EngineRPM = 40920 Figure 12-50: DemoAppCAN - Logger output for engine RPM Document Number 1135-4713 Rev G Page 113 THIS DOCUMENT CONTAINS CONFIDENTIAL AND PROPRIETARY INFORMATION OF QUAKE GLOBAL CORPORATION.
User Guide to Q4000/QPRO 12.4.5 DemoAppFFS The FFS example demonstrates use of the Flash File System (FFS). The application gets a GPS position each time it starts, and creates a trail of the last positions which is stored in the FFS, so that the trail of positions is retained over power cycles. The FFS functionality demonstrated is fairly basic. Note that this application is network-specific. Figure 12-51: DemoAppFFS - Selecting the Workspace 2. Now build, load and execute DemoAppFFS.
