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 60 of 182
established. For a data call there are the following scenarios (see the u-blox AT Commands Manual [2]
for the definition of the interface data mode, command mode and online command mode):
PSD data call: Before activating the PPP protocol (data mode) a dial-up application must provide
the ATD*99***<context_number># to the module: with this command the module switches from
command mode to data mode and can accept PPP packets. The module sets the DCD line to the
ON state, then answers with a CONNECT to confirm the ATD*99 command. The DCD ON is not
related to the context activation but with the data mode.
CSD data call: To establish a data call, the DTE can send the ATD<number> command to the
module which sets an outgoing data call to a remote modem (or another data module). Data can
be transparent (non-reliable) or non-transparent (with the reliable RLP protocol). When the remote
DCE accepts the data call, the module DCD line is set to ON and the CONNECT <communication
baudrate> string is returned by the module. At this stage, the DTE can send characters through
the serial line to the data module which sends them through the network to the remote DCE
attached to a remote DTE.
☞ For a voice call, DCD is set to ON state on all the serial communication interfaces supporting the
AT command interface (including MUX virtual channels, if active).
☞ DCD is set to ON during the execution of a command that requires input data from the DTE (all the
commands where a prompt is issued; see AT commands +CMGS, +CMGW, +USOWR, +USODL,
+UDWNFILE in the u-blox AT Commands Manual [2]). The DCD line is set to ON state as soon as
the switch to binary/text input mode is completed and the prompt is issued; DCD line is set to OFF
as soon as the input mode is interrupted or completed.
☞ DCD line is kept to ON state even during the online command mode to indicate that the data call
is still established even if suspended, while if the module enters command mode, the DSR line is
set to OFF state. For more details, see the DSR signal behavior description.
☞ For scenarios where the DCD line setting is requested for various reasons (e.g. SMS texting during
online command mode), the DCD line changes to guarantee the correct behavior for all the
scenarios. For instance, in case of SMS texting in online command mode, if the data call is
released, the DCD line will be kept to ON until the SMS command execution is completed (even if
the data call release would request the DCD setting to OFF).
RI signal behavior
The RI module output line is set by default to the OFF state (high level) at UART initialization. Then,
during an incoming call, the RI line is switched from OFF state to ON state with a 4:1 duty cycle and a
5 second period (ON for 1 second, OFF for 4 seconds, see Figure 26), until the DTE attached to the
module sends the ATA string and the module accepts the incoming data call. The RING string sent by
the module (DCE) to the serial port at constant time intervals is not correlated with the switch of the
RI line to the ON state.
Figure 26: RI behavior during an incoming call
1s
time [s]
151050
RI ON
RI OFF
Call incomes
1s
time [s]
151050
RI ON
RI OFF
Call incomes