Search Sort Posts:  Oldest to newest Newest to oldest

03-29-2004, 8:24 AM rhernandez Joined on 11-26-2003 Madrid - SPAIN Posts 42 Sending SMS Text Messages from B3000-ENET SMS Text Messages require an external GSM modem. While this cannot be connected directly to the B3000-ENET processor, you can connect it by using a SNAP-SCM232 module. (The RS232 port on the brain only allows PPP connections or ioManager maintenance mode) Through scratchpad configuration any digital or analog event can be made to activate an event message. Enabling a serial module message and configuring the corresponding serial port mask allows SMS messages to be sent to any GSM mobile phone using standard AT commands. Example: AT+CMGS=7017729000Required Text Message Where: 7017729000 is the mobile phone number where the message is to be sent. is represented using _ in a brain running V5.0 software or higher is represented using the plugin _ in a brain running V5.0 software or higher Tip01. Understand if your GSM modem supports PDU mode or Text.mode only. If it does support both you may need to include CMGF=1 in the AT command to switch to text mode. If the modem does not support PDU mode then sending this command can cause the modem to lock up! If the modem does support both PDU and Text modes, the previous AT command would need to be changed to. (Note representation of and ) AT+CMGF=1+CMGS=7017729000 _ Required Text Message_ Tip02. You can include plugins in the field “Required Text Message” to customize the message sent or include realtime data. An SMS message text can include up to 160 characters. Do not use accents as not all mobile phones treat accented characters in the same way. Some even lock up when trying to read the received message! Tip03. Make sure the scratchpad logic does not allow several different event messages to be activated at the same time. Most modems require a small time delay between messages, to process the buffer. Not respecting this will cause the first SMS messages to be corrupted, and following SMS messages to be lost, although exact effects depend on the modems characteristics. Tip04. Store the phone number in another scratchpad text register and use a plugin to include this in the AT command being sent to the modem. That way if you need to change to phone number (Guy on holiday, lost phone etc) its not a nightmare to reconfigure all the event messages. Tip05. Don’t forget to save all configuration changes to flash, through the Status Write Operation Commands, or else on next power loss, your work will mysteriously disappear. Also note that option is dangerously right next to the option “Erase configuration from flash”    Report

OptoForums » Application For... » Automation, Con... » Sending SMS Text Messages from B3000-ENET

(please select) Forums Home |- Search Forums |- Active Topics |- Unanswered Posts User Options |- Sign In |- Join this community |- Forgot Password Product Forum |- SNAP PAC Systems |- Other Hardware Systems |- Other Software |- Protocols and Drivers |- SNAP PAC Learning |- Shoot This, Opto! Application Forum |- Automation, Control, Data Acquisition, and Remote Applications |- Systems Integrator, VAR, and OptoPartner Section |- Where's Your Opto 22? International |- Opto 22 in Latin America |- Opto 22 Forum for French (Français) Speaking Customers