TC45 TC45 JAVA User's Guide
Confidential / Released
TC45_JAVA User's Guide_V02
Page 19 of 72
30.06.2003
3.5 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.
3.5.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 \IMPSIEMENS\doc\index.html [6].
3.5.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 [8]) on this AT
Command API instance before passing the first AT Command.
3.5.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.
