Integration Manual
Table Of Contents
- Document Information
- Contents
- 1 System description
- 1.1 Overview
- 1.2 Architecture
- 1.3 Pin-out
- 1.4 Operating modes
- 1.5 Power management
- 1.6 System functions
- 1.7 RF connection
- 1.8 (U)SIM interface
- 1.9 Serial communication
- 1.9.1 Serial interfaces configuration
- 1.9.2 Asynchronous serial interface (UART)
- 1.9.2.1 UART features
- 1.9.2.2 UART signal behavior
- 1.9.2.3 UART and power-saving
- 1.9.2.4 UART application circuits
- Providing the full RS-232 functionality (using the complete V.24 link)
- Providing the TxD, RxD, RTS, CTS and DTR lines only (not using the complete V.24 link)
- Providing the TxD, RxD, RTS and CTS lines only (not using the complete V.24 link)
- Providing the TxD and RxD lines only (not using the complete V24 link)
- Additional considerations
- 1.9.3 USB interface
- 1.9.4 SPI interface
- 1.9.5 MUX protocol (3GPP TS 27.010)
- 1.10 DDC (I2C) interface
- 1.11 Audio Interface
- 1.12 General Purpose Input/Output (GPIO)
- 1.13 Reserved pins (RSVD)
- 1.14 Schematic for LISA-U2 module integration
- 1.15 Approvals
- 1.15.1 European Conformance CE mark
- 1.15.2 US Federal Communications Commission notice
- 1.15.3 Innovation, Science, Economic Development Canada notice
- 1.15.4 Australian Regulatory Compliance Mark
- 1.15.5 ICASA Certification
- 1.15.6 KCC Certification
- 1.15.7 ANATEL Certification
- 1.15.8 CCC Certification
- 1.15.9 Giteki Certification
- 2 Design-In
- 3 Features description
- 3.1 Network indication
- 3.2 Antenna detection
- 3.3 Jamming Detection
- 3.4 TCP/IP and UDP/IP
- 3.5 FTP
- 3.6 HTTP
- 3.7 SSL/TLS
- 3.8 Dual stack IPv4/IPv6
- 3.9 AssistNow clients and GNSS integration
- 3.10 Hybrid positioning and CellLocate®
- 3.11 Control Plane Aiding / Location Services (LCS)
- 3.12 Firmware update Over AT (FOAT)
- 3.13 Firmware update Over the Air (FOTA)
- 3.14 In-Band modem (eCall / ERA-GLONASS)
- 3.15 SIM Access Profile (SAP)
- 3.16 Smart Temperature Management
- 3.17 Bearer Independent Protocol
- 3.18 Multi-Level Precedence and Pre-emption Service
- 3.19 Network Friendly Mode
- 3.20 Power saving
- 4 Handling and soldering
- 5 Product Testing
- Appendix
- A Migration from LISA-U1 to LISA-U2 series
- A.1 Checklist for migration
- A.2 Software migration
- A.2.1 Software migration from LISA-U1 series to LISA-U2 series modules
- A.3 Hardware migration
- A.3.1 Hardware migration from LISA-U1 series to LISA-U2 series modules
- A.3.2 Pin-out comparison LISA-U1 series vs. LISA-U2 series
- A.3.3 Layout comparison LISA-U1 series vs. LISA-U2 series
- B Glossary
- Related documents
- Revision history
- Contact
LISA-U2 series - System Integration Manual
UBX-13001118 - R25 System description Page 58 of 182
TxD signal behavior
The module data input line (TxD) is set by default to OFF state (high level) at UART initialization. The
TxD line is then held by the module in the OFF state if the line is not activated by the DTE: an active
pull-up is enabled inside the module on the TxD input.
CTS signal behavior
The module hardware flow control output (CTS line) is set to the ON state (low level) at UART
initialization.
If the hardware flow control is enabled, as it is by default, the CTS line indicates when the UART
interface is enabled (data can be sent and received). The module drives the CTS line to the ON state
or to the OFF state when it is either able or not able to accept data from the DTE over the UART (see
1.9.2.3 for more details).
☞ If hardware flow control is enabled, then when the CTS line is OFF it does not necessarily mean
that the module is in low-power idle mode, but only that the UART is not enabled, as the module
could be forced to stay in active mode for other activities, e.g. related to the network or related to
other interfaces.
☞ When the multiplexer protocol is active, the CTS line state is mapped to the FCon / FCoff MUX
command for flow control issues outside the power saving configuration, while the physical CTS
line is still used as a power state indicator. For more details, see the Mux Implementation
Application Note [14].
The CTS hardware flow control setting can be configured by AT commands (for more details, see the
u-blox AT Commands Manual [2], AT&K, AT\Q, AT+IFC, AT+UCTS AT command).
If the hardware flow control is not enabled, the CTS line after the UART initialization behaves as
follows:
on LISA-U2 modules "01", "x2", "63" and "68" product versions, the CTS line is always held in the ON
state
on LISA-U2 modules "03" product version onward, the CTS line is by default set in the ON state,
but can be configured in the OFF state by the AT+UCTS command
☞ When the power saving configuration is enabled and the hardware flow-control is not implemented
in the DTE/DCE connection, data sent by the DTE can be lost: the first character sent when the
module is in the low-power idle mode will not be a valid communication character (see 1.9.2.3 for
more details).
RTS signal behavior
The hardware flow control input (RTS line) is set by default to the OFF state (high level) at UART
initialization. The RTS line is then held by the module in the OFF state if the line is not activated by
the DTE: an active pull-up is enabled inside the module on the RTS input.
If the HW flow control is enabled (for more details, see the u-blox AT Commands Manual [2] AT&K,
AT\Q, AT+IFC command description) the RTS line is monitored by the module to detect permission
from the DTE to send data to the DTE itself. If the RTS line is set to OFF state, any on-going data
transmission from the module is immediately interrupted or any subsequent transmission forbidden
until the RTS line changes to ON state.
☞ The DTE must be able to still accept a certain number of characters after the RTS line has been
set to OFF state: the module guarantees the transmission interruption within 2 characters from
RTS state change.