Special At Command Set For Java Applications; Switching From Data Mode To Command Mode; Mode Indication After Midlet Startup; Long Responses - Siemens TC65 JAVA User Manual
Cellular
Hide thumbs
Also See for TC65 JAVA:
- Hardware interface description (99 pages) ,
- User manual (90 pages) ,
- Operating instructions manual (55 pages)
Table of Contents
Advertisement
TC65 JAVA User's Guide
Strictly confidential / Draft
5.6
Special AT Command Set for Java Applications
For the full AT command set refer to [4]. There are differences in the behaviour of issuing AT
commands from a Java application compared to using AT commands over a serial interface.
5.6.1
Switching from Data Mode to Command Mode
Cancelling the data flow with "+++" is not available in Java applications, see [4] for details. To
break the data flow use breakConnection(), refer to \wtk\doc\index.html [6].
5.6.2
Mode Indication after MIDlet Startup
As on the serial interface after starting the module without autobauding on, the module sends
its state (^SYSSTART, ^SYSSTART ALARM MODE etc.) to the MIDlet. This is done via 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 [6]) on this AT Command
API instance before passing the first AT Command.
5.6.3
Long 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, i.e. at^moni, at^smong.
These AT commands have to be used without parameters, i.e. at^moni the periods have
to be implemented in Java.
5.6.4
Configuration 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 serial interface are ignored. Especially
these are the following:
• AT+IPR
• AT\Q3
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 by the class
CommConnection. This is fully independent of any AT commands relating a serial interface.
5.6.5
Java Commands
There is a small set of special Java AT commands:
TC65 JAVA User's Guide_V01
Page 27 of 69
s
11.03.2005
Advertisement
Table of Contents
