TC65i AT-Commands Set. Manual - part 6

 

  Index      Manuals     TC65i AT-Commands Set. Manual

 

Search            copyright infringement  

 

 

 

 

 

 

 

 

Content      ..     4      5      6      7     ..

 

 

TC65i AT-Commands Set. Manual - part 6

 

 

Examples
EXAMPLE 1
Make a new phonebook entry at the first free location
AT+CPBW=,"+431234567",145,"international"
EXAMPLE 2
Delete entry at location 1
AT+CPBW=1
EXAMPLE 3
The following examples are provided to illustrate the effect of writing phonebook entries with different types
of dial string modifiers in <number>
AT+CPBW=5,"12345678",,"Arthur"
AT+CPBW=6,"432!+-765()&54*654#",,"John"
AT+CPBW=7,"432!+-765()&54*654#",129,"Eve"
AT+CPBW=8,"432!+-765()&54*654#",145,"Tom"
AT+CPBW=9,"432!+-765()&54*654#",209,"Richard"
EXAMPLE 4
Read phonebook entries from locations 5 - 9 via AT+CPBR
+CPBR:5,"12345678",129,"Arthur"
+CPBR:6,"432!+-765()&54*654#",209,"John"
+CPBR:7,"432+76554*654#",129,"Eve"
+CPBR:8,"+432+76554*654#",145,"Tom"
+CPBR:9,"432!+-765()&54*654#",209,"Richard"
17.6
AT^SPBW Write into Phonebook with location report
The AT^SPBW write command can be used to create, edit and delete a phonebook entry at a <location> of
the active storage selected with AT+CPBS. After having written the phonebook entry <location> is shown.
If <storage>="FD" (SIM fixed dialing numbers) is selected, PIN2 authentication has to be performed prior to
any write access.
The AT^SPBW test command returns the location range supported by the current storage, the maximum length
of the <number> field, the range of supported <type> values and the maximum length of the <text> field.
Note: The length may not be available while SIM storage is selected. If storage does not offer format information,
the format list contains empty parenthesizes.
Syntax
Test Command
AT^SPBW=?
Response(s)
^SPBW: (1-<maxloc>), <nlength>, (list of supported <type>s), <tlength>
OK
ERROR
+CME ERROR: <err>
Write Command
AT^SPBW=[<location>][, <number>[[, <type>][, <text>]]]
Response(s)
^SPBW: <location>
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
Reference(s)
+
+
+
+
+
+
+
-
+
-
GSM 07.07, GSM 04.08
Parameter Description
<location>(num)
Location number within phonebook memory. The maximum range supported by each storage type is indicated
in the test command response. If <location> is not given, the first free entry will be used.
If <location> is given as the only parameter, the phonebook entry specified by <location> is deleted.
<number>(str)
Phone number in format specified by <type>. Parameter must be present, although it may be an empty string.
Alphabetic characters are not permitted. <number> may contain dialstring modifiers "*", "#" or "+".
If other printable non-alphabetic characters are used the entry needs to be saved with <type>=209. Otherwise,
if <type>=209 is not used any non-digit characters other than "*", "#" or "+" will be removed from the string and
only accepted modifiers from the GSM alphabet will be saved.
A <number> saved with <type>=209 requires double memory. In order to fit into a standard location, the num-
ber needs to be reduced to a maximum length of <nlength>/2, including all digits and dial string modifiers.
Extended locations may be used as stated below for <nlength>.
<type>(num)
Type of address octet, which defines the used type of number (ton) and the numbering plan identification (npi).
Please consider that for types other than 129 or 145 dialing from phonebook with ATD><mem><n> is, depending
on the network, not always possible (refer GSM 04.08 subclause 10.5.4.7 for details).
If <type> is not specified the unknown <type>=129 is used. If <number> contains a leading "+" <type>=145
(international) is used.
Supported values are:
145
Dialing string <number> includes international access code character "+"
161
National number. The network support for this type is optional.
209
Dialing string <number> will be saved as ASCII string.
This is the default value, if <type> is not specified explicitly and characters
other than "*", "#" or "+" are included in <number>.
Note that phonebook entries saved with this type cannot be dialed.
255
Dialing string <number> is a command to control a Supplementary Service,
i.e. "*", "#" codes are contained. Network support of this type is optional.
129
Unknown number. If <type> is unknown and the <number> contains a lead-
ing "+", <type>=145 (international) is used.
<text>(str)(+CSCS)
Text assigned to the phone number. The maximum length of this parameter is given in the test command
response <tlength>. When using an ASCII terminal, characters which are coded differently in ASCII and GSM
have to be entered via escape sequences as described in Section 1.6, Supported character sets.
<maxloc>(num)
Maximum number of locations supported by the currently selected storage. For phonebooks located on SIM,
this value varies depending on the SIM card. See AT+CPBS for typical values.
<nlength>(num)
Maximum length of phone number for "normal" locations. Depending on the storage, a limited number of loca-
tions with extended memory is available per phonebook. These locations allow storing numbers with twice the
standard length, which is 2*<nlength> digits for normal numbers, but only <nlength> digits for numbers
saved with parameter <type>= 209. If all extended locations of the selected phonebook are used up, then any
attempt to write a number which requires extended memory will be denied with "+CME ERROR: invalid dial
string".
<tlength>(num)
Maximum length of <text> assigned to the telephone number. The value indicated by the test command is
given in octets. If the <text> string is given in GSM characters, each character corresponds to one octet. If the
<text> string is given in UCS2, the maximum number of characters depends on the coding scheme used for
the alpha field of the SIM. In the worst case the number of UCS2 characters is at least one less than half the
number of GSM characters.
For a detailed description please refer to GSM 11.11, Annex B [25].
Notes
• Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data
may not yet be accessible, resulting in a short delay before the requested AT command response is returned.
See Section 23.1, Restricted access to SIM data after SIM PIN authentication for further detail.
• During AT^SPBW write command it is possible that in some cases returns "+CME ERROR: operation tempo-
rary not allowed". Use AT^SPBW write command again.
Examples
EXAMPLE 1
Make a new phonebook entry at the first free location (here location 3)
AT^SPBW=,"+431234567",145,"international"
^SPBW: 3
EXAMPLE 2
Delete entry at location 3
AT^SPBW=3
EXAMPLE 3
The following examples are provided to illustrate the effect of writing phonebook entries with different types
of dial string modifiers in <number>
AT^SPBW=5,"12345678",,"Arthur"
^SPBW: 5
AT^SPBW=6,"432!+-765()&54*654#",,"John"
^SPBW: 6
AT^SPBW=7,"432!+-765()&54*654#",129,"Eve"
^SPBW: 7
AT^SPBW=8,"432!+-765()&54*654#",145,"Tom"
^SPBW: 8
AT^SPBW=9,"432!+-765()&54*654#",209,"Richard"
^SPBW: 9
EXAMPLE 4
Read phonebook entries from locations 5 - 9 via AT+CPBR
+CPBR:5,"12345678",129,"Arthur"
+CPBR:6,"432!+-765()&54*654#",209,"John"
+CPBR:7,"432+76554*654#",129,"Eve"
+CPBR:8,"+432+76554*654#",145,"Tom"
+CPBR:9,"432!+-765()&54*654#",209,"Richard"
17.7
AT^SDLD Delete the 'last number redial' memory
AT^SDLD deletes all numbers stored in the "LD" memory.
Syntax
Test Command
AT^SDLD=?
Response(s)
OK
Exec Command
AT^SDLD
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
+
+
+
+
+
+
+
-
+
-
Note
• Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data
may not yet be accessible, resulting in a short delay before the requested AT command response is returned.
See Section 23.1, Restricted access to SIM data after SIM PIN authentication for further detail.
17.8
AT^SPBC Find first matching entry in sorted phonebook
The AT^SPBC write command searches the current phonebook for the index number of the first (lowest) entry
that matches the character specified with <schar>. The AT^SPBC test command returns the list of phonebooks
which can be searched through with AT^SPBC.
CAUTION: Please note that AT^SPBC is assigned the same index as AT^SPBG or AT^SPBS which is not identical
with the physical location numbers used in the various phonebooks. Therefore, do not use the index numbers
retrieved with AT^SPBC to dial out or modify phonebook entries.
Syntax
Test Command
AT^SPBC=?
Response(s)
^SPBC: "FD","SM","ME"
OK
ERROR
+CME ERROR: <err>
Write Command
AT^SPBC=<schar>
Response(s)
^spbc: <index>
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
+
+
+
+
+
+
+
-
+
-
Parameter Description
<schar>(str)
First character of the entry to be searched in the sorted list of phonebook entries.
<index>(num)
In the active phonebook, the first (lowest) index number of an entry beginning with <schar>. As stated above,
the retrieved index number shall not be used to dial out or edit phonebook entries. If no matching phonebook
entry is found, <index>=0 will be returned.
Note
• Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data
may not yet be accessible, resulting in a short delay before the requested AT command response is returned.
See Section 23.1, Restricted access to SIM data after SIM PIN authentication for further detail.
17.9
AT^SPBD Purge phonebook memory storage
AT^SPBD can be used to purge the selected phonebook <storage> manually, i.e. all entries stored in the
selected phonebook storage will be deleted. CAUTION! The operation cannot be stopped nor reversed!
The AT^SPBD test command returns the list of phonebooks which can be deleted with AT^SPBD.
An automatic purge of the phonebooks is performed when the SIM card is removed and replaced with a different
SIM card. This affects the ME based part of the "LD" storage, and storages "MC" and "RC". Storage "ME" is not
affected.
Syntax
Test Command
AT^SPBD=?
Response(s)
^SPBD: list of supported <storage>s
OK
ERROR
+CME ERROR: <err>
Write Command
AT^SPBD=<storage>
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
+
+
+
+
+
+
+
-
+
-
Parameter Description
<storage>(str)
If test command: List of phonebooks which can be deleted by AT^SPBD.
If write command: Phonebook to be deleted.
For a detailed description of storages see AT+CPBS.
“LD“
Last number dialed phonebook
“MC“
Missed (unanswered received) calls list
“RC“
Received calls list
Note
• Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data
may not yet be accessible, resulting in a short delay before the requested AT command response is returned.
See Section 23.1, Restricted access to SIM data after SIM PIN authentication for further detail.
17.10
AT^SPBG Display phonebook entries in alphabetical order
AT^SPBG sorts the entries of the current phonebook in alphabetical order by name (the first six characters matt
er). The sort order is described in Section 17.1, Sort Order for Phonebooks.
There are two ways to use AT^SPBG:
• If the optional parameter <RealLocReq> equals 0 or is omitted the sorted entries will be sequentially num-
bered. As these numbers are not identical with the location numbers stored in the various phonebooks
AT^SPBG can be used for reading only. For example, it helps you find entries starting with matching charac-
ters. Do not use the serial numbers to dial out or modify entries.
• If parameter <RealLocReq>=1 is given by the write command, the response parameter <location> addi-
tionally appended to each entry indicates the actual location number. This number can be used for editing
with AT+CPBW or dialing with ATD><mem><n>. The first index number of each entry is only the serial number
of the sorted list.
Before using the AT^SPBG write command it is recommended to query the number of records currently stored in
the active phonebook (refer to test command parameter <used>). The test command also includes the param-
eters <nlength> and <tlength>. Note that if SIM storage is selected the length may not be available. If stor-
age does not offer format information, the format list should be empty parenthesises.
Syntax
Test Command
AT^SPBG=?
Response(s)
^SPBG: (1-<used>), <nlength>, <tlength>
OK
ERROR
+CME ERROR: <err>
Write Command
AT^SPBG=<index1>[, <index2>][, <RealLocReq>]
Response(s)
[^SPBG: <index1>, <number>, <type>, <text>[, <location>]]
[^SPBG: <index2>, <number>, <type>, <text>[, <location>]]
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
+
+
+
+
+
+
+
-
+
-
Parameter Description
<index1>(num)
First index number in the sorted list where to start reading. The supported range is given in the test command
response.
If <index 1> exceeds the upper bound <used>, "+CME ERROR: invalid index" will be returned.
<index2>(num)
Last index number in the sorted list where to stop reading. The supported range is given in the test command
response.
If <index2> is not given via write command, only the entry located at <index1> will be displayed.
If both <index1> and <index2> are in the range indicated by the test command parameter <used>, the list
of entries will be output and terminated with OK.
If
<index2> exceeds the range indicated by the test command parameter <used>, the list of entries will be
output but terminated with a "+CME ERROR: invalid index".
Note: The maximum value of <index2> is 255, regardless of the phonebook type and its range indicated by
the parameter <used>. If a value greater than 255 is used the query returns no phonebook records, and only
"+CME ERROR: invalid index" is shown.
<RealLocReq>(num)
Is a display of the "real" <location> of the entry required?
[0]
Do not show an entry's "real" location number. Parameter <location> will not
be displayed.
1
Show the "real" location number as parameter <location> at the end of each
entry.
<number>(str)
String type phone number in format specified by <type>.
The number parameter may be an empty string.
<type>(num)
Type of address octet, which defines the used type of number (ton) and the numbering plan identification (npi).
Please consider that for types other than 129 or 145 dialing from phonebook with ATD><mem><n> is, depending
on the network, not always possible (refer to GSM 04.08 subclause 10.5.4.7 for details). See also <type> of
AT+CPBW.
Possible values are:
145
Dialing string <number> includes international access code character '+'
161
National number. Network support of this type is optional.
209
Dialing string <number> has been saved as ASCII string and includes non-
digit characters other than "*", "#" or "+". Note that phonebook entries saved
with this type cannot be dialed.
255
Dialing string <number> is a command to control a Supplementary Service,
i.e. "*", "#" codes are contained. Network support of this type is optional.
129
Otherwise
<text>(str)(+CSCS)
Text assigned to the phone number. The maximum length for this parameter is given in test command response
<tlength>.
<used>(num)
Value indicating the number of used locations in selected memory storage.
<location>(num)
The location within phonebook memory at which the corresponding entry is located.
This location may be used for other commands (e.g. AT+CPBR or ATD><mem><n>)
<nlength>(num)
Maximum length of phone number for "normal" locations. Depending on the storage, a limited number of loca-
tions with extended memory is available per phonebook. Please refer to AT command AT+CPBW for detail.
<tlength>(num)
Maximum length of <text> assigned to the telephone number. The value indicated by the test command is
given in octets. If the <text> string is given in GSM characters, each character corresponds to one octet. If the
<text> string is given in UCS2, the maximum number of characters depends on the coding scheme used for
the alpha field of the SIM according to GSM 11.11, Annex B [25]. In the worst case the number of UCS2 char-
acters is at least one less than half the number of GSM characters.
Notes
• The command can be used for the phonebooks "SM", "FD", "ME" (cf. AT+CPBS).
• Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data
may not yet be accessible, resulting in a short delay before the requested AT command response is returned.
See Section 23.1, Restricted access to SIM data after SIM PIN authentication for further detail.
Examples
EXAMPLE 1
Using AT^SPBG without <RealLocReq>:
AT^SPBG=?
First run the AT^SPBG test command to find out the
range of entries stored in the current phonebook.
^SPBG: (1-33),20,17
TA returns the range, where 33 is the number of
entries stored in the current phonebook.
AT^SPBG=1,33
Now, enter the write command. To obtain best
^SPBG:1,"+999999",145,"Arthur"
results it is recommended to query the full range of
^SPBG:2,"+777777",145,"Bill"
entries. TA returns phonebook entries in alphabetical
order.
^SPBG:3,"+888888",145,"Charlie"
The numbers at the beginning of each line are not the memory locations in the phonebook, but only serial
numbers assigned to the entries' positions in the alphabetical list.
EXAMPLE 2
Using AT^SPBG with <RealLocReq>:
AT^SPBG=?
First run the AT^SPBG test command to find out the
range of entries stored in the current phonebook.
^SPBG: (1-33),20,17
TA returns the range, where 33 is the number of
entries stored in the current phonebook.
AT^SPBG=1,33,1
Now, enter the write command including parameter
^SPBG:1,"+999999",145,"Arthur",27
<RealLocReq>=1 to get the actual location num-
^SPBG:2,"+777777",145,"Bill",6
bers.
^SPBG:3,"+888888",145,"Charlie",15
The numbers at the end of each line are the memory locations in the phonebook and can be used for dialing
or editing phonebook entries:
AT+CPBR=27
Read out phonebook location 27.
+CPBR: 27,"+999999",145,"Arthur"
This entry can be edited with AT+CPBW or used for
dialing with ATD><mem><n>.
17.11
AT^SPBS Step through the selected phonebook alphabetically
AT^SPBS can be used to scroll sequentially through the active phonebook records in alphabetical order by na
me. Three entries will be displayed at a time.
Every time the write command is executed, 3 rows of phonebook records are returned. Each triplet overlaps with
the next one. The actual index depends on parameter <value>. This parameter determines whether the index
will be increased or decreased.
If the index in one output line reaches the last index in the alphabetical list, the next output line will display the
first list entry.
After the last record of the phonebook has been reached (see parameter <used> for AT^SPBG), the <inter-
nal-counter> switches over to the first.
There are two ways to use AT^SPBS:
• If the optional parameter <RealLocReq> is omitted or (0) the sorted entries will be sequentially numbered.
As these numbers are not identical with the location numbers stored in the various phonebooks AT^SPBS can
be used for reading only. For example, it helps you find entries starting with matching characters. Do not use
the serial numbers to dial out or modify entries.
• If parameter <RealLocReq>=1 is given by the write command, the response parameter <location> addi-
tionally appended to each entry indicates the actual location number. This number can be used for editing
with AT+CPBW or dialing with ATD><mem><n>. The first index number of each entry is only the serial number
of the sorted list.
See examples below.
Syntax
Test Command
AT^SPBS=?
Response(s)
^SPBS: (list of supported <value>)
OK
Write Command
AT^SPBS=<value>[, <RealLocReq>]
Response(s)
^SPBS: <index-a>, <number>, <type>, <text>[, <location>]
^SPBS: <index-b>, <number>, <type>, <text>[, <location>]
^SPBS: <index-c>, <number>, <type>, <text>[, <location>]
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
+
+
+
+
+
+
+
-
+
-
Parameter Description
<value>(num)
1
To make a step forward in the alphabetically sorted phonebook.
2
To make a step backward in the alphabetically sorted phonebook.
<index-a>(num)
1...maxindex
The index in the sorted list of phonebook entries that identifies the first entry
displayed.
The value of <index-a> is determined by the value of the <internal-
counter> and by parameter <value>.
After a write command has terminated successfully with "OK", the value from
parameter <index-a> is saved and retained as the new <internal-
counter> value.
Mind after the last record of phonebook, the first entry follows.
<index-b>(num)
1...maxindex
The index in the sorted list of phonebook entries that identifies the second entry
displayed.
<index-b>= (<index-a>+1).
Mind after the last record of phonebook, the first entry follows.
<index-c>(num)
1...maxindex
The index in the sorted list of phonebook entries that identifies the third entry
displayed.
<index-c>= (<index-b>+1).
Mind after the last record of phonebook, the first entry follows.
<number>(str)
String type phone number in format specified by <type>.
the number parameter may be an empty string.
<type>(num)
Type of address octet, which defines the used type of number (ton) and the numbering plan identification (npi).
Please consider that for types other than 129 or 145 dialing from phonebook with ATD><mem><n> is, depending
on the network, not always possible (refer to GSM 04.08 subclause 10.5.4.7 for details). See also <type> of
AT+CPBW.
Possible values are:
145
Dialing string <number> includes international access code character '+'
161
National number. Network support of this type is optional.
209
Dialing string <number> has been saved as ASCII string and includes non-
digit characters other than "*", "#" or "+". Note that phonebook entries saved
with this type cannot be dialed.
255
Dialing string <number> is a command to control a Supplementary Service,
i.e. "*", "#" codes are contained. Network support of this type is optional.
129
Otherwise
<text>(str)(+CSCS)
Text assigned to the phone number.
<RealLocReq>(num)
Is a display of the "real" <location> of the entry required?
[0]
Do not show an entry's "real" location number. Parameter <location> will not
be displayed
1
Show the "real" location number as parameter <location> at the end of the
entry
<location>(num)
The location within phonebook memory at which the corresponding entry is located.
This location may be used for other phonebook commands (e.g. AT+CPBR, AT+CPBW, ATD><mem><n>).
<internal-counter>(num)
0(&F)...maxindex
This parameter is only an internal parameter and cannot modified directly.
The internal counter will be reset to index 0 after a call to ATZ or AT&F.
Notes
• The complete list of sorted entries can be retrieved using AT command AT^SPBG.
• The command can be used for the phonebooks "SM", "FD", "ME" (cf. AT+CPBS).
• Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data
may not yet be accessible, resulting in a short delay before the requested AT command response is returned.
See Section 23.1, Restricted access to SIM data after SIM PIN authentication for further detail.
Examples
EXAMPLE 1
This example illustrates how to search down and up again using AT^SPBS=1 and 2:
at&f
First, AT&F is issued to make sure that AT^SPBS=1
OK
starts from the first character in alphabetical order.
at^spbs=1
^SPBS:1,"+999999",145,"Arthur"
^SPBS:2,"+777777",145,"Bill"
^SPBS:3,"+888888",145,"Charlie"
OK
at^spbs=1
^SPBS:2,"+777777",145,"Bill"
^SPBS:3,"+888888",145,"Charlie"
^SPBS:4,"0304444444",129,"Esther"
OK
at^spbs=1
^SPBS:3,"+888888",145,"Charlie"
^SPBS:4,"0304444444",129,"Esther"
^SPBS:5,"03033333333",129,"Harry"
OK
at^spbs=2
^SPBS:2,"+777777",145,"Bill"
^SPBS:3,"+888888",145,"Charlie"
^SPBS:4,"0304444444",129,"Esther"
OK
EXAMPLE 2
This example shows that when the last index in the sorted list has been reached, the internal counter over-
flows to the first index.
at&f
Reset internal counter to 0.
OK
at^spbs=2
Step down one entry starting from
(internal
^SPBS:33,"+49301234567",145,"TomTailor"
counter)=0 - overflow occurs.
^SPBS:1,"+999999",145,"Arthur"
^SPBS:2,"+777777",145,"Bill"
OK
EXAMPLE 3
Using AT^SPBS with <RealLocReq>=1 in order to obtain the entries' location numbers:
at^spbs=1,1
^SPBS:1,"+999999",145,"Arthur",27
^SPBS:2,"+777777",145,"Bill",6
^SPBS:3,"+888888",145,"Charlie",15
The numbers at the end of each line are the memory locations in the phonebook and can be used for dialing
or editing phonebook entries:
at+cpbr=27
Read out phonebook location 27.
+CPBR: 27,"+999999",145,"Arthur"
This entry can be edited with AT+CPBW or used for
dialing with ATD><mem><n>.
18.
Audio Commands
The AT Commands described in this chapter are related to the TC65i's audio interface.
18.1
Audio programming model
The following figure illustrates how the signal path can be adjusted with the parameters <inCalibrate>,
<inBbcGain>, <outBbcGain>, <outCalibrate> and <sideTone> as well as <io>, <mic> and <ep>.
Figure 18.1: Audio programming model for TC65i Module
18.2
ATL Set monitor speaker loudness
ATL is implemented for V.250ter compatibility reasons only, and has no effect. In multiplex mode (refer
AT+CMUX) the command is supported on logical channel 1 only.
Syntax
Exec Command
ATL[<val>]
Response(s)
OK
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
Reference(s)
-
+
-
-
+
-
-
-
+
-
V.250
Parameter Description
<val>(num)
18.3
ATM Set monitor speaker mode
ATM is implemented for V.250ter compatibility reasons only, and has no effect. In multiplex mode (refer
AT+CMUX) the command is supported on logical channel 1 only.
Syntax
Exec Command
ATM[<val>]
Response(s)
OK
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
Reference(s)
-
+
-
-
+
-
-
-
+
-
V.250
Parameter Description
<val>(num)
18.4
AT+CLVL Loudspeaker volume level
Syntax
Test Command
AT+CLVL=?
Response(s)
+CLVL: (list of supported<level>s)
OK
Read Command
AT+CLVL?
Response(s)
+CLVL: <level>
OK
ERROR
+CME ERROR: <err>
Write Command
AT+CLVL=<level>
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1
MUX2
MUX3
Charge
4
Last
Reference(s)
-
+
+
+
+
+
+
-
+
-
GSM 07.07
Parameter Description
<level>(num)
Loudspeaker Volume Level
0...4(D)
Notes
• The write command can only be used in audio mode 2 - 6.
• The values of the volume steps are specified with the parameters <outCalibrate>[0],...<outCali-
brate>[4] of the AT^SNFO command.
• As an alternative to AT+CLVL, you can use AT^SNFO and AT^SNFV. The parameter <level> is identical with
<outStep> used by both commands.
• Any change to <level> (or <outStep>) takes effect in audio modes 2 to 6. That is, when you change
<level> (or <outStep>) and then select another mode with AT^SNFS, the same step will be applied.
The only exception is audio mode 1 which is fixed to <level>=4 (or accordingly <outStep>=4).
<level> (or <outStep>) is stored non-volatile when the ME is powered down with AT^SMSO or reset with
AT+CFUN=1,1.
18.5
AT+CMUT Mute control
The AT+CMUT command mutes the microphone input. The command can be used in all audio modes (1 to 6) and
during a voice call only. See AT^SNFS for more details on the various audio modes. As alternative, you can use
the AT^SNFM command.
During an active call, users should be aware that when they switch back and forth between different audio modes
(for example handsfree on/off) the value of <mute> does not change, i.e. the microphone mode is retained until
explicitly changed.
Syntax
Test Command
AT+CMUT=?
Response(s)
+CMUT: (list of supported<mute>s)
OK
Read Command
AT+CMUT?
Response(s)
+CMUT: <mute>
OK
ERROR
+CME ERROR: <err>
Write Command
AT+CMUT=<mute>
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1
MUX2 MUX3
Charge
4
Last
Reference(s)
-
+
+
+
+
+
+
-
+
-
GSM 07.07
Parameter Description
<mute>(num)
0(P)
Mute off
1
Mute on
18.6
AT+VTD Tone duration
This command refers to an integer <duration> that defines the length of tones transmitted with the AT+VTS
command.
Syntax
Test Command
AT+VTD=?
Response(s)
+VTD: (list of supported<duration>s)
OK
Read Command
AT+VTD?
Response(s)
<duration>
OK
ERROR
+CME ERROR: <err>
Write Command
AT+VTD=<duration>
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3
Charge
4
Last
Reference(s)
-
+
+
+
+
+
+
-
-
-
GSM 07.07
Parameter Description
<duration>(num)
Duration of the DTMF signal in 1/10 seconds with tolerance.
The minimum duration of DTMF signals is 300ms.
1(&F)(P)...255
18.7
AT+VTS DTMF and tone generation
AT+VTS is intended to send ASCII characters or strings which cause the Mobile Switching Center (MSC) to trans-
mit DTMF tones to a remote subscriber. The command can only be used during active voice calls and offers the
following variants:
AT+VTS=<dtmfString> allows to send a sequence of DTMF tones with a duration defined with AT+VTD.
AT+VTS=<dtmf>[,<duration>] allows to send a single DTMF tone. In this case, the duration can be ind-
vidually determined during the call.
Syntax
Test Command
AT+VTS=?
Response(s)
+VTS: (list of supported<dtmf>s), (list of supported<duration>s)
OK
Write Command
AT+VTS=<dtmfString>
Response(s)
OK
ERROR
+CME ERROR: <err>
Write Command
AT+VTS=<dtmf>[, <duration>]
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
Reference(s)
-
+
+
+
+
+
+
-
-
-
GSM 07.07
Parameter Description
<dtmfString>(str)
String of ASCII characters in the set 0-9,#,*,A, B, C, D. Maximal length of the string is 29. The string must be
enclosed in quotation marks ("...").
<dtmf>(str)
ASCII character in the set 0...9,#,*, A, B, C, D.
<duration>(num)
Tone duration in 1/10 seconds with tolerance. If not specified current setting of AT+VTD is used.
The minimum duration of DTMF signals is 300ms.
1...255
18.8
AT^SAIC Audio Interface Configuration
AT^SAIC configures the interface connections of the active audio mode. The write command is usable in audio
modes 2 to 6 only.
If AT^SNFS=1, any attempt to use AT^SAIC write command is rejected with error response. This is because all
default parameters in audio mode 1 are determined for type approval and are not adjustable.
To allocate a specific audio mode to one of the audio interfaces, first select the audio mode with AT^SNFS and
then choose the interface using AT^SAIC.
Syntax
Test Command
AT^SAIC=?
Response(s)
^SAIC:(list of supported <io>s), (list of supported<mic>s), (list of supported<ep>s), (list of
supported<clock>s), (list of supported<mode>s), (list of supported<frame_mode>s)
OK
Read Command
AT^SAIC?
Response(s)
^SAIC: <io>, <mic>, <ep>, <clock>, <mode>, <frame_mode>
OK
ERROR
+CME ERROR: <err>
Write Command
AT^SAIC=<io>[, <mic>[, <ep>][, <clock>, <mode>, <frame_mode>]]
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Parameter Description
<io>(num)(^SNFW)
Input and output selection
1
Digital input and output
2
Analog input and output
<mic>(num)(^SNFW)
Microphone selection
1
Microphone 1
2
Microphone 2
<ep>(num)(^SNFW)
Select differential earpiece amplifier
1
Selects the earpiece amplifier 1
2
Selects the earpiece amplifier 2
3
Selects both amplifiers. Note that both amplifiers are connected in parallel and
therefore, get the same output power if <ep>=3.
<clock>(num)(^SNFW)
Parameter is mandatory if <io>=1 (digital).
0
256kHz clock
1
512kHz clock
<mode>(num)(^SNFW)
Parameter is mandatory if <io>=1 (digital).
0
Master mode
1
Slave mode
<frame_mode>(num)(^SNFW)
Parameter is mandatory if <io>=1 (digital).
0
Short frame
1
Long frame
Notes
• The factory defaults of AT^SAIC vary with the selected audio mode.
If AT^SNFS=1 or 4 or 5, then AT^SAIC=2,1,1,0,0,0.
If AT^SNFS=2 or 3 or 6, then AT^SAIC=2,2,2,0,0,0.
AT^SNFD can be used to reset the factory defaults.
• For use after restart of the ME, you are advised to store the settings of AT^SAIC and AT^SNFS to the audio
profile saved with AT^SNFW. Otherwise, audio mode
1
(AT^SNFS=1) and audio interface
2
(AT^SAIC=2,1,1,0,0,0) will be active each time the ME is powered up.
• The parameters <clock>, <mode> and <frame_mode> are mandatory, if parameter <io> is set to 1 (digi-
tal). These parameters can be used to configure the PCM functionality over the digital audio interface (DAI).
The PCM interface supports master or slave mode, short frame or long frame synchronization and 256 kHz
or 512 kHz bit clock frequency. In slave mode the clock frequency setting has no influence, because of the
BCLKIN signal being directly used for data shifting. The setting may therefore be either 0 or 1. The table below
lists possible configuration combinations.
Configuration
<clock>
<mode>
<framemode>
Master, 256kHz, short frame
0
0
0
Master, 256kHz, long frame
0
0
1
Master, 512kHz, short frame
1
0
0
Master, 512kHz, long frame
1
0
1
Slave, 256kHz, short frame
0 or 1
1
0
Slave, 256kHz, long frame
0 or 1
1
1
Slave, 512kHz, short frame
0 or 1
1
0
Slave, 512kHz, long frame
0 or 1
1
1
18.9
AT^SNFA Set or query of microphone attenuation
AT^SNFA specifies the large-
scale attenuation on the microphone path of the audio device currently selected with AT^SNFS. The write com-
mand is only available in audio modes 2 to 6.
Syntax
Test Command
AT^SNFA=?
Response(s)
^SNFA: (list of supported <atten>s)
OK
Read Command
AT^SNFA?
Response(s)
^SNFA: <atten>
OK
ERROR
+CME ERROR: <err>
Write Command
AT^SNFA=<atten>
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3
Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Parameter Description
<atten>(num)(^SNFW)
Multiplication factor for input samples. Parameter <atten> is identical with <inCalibrate> of AT^SNFI.
Formula used to calculate microphone attenuation (negative gain):
Gain in dB = 20 * log(<atten>/32768)
0...32767(P)...65535
0
Microphone is muted.
Please note that AT^SNFA cannot be used to mute the microphone. Therefore,
any attempt to enter 0 will be rejected with error response. Value 0 is returned
only by the read command AT^SNFA? after the microphone was muted with
AT^SNFM=0 during an active call.
32767
No attenuation on the microphone path
Values greater than 32767 will be suppressed to 32767.
Notes
• This command is provided for compatibility with former products (e.g. M20) and is a subset of AT^SNFI. The
parameter <inCalibrate> of AT^SNFI is identical with <atten> of AT^SNFA.
• To make the changes persistent use AT^SNFW.
Example
^SYSSTART
at^snfa=?
^SNFA: (0-65535)
OK
at^snfa?
^SNFA: 32767
OK
at^snfs=4
OK
at^snfa=1
OK
at^snfa?
^SNFA: 1
OK
at^snfi?
^SNFI: 5,1
OK
at^snfi=5,45
OK
at^snfa?
^SNFA: 45
OK
18.10
AT^SNFD Set audio parameters to manufacturer default values
AT^SNFD sets the active audio parameters to manufacturer defined default values. These default values can be
changed and stored by the user and also by download with a new set of parameters.
The restored values are:
AT^SNFA: <atten>
AT^SNFI: <inBbcGain>, <inCalibrate>
AT^SNFO: <outBbcGain>, <outCalibrate>[0 to 4], <sideTone>
AT^SAIC: <io>, <mic>, <ep>
AT^SNFS: <audMode>
Syntax
Test Command
AT^SNFD=?
Response(s)
OK
Exec Command
AT^SNFD
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Note
• Remember that the factory set audio mode 1 is fixed to <outStep>=4. Consequently, AT^SNFD restores
<audMode> together with <outStep>=4, but does not affect the values of <outStep> currently selected in
audio modes 2 - 6. This means, if <audMode>=1, the read commands AT^SNFO, AT^SNFV and AT+CLVL will
always deliver <outStep>=4. In all other modes the <outStep> value is retained until explicitly changed.
18.11
AT^SNFG Generate Tone
The AT^SNFG write command generates a 'local tone' via the selected audio output device.
Beside the duration up to 3 combinations of frequency and amplitude can be used to compose a local tone.
Syntax
Test Command
AT^SNFG=?
Response(s)
^SNFG:(list of supported <duration>s), (list of supported <frequency>s), (list of supported
<amplitude>s)[, ...]
OK
Write Command
AT^SNFG=<duration>, <frequency>, <amplitude>[, <frequency>, <amplitude>[, <frequency>,
<amplitude>]]
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Parameter Description
<duration>(num)
in Milliseconds.
0...65535
0
Mutes the currently played tone immediately.
65535
Activates a tone with infinit duration.
<frequency>(num)
in Hertz
200...3400
to be input in 1 Hz steps. Audible bandwidth is limited due to the voice band filters.
<amplitude>(num)
of the tone generator belonging to a frequency.
0...100
The output level at the speaker is dependent of the <outBbcGain> value (see AT^SNFO).
If more than one tone should be played, each amplitude level will be divided by the number of running tones to
avoid overdriving of the internal amplifier. For example, if three tones with amplitude of 30 units should be gen-
erated each amplitude is reduced to 10. Setting of amplitude to 100 corresponds with using of current <outB-
bcGain> value (see AT^SNFO), 0 is mute.
Notes
• Response of the command is always "OK" as long as the input parameters are valid.
• If more than one pair of <frequency> and <amplitude> is used then the amplitude for each frequency is
devided by the number of pairs.
• Tone priorities
Ring tones (incoming call/short message), Supervisory tones,Call Progress tones, Battery tones, RTC tones
and DTMF tones always have higher priority than a local tone. This means a local tone will be played only if
no module tone with a higher priority is being played. A local tone will be stopped and ended when a tone or
melody from the module starts to play.
• To suspend a local tone from playing use "AT^SNFG=0".
• Switching the tone generator on and off will trigger AT+CIND indicator "sounder" depending on current
AT+CMER settings.
• If there is a voice call active then the local tone is mixed into the voice signal. In case of a multi party call the
local tones are not available.
18.12
AT^SNFI Set microphone path parameters
AT^SNFI controls the microphone path amplification. Read and write options of this command refer to the acti
ve audio mode. The write command works only in audio modes 2 to 6.
Syntax
Test Command
AT^SNFI=?
Response(s)
^SNFI: (list of supported <inBbcGain>s) , (list of supported <inCalibrate>s)
OK
Read Command
AT^SNFI?
Response(s)
^SNFI: <inBbcGain>, <inCalibrate>
OK
ERROR
+CME ERROR: <err>
Write Command
AT^SNFI=<inBbcGain>, <inCalibrate>
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Parameter Description
<inBbcGain>(num)(^SNFW)
ADC gain adjustable in eight 6 dB steps from 0 dB to 42 dB (0=0dB, 7=42dB, 8 steps of 6 dB).
0...7
<inCalibrate>(num)(^SNFW)
Multiplication factor for input samples. Formula to calculate the negative gain (attenuation) of the input signal:
Gain in dB = 20 * log (inCalibrate / 32768)
0...32767
Notes
• The range of <inCalibrate> is up to 65535 but will be suppressed to 32767. Values above <inCali-
brate>= 65535 will cause a failure.
• The parameter <inCalibrate> of AT^SNFI is identical with <atten> of AT^SNFA.
• For use after restart, changed values can be stored with AT^SNFW.
• Attention! When you adjust audio parameters avoid exceeding the maximum allowed level. Bear in mind that
exposure to excessive levels of noise can cause physical damage to users!
18.13
AT^SNFM Set microphone audio path and power supply
The AT^SNFM read command returns the microphone mute and supply voltage status.
The AT^SNFM write command can be used to switch the microphone's audio path (muted / not muted) or to con-
trol the power supply of the VMIC line for the two microphone inputs of the TC65i Module.
The microphone can be muted or activated by changing <MicSwitch> in all audio modes (1 to 6) and during a
voice call only. As an alternative, you can use the AT+CMUT command to mute the microphone.
Syntax
Test Command
AT^SNFM=?
Response(s)
^SNFM: (list of supported <MicSwitch>s) , (list of supported <MicVccCtl>s)
OK
Read Command
AT^SNFM?
Response(s)
^SNFM: <MicSwitch>, <MicVccState>
OK
ERROR
+CME ERROR: <err>
Write Command
AT^SNFM=[<MicSwitch>][, <MicVccCtl>]
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Parameter Description
<MicSwitch>(num)
Microphone mute control parameter.
Evaluated only during voice calls and if <MicVccCtl> is omitted, e.g. AT^SNFM=1.
Command does not depend on audio mode.
0
Mutes the microphone.
1(P)
Activates the microphone.
<MicVccCtl>(num)
Microphone supply voltage control parameter. Controls the power supply VMIC of the two microphone inputs of
the TC65i Module.
CME error is given if <MicSwitch> is not omitted. Enter for example AT^SNFM=,1 or AT^SNFM=,2.
0
Supply voltage is always switched off.
1
Supply voltage is always switched on.
2(P)
Supply voltage state during voice calls is controlled by the ME. Actual value is
determined by parameter data set of the selected audio mode.
<MicVccState>(num)
Microphone supply voltage control status.
0
Supply voltage was set to a constant value.
2
Supply voltage state is controlled by the ME and depends on parameter data
set of the selected audio mode.
Notes
• The programmable power supply of the VMIC line gives you greater flexibility in connecting audio accessories
or using the two analog audio interfaces for a variety of functions other than audio. A detailed description of
the extended usage of the analog audio interfaces can be found in [10].
• During an active call, users should be aware that when they switch back and forth between different audio
modes (for example handsfree on/off) the value of <MicSwitch> does not change, i.e. the microphone mode
is retained until explicitly changed.
18.14
AT^SNFO Set audio output (= loudspeaker path) parameter
AT^SNFO controls the earpiece path amplification. The read and write commands refer to the active audio mod
e. The write command works only in audio modes 2 to 6.
Syntax
Test Command
AT^SNFO=?
Response(s)
^SNFO: (list of supported <outBbcGain>s), (list of supported <outCalibrate>s), (list of supported
<outStep>s), (list of supported <sideTone>s)
OK
Read Command
AT^SNFO?
Response(s)
^SNFO: <outBbcGain>, <outCalibrate>[0] , <outCalibrate>[1] , <outCalibrate>[2] ,
<outCalibrate>[3] , <outCalibrate>[4] , <outStep>, <sideTone>
OK
ERROR
+CME ERROR: <err>
Write Command
AT^SNFO=<outBbcGain>, <outCalibrate>[0] , <outCalibrate>[1] , <outCalibrate>[2] ,
<outCalibrate>[3] , <outCalibrate>[4] , <outStep>, <sideTone>
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Parameter Description
<outBbcGain>(num)(^SNFW)
Negative DAC gain (attenuation) adjustable in four 6 dB steps from 0 dB to -18 dB (0=0 dB, 3=-18 dB)
0...3
<outCalibrate>(num)(^SNFW)
Formula to calculate the value of the 5 volume steps selectable with parameter <outStep>:
Attenuation = 20 * log (2 * outCalibrate[n] / 32768)
0...32767
<outStep>(num)
Volume steps 0 - 4, each defined with outCalibrate[n]
0...[4]
<sideTone>(num)(^SNFW)
Multiplication factor for the sidetone gain.
Formula to calculate how much of the original microphone signal is added to the earpiece signal:
Sidetone gain in dB = 20 * log (sideTone / 32768).
0...32767
Notes
<outCalibrate> specifies the amount of volume of each <outStep>. The range of each <outCali-
brate> is up to 65535, but will be suppressed to 32767. A value above <outCalibrate>= 65535 will cause
an error.
• The range of <sideTone> is up to 65535, but will be suppressed to 32767. A value above <sideTone>=
65535 will cause an error.
• Any change to <outStep> takes effect in audio modes 2 to 6. That is, when you change <outStep> and
then select another mode with AT^SNFS, the same step will be applied. Nevertheless, the sound quality and
the amount of volume are not necessarily the same, since all remaining audio parameters can use different
values in either mode.
• Audio mode 1 is fixed to <outStep>=4. In this mode, any attempt to change <outStep> or other parameters
returns an error.
• The value of <outStep> is stored non-volatile when the ME is powered down with AT^SMSO or reset with
AT+CFUN=x,1. Any other parameters changed with AT^SNFO need to be saved with AT^SNFW for use after
restart. See also AT^SNFD for details on restoring factory defaults.
• The values of <outStep> can also be changed with AT^SNFV and AT+CLVL.
• CAUTION! When you adjust audio parameters avoid exceeding the maximum allowed level. Bear in mind that
exposure to excessive levels of noise can cause physical damage to users!
18.15
AT^SNFPT Set progress tones
AT^SNFPT controls the Call Progress Tones generated at the beginning of a mobile originated call setup.
Please note that the setting is stored volatile, i.e. after restart or reset, the default value 1 will be restored.
Syntax
Test Command
AT^SNFPT=?
Response(s)
^SNFPT: (list of supported <pt>s)
OK
Read Command
AT^SNFPT?
Response(s)
^SNFPT: <pt>
OK
ERROR
+CME ERROR: <err>
Write Command
AT^SNFPT=<pt>
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1
MUX2 MUX3
Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Parameter Description
<pt>(num)
0
Disables Call Progress Tones
1(P)
Enables Call Progress Tones (audible tones shortly heard on the phone when
ME starts to set up a call.)
18.16
AT^SNFS Select audio hardware set
The AT^SNFS write command serves to set the audio mode required for the connected equipment.
AT^SNFS can also be used in conjunction with AT^SAIC. This is useful, for example, if the audio interfaces are
operated alternatively to benefit from different devices. Each audio mode can be assigned a specific interface.
To do so, first select the audio mode with AT^SNFS, then activate the audio interface with AT^SAIC and finally
enter AT^SNFW to store the settings to your audio profile. To switch back and forth it is sufficient to use AT^SNFS.
Syntax
Test Command
AT^SNFS=?
Response(s)
^SNFS: (list of supported <audMode>s)
OK
Read Command
AT^SNFS?
Response(s)
^SNFS: <audMode>
OK
ERROR
+CME ERROR: <err>
Write Command
AT^SNFS=<audMode>
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1
MUX2 MUX3
Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Parameter Description
<audMode>(num)(^SNFW)
[1]
Audio mode 1: Standard mode optimized for the reference handset, that can
be connected to the analog interface 1 (see "TC65i Hardware Interface
Description" for information on this handset.) To adjust the volume use the
knob of the reference handset. In audio mode 4, this handset can be used with
user defined parameters.
Note: The default parameters are determined for type approval and are not
adjustable with AT commands.
AT^SNFD restores <audMode> 1.
2
Audio mode 2: Customer specific mode for a basic handsfree (speakerphone)
device (Siemens Car Kit Portable).
Analog interface 2 is assumed as default.
3
Audio mode 3: Customer specific mode for a mono-headset.
Analog interface 2 is assumed as default.
4
Audio mode 4: Customer specific mode for a user handset.
Analog interface 1 is assumed as default.
5
Audio mode 5: Customer specific mode.
Analog interface 1 is assumed as default.
6
Audio mode 6: Customer specific mode.
Analog interface 2 is assumed as default.
Notes
• The write command can be used during a voice call to switch back and forth between different modes. This
allows the user, for example, to switch handsfree operation (speakerphone) on and off.
• Users should be aware that <outStep> is a global setting. This means, when another audio mode is selected
during a call, the value of <outStep> does not change. This is also true for mute operation which can be set
with AT^SNFM or AT+CMUT: If the microphone is muted and the user selects another audio mode during the
call, then the microphone remains muted until explicitly changed. Exception: In audio mode 1 <outStep>=4
is fix.
• For use after restart of the module, you are advised to store the selected mode to the audio profile saved with
AT^SNFW. Otherwise, audio mode 1 will be active each time the module is powered up.
• Users should be aware that when using this AT command quickly after "^SYSSTART" a "+CME ERROR:
operation temporary not allowed" is received. The audio data may not yet be accessible, resulting in a short
delay (less than 400ms) before the requested AT command response is returned.
Examples
EXAMPLE 1
Suppose a user wishes to use alternatively a handsfree device (speakerphone) and a handset. The handset
can be connected to the first analog interface and adjusted to audio mode 4. The handsfree device can be
attached to the second analog interface and adjusted to audio mode 2. The factory defaults of AT^SAIC need
not be changed.
Settings for the handset:
AT^SNFS=4
OK
AT^SAIC?
Factory default of AT^SAIC assigned to audio mode 4.
^SAIC: 2,1,1
OK
Settings for the handsfree device:
AT^SNFS=2
OK
AT^SAIC?
Factory default of AT^SAIC assigned to audio mode 2.
^SAIC: 2,2,2
OK
To store the configuration to the user defined audio profile:
AT^SNFW
Stores the audio mode and the interface.
OK
To switch back and forth:
AT^SNFS=4
Switches to the handset connected to analog interface 1.
OK
AT^SNFS=2
Switches to the handsfree device at analog interface 2.
OK
EXAMPLE 2
The following example illustrates a combination of a handset and a handsfree device connected to other inter-
faces than those assumed as factory default.
Settings for a handset connected to the second analog interface and adjusted to audio mode 4:
AT^SNFS=4
OK
AT^SAIC=2,2,2
OK
Settings for a handsfree device connected to the first analog interface and adjusted to audio mode 2:
AT^SNFS=2
OK
AT^SAIC=2,1,1
OK
To store the configuration to the user defined audio profile:
AT^SNFW
Stores the audio mode and the interface.
OK
To switch back and forth:
AT^SNFS=4
Switches to the handset connected to analog interface 1.
OK
AT^SNFS=2
Switches to the handsfree device at analog interface 2.
OK
18.17
AT^SNFTTY Signal TTY/CTM audio mode capability
TC65i offers basic support for equipment using the CTM standard (Cellular Text Telephone Modems). The ben-
efit of CTM is that text characters typed on a TTY device (Text Telephone Type-writer) can be transformed into
special audio burst signals for reliable transmission via the existing speech channels of a cellular phone system.
If CTM mode is activated, the ME will set the necessary bearer capability bit on outgoing (mobile originated) calls
and incoming calls with this bearer capability bit set are accepted. The TE needs to decode the special audio
burst signals.
If CTM mode is disabled, the ME will clear the bearer capability bit on mobile originated calls and incoming calls
with the bearer capability bit set are rejected because the TC65i expects that CTM coded speech data cannot
be decoded by the TE.
Designed to set the module's speech system into CTM mode, the AT^SNFTTY command allows a CTM device
to be connected to one of the three audio interfaces of TC65i. Traditional TTY devices that do not incorporate
CTM functionality can be connected through an external TTY-to-CTM adapter.
Related documents: Refer to the relevant standards, such as 3GPP TS 26.226 (ETSI TS 126 226) and 3GPP
TS 23.228 (ETSI TS 123 226). 3GPP documentation can be retrieved, for example, from http://www.3gpp.org/
specs/specs.htm. Application Note 22 "Using TTY/CTM equipment" supplies information needed to connect
TTY/CTM equipment to the TC65i.
Requirements for using TTY/CTM features:
• The TTY/CTM functionality requires audio mode 5 or 6 which is set by AT^SNFS. When the appropriate audio
settings are enabled you may select either AT^SNFTTY=1 or 2.
• Depending on which audio interface the CTM device is connected to, select the appropriate settings via
AT^SAIC.
Syntax
Test Command
AT^SNFTTY=?
Response(s)
^SNFTTY: (list of supported <audioState>s)
OK
Read Command
AT^SNFTTY?
Response(s)
^SNFTTY: <audioState>
OK
ERROR
+CME ERROR: <err>
Write Command
AT^SNFTTY=<audioState>
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
-
-
Parameter Description
<audioState>(num)
0(P)
Audio path is in normal speech mode.
1
Audio path is in TTY/CTM mode (external CTM modem).
2
Audio path is in TTY/CTM mode (internal CTM modem).
18.18
AT^SNFV Set loudspeaker volume
AT^SNFV can be used to set the volume of the loudspeaker to the value <outCalibrate> addressed by
<outStep>. The read and write commands refer to the active audio mode. The write command works only in
audio modes 2 to 6.
Syntax
Test Command
AT^SNFV=?
Response(s)
^SNFV: (list of supported <outStep>s)
OK
Read Command
AT^SNFV?
Response(s)
^SNFV: <outStep>
OK
ERROR
+CME ERROR: <err>
Write Command
AT^SNFV=<outStep>
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3
Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Parameter Description
<outStep>(num)
The actual volume of each step is defined by the parameter <outCalibrate>, which can be set with AT^SNFO.
0...4(P)
Notes
• Any change to <outStep> takes effect in audio modes 2 to 6. That is, when you change <outStep> and
then select another mode with AT^SNFS, the same step will be applied. Nevertheless, the actual volume can
be quite different, depending on the values of <outCalibrate> set in each mode. The only exception is
audio mode 1 which is fixed to <outStep>=4.
<outStep> is stored non-volatile when the ME is powered down with AT^SMSO or reset with AT+CFUN=1,1.
<outStep> is not stored by AT^SNFW.
<outStep> can also be changed by AT^SNFO (Section 18.14) and AT+CLVL (Section 18.4).
• Users should be aware that when using this AT command quickly after "^SYSSTART" a "+CME ERROR:
operation temporary not allowed" is received. The audio data may not yet be accessible, resulting in a short
delay (less than 400ms) before the requested AT command response is returned.
18.19
AT^SNFW Write audio setting in non-volatile store
AT^SNFW causes the TA to write the currently selected audio parameters to non-
volatile store. The saved audio profile includes the following parameters:
AT^SNFA: <atten>
AT^SNFI: <inBbcGain>, <inCalibrate>
AT^SNFO: <outBbcGain>, <outCalibrate>[0 to 4], <sideTone>
AT^SNFS: <audMode>
AT^SAIC: <io>, <mic>, <ep>.
Syntax
Test Command
AT^SNFW=?
Response(s)
OK
Exec Command
AT^SNFW
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
+
-
18.20
AT^SRTC Ring tone configuration
The AT^SRTC read command returns the current <type> and current <volume>. The read command can be
used while test playback is off or on. In the latter case, see execute command for details.
The AT^SRTC execute command is intended only for testing. It starts to play a melody from the audio output cur-
rently selected with AT^SNFS. To deactivate test playback use AT^SRTC again.
During test playback, you can enter the write command to select another melody and adjust the volume. Also,
you can enter the read command to check the type and volume of the current ring tone, and to view the status
of playback (on / off).
The AT^SRTC write command chooses the type and volume of ring tones. The selected <type> and <volume>
are stored non-volatile. The only exception is <type>=0 which is not stored because it is intended only to quickly
mute the tone currently played. So <type>=0 only stops immediately the audible ring tone, but does not termi-
nate the RING URC.
Syntax
Test Command
AT^SRTC=?
Response(s)
^SRTC:(list of supported) <type>s, (list of supported) <volume>s
OK
Read Command
AT^SRTC?
Response(s)
^SRTC: <type>, <volume>, <status>
OK
ERROR
+CME ERROR: <err>
Exec Command
AT^SRTC
Response(s)
OK
ERROR
+CME ERROR: <err>
Write Command
AT^SRTC=[<type>][, <volume>]
Response(s)
^SRTC: <type>, <volume>
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3
Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Parameter Description
<type>(num)
Type of ring tone. You have a choice of 7 different ring tones and melodies. All will be played from the audio
output selected with the AT^SNFS command. <type>=0 is only intended for muting.
0
Mutes the currently played tone immediately.
1
Sequence 1
2
Sequence 2
3(D)
Sequence 3
4
Sequence 4
5
Sequence 5
6
Sequence 6
7
Sequence 7
<volume>(num)
Volume of ring tone, varies from low to high
0(D)
Mute
1
Very low
2
Identical with 1
3
Low
4
Identical with 3
5
Middle
6
Identical with 5
7
High
<status>(num)
Status of test ringing. Indicates whether or not a melody is currently being played back for testing
0
Switched off
1
Switched on
Notes
• Before first using ring tones note that the following settings apply:
We have chosen to let you decide your own preferences when you start using ring tones. Therefore, factory
setting is AT^SRTC=3,0,0 (ring tones are muted). To activate ring tones for the very first time, first enter the
write command and simply change the volume. After applying a firmware update the volume and type
selected before the firmware update will be preserved.
• If the <type> is changed while a call is ringing (RING URC) or active, the ME returns OK, but the new melody
does not take effect until after the call has ended.
• Users should be aware that when using this AT command quickly after "^SYSSTART" a "+CME ERROR:
operation temporary not allowed" is received. The audio data may not yet be accessible, resulting in a short
delay (less than 400ms) before the requested AT command response is returned.
19.
Hardware related Commands
All AT commands described in this chapter are related to the hardware interface of the TC65i. Further information
regarding this interface is available in the "TC65i Hardware Interface Description" [2].
19.1
AT+CCLK Real Time Clock
Syntax
Test Command
AT+CCLK=?
Response(s)
OK
Read Command
AT+CCLK?
Response(s)
+CCLK: <time>
OK
Write Command
AT+CCLK=<time>
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
Reference(s)
-
+
+
+
+
+
+
+
+
-
GSM 07.07
Parameter Description
<time>(str)
Format is "yy/mm/dd,hh:mm:ss", where the characters indicate the two last digits of the year, followed by month,
day, hour, minutes, seconds; for example 6th of July 2005, 22:10:00 hours equals to "05/07/06,22:10:00"
Factory default is "02/01/01,00:00:00"
Notes
<time> is retained if the device enters the Power Down mode via AT^SMSO.
<time> will be reset to its factory default if power is totally disconnected. In this case, the clock starts with
<time>= "02/01/01,00:00:00" upon next power-up.
• Each time TC65i is restarted it takes 2s to re-initialize the RTC and to update the current time. Therefore, it
is recommended to wait 2s before using the commands AT+CCLK and AT+CALA (for example 2s after
^SYSSTART has been output).
19.2
AT+CALA Set alarm time
The AT+CALA write command can be used to set an alarm time in the ME or to clear a programmed alarm. When
the alarm time is reached and the alarm is executed the ME returns an Unsolicited Result Code (URC) and the
alarm time is reset to "00/01/01,00:00:00".
The alarm can adopt two functions, depending on whether or not you switch the GSM engine off after setting the
alarm:
• Reminder message: You can use the alarm function to generate reminder messages. For this purpose, set
the alarm as described below and do not switch off or power down the ME. When executed the message
comes as an Unsolicited Result Code which reads "+CALA".
• Airplane mode: The alarm function can be used to wake up the ME at a scheduled time. For this purpose, set
the alarm as described below. Then power down the ME by entering the AT^SMSO command. When the alarm
time is reached the ME enters the Airplane mode, notified to the user by the URC "^SYSSTART AIRPLANE
MODE" and, if available, by a user defined text message (specified with <text>). In Airplane mode, the RF
interface of the ME is shut down to prevent it from unintentionally logging into the GSM network. All AT com-
mands whose execution requires a radio connection are disabled. A list of AT commands supported during
Airplane mode can be found in Section 23.4, Availability of AT Commands Depending on Oper-
ating Mode of ME. To return from Airplane mode to Normal mode use the AT^SCFG command and set
the parameter <map> to "off". This immediately activates the RF interface and restores access to all AT com-
mands. The URC "^SYSSTART" notifies the user that the ME has returned to Normal mode. Please note that
setting an alarm with AT+CALA is one method to wake up into Airplane mode. The second approach is using
the AT^SCFG command, parameter <mapos>. For further detail on Airplane mode refer to Section 2.14,
AT^SCFG.
The AT+CALA test command returns the supported array index values <n>, the supported alarm types <type>
and the maximum length of the text <tlength> to be output.
The AT+CALA read command returns the current alarm settings in the ME.
Syntax
Test Command
AT+CALA=?
Response(s)
+CALA: (list of supported<n>s), (list of supported<type>s), (list of supported<tlength>s)
OK
ERROR
+CME ERROR: <err>
Read Command
AT+CALA?
Response(s)
+CALA: <time>[, <n>[, <type>[, <text>]]]
OK
ERROR
+CME ERROR: <err>
Write Command
AT+CALA=<time>[, <n>[, <type>[, <text>]]]
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
Reference(s)
-
+
+
+
+
+
+
+
+
-
GSM 07.07
Unsolicited Result Code
+CALA: [<text>]
Indicates reminder message.
After power-down and wake-up at the scheduled time, the following URC indicates that the ME has entered the
Airplane mode:
"^SYSSTART AIRPLANE MODE"
+CALA: [<text>]
Parameter Description
<time>(str)
Format is "yy/MM/dd,hh:mm:ss". For example, 6th of July 2005, 22:10:00 equals to "05/07/06,22:10:00" (see
also AT+CCLK).
To clear a given alarm before its scheduled time simply enter an empty string for parameter <time>. See exam-
ples below.
Note: <time> can be set to a date of maximum 365 days minus 1 second ahead of the currently set time, oth-
erwise the write command returns an error and resets the alarm time. If <time> equals the current date and
time or is set to an earlier date, the write command returns an error.
<n>(num)
Integer type value indicating the array index of the alarm.
The ME allows to set only one alarm at a time. Therefore, the list of supported alarm events indicated by the test
command AT+CALA=? is <n>=0. If a second alarm time is set, the previous alarm will be deleted. Therefore, the
read command AT+CALA? will always return <n>=0. This is also true if individual settings are made on ASC0
and ASC1 or the various Multiplexer channels, for details see notes below.
<type>(num)
Integer type value indicating the type of the alarm.
0
Alarm indication: text message via serial interface
<text>(str)
String type value indicating the text to be displayed when alarm time is reached; maximum length is <tlength>.
By factory default, <text> is undefined.
Note: <text> will be stored to the non-volatile flash memory when the device enters the Power Down mode via
AT^SMSO. Once saved, it will be available upon next power-up, until you overwrite it by typing another text. This
eliminates the need to enter the full string when setting a fresh alarm.
<text> should not contain characters which are coded differently in ASCII and GSM (e.g. umlauts), see also
"Supported character sets" and "GSM alphabet tables".
<tlength>(num)
Integer type value indicating the maximum length of <text>. The maximum length is 16.
Notes
• After the alarm was executed the parameter <time> of AT+CALA will be reset to "00/01/01,00:00:00", but
<text> will be preserved as described above.
• If TC65i is totally disconnected from power supply the most recently saved configuration of +CALA:
<time>[,<n>[,<type>[,<text>]]] will be presented when TC65i is powered up.
• Each time TC65i is restarted with ignition it takes 2s to re-initialize the RTC and to update the current time.
Therefore, it is recommended to wait 2s before using the commands AT+CCLK and AT+CALA (for example
2s after ^SYSSTART has been output).
• Alarm settings on ASC0 / ASC1 and different Multiplexer channels (see AT+CMUX):
- On each interface an individual <text> message can be stored, but only one time setting applies. This
means an alarm <time> set on one of the interfaces overwrites the time setting on all remaining inter-
faces. Therefore, the total number of alarm events returned by the read command AT+CALA? will always
be <n>=0, no matter whether different text messages are stored.
- When the scheduled alarm occurs, the ME sends the URC only on the interface where the most recent
alarm setting was made. The alarm time will be reset to "00/01/01,00:00:00" on all interfaces.
Examples
EXAMPLE 1
You may want to configure a reminder message for July 31, 2005, at 9.30h, including the message "Good
Morning".
AT+CALA="05/07/31,09:30:00",0,0,"Good Morning"
OK
Do not switch off the GSM engine.When the alarm occurs the ME returns the following URC:
+CALA: Good Morning
EXAMPLE 2
To set a fresh alarm using the same message as in Example 1, simply enter date and time. <n>, <type>,
<text>, <tlength> can be omitted:
AT+CALA="05/07/31,08:50:00"
OK
When the alarm is executed the URC comes with the same message:
+CALA: Good Morning
EXAMPLE 3
To enable the ME to wake up into Airplane mode, e.g. on July 20, 2005, at 8.30h, enter
AT+CALA="05/07/20,08:30:00"
OK
Next, power down the ME:
AT^SMSO
^SMSO: MS OFF
OK
^SHUTDOWN
When the alarm is executed the ME wakes up to Airplane mode and displays a URC. If available, this line is
followed by the individual <text> most recently saved. If no individual message was saved only the first line
appears.
"^SYSSTART AIRPLANE MODE"
+CALA: Good Morning
EXAMPLE 4
To delete an alarm before its scheduled time is reached enter an empty string for parameter <time>. This
will restore the default time and clear any individual message defined with <text>.
AT+CALA=""
OK
AT+CALA?
+CALA: "00/01/01,00:00:00",0,0,""
OK
19.3
AT^SBC Battery Charge Control
The functions of the AT^SBC differ depending on whether or not a battery is present.
• General functions:
The AT^SBC provides URCs used to alert the user of undervoltage and overvoltage conditions before the
module switches off. The automatic shutdown caused by undervoltage or overvoltage is equivalent to the
power-down initiated with the AT^SMSO command, i.e. ME logs off from the network and the software enters
a secure state avoiding loss of data. When the module is in IDLE mode it takes typically one minute to dereg-
ister from the network and to switch off. For further details regarding automatic shutdown and voltage ratings
please refer to the Hardware Interface Description [2].
The URCs do not need to activated by the TE. They will be output automatically when fault conditions occur.
• Functions available with battery connected:
The AT^SBC read command can be used to query the status of the battery and the charger.
The AT^SBC write command is important for entering the current consumption of the external application via
<current>. It should be noted that the charge control supported by TC65i works only if the requirements
described in the Hardware Interface Description [2] are met (battery type Lithium-Ion or Lithium Polymer,
presence of an NTC and protection circuit etc.) and if <current> is correctly specified. If the battery does
not incorporate an NTC, or the battery and the NTC are not compliant with the specified requirements the
battery cannot be detected by TC65i.
Syntax
Test Command
AT^SBC=?
Response(s)
^SBC:(list of supported <bcs>s), (list of supported <bcl>s), (list of supported <mpc>s)
OK
Read Command
AT^SBC?
Response(s)
^SBC: <bcs>, <bcl>, <mpc>
OK
ERROR
+CME ERROR: <err>
Write Command
AT^SBC=<current>
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
±
+
-
Unsolicited Result Codes
URC 1
^SBC: Undervoltage
The message will be reported, for example, when the user attempts to set up a call while the voltage is close
to the critical limit and further power loss is caused during the transmit burst. When the external charging cir-
cuit includes an NTC connected to the BATT_TEMP pin, the URC appears several times before the module
switches off.
In applications which are not battery operated, i.e. where no NTC is connected to the BATT_TEMP pin, TC65i
will present the undervoltage URC only once and will then switch off without sending any further messages.
URC 2
^SBC: Overvoltage warning
This URC is an alarm indicator displayed when the supply voltage approaches its maximum level. The URC
appears only once.
URC 3
^SBC: Overvoltage shutdown
This URC will be reported when the voltage exceeds the maximum level specified in the Hardware Interface
Description [2]. It appears only once before the module starts to perform an orderly shutdown.
In applications powered from Lithium batteries the incorporated protection circuit typically prevents over-
charging, thus eliminating the risk of overvoltage conditions. Yet, in case of charging errors, for example
caused by a bad battery or due to the absence of a battery protection circuit, the module's overvoltage shut-
down function will take effect to avoid overcharging.
Parameter Description
<bcs>(num)
Connection status of battery pack
0
No charging adapter is connected
1
Charging adapter is connected
2
Charging adapter is connected, charging in progress
3
Charging adapter is connected, charging has finished
4
Charging error, charging is interrupted
5
False charging temperature, charging is interrupted while temperature is
beyond allowed range
<bcl>(num)
Battery capacity
0, 20, 40, 60, 80, 100 percent of remaining capacity (6 steps).
"0" indicates that either the battery is exhausted or the capacity value is not available. "100" indicates a remain-
ing capacity between 81 and 100 percent, "80" indicates 61 ... 81 percent, and so on.
While charging is in progress (charging adapter connected) the battery capacity is not available. Consequently,
parameter <bcl>=0. To query the battery capacity disconnect the charger.
<mpc>(num)
Current consumption of the host application as specified with parameter <current>.
<current>(num)
0(P)...5000
Enter the current consumption of your host application in mA. This information
enables TC65i to correctly determine the end of charging and terminate charg-
ing automatically when the battery is fully charged. Note that if <current> is
inaccurate, and the application draws a current higher than the final charge
current, either charging will not be terminated or the battery fails to reach its
maximum voltage. Therefore, the termination condition is defined as: current
consumption dependent on operating mode of the ME plus current consump-
tion of the external application. If used, the current flowing over the VEXT pin
of the application interface must be added, too.
The specified value will also be displayed as parameter <mpc> of the AT^SBC
read command.
When the TC65i is powered down or reset, the value of <current> is restored
to its default. This affects the charging control. Therefore, the parameter should
be set every time when needed after rebooting the TC65i.
Notes
• If multiplex mode (AT+CMUX) is active, any virtual channel can be used for entering the read or write com-
mand. The undervoltage URC will be issued simultaneously on all three channels.
• Another URC type required for battery powered applications is the URC "^SYSSTART CHARGE ONLY MODE".
It is indicated automatically when the module enters this mode (except when autobauding is active). See
AT+CFUN for details.
19.3.1
Responses returned by read command
Responses returned by the AT^SBC read command vary with the operating mode of the TC65i:
• Normal mode: TC65i is switched on by Ignition pin and running in SLEEP, IDLE, TALK or DATA mode.
Charger is not connected. The AT^SBC read command indicates the battery capacity and the current con-
sumption of the application (if value of application was specified before as <current>).
• Normal mode + charging: Allows charging while TC65i is switched on by Ignition pin and running in SLEEP,
IDLE, TALK or DATA mode. The AT^SBC read command returns only charger status and current consump-
tion of the application. Percentage of battery capacity is not available.
• CHARGE ONLY mode: Allows charging while TC65i is detached from GSM network. When started, the mode
is indicated by the URC "^SYSSTART CHARGE ONLY MODE". The AT^SBC read command returns only the
charger status and current consumption of the application. Percentage of battery capacity is not available. In
CHARGE ONLY mode a limited number of AT commands is accessible (see Appendix). There are several
ways to activate the CHARGE ONLY mode:
- from POWER DOWN mode: Connect charger while the TC65i was powered down with AT^SMSO
- from Normal mode: Connect charger, then enter AT^SMSO.
19.4
AT^SBV Battery/Supply Voltage
The AT^SBV execute command allows to monitor the supply (or battery) voltage of the module. The voltage is
continuously measured at intervals depending on the operating mode of the RF interface. The duration of a mea-
surement period ranges from 0.5s in TALK / DATA mode up to 50s when TC65i is in IDLE mode or Limited Ser-
vice (deregistered). The displayed value is averaged over the last measuring period before the AT^SBV
command was executed.
The measurement is related to the reference points of BATT+ and GND. For details on the reference points
please refer to the Hardware Interface Description [2].
Syntax
Test Command
AT^SBV=?
Response(s)
OK
ERROR
+CME ERROR: <err>
Exec Command
AT^SBV
Response(s)
^SBV: <value>
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Parameter Description
<value>(num)
Supply (or battery) voltage in mV
19.5
AT^SCTM Set critical operating temperature presentation mode
or query temperature
Use this command to monitor the temperature range of the module and the battery. The write command
enables or disables the presentation of URCs to report critical temperature limits.
CAUTION: During a guard period of two minutes after power-up, the module will not switch off, even if the critical
temperature limit is exceeded. This allows the user to issue emergency calls before the module switches off.
During this guard period, the module operates in an automatic report mode: URCs can be always displayed
regardless of the selected mode <n>. Refer to Section 19.5.1, Deferred shutdown for detail.
Syntax
Test Command
AT^SCTM=?
Response(s)
^SCTM:(list of supported <n>s)[, (range of <temp>in Celsius)]
OK
Read Command
AT^SCTM?
Response(s)
^SCTM: <n>, <m>[, <temp>]
OK
ERROR
+CME ERROR: <err>
Write Command
AT^SCTM=<n>[, <p>]
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
+
+
-
Unsolicited Result Codes
URC 1
URCs will be automatically sent to the TA when the temperature reaches or exceeds the critical level, or when
it is back to normal.
^SCTM_A: <m>
for battery temperature
URC 2
^SCTM_B: <m>
for module (board) temperature
Command Description
The read command returns:
• the URC presentation mode
• information about the current temperature range of the module
• The board temperature in Celsius if parameter <p>=1.
Please note that the Read command does not indicate the temperature range of the battery. The battery temper-
ature can only be reported by an Unsolicited Result Code.
Select <n> to enable or disable the presentation of the URCs. Please note that the setting will not be stored upon
Power Down, i.e. after restart or reset, the default <n>=0 will be restored. To benefit from the URCs <n>=1 needs
to be selected every time you reboot the GSM engine.
Parameter Description
<n>(num)
0(&F)(P)
Presentation of URCs is disabled (except for <m> equal to -2 or +2).
1
Presentation of URCs is enabled.
<m>(num)
-2
Below lowest temperature limit (causes immediate switch-off)
-1
Below low temperature alert limit
0
Normal operating temperature
1
Above upper temperature alert limit
2
Above uppermost temperature limit (causes immediate switch-off)
<p>(num)
0(&F)(P)
Suppress output of <temp> in read command.
1
Output <temp> in test and read command.
<temp>(num)
Board temperature in Celsius. Is comprised between the lowest temperature warning level and the uppermost
temperature warning level.
Notes
• Please refer to the "Hardware Interface Description" for specifications on critical temperature ranges.
• To avoid damage the module will shut down once the critical temperature is exceeded.
The procedure is equivalent to the power-down initiated with AT^SMSO.
• URCs indicating the alert level "1" or "-1" are intended to enable the user to take appropriate precautions,
such as protect the module and the battery from exposure to extreme conditions, or save or back up data etc.
The presentation of "1" or "-1" URCs depends on the settings selected with the write command:
If <n>=0: Presentation is enabled during the two minute guard period after the module was switched on. After
expiry of the two minute guard period, the presentation will be disabled, i.e. no URCs with alert levels "1" or
''-1" will be generated.
If <n>= 1: Presentation of "1" or "-1" URCs is always enabled.
• Level "2" or "-2" URCs are followed by immediate shutdown, except in cases described in Section 19.5.1,
Deferred shutdown. The presentation of these URCs is always enabled, i.e. they will be output even though
the factory setting AT^SCTM=0 was never changed.
Examples
EXAMPLE 1
URCs issued when the operating temperature is out of range:
^SCTM_A: 1
Caution: Battery close to overtemperature limit.
^SCTM_A: 2
Alert: Battery above overtemperature limit. Engine switches off.
^SCTM_B: 1
Caution: Module close to overtemperature limit.
^SCTM_B: 2
Alert: Module is above overtemperature limit and switches off.
^SCTM_A: -1
Caution: Battery close to undertemperature limit.
^SCTM_A: -2
Alert: Battery below undertemperature limit. Engine switches off.
^SCTM_B: -1
Caution: Module close to undertemperature limit.
^SCTM_B: -2
Alert: Module is below undertemperature limit and switches off.
EXAMPLE 2
URCs issued when the temperature is back to normal (URC is output once):
^SCTM_A: 0
Battery temperature back to normal temperature.
^SCTM_B: 0
Module back to normal temperature.
19.5.1
Deferred shutdown
In the following cases, automatic shutdown will be deferred if a critical temperature limit is exceeded:
• while an emergency call is in progress
• during a two minute guard period after powerup. This guard period has been introduced in order to allow for
the user to make an emergency call. The start of any one of these calls extends the guard period until the end
of the call. Any other network activity may be terminated by shutdown upon expiry of the guard time.
While in a "deferred shutdown" situation, the engine continues to measure the temperature and to deliver alert
messages, but deactivates the shutdown functionality. Once the guard period is expired or the call is terminated,
full temperature control will be resumed. If the temperature is still out of range, ME switches off immediately (with-
out another alert message).
CAUTION! Automatic shutdown is a safety feature intended to prevent damage to the module. Extended usage
of the deferred shutdown facilities provided may result in damage to the module, and possibly other severe con-
sequences.
19.6
AT^SSYNC Configure SYNC Pin
The AT^SSYNC command serves to configure the SYNC pin of the application interface. Please note that the
SYNC pin may be assigned different functions: Depending on the design of the host application, the pin can
either be used to indicate the current consumption in a transmit burst or to drive a status LED connected to the
pin as specified in [2]. For detailed information on the SYNC pin and its LED functionality refer to [2]. Before
changing the mode of the SYNC pin, carefully read the technical specifications.
Syntax
Test Command
AT^SSYNC=?
Response(s)
^SSYNC:list of supported <mode>s
OK
Read Command
AT^SSYNC?
Response(s)
^SSYNC:<mode>
OK
Write Command
AT^SSYNC=<mode>
Response(s)
OK
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
-
-
Parameter Description
<mode>(num)
Operation mode of the SYNC pin. Setting is stored non-volatile.
0(D)
SYNC mode:
Enables the SYNC pin to indicate growing power consumption during a trans-
mit burst. You can make use of the signal generated by the SYNC pin, if power
consumption is your concern. To do so, ensure that your application is capable
of processing the signal. Your platform design must be such that the incoming
signal causes other components to draw less current. In short, this allows your
application to accommodate current drain and thus, supply sufficient current to
the GSM engine if required.
1
LED mode:
Enables the SYNC pin to drive a status LED installed in your application
according to the specifications provided in [2].
The coding of the LED is described in Section 19.6.1, ME status indicated by
status LED patterns.
2
LED mode:
Like <mode>=1, but, additionally, enables different LED signalization in SLEEP
mode depending on the status of PIN authentication and network registration.
Please see AT+CFUN for details on SLEEP mode.
19.6.1
ME status indicated by status LED patterns
The following table lists the possible patterns of status LED behavior, and describes the ME operating status indi-
cated by each pattern if AT^SSYNC parameter <mode>=1 and <mode>=2. To better monitor the operating states
while power saving is enabled, we recommend that priority be given to <mode>=2.
During the transition from one LED pattern to another the "on" and/or "off" periods of the LED may vary in length.
This is because an event that triggers the change may occur any time and, thus, truncate the current LED pattern
at any point.
The statements on LED behavior during SLEEP mode are not applicable if the USB cable is plugged. This is
because power saving with connected USB host does not take effect if set with AT+CFUN only. For details see
notes provided with AT+CFUN. Therefore, while the USB cable is plugged, the LED is always on and flashes as
if the module works at AT+CFUN=1, no matter whether AT^SSYNC=1 or AT^SSYNC=2 is enabled.
Table 19.1: Modes of the LED and indicated ME functions
LED behavior
ME operating status if AT^SSYNC=1
ME operating status if AT^SSYNC=2
Permanently off
ME is in one of the following modes:
ME is in one of the following modes:
- POWER DOWN mode
- POWER DOWN mode
- AIRPLANE mode
- AIRPLANE mode
- CHARGE ONLY mode
- CHARGE ONLY mode
- NON-CYCLIC SLEEP mode
- CYCLIC SLEEP mode with no tempo-
rary wake-up event in progress 1)
600 ms on / 600ms off
Limited Network Service: No SIM card
Same as for AT^SSYNC=1
inserted or no PIN entered, or network
search in progress, or ongoing user
authentication, or network login in
progress.
75 ms on / 3 s off
IDLE mode: The mobile is registered to
Same as for AT^SSYNC=1
the GSM network (monitoring control
channels and user interactions). No call
is in progress.
75 ms on / 75 ms off /
One or more GPRS PDP contexts acti-
Same as for AT^SSYNC=1
75 ms on / 3 s off
vated.
500 ms on / 50 ms off
Packet switched data transfer is in
Same as for AT^SSYNC=1
progress.
Permanently on
Depending on type of call:
Same as for AT^SSYNC=1
Voice call: Connected to remote party.
Data call: Connected to remote party or
exchange of parameters while setting
up or disconnecting a call.
<n> ms on / <n> ms off 2)
Not possible: With AT^SSYNC=1, LED
SLEEP mode is activated (AT+CFUN
signalization is disabled in SLEEP
parameter <fun> ≠ 1), but the ME is not
mode.
registered to the GSM network (e.g. SIM
not inserted or PIN not entered, and
therefore, either no network service or
only Limited Network Service is avail-
able.
LED behavior
ME operating status if AT^SSYNC=1
ME operating status if AT^SSYNC=2
25 ms on / 4 * <n> ms off 2)
Not possible: With AT^SSYNC=1, LED
SLEEP mode is activated (AT+CFUN
signalization is disabled in SLEEP
parameter <fun> ≠ 1) while the ME is
mode.
registered to the GSM network and in
IDLE mode.
25 ms on / <m> ms off /
Not possible: With AT^SSYNC=1, LED
SLEEP mode is activated (AT+CFUN
25 ms on / 3 * <m> ms off
signalization is disabled in SLEEP
parameter <fun> ≠ 1) while the ME is
2)
mode.
registered to the GSM network. Addi-
tionally, PDP context is activated.
1) When a temporary wake-up event (for example a call, a URC, a packet switched transfer) occurs in CYCLIC SLEEP mode
the LED flashes according to the patterns listed above. See Section 2.9.1, Wake up the ME from SLEEP mode for details
on the various SLEEP modes and wake-up events.
2) The duration of <n> and <m> depends on the network: In SLEEP mode, the module can only change its LED status during
intermittent wake-up periods when listening to paging information from the base station. Therefore the values of <n> and
<m> vary as follows:
<n> = value from 471 ms to 2118 ms
<m> = 3000 ms
19.7
AT^SSPI Serial Protocol Interface
The AT^SSPI command enables the module to be connected to external I²C or SPI devices.
The I²C/SPI datastream is mapped through an internal I²C/SPI driver to and from an ASCII hex protocol which
can be exchanged with an internal application (JAVA) or an external application via V24.
The AT^SSPI write command configures and activates the I²C/SPI interface and changes from command mode
into data mode. All values must be given in hexadecimal format (0 - 9, A - F) without "0x". For details on data
mode please refer to Section 19.7.3, Transmitting Data over AT Interface.
Caution:
If I²C or SPI data mode is active the DCD line of the connected serial port goes high.
If I²C or SPI are opened from a Java application be sure to close the I²C or SPI channels before Java terminates.
Syntax
Test Command
AT^SSPI=?
Response(s)
^SSPI:(list of supported <basicConfiguration>s), (list of supported <delayOne>s), (list of supported
<delayTwo>s), (list of supported <wordLength>s), (list of supported <extendedSpiConfiguration>s)
OK
Read Command
AT^SSPI?
Response(s)
^SSPI: <connectionState>, <basicConfiguration>, <delayOne>, <delayTwo>, <wordLength>,
<extendedSpiConfiguration>
OK
ERROR
+CME ERROR: <err>
Write Command
AT^SSPI=[<basicConfiguration>[, <delayOne>[, <delayTwo>[, <wordLength>[,
<extendedSpiConfiguration>]]]]]
Response(s)
CONNECT
(indicates that ME has entered data mode)
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
+
+
Parameter Description
<connectionState>(num)
Parameter returned by the AT^SSPI? read command.
Indicates whether or not the I²C or SPI channel is used. When the channel is open and the ME is in data mode,
the read command can only be used if one of the remaining interfaces is available. For example, when the chan-
nel was opened on ASC0, you can use ASC1 or the MUX channels to check the status.
[0](&F)
Not connected (channel closed). All following parameters are the factory set-
tings AT^SSPI=0,0010,0000,0000,0000,0000.
1
Connected (channel open, ME in data mode). All following parameters are the
values currently used, for example AT^SSPI=1,0010,FFFF,FFFF,0000,0000.
<basicConfiguration>(num)
Parameter <basicConfiguration> is a 16 bit word which contains four subparameters to control the follow-
ing functions:
Subparameter
Bit
Hexadecimal
Selected function
Interface type
D15 - D12
0
I²C bus (default)
1
SPI device
Port
D11 - D8
0
Internal port
Data transfer rate
D7 - D4
0
I²C at 100 kbps
1
I²C at 400 kbps (default)
0
SPI at 100 kbps
1
SPI at 250 kbps
2
SPI at 500 kbps
3
SPI at 1.083 Mbps
4
SPI at 3.25 Mbps
5
SPI at 6.5 Mbps
Protocol
D3 - D0
0
ASCII (hex coding)
<delayOne>(num)
I²C: This parameter specifies a delay after each written byte. See Section 19.7.1, Specifying Delay Time for I²C
for further details.
SPI: 0000 only.
[0](&F)...FFFF
Unsigned 16 bit value
<delayTwo>(num)
I²C: This parameter specifies the delay after a each read byte. See Section 19.7.1, Specifying Delay Time for
I²C for further details.
SPI: 0000 only.
[0](&F)...FFFF
Unsigned 16 bit value
<wordLength>(num)
For SPI only:
0000
Length of SPI word = 8 bits
<extendedSpiConfiguration>(num)
For SPI only: Parameter <extendedSpiConfiguration> is a 16 bit word which contains four subparameters
to control the following functions:
Subparameter
Bit
Hexadecimal
Selected function
SPI mode
D15 - D12
0
Four different SPI modes. Phase and
1
polarity of all SPI modes are illustrated in
2
Section 19.7.2, Selecting SPI Mode.
3
Chip Select (CS) mode
D11 - D8
0
One Chip Select per Transfer Frame.
Arrangement of bytes
D7 - D4
0
Big endian
Bit sequence
D3 - D0
0
MSB first
(arrangement of bits on the SPI)
19.7.1
Specifying Delay Time for I²C
The parameters <delayOne> and <delayTwo> are depending on the I²C device connected to the TC65i. If the
delay times set with <delayOne> and <delayTwo> are not adequate the connected I²C device might not be
able to answer.
The following figures are provided to assist you in specifying appropriate values for both parameters. All delays
are relative to the data transfer rate. To calculate the delay use the formula and the values given below.
Figure 19.1: Formula for calculating the delay
Table 19.2: Values for calculating the delay
Parameter
Values
Delay value
Value set with parameter <delayOne> or <delayTwo>
Master clock
13 MHz
Default data transfer rate
400 bps
User data transfer rate
Value selected with subparameter data transfer rate within <basicConfigura-
tion>, for example 100 kbps or 400 kbps
Delay_min for Write
7.4 µs at 100 kbps
2.0 µs at 400 kbps
Delay_min for Read
9.9 µs at 100 kbps
2.6 µs at 400 kbps
Figure 19.2: Delay time on I²C after Write
Figure 19.3: Delay time on I²C after Read
19.7.2
Selecting SPI Mode
The figure shows the four types of SPI mode selectable by setting the appropriate hexadecimal value within the
parameter <extendedSpiConfiguration>.
Figure 19.4: SPI modes selectable on SPI
19.7.3
Transmitting Data over AT Interface
This section provides information on the protocol used for data transmission to or from I²C/SPI devices and
explains the data mode. It is assumed that you are familiar with the I²C specification.
Throughout this section the following document conventions are used to mark the direction of send and receive:
Transfer Message: AT → I²C or SPI device driver
Response Message: AT ← I²C or SPI device driver
Channel Open / Close:
To change from command mode to data mode use the AT^SSPI write command. To close down the channel
and return to command mode send the ASCII code # (0x23).
ASCII Protocol for I²C or SPI communication over AT interface:
The protocol allows using a Terminal program for the communication between the module and the I²C slave
device/SPI device. To visualize transferred characters and response data it is recommended to run the Terminal
program in chat mode or to switch on local echo.
For transfer and response, special characters are defined, such as Start and Stop to mark a single message and
Close to disconnect the data channel. All valid special characters are listed below:
Table 19.3: Special characters for ASCII coding
Direction
Function in protocol
Special
Hex value
Description
AT - Driver
character
Start Transfer Message
<
0x3C
Special character sent to the I²C/SPI
driver to start sending.
Stop Transfer Message
>
0x3E
Special character sent to the I²C/SPI
driver to stop sending.
Channel Close
#
0x23
For signalling.
Channel Close can be sent any time inside
or outside a transmit or receive message.
Causes the transfer to be aborted and
takes the ME back to AT command mode.
Start Response Message
{
0x7B
Special character sent to the I²C/SPI
driver to mark the beginning of a Response
Message.
Stop Response Message
}
0x7D
Special character sent to the I²C/SPI
driver to mark the end of a Response Mes-
sage.
Protocol error
!
0x21
For signalling.
Reports to the AT interface that the Trans-
fer Frame does not comply with the proto-
col definition (syntax error).
Transmission OK
+
0x2B
Notifies the AT interface that data were
(in I²C protocol referred to
successfully transmitted or, on the I²C bus,
as ACK)
the I²C Slave Address was recognized.
On I²C bus only:
Transmission error
-
0x2D
Notifies the AT interface that data transmis-
(in I²C protocol referred to
sion failed or the I²C Slave Address was
as NAK)
not recognized. On the I²C bus, the faulty
data byte (16 bit byte counter) is identified
as well.
Message syntax:
Each Message consists of a Start and Stop character, a Message-ID, further protocol data and user data. The
notation of all elements is explained below:
Notation of Message-ID:
• All ASCII characters between 0x00...0x7F. It is recommended to use only the characters 0...9, A...Z, a...z.
• Length of the Message-ID: only one character
Notation of protocol data (except Message-ID) and user data:
• Hex (0...9, a...f, A...F)
• Without "0x" (0x01 →01)
• Each hex value consists of 2 characters (1 →01)
• Without delimiters such as comma, semicolon, space etc. (0xAE 0x01 0xA5 →AE01A5)
• In a Transfer Message, the number of all characters after the Message ID shall be even. If it is odd, a protocol
error will be reported. On the I²C bus, this applies to the I²C Slave Address and all subsequent written user
data. On the SPI this applies to the Read Offset Byte and the Read Length and, if available, all written user
data. (Keep in mind that the number of all characters transmitted between Start "<" and Stop ">" of the Trans-
fer Frame shall always be odd because the ID is one character only.)
• Length of I²C Slave Address and user data: ≤ 2048 bytes
The first element of each message is the Start character ("<" for Transfer, "{" for the Response). Accordingly, the
last character of a message is the Stop character (">" for Transfer, "}" for the Response).
The second element of each message is the Message ID (1 character). The Message ID serves the user to dis-
tinguish between different messages. It is only relevant on protocol level (between AT interface and I²C device
driver), i.e. it is not sent to the I²C slave device.
Each transfer to the device is followed by a Response Message sent from the driver to the AT interface. The
response includes the Message ID and either OK ("+") or error characters ("-" or "!"). A successful response to
a Read Message contains the OK character and the read data. If an error occurs on the I²C bus, the response
consists of an error character followed by a 16 bit code specifying the faulty byte.
After each Transfer Message, wait for the Response Message before sending the next Transfer Message.
All characters entered outside a valid message (i.e. not input between Start character "<" and Stop character ">")
are ignored.
19.7.3.1
Structure of Messages on the I²C Bus
Table 19.4: Structure of Transfer and Response Messages on the I²C bus
Frame
Format
Write Transfer Message
< ID SlaveAddress Data >
Maximum length: 2048 bytes for I²C Slave Address
and written data. LSB of I²C Slave Address = "0".
Read Transfer Message
< ID SlaveAddress ReadLength >
Read Length ≤ 2048 bytes. LSB I²C of Slave Address
= "1".
Response Message
Write OK
{ID + }
Read of x bytes OK
{ID + Data }
NAK for xth byte if Read or Write
{ID - xxxx }
Protocol error in xth byte
{ID ! xxxx }
On the I²C bus, read and write data are handled in two separate frames transmitted one after the other. This is
because the I²C bus has only two bus lines, I2CDAT (I2CDAT_SPIDO) for the serial data and I2CCLK
(I2CCLK_SPICLK) for the serial clock. Write data are packed into a Transfer Frame. Read data are packed into
a Response Frame. The Transfer Frame contains a Receive or Transmit Request (R/W Request) for the I²C mas-
ter.
In a Transfer Message (Read or Write), the third element is the 7-bit I²C Slave Address (2 characters) that iden-
tifies each single device connected to the bus. The 8th bit of this byte is the LSB that determines the direction of
the message. If the LSB is "0" the master will write information to the selected slave. If the LSB is "1" the master
will read information sent from the slave.
In a Read Transfer Message on the I²C bus, the size of the expected data must be specified explicitly. This is an
element of 4 characters stating the number of bytes to be read. It must be placed after the I²C Slave Address.
19.7.3.2
Structure of Messages on the SPI
Table 19.5: Structure of Transfer and Response Messages for SPI
Message
Format
Transfer Message
< ID ReadOffset ReadLength Data >
Read Offset = 8 bits
Read Length = 16 bits
Read Offset + Read Length ≤ 2048 bytes
Max. length of read data: 2048 bytes
Response Message
Write OK
{ID +}
Reading x bytes was OK
{ID + Data }
Protocol error in xth byte
{ID ! xxxx }
The SPI has two serial data lines, DO (I2CDAT_SPIDO) for sending data from the master to the slave, and DI
(SPIDI) for receiving data sent from the slave to the master. Both data lines are controlled by one serial clock
line CLK (I2CCLK_SPICLK). TC65i acts as master providing the clock. Write and read data are handled in the
same Transfer Messages and Response Messages. In a Transfer Message, the next two elements after the ID
are the Read Offset and the Read Length, both required to enable reading data from the slave. The Read Offset
specifies where to start reading, i.e. which byte is the first to start reading from. If the Read Offset is zero then
reading starts from the first byte. The Read Length specifies the number of expected bytes. If the Read Offset is
zero and the Read Length does not equal zero, the master reads the specified number of bytes, starting from the
first byte. If the Read Length is zero, the Read Offset is ignored, meaning that the master will not read data from
the slave. To transmit data from the master to the slave all data can be entered after the Read Length.
In a Response Message the ID is followed by a special character to indicate the result of reading. If successful,
"+" is given, followed by the read data. If reading fails only "!" is received.
19.7.4
Error Handling on the I²C Bus
Protocol error:
If a protocol error is detected the ASCII value "!" is sent to the AT interface. Also, a Stop Condition is sent to the
I²C device.
A protocol error occurs if
• any data / address characters do not equal 0...9, a...f and A...F
• the length of a read word is smaller or greater than 16 bits
• the number of ASCII data is odd (e.g. "af1" instead of "af01")
• the Read or Write request is greater than 2 KB (0x0800).
Acknowledge:
Once a transmission has completed successfully (Write or Read), the special character "+" (ACK) is included in
the Response sent to the AT interface.
During a Write Transfer, the I²C driver acknowledges each transferred byte, but the Response contains only one
ACK which is transmitted only if all bytes are successfully transferred. During a Read Transfer, an ACK is sent
when the I²C slave device notifies that it has recognized the I²C Slave Address.
Not Acknowledge:
During a Transmit Transfer, a NAK is given when the I²C Slave Device notifies a failure to receive either the I²C
Slave Address or a data byte. In this case, a Stop Condition is sent to the I²C device.
During a Receive Transfer, a NAK is transmitted only when the I²C does not receive any reponse for the I²C Slave
Address. The I²C device never acknowledges the validity of the received data (by sending an ACK the master
acknowledges each received byte to the slave).
19.7.5
Example: Using I²C Bus
As stated above, it is recommended to run the Terminal program in chat mode or to use the local echo. First,
activate the I²C interface:
AT^SSPI=0010,0000,0000,0000,0000
The first group of characters forms the <basicCon-
CONNECT
figuration>, where the first "0" sets I²C, the sec-
ond "0" is the internal port, the digit "1" sets 400 kbps
bit rate on the I²C bus, and the next "0" selects ASCII
coding. This is followed by a comma and the value
"0000" = no delay time after Write and Read.
Note: If omitted all above parameters are assumed
by
default.
Therefore,
instead
of
AT^SSPI=0010,0000,0000 it is sufficient to enter
only AT^SSPI=
The module is in data mode now. This allows you to send a Write Transfer Message:
<aAE000102030405060708090A0B0C0D0E0F>
Write Transfer Frame, where a = ID, AE = Slave
Address and write request.
{a+}
Write Response Message, where a = ID.
<bAF0010>
Read Transfer Message, where b = ID, AF = Slave
Address and read request,
0010
= number of
expected bytes.
{b+000102030405060708090A0B0C0D0E0F}
Read Response Message, where b = ID.
To quit data mode and return to command mode enter the Close character "#":
#
OK
The response OK confirms that the ME is back to
command mode and ready to accept any AT com-
mands.
If the ME is in command mode, the response to the read command contains the factory settings.
AT^SSPI?
AT^SSPI=0,0010,0000,0000
The read command returns the connection state "not
connected" (Channel closed) and the factory set-
tings for I²C.
OK
If the ME is in data mode, the response to the read command contains the current settings.
AT^SSPI?
AT^SSPI=1,0010,0012,00FF,0000,0000
The read command returns the connection state
"connected" (Channel open) and the current settings
for I²C.
OK
19.7.6
Example: Transfer and Response Messages on SPI
The following examples shall illustrate the message structure and write/read procedures explained in Section
19.7.3.2, Structure of Messages on the SPI. Blanks are inserted only to better visualize frame elements. In prac-
tice no blanks are allowed.
<0 00 0000 11 22 33>
Transfer Message: The master writes 3 bytes.
{0 +}
Response Message: Transmission successful.
<1 00 0010>
Transfer Message: The master requests to read 16
bytes from the slave. Read Offset is zero, therefore,
reading starts from the first byte.
{1 + 11 22 33 44 ... FF 00}
Response Message: Reading data successful.
<2 03 0008>
Transfer Message: The master requests to read 8
bytes from the slave. Read Offset is 3, therefore,
reading starts from the fourth byte.
{2 + 44 55 66 77 88 99 AA BB}
Response Message: Reading data successful.
<3 03 0004 11 22 33 44 55 66>
Transfer Message: The master writes 6 bytes and
requests to read 4 bytes from the slave. Read Offset
is 3, therefore, reading starts from the fourth byte.
{3 + AA BB CC DD}
Response Message: Reading and writing data suc-
cessful.
19.8
AT^SAADC Show ADC Adjustment Values
The AT^SAADC command is intended only for the TC65i Terminal. It returns TC65i Terminal specific values
needed to recalculate the raw values captured with AT^SRADC in order to obtain the actual voltage applied at the
ADCx_IN input of the Terminal. The recalculation is necessary to account for the effect of component tolerances,
mainly caused by the measurement amplifier inside the TC65i Terminal. The amplifier is used to scale down the
ADCx_IN input voltage of the TC65i Terminal (5V) to the ADCx_IN input voltage of the in-built TC65i Module
(2.4V).
To recalculate the exact voltages measured at the ADC1_IN input use the following equation:
Value = (<value> from AT^SRADC - <ofs1>) * <amp1> / 4096
where the divisor 4096 is constant. For ADC2_IN use the equivalent parameters <ofs2> and <amp2>.
The voltage offset and the amplification factor are specific to each TC65i Terminal. The values are stored in the
device and are not changeable. Therefore, it is necessary to read the values only once in the lifetime of the TC65i
Terminal. ADC1_IN and ADC2_IN may have different offset values and amplification factors.
Syntax
Read Command
AT^SAADC?
Response(s)
^SAADC: <ofs1>, <amp1>, <ofs2>, <amp2>
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Parameter Description
<ofs1>(num)
Offset in mV to be deducted from the measurement <value> captured with AT^SRADC at ADC1_IN.
-32768...+32767
<amp1>(num)
Amplification factor for ADC1_IN
0...65535
The amplification factor is given as 16 bit unsigned integer. An amplification
factor of 1 equals 4096, an amplification factor of 2 equals 8192 etc. The TC65i
Terminal has typically an amplification factor around 2. See example below.
<ofs2>(num)
Offset in mV to be deducted from the measurement <value> captured with AT^SRADC at ADC2_IN.
-32768...+32767
<amp2>(num)
Amplification factor for ADC2_IN
0...65535
See <amp1> for further detail.
Example
The example shows how to determine the voltage actually measured at ADC1_IN of the TC65i Terminal. First,
find out the voltage offset and the amplification factor required for the recalculation of all later measurements
done with AT^SRADC:
AT^SAADC?
Query voltage offsets and amplification factors.
^SRADC: 3,8533,2,8000
The ADC1_IN line of the TC65i Terminal has the fol-
OK
lowing values: voltage offset
<ofs1>= 3mV and
<amp1>= 8533 which equals an amplification factor
of 2.083251953125. The values of ADC2_IN are not
relevant for this example.
Measure the voltage applied at ADC1_IN:
AT^SRADC=0
Open the ADC1_IN channel and query the voltage
^SRADC: 0,1,433
applied.
The voltage measured at ADC1_IN is 433mV.
OK
Now recalculate the value captured with AT^SRADC:
Value = (433 - 3) * 8533 / 4096 = 895.8mV
The actual voltage measured at ADC1_IN is
895.8mV.
19.9
AT^SRADC Configure and Read ADC Measurement
The AT^SRADC controls the module's Analog-to-Digital Converter. The ADC can be used to measure the voltage
of external devices connected to the ADC inputs. The AT^SRADC configures the parameters required for ADC
measurement and returns the measurement result(s). The value(s) can be delivered once on request by using
the single measurement mode, or periodically by specifying the measurement interval.
Note that the TC65i Module uses an unbalanced input with two pins. This requires different pin names as listed
below. See also [2]
First ADC channel of TC65i Module: ADC1_IN.
Second ADC channel of TC65i Module: ADC2_IN.
Syntax
Test Command
AT^SRADC=?
Response(s)
^SRADC:(list of supported <ch>s), (list of supported <oc>s), (list of supported <it>s)
OK
Read Command
AT^SRADC?
Response(s)
Current settings of first and second ADC channel:
^SRADC: <ch>, <oc>, <it>
^SRADC: <ch>, <oc>, <it>
OK
Write Command
Single measurement. Implies automatic channel open and close (<oc>=1 and 0) and no interval (<it>=0).
AT^SRADC=<ch>
Response(s)
^SRADC: <ch>, <count>, <value>
OK
ERROR
+CME ERROR: <err>
Write Command
Periodic measurement. Requires <oc>=1 and <it>=100ms...30000ms
AT^SRADC=<ch>, <oc>, <it>
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Unsolicited Result Code
URC indicating the used channel, the number of measured samples and the voltage. Applies only if periodic
measurement mode is enabled.
^SRADC: <ch>, <count>, <value>[, <value>[, <value>[, <value>[, <value>[, <value>[,
<value>[, <value>[, <value>[, <value>[, <value>]]]]]]]]]]
Parameter Description
<ch>(num)
Select ADC channel
0
First ADC channel
(ADC1_IN at TC65i Module.)
1
Second ADC channel
(ADC2_IN at TC65i Module.)
<oc>(num)
Open or close ADC channel
[0]
Close ADC channel specified with <ch>
1
Open ADC channel specified with <ch>
<it>(num)
Measurement interval
[0]
Single measurement mode
100...30,000
Output interval in ms at steps of 60/13 ms to enable periodic measurement
mode.
<value>(num)
Measurement value
-25...+2425
Measured voltage in mV
Resolution: 1mV
Accuracy (typ.): 2mV
The captured value is the actual voltage applied at the ADCx_IN input. No fur-
ther calculation is required.
<count>(num)
1...11
Number of measured samples
In single measurement mode: <count> is always 1.
In periodic measurement mode: <count> is number of <value>s indicated by
each URC "^SRADC". The higher the sample rate set with <it>, the more mea-
sured values are reported within the URC "^SRADC".
Notes
• If power saving is enabled with AT+CFUN, take into account that the periodic mode lets the ME consume cur-
rent each time the measurement is performed. This reduces the effect of power saving and thus decreases
the operation time.
• If an AT command is input on the same interface where the periodic measurement mode is on, up to 5
"^SRADC" URCs are queued up and sent after AT command completion.
If more than 5 URCs occur before the AT command is completed their measurement values are lost. In this
case, one additional URC with a negative <count> and the single value "32767" is sent along with the first
5 buffered URCs. The negative <count> indicates the number of lost measurement values (not the number
of URCs). See example below.
Examples
EXAMPLE 1
Single measurement
AT^SRADC=0
Open the first ADC channel for single measurement.
^SRADC: 0,1,2375
OK
EXAMPLE 2
Periodic measurement at low sample rate (5s):
AT^SRADC=0,1,5000
Start periodic measurement mode on the first ADC
^SRADC: 0,1,2375
channel. Samples are taken every 5s. Every 5s the
^SRADC: 0,1,2375
URC "^SRADC" appears to report the measured volt-
ages. The second parameter represents the number
^SRADC: 0,1,2375.
of measured samples, in this case only one.
^SRADC: 0,1,2375AT^SRADC=0,0
Stop the periodic measurement.
OK
EXAMPLE 3
Periodic measurement at high sample rate (250ms):
AT^SRADC=0,1,250
Start periodic measurement on the first ADC chan-
^SRADC: 0,4,2375,2375,2375,2375
nel. Samples are taken every 250ms. Every second
^SRADC: 0,4,2375,2375,2375,2375
a URC "^SRADC" appears to report the measured
voltage. The number of samples is 4 or 5.
^SRADC: 0,5,2375,2375,2375,2375,2375
^SRADC: 0,4,2375,2375,2375,2375AT^SRADC=0,0
OK
Stop the periodic measurement.
EXAMPLE 4
Handling of "^SRADC" URCs and AT command execution on the same interface:
AT^SRADC=0,1,250
Start periodic measurement mode on the first ADC
^SRADC: 0,4,2375,2375,2375,2375
channel. Samples are taken every 250ms.
^SRADC: 0,5,2375,2375,2375,2375,2375
^SRADC: 0,4,2375,2375,2375,2375
^SRADC: 0,4,2375,2375,2375,2375AT^SRADC?
Input of AT command and <CR> takes 4s.
^SRADC: 0,1,250
^SRADC: 1,0,0
OK
^SRADC: 0,4,2375,2375,2375,2375
4 URCs were buffered during command input and
^SRADC: 0,4,2375,2375,2375,2375
sent after completion.
^SRADC: 0,4,2375,2375,2375,2375
^SRADC: 0,4,2375,2375,2375,2375
^SRADC: 0,4,2375,2375,2375,2375
More URCs are delivered.
^SRADC: 0,4,2375,2375,2375,2375
^SRADC: 0,4,2375,2375,2375,2375
^SRADC: 0,4,2375,2375,2375,2375
^SRADC: 0,4,2375,2375,2375,2375AT^SRADC?
Input of AT command and <CR> takes 7s.
^SRADC: 0,1,250
^SRADC: 1,0,0
OK
^SRADC: 0,4,2375,2375,2375,2375
5 URCs were buffered during command input and
^SRADC: 0,4,2375,2375,2375,2375
sent after completion, another 2 URCs are lost.
^SRADC: 0,4,2375,2375,2375,2375
^SRADC: 0,4,2375,2375,2375,2375
^SRADC: 0,4,2375,2375,2375,2375
^SRADC: 0,-8,32767
The URC indicates 8 lost measurement results.
^SRADC: 0,4,2375,2375,2375,2375
More URCs are delivered.
^SRADC: 0,4,2375,2375,2375,2375
19.10
AT^SWDAC Configure and Read PWM Signal for DAC
The AT^SWDAC controls the PWM (Pulse Width Modulation) signals generated by means of the DAC_OUT pin
of the TC65i Module.
Syntax
Test Command
AT^SWDAC=?
Response(s)
^SWDAC:(list of supported <dc>s), (list of supported <oc>s), (list of supported <fq>s)
OK
Read Command
AT^SWDAC?
Response(s)
^SWDAC: <dc>, <oc>, <fq>
OK
ERROR
+CME ERROR: <err>
Write Command
AT^SWDAC=<dc>[, <oc>[, <fq>]]
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2
MUX3
Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Parameter Description
<dc>(num)
Duty cycle in percentage steps
0...100
<oc>(num)
Open or close DAC
0
Close DAC
1
Open DAC
<fq>(num)
PWM frequency
0
320 Hz (accuracy of 1 percentage step)
1
970 Hz (accuracy of 3 percentage steps)
2
8,125 Hz (accuracy of 1 percentage step)
3
16,250 Hz (accuracy of 1 percentage step)
4
32,500 Hz (accuracy of 1 percentage step)
5
65,000 Hz (accuracy of 2 percentage steps)
Example
This example shows how to open the DAC_OUT output and change the duty cycle while using the same fre-
quency.
AT^SWDAC=50,1,2
Initial opening of DAC_OUT, while setting PWM sig-
nal to 8,125 Hz at 50% duty cycle.
OK
AT^SWDAC=75
Change duty cycle of the open DAC_OUT output.
OK
AT^SWDAC=80
Change duty cycle of the open DAC_OUT output.
OK
AT^SWDAC=0,0
Close DAC_OUT.
OK
20.
GPIO Commands
This chapter describes the AT commands needed to access and configure the GPIO pins of the TC65i.
Please also refer to [2] for electrical specifications of the GPIOs and their signal states after startup and during
application.
Except for the pulse counter commands, usage of all GPIO commands is restricted to the same interface where
the GPIO driver was openend with AT^SPIO. Any attempt to access GPIOs from another interface will be denied
with an error message.
When the TC65i starts up, all GPIO pins are set to high-impedance state after initializing. Therefore, it is recom-
mended to connect pull-up or pull-down resistors to all GPIO pins you want to use as output. This is necessary
to keep these pins from floating or driving any external devices before all settings are done by AT command (at
least AT^SPIO, AT^SCPIN), and after closing the GPIOs again.
20.1
AT^SPIO General Purpose IO Driver Open/Close
The AT^SPIO write command opens and closes the general purpose IO driver. The command must be executed
before any other GPIO command can be used. After closing the driver, all pins used (i.e. opened) will be put into
high impedance state (inputs) with no internal pull up or down.
The command does not reserve any general purpose IO pin, only the drivers required for GPIO pin management
will be loaded.
Syntax
Test Command
AT^SPIO=?
Response(s)
^SPIO:(list of supported <mode>s)
OK
Write Command
AT^SPIO=<mode>
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Parameter Description
<mode>(num)
0
Close General purpose IO driver
1
Open General purpose IO driver
20.2
AT^SCPIN Pin Configuration
The AT^SCPIN write command serves to add (or remove) and configure pins.
Syntax
Test Command
AT^SCPIN=?
Response(s)
^SCPIN:(list of supported <mode>s), (list of supported <pin_id>s), (list of supported <direction>s), (list
of supported <startValue>s)
OK
Write Command
AT^SCPIN=<mode>, <pin_id>, <direction>[, <startValue>]
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1
MUX2 MUX3
Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Parameter Description
<mode>(num)
0
Close pin
1
Open pin
<pin_id>(num)
Pin identifier
0
GPIO1
1
GPIO2
2
GPIO3
3
GPIO4
4
GPIO5
5
GPIO6
6
GPIO7
7
GPIO8
8
GPIO9
9
GPIO10
The GPIO10 pin can be used either as GPIO or as pulse counter. If configured
as GPIO, the pulse counter option cannot be enabled. Vice versa, if configured
as pulse counter the GPIO option is not available. See AT^SCCNT and
AT^SSCNT for further details on the pulse counter.
<direction>(num)
Parameter <direction> is mandatory when opening a pin, but can be omitted when closing a pin
0
Input
1
Output
<startValue>(num)
Can be set only for outputs.
[0]
Low
1
High
Notes
• For closing a pin with the write command (<mode>=0), the parameter <direction> is not needed.
• Before changing the configuration of a pin be sure to close the pin.
20.3
AT^SCPOL Polling Configuration
The AT^SCPOL write command serves to start and stop polling a pin or port specified with <io_id>. The pin or
port must already be configured via AT^SCPIN or AT^SCPORT. Polling is only applicable to input pins.
After polling has been activated on a specified pin or port, all new values related to this pin or port will be reported
via the "^SCPOL" URC.
Syntax
Test Command
AT^SCPOL=?
Response(s)
^SCPOL:(list of supported <mode>s), (list of supported <io_id>s)
OK
Write Command
AT^SCPOL=<mode>, <io_id>
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Unsolicited Result Code
^SCPOL: <io_id>, <value>
Parameter Description
<mode>(num)
0
Suppress polling
1
Activate polling
<io_id>(num)
This can be either a <pin_id> already configured or a <port_id> already opened.
<value>(num)
New value on this <io_id>.
0
Low for <pin_id>
1
High for <pin_id>
0...1023
For <port_id>
Notes
• The pins will be polled at every TDMA frame interrupt, i.e. every 4.616ms. In SLEEP mode, the frequency of
polling is reduced, as polling will be done only when the module shortly suspends power saving when CTS is
activated. So in SLEEP mode polling intervals are extended to a range from 0.9s to 2.7s.
After a state change has been detected the "^SCPOL" URC is issued if the state of the pin remains stable for
8 TDMA frames (= 36.93ms) with 10% tolerance in Normal mode, or accordingly, 0.9s to 2.7s in SLEEP mode.
The maximum frequency of changing of the pin state that can be detected is 11 Hz.
• If the <value> of one or more of the polled pins has changed since polling has been performed last time, or
since a particular pin or its entire port have last been queried with AT^SGIO, polling will be suspended to send
a URC. There will be one URC reported for each polled pin whose <value> has changed, and one for each
polled port with one or more changed pins.
20.4
AT^SCPORT Port Configuration
With AT^SCPORT a group of maximum 10 pins can be configured to act as a parallel port, which can be controlled
with a single AT command. A pin can only be added once to a port, and only to a port. The first, i.e. left most
parameter, corresponds to the port's LSB.
All pins of a port must be set to the same direction (input or output). See AT^SCPIN.
Syntax
Test Command
AT^SCPORT=?
Response(s)
OK
Write Command
AT^SCPORT=<pin_id>1[, <pin_id>2[, <pin_id>3[, <pin_id>4[, <pin_id>5[, <pin_id>6[, <pin_id>7[,
<pin_id>8[, <pin_id>9[, <pin_id>10]]]]]]]]]
Response(s)
^SCPORT: <port_id>
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Parameter Description
<port_id>(num)
Assigned port
<pin_id>(num)
Pin ID of the xth pin of this port
See AT^SCPIN for possible pin value.
20.5
AT^SDPORT Delete a Port Configuration
The AT^SDPORT write command removes a parallel port. The pins of the port remain open and can be added to
a new port.
Syntax
Test Command
AT^SDPORT=?
Response(s)
(list of supported <port_id>s)
OK
Write Command
AT^SDPORT=<port_id>
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Parameter Description
<port_id>(num)
ID of the port to be closed
20.6
AT^SGIO Get IO state of a specified pin or port
Syntax
Test Command
AT^SGIO=?
Response(s)
^SGIO:(list of supported <io_id>s)
OK
Write Command
AT^SGIO=<io_id>
Response(s)
^SGIO: <value>
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Parameter Description
<io_id>(num)
This can be either an already configured <pin_id> or an already opened <port_id>.
<value>(num)
State read on this <io_id>.
0
Low for <pin_id>
1
High for <pin_id>
0...1023
For <port_id>
Note
• If one gets the state of a port whose width is less than 10 bits, the bits of <value> that are more significant
than the MSB of the port are set to zero.
20.7
AT^SSIO Set IO state of a specified pin or port
Syntax
Test Command
AT^SSIO=?
Response(s)
^SSIO:(list of supported <io_id>s), (list of supported <value>s)
OK
Write Command
AT^SSIO=<io_id>, <value>
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Parameter Description
<io_id>(num)
This can be either an already configured <pin_id> or an already opened <port_id>.
<value>(num)
State to be set for this <io_id>.
0
Low for <pin_id>
1
High for <pin_id>
0...1023
For <port_id>
Notes
• If you set a state on a port whose width is less than 10 bits, the bits of <value> that are more significant than
the MSB of the port are ignored.
• The write command is only applicable to <pin_id>s or <port_id>s which are configured as output.
20.8
AT^SCCNT Configure Pulse Counter
The AT^SCCNT write command serves to configure the GPIO10 pin as pulse counter. The pulse counter is
designed to measure signals from 0 to 1000 pulses per second.
Remember that if the GPIO10 line is configured as GPIO (see AT^SCPIN) any attempt to activate the pulse
counter will be rejected. Vice versa, if the pulse counter is opened the GPIO10 line cannot be configured as
GPIO.
See also [2] for further detail on the pulse counter.
Syntax
Test Command
AT^SCCNT=?
Response(s)
^SCCNT:(list of supported <action>s), (list of supported <mode>s), (list of supported <limit>s)
OK
Read Command
AT^SCCNT?
Response(s)
^SCCNT: <action>, <mode>[, <limit>]
OK
ERROR
+CME ERROR: <err>
Write Command
AT^SCCNT=<action>, <mode>[, <limit>]
Response(s)
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Unsolicited Result Code
^SCCNT: <time>
The URC applies only to the Limit counter mode set with parameter <mode>=1. It is delivered once the pulse
counter has completed counting the number of pulses requested with parameter <limit>.
Parameter Description
<action>(num)
0
Close pulse counter
1
Open pulse counter
<mode>(num)
0
Activates the Start-Stop counter mode.
After setting this mode, use AT^SSCNT and the <action> parameter to start
or stop the pulse counter or to read out the measured pulses.
1
Activates the Limit counter mode and immediately starts the pulse counter.
Parameter <limit> is mandatory for this mode.
<limit>(num)
1...65534
Number of pulses to be counted.
Parameter <limit> applies only to the Limit counter mode and is mandatory
for this mode. Once the given number of pulses is reached, the ME sends one
single URC "^SCCNT" which indicates the parameter <time>.
<time>(num)
1...4294967295
Time (in milliseconds) taken to count the number of pulses specified with
<limit>.
Note
• Measurement accuracy: In Limit counter mode, the parameter <time> implies an inaccuracy <5ms.
20.8.1
Using the Pulse Counter in Limit Counter Mode
This example assumes that a 1 kHz frequency is applied at the GPIO10 pin. Limit counter mode is enabled to
request the time the pulse counter needs to count a specified number of pulses.
at^sccnt=1,1,1000
Open pulse counter, enable Limit counter mode, request the time
needed to count 1000 pulses.
OK
^SCCNT: 0000001047
"^SCCNT" URC indicates the time taken to count 1000 pulses.
at^sccnt=1,1,2000
Open pulse counter, enable Limit counter mode, request the time
needed to count 2000 pulses.
OK
^SCCNT: 0000002040
"^SCCNT" URC indicates the time taken to count 2000 pulses.
at^sccnt=1,1,10000
Open pulse counter, enable Limit counter mode, request the time
needed to count 10000 pulses.
OK
^SCCNT: 0000010043
"^SCCNT" URC indicates the time taken to count 10000 pulses.
at^sccnt=1,1,20000
Open pulse counter, enable Limit counter mode, request the time
needed to count 20000 pulses.
OK
^SCCNT: 0000020040
"^SCCNT" URC indicates the time taken to count 20000 pulses.
This example shows how to stop the Limit counter mode and close the pulse counter without waiting for the
"^SCCNT" URC. Both methods have the same effect, it is up to you which one to use.
at^sccnt=0,0
Stop and close the pulse counter immediately, without "^SCCNT" URC
being indicated.
OK
at^sscnt=3
Stop and close the pulse counter immediately, without "^SCCNT" URC
being indicated.
OK
20.9
AT^SSCNT Start and Stop Pulse Counter
The AT^SSCNT write command serves to read, start, restart and stop the pulse counter.
Syntax
Test Command
AT^SSCNT=?
Response(s)
^SSCNT:(list of supported <action>s)
OK
Read Command
AT^SSCNT?
Response(s)
^SSCNT: <action>
OK
If an error occurs:
ERROR
+CME ERROR: <err>
Write Command
AT^SSCNT=<action>
Response(s)
If <action>=0 or 1:
OK
If <action>=2 or 3:
OK
"^SSCNT" URC with parameter <pulse>
If an error occurs:
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Unsolicited Result Code
^SSCNT: <pulse>
The URC applies only to the Start-Stop mode set with AT^SCCNT, parameter <mode>=0. It is delivered once the
pulse counter result was requested with <action>=2 or the pulse counter was stopped with <action>=3. The
URC indicates the number of pulses counted.
Parameter Description
<action>(num)
This parameter can only be used after configuring the pulse counter with AT^SCCNT. The <action> types 0, 1
and 2 apply only to the Start-Stop counter mode set with AT^SCCNT.
0
Reset and start pulse counter from 0.
1
Restart pulse counter and continue counting from the <pulse> value of the
last run.
2
Read out current <pulse> value.
3
The effect of value 3 depends on the selected counter mode:
If AT^SCCNT, parameter
<mode>=
0
(Start-Stop counter mode), then
<action> type 3 stops the pulse counter and displays, as "^SSCNT" URC, the
number of pulses counted until this time.
If AT^SCCNT, parameter <mode>= 1 (Limit counter mode), then <action>
type 3 immediately stops the pulse counter without indicating the "^SCCNT"
URC. This action has the same effect as the command AT^SCCNT=0,0.
<pulse>(num)
Measurement result of the pulse counter in Start-Stop mode, indicated within the "^SSCNT" URC, if AT^SCCNT,
parameter <action>=2 or 3. The value range of <pulse> is 32 bits (232-1).
0...4294967295
Number of pulses counted.
Note
• Measurement accuracy: In Start-Stop mode, you can achieve 100% accuracy if you take care that pulse trans-
mission begins after the start command (AT^SSCNT=0 or 1) has returned OK and ends before the stop com-
mand (AT^SSCNT=3) is issued.
20.9.1
Using the Pulse Counter in Start-Stop Counter Mode
at^sccnt=1,0
Open pulse counter and enable Start-Stop counter mode.
OK
at^sscnt=0
Reset and start pulse counter from 0.
OK
at^sscnt=2
Request value.
OK
^SSCNT: 0000003254
"^SSCNT" URC indicates number of pulses counted.
at^sscnt=2
Request value.
OK
^SSCNT: 0000010024
"^SSCNT" URC indicates number of pulses counted.
at^sscnt=2
Request value.
OK
^SSCNT: 0000015134
"^SSCNT" URC indicates number of pulses counted.
at^sscnt=3
Request value and stop pulse counter.
OK
^SSCNT: 0000021020
"^SSCNT" URC indicates number of pulses counted until this time.
at^sscnt=2
Request value.
OK
^SSCNT: 0000021020
"^SSCNT" URC still indicates the count of the last run.
at^sscnt=1
Restart pulse counter at the value of the last run.
OK
at^sscnt=2
Request value.
^SSCNT: 0000022123
"^SSCNT" URC indicates number of pulses incremented from the last
run.
21.
Java related Commands
This chapter describes the AT commands related to Java applications processed by the TC65i.
21.1
AT^SJRA Run Java Application
The AT^SJRA write command launches the Java application.
Syntax
Test Command
AT^SJRA=?
Response(s)
("IMlet path")
Write Command
AT^SJRA=<appName>
Response(s)
^SJRA:
OK
If not successful:
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Parameter Description
<appName>(str)
Path of the Java application
The application name must be given as a fully qualified pathname (a:/.../...) to the jar/jad file containing the
desired application.
The local flash file system is identified by: A:. Directory separator is ''/'' (002Fh).
Example: A:/java/jam/example/helloworld/helloworld.jar
Notes
• As an alternative, the Java application can be enabled to start up automatically whenever TC65i is getting
started. Use the AT^SCFG command to make all the settings need for the Java autostart mode.
• When the Java application starts, all current calls will be terminated.
21.2
AT^SJNET Set Dialup Network Access Parameters
The AT^SJNET write command allows to create a profile which contains all parameters needed for automated
network access through a dialup connection.
Syntax
Test Command
AT^SJNET=?
Response(s)
^SJNET:("csd"|"gprs"), ("Tel. num."|"access point name"), ("login"), ("password"), ("dns"), (list of supported
<timeout>s)
OK
Read Command
AT^SJNET?
Response(s)
^SJNET: <bearer service>, <entry point>, <login>, <password>, <dns>, <timeout>
OK
ERROR
+CME ERROR: <err>
Write Command
AT^SJNET=<bearer service>, <entry point>, <login>, <password>[, <dns>][, <timeout>]
Response(s)
^SJNET: <bearer service>, <entry point>, <login>, <password>, <dns>, <timeout>
OK
ERROR
+CME ERROR: <err>
PIN ASC0 ASC1
USB MUX1 MUX2 MUX3 Charge
4
Last
-
+
+
+
+
+
+
-
+
-
Parameter Description
<bearer service>(str)(+CSCS)
“none“(P)
No bearer specified
“csd“
Dialup access uses Circuit Switched Data connection
“gprs“
Dialup access via GPRS
<entry point>(str)(+CSCS)
““(P)
The content of parameter <entry point> depends on <bearer service>.
The parameter is global for all interfaces, volatile and will not be reset by AT&F.
• If <bearer service> is "csd", then parameter specifies the dialup phone
number. The phone number can be modified to select between ISDN and
anlaog call and to choose a bitrate. See also examples below.
- The first character added to the phone number selects the mode: i =
ISDN call, a = analog call (default). If omitted the default setting "analog"
applies.
- The last character appended to the phone number determines the
bitrate. If omitted the default setting "9600 bps" applies.
h = 14400 bps
m = 9600 bps (default)
l
= 4800 bps
s = 2400 bps
• If
<bearer service> is "gprs", then parameter specifies the GPRS
access point name.
<login>(str)(+CSCS)
““(P)
Specifies the login name for access to the dialup network. The login name con-
sists of maximal 31 characters.
Parameter is global for all interfaces, volatile and will not be reset by AT&F.
<password>(str)(+CSCS)
““(P)
Specifies the password for access to the dialup network.
Parameter is global for all interfaces, volatile and will not be reset by AT&F.
<dns>(str)(+CSCS)
““(P)
Specifies the Primary DNS server (Nameserver) for the dialup network. The
server address has to be specified in dotted IP address format
(e.g.
145.146.147.148). If the parameter is omitted, the DNS assigned by the net-
work is used.
It is recommended to set manual DNS server addresses rather than using
automatic DNS assignment. This avoids problems in case the network is
unable to properlyhandle the automatic DNS service.
Parameter is global for all interfaces, volatile and will not be reset by AT&F.
<timeout>(num)
Idle Timeout in seconds
0(P)...[30]...21600
Specifies the Java network idle timeout, which is the number of seconds to wait
before the network connection is terminated automatically when no data trans-
fer or other network activities take place. The value 0 means no timeout at all
(you have to terminate a Circuit Switched Data connection using ATH and a
GPRS connection using AT+CGATT=0).
We recommend to use values greater than 10 seconds because otherwise you
may get unintentional timeouts for slow network connections.
Parameter is global for all interfaces, volatile and will not be reset by AT&F.
Note
• The authentication mode for CSD and GPRS is always PAP.
Examples
EXAMPLE 1
This example illustrates how to configure a profile for circuit switched network access: The dialup phone num-
ber is +49800654321, user name is "user1", password is "dialup123", and the primary DNS has IP address
"145.146.147.148". The phone number does not contain additional characters, therefore the destination is an
analog device (default) and the bitrate is 9600 bps (default).
AT^SJNET="CSD", "+49800654321", "user1", "dialup123", "145.146.147.148"
^SJNET: "csd","+49800654321","user1","dialup123","145.146.147.148",30
OK
EXAMPLE 2
Same example as above, but the phone number contains additional characters for ISDN and 14400bps.
AT^SJNET="CSD", "i+49800654321h", "user1", "dialup123", "145.146.147.148"
^SJNET: "csd","i+49800654321h","user1","dialup123","145.146.147.148",30
OK

 

 

 

 

 

 

 

Content      ..     4      5      6      7     ..