User Manual

Table Of Contents
SARA-R4/N4 series-AT Commands Manual
UBX-17003787 - R11
10V24 control and V25ter
Page 98 of 308
10.6.3Defined values
Parameter Type Description
<format> Number
0: auto detect
1: 8 data 2 stop
2: 8 data 1 parity 1 stop
3: 8 data 1 stop
4: 7 data 2 stops
5: 7 bit, 1 parity, 1 stop
6: 7 bit, 1 stop
<parity> Number
0: odd
1: even
10.6.4Notes
SARA-R4
Automatic frame recognition is not supported (<format> cannot be set to 0).
The only supported values are <format> = 3 and <parity> = 1.
10.7DTE-DCE local flow control +IFC
+IFC
SARA-R410M-52B SARA-R412MModules
SARA-N4
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No Profile No - +CME Error
10.7.1Description
Controls the operation of the local flow control between DTE and DCE used when the data are sent or received.
The SW flow control (XON/XOFF) activation is only allowed in case of the text transmission: the binary data
cannot be transmitted because it may contain the special flow control characters (XON/XOFF). For the SW
flow control enhancement, allowing its usage during a PSD call with PPP L2 protocol, see SW flow control
enhancement for PSD data transfer with PPP L2 protocol in the AT&K command description.
When the software flow control (XON/XOFF) is used, the DC1 (XON, 0x11) and DC3 (XOFF, 0x13) characters are
reserved and therefore filtered (e.g. in SMS text mode these two characters can not be input).
Since the DTE-DCE communication relies on the correct reception of DC1/DC3 characters, the UART power
saving should be disabled on the module when SW flow control is used. If the UART power saving is active, the
DC1/DC3 characters could be used to wake up the module's UART, and therefore lost. In case a DC3 character
(XOFF) is correctly received by module's UART and some data is waiting to be transmitted, the module is forced
to stay awake until a subsequent DC1 character (XON) is received.
The software flow control (XON/XOFF) setting is not allowed on the USB interfaces, on the SPI interface
and on a multiplexer channel. See the Multiple AT command interfaces for all the behavior differences in
respect to the supported interfaces.
10.7.2Syntax
Type Syntax Response Example
Set AT+IFC=[<DCE_by_DTE>[,<DTE_by_
DCE>]]
OK AT+IFC=2,2
OK
Read AT+IFC? +IFC: <DCE_by_DTE>,<DTE_by_
DCE>
OK
+IFC: 2,2
OK
Test AT+IFC=? +IFC: (list of supported <DCE_by_
DTE>),(list of supported <DTE_by_
DCE>s)
OK
+IFC: (0-2),(0-2)
OK