14.03.2015 Views

AT Commands Reference Manual - wireless netcontrol GmbH

AT Commands Reference Manual - wireless netcontrol GmbH

AT Commands Reference Manual - wireless netcontrol GmbH

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

UI (User Interface)<br />

The following table shows the +CRSM parameters.<br />

Table 3-180: +CRSM Parameters<br />

<br />

<br />

Description<br />

Integer type. Command passed on by the ME to the SIM.<br />

176 READ BINARY<br />

178 READ RECORD<br />

192 GET RESPONSE<br />

214 UPD<strong>AT</strong>E BINARY<br />

220 UPD<strong>AT</strong>E RECORD<br />

242 ST<strong>AT</strong>US<br />

<br />

,,<br />

<br />

Integer type. This is the identifier of a elementary data file on SIM. Mandatory for<br />

every except of ST<strong>AT</strong>US.<br />

Integer type. Parameters passed on by the ME to the SIM. These parameters are<br />

mandatory for every command, except GET RESPONSE and ST<strong>AT</strong>US.<br />

Valid value range: 0-255.<br />

<br />

<br />

Information which shall be written to the SIM (hexadecimal character format).<br />

Mandatory for UPD<strong>AT</strong>E BINARY and UPD<strong>AT</strong>E RECORD.<br />

Integer character format. Information from the SIM about the execution of the actual<br />

command. These parameters are delivered to the TE in both cases, on successful or<br />

failed execution of the command.<br />

Valid value range: 0-255.<br />

<br />

Response of a successful completion of the command previously issued (hexadecimal<br />

character uppercase format). ST<strong>AT</strong>US and GET RESPONSE return data, which gives<br />

information about the current elementary data . This information includes<br />

the type of file and its size (refer TS 51.011 and TS 31.101). After READ BINARY or<br />

READ RECORD command the requested data will be returned. is empty<br />

string after a UPD<strong>AT</strong>E BINARY or UPD<strong>AT</strong>E RECORD command.<br />

Example<br />

<strong>AT</strong>+CRSM=192,28474<br />

// GET RESPONSE, ADN(6F3A)<br />

+CRSM: 144,0,"621E82054221001EFA83026F3AA5038001318A01058B036F060980021D4C8800"<br />

OK<br />

<strong>AT</strong>+CRSM=178,28474,1,4,0 // READ RECORD, ADN(6F3A)<br />

+CRSM: 144,0,"4245545441FFFFFFFFFFFFFFFFFFFFFF06913355555555FFFFFFFFFFFFFF"<br />

OK<br />

<strong>AT</strong>+CRSM=242,28474<br />

// ST<strong>AT</strong>US, ADN(6F3A)<br />

+CRSM: 144,0,"62208202782183027F10A5038001318A01058B032F0611C609900140830101830181"<br />

OK<br />

<strong>AT</strong>+CRSM=220,28474,1,4,30,"4245545441FFFFFFFFFFFFFFFFFFFFFF06913355555555FFFFFFFF<br />

FFFFFF"<br />

//UPD<strong>AT</strong>E RECORD, ADN (6F3A), 1st record<br />

+CRSM: 144,0,""<br />

3-272 H24 - <strong>AT</strong> <strong>Commands</strong> <strong>Reference</strong> <strong>Manual</strong> April 15, 2010

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!