(only available for certain terminals with a suitable serial aynchronous interface, and a special firmware)
Note: Since we never managed to get the GSM/GPRS modem's internal FTP client running properly (without hardware handshake), we abandoned the support for GSM/GPRS modems in the MKT-View terminal completely. Sorry about that, but we had more important things to do. If you think you need something with a full TCP/IP protocol stack, buy a device with embedded Windows or Linux ;-)
This document describes how the terminal can be connected to an external GSM/GPRS modem through the serial interface. For this purpose, certain terminal firmware variants have built-in support for such modems.
Note: Only very few terminals support this optional function
- see Feature Matrix : "GSM modem") !
Furthermore, this feature must be unlocked (by the manufacturer, or via password)
before using it .
See also:
Note: The support for GSM/GPRS modems inside the terminal is an optional feature, which must be unlocked to use it. You can use this function for testing purposes (before paying for it) in "evaluation mode". In evaluation mode, most of the functions mentioned in this document will work only for a few minutes after power-up. This is not a bug, but a motivation to contact the manufacturer to have this feature unlocked. The unlock procedure is described in document #85115 "System Menu and Terminal Setup" (same procedure as for other unlockable features, just a different 'UNLOCK' password).
The terminal must know a lot of things about your SIM card, about your GSM/GPRS service provider, and how the modem shall connect to the internet (one fine day). This information is usually stored in a special modem configuration file ("modem.cfg"), located on the compact flash card (or, during software development, in the directory of the programming tool).
Here is an example for such a file. Of course, YOU must provide all required data ! Use a plain text editor to write your own configuration. The phone numbers for most GSM/GPRS services can be found on the homepage of your wireless service provider (hopefully ... the author had some trouble to find all required info ! ). A few notes about the syntax of the modem configuration file follow after this example :
; GSM/GPRS modem configuration file for MKT-view . ; Modify this according to your SIM card / service provider ! ; Save the modified file as "modem.cfg" ON THE COMPACT FLASH CARD . Encryption=0 ; 0 if this file is NOT scrambled [SIM_Card] PIN=0815 ; first PIN of the SIM card MyNr=0123456789 ; "my phone number" [Provider] .... still a lot of work to do here .... ;-) [GPRS] [SMS] [Email] [FTP_Up]
Notes:
Modem control commands and -functions in alphabetical order:
gsm.baud
@gsm.baud=4800
sets the baudrate of the serial port to 4800 bit/sec (this is the
maximum supported by most of MKT's programmable terminals).
gsm.cfg
gsm.pin
gsm.login
Many GSM modems can be used as mobile phones for voice calls too. They usually have a standard audio connector for this purpose. The following interpreter commands can be used to make outgoing voice calls, and accept incoming voice calls. Of couse, they only work if the modem is registered ("logged into") the GSM network.
gsm.vc(<dialing
string>)
gsm.ringing
gsm.accept
gsm.off
There is a small test file for the MKT-View which demonstrates some of the modemr functions. You can load it from \programs\gsm_test.cvt .
On this screen of the test application, some of the modem control functions are shown, along with the results when testing it with a modem and (SIM card properly installed).
The baudrate or the serial interface between terminal and modem is displayed. The SIM PIN and the SIM's own phone number are made unreadable here for privacy.
"Registered" means the modem is logged into the GSM network; which means
it can accept calls and make outgoing calls.
"Connected" means the modem is involved in a connection (voice or data) at
the moment.
"Roaming" means the modem is currently using a foreign provider. This is
not possible with all SIM cards ! Caution: International roaming can cause
high additional costs, so it may be a good idea to include a similar indicator
in your own terminal application too, so the operator can see what's going
on (don't blame us for an enormous telephone bill - you are responsible for
what your application does with the modem ! ).
The "gsm.rcvd" function shows the last response received from the modem. This is often one of the URC's (Unsolicited Result Code) which are explained in your modem manufacturer's manual (often called something like "AT Command Set", though URCs are no AT-commands). Some examples for such URCs are here.
.
Originally, the serial port was exclusively used to download the terminal application ("user program") through the PC's RS-232 interface. Since the serial port may now be occupied by the GPS receiver or a GSM modem, the terminal cannot (always) listen for commands from the PC. Why ?
The program download between PC and Terminal uses a block-oriented protocol for the serial port called "3964R". When you select "Send application to the terminal through the serial port", but the serial port is occupied by the application (as described in this document), the 3964R-handler may be passive to avoid interference with the protocol which your terminal-application uses (through appropriate interpreter commands). The PC will therefore never receive the expected response from the terminal .... and your terminal application will, at least, be "irritated" by the characters received from the serial port.
So what to do in this case, when your application occupies the terminal's serial port, but you want to download a new application through just this port ? The solution is:
The terminal will reprogram the serial port for communication with the PC in this case, which includes the initialisation of the 3964R-protocol.
If the serial port is not occupied by the terminal-application or the GPS-decoder (which is the default, see gps.prot), you don't necessarily have to use the system menu to activate the download.
File: ..?..\uptwin1\help\modem_01.htm
Author: W.Büscher, MKT Systemtechnik
Last modified: 2006-06-07 (ISO8601, YYYY-MM-DD)