app s | submitted / available | |||||||
---|---|---|---|---|---|---|---|---|
1 | Schematics | October 05 2018 | ||||||
1 |
|
41110401 mangOH Red Developers Guide r4 | Operational Description | 516.47 KiB | October 05 2018 | |||
1 | Block Diagram | October 05 2018 | ||||||
1 | RF Exposure Info | October 05 2018 | ||||||
1 | ID Label/Location Info | October 05 2018 | ||||||
1 | Test Report | October 05 2018 | ||||||
1 | Test Report | October 05 2018 | ||||||
1 | External Photos | October 05 2018 | ||||||
1 | Internal Photos | October 05 2018 | ||||||
1 | Test Setup Photos | October 05 2018 | ||||||
1 | Parts List/Tune Up Info | October 05 2018 | ||||||
1 | External Photos | October 05 2018 |
1 | 41110401 mangOH Red Developers Guide r4 | Operational Description | 516.47 KiB | October 05 2018 |
mangOH Red Developers Guide 41110401 Rev 4 mangOH Red Developers Guide Important Notice Safety and Hazards Limitation of Liability 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. 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 2 41110401 Preface This document contains information which is proprietary to Sierra Wireless Inc. and is licensed pursuant to Creative Commons Attribution 4.0 International License. Title: mangOH Red Developers Guide Author: Sierra Wireless Source: https://mangoh.io 2018 Sierra Wireless. Licensed under the Creative Commons Attribution 4.0 license, http://creativecommons.org/licenses/by/4.0/
Indicate any modifications made to the original document. mangOH and the mangOH logo are trademarks of Sierra Wireless. Other trademarks are the property of their respective owners. Patents Document details Copyright Disclaimer Trademarks Revision History Revision number Release date Changes 1 2 3 4 May 2017 June 2017 April 2018 Document created Updated image to DV3 board Updated image to DV5 board Added Wi-Fi/BT RF specifications Added Regulatory chapter Minor corrections May 2018 Updated 2.5 Wi-Fi/BT Chipsetindicated supported RF Rev 4 May.18 3 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 4 41110401 Regulatory Compliance . 34 Important Compliance Information for North American Users . 34 USA . 34 Canada . 34 Contents Rev 4 May.18 5 41110401 1: Introduction 1 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 developers guide describes the mangOH Reds 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 6 41110401 2: Hardware 2 This chapter describes the mangOH Red platforms hardware components and interfaces. 2.1 mangOH Red Hardware Overview Figure 2-1 provides an overview of the mangOH Reds 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:
mangOH Red User GuideInstructions on setting up the hardware components Available at source.sierrawireless.com:
Sierra Wireless CF3 module-specific Product Technical Specification documents AirPrime Embedded Module Common Flexible Form Factor (CF3) Specification
A m 0 0 0 1
@
V 7
. 3 y t i s r e v D i S P G N O _ r e w o P c i r e n e G n o t t u b t e s e R LEDs Audio i n a ESIM M microSD
/uSIM Holder SDIO uUSB Connector Type A USB Connector uUSB Connector IoT Connector Raspberry Pi Connector Figure 2-1: mangOH Red Hardware Components Overview Wi-Fi + BT Integrated u.FL DNI Wi-Fi/BT chipset Real-time I/O Low Power I/O CF3 Module Gyroscope /
Accelerometer Pressure /
Temperature Sensor Light Sensor Rev 4 May.18 7 41110401 mangOH Red Developers Guide 1Pluggable IoT connector
(CN306 (IOT0)) 2Power supply select (CN804) 3Battery connector (CN802) 4Signals control (SW401) 5Main antenna (CN301) 6GNSS antenna (CN303) 7Diversity antenna (CN302) 8Wi-Fi/Bluetooth antenna
(ANT1000) 9USB Host (CN304) 10Audio (CN500) 11USB Console connector
(CN305) 12Raspberry PI RevB-compatible header (CN307) 13Generic button (SW200) 14PWR_ON switch (SW402) 15Reset switch (SW400) 16CF3 module socket (J200) 17Real Time I/O (CN310) 18Low Power I/O (CN312) 7 18 15 9 10 4 1 16 3 2 11 13 14 17 8 6 5 12 Figure 2-2: mangOH RedTop Side Switches/Connectors Note: For reference only. For latest schematic, visit mangoh.io/mangoh-red-resources-hardware. Rev 4 May.18 8 41110401 Hardware 2 3 4 1 1USB CF3 connector
(CN801) 2micro-SIM
(CN600, bottom slot) 3microSD
(CN600, top slot) 4ESIM (U603 (DNI)) 5Wi-Fi/BT chipset
(U1000) 6Integrated Wi-Fi/Bluetooth antenna
(ANT1000) 7Wi-Fi/Bluetooth antenna
(CN1000 (DNI)) 5 6 7 Figure 2-3: mangOH RedBottom Side Switches/Connectors Note: For reference only. For latest schematics, visit mangoh.io/mangoh-red-resources-hardware. Rev 4 May.18 9 41110401 mangOH Red Developers Guide 2.2 mangOH Red Hardware Architecture CF3 module socket The mangOH Red platform provides several hardware components, including:
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 Reds hardware architecture (connectors and signals). The following sections describe these features in greater detail:
mangOH Red Hardware Components on page 12Components available to the CF3 module and Wi-Fi/BT chipset.
CF3 Module Signals on page 17CF3 module connections to hardware components.
Wi-Fi/BT Chipset on page 28Wi-Fi/BT chipset connections to hardware components.
IoT Connector Interfaces on page 31IoT Expansion Card signal connections to the hardware components. Rev 4 May.18 10 41110401 L A T X z H M 6 2
) 9 2 O P G I
(
I S O M _ P S I
) 0 3 O P G I
(
I O S M _ P S I
) 7 2 O P G I
(
K L C _ P S I
) 2 3 O P G I
(
Y D R M _ P S I I P S 1 T R A U 2 T R A U
) 8 3 O P G I
(
S T R _ 1 T R A U
) 9 3 O P G I
(
S T C _ 1 T R A U
) 6 3 O P G I
(
X R _ 1 T R A U
) 7 3 O P G I
(
X T _ 1 T R A U r e t f i h S l e v e L T R A U x u M o t B S U T R A U I D T F Hardware B S U A e p y T n o i t a r u g i f n o C e r a w d r a H t l u a f e D 0
#
n o c t o I W D B S U W D B S U W D B S U 3 0 5 3 B S U P U C S H I i p R n p i 6 2 I P S o t B S U 0 1 3 N C l I O P s G a n g S i i l P r t C y r r e b p s a R I C S H I C S H t r a m S 3 F C 3 C D A 2 M S I 1 M S I s u o i r a V s l a n g i s r o s n e S t h g L i I M S E M S I 1
#
R E D L O H n o i t c n u f
-
i t l u M h c t i w s l a c i s y h P s e h c t i w s
, n O r e w o P
, t e s e R c i r e n e G n o t t u b I V D S P G I N A M i o d u A X U M l g o a n A c e d o C m m 5 3
. k c a J 0
. 2 B S U 1 C 2 I M C P 8 V 1 U S P 3 V 3 U S P 0 V 5 U S P n o i t c e S r e w o P y r e t t a B r e g r a h C h c t i w s 2
-
B S U u 1
-
B S U u y r e t t a B t u p n I l a e R e m T i O I T B
/
i F
-
i W t e s p h c i l e b a l i a v a y n o s l i
. d e l l a
) 1 T R A U T B
/
i F
-
i W
(
n o i t c e s i s h T t s n i s i l e u d o m 3 F C L H n a n e h w
) I N D
(
L F u
. T B
/
i i F W 2 1 3 N C d e t a r g e t n I O I r e w o P w o L 1 T R A U 2 T R A U 0 C D A I 1 P S R E T S A M I O D S I O P G C 2 I y r e t t a B e g u a G I O D S X U M C 2 I B U H C 2 I D S u R E D L O H I O P G x 4
/
e p o c s o r y G r e t e m o r e l e c c A 9 0 5 1 X S I O P G
/
e r u s s e r P e r u t a r e p m e T r o s n e S Figure 2-4: mangOH Red Hardware Architecture (Default) Rev 4 May.18 11 41110401 mangOH Red Developers 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. CF3 Module Signals on page 17 The mangOH Reds default configuration enables specific interfaces when the platform boots. For interface details, see:
MUXing 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 Designatora Description Signals / Module Pins Notes Modules/Processors/etc. For details, see CF3 Module Signals on page 17. IoT Expansion Card Connections to multiple CF3 module interfaces. For details, see IoT Expansion Card on page 15. CF3 module
(J200) IOT0
(CN306) Wi-Fi/BT chipset
(U1000) Card slots Micro-SIM
(CN600) micro-SD
(CN600) MediaTek Wi-Fi/
BT chipset with ARM Cortex-M4 application processor Micro-SIM/
microSD holder
(bottom slot) CF3 UIM1
(Pins: 2629) Micro-SIM/
microSD holder
(top slot) CF3 SDIO
(Pins: 161166) ESIM
(U603) Embedded SIM CF3 UIM2
(Pins 5558) For details, see Wi-Fi/BT Chipset on page 28. Purpose: UIM used to establish mobile network connection. For details, see UIM1 on page 27. Purpose: Provide access to microSD card. For details, see:
MUXing on page 17 SDIO on page 24 Purpose: Built-in UIM used to establish mobile network connection. For details, see UIM2 on page 28. Note: eSIM is DNI. Rev 4 May.18 12 41110401 Table 2-1: mangOH Red Hardware Components (Continued) Type and Designatora Description Signals / Module Pins Notes Hardware USB-type connectors micro-USB
(CN801) CF3 USB micro-USB connector micro-USB
(CN305) Console USB micro-USB connector
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: 9699) Power (if selected)
Purpose:
ConsoleConnects 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. USB Host
(CN304) USB Type A connector HSIC
(Pins: 14, 15) RF, Audio, Raspberry Pi connectors For details, see UART2 on page 26. Purpose: Provides USB host capability to CF3 module. For details, see HSIC (USB/Ethernet) on page 20. RF Antennas Main (CN301) GNSS (CN303) Diversity (CN302) Wi-Fi/Bluetooth Antennas
(Integrated ANT1000;
u.FLCN1000
(DNI)) u.FL connectors CF3 RF
(Pins: 49 (Main), 38 (GNSS), 31 (Diversity)) For details, see RF on page 24. 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: 3033) Purpose: Provide audio capability to CF3 module. For details, see:
MUXing on page 17 Audio (Analog and PCM) on page 18 Raspberry Pi
(CN307) 26-pin Rev B-compatib le connector Other ICs and components Gyroscope/
Accelerometer
(U704) Integrated BMI160 inertial measurement module
CF3 HSIC signals (via SPI or USB (DNI)) For details, see Raspberry Pi Rev B-compatible Connector on page 22.
Wi-Fi/BT chipset SPI CF3 I2C1 interface 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. Rev 4 May.18 13 41110401 mangOH Red Developers Guide Table 2-1: mangOH Red Hardware Components (Continued) Type and Designatora Description Signals / Module Pins Notes Pressure sensor/
Temperature sensor (U705) Integrated BMP280 barometric pressure sensor CF3 I2C1 interface Light sensor
(U706) Integrated PNJ4K01F ambient light sensor CF3 ADC3 GPIO/PWM expander
(U1004) Integrated SX1509 expander 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. 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. Purpose: Provides additional GPIOs. For details, see:
GPIO Expander on page 20 I2C1 on page 21 Low Power I/O connector
(CN312) 6-pin header 6-pin header CF3 ADC1/ADC2 CF3 GPIOs (if resistors are populated) CF3 UIM2_DET Wi-Fi/BT chipset user-
configurable multi-purpose pins (for ADC, GPIO, PWM, I2C, etc.) Purpose: Connect low-power input sources to CF3 module. For details, see ADC on page 17. 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. Green LED GPIO expander I/O_8 via LED_CARD_DETECT_IOT0 Purpose: Indicates IoT Expansion Card is in slot IOT0. Green LED CF3 TX_ON Purpose: Indicates CF3 module is transmitting/
receiving. 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 (user-
defined)
(D410) Green LED CF3 GPIO34 (via expander WP_GPIO_7_lvl) Purpose: User-defined (programmable) Rev 4 May.18 14 41110401 Real-time I/O connector
(CN310) LEDs IoT Expansion Card 0
(D401) Rx/Tx (CF3 module)
(D402) WLAN Connected
(D200) Table 2-1: mangOH Red Hardware Components (Continued) Type and Designatora Platform controls Description Signals / Module Pins Notes Hardware Multi-switch
(SW401) Module signals control Eight dipswitches:
1. PWR_ON 2. WIFI_UART1_TX 3. VCC_3V7_ULPM 4. HL_MODE Enable/disable CF3 modules POWER_ON signal Enable (On)/disable (Off) firmware download (recovery mode) to the CF3 module. Similar functionality to TP1_BOOT. When device is in ULPM:
OFFonly the CF3 module is receiving power. ONthe CF3 module + accessories receive power Used with pin 8 (LowPower_RESET) to indicate whether in HL mode or WP mode
ONHL mode OFFWP mode 5. BATT_TS+
Enable (On)/disable (off) battery charging 6. CONS_DIR 7. TP1_BOOT 8. LowPower_RESET Console USB connectors connects to:
OFFCF3 module console
ONWi-Fi/BT chipset console
Note: To download firmware to the:
CF3 moduleSet CONS_DIR Off and TP1_BOOT On.
Wi-Fi/BT chipsetSet CONS_DIR On and WIFI_UART_TX On. Enable (On)/disable (Off) CF3 modules TP1 (boot) signal. Used with pin 4 (HL_MODE) to indicate whether in HL mode or WP mode
For details, see Power Management on page 32. ONWP mode OFFHL mode 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 CF3s 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 Developers 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 USB UART SPI I2C CF3 Signal(s) Signal Path Notes HSIC
(Pins 14, 15) Single Purpose: Data transfer; application control For details, see HSIC (USB/Ethernet) on page 20. UART1
(Pins 2, 9) MUX SPI1
(Pins 5154) Yes Purpose: Data transfer For details, see:
UART1 on page 25
MUXing on page 17 Purpose: Data transfer For details, see:
MUXing on page 17 SPI1 on page 25 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 14 GPIO
(7, 8, 13, 42) Single Purpose: Customer-defined data communication For details, see CF3 GPIOs on page 18. SDIO ADC0 SDIO
(Pins 161166) Yes Purpose: Data transfer For details, see:
MUXing on page 17 SDIO on page 24 ADC0
(Pin 25) Single Purpose: General purpose ADC output to host application (e.g. indicate when a sensor has triggered) For details, see ADC on page 17. Power Power n/a Default configurationReceives three power inputs:
For details, see Power Management on page 32. 5.0V @ 500 mA 3.3V @ 1 A 1.8V @ 200 mA PCM PCM Single Purpose: Digital audio interface RESET_IOT0 GPIO2 Purpose: Data transfer For details, see CF3 GPIOs on page 18. PPS DR_SYNC 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). CARD_DETECT_IOT0 GPIO33 Purpose: Data transfer For details, see CF3 GPIOs on page 18. Rev 4 May.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 Hubs
Audio (Analog and PCM) on page 18 SDIO on page 24 UART2 on page 26 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 typesome 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:
ADC0IoT Connector 0 (CN1000, slot IOT0), pin 20 ADC1, ADC2Low Power I/O (CN312), pins 4 and 5 ADC3Light sensor (U706), pin 6 ADC0 ADC1 ADC2 ADC3 CF3 Figure 2-5: ADC Configuration ADC0 IoT Connector #0
(CN306, slot IOT0) Low Power I/O
(CN312) Light sensor
(U706) Rev 4 May.18 17 41110401 mangOH Red Developers 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 Change effect Method Change duration Hardware MuxUse default or alternate configuration Selected configuration used every time device boots up. Populate/depopulate resistors on the Mux:
R508 pulls signal low (default configuration) R520 pulls signal high (alternate configuration)
Mux CF3 PCM IoT Connector #0
(CN306, slot IOT0) Digital-
Analog 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:
One GPIO (GPIO32) connects to the NINT (active low interrupt) output signal from a GPIO expander (U1004). Six GPIOs connect to the IoT slot (for card detect, card reset, and four for use as GPIOs). 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 GPIO42 GPIO13 GPIO7 GPIO8 GPIO33 GPIO2 GPIO6 GPIO32 GPIO36 GPIO22 GPIO23 GPIO24 EXT_GPS_LNA_EN GPIO35 GPIO34 GPIO21 CF3 GPIO Expander (U1004) NINT Level Shifter (U306) WP_GPIO_1 WP_GPIO_2 WP_GPIO_3 PWM_OUT WP_GPIO_8 WP_GPIO_7 SPI2_SRDY _WIFI_1V8 SPI2_SRDY _WIFI_3V3 Level Shifter (U307) Hardware IOT0_GPIO1 IOT0_GPIO2 IOT0_GPIO3 IOT0_GPIO4 IoT Connector #0
(CN306, slot IOT0) CARD_DETECT_IOT0 RESET_IOT0 SW401 LowPower_RESET Low Power I/O (CN312) WP_GPIO_5_wakeable WP_GPIO_1_lvl WP_GPIO_2_lvl WP_GPIO_3_lvl PWM_OUT_3V3 WP_GPIO_8_lvl LED
(D410) GPIO59 Raspberry Pi Connector
(CN307) Wi-Fi module
(U1000) GPIO25 RESET_WIFI_1V8 RESET_WIFI_3V3 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 Developers 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 modules 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 I/O 0 I/O 1 I/O 2 I/O 3 Signal Name BOARD_REV1 BOARD_REV2 BOARD_REV3 GPIO_EXP_RPI_1 I/O_4 GPIO_EXP_RPI_2 I/O_5 MTK_TO_WP_UART_EN I/O_6 WIFI_UART1_TX Purpose Reserved for future use. Reserved for future use. Reserved for future use. Raspberry Pi connector, pin 16 Raspberry Pi connector, pin 18 Enable MTK recovery mode from WP (0), or connects CF3 UART1 to Wi-Fi/BT chipset UART0 (1) Wi-Fi/BT chipset UART TxNormal (0), or MTK recovery mode (1) for firmware downloads/recovery
(Note: DNIR754 must be populated to access this signal.) I/O_7 I/O_8 I/O_9 I/O_10 I/O_11 I/O_12 I/O_13 I/O_14 GPIO_EXP_RPI_3 Raspberry PI connector, pin 22 LED_CARD_DETECT_IOT0 Indicates whether IoT expansion card is present SDIO_SEL Connect SD interface to IoT0 (0) or SD card (1) Power_Fail_Indicator Indicate power fail SENSOR_INT1 SENSORT_INT2 PCM_EXP1_SEL Accelerometer/gyroscope sensor interrupt Accelerometer/gyroscope sensor interrupt Connect PCM interface to IoT0 or to PCM codec (audio) 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) CF3 HSIC HSIC Up USB3503 Hub
(U701) USB DW USB DW USB DW USB to SPI bridge
(U1006) SPI SPI USB USB Wi-Fi/BT chipset
(U1000) Raspberry Pi Connector
(CN307) IoT Connector #0
(CN306, slot IOT0) USB Host Type A Connector
(CN304) DNI 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:
GPIO/PWM expander (U1004)Used internally on the mangOH Red for I/O functions such as driving LEDs, 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) resetting board components, etc. (see GPIO Expander on page 20) For detailed information, refer to mangOH Red schematics available at mangoh.io/mangoh-red-resources-
hardware. 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 Developers 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. Wi-Fi/BT chipset
(U1000) I2C1 R793/R794 CF3 I2C1 R795/R796 R460/R461 R345/R346 Gyroscope/
Accelerometer Sensor (U704) Pressure /
Temperature Sensor (U705) Audio Codec
(U500) 3.5mm jack
(CN500) Note: Default configuration Solid lines Alternate configuration Dashed lines Note: Populate/depopulate identified resistors to choose alternate configurations. I2C Expander
(U404) IoT Connector #0
(CN306, slot IOT0) 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 modules 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 Reds 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) 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) 1 3 5 7 9 11 13 15 17 19 21 23 25 2 4 6 8 10 12 14 16 18 20 22 24 26 Figure 2-10: Raspberry Pi Signal Groups UART1 Level shifter UART1 PWM
(4) GPIO
(3) GPIO Raspberry Pi Connector CN307 I2C SPI2 5.0V EXT_GPS_LNA_EN CF3 Level shifter GPIO GPIO expander I2C hub USB hub SPI bridge GPIO Wi-Fi/BT chipset
(U1000) R371 R382 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 Developers Guide 2.4.9 RF The mangOH Red provides u.FL connectors that connect to the CF3 modules RF signals:
RF_MAINCN301 RF_GPSCN303 RF_DIVCN302 Power for these signals can be enabled/disabled as described in Table 2-5. Table 2-5: CF3 GPIO Interface Configuration Changes Change type Change effect Method Change duration Software Enable/disable RF power for CF3 module AT command Legato API RF_MAIN CF3 RF_GPS RF_DIV Figure 2-12: CF3 module RF Connections Main
(CN301) GPS
(CN303) DIversity
(CN302) 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 Change effect Method Change duration Software
Use default or alternate configuration. API command Selected configuration used every time device boots up. Rev 4 May.18 24 41110401 Hardware Mux CF3 SDIO uSD Holder
(CN600) 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 modules UART1 signals, which connect to the following sources, as shown in Figure 2-15:
Wi-Fi/BT chipset (Note, the level shifter must be ON. In the default board configuration, the level shifter is IoT Connector 0 (CN306)Default configuration Raspberry Pi connector (CN307) 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 Developers Guide UART IoT Connector #0
(CN306, slot IOT0) UART Raspberry Pi Connector (CN307) UART Wi-Fi/BT chipset
(U1000) Note: Default configuration Solid lines Alternate configuration Dashed lines CF3 UART1 Level shifter Level shifter Figure 2-15: UART1 Configuration 2.4.13 UART2 The mangOH Red supports the CF3 modules 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 chipsets UART signal (U1000)CF3 modules UART2 and Wi-Fi/BT chipsets 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:
Wi-Fi/BT chipset UART0 to Console USB connector (CN305)
Direct connect between CF3 module UART2 and Wi-Fi/BT chipset UART0 CF3 module UART2 to Console USB connector (CN305) 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 Wi-Fi/BT chipset UART0 to Console USB CF3 module UART2 to Wi-Fi/
BT chipset UART0 Pull low (Pin OFF) Pull high (Pin ON) n/a Pull low Pulll low Pull high Rev 4 May.18 26 41110401 Hardware CONS_DIR MTK_TO_WP_UART_EN CF3 UART2 Level shifter UART buffer USB-UART FTDI Console USB Wi-Fi/BT chipset UART0 Mux Figure 2-16: UART Console Connections Note: Default configuration Solid lines Alternate configurations Dashed lines 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. CF3 UIM1 UIM2 SIM Holder
(CN600)
(DNI) eSIM (U603) Note: Default configuration Solid lines Alternate configuration Dashed lines Figure 2-17: SIM Interfaces Configuration 2.4.15.1 UIM1 The CF3 modules UIM1 signal connects to the micro-SIM holder (CN600). Note: The CF3 modules UIM1_DET signal indicates when a SIM is present in the holder. Rev 4 May.18 27 41110401 mangOH Red Developers 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 modules 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 modules USB signal connects directly to the mangOH Reds 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 Change effect Method Hardware
Jumper on pins closest to CF3 USBSelect CF3 USB power Jumper on pins closest to Console USBSelect Console USB power Jumper offUse battery if connected, otherwise no power supplied Position jumper on CN804 to choose CF3 USB or CONSOLE USB connector to supply power. Note: mangOH Red ships with CF3 USB power selected (jumper on pins closest to CF3 USB connector). Change duration mangOH Red uses the selected power supply until the jumper changes. USB2.0 micro-USB CF3 USB connector
(CN305) CF3 USB 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:
Supports 2.4GHz Wi-Fi (802.11b/g/nHT20) and 2.4GHz BLE (Bluetooth Low Energy) RF:
Wi-Fi/Bluetooth/WLAN connections via an integrated 2.4 GHz antenna IOT0 connection via Wi-Fi/BT chipsets UART1 Application processorReal-time application processing using the mangOH Reds real-time I/O connector, via GPIO, ADC, and I2C interfaces.
Rev 4 May.18 28 41110401 Hardware Access to mangOH Reds 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) SW401 Pin 4: HL_MODE UART1 Level shifter UART1 SPI2 SPI Bridge SPI2_CS0 USB USB Hub HSIC Wi-Fi/BT chipset SPI2_CS1 SPI2_CS2 Raspberry Pi CF3 I2C I2C ADC GPIO SPI1 R460/R461 I2C Expander R345/R346 Real-time I/O Note: Populate/depopulate identified resistors to connect either the CF3 module or the Wi-Fi/BT chipset to the I2C expander. 32Mb Flash Memory UART0 Refer to Figure 2-16 for UART0 details. Figure 2-19: Wi-Fi/BT Chipset Connections Note: Default configuration Solid lines Alternate configuration Dashed lines Rev 4 May.18 29 41110401 mangOH Red Developers 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 Reds 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 2.4 GHz WLAN 2412 2437 2462 11.5 11.5 10.5 12.0 13.0 11.5 11.5 14.0 11.0 Parameter Description Min (dB) Max (dB) 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).
-1.5 1.5 Table 2-10 describes the mangOH Reds 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 Average Power (dBm) Bluetooth LE, GFSK 8.5 Rev 4 May.18 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 Change effect Method Change duration Software Enable/disable identified signal(s) on a specific IoT Connector. API command Modifies running configuration until device reboots or another change is made. IoT Connector #0
(CN306, slot IOT0) UART PCM SPI SDIO USB n_RESET I2C GPIO(1-4) ADC0 PPS CF3 n_CARD_DETECT Figure 2-20: IoT Connector Configuration Note: Default configuration Solid lines Alternate configuration Dashed lines Rev 4 May.18 31 41110401 mangOH Red Developers 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. VCC_1V8 SW401.pin4 WP= OFF HL=ON 10k 100k WP_LowPower_Reset GPIO Expander(SX1509) TCA9546 USB HUB
(USB3503) Battery Charger 3V7 NCP303 POR reset 3.0V Reset
(open drain out) Reset Button Main CF3 DNI System_reset SW401.pin8 WP= ON HL=OFF LowPower_Reset CF3_IOT0_RESET Reset IoT #1 IoT #1 47k VCC_1V8 47k CF3_GPIO_WIFI_RESET RESET_WIFI_1V8 Level Shift U307 RESET_WIFI_3V3 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 modules POWER_ON_signal Rev 4 May.18 32 41110401
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 Hardware Regulator and charger Battery Charger with Power Path Jumper:
Battery SW401 Battery Gauge L910 VGPIO EN 5V boost VGPIO 0 ohm L911 EN 3.3V Buck 0 ohm VGPIO EN 1.8V Buck 0 Ohm 100mA typ 500mA Max 300mA typ 600mA max 5V Peripherals 3V3 Peripherals Including WiFi/BT chipset 50mA typ 100mA Max 1V8 Peripherals 300mA typ 500mA Max 200mA typ 900mA max 50mA typ 100mA Max 1x IoT 5V 3V3 Vbatt 1V8 0 OHM Low Power 1.8V LDO 3.7V @ 1A continous, 2.5A peak CF3 Main Low Power I/Os Raspberry Pi Connector 4.5V to 5.5V uUSB CF3 Jumper uSUB Console DNI LiPo Battery 3.7V JST-PH Connector Figure 2-22: Power Management Rev 4 May.18 33 41110401 3: Regulatory Compliance 3.1 Important Compliance Information for North American Users 3 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 prsent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorise aux deux conditions suivantes :
1) l'appareil ne doit pas produire de brouillage;
2) l'appareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible d'en com-
promettre le fonctionnement. Rev 4 May.18 34 41110401
frequency | equipment class | purpose | ||
---|---|---|---|---|
1 | 2018-05-13 | 2412 ~ 2462 | DTS - Digital Transmission System | Original Equipment |
app s | Applicant Information | |||||
---|---|---|---|---|---|---|
1 | Effective |
2018-05-13
|
||||
1 | Applicant's complete, legal business name |
Sierra Wireless Inc.
|
||||
1 | FCC Registration Number (FRN) |
0005810874
|
||||
1 | Physical Address |
13811 Wireless Way
|
||||
1 |
Richmond, BC, N/A V6V 3A4
|
|||||
1 |
Canada
|
|||||
app s | TCB Information | |||||
1 | TCB Application Email Address |
h******@acbcert.com
|
||||
1 | TCB Scope |
A4: UNII devices & low power transmitters using spread spectrum techniques
|
||||
app s | FCC ID | |||||
1 | Grantee Code |
N7N
|
||||
1 | Equipment Product Code |
RED
|
||||
app s | Person at the applicant's address to receive grant or for contact | |||||
1 | Name |
Y**** W******
|
||||
1 | Title |
Sr. Manager, Regulatory Compliance
|
||||
1 | Telephone Number |
604-2********
|
||||
1 | Fax Number |
604-2********
|
||||
1 |
y******@SierraWireless.com
|
|||||
app s | Technical Contact | |||||
1 | Firm Name |
Sierra Wireless.lnc.
|
||||
1 | Name |
Y**** W****
|
||||
1 | Physical Address |
Canada
|
||||
1 |
y******@sierrawireless.com
|
|||||
app s | Non Technical Contact | |||||
n/a | ||||||
app s | Confidentiality (long or short term) | |||||
1 | Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | No | ||||
1 | Long-Term Confidentiality Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | No | ||||
if no date is supplied, the release date will be set to 45 calendar days past the date of grant. | ||||||
app s | Cognitive Radio & Software Defined Radio, Class, etc | |||||
1 | Is this application for software defined/cognitive radio authorization? | No | ||||
1 | Equipment Class | DTS - Digital Transmission System | ||||
1 | Description of product as it is marketed: (NOTE: This text will appear below the equipment class on the grant) | Open-Source Hardware Development Platform | ||||
1 | Related OET KnowledgeDataBase Inquiry: Is there a KDB inquiry associated with this application? | No | ||||
1 | Modular Equipment Type | Does not apply | ||||
1 | Purpose / Application is for | Original Equipment | ||||
1 | Composite Equipment: Is the equipment in this application a composite device subject to an additional equipment authorization? | No | ||||
1 | Related Equipment: Is the equipment in this application part of a system that operates with, or is marketed with, another device that requires an equipment authorization? | No | ||||
1 | Grant Comments | Power output is conducted. The device has been certified for fixed and mobile uses. Any co-location must be done through the use of FCC multi-transmitter product procedures. End-users and installers must be provided with antenna installation instructions and transmitter operating conditions for satisfying RF exposure compliance. | ||||
1 | Is there an equipment authorization waiver associated with this application? | No | ||||
1 | If there is an equipment authorization waiver associated with this application, has the associated waiver been approved and all information uploaded? | No | ||||
app s | Test Firm Name and Contact Information | |||||
1 | Firm Name |
Sporton International Inc.
|
||||
1 | Name |
A**** C******
|
||||
1 | Telephone Number |
886-3********
|
||||
1 | Fax Number |
+886-********
|
||||
1 |
a******@sporton.com.tw
|
|||||
Equipment Specifications | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
1 | 1 | 15C | 2402 | 2480 | 0.009 | ||||||||||||||||||||||||||||||||||||
1 | 2 | 15C | 2412 | 2462 | 0.095 |
some individual PII (Personally Identifiable Information) available on the public forms may be redacted, original source may include additional details
This product uses the FCC Data API but is not endorsed or certified by the FCC