TC65 JAVA User's Guide
Strictly confidential / Draft
Basic maintenance features of the TC65 are described below. Explicit details of these
functions and modes can be found in the AT Command Set  and the Hardware Interface
The module supports several power saving modes which can be configured by the AT
command at+cfun . Power saving affects the Java application in two ways. On the one
hand it limits the access to the serial interface (RS-232-API) and the GPIO pins and on the
other hand power saving efficiency is directly influenced by the way a Java application is
Java hardware access limitations:
• In NON-CYCLIC SLEEP mode (cfun=0) the serial interface cannot be accessed while in
CYCLIC SLEEP mode (CFUN=7 or 9) the serial interface can be used with hardware flow
• In all SLEEP modes the GPIO polling frequency is reduced, so that only signal changes
which are less than 0.2Hz can be detected properly. Furthermore it should be mentioned
that the signal must be constant for at least 2.12s to detect changes. For further details
refer to .
Java power saving efficiency:
• As long as any Java thread is active, power consumption cannot be reduced, regardless
whether any SLEEP mode has been activated or not. So a Java application that wants to
be power efficient should not have any unnecessarily active threads (e.g. no busy loops).
Please refer to  and  for general information about charging. Charging can be monitored
by the running Java application. The JVM is active in Charge mode and when autostart is
activated also in Charge-Only mode. Only a limited number of AT commands are available
when the module is in Charge-Only mode. A Java application must be able to handle the
Charge-Only mode and reset the module to reinstate the normal mode. See  for
information about the Charge-Only mode.
The Charge-Only mode is indicated by URC "SYSSTART CHARGE-ONLY MODE".
Note: When a Java application is started in Charge-Only mode only AT Command APIs
without CSD are available. The indicating URC is created after issuing the very first AT
command on any opened channel. To read the URC it is necessary to register a listener (see
) on this AT command API instance before passing the first AT command.
TC65 JAVA User's Guide_V01
Page 24 of 69