02.06.2014 Views

TC35i Module TC35i Terminal

TC35i Module TC35i Terminal

TC35i Module TC35i Terminal

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.

<strong>TC35i</strong> AT Command Set<br />

Confidential / Released<br />

1.6 Flow control<br />

Flow control is essential to prevent loss of data or avoid errors when, in a data or fax call, the sending<br />

device is transferring data faster than the receiving side is ready to accept. When the receiving buffer<br />

reaches its capacity, the receiving device should be capable to cause the sending device to pause until<br />

it catches up.<br />

There are basically two approaches to regulate data flow: software flow control and hardware flow<br />

control. The High Watermark of the input / output buffer should be set to approximately 60% of the total<br />

buffer size. The Low Watermark is recommended to be about 30%. The data flow should be<br />

stopped when the capacity rises close to the High Watermark and resumed when it drops below the<br />

Low Watermark. The time required to cause stop and go results in a hysteresis between the High and<br />

Low Watermarks.<br />

In Multiplex mode, it is recommended to use hardware flow control. For details please refer to [4].<br />

1.6.1 Software flow control (XON/OFF flow control)<br />

Software flow control sends different characters to stop (XOFF, decimal 19) and resume (XON, decimal<br />

17) data flow. The only advantage of software flow control is that three wires would be sufficient<br />

on the serial interface.<br />

1.6.2 Hardware flow control (RTS/CTS flow control)<br />

Hardware flow control sets or resets the RTS/CTS wires. This approach is faster and more reliable,<br />

and therefore, the better choice. When the High Watermark is reached, CTS is set inactive until the<br />

transfer from the buffer has completed. When the Low Watermark is passed, CTS goes active once<br />

again.<br />

To achieve smooth data flow, ensure that the RTS/CTS lines are present on your application platform.<br />

The application should include options to enable RTS/CTS handshake with the GSM engine. This<br />

needs to be done with the AT commands AT\Q3 or AT+IFC - it is not sufficient to set RTS/CTS handshake<br />

in the used <strong>Terminal</strong> program only. For details refer to Chapter 2.3 and Chapter 2.45.<br />

Often, fax programs run an intialization procedure when started up. The intialization commonly includes<br />

enabling RTS/CTS hardware handshake, eliminating the need to set AT\Q3 once again. However,<br />

before setting up a CSD call, you are advised to check that RTS/CTS handshake is set.<br />

Note:<br />

After deactivating the RTS line, the ME may still send up to 264 bytes (worst case). This can<br />

be easily managed if the buffer of the host application is sufficiently sized, and if a hysteresis<br />

is implemented in its Rx buffer as mentioned in Chapter 1.6. For host applications that are required<br />

to handle a large amount of data at high speed, a total buffer capacity of at least 512<br />

bytes is recommended.<br />

<strong>TC35i</strong>_ATC_V01.05 Page 16 of 278 04.08.2003

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

Saved successfully!

Ooh no, something went wrong!