Cep Terminals GSM/GPRS TERMINAL CT63 JAVA 6203 User Manual

5.8 Special AT Command Set for Java Applications



wm_java_usersguide_v19

Page 31 of 109

2012-01-27

Confidential / Released

For the full AT command set refer to 

. There are differences in the behaviour AT commands 

issued from a Java application in comparison to AT commands issued over a serial interface.

Cancellation of the data flow with “+++” is not available in Java applications, see 

 for details. 

To break the data flow use breakConnection(). For details refer to 

After starting a module without autobauding on, the startup state is indicated over the serial in-
terface.  Similarly, after MIDlet startup the module sends its startup state (^SYSSTART, ^SYS-
START AIRPLANE MODE etc.) to the MIDlet. This is done via a URC to the AT Command API 
instance which executes the very first AT Command from within Java. To read this URC it is 
necessary to register a listener (see 

) on this AT Command API instance before passing the 

first AT Command.

The AT Command API can handle responses of AT commands up to a length of 1024 bytes. 
Some AT commands have responses longer than 1024 bytes, for these responses the Java 
application will receive an Exception.

Existing workarounds:
•

Instead of listing the whole phone book, read the entries one by one

•

Instead of listing the entire short message memory, again list message after message

•

Similarly, read the provider list piecewise

•

Periods of monitoring commands have to be handled by Java, e.g. AT^MONI, AT^SMONG.
These AT commands have to be used without parameters, e.g. for AT^MONI the periods
must be implemented in Java.

While a Java application is running on the module, only the AT Command API is able to handle 
AT commands. All AT commands referring to a serial interface are ignored. This includes the 
commands:
•

AT+IPR (sets a fixed local bit rate)

•

AT\Q1, AT\Q2 and AT\Q3 (sets type of flow control)

If Java is running, the firmware will ignore any settings from these commands. Responses to 
the read, write or test commands will be invalid or deliver „ERROR“. 

Note: When a Java application is running, all settings of the serial interface are done with the 
class CommConnection. This is fully independent of any AT commands relating to a serial in-
terface. However, the following restrictions apply in configuring the serial interface: Baudrate: 
Only 300, 600, 1200, 2400, 4800, 9600, 14400, 19200, 28800, 38400, 57600, 115200, 230400 
and 460800 are supported; Stopbits: Only "1" is supported; Parity: "7N1" is not supported.