Siemens TC65 Special AT Command Set for Java Applications, Mode Indication after MIDlet Startup

Java User’s Guide

5.8 Special AT Command Set for Java Applications

s

5.8Special AT Command Set for Java Applications

For the full AT command set refer to [1]. There are differences in the behaviour AT commands issued from a Java application in comparison to AT commands issued over a serial interface.

5.8.1Switching from Data Mode to Command Mode

Cancellation of the data flow with “+++” is not available in Java applications, see [1] for details. To break the data flow use breakConnection(). For details refer to [3].

5.8.2Mode Indication after MIDlet Startup

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

5.8.3Long Responses

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.

5.8.4Configuration of Serial Interface

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 interface.

wm_java_usersguide_v12	Page 40 of 123	2008-02-25
Confidential / Released