Sierra Wireless RED Open-Source Hardware Development Platform User Manual mangOH Red Developer s Guide
Sierra Wireless Inc. Open-Source Hardware Development Platform mangOH Red Developer s Guide
41110401 mangOH Red Developers Guide r4
mangOH™ Red Developer’s Guide 41110401 Rev 4 mangOH Red Developer’s Guide Important Notice Safety and Hazards Due to the nature of wireless communications, transmission and reception of data can never be guaranteed. Data may be delayed, corrupted (i.e., have errors) or be totally lost. Although significant delays or losses of data are rare when wireless devices such as the Sierra Wireless modem are used in a normal manner with a well-constructed network, the Sierra Wireless modem should not be used in situations where failure to transmit or receive data could result in damage of any kind to the user or any other party, including but not limited to personal injury, death, or loss of property. Sierra Wireless accepts no responsibility for damages of any kind resulting from delays or errors in data transmitted or received using the Sierra Wireless modem, or for failure of the Sierra Wireless modem to transmit or receive such data. Do not operate the Sierra Wireless modem in areas where blasting is in progress, where explosive atmospheres may be present, near medical equipment, near life support equipment, or any equipment which may be susceptible to any form of radio interference. In such areas, the Sierra Wireless modem MUST BE POWERED OFF. The Sierra Wireless modem can transmit signals that could interfere with this equipment. Do not operate the Sierra Wireless modem in any aircraft, whether the aircraft is on the ground or in flight. In aircraft, the Sierra Wireless modem MUST BE POWERED OFF. When operating, the Sierra Wireless modem can transmit signals that could interfere with various onboard systems. Note: Some airlines may permit the use of cellular phones while the aircraft is on the ground and the door is open. Sierra Wireless modems may be used at this time. The driver or operator of any vehicle should not operate the Sierra Wireless modem while in control of a vehicle. Doing so will detract from the driver or operator's control and operation of that vehicle. In some states and provinces, operating such communications devices while in control of a vehicle is an offence. Limitation of Liability The information in this manual is subject to change without notice and does not represent a commitment on the part of Sierra Wireless. SIERRA WIRELESS AND ITS AFFILIATES SPECIFICALLY DISCLAIM LIABILITY FOR ANY AND ALL DIRECT, INDIRECT, SPECIAL, GENERAL, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES INCLUDING, BUT NOT LIMITED TO, LOSS OF PROFITS OR REVENUE OR ANTICIPATED PROFITS OR REVENUE ARISING OUT OF THE USE OR INABILITY TO USE ANY SIERRA WIRELESS PRODUCT, EVEN IF SIERRA WIRELESS AND/OR ITS AFFILIATES HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES OR THEY ARE FORESEEABLE OR FOR CLAIMS BY ANY THIRD PARTY. Notwithstanding the foregoing, in no event shall Sierra Wireless and/or its affiliates aggregate liability arising under or in connection with the Sierra Wireless product, regardless of the number of events, occurrences, or claims giving rise to liability, be in excess of the price paid by the purchaser for the Sierra Wireless product. Rev 4 May.18 41110401 Preface Patents This document contains information which is proprietary to Sierra Wireless Inc. and is licensed pursuant to Creative Commons Attribution 4.0 International License. Document details Title: mangOH Red Developer’s Guide Author: Sierra Wireless Source: https://mangoh.io Copyright © 2018 Sierra Wireless. Licensed under the Creative Commons Attribution 4.0 license, http://creativecommons.org/licenses/by/4.0/ Disclaimer Indicate any modifications made to the original document. Trademarks mangOH™ and the mangOH logo are trademarks of Sierra Wireless. Other trademarks are the property of their respective owners. Revision History Revision number Release date Changes May 2017 Document created June 2017 Updated image to DV3 board April 2018 Updated image to DV5 board Added Wi-Fi/BT RF specifications Added Regulatory chapter Minor corrections May 2018 Updated 2.5 Wi-Fi/BT Chipset—indicated supported RF Rev 4 May.18 41110401 Contents Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 mangOH Red Hardware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 mangOH Red Hardware Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 mangOH Red Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 MUXing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 CF3 Module Signals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 ADC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Audio (Analog and PCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 CF3 GPIOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 GPIO Expander . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 HSIC (USB/Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 I2C1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Light Sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Raspberry Pi Rev B-compatible Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 RF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 SDIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 SPI1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 UART1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 UART2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 UART Console Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 UIM Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 USB 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Wi-Fi/BT Chipset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Wi-Fi RF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Bluetooth RF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 IoT Connector Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Reset Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Power Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Rev 4 May.18 41110401 Contents Regulatory Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Important Compliance Information for North American Users . . . . . . . . . . . . . . . . . . . . . . 34 USA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Canada . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Rev 4 May.18 41110401 1: Introduction The mangOH Red open-source hardware development platform for CF3 modules incorporates several hardware interfaces and a standardized IoT Expansion Card slot for expanded functionality. This developer’s guide describes the mangOH Red’s architecture and provides details on how to develop applications for CF3 modules. For the full mangOH Red documentation suite, refer to mangoh.io/mangoh-red-resources. Rev 4 May.18 41110401 2: Hardware This chapter describes the mangOH Red platform’s hardware components and interfaces. 2.1 mangOH Red Hardware Overview Figure 2-1 provides an overview of the mangOH Red’s hardware components relative to the CF3 module, and Figure 2-2 on page 8 and Figure 2-3 on page 9 show their physical locations. For additional details, see the following documents: • Available at mangoh.io/mangoh-red-resources: • Available at source.sierrawireless.com: · mangOH Red User Guide—Instructions on setting up the hardware components Generic button Reset ESIM Power_ON SDIO microSD /uSIM Holder 3.7V @ 1000mA AirPrime Embedded Module Common Flexible Form Factor (CF3) Specification Diversity · GPS Sierra Wireless CF3 module-specific Product Technical Specification documents Main · LEDs Audio Wi-Fi + BT u.FL Integrated DNI uUSB Connector Wi-Fi/BT chipset Type A USB Connector CF3 Module uUSB Connector Real-time I/O IoT Connector Raspberry Pi Connector Gyroscope / Accelerometer Low Power I/O Pressure / Temperature Sensor Light Sensor Figure 2-1: mangOH Red Hardware Components Overview Rev 4 May.18 41110401 mangOH Red Developer’s Guide 1—Pluggable IoT connector (CN306 (IOT0)) 2—Power supply select (CN804) 3—Battery connector (CN802) 4—Signals control (SW401) 5—Main antenna (CN301) 6—GNSS antenna (CN303) 7—Diversity antenna (CN302) 8—Wi-Fi/Bluetooth antenna (ANT1000) 9—USB Host (CN304) 10—Audio (CN500) 11—µUSB Console connector (CN305) 12—Raspberry PI RevB-compatible header (CN307) 13—Generic button (SW200) 14—PWR_ON switch (SW402) 18 15—Reset switch (SW400) 16—CF3 module socket (J200) 17—Real Time I/O (CN310) 18—Low Power I/O (CN312) 15 10 11 13 16 14 17 12 Figure 2-2: mangOH Red—Top Side Switches/Connectors Note: For reference only. For latest schematic, visit mangoh.io/mangoh-red-resources-hardware. Rev 4 May.18 41110401 Hardware 1—µUSB CF3 connector (CN801) 2—micro-SIM (CN600, bottom slot) 3—microSD (CN600, top slot) 4—ESIM (U603 (DNI)) 5—Wi-Fi/BT chipset (U1000) 6—Integrated Wi-Fi/Bluetooth antenna (ANT1000) 7—Wi-Fi/Bluetooth antenna (CN1000 (DNI)) Figure 2-3: mangOH Red—Bottom Side Switches/Connectors Note: For reference only. For latest schematics, visit mangoh.io/mangoh-red-resources-hardware. Rev 4 May.18 41110401 mangOH Red Developer’s Guide 2.2 mangOH Red Hardware Architecture The mangOH Red platform provides several hardware components, including: • CF3 module socket • Wi-Fi/BT chipset (MediaTek Wi-Fi+Bluetooth) • Pluggable IoT Connector (socket for IoT Expansion Card) • Raspberry Pi Rev B-compatible 26-pin connector • Several I/O connectors (SIM, SD, Audio, USB, etc.) Figure 2-4 illustrates the mangOH Red’s hardware architecture (connectors and signals). The following sections describe these features in greater detail: • mangOH Red Hardware Components on page 12—Components available to the CF3 module and Wi-Fi/BT chipset. • CF3 Module Signals on page 17—CF3 module connections to hardware components. • Wi-Fi/BT Chipset on page 28—Wi-Fi/BT chipset connections to hardware components. • IoT Connector Interfaces on page 31—IoT Expansion Card signal connections to the hardware components. Rev 4 May.18 10 41110401 Rev 4 May.18 uUSB-1 Pressure / Temperature Sensor SX1509 GPIO Gyroscope / Accelerometer PSU 5V0 PSU 3V3 11 I2C I2C HUB I2C Audio MUX Iot con #0 4xGPIO Battery Charger PSU 1V8 Analog Codec Power Section Battery Gauge Battery Input switch uUSB-2 3.5mm Jack GPIO I2C1 USB 2.0 PCM MAIN USB to UART FTDI ADC0 PowerOn, Reset, Generic button Physical switches SPI1 MASTER DIV uSD HOLDER SDIO MUX SDIO GPS UART Mux UART2 SIM 1 SIM HOLDER #1 UART1 ESIM WiFi/BT SIM 2 UART1_TX (GPIO37) UART1_RX (GPIO36) UART1_CTS (GPIO39) UART1_RTS (GPIO38) Real Time IO UART2 UART1 SPI Wi-Fi/BT chipset HSIC Raspberry Ctrl Pi Signals GPIO ADC3 Light Sensor Default Hardware Configuration Level Shifter This section (Wi-Fi/BT UART1) is only available when an HL CF3 module is installed. u.FL (DNI) Integrated CN312 Low Power IO CF3 Smart Various signals Multi-function switch CN310 26 MHz XTAL SPI_MOSI (GPIO29) SPI_MRDY (GPIO32) SPI_CLK (GPIO27) SPI_MISO (GPIO30) HSIC USB TypeA USB DW USB3503 USB to SPI USB DW HSIC UP 26 pin Rpi USB DW Hardware Figure 2-4: mangOH Red Hardware Architecture (Default) 41110401 mangOH Red Developer’s Guide 2.2.1 mangOH Red Hardware Components Key mangOH Red hardware components and their connections to the CF3 module and/or Wi-Fi/BT chipset are listed in Table 2-1 on page 12. The mangOH Red’s default configuration enables specific interfaces when the platform boots. For interface details, see: • MUXing on page 17 • CF3 Module Signals on page 17 • Wi-Fi/BT Chipset on page 28 • IoT Connector Interfaces on page 31 • Reset Methods on page 32 • Power Management on page 32 Table 2-1: mangOH Red Hardware Components Type and Designator a Description Signals / Module Pins Notes Modules/Processors/etc. CF3 module (J200) For details, see CF3 Module Signals on page 17. IOT0 (CN306) IoT Expansion Card Wi-Fi/BT chipset (U1000) MediaTek Wi-Fi/ BT chipset with ARM Cortex-M4 application processor Connections to multiple CF3 module interfaces. For details, see IoT Expansion Card on page 15. For details, see Wi-Fi/BT Chipset on page 28. Card slots Micro-SIM (CN600) Micro-SIM/ microSD holder (bottom slot) CF3 UIM1 (Pins: 26–29) Purpose: UIM used to establish mobile network connection. For details, see UIM1 on page 27. micro-SD (CN600) Micro-SIM/ microSD holder (top slot) CF3 SDIO (Pins: 161–166) Purpose: Provide access to microSD card. For details, see: • SDIO on page 24 • MUXing on page 17 ESIM (U603) Embedded SIM Purpose: Built-in UIM used to establish mobile network connection. For details, see UIM2 on page 28. CF3 UIM2 (Pins 55–58) Note: eSIM is DNI. Rev 4 May.18 12 41110401 Hardware Table 2-1: mangOH Red Hardware Components (Continued) Type and Designator a Description Signals / Module Pins Notes USB (Pins: 12, 13, 16) Power (if selected) Purpose: • Direct connection to CF3 USB • Power supply when selected by the Power Supply Selection Jumper (CN804). See mangOH Red User Guide for details. For details, see USB 2.0 on page 28. UART2 (Pins: 96–99) Power (if selected) Purpose: • Console—Connects to CF3 module console or Wi-Fi/BT chipset console • Power supply when selected by the Power Supply Selection Jumper (CN804). See mangOH Red User Guide for details. For details, see UART2 on page 26. USB-type connectors micro-USB (CN801) CF3 USB micro-USB connector • • micro-USB (CN305) Console USB micro-USB connector • • USB Host (CN304) USB Type A connector HSIC (Pins: 14, 15) Purpose: Provides USB host capability to CF3 module. For details, see HSIC (USB/Ethernet) on page 20. RF Antennas Main (CN301) u.FL connectors GNSS (CN303) Diversity (CN302) CF3 RF (Pins: 49 (Main), 38 (GNSS), 31 (Diversity)) For details, see RF on page 24. Wi-Fi/Bluetooth Antennas (Integrated— ANT1000; u.FL—CN1000 (DNI)) Antenna Wi-Fi/BT chipset RF For details, see Wi-Fi/BT Chipset on page 28. Audio (CN500) 3.5 mm connector CF3 digital audio signals (Pins: 30–33) Purpose: Provide audio capability to CF3 module. For details, see: • Audio (Analog and PCM) on page 18 • MUXing on page 17 Raspberry Pi (CN307) 26-pin Rev B-compatib le connector • RF, Audio, Raspberry Pi connectors • CF3 HSIC signals (via SPI or USB (DNI)) Wi-Fi/BT chipset SPI For details, see Raspberry Pi Rev B-compatible Connector on page 22. Other ICs and components Gyroscope/ Accelerometer (U704) Rev 4 May.18 Integrated BMI160 inertial measurement module CF3 I2C1 interface 13 Purpose: Provides rotational, linear motion, and gravitational force measurements for use in (for example) gaming, mapping, navigation, and optical image stabilitization applications. For details, see I2C1 on page 21. 41110401 mangOH Red Developer’s Guide Table 2-1: mangOH Red Hardware Components (Continued) Type and Designator a Description Signals / Module Pins Notes CF3 I2C1 interface Purpose: Provides barometric pressure, altitude, and temperature measurements for use in (for example) GPS navigation, indoor/outdoor navigation, and weather forecasting applications. For details, see I2C1 on page 21. CF3 ADC3 Purpose: Provide ambient light measurements for use in (for example) brightness control systems. For details, see Raspberry Pi Rev B-compatible Connector on page 22. Integrated SX1509 expander CF3 I2C1 interface Purpose: Provides additional GPIOs. For details, see: • GPIO Expander on page 20 • I2C1 on page 21 6-pin header CF3 ADC1/ADC2 CF3 GPIOs (if resistors are populated) CF3 UIM2_DET Purpose: Connect low-power input sources to CF3 module. For details, see ADC on page 17. 6-pin header Wi-Fi/BT chipset userconfigurable multi-purpose pins (for ADC, GPIO, PWM, I2C, etc.) Purpose: Connect input sources to Wi-Fi/BT chipset for use by its real-time application processor. (Multi-purpose pin details forthcoming.) For details, see Wi-Fi/BT Chipset on page 28. IoT Expansion Card 0 (D401) Green LED GPIO expander I/O_8 via LED_CARD_DETECT_IOT0 Purpose: Indicates IoT Expansion Card is in slot IOT0. Rx/Tx (CF3 module) (D402) Green LED CF3 TX_ON Purpose: Indicates CF3 module is transmitting/ receiving. WLAN Connected (D200) Green LED CF3 WWAN_LED_N Purpose: Indicates device is connected to a WLAN (will be OFF when LowPower Mode is enabled). VCC_3V3 (D803) Green LED VCC_3V3 Purpose: Indicates device is powered on. Generic (userdefined) (D410) Green LED CF3 GPIO34 (via expander WP_GPIO_7_lvl) Purpose: User-defined (programmable) Pressure sensor/ Temperature sensor (U705) Integrated BMP280 barometric pressure sensor Light sensor (U706) Integrated PNJ4K01F ambient light sensor GPIO/PWM expander (U1004) Low Power I/O connector (CN312) Real-time I/O connector (CN310) LEDs Rev 4 May.18 14 41110401 Hardware Table 2-1: mangOH Red Hardware Components (Continued) Type and Designator a Description Signals / Module Pins Notes Platform controls Eight dipswitches: 1. PWR_ON Enable/disable CF3 module’s POWER_ON signal 2. WIFI_UART1_TX Enable (On)/disable (Off) firmware download (recovery mode) to the CF3 module. Similar functionality to TP1_BOOT. VCC_3V7_ULPM When device is in ULPM: • OFF—only the CF3 module is receiving power. • ON—the CF3 module + accessories receive power 4. HL_MODE Used with pin 8 (LowPower_RESET) to indicate whether in HL mode or WP mode • ON—HL mode • OFF—WP mode 5. BATT_TS+ Enable (On)/disable (off) battery charging 6. CONS_DIR Console USB connectors connects to: • OFF—CF3 module console • ON—Wi-Fi/BT chipset console Note: To download firmware to the: • CF3 module—Set CONS_DIR Off and TP1_BOOT On. • Wi-Fi/BT chipset—Set CONS_DIR On and WIFI_UART_TX On. 7. TP1_BOOT Enable (On)/disable (Off) CF3 module’s TP1 (boot) signal. LowPower_RESET Used with pin 4 (HL_MODE) to indicate whether in HL mode or WP mode • ON—WP mode • OFF—HL mode For details, see Power Management on page 32. 3. Multi-switch (SW401) Module signals control 8. a. Board designators (e.g. CN311, SW401, etc.) are for reference against the published mangOH Red schematic. For component locations on the board, see Figure 2-2 on page 8 and Figure 2-3 on page 9. 2.2.1.1 IoT Expansion Card mangOH Red includes one IoT Expansion Card slot (IOT0), which has an IoT Connector (CN306) that connects to the CF3’s signals as detailed in Table 2-2. This slot provides full support for the IoT Expansion Card specification. By default, specific signals are enabled when the mangOH Red boots. For additional information, including default configuration and how to temporarily change it, see IoT Connector Interfaces on page 31. Rev 4 May.18 15 41110401 mangOH Red Developer’s Guide For detailed specifications, see the Project mangOH IoT Expansion Card Design Specification available at mangoh.io/iot-card-resources-documentation. Table 2-2: IoT Expansion Card Signal Connections to CF3 Module IoT Signals CF3 Signal(s) Signal Path Notes USB HSIC (Pins 14, 15) Single Purpose: Data transfer; application control For details, see HSIC (USB/Ethernet) on page 20. UART UART1 (Pins 2, 9) MUX Purpose: Data transfer For details, see: • UART1 on page 25 • MUXing on page 17 SPI SPI1 (Pins 51–54) Yes Purpose: Data transfer For details, see: • SPI1 on page 25 • MUXing on page 17 I2C I2C1 (Pins 1, 66) Hub Purpose: Data transfer (standard mode). Higher speeds possible if supported by host application. For details, see I2C1 on page 21. GPIOs 1–4 GPIO (7, 8, 13, 42) Single SDIO SDIO (Pins 161–166) ADC0 ADC0 (Pin 25) Power Power PCM PCM RESET_IOT0 GPIO2 PPS DR_SYNC CARD_DETECT_IOT0 GPIO33 Rev 4 May.18 Yes Purpose: Customer-defined data communication For details, see CF3 GPIOs on page 18. Purpose: Data transfer For details, see: • SDIO on page 24 • MUXing on page 17 Purpose: General purpose ADC output to host application (e.g. indicate Single when a sensor has triggered) For details, see ADC on page 17. n/a Default configuration—Receives three power inputs: • 5.0V @ 500 mA • 3.3V @ 1 A • 1.8V @ 200 mA For details, see Power Management on page 32. Single Purpose: Digital audio interface Purpose: Data transfer For details, see CF3 GPIOs on page 18. Purpose: Clock signal used to manage timing for sensor nodes (or other devices) that are connected to the expansion card. The signal is a stratum 1 clock input from the host application, where the host application operates as a stratum 1 time source connected to GPS (a stratum 0 source). Purpose: Data transfer For details, see CF3 GPIOs on page 18. 16 41110401 Hardware 2.3 MUXing Several interfaces use MUXing (simple switches) to associate multiple hardware connectors with a single signal from the CF3 module, or multiple signals with a single hardware connector. The following sections describe these MUX implementations • • MUX · Audio (Analog and PCM) on page 18 · SDIO on page 24 · UART2 on page 26 Hubs · HSIC (USB/Ethernet) on page 20 · I2C1 on page 21 2.4 CF3 Module Signals This section describes how CF3 module signals connect to the platform hardware (described in mangOH Red Hardware Components on page 12). Important: CF3 module signal availability depends on the module type—some modules may not implement certain Extension signals from the CF3 specification. 2.4.1 ADC The mangOH Red supports four CF3 module ADC (Analog to Digital converter) signal sources (ADC0-ADC3). The ADC signals connect to the following sources, as shown in Figure 2-5: • ADC0—IoT Connector 0 (CN1000, slot IOT0), pin 20 • ADC1, ADC2—Low Power I/O (CN312), pins 4 and 5 • ADC3—Light sensor (U706), pin 6 ADC0 ADC1 CF3 ADC2 ADC3 ADC0 IoT Connector #0 (CN306, slot IOT0) Low Power I/O (CN312) Light sensor (U706) Figure 2-5: ADC Configuration Rev 4 May.18 17 41110401 mangOH Red Developer’s Guide 2.4.2 Audio (Analog and PCM) The mangOH Red supports the CF3 module PCM (digital) audio signals. The signals connect via a Mux (analog switch) to the following sources, as shown in Figure 2-6: • 3.5 mm analog audio jack (Default configuration) • IoT connector (Alternate configuration) The audio interface configuration can be modified as described in Table 2-3. Table 2-3: Audio Interface Configuration Changes Change type Hardware Change effect Mux—Use default or alternate configuration Method Change duration Populate/depopulate resistors on the Mux: • R508 pulls signal low (default configuration) • R520 pulls signal high (alternate configuration) Selected configuration used every time device boots up. Mux IoT Connector #0 (CN306, slot IOT0) CF3 PCM DigitalAnalog Codec 3.5mm Jack (CN500) Note: Default configuration — Solid lines Alternate configuration — Dashed lines Figure 2-6: Audio Configuration 2.4.3 CF3 GPIOs The mangOH Red supports several CF3 module GPIOs, as shown in Figure 2-7. Notes: • Six GPIOs connect to the IoT slot (for card detect, card reset, and four for use as GPIOs). • One GPIO (GPIO32) connects to the NINT (active low interrupt) output signal from a GPIO expander (U1004). Note: The mangOH Red uses a GPIO expander for additional I/O functions. See GPIO Expander on page 20. Rev 4 May.18 18 41110401 Hardware GPIO42 IOT0_GPIO1 GPIO13 IOT0_GPIO2 GPIO7 IOT0_GPIO3 IoT Connector #0 (CN306, slot IOT0) GPIO8 IOT0_GPIO4 GPIO33 CARD_DETECT_IOT0 GPIO2 RESET_IOT0 SW401 GPIO6 LowPower_RESET GPIO Expander (U1004) GPIO32 NINT Low Power I/O (CN312) GPIO36 WP_GPIO_5_wakeable Level Shifter (U306) CF3 GPIO22 WP_GPIO_1 WP_GPIO_1_lvl GPIO23 WP_GPIO_2 WP_GPIO_2_lvl GPIO24 WP_GPIO_3 WP_GPIO_3_lvl PWM_OUT PWM_OUT_3V3 GPIO35 WP_GPIO_8 WP_GPIO_8_lvl GPIO34 WP_GPIO_7 LED (D410) EXT_GPS_LNA_EN GPIO21 SPI2_SRDY _WIFI_1V8 SPI2_SRDY _WIFI_3V3 GPIO59 Wi-Fi module (U1000) Level Shifter (U307) GPIO25 RESET_WIFI_1V8 RESET_WIFI_3V3 Raspberry Pi Connector (CN307) SYS_RST_N Note: Default configuration — Solid lines Alternate configuration — Dashed lines Figure 2-7: GPIO Configuration Rev 4 May.18 19 41110401 mangOH Red Developer’s Guide 2.4.4 GPIO Expander The mangOH Red includes one SX1509 16-channel GPIO/PWM expander (U1004), as detailed in Table 2-4. The expander provides additional GPIOs (carried over the CF3 module’s I2C1 interface) that are used for internal I/O functions such as driving LEDs, resetting board components, etc. For detailed specifications, see the mangOH Red schematics at mangoh.io/mangoh-red-resources-hardware. Table 2-4: GPIO Expander (U1004) Signals Pin Signal Name Purpose I/O 0 BOARD_REV1 Reserved for future use. I/O 1 BOARD_REV2 Reserved for future use. I/O 2 BOARD_REV3 Reserved for future use. I/O 3 GPIO_EXP_RPI_1 Raspberry Pi connector, pin 16 I/O_4 GPIO_EXP_RPI_2 Raspberry Pi connector, pin 18 I/O_5 MTK_TO_WP_UART_EN Enable MTK recovery mode from WP (0), or connects CF3 UART1 to Wi-Fi/BT chipset UART0 (1) I/O_6 WIFI_UART1_TX Wi-Fi/BT chipset UART Tx—Normal (0), or MTK recovery mode (1) for firmware downloads/recovery (Note: DNI—R754 must be populated to access this signal.) I/O_7 GPIO_EXP_RPI_3 Raspberry PI connector, pin 22 I/O_8 LED_CARD_DETECT_IOT0 Indicates whether IoT expansion card is present I/O_9 SDIO_SEL Connect SD interface to IoT0 (0) or SD card (1) I/O_10 Power_Fail_Indicator Indicate power fail I/O_11 SENSOR_INT1 Accelerometer/gyroscope sensor interrupt I/O_12 SENSORT_INT2 Accelerometer/gyroscope sensor interrupt I/O_13 PCM_EXP1_SEL Connect PCM interface to IoT0 or to PCM codec (audio) I/O_14 Generic_Push_Button SW200 generic pushbutton I/O_15 CONS_DIR Use with MTK_TO_WP_UART_EN to choose UART source -- CF3 module or Wi-Fi/BT chipset 2.4.5 HSIC (USB/Ethernet) The mangOH Red supports CF3 module HSIC signals, which connect through a USB hub controller to the following sources, as shown in Figure 2-8: • SPI interface: · Wi-Fi/BT chipset (U1000) and Raspberry Pi Connector (CN307), via USB to SPI bridge (U1006). Note: The Wi-Fi/BT chipset uses SPI2_CS0, and Raspberry Pi connector uses SPI2_CS1/SPI2_CS2. Rev 4 May.18 20 41110401 Hardware • USB interface: · IoT Connector 0 (CN306) or (DNI) Raspberry Pi Connector (CN307) · USB Host connector (CN304) SPI USB DW CF3 HSIC HSIC Up USB3503 Hub (U701) USB to SPI bridge (U1006) SPI USB Wi-Fi/BT chipset (U1000) Raspberry Pi Connector (CN307) DNI USB DW USB USB DW IoT Connector #0 (CN306, slot IOT0) USB Host Type A Connector (CN304) Note: Default configuration — Solid lines Alternate configuration — Dashed lines Figure 2-8: HSIC Configuration 2.4.6 I2C1 The mangOH Red supports CF3 module I2C1 signals, which connect to the following sources (directly or via an expander), as shown in Figure 2-9: • Audio codec (U500) • Pressure sensor (U705)—Accessible via API commands. • Accelerometer/Gyroscope/Temperature sensor (U704)—Accessible via API commands. • Battery charger (U800)—Accessible via API commands. • Battery gauge (U801)—Accessible via API commands. • IoT Connector 0 (CN306) • Raspberry Pi connector (CN307) • GPIO/PWM expander (U1004)—Used internally on the mangOH Red for I/O functions such as driving LEDs, resetting board components, etc. (see GPIO Expander on page 20) For detailed information, refer to mangOH Red schematics available at mangoh.io/mangoh-red-resourceshardware. • USB Hub controller (U701) All signal sources are enabled by default. Note: The mangOH Red I2C interface operates in a single-master/multi-slave setup. Rev 4 May.18 21 41110401 mangOH Red Developer’s Guide Note: By default, the CF3 I2C interface is connected as shown in Figure 2-9. The board can be modified to connect the Wi-Fi/ BT chipset I2C interface to the I2C expander and gyroscope/accelerometer sensor by populating/depopulating appropriate resistors. R460/R461 Wi-Fi/BT chipset (U1000) Note: Default configuration — Solid lines Alternate configuration — Dashed lines I2C1 Note: Populate/depopulate identified resistors to choose alternate configurations. R793/R794 IoT Connector #0 (CN306, slot IOT0) R345/R346 CF3 I2C1 R795/R796 Gyroscope/ Accelerometer Sensor (U704) I2C Expander (U404) Pressure / Temperature Sensor (U705) Audio Codec (U500) 3.5mm jack (CN500) Raspberry Pi Connector (CN307) GPIO Expander (U1004) USB3503 Hub (U701) Battery Charger (U800) Battery Gauge (U801) Figure 2-9: I2C1 Configuration 2.4.7 Light Sensor The mangOH Red provides a light sensor (U706) that connects to the CF3 module’s ADC3 signal, as shown in Figure 2-5 on page 17. 2.4.8 Raspberry Pi Rev B-compatible Connector The mangOH Red provides a 26-pin Raspberry Pi RevB-compatible connector (CN307). The mangOH Red provides the Raspberry Pi primary signals (alternate Raspberry Pi signals are not supported) as shown in Figure 2-10 on page 23. These signals connect the mangOH Red’s hardware components to a Raspberry Pi attached to the connector, as shown in Figure 2-11 on page 23. Rev 4 May.18 22 41110401 Hardware I2C (Pins 3/5) GPIO (CF3) (Pins 7/11/13/15) SPI (Pins 19/21/23/24/26) 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 Power 3.3V (Pins 1/17) 5.0V (Pins 2/4) UART (Pins 8/10) PWM (Pin 12) GPIO (Expander) (Pins 16/18/22) Ground (Pins 6/9/14/20/25) Figure 2-10: Raspberry Pi Signal Groups UART1 Level shifter UART1 EXT_GPS_LNA_EN PWM CF3 Level shifter (4) GPIO GPIO (3) GPIO GPIO expander Raspberry Pi I2C Connector CN307 I2C hub USB hub SPI2 SPI bridge R371 5.0V R382 GPIO Wi-Fi/BT chipset (U1000) VCC_5V0 USB_VBUS Note: Default configuration — Solid lines Alternate configuration — Dashed lines Figure 2-11: Raspberry Pi Connections Rev 4 May.18 23 41110401 mangOH Red Developer’s Guide 2.4.9 RF The mangOH Red provides u.FL connectors that connect to the CF3 module’s RF signals: • RF_MAIN—CN301 • RF_GPS—CN303 • RF_DIV—CN302 Power for these signals can be enabled/disabled as described in Table 2-5. Table 2-5: CF3 GPIO Interface Configuration Changes Change type Software CF3 Change effect Enable/disable RF power for CF3 module Method Change duration AT command Legato API RF_MAIN Main (CN301) RF_GPS GPS (CN303) RF_DIV DIversity (CN302) Figure 2-12: CF3 module RF Connections 2.4.10 SDIO The mangOH Red supports the CF3 module SDIO signals, which connect via a MUX to the following sources, as shown in Figure 2-13: • microSD holder (CN600)—Default configuration • IOT Connector 0 (CN306) The SDIO interface configuration can be modified as detailed in Table 2-6. Table 2-6: SDIO Interface Configuration Changes Change type Software Rev 4 May.18 Change effect • Use default or alternate configuration. Method API command 24 Change duration Selected configuration used every time device boots up. 41110401 Hardware Mux uSD Holder (CN600) CF3 SDIO IoT Connector #0 (CN306, slot IOT0) Note: Default configuration — Solid lines Alternate configuration — Dashed lines Figure 2-13: SDIO Configuration 2.4.11 SPI1 The mangOH Red supports the CF3 module SPI1 signals, which connect to the following source, as shown in Figure 2-14: • IOT Connector 0 (CN306) CF3 SPI1 SPI IoT Connector #0 (CN306, slot IOT0) Figure 2-14: SPI1 Configuration 2.4.12 UART1 The mangOH Red supports the CF3 module’s UART1 signals, which connect to the following sources, as shown in Figure 2-15: • IoT Connector 0 (CN306)—Default configuration • Raspberry Pi connector (CN307) • Wi-Fi/BT chipset (Note, the level shifter must be ON. In the default board configuration, the level shifter is OFF.) Note: At any one time, use only the IoT expansion card UART or the Raspberry Pi UART, not both. Rev 4 May.18 25 41110401 mangOH Red Developer’s Guide CF3 UART1 UART IoT Connector #0 (CN306, slot IOT0) Level shifter UART Raspberry Pi Connector (CN307) Level shifter UART Wi-Fi/BT chipset (U1000) Note: Default configuration — Solid lines Alternate configuration — Dashed lines Figure 2-15: UART1 Configuration 2.4.13 UART2 The mangOH Red supports the CF3 module’s UART2 signals, which connect via a MUX to the following sources, as shown in Figure 2-16: • Console USB connector (CN305)—UART2 connects to the physical Console USB connector when both MTK_TO_WP_UART_EN and CONS_DIR are low. • Wi-Fi/BT chipset’s UART signal (U1000)—CF3 module’s UART2 and Wi-Fi/BT chipset’s UART0 are linked when MTK_TO_WP_UART_EN signal is pulled high. 2.4.14 UART Console Connections The mangOH Red supports the following console connections for the CF3 module (UART2) and Wi-Fi/BT chipset (UART0), as shown in Figure 2-16: • CF3 module UART2 to Console USB connector (CN305) • Wi-Fi/BT chipset UART0 to Console USB connector (CN305) • Direct connect between CF3 module UART2 and Wi-Fi/BT chipset UART0 Table 2-7: UART Console Connection Options Connection CONS_DIR (SW401 pin 6) MTK_TO_WP_UART_EN (API) CF3 module UART2 to Console USB Pull low (Pin OFF) Pull low Wi-Fi/BT chipset UART0 to Console USB Pull high (Pin ON) Pulll low CF3 module UART2 to Wi-Fi/ BT chipset UART0 n/a Pull high Rev 4 May.18 26 41110401 Hardware CONS_DIR MTK_TO_WP_UART_EN CF3 UART2 Level shifter USB-UART FTDI UART buffer Wi-Fi/BT chipset UART0 Console USB Mux Note: Default configuration — Solid lines Alternate configurations — Dashed lines Figure 2-16: UART Console Connections 2.4.15 UIM Signals The mangOH Red supports both CF3 module UIM interfaces (UIM1, UIM2), where UIM1 is a removable SIM, and UIM2 is an embedded SIM (DNI). The default boot configuration is shown in Figure 2-17. Note: Throughout this document, ‘UIM’ is used to refer to UIM, USIM, SIM, UICC. UIM1 SIM Holder (CN600) UIM2 (DNI) eSIM (U603) CF3 Note: Default configuration — Solid lines Alternate configuration — Dashed lines Figure 2-17: SIM Interfaces Configuration 2.4.15.1 UIM1 The CF3 module’s UIM1 signal connects to the micro-SIM holder (CN600). Note: The CF3 module’s UIM1_DET signal indicates when a SIM is present in the holder. Rev 4 May.18 27 41110401 mangOH Red Developer’s Guide 2.4.15.2 UIM2 Note: The mangOH Red does not ship with an eSIM (the component is DNI). For details, refer to the mangOH Red schematics available at mangoh.io/mangoh-red-resources-hardware. The CF3 module’s UIM2 signal connects to the eSIM (U603). Note: The corresponding UIM2_DET signal pin is reserved for future use. 2.4.16 USB 2.0 The CF3 module’s USB signal connects directly to the mangOH Red’s CF3 USB micro-USB connector (CN305) as shown in Figure 2-18, for control by a connected computer. Note: The micro-USB connector also acts as a power source, if selected. See Power Management on page 32. The USB 2.0 interface configuration can be modified as detailed in Table 2-8. Table 2-8: USB 2.0 Interface Configuration Methods Change type Hardware Change effect • • • CF3 Jumper on pins closest to CF3 USB—Select CF3 USB power Jumper on pins closest to Console USB—Select Console USB power Jumper off—Use battery if connected, otherwise no power supplied USB Method Change duration Position jumper on CN804 to choose CF3 USB or CONSOLE USB connector to supply power. mangOH Red uses the selected power supply until the jumper changes. Note: mangOH Red ships with CF3 USB power selected (jumper on pins closest to CF3 USB connector). CF3 USB USB2.0 micro-USB connector (CN305) Figure 2-18: USB_2.0 Configuration 2.5 Wi-Fi/BT Chipset The mangOH Red incorporates a Wi-Fi/BT chipset (MediaTek Wi-Fi+Bluetooth) that provides the following functionality: • RF: · Wi-Fi/Bluetooth/WLAN connections via an integrated 2.4 GHz antenna · Supports 2.4GHz Wi-Fi (802.11b/g/nHT20) and 2.4GHz BLE (Bluetooth Low Energy) • IOT0 connection via Wi-Fi/BT chipset’s UART1 • Application processor—Real-time application processing using the mangOH Red’s real-time I/O connector, via GPIO, ADC, and I2C interfaces. Rev 4 May.18 28 41110401 Hardware • Access to mangOH Red’s accelerometer/gyroscope/temperature sensor via GPIO interface • Access to Raspberry Pi connector via SPI interface • Wi-Fi/BT chipset console connection to either the Console USB connector or the CF3 module console, including ability to receive firmware downloads from either source. • Optional debug connector (CN400, DNI) to use for serial wire debugging The Wi-Fi/BT chipset can connect to several components on the mangOH Red, as show in Figure 2-19. Wi-Fi/BT/WLAN U.FL connector (CN1000) Integrated antenna (ANT1000) RF Off (default) UART1 SW401 Pin 4: HL_MODE Level shifter UART1 CF3 SPI2 SPI Bridge USB SPI2_CS0 SPI2_CS1 Wi-Fi/BT chipset USB Hub HSIC I2C Raspberry Pi SPI2_CS2 R460/R461 I2C ADC I2C Expander R345/R346 Note: Populate/depopulate identified resistors to connect either the CF3 module or the Wi-Fi/BT chipset to the I2C expander. Real-time I/O GPIO SPI1 UART0 32Mb Flash Memory Refer to Figure 2-16 for UART0 details. Note: Default configuration — Solid lines Alternate configuration — Dashed lines Figure 2-19: Wi-Fi/BT Chipset Connections Rev 4 May.18 29 41110401 mangOH Red Developer’s Guide 2.5.1 Wi-Fi RF The mangOH Red supports 2.4GHz Wi-Fi (802.11b/g/nHT20). Table 2-9 describes the mangOH Red’s Wi-Fi RF average output power. For Wi-Fi 2.4 GHz RF receiver specifications, refer to the MediaTek MT7697 Datasheet, version 1.01. Table 2-9: Maximum Wi-Fi RF Average Output Power Average Power (dBm) Mode Frequency 802.11b 802.11g 802.11n-HT20 2412 11.5 12.0 11.5 2437 11.5 13.0 14.0 2462 10.5 11.5 11.0 Min (dB) Max (dB) -1.5 1.5 2.4 GHz WLAN Parameter Description • Output power variation • TSSI closed-loop control across all temperature range and channels and VWSR 1.5:1 VCC_3V3 voltage is within ±5% of typical value 2.5.2 Bluetooth RF The mangOH Red supports 2.4GHz BLE (Bluetooth Low Energy). Table 2-10 describes the mangOH Red’s Bluetooth RF average output power. For Bluetooth 2.4 GHz RF receiver specifications, refer to the MediaTek MT7697 Datasheet, version 1.01. Table 2-10: Maximum Bluetooth RF Average Output Power Mode Bluetooth Rev 4 May.18 Average Power (dBm) LE, GFSK 8.5 30 41110401 Hardware 2.6 IoT Connector Interfaces The mangOH Red provides one IoT Connector (CN306, slot IOT0), which supports the signals defined in the Project mangOH IoT Expansion Card Design Specification, as detailed in Table 2-2 on page 16. The default configuration (enabled signals) for the IoT Connector is shown in Figure 2-20. The IoT Connector interface configuration can be modified as detailed in Table 2-11. Table 2-11: IoT Connector Interface Configuration Changes Change type Software Change effect Method Enable/disable identified signal(s) on a specific IoT Connector. API command Change duration Modifies running configuration until device reboots or another change is made. IoT Connector #0 (CN306, slot IOT0) UART PCM SPI SDIO USB CF3 Note: Default configuration — Solid lines Alternate configuration — Dashed lines n_RESET I2C GPIO(1-4) ADC0 PPS n_CARD_DETECT Figure 2-20: IoT Connector Configuration Rev 4 May.18 31 41110401 mangOH Red Developer’s Guide 2.7 Reset Methods The mangOH Red supports hardware and software resets of the entire board or certain components of the board, as shown in Figure 2-21: Table 2-12: Reset Methods Board Components to Reset Reset Method Entire board, including CF3 module (WP or HL) Press Reset button (SW400) IOT Expansion Card CF3_IOT0_RESET or Use an API command to trigger the CF3 module signal GPIO_IOT0_RESET. Wi-Fi/BT chipset CF3_GPIO_WIFI_RESET For detailed specifications showing how full or partial resets are enabled, see the mangOH Red schematics available at mangoh.io/mangoh-red-resources-hardware. GPIO Expander(SX1509) VCC_1V8 Battery Charger SW401.pin4 WP= OFF HL=ON TCA9546 10k USB HUB (USB3503) 3V7 100k NCP303 POR reset 3.0V WP_LowPower_Reset Reset (open drain out) Reset Button System_reset SW401.pin8 WP= ON HL=OFF Main CF3 Reset IoT #1 CF3_IOT0_RESET LowPower_Reset IoT #1 47k DNI VCC_1V8 47k CF3_GPIO_WIFI_RESET RESET_WIFI_1V8 Level Shift RESET_WIFI_3V3 U307 CP2130 MTD7697D Figure 2-21: Reset Methods 2.8 Power Management The mangOH Red has two primary power supplies (CF3 USB connector and CONSOLE USB connector), and a rechargeable backup battery power supply option. Figure 2-22 illustrates these power supplies, their voltage/current specifications, and how they supply various components on the mangOH Red platform. A multi-function switch (SW401) controls some power-related features (see Multi-switch (SW401) on page 15), including: • Pin 1 (PWR_ON)—Enable/disable CF3 module’s POWER_ON_signal Rev 4 May.18 32 41110401 Hardware • Pin 3 (VCC_3V7_ULPM)—In ULPM, enable/disable power to accessories (CF3 module always receives power) • Pin 5 (BATT_TS+)—Enable/disable backup battery charging VGPIO L910 100mA typ 500mA Max EN 5V boost 5V Peripherals 0 ohm 4.5V to 5.5V uUSB CF3 Raspberry Pi Connector Regulator and charger 300mA typ 600mA max VGPIO Jumper L911 EN 3.3V Buck DNI 3V3 Peripherals Including WiFi/BT chipset 50mA typ 100mA Max 0 ohm Battery Charger with Power Path 1V8 Peripherals uSUB Console VGPIO Jumper: Battery SW401SLQ LiPo Battery 3.7V 1x IoT EN 0 Ohm 300mA typ 500mA Max 1.8V Buck 200mA typ 900mA max JST-PH Connector 50mA typ 100mA Max 5V 3V3 Vbatt 1V8 Battery Gauge 0 OHM Low Power 1.8V LDO 3.7V @ 1A continous, 2.5A peak CF3 Main Low Power I/Os Figure 2-22: Power Management Rev 4 May.18 33 41110401 3: Regulatory Compliance 3.1 Important Compliance Information for North American Users 3.1.1 USA Caution: Changes or modifications not expressly approved by Sierra Wireless could void the user's authority to operate the equipment. This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Note: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: · Reorient or relocate the receiving antenna. · Increase the separation between the equipment and receiver. · Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. · Consult the dealer or an experienced radio/TV technician for help. 3.1.2 Canada This device complies with Industry Canada's licence-exempt RSSs. 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. Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorisée aux deux conditions suivantes : 1) l'appareil ne doit pas produire de brouillage; 2) l'appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d'en compromettre le fonctionnement. Rev 4 May.18 34 41110401
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.6 Linearized : No Author : Sierra Wireless Create Date : 2018:05:08 14:02:20Z Modify Date : 2018:05:08 14:14:01-07:00 XMP Toolkit : Adobe XMP Core 5.6-c015 84.159810, 2016/09/10-02:41:30 Format : application/pdf Creator : Sierra Wireless Title : mangOH Red Developer's Guide Creator Tool : FrameMaker 2015.0.5 Metadata Date : 2018:05:08 14:14:01-07:00 Producer : Acrobat Distiller 18.0 (Windows) Document ID : uuid:e37280b5-1226-4f0d-8419-d15a8954fc1a Instance ID : uuid:38320812-5ad9-476f-9ac7-1b3b721485c4 Page Mode : UseOutlines Page Count : 34EXIF Metadata provided by EXIF.tools