LANTRONIX SARA-R5 Series NB-IoT Modules User Manual

LANTRONIX SARA-R5 Series NB-IoT Modules

Document information

• Title SARA-R500S-01B
• Subtitle LTE-M / NB-IoT modules
• Document type Data sheet

 |
---|---
Product Status| Corresponding content status
Functional sample| Draft| For functional testing. Revised and supplementary data will be published later.
In development /

Prototype

| Objective specification| Target values. Revised and supplementary data will be published later.
Engineering sample| Advance information| Data based on early testing. Revised and supplementary data will be published later.
Initial production| Early production information| Data from product verification. Revised and supplementary data may be published later.
Mass production /

End of life

| Production information| The document contains the final product specification.

Functional description

Overview

• SARA-R500S-01B, general purpose LTE Cat M1 / LTE Cat NB2 product designed for multi-regional deployments

The miniature SARA LGA form factor (26.0 x 16.0 mm, 96-pin) allows easy integration into compact designs and seamless drop-in migration from other LTRX cellular module families. SARA-R5 series modules are form-factor compatible with the LTRX LISA, LARA and TOBY cellular module families and they are pin-to-pin compatible with the u-blox SARA-R4, SARA-N2, SARA-N3, SARA-N4, SARA-G3, SARA-G4 and SARA-U2 cellular modules families. This facilitates migration from other LTRX LPWA modules as well as from other LTRX GSM/GPRS, CDMA, UMTS/HSPA and higher LTE categories modules, maximizing customer investments, simplifying logistics, and enabling very short time-to-market. SARA-R500S-01B modules provide software-based multi-band configurability enabling international multi-regional coverage in LTE Cat M1 / NB2 radio access technologies, supporting a comprehensive set of 3GPP Rel. 14 features that are relevant for IoT applications. SARA-R500s modules offer data communications up to 1200 kbit/s over an extended operating temperature range of –40 °C to +85 °C, with low power consumption, and coverage enhancement for a deeper range into buildings and basements (and underground with NB2).

Block diagram

1.4 Product description

Item SARA-R500S-01B

Cellular protocol stack              3GPP Rel.13 LTE Cat M1 and NB1

3GPP Rel.14 LTE Cat M1: Coverage Enhancement Mode B, Uplink TBS of 2984b 3GPP Rel.14 LTE Cat NB2: Higher data rate (TBS of 2536b), Mobility enhancement (RRC connection re-establishment), E-Cell ID, two HARQ processes, Release Assistant, Random access on Non-Anchor Carrier

Cellular RAT                            LTE Cat M1 Half-Duplex LTE Cat NB2 Half-Duplex

Cellular operating bands| LTE FDD band 1 (2100 MHz)

LTE FDD band 2 (1900 MHz)

LTE FDD band 3 (1800 MHz)

LTE FDD band 4 (1700 MHz)

LTE FDD band 5 (850 MHz)

LTE FDD band 8 (900 MHz)

LTE FDD band 12 (700 MHz)

LTE FDD band 13 (750 MHz)

LTE FDD band 18 (850 MHz)

LTE FDD band 19 (850 MHz)

LTE FDD band 20 (800 MHz)

LTE FDD band 25 (1900 MHz)

LTE FDD band 26 (850 MHz)

LTE FDD band 28 (700 MHz)

LTE FDD band 66 (1700 MHz)

LTE FDD band 71 (600 MHz)

LTE FDD band 85 (700 MHz)

Cellular power class                  LTE power class 3 (23 dBm) LTE power class 3 (23 dBm)

Cellular data rate                    LTE category M1:

up to 1200 kbit/s UL, up to 375 kbit/s DL LTE category NB2:

up to 140 kbit/s UL, up to 125 kbit/s DL

AT command support
The SARA-R500s modules support AT commands according to the 3GPP standards TS 27.007 [4],  TS 27.005 [5], TS 27.010 [6].

• For the complete list of all supported AT commands and their syntax, see SARA-R5 series AT  commands manual [1].

Supported features
Table 3 lists some of the main features supported by SARA-R500s modules. For more details, see the SARA-R5 series system integration manual [2] and the SARA-R5 series AT commands manual [1].

chips and modules through I2C interface.

This means that any external host processor can control the SARA-R500E, SARA- R500S or SARA-R510S cellular module and the u-blox GNSS chip/module through a single serial port.

Embedded AssistNow Software| Embedded AssistNow Online and AssistNow Offline clients are available to provide better GNSS performance and faster Time-to- First-Fix. An AT command can enable/disable the clients.
CellLocate®| Enables the estimation of device position based on the parameters of the mobile network cells visible to the specific device based on the CellLocate® database.

CellLocate® is available via a set of AT commands for CellLocate® service configuration and position requests.

Hybrid Positioning| Provides the module’s current position using a u-blox positioning chip or module (external for SARA-R500E / SARA-R500S / SARA-R510S, integrated UBX-M8 chip for SARA-R510M8S) or

the estimated position from CellLocate®, depending on which positioning method provides the best and fastest solution according to the user configuration.

Hybrid positioning is implemented through a set of AT commands that allow the configuration and the position request.

CellTime| Returns accurate timing retrieved from the LTE network and/or from the u-blox positioning chip or module (external for the SARA-R500E / SARA- R500S / SARA-R510S cellular modules, integrated UBX-M8 chip for the SARA- R510M8S modules).

Can be used to provide periodic time stamps to an external application processor or to output a time indication associated to an interrupt detected on a GPIO (e.g. coming from an external sensor connected to the module).

The implementation of CellTime can be extended to control and maintain timing info in a network of sensors (each one integrating a SARA-R5 module).

Antenna dynamic tuning| Control via two GPIOs and an external antenna matching IC according to the LTE band used by the module.
Embedded TCP and UDP stack| Embedded TCP/IP and UDP/IP stack including direct link mode for TCP and UDP sockets. Sockets can be set in Direct Link mode to establish a transparent end-to-end communication with an already connected TCP or UDP socket via the serial interface.
HTTP, HTTPS (v1.0 for +UHTTP,

v1.1 for LwM2M client)

| Hyper-Text Transfer Protocol as well as Secure Hyper-Text Transfer Protocol (SSL encryption) functionalities are supported via AT commands.
FTP, FTPS| File Transfer Protocol as well as Secure File Transfer Protocol (SSL encryption of FTP control channel) functionalities are supported by means of AT commands.
CoAP

(RFC 7252) [11]

| Embedded Constrained Application Protocol (CoAP) datagram-based client/server application protocol designed to easily translate from HTTP for simplified integration with the web.
MQTT (v3.1.1) and MQTT-SN (v1.2)| Embedded Message Queuing Telemetry Transport (MQTT) and MQTT for Sensor Networks (MQTT-SN) publish-subscribe messaging protocols designed for lightweight M2M communications over TCP (MQTT) or over UDP (MQTT-SN). These allow one-to-one, one-to-many and many-to-one communications over a TCP or UDP connection.
LwM2M with dynamically loaded objects (v1.0)| The LwM2M is a light and compact communication protocol designed for managing IoT machine-to-machine communication between a LwM2M Server and a LwM2M Client located in lightweight, low power or resource-constrained LwM2M devices, with object data model.

SARA-R5 series modules allow customers to configure dynamically loaded run time objects, define necessary custom objects, create instances of those objects as appropriate, and manage the module LwM2M protocol stack to interact with the LwM2M server.

TLS (v1.0, v1.1, v1.2, v1.3)

and DTLS (v1.2)

| Transport Layer Security (TLS) provides security for HTTP, FTP, MQTT and TCP communications.

Embedded Datagram Transport Layer Security (DTLS) provides security for CoAP, LwM2M, MQTT-SN and UDP communications.

Jamming detection| Detects “artificial” interference that obscures the operator’s carrier entitled to give access to the radio service and automatically reports the start and stop of such conditions to the application processor that can react accordingly.

Interfaces

Power management

Module supply input (VCC)
SARA-R500S-01B modules must be supplied through the VCC pins by a proper external DC power supply providing a nominal voltage within the normal operating range (see Table 11). Voltage must be stable, because during operation the current drawn from VCC may vary significantly, based on the power consumption profile of the LTE Cat M1 and LTE Cat NB2 radio access technologies (described in the SARA-R5 series system integration manual [2]). The three VCC pins of SARA-R5 series modules are internally connected to both the internal Power Amplifier and the internal Power Management Unit, which integrates voltage regulators generating all the internal supply voltages needed by the module for the designed operations, as the supply voltage for the generic digital interfaces (V_INT), the supply voltage for the SIM interface (VSIM), and the supply voltage for the internal GNSS receiver. It is important that the system power supply circuit is able to withstand the maximum pulse current during a transmit burst at maximum power level (see Table 13).

Generic digital interfaces supply output (V_INT)
SARA-R5 series modules provide a 1.8 V supply rail output on the V_INT pin, which is internally generated when the module is switched on. The same voltage domain is used internally to supply the generic digital interfaces of the module. The V_INT supply output can be used in place of an external discrete regulator.

• It is recommended to provide accessible test point directly connected to the V_INT pin.

Antenna interface

Cellular antenna RF interface (ANT)
The ANT pin is the cellular RF antenna I/O interface, designed with 50 Ω characteristic impedance.

GNSS antenna RF interface (ANT_GNSS)

• The GNSS antenna RF interface is not supported by SARA-R500E, SARA-R500S, and SARA-R510S. The ANT_GNSS pin represents the GNSS RF input of the SARA-R510M8S modules, designed with 50  characteristic impedance and with an internal DC block, suitable for both active and/or passive GNSS antennas due to the built-in SAW filter followed by an LNA in front of the integrated high performing LTRX M8 concurrent positioning engine.

Antenna detection (ANT_DET)
The ANT_DET pin is an Analog to analog-to-digital converter (ADC) input with a current source provided by SARA-R5 series modules to sense the external antenna presence (as an optional feature), evaluating the DC resistance to GND by means of an externally implemented circuit (for more details, see the LTRX SARA-R5 series system integration manual [2] and the SARA-R5 series AT commands manual [1]).

System functions

Module power-on

When the SARA-R500E, SARA-R500S and SARA-R510M8S modules are not powered, they can be switched on as follows:

• Rising edge on the VCC supply input to a valid voltage for modules supply: the modules switch on applying VCC supply starting from a voltage value lower than 2.15 V, providing a fast enough VCC voltage slope, as it must ramp from 2.15 V to 3.0 V within 300 ms, and reach a regular nominal VCC voltage value within the operating range (see Table 11). When the SARA-R510S modules are not powered, they can be switched on as follows:
• Applying a voltage at the VCC module supply input within the operating range (see Table 11), and then forcing a low level at the PWR_ON input pin, which is normally set high by an internal pull-up, for a valid period (see section 4.2.9, module switch on). When the SARA-R5 series modules are in power-off mode (i.e. switched off, but with a valid voltage present at the VCC module supply input within the operating range reported in Table 11), they can be switched on as follows:
• Forcing a low level at the PWR_ON input pin, which is normally set high by an internal pull-up, for a valid period (see section 4.2.9, module switch-on). When the SARA-R5 series modules are in low-power PSM / eDRX6 deep-sleep mode, with a valid voltage present at the VCC module supply input within the operating range reported in Table 11, they can be woken up as follows:
• Forcing a low level at the PWR_ON input pin, which is normally set high by an internal pull-up, for a valid period (see section 4.2.9, module early wake-up from PSM / eDRX deep-sleep). The PWR_ON line is intended to be driven by the open drain, open collector or contact switch.

Module power-off
The proper graceful power-off of the SARA-R5 series modules, with storage of the current parameter settings in the module’s non-volatile memory and a clean network detach, can be triggered by:

• AT+CPWROFF command (see the SARA-R5 series AT commands manual [1]) A faster and safe power-off procedure of the modules, with storage of the current parameter settings in the module’s non-volatile memory and without a clean network detach, can be triggered by:
• AT+CFUN=10 command (see the SARA-R5 series AT commands manual [1])
• Toggling the GPIO input configured with the faster and safer power-off function (see section 2.7) An abrupt emergency hardware shutdown of the modules, without saving current parameter settings in the module’s non-volatile memory and without clean network detach, can be executed by:
• Forcing a low pulse at the PWR_ON and RESET_N input pins, in the proper sequence described in section 4.2.9 with details in Figure 6
• It is recommended to provide an accessible test point directly connected to the PWR_ON input pin.

An abrupt under-voltage shutdown occurs on SARA-R5 series modules when the VCC supply is removed. If this occurs, it is not possible to store the current parameter settings in the module’s non-volatile memory or to perform the proper network detach.
An over-temperature or an under-temperature shutdown occurs on the SARA-R5 series modules when the temperature measured within the module reaches the dangerous area (see section 4.2.16), if the optional “Smart temperature supervisor” feature is enabled and configured by the dedicated AT command (see the SARA-R5 series AT commands manual [1], +USTS AT command).

Module reset
SARA-R5 series modules can be reset (re-booted), saving current parameter settings in the module’s non-volatile memory and performing a proper network detach, by:

• AT+CFUN=16 command (for other options and further details, see the SARA-R5 series AT commands manual [1]). This causes a graceful software reset of the module. An abrupt software reset of the module is executed by applying a low pulse at the RESET_N input pin, which is normally set high by an internal pull-up, for a valid time period (see section 4.2.10). The current parameter settings are not saved in the module’s non-volatile memory and a proper network detach is not performed.
  The RESET_N line is intended to be driven by open drain, open collector or contact switch.

• It is recommended to provide accessible test point directly connected to the RESET_N input pin.

SIM

• The external SIM interface is not supported by the SARA-R500E modules.

SIM interface
SARA-R5 series modules provide the VSIM, SIM_IO, SIM_CLK, SIM_RST pins as an interface to connect an external SIM card/chip. Both 1.8 V and 3.0 V SIM types are supported. Activation and deactivation with an automatic voltage switch from 1.8 V to 3.0 V is implemented according to the ISO-IEC 7816-3 specifications.

SIM detection
The GPIO5 pin of SARA-R5 series modules is a 1.8 V digital input which can be configured as an external interrupt to detect the SIM card presence (as a feature which can be optionally used), as intended to be properly connected to the mechanical switch of an external SIM card holder. For more details, see the SARA-R5 series system integration manual [2] and the SARA-R5 series AT commands manual [1].

Serial communication
The SARA-R5 series provides the following serial communication interfaces:

• UART interfaces, available for communications with host application processor (2.5.1)
• USB 2.0 compliant interface, available for diagnostics only (2.5.2)
• SPI interfaces, available for communications with external SPI devices and for diagnostic (2.5.3)
• SDIO interface, available for communications with external SDIO devices (2.5.4)
• I2C bus compatible interface, available for communications with external I2C devices (2.5.5)

UART interfaces
The SARA-R5 series modules include 1.8 V unbalanced asynchronous serial interfaces (UART) for communication with external application host processor(s). UART can be configured by a dedicated AT command in the following variants:

• Variant 0 (default configuration), consists of a single UART interface that supports AT commands, data communication, multiplexer protocol functionality, FW update using FOAT or using the u-blox EasyFlash tool, and provides the following lines:
  • data lines (RXD as output, TXD as input),
  • hardware flow control lines (CTS as output, RTS as input),
  • modem status and control lines (DTR as input, RI as output)
• Variant 1, consists of a single UART interface that supports AT commands, data communication, multiplexer protocol functionality, FW update using FOAT or using the u-blox EasyFlash tool, and provides the following lines:
  • data lines (RXD as output, TXD as input),
  • hardware flow control lines (CTS as output, RTS as input),
  • modem status and control lines (DTR as input, DSR as output, DCD as output, RI as output)
• Variants 2, 3 and 4, consists of two UART interfaces plus ring indicator function:
  • First primary UART interface supports AT commands, data communication, multiplexer protocol functionality, FW update using FOAT or using the u-blox EasyFlash tool, and provides the following lines:
• data lines (RXD as output, TXD as input),
• hardware flow control lines (CTS as output, RTS as input),
• Second auxiliary UART interface supports AT commands (variant 2 only), data communication (variant 2 only), FW update using FOAT (variant 2 only), diagnostic trace logging (variant 3 only), and GNSS tunnelling (variant 4 only), and provides the following lines:
  • data lines (DCD as data output, DTR as data input),
  • hardware flow control lines (RI as flow control output, DSR as flow control input),
  • Ring indicator function over the GPIO pin configured with RI function (see section 2.7)

UART general features, valid for all variants, are:

• Serial port with RS-232 functionality conforming to the ITU-T V.24 recommendation [8], with CMOS compatible levels (0 V for low data bit or ON state, and 1.8 V for high data bit or OFF state)
• Hardware flow control (default value) or none flow control is supported
• UART power saving indication available on the hardware flow control output, if hardware flow control is enabled: the line is driven to the OFF state when the module is not prepared to accept data by the UART interface
• One-shot autobauding is supported and it is enabled by default: automatic baud rate detection is performed only once, at module start-up. After the detection, the module works at the fixed baud rate (the detected one) and the baud rate can only be changed via AT command (see SARA-R5 series AT commands manual [1])
• The following baud rates are supported and can be auto-detected: 9600 bit/s, 19200 bit/s, 38400 bit/s, 57600 bit/s, 115200 bit/s, 230400 bit/s, 460800 bit/s, 921600 bit/s
• The following baud rates are supported but cannot be auto-detected: 3000000 bit/s, 3250000 bit/s
• The default frame format is 8N1 (8 data bits, no parity, 1 stop bit)
• Following frame formats are supported: 8N1 (8 data bits, no parity, 1 stop bit), 8N2 (8 data bits, no parity, 2 stop bit), 8E1 (8 data bits, even parity, 1 stop bit), 8O1 (8 data bits, odd parity, 1 stop bit), 7N1 (7 data bits, no parity, 1 stop bit), 7E1 (7 data bits, even parity, 1 stop bit), 7O1 (7 data bits, odd parity, 1 stop bit) The UART interfaces can be conveniently configured through AT commands. For more details, see the SARA-R5 series AT commands manual [1] and SARA-R5 series system integration manual [2].
• It is highly recommended to provide accessible test points directly connected to the TXD and RXD pins for FW upgrade purposes.
• It is recommended to provide accessible test points directly connected to the DCD and DTR pins for diagnostic purposes.

Multiplexer protocol
SARA-R5 series modules include multiplexer functionality as per 3GPP TS 27.010 [6] on the UART interface physical link. This is a data link protocol that uses HDLC-like framing and operates between the module (DCE) and the application processor (DTE), allowing several simultaneous sessions over the physical link (UART). When USIO variant 0 or 1 is set, the following virtual channels are defined:

• Channel 0: control channel
• Channel 1 – 3: AT commands/data communication
• Channel 4: GNSS tunnelling

When USIO variant 2 is set, AT commands and data communication are available on the second auxiliary UART and the following virtual channels are defined on the primary UART:

• Channel 0: control channel
• Channel 1 – 2: AT commands/data communication
• Channel 3: GNSS tunnelling

When USIO variant 3 is set, the diagnostic trace log is available on the second auxiliary UART and the following virtual channels are defined on the primary UART:

• Channel 0: control channel
• Channel 1 – 3: AT commands/data communication
• Channel 4: GNSS tunnelling

When USIO variant 4 is set, GNSS tunnelling is available on the second auxiliary UART, and the following virtual channels are defined on the primary UART:

• Channel 0: control channel
• Channel 1 – 3: AT commands/data communication

USB interface
SARA-R5 series modules include a high-speed USB 2.0 compliant interface with a maximum 480 Mbit/s data rate according to the USB 2.0 specification [9]. The module itself acts as a USB device and can be connected to any USB host equipped with compatible drivers. The USB interface is available for diagnostic purposes only. The USB_D+ / USB_D- lines carry the USB data and signaling, while the VUSB_DET pin represents the input to enable the USB interface by applying an external valid USB VBUS voltage (5.0 V typical).

It is highly recommended to provide accessible test points directly connected to the USB interface pins (VUSB_DET, USB_D+, USB_D-) for diagnostic purpose.

SPI interfaces

• The SPI interfaces are not supported by the “00B”, “01B”, “61B”, and “71B” product versions of SARA-R5 series modules, except for diagnostic purposes. SARA-R5 series modules include 1.8V Serial Peripheral Interfaces available for communications with external SPI target devices, or with the module acting as SPI controller, for diagnostic purposes.

SDIO interface

• The SDIO interface is not supported by the “00B”, “01B”, “61B”, and “71B” product versions of SARA-R5 series modules. SARA-R5 series modules include a 1.8V 4-bit Secure Digital Input Output interface over the SDIO_D0, SDIO_D1, SDIO_D2, SDIO_D3, SDIO_CLK and SDIO_CMD pins, with the module acting as an SDIO controller, available for communications with compatible external SDIO devices, and for diagnostic purpose.
• Accessible test points directly connected to the SDIO_D0, SDIO_D1, SDIO_D2 and SDIO_D3 pins may be provided for diagnostic purposes, alternatively to the highly recommended accessible test points provided on the USB interface pins.

I2C interface

• Communication with an external GNSS receiver is not supported by SARA-R510M8S modules. SARA-R5 series modules include a 1.8V I2C-bus compatible interface over the SDA and SCL pins, available to communicate with an external u-blox GNSS receiver and with external I2C devices as an audio codec: the SARA-R5 series module acts as an I2C controller that can communicate with I2C target devices per the I2C bus specifications [10].

Audio

• Audio is not supported by SARA-R5 series modules. SARA-R5 series modules include a 1.8V I2S digital audio interface over the I2S_TXD, I2S_RXD, I2S_CLK and I2S_WA pins, not supported by any product version.

ADC

• ADC is not supported by the “00B” product version of SARA-R5 series modules. SARA-R5 series modules include an Analog-to-Digital Converter input pin, ADC, configurable via a dedicated AT command (for further details, see the SARA-R5 series AT commands manual [1]).

GPIO
SARA-R5 series modules include pins that can be configured as general-purpose input/output or to provide custom functions as summarized in Table 4. For further details, see the SARA-R5 series system integration manual [2] and the SARA-R5 series AT commands manual [1], +UGPIOC, +UGPIOR, +UGPIOW AT commands).

Function| Description| Default GPIO| Configurable GPIOs
---|---|---|---
General purpose output| Output to set high or low digital level| –| GPIO1, GPIO2, GPIO3, GPIO4, GPIO5, GPIO6
General purpose input| Input to sense high or low digital level| –| GPIO1, GPIO2, GPIO3, GPIO4, GPIO5, GPIO6
Network status indication| Output indicating cellular network status: registered, data transmission, no service| –| GPIO1, GPIO2, GPIO3, GPIO4, GPIO5, GPIO6
External GNSS supply enable 7| Output to enable/disable the supply of an external u-blox GNSS receiver connected to the cellular module by the I2C interface| –| GPIO2 7
External GNSS data ready 7| Input to sense when an external u-blox GNSS receiver connected to the module is ready for sending data over the I2C interface| –| GPIO3 7
SIM card detection 8| Input for SIM card physical presence detection, to optionally enable / disable SIM interface upon detection of external SIM card physical insertion / removal| –| GPIO5 8
Module status indication| Output indicating module status: power-off or deep- sleep mode versus idle, active or connected mode| –| GPIO1, GPIO2, GPIO3, GPIO4, GPIO5, GPIO6
Module operating mode indication| Output indicating module operating mode: power-off, deep-sleep or idle mode versus active or connected mode| –| GPIO1, GPIO2, GPIO3, GPIO4, GPIO5, GPIO6
Ring indicator| Output providing events indicator| –| GPIO1, GPIO2, GPIO3, GPIO4, GPIO5, GPIO6
Last gasp| Input to trigger last gasp notification| –| GPIO1, GPIO2, GPIO3 9, GPIO4, GPIO6
Time pulse output| Output providing accurate time reference, as a sequence with configurable10 PPS or as single time pulse, based on the GNSS system or the LTE system (CellTime)| –| GPIO6
Time stamp of external interrupt input| Input triggering via interrupt the generation of an URC time stamp over AT serial interface| –| EXT_INT
Faster and safe power-off| Input to trigger a faster and safe shutdown of the module (as triggered by AT+CFUN=10 command)| –| GPIO1, GPIO2, GPIO3 9, GPIO4, GPIO6
External GNSS time pulse 7| Input to receive an accurate time reference, as a sequence with configurable10 PPS from an external GNSS system| –| SDIO_CMD 7
External GNSS time stamp of external interrupt 7| Output triggering via interrupt the generation of an URC time stamp from an external GNSS system| –| GPIO4 7
Pin disabled| Tri-state with an internal active pull-down enabled| GPIO1, GPIO2, GPIO3, GPIO4, GPIO5, GPIO6, EXT_INT, SDIO_CMD| GPIO1, GPIO2, GPIO3, GPIO4, GPIO5, GPIO6, EXT_INT, SDIO_CMD

Cellular antenna dynamic tuner interface
SARA-R5 series modules include two output pins (named I2S_TXD and I2S_WA) that can optionally be used to control in real time an external antenna tuning IC, as the two pins change their output value dynamically according to the specific current LTE band in use by the module (see Table 5).

Table 5: SARA-R5 series modules antenna dynamic tuning truth table

For design guidelines, see the SARA-R5 series system integration manual [2]. For details about how to enable the feature, see the SARA-R5 series AT commands manual [1], +UTEST=4 AT command.

GNSS peripheral outputs

• The GNSS peripheral output pins are not supported by SARA-R500E, SARA-R500S, SARA-R510S and SARA-R510M8S-00B product versions.

SARA-R510M8S modules provide the following 1.8 V peripheral output pins directly connected to the internal u-blox M8 GNSS chipset (as is illustrated in Figure 4):

• The ANT_ON output pin, over the I2S_RXD pin, can provide optional control for switching off power to an external active GNSS antenna or an external separate LNA. This facility is provided to help minimize power consumption in power save mode operation.
• The GEOFENCE output pin, over the I2S_CLK pin, can provide an optional indication of the geofencing status and can be used, for example, to wake up a host on activation.

Reserved pin (RSVD)
SARA-R5 series modules have a pin reserved for future use, marked as RSVD. This pin is to be left unconnected on the application board.

Pin definition

Pin assignment

No.| Name| Power domain| I/O| Description| Remarks
---|---|---|---|---|---
1| GND| –| N/A| Ground| All the GND pins must be connected to the ground.
2| RSVD| –| N/A| Reserved pin| Leave unconnected.
3| GND| –| N/A| Ground| All the GND pins must be connected to the ground.
4| V_INT| –| O| Generic Digital Interfaces supply output| V_INT is generated by the module when is switched on. See section 2.1.2 for functional description.

See section 4.2.3 for detailed electrical specs.

Provide test point for diagnostic purposes.

5| GND| –| N/A| Ground| All the GND pins must be connected to the ground.
6| DSR| GDI| O / I| UART data set ready /

AUX UART request to send

| Circuit 107 in ITU-T V.24 (DSR output, push-pull, idle high, active low), alternatively configurable as Second Auxiliary UART RTS (HW flow control input, idle high, active low, with internal active pull-up enabled).

See section 2.5.1 for a functional description.

See section 4.2.12 for detailed electrical specs.

No.| Name| Power domain| I/O| Description| Remarks
---|---|---|---|---|---
7| RI| GDI| O / O| UART ring indicator / AUX UART clear to send| Circuit 125 in ITU-T V.24 (RI output, push-pull, idle high, active low), alternatively configurable as Second Auxiliary UART CTS (HW flow control output, push-pull, idle high, active low).

See section 2.5.1 for functional description.

See section 4.2.12 for detailed electrical specs.

8| DCD| GDI| O / O| UART data carrier detect / AUX UART data output| Circuit 109 in ITU-T V.24 (DCD output, push-pull, idle high, active low), alternatively settable as Second Auxiliary UART RXD (data output, push-pull, idle high, active low). Fixed push-pull.

See section 2.5.1 for functional description.

See section 4.2.12 for detailed electrical specs. Provide test point for diagnostic purposes.

9| DTR| GDI| I / I| UART data terminal ready / AUX UART data input| Circuit 108/2 in ITU-T V. 24 (DTR input, idle high, active low, with internal active pull-up enabled), alternatively settable as Second Auxiliary UART TXD (data input, idle high, active low, with internal active pull-up enabled).

See section 2.5.1 for functional description. See section 4.2.12 for detailed electrical specs.

Provide test point for diagnostic purposes.

10| RTS| GDI| I| UART request to send| Circuit 105 in ITU-T V.24 (RTS flow control input, idle high, active low, with internal active pull-up enabled).

See section 2.5.1 for functional description.

See section 4.2.12 for detailed electrical specs.

11| CTS| GDI| O| UART clear to send| Circuit 106 in ITU-T V.24 (CTS hardware flow control output, push-pull, idle high, active low).

See section 2.5.1 for functional description.

See section 4.2.12 for detailed electrical specs.

12| TXD| GDI| I| UART data input| Circuit 103 in ITU-T V.24 (TxD data input, idle high, active low, with internal active pull-up enabled).

See section 2.5.1 for functional description.

See section 4.2.12 for detailed electrical specs. Provide test point for FW update purposes.

13| RXD| GDI| O| UART data output| Circuit 104 in ITU-T V.24 (RxD data output, push-pull, idle high, active low).

See section 2.5.1 for functional description. See section 4.2.12 for detailed electrical specs.

Provide test point for FW update purposes.

14| GND| –| N/A| Ground| All the GND pins must be connected to ground.
15| PWR_ON| POS| I| Power-on input| Internal active pull-up. Active low.

See section 2.3.1 and 2.3.2 for functional description. See section 4.2.9 for detailed electrical specs.

Provide test point for diagnostic purposes.

16| GPIO1| GDI| I/O| GPIO| Configurable GPIO. Push-pull output type. See section 2.8 for functional description.

See section 4.2.12 for detailed electrical specs.

17| VUSB_DET| USB| I| USB detect input| Input for VBUS (5 V typical) USB supply sense.

USB interface supported for diagnostic purpose only. See section 2.5.2 for functional description.

See section 4.2.15 for detailed electrical specs.

Provide test point for diagnostic purposes.

18| RESET_N| GDI| I| External reset input| Internal active pull-up. Active low.

See section 2.3.3 for functional description. See section 4.2.10 for detailed electrical specs.

Provide test point for diagnostic purposes.

No.| Name| Power domain| I/O| Description| Remarks
---|---|---|---|---|---
19| GPIO6| GDI| I/O / O| GPIO /

Time pulse output

| Configurable GPIO, alternatively configurable as accurate time reference output. Push-pull output type.
 |  |  |  |  | See section 2.8 for functional description.
 |  |  |  |  | See section 4.2.12 for detailed electrical specs.
20| GND| –| N/A| Ground| All the GND pins must be connected to ground.
21| GND 11| –| N/A| Ground| All the GND pins must be connected to ground.
 | ADC 12| ADC| I| ADC input| 12-bit Analog to Digital Converter input.

This pin can be externally connected to GND, if the ADC function is not needed in the application.

 |  |  |  |  | See section 4.2.16 for detailed electrical characteristics.
22| GND| –| N/A| Ground| All the GND pins must be connected to ground.
23| GPIO2| GDI| I/O| GPIO| Configurable GPIO. Push-pull output type.
 |  |  |  |  | See section 2.8 for functional description.
 |  |  |  |  | See section 4.2.12 for detailed electrical specs.
24| GPIO3| GDI| I/O| GPIO| Configurable GPIO. Push-pull output type.
 |  |  |  |  | See section 2.8 for functional description.
 |  |  |  |  | See section 4.2.12 for detailed electrical specs.
25| GPIO4| GDI| I/O / O| GPIO /

External GNSS time stamp

of external interrupt 13

| Configurable GPIO, alternatively configurable as output indicating the generation of an URC time stamp. Push-pull

output type.

 |  |  |  |  | See section 2.8 for functional description.
 |  |  |  |  | See section 4.2.12 for detailed electrical specs.
26| SDA| I2C| I/O| I2C bus data line| Open drain output type.
 |  |  |  |  | Internal active pull-up. Idle high, active low.
 |  |  |  |  | See section 2.5.5 for functional description.
 |  |  |  |  | See section 4.2.14 for detailed electrical specs.
27| SCL| I2C| O| I2C bus clock line| Open drain output type.
 |  |  |  |  | Internal active pull-up. Idle high, active low.
 |  |  |  |  | See section 2.5.5 for functional description.
 |  |  |  |  | See section 4.2.14 for detailed electrical specs.
28| USB_D-| USB| I/O| USB Data Line D-| 90 W nominal differential impedance.
 |  |  |  |  | Pull-up, pull-down and series resistors, as required by the USB 2.0 specifications [9], are part of the USB pin driver and shall not be provided externally.
 |  |  |  |  | USB interface supported for diagnostic purpose only.
 |  |  |  |  | See section 2.5.2 for functional description.
 |  |  |  |  | See section 4.2.15 for detailed electrical specs.
 |  |  |  |  | Provide test point for diagnostic purposes.
29| USB_D+| USB| I/O| USB Data Line D+| 90 W nominal differential impedance.
 |  |  |  |  | Pull-up, pull-down and series resistors, as required by USB

2.0 specifications [9], are part of the USB pin driver and

shall not be provided externally.

 |  |  |  |  | USB interface supported for diagnostic purpose only.
 |  |  |  |  | See section 2.5.2 for functional description.
 |  |  |  |  | See section 4.2.15 for detailed electrical specs.
 |  |  |  |  | Provide test point for diagnostic purposes.
30| GND| –| N/A| Ground| All the GND pins must be connected to ground.
No.| Name| Power domain| I/O| Description| Remarks
---|---|---|---|---|---
31| ANT_GNSS14| –| I| GNSS antenna| RF input for GNSS Rx antenna.
 |  |  |  |  | 50 Ω nominal impedance.
 |  |  |  |  | See section 2.2.2 and Table 2 for functional description.
32| GND| –| N/A| Ground| All the GND pins must be connected to ground.
33| EXT_INT| GDI| I| External interrupt| Configurable as interrupt input triggering the generation
 |  |  |  |  | of an URC time stamp. Internal active pull-down enabled.
 |  |  |  |  | See section 2.8 for functional description.
 |  |  |  |  | See section 4.2.12 for detailed electrical specs.
34| I2S_WA| GDI| O /| I2S word alignment /| I2S not supported by “00B”, “01B”, “61B”, “71B” versions.
 |  |  | O| Pin for antenna

dynamic tuning

| Configurable as pin for antenna dynamic tuning. Push-pull output type.
 |  |  |  |  | See section 2.7 / 2.9 for functional description.
 |  |  |  |  | See section 4.2.12 for detailed electrical specs.
35| I2S_TXD| GDI| O /| I2S transmit data /| I2S not supported by “00B”, “01B”, “61B”, “71B” versions.
 |  |  | O| Pin for antenna

dynamic tuning

| Configurable as pin for antenna dynamic tuning. Push-pull output type.
 |  |  |  |  | See section 2.7 / 2.9 for functional description.
 |  |  |  |  | See section 4.2.12 for detailed electrical specs.
36| I2S_CLK| GDI| O| I2S clock| I2S not supported by “00B”, “01B”, “61B”, “71B” versions.
 | GEOFENCE15| GNSS| O| Geofencing status| Configurable to provide optional indication of the
 |  |  |  | indication| geofencing status.
 |  |  |  |  | See section 4.2.13 for detailed electrical specs.
37| I2S_RXD| GDI| I| I2S receive data| I2S not supported by “00B”, “01B”, “61B”, “71B” versions.
 | ANT_ON15| GNSS| O| Antenna or LNA enable| External GNSS active antenna and/or LNA on/off signal
 |  |  |  |  | driven by u-blox M8 chipset, connected to internal LNA.
 |  |  |  |  | See section 4.2.13 for detailed electrical specs.
38| SIM_CLK| SIM| O| SIM clock| External SIM not supported by SARA-R500E modules.
 |  |  |  |  | See section 2.4.1 for functional description.
 |  |  |  |  | See section 4.2.11 for detailed electrical specs.
39| SIM_IO| SIM| I/O| SIM data| External SIM not supported by SARA-R500E modules.
 |  |  |  |  | See section 2.4.1 for functional description.
 |  |  |  |  | See section 4.2.11 for detailed electrical specs.
40| SIM_RST| SIM| O| SIM reset| External SIM not supported by SARA-R500E modules.
 |  |  |  |  | See section 2.4.1 for functional description.
 |  |  |  |  | See section 4.2.11 for detailed electrical specs.
41| VSIM| –| O| SIM supply output| External SIM not supported by SARA-R500E modules.
 |  |  |  |  | See section 2.4.1 for functional description.
 |  |  |  |  | See section 4.2.11 for detailed electrical specs.
42| GPIO5| GDI| I/O /| GPIO /| Configurable GPIO, alternatively configurable as input pin
 |  |  | I| SIM card detection 16| for SIM card detection. Push-pull output type.
 |  |  |  |  | See sections 2.4.2 and 2.8 for functional description.
 |  |  |  |  | See section 4.2.12 for detailed electrical specs.
43| GND| –| N/A| Ground| All the GND pins must be connected to ground.
44| SDIO_D2| GDI| I/O /| SDIO serial data [2] /| SDIO not supported by “00B”, “01B”, “61B”, “71B” versions
 |  |  | O| SPI_CLK| The pin is alternatively configurable as SPI_CLK, for
 |  |  |  |  | diagnostic purpose only. Push-pull output type.
45| SDIO_CLK| GDI| O| SDIO serial clock| SDIO not supported by “00B”, “01B”, “61B”, “71B” versions

• Not supported by SARA-R500S and SARA-R510S modules
• Not supported by “00B” products versions
• Not supported by SARA-R500E modules

No.| Name| Power domain| I/O| Description| Remarks
---|---|---|---|---|---
46| SDIO_CMD| GDI| I/O / I| SDIO command /

External GNSS time pulse input 17

| SDIO not supported by “00B”, “01B”, “61B”, and “71B” versions Configurable as input for external GNSS time pulse.

Push-pull output type.

See section 2.8 for a functional description.

See section 4.2.12 for detailed electrical specs.

47| SDIO_D0| GDI| I/O / O| SDIO serial data [0] / SPI_MOSI| SDIO not supported by “00B”, “01B”, “61B”, “71B” versions The pin is alternatively configurable as SPI_MOSI, for diagnostic purposes only. Push-pull output type.
48| SDIO_D3| GDI| I/O / O| SDIO serial data [3] / SPI_CS| SDIO not supported by “00B”, “01B”, “61B”, “71B” versions The pin is alternatively configurable as SPI_CS, for diagnostic purposes only. Push-pull output type.
49| SDIO_D1| GDI| I/O / I| SDIO serial data [1] / SPI_MISO| SDIO not supported by “00B”, “01B”, “61B”, “71B” versions The pin is alternatively configurable as SPI_MISO, for diagnostic purpose only.
50| GND| –| N/A| Ground| All the GND pins must be connected to ground.
51| VCC| –| I| Module supply input| All VCC pins must be connected to external supply. See section 2.1.1 for functional description.

See section 4.2.3 for detailed electrical specs.

52| VCC| –| I| Module supply input| All VCC pins must be connected to external supply. See section 2.1.1 for functional description.

See section 4.2.3 for detailed electrical specs.

53| VCC| –| I| Module supply input| All VCC pins must be connected to external supply. See section 2.1.1 for functional description.

See section 4.2.3 for detailed electrical specs.

54| GND| –| N/A| Ground| All the GND pins must be connected to ground.
55| GND| –| N/A| Ground| All the GND pins must be connected to ground.
56| ANT| –| I/O| Cellular antenna| RF input/output for Cellular Rx/Tx antenna. 50 W nominal impedance.

See section 2.2.1 and 4.2.6 for details.

57| GND| –| N/A| Ground| All the GND pins must be connected to ground.
58| GND| –| N/A| Ground| All the GND pins must be connected to ground.
59| GND| –| N/A| Ground| All the GND pins must be connected to ground.
60| GND| –| N/A| Ground| All the GND pins must be connected to the ground.
61| GND| –| N/A| Ground| All the GND pins must be connected to the ground.
62| ANT_DET| ADC| I| Antenna detection| Antenna presence detection function. See section 2.2.3 for details.

See section 4.2.7 for detailed electrical specs.

63| GND| –| N/A| Ground| All the GND pins must be connected to ground.
64| GND| –| N/A| Ground| All the GND pins must be connected to ground.
65-96| GND| –| N/A| Ground| All the GND pins must be connected to ground.

• For more information about pin-out, see the u-blox SARA-R5 series system integration manual [2].
• See appendix A for an explanation of the abbreviations and terms used.

Electrical specifications

Stressing the device above one or more of the ratings listed in the Absolute Maximum Rating section may cause permanent damage. These are stress ratings only. Operating the module at these or at any conditions other than those specified in the Operating Conditions sections (section 4.2) of the specification should be avoided. Exposure to Absolute Maximum Rating conditions for extended periods may affect device reliability.

• Electrical characteristics are defined according to the verification on a representative number of samples or according to the simulation.
• Where application information is given, it is advisory only and does not form part of the specification.

Absolute maximum rating

• The limiting values given below are per Absolute Maximum Rating System (IEC 134).

The product is not protected against overvoltage or reversed voltages. If necessary, voltage spikes exceeding the voltage specifications given in the table above, must be limited to values within the specified boundaries by using appropriate protection devices.

Maximum ESD

JS-001-2017
 |  | 500| V| Charged Device Model according to JS-002-2018

• LTRX cellular modules are electrostatic-sensitive devices and require special precautions when handling. See section 7.3 for ESD handling instructions.

Operating conditions

• Unless otherwise indicated, all operating condition specifications are at an ambient temperature of +25 °C.
• Operation beyond the operating conditions is not recommended and extended exposure beyond them may affect device reliability.

Operating temperature range

specifications
Extended operating temperature| -40|  | +85| °C| Operating with a possible slight deviation in RF performance outside the normal operating range

Thermal parameters

Symbol| Parameter| Min.| Typ.| Max.| Unit| Remarks
---|---|---|---|---|---|---
ΨM-A| Module-to-Ambient thermal parameter|  | 10|  | °C/W| Thermal characterization parameter ΨM-A = (TM – TA) / PH proportional to the delta between internal module temperature (TM) and ambient temperature (TA), due to heat power dissipation (PH), with the module mounted on a 79 x 62 x 1.41 mm 4-Layer PCB with a high coverage of copper, in still air conditions
ΨM-C| Module-to-Case thermal parameter|  | 2|  | °C/W| Thermal characterization parameter ΨM-C =(TM – TC) / PH proportional to the delta between internal module temperature (TM) and ambient temperature (TC), due to heat power dissipation (PH),

with the module mounted on a 79 x 62 x 1.41 mm 4-Layer PCB with a high coverage of copper, with a robust aluminium heat-sink and with forced air ventilation, i.e. reducing to a value close to 0 °C/W the thermal resistance from the case of the module to the ambient

Table 10: Thermal characterization parameters of the module

Supply/power pins

Table 11: Input characteristics of the Supply/Power pins

Table 12: Output characteristics of the Supply/Power pins

1. Operating within 3GPP / ETSI specifications.
2. Operating with possible slight deviation in RF performance outside normal operating range. The input voltage has to be above the extended operating range minimum limit to switch-on the module and to avoid possible switch-off of the module.
3. Typical values with matched antenna, VCC = 3.8 V

Current consumption

Mode| Condition| Tx power| Module| Min| Typ 20| Max| Unit
---|---|---|---|---|---|---|---
Power-off mode| Average current value (power-off mode)| —| SARA-R510S|  | 0.5| | µA
 |  | SARA-R500E SARA-R500S SARA-R510M8S|  | 62|  | µA
PSM deep-sleep mode| Average current value (PSM deep-sleep mode)| —| SARA- R510S|  | 0.5|  | µA
 |  | SARA-R500E SARA-R500S SARA-R510M8S|  | 62|  | µA
Cyclic deep-sleep / active mode (+UPSV: 1)| Average current value (eDRX deep- sleep mode21 rock bottom floor current)| —| SARA-R510S|  | 0.5|  | µA
 | SARA-R500E SARA-R500S SARA-R510M8S|  | 62|  | µA
 | Average current value

(DRX = 2.56 s, PTW = 20.48 s, eDRX = 655.36 s, +UPSMVER: 822)

| —| SARA-R510S|  | 180|  | µA
 | SARA-R500E SARA-R500S SARA-R510M8S|  | 250|  | µA
Cyclic idle / active mode (+UPSV: 1)| Average current value (low power idle mode

rock bottom floor current)

| —| All|  | 0.723|  | mA
 | Average current value

(DRX = 2.56 s, PTW = 20.48 s, eDRX = 655.36 s, +UPSMVER: 0)

| —| All|  | 0.723|  | mA
 | Average current value (DRX = 2.56 s, no eDRX)| —| All|  | 1.123|  | mA
 | Average current value (DRX = 1.28 s, no eDRX)| —| All|  | 1.523|  | mA
Idle mode (+UPSV: 1)| Average current value (airplane mode, +CFUN: 0)| —| All| | 0.723|  | mA
Active mode (+UPSV: 0)| Average current value (DRX = 1.28 s)| —| All|  | 25| | mA
LTE Cat M1

connected mode

| Average current value (Tx / Rx data transfer)| Minimum| All|  | 95|  | mA
0 dBm| All|  | 100|  | mA
 |  | 8 dBm| All|  | 115|  | mA
 |  | 14 dBm| All|  | 140|  | mA
 |  | 20 dBm| All|  | 170|  | mA
 |  | Maximum| All|  | 195|  | mA
 | Maximum current value (during Tx only)| Maximum| All|  | 395|  | mA
LTE Cat NB2

connected mode

| Average current value (Tx / Rx data transfer)| Minimum| All|  | 85|  | mA
0 dBm| All|  | 90|  | mA
 |  | 8 dBm| All|  | 100|  | mA
 |  | 14 dBm| All|  | 110|  | mA
 |  | 20 dBm| All|  | 125|  | mA
 |  | Maximum| All|  | 135|  | mA
 | Maximum current value (during Tx only)| Maximum| All|  | 395|  | mA
Mode / Condition| Min| Typ 24| Max| Unit
---|---|---|---|---
Average current value with power saving enabled (+UPSV: 1),

UBX-R5 in PSM, UBX-M8 in cyclic tracking mode with 1 s update period (GPS)

|  | 13|  | mA
Average current value with power saving enabled (+UPSV: 1),

UBX-R5 in PSM, UBX-M8 in cyclic tracking mode with 1 s update period (GPS & GLONASS)

|  | 14|  | mA
Average current value with power saving enabled (+UPSV: 1),

UBX-R5 in PSM, UBX-M8 in continuous tracking mode (GPS & GLONASS)

|  | 41|  | mA
Average current value with power saving enabled (+UPSV: 1),

UBX-R5 in DRX = 1.28 s, UBX-M8 in cyclic tracking mode with 1 s update period (GPS)

|  | 14|  | mA
Average current value with power saving enabled (+UPSV: 1),

UBX-R5 in DRX = 1.28 s, UBX-M8 in cyclic tracking mode with 1 s update period (GPS & GLONASS)

|  | 15|  | mA
Average current value with power saving enabled (+UPSV: 1),

UBX-R5 in DRX = 1.28 s, UBX-M8 in continuous tracking mode (GPS & GLONASS)

|  | 42|  | mA
Average current value with power saving disabled (+UPSV: 0),

UBX-R5 in DRX = 1.28 s, UBX-M8 in continuous tracking mode (GPS & GLONASS)

|  | 64|  | mA
Average current value with power saving disabled (+UPSV: 0),

UBX-R5 in DRX = 1.28 s, UBX-M8 in acquisition mode (GPS & GLONASS)

|  | 72|  | mA
Peak current value with power saving disabled (+UPSV: 0),

UBX-R5 in DRX = 1.28 s, UBX-M8 in acquisition mode (GPS & GLONASS)

|  | 100|  | mA

Table 14: Indicative VCC current consumption of the SARA-R510M8S module with GNSS on

GNSS characteristics

Parameter| Condition| Value|  |  |  |
---|---|---|---|---|---|---
Receiver type|  | 72-channel u-blox M8 engine

GPS L1C/A, SBAS L1C/A, QZSS L1C/A, QZSS L1-SAIF,

GLONASS L1OF, BeiDou B1I, Galileo E1B/C

|
Operational limits25| Dynamics| ≤ 4 g|  |  |  |
 | Altitude| 50’000 m|  |  |  |
 | Velocity| 500 m/s|  |  |  |
Velocity accuracy26|  | 0.05 m/s|  |  |  |
Heading accuracy26|  | 0.3 degrees|  |  |  |
GNSS|  | GPS & GLONASS| GPS| GLONASS| BeiDou| Galileo
Horizontal position accuracy27|  | 2.5 m| 2.5 m| 4 m| 3 m| 3 m
Max navigation update rate|  | 10 Hz| 18 Hz| 18 Hz| 18 Hz| 18 Hz
Time-To-First-Fix28| Cold start| 26 s| 29 s| 30 s| 34 s| 45 s
 | Aided starts29| 2 s| 2 s| 2 s| 3 s| 7 s
Sensitivity| Tracking & Navigation| -167 dBm| -166 dBm| -166 dBm| -160 dBm| -159 dBm
 | Reacquisition| -160 dBm| -160 dBm| -156 dBm| -157 dBm| -153 dBm
 | Cold start| -148 dBm| -148 dBm| -145 dBm| -143 dBm| -138 dBm

Table 15: GNSS characteristics and performance of the SARA-R510M8S module

• Typical values with matched antenna, VCC = 3.8 V
• Assuming Airborne < 4 g platform
• 50% @ 30 m/s
• CEP, 50%, 24 hours static, -130 dBm, > 6 SVs
• All satellites at -130 dBm, except Galileo at -127 dBm
• Dependent on aiding data connection speed and latency
• Time pulse/time stamp is always generated by the UBX-R5 cellular chipset after the process of the GNSS time pulse signal.

LTE RF characteristics
The LTE Cat M1 / NB2 bands supported by SARA-R5 series modules are defined in Table 2, while the following Table 16 describes the frequency ranges for each LTE band as per 3GPP TS 36.521-1 [7].

Frequency range

FDD band 71 (600 MHz)

| Uplink| 663| 698| MHz| Module transmits
Downlink| 617| 652| MHz| Module receives
Frequency range

FDD band 12 (700 MHz)

| Uplink| 699| 716| MHz| Module transmits
Downlink| 729| 746| MHz| Module receives
Frequency range

FDD band 28 (700 MHz)

| Uplink| 703| 748| MHz| Module transmits
Downlink| 758| 803| MHz| Module receives
Frequency range

FDD band 85 (700 MHz)

| Uplink| 698| 716| MHz| Module transmits
Downlink| 728| 746| MHz| Module receives
Frequency range

FDD band 13 (750 MHz)

| Uplink| 777| 787| MHz| Module transmits
Downlink| 746| 756| MHz| Module receives
Frequency range

FDD band 20 (800 MHz)

| Uplink| 832| 862| MHz| Module transmits
Downlink| 791| 821| MHz| Module receives
Frequency range

FDD band 26 (850 MHz)

| Uplink| 814| 849| MHz| Module transmits
Downlink| 859| 894| MHz| Module receives
Frequency range

FDD band 18 (850 MHz)

| Uplink| 815| 830| MHz| Module transmits
Downlink| 860| 875| MHz| Module receives
Frequency range

FDD band 5 (850 MHz)

| Uplink| 824| 849| MHz| Module transmits
Downlink| 869| 894| MHz| Module receives
Frequency range

FDD band 19 (850 MHz)

| Uplink| 830| 845| MHz| Module transmits
Downlink| 875| 890| MHz| Module receives
Frequency range

FDD band 8 (900 MHz)

| Uplink| 880| 915| MHz| Module transmits
Downlink| 925| 960| MHz| Module receives
Frequency range

FDD band 4 (1700 MHz)

| Uplink| 1710| 1755| MHz| Module transmits
Downlink| 2110| 2155| MHz| Module receives
Frequency range

FDD band 66 (1700 MHz)

| Uplink| 1710| 1780| MHz| Module transmits
Downlink| 2110| 2200| MHz| Module receives
Frequency range

FDD band 3 (1800 MHz)

| Uplink| 1710| 1785| MHz| Module transmits
Downlink| 1805| 1880| MHz| Module receives
Frequency range

FDD band 2 (1900 MHz)

| Uplink| 1850| 1910| MHz| Module transmits
Downlink| 1930| 1990| MHz| Module receives
Frequency range

FDD band 25 (1900 MHz)

| Uplink| 1850| 1915| MHz| Module transmits
Downlink| 1930| 1995| MHz| Module receives
Frequency range

FDD band 1 (2100 MHz)

| Uplink| 1920| 1980| MHz| Module transmits
Downlink| 2110| 2170| MHz| Module receives

Table 16: LTE operating RF frequency bands

SARA-R5 series modules include a UE Power Class 3 LTE Cat M1 / NB2 transmitter (see Table 2) and an LTE receiver, with output power and characteristics according to 3GPP TS 36.521-1 [7].

• The “00B” product version of SARA-R5 series modules and SARA-R500E modules do not support the LTE NB-IoT Radio Access Technology.
• The “00B” product version of SARA-R5 series modules do not support LTE FDD bands 66, 71, 85.SARA-R5 series modules’ LTE receiver characteristics are compliant to 3GPP TS 36.521-1 [7], with LTE-conducted receiver sensitivity performance described in Table 17 and Table 18.

repetitions
Receiver input sensitivity Band 12 / 28 / 85 (700 MHz)|  | –108.0|  | dBm| Without repetitions
Receiver input sensitivity Band 13 (750 MHz)|  | –108.0|  | dBm| Without repetitions
Receiver input sensitivity Band 20 (800 MHz)|  | –108.0|  | dBm| Without repetitions
Receiver input sensitivity

Band 5 / 18 / 19 / 26 (850 MHz)

|  | –107.0|  | dBm| Without repetitions
Receiver input sensitivity Band 8 (900 MHz)|  | –107.0|  | dBm| Without repetitions
Receiver input sensitivity Band 3 (1800 MHz)|  | –107.0|  | dBm| Without repetitions
Receiver input sensitivity Band 2 / 25 (1900 MHz)|  | –107.0|  | dBm| Without repetitions
Receiver input sensitivity Band 1 / 4 / 66 (2100 MHz)|  | –107.0|  | dBm| Without repetitions
Condition: 50 W, throughput > 95%, QPSK modulation, other settings as per clause 7.3EA of 3GPP TS 36.521-1 [7]

Table 17: LTE Cat M1 receiver sensitivity performance

repetitions
Receiver input sensitivity Band 12 / 28 / 85 (700 MHz)|  | -116.0|  | dBm| Without repetitions
Receiver input sensitivity Band 13 (750 MHz)|  | -116.0|  | dBm| Without repetitions
Receiver input sensitivity Band 20 (800 MHz)|  | -115.5|  | dBm| Without repetitions
Receiver input sensitivity

Band 5 / 18 / 19 / 26 (850 MHz)

|  | -115.5|  | dBm| Without repetitions
Receiver input sensitivity Band 8 (900 MHz)|  | -115.0|  | dBm| Without repetitions
Receiver input sensitivity Band 3 (1800 MHz)|  | -114.0|  | dBm| Without repetitions
Receiver input sensitivity Band 2 / 25 (1900 MHz)|  | -115.0|  | dBm| Without repetitions
Receiver input sensitivity Band 1 / 4 / 66 (2100 MHz)|  | -115.0|  | dBm| Without repetitions
Condition: 50 W, throughput > 95%, other settings as per clause 7.3F of 3GPP TS 36.521-1 [7]

Condition: 50Ω, throughput > 95%, other settings as per clause 7.3F of 3GPP TS 36.521-1 [7]

Table 18: LTE Cat NB2 receiver sensitivity performance

ANT_DET pin

Pin Name| Parameter| Min.| Typ.| Max.| Unit| Remarks
---|---|---|---|---|---|---
ANT_DET| Output DC current pulse value|  | 3|  | µA|
 | Output DC current pulse time length|  | 20|  | ms|

Time pulse

100

| ns ns
 | LTE source| RMS 99%| 500

1

| ns

µs

Configurable31 period of time pulse|  | 0.5, 1.0, 2.0, 3.0 or 4.0| s

PWR_ON pin

Parameter| Module| Min.| Typical| Max.| Unit| Remarks
---|---|---|---|---|---|---
Low-level input| All| -0.3|  | 0.3| V|
Pull-up resistance| All|  | 10|  | kW| Integrated pull-up to internal rail
Low-level input current| All|  | -300|  | µA|
PWR_ON low time| SARA-R510S| 1|  | 2| s| Low time to trigger module switch-on from power-off mode
 |  | 1|  | 2| s| Low time to trigger module early wake-up from PSM / eDRX32 deep-sleep
 | SARA-R500E SARA-R500S SARA-R510M8S| 0.1|  | 2| s| Low time to trigger module switch-on from power-off mode
 | 0.1|  | 2| s| Low time to trigger module early wake-up from PSM / eDRX32 deep-sleep

The PWR_ON and RESET_N input lines have to be driven as described in Figure 6 to perform an abrupt emergency hardware shutdown of the SARA-R5 series modules:

• First, PWR_ON line has to be set to the LOW level
• Then, RESET_N line has to be set to the LOW level, keeping the PWR_ON line set to the LOW level
• Then, after at least 23 s (minimum) since the PWR_ON line has been set to the LOW level, the PWR_ON line has to be released to the HIGH level, keeping the RESET_N line set to the LOW level
• Then, after at least 1.5 s (minimum) since the PWR_ON line has been released to the HIGH level,  the RESET_N line has to be released to the HIGH level

1. The time pulse/time stamp is always generated by the UBX-R5 cellular chipset after the process of the GNSS time pulse signal.
2. Configurability not supported by “00B” products version; period is fixed to 1.0 s
3. eDRX deep-sleep is not supported by “00B” products version

RESET_N pin

SIM pins
The SIM pins are a dedicated interface to the external SIM card/chip. The electrical characteristics fulfill the regulatory specification requirements. The values in Table 23 are for information only.

1.8 V SIM type
 | 3.0|  | V| VSIM, with external 3.0 V SIM type
Low-level input| -0.3|  | 0.2VSIM| V|
High-level input| 0.6VSIM|  | VSIM+0.3| V|
Low-level output|  | 0.0|  | V|
High-level output|  | VSIM|  | V|
Internal pull-up resistor on SIM_IO|  | 4.7|  | kW| Internal pull-up to VSIM supply
Clock frequency on SIM_CLK|  | 3.13|  | MHz|

Generic Digital Interfaces pins

(V_INT)
Low-level input| -0.3|  | 0.5| V|
High-level input| 1.3|  | 2.1| V|
Low-level output|  | 0.0| 0.4| V|
High-level output| 1.4| 1.8|  | V|
Input leakage current|  |  | 1| µA| 0 V < VIN < 1.8 V
Output high driver strength| 3.28| 5.22| 7.92| mA| VOUT = 1.4
Output low driver strength| 3.02| 5.41| 8.63| mA| VOUT = 0.4
Pull-up input current| -18| -32| -56| µA|
Pull-down input current| 15| 30| 56| µA|

GNSS digital interfaces pins

I2C pins
I2C lines (SCL and SDA) are compliant to the I2C-bus standard mode specification. See the I2C-bus specification [10] for detailed electrical characteristics.

(V_INT)
Low-level input| -0.3|  | 0.5| V|
High-level input| 1.3|  | 2.1| V|
Low-level output|  | 0.0|  | V|
Pull-up input current|  | -450|  | µA|

USB pins
USB data lines (USB_D+ / USB_D–) are compliant with the USB 2.0 high-speed specification. See the Universal Serial Bus specification revision 2.0 [9] for detailed electrical characteristics. The values in Table 27 related to USB 2.0 high-speed physical layer specifications are for information only.

High speed disconnect detection threshold (input differential signal amplitude)| 525|  | 625| mV|
High-speed data signaling input common mode voltage range| –50|  | 500| mV|
High-speed idle output level| –10|  | 10| mV|
High-speed data signaling output high level| 360|  | 440| mV|
High-speed data signaling output low level| –10|  | 10| mV|
Chirp J level (output differential voltage)| 700|  | 1100| mV|
Chirp K level (output differential voltage)| –900|  | –500| mV|

ADC pin

Smart temperature supervisor

Table 29: Thresholds definition for the “Smart temperature supervisor” feature on the SARA-R5 series modules

• The sensor measures the board temperature inside the shield, which can differ from the ambient temperature.

Parameters for ATEX applications
This section provides useful parameters and information to integrate SARA-R5 series modules in applications intended for use in areas with potentially explosive atmospheres (ATEX), including:

• Total internal capacitance and inductance of the modules (see Table 30)
• Maximum RF output power at the antenna (ANT) pin of the modules (see Table 31)
  • For any device integrating the SARA-R5 series modules and intended for use in potentially explosive atmospheres, check the detailed requisites on the pertinent normative for the application, as for example the IEC 60079-0 [12], IEC 60079-11 [13], and IEC 60079-26 [14] standards. The requirements must be fulfilled according to the exact applicable standards.
  • The certification of the application device that integrates a SARA-R5 series module and the compliance of the application device with all the applicable certification schemes, directives and standards required for use in potentially explosive atmospheres are the sole responsibility of the application device manufacturer.

Table 30 describes the maximum total internal capacitance and the maximum total internal inductance, considering internal parts tolerance, of the SARA-R5 series modules.

Table 30: SARA-R5 series maximum total internal capacitance and maximum total internal inductance

Table 31 describes the maximum RF output power transmitted by SARA-R5 series modules from the antenna (ANT) pin as Power Class 3 User Equipment for the LTE bands.

• SARA-R5 series modules do not contain internal blocks that increase the input voltage (such as step-up, duplicators, or boosters) except for the antenna (ANT) pin, for which the maximum RF output power shown in Table 31.

Mechanical specifications

Parameter| Description| Typical|  | Tolerance|
---|---|---|---|---|---
A| Module height [mm]| 26.0| (1023.6 mil)| +0.20/-0.20| (+7.9/-7.9 mil)
B| Module width [mm]| 16.0| (629.9 mil)| +0.20/-0.20| (+7.9/-7.9 mil)
C| Module thickness [mm]| 2.2| (86.6 mil)| +0.25/-0.15| (+9.8/-5.9 mil)
D| Horizontal edge to lateral pin pitch [mm]| 2.0| (78.7 mil)| +0.20/-0.20| (+7.9/-7.9 mil)
E| Vertical edge to lateral pin pitch [mm]| 2.5| (98.4 mil)| +0.20/-0.20| (+7.9/-7.9 mil)
F| Edge to lateral pin pitch [mm]| 1.05| (41.3 mil)| +0.20/-0.20| (+7.9/-7.9 mil)
G| Lateral pin to pin pitch [mm]| 1.1| (43.3 mil)| +0.05/-0.05| (+2.0/-2.0 mil)
H1| Lateral pin height [mm]| 0.8| (31.5 mil)| +0.05/-0.05| (+2.0/-2.0 mil)
H2| Lateral pin close to ANT height [mm]| 0.9| (35.4 mil)| +0.05/-0.05| (+2.0/-2.0 mil)
I| Lateral pin width [mm]| 1.5| (59.1 mil)| +0.05/-0.05| (+2.0/-2.0 mil)
J1| Lateral pin to pin distance [mm]| 0.3| (11.8 mil)| +0.05/-0.05| (+2.0/-2.0 mil)
J2| Lateral pin to pin close to ANT distance [mm]| 0.2| (7.9 mil)| +0.05/-0.05| (+2.0/-2.0 mil)
K| Horizontal edge to central pin pitch [mm]| 2.75| (108.3 mil)| +0.20/-0.20| (+7.9/-7.9 mil)
L| Vertical edge to central pin pitch [mm]| 2.75| (108.3 mil)| +0.20/-0.20| (+7.9/-7.9 mil)
M1| Central pin to pin horizontal pitch [mm]| 1.8| (70.9 mil)| +0.05/-0.05| (+2.0/-2.0 mil)
M2| Central pin to pin horizontal pitch [mm]| 3.6| (141.7 mil)| +0.05/-0.05| (+2.0/-2.0 mil)
N| Central pin to pin vertical pitch [mm]| 2.1| (82.7 mil)| +0.05/-0.05| (+2.0/-2.0 mil)
O| Central pin height and width [mm]| 1.1| (43.3 mil)| +0.05/-0.05| (+2.0/-2.0 mil)
P| Horizontal edge to pin 1 indicator pitch [mm]| 0.9| (35.4 mil)| +0.20/-0.20| (+7.9/-7.9 mil)
Q| Vertical edge to pin 1 indicator pitch [mm]| 1.0| (39.4 mil)| +0.20/-0.20| (+7.9/-7.9 mil)
R| Pin 1 indicator height and width [mm]| 0.5| (19.7 mil)| +0.05/-0.05| (+2.0/-2.0 mil)
Weight| Module weight [g]| < 3|  |  |

Table 32 : SARA-R5 series dimensions

• Module height tolerance +/–0.20 mm may be exceeded close to the corners of the PCB due to the cutting process: in the worst cases, the height could be +0.40 mm longer than the typical value.
• For information regarding the Footprint and Paste Mask recommended for the application board integrating the cellular module, see the SARA-R5 series system integration manual [2].

Qualification and approvals

Reliability tests
Reliability tests for SARA-R5 series modules are executed according to u-blox qualification policy, based on AEC-Q104 standard.

Approvals
SARA-R500s modules comply with the Directive 2011/65/EU of the European Parliament and the Council on the Restriction of Use of certain Hazardous Substances in Electrical and Electronic Equipment (EU RoHS 2) and its amendment Directive (EU) 2015/863 (EU RoHS 3). SARA-R500s modules are RoHS 3 compliant. No natural rubbers, hygroscopic materials, or materials containing asbestos are employed. Table 33, Table 34 and Table 35 summarize the main approvals for the “00B” and “01B” product versions of SARA-R5 series modules .

• For guidelines and notices about compliance with certification approvals requirements integrating the SARA-R5 series modules in the end-device, see the SARA-R5 series system integration manual [2].
• For the complete list of approvals and for specific details on all country, conformance and network operators’ certifications available for all the different SARA-R5 series modules’ ordering numbers, including related certificates of compliancy, please contact your nearest u-blox office or sales representative. The certification approvals listed in Table 33, Table 34 and Table 35 might not be available for all the different product type numbers.

Important Compliance Information for North American Users
The SARA-R500S-01B has been granted modular approval for mobile applica-tions. Integrators may use the SARA-R500S-01B1 in their end products without additional FCC certification if they meet the following conditions. Otherwise, addi-tional FCC approvals must be obtained.

1. The end product must use the RF trace design approved with the SARA-R500S-01B.The Gerber file of the trace design can be obtained up-oddnform LANTRONIX request.
2. At least 20 cm separation distance between the antenna and the user’s body must be maintained at all times.
3. To comply with FCC regulations limiting both maximum RF output power and human exposure to RF radiation, the maximum antenna gain including cable loss in a mobile-only exposure condition must not exceed the limits stipulated in below

• 7.8 dBi in 700 MHz, i.e. LTE FDD-12 band
• 9.2 dBi in 750 MHz, i.e. LTE FDD-13 band
• 9.4 dBi in 850 MHz, i.e. LTE FDD-5 band
• 7.4 dBi in 850 MHz, i.e. LTE FDD-26 band
• 6.8 dBi in 1700 MHz, i.e. LTE FDD-4 band
• 10.3 dBi in 1900 MHz, i.e. LTE FDD-2 band
• 10 4 dBi in 1900 MHz ie LTE FDD-25 band

1. SARA-R500S-01B may transmit simultaneously with other collocated radio transmitters within a host device, provided the following conditions are met:
   • Each collocated radio transmitter has been certified by FCC for mobile application.
   • At least 20 cm separation distance between the antennas of the collocated transmitters and the user’s body must be maintained at all times.
2. A label must be affixed to the outside of the end product into which the SARA-R500S-01B is incorporated, with a statement similar to the follow-ing: This device contains FCC ID: R68FOX4M1BLE
3. A user manual with the end product must clearly indicate the operating requirements and conditions that must be observed to ensure compliance with current FCC RF exposure guidelines. The end product with an embedded SARA-R500S-01B may also need to pass the FCC Part 15 unintentional emission testing requirements and be properly authorized per FCC Part 15.

Note: If this module is intended for use in a portable device, you are responsible for separate approval to satisfy the SAR requirements of FCC Part 2.1093.

Important Compliance Information for the United States and Canada
RC7611(-1), upon commercial release, will have been granted modular approval for mobile applications. Integrators may use the SARA-R500S-01B in their final products with- out additional FCC/ISED (Industry Canada) certification if they meet the following con-ditions. Otherwise, additional FCC/ISED approvals must be obtained.

1. At least 20 cm separation distance between the antenna and the user’s body must be maintained at all times.
2. To comply with FCC/ISED regulations limiting both maximum RF output power and human exposure to RF radiation, the maximum antenna gain including cable loss in a mobile-only exposure condition must not exceed the limits
3. A label must be affixed to the outside of the end product into which SARA-R500S-01B module is incorporated, with a statement similar to the following:
   •  This device contains FCC ID: R68FOX4M1BLE Contains transmitter module ISED: 3867A-FOX4M1BLE
4. A user manual with the end product must clearly indicate the operating requirements and conditions that must be observed to ensure compliance with current FCC/ISED RF exposure guidelines.

The end product with an embedded RC7611-1 module may also need to pass the FCC Part 15 unintentional emission testing requirements and be properly authorized per FCC Part 15.

Note: If this module is intended for use in a portable device, you are responsible for separate approval to satisfy the SAR requirements of FCC Part 2.1093 and ISED RSS102.

Industry Canada Statement
This device complies with Industry Canada license-exempt RSS standard(s). Operation is subject to the following two conditions:

1. this device may not cause interference, and
2. this device must accept any interference, including interference that may cause undesired operation of the device.

This module is intended for OEM integrators. The OEM integrator is responsible for compliance to all the rules that apply to the product into which this certified RF module is integrated. Additional testing and certification may be necessary when multiple modules are used. This equipment complies with ISED RSS-102 radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with a minimum distance 20 cm between the radiator and your body.

Table 38 : SARA-R5 series tape dimensions (mm)

• 10 sprocket hole pitch cumulative tolerance ± 0.2 mm.
• Pocket position relative to the sprocket hole is measured as the true position of the pocket, not a pocket hole.
• A0 and B0 are calculated on a plane at a distance “R” above the bottom of the pocket.

Moisture sensitivity levels

• SARA-R5 series modules are moisture-sensitive devices (MSD) per the IPC/JEDEC specification.
  The Moisture Sensitivity Level (MSL) relates to the packaging and handling precautions required. SARA-R5 series modules are rated at MSL level 4. For more information regarding moisture sensitivity levels, labelling, storage and drying, see the u-blox package information user guide [3].
  ☞ For the MSL standard, see IPC/JEDEC J-STD-020 (can be downloaded from www.jedec.org).

Reflow soldering
Reflow profiles are to be selected according to u-blox recommendations (see the SARA-R5 series system integration manual [2]).

• Failure to observe these recommendations can result in severe damage to the device!

ESD precautions

• SARA-R5 series modules contain highly sensitive electronic circuitry and are Electrostatic Sensitive Devices (ESD). Handling SARA-R5 series modules without proper ESD protection may destroy or damage them permanently. SARA-R5 series modules are Electrostatic Sensitive Devices (EDS) and require special ESD precautions typically applied to ESD-sensitive components. Table 8 details the maximum ESD ratings of the SARA-R5 series modules. Proper ESD handling and packaging procedures must be applied throughout the processing, handling and operation of any application that incorporates SARA-R5 series modules. ESD precautions should be appropriately implemented on the application board where the module is mounted, as described in the SARA-R5 series system integration manual [2].
•  Failure to observe these precautions can result in severe damage to the device!

References

• Home | JEDEC
• Home | JEDEC
• Home | u-blox

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>