FCC ID: 2AKPQNDWM005 PE IoT Engine-Sub 1 GHz IPv6/6LoWPAN communication module

PE IoT Engine Datasheet PE IoT Engine Datasheet Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 1 / 30 PE IoT Engine Datasheet Table of contents 1. List of Acronyms ......................................................................................................................................................... 3 Product Description ................................................................................................................................................... 4 Architecture ............................................................................................................................................................... 6 Features ..................................................................................................................................................................... 8 Technical specifications ............................................................................................................................................. 9 6. Dimensions ............................................................................................................................................................... 12 Connectors and Switches ......................................................................................................................................... 13 Requirements of KDB 006360 D03 FCC certifications ........................................................................................... 18 Section 2.2 List of applicable FCC rules ........................................................................................................... 18 Section 2.3 Summarize the specific operation use conditions ........................................................................ 18 Section 2.4 Limited module procedures ......................................................................................................... 18 Section 2.5 Trace antenna design ................................................................................................................... 18 Section 2.6 RF exposure considerations .......................................................................................................... 19 Section 2.7 Antennas ....................................................................................................................................... 20 Section 2.8 Label and compliance information ............................................................................................... 20 Section 2.9 Information on test modes and additional testing requirements ................................................ 21 Section 2.10 Additional testing, Part 15 Subpart B disclaimer ........................................................................ 22 9. Maximum Permissible Exposure (MPE) Limits ......................................................................................................... 22 US United States ........................................................................................................................................... 23 EU Europe ..................................................................................................................................................... 23 9.2.1 Maximum Permissible Exposure (MPE) Limits ............................................................................................ 23 9.2.2 EU Declaration of Conformity ..................................................................................................................... 25 10. Certifications ......................................................................................................................................................... 26 10.1 US United States ........................................................................................................................................... 26 10.2 EU - Europe...................................................................................................................................................... 26 10.3 Symbols and Approval Marks .......................................................................................................................... 27 Ordering Codes ..................................................................................................................................................... 28 Related Documents............................................................................................................................................... 29 Revision History .................................................................................................................................................... 30 2. 3. 4. 5. 7. 8. 8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 8.9 9.1 9.2 11. 12. 13. Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 2 / 30 PE IoT Engine Datasheet 1. List of Acronyms Acronym Description AES CMS GFSK GPS HDLC LED MCU NA PCB PE RMS RTC Advanced Encryption Standard Central Management System Gaussian Frequency Shift Key Global Positioning System High-Level Data Link Control Light Emission Diode Microcontroller Unit Not Applicable Printed Circuit Board Paradox Engineering Root Mean Square Real Time Clock IPv6/6LoWPAN IPv6 over Low-Power Wireless Personal Area Networks Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 3 / 30 PE IoT Engine Datasheet 2. Product Description The PE IoT Engine is a Sub 1-GHz IPv6/6LoWPAN hardware radio communication module, as shown in Figure 1 below. The PE IoT Engine is used to build interoperable, fully customized solutions and applications for the Internet of Things

(IoT) and Smart Cities. As a communications module, the PE IoT Engine is responsible for handling all network-layer events such as joining the 6LoWPAN mesh network, sending and receiving data, and encrypting the data sent over the network. In order to utilize the capabilities of the PE IoT Engine in an IoT or Smart City application, the PE IoT Engine must be integrated into a 3rd party application board including any external sensors (or actuators) necessary for the application. Figure 1: The PE IoT Engine PE Smart Urban Network is Paradox Engineerings flagship platform to enable true Smart City applications, which gives city managers the ability to have bi-directional communication (allowing both remote sensing and remote control) to IoT devices deployed in a city environment and constructing their own private IPv6 wireless network. An example of some of the many Smart City use cases which can be realized using the PE technologies, including the PE IoT Engine, is shown Figure 2, located below. Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 4 / 30 PE IoT Engine Datasheet IPv6 6LoWPAN Wireless Mesh Network (Encrypted) Figure 2: The PE IoT Engine and Other PE Technologies Operating in a Smart City Application As an open and interoperable platform, the PE IoT Engine adopts the uCIFI standard for Smart City applications. This provides city managers the ability to use an open and standardized data model for sensor data traversing mesh network. The uCIFI standard also ensures that city managers have a well-defined interface to access their data. As depicted in Figure 2, the PE IoT Engine forms a wireless mesh network with other PE Smart devices (such as the Parking Sensor, the Lighting Node, as well as other PE IoT Engine devices). The PE IoT Engine provides city managers an interoperable, ready-to-use device to connect field objects to their network. Once connected, the IoT devices that leverage the PE IoT Engine are able to exchange data, receive commands, and execute procedures through PE Smart Gateways. All management and control is provided by the PE Smart CMS (Central Management System). Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 5 / 30 PE IoT Engine Datasheet 3. Architecture The PE IoT Engine is a communication module that allows custom, 3rd party IoT applications to have full access to a private, encrypted, self-configuring, self-healing, IPv6/6LoWPAN, wireless mesh network which can easily be deployed in city and urban environments. One of the core objectives of the PE IoT Engine is to provide hardware engineers a single module that abstracts the networking, mesh topology, IPv6 stack, and Sub 1-GHz radio protocols. Engineers have a versatile data modeling API with the embedded LwM2M engine. The PE IoT Engine supports multiple interfaces such as UART, USB, I2C, Serial, and GPIO to allow external devices to leverage the PE IoT Engine as a network communications module. PE IoT Engine consists of a single electronic printed circuit board (PCB) that includes the following:

Microcontroller unit (MCU) and flash memory RF transceiver (sub 1-GHz radio) with UFL connector for external antenna (Note: UFL antenna is not provided) Micro USB 2.0 connector External connectors (located on the bottom side) for interfacing with 3rd-party boards The electronic PCB and the physical connectors for PE IoT Engine are pictured in Figure 3 below. Figure 3: The Top, Bottom, and Side Views of the PE IoT Engine Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 6 / 30 PE IoT Engine Datasheet A high-level block diagram of the PE IoT Engine is pictured in Figure 4, located below. Figure 4: The PE IoT Engine High Level Block Diagram Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 7 / 30 UFLAntennaConnectorPowerSupplyMCU(80 MHz)RadioFlashMemory(1 MB)ExternalConnector(J1, J2)MicroUSB PortGPIOUARTSWDI2CUSB 25.0 or 3.3 VDCUSB 2ADC PE IoT Engine Datasheet 4. Features The PE IoT Engine offers the following features:

Radio communications module providing access to IPv6/6LoWPAN mesh network and highly secure communication infrastructure for bidirectional data transmission Dual inline connectors for simple integration with 3rd party boards (such as the Arduino, Raspberry Pi, and Beagle Bone platforms) HDLC over UART interface for device configuration and data communications Ability to operate in low power mode suitable for use with an (optional) external battery LwM2M engine to allow data model definition, data manipulation, and notifications via the IPv6/6LoWPAN mesh network Remote OTA firmware upgrade via the IPv6/6LoWPAN mesh network 128-bit AES encryption for all data and communications sent over the IPv6/6LoWPAN mesh network Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 8 / 30 PE IoT Engine Datasheet 5. Technical specifications Symbol Item VDD_2V 2 V Operating Supply Voltage VDD_3.3V 3.3V Operating Supply Voltage VDD_5V 5V Operating Supply Voltage VANALOG IO Pin Voltage VDIGITAL IO Pin Voltage Extended Range VBAT External Power backup for RTC VRESET Reset Pin Voltage TOTG TSTG Operating temperature range Storage temperature range

(1) Low Power Mode Table 1 Absolute Maximum Ratings Unit VDC VDC VDC VDC VDC VDC VDC C C Min. 1.9(1) 2.7 3.6 0

-0.3 1.55

-0.3

-40

-40 Typ. 3.3 2 5

3.3 Max. 2.2 3.5 6 VREF +0.3V VDD +0.3V

(5V tolerant UART1) VDD +0.3V 3.6 70 85 The power of the source that supplies the product shall be less or equal than 15 W. Table 2 I/O Operating Specification VIL VIH Symbol Item Min. Typ. Max. I/O input Low voltage I/O input High voltage VIL(RESET) Reset Low Level Voltage 0.7 x Min (VDD)

VIH(RESET) Reset High Level Voltage 0.7 x Min (VDD)

0.3 x Min (VDD) 0.3 x Min (VDD)

Unit VDC VDC VDC VDC Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 9 / 30 Table 3 Power Consumption Symbol Item Transmission

@11 dBm Reception Sleep Mode Unit mA mA uA Min.

Typ. 31 28

Max.

PE IoT Engine Datasheet IDD IDD IDD Table 4 Sub 1-GHz Radio Narrowband Interface Item Unit Description 802.15.4g 6LoWPAN RX sensitivity (BER <1%) dBm

-104 Radio protocol Radio modulation Data rate Tx bandwidth RX bandwidth Data transmission Data encryption Antenna connector GFSK kbps 100 kHz kHz 200 260

Bi-directional AES-128 bit External 50 SMA Connector Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 10 / 30 PE IoT Engine Datasheet Table 5 Sub 1-GHz Radio Narrowband Country Parameters Country Frequency band (MHz)1 Channels Ch. Spacing

(kHz) Comments US 902.42 927.58 Frequency Hopping 75 340 14 Frequency Hopping /

Single channel TX power

(dBm) EU 868.0 868.6 Single channel EU 869.525 (band P) Single channel JP 920.70 - 923.30 Single channel

14 14 13 14 3 ch., 200 kHz spacing

(868.1, 868.3 and 868.5 MHz) 1 ch., (869.525 MHz) 13 ch., 200 kHz spacing

(922.3 MHz ch. cannot be used by ARIB STD-

T108 tab. 3-12) 5 ch., 290 kHz spacing, device max TX power is 14 dBm, certification limit is 17 dBm

9 TH 920.41 - 924.59 Frequency Hopping 20 220 14 KH 923.42 - 924.58 Single channel PH 915.42 - 917.58 Frequency Hopping 270 14 Item USB Serial Port SWD GPIO ADC UART I2C Table 6 I/O Operating Specifications Digital Interfaces Description USB 2.0 for Serial Communication and Firmware Upgrade 115200/N/8 For debugging and programming purposes Up to 14 General Purpose Digital IO Up to 2 Analog/Digital Converter Single-ended I2C (Inter-Integrated Circuit) interface Tx / Rx 1 The values indicate the carrier frequency of the lowest and the highest channels Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 11 / 30 PE IoT Engine Datasheet 6. Dimensions Mechanical dimensions of PE IoT Engine are pictured in Figure 5 below. Figure 5: Dimension Views of the PE IoT Engine in Millimeters Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 12 / 30 PE IoT Engine Datasheet 7. Connectors and Switches Table 7 List of Connectors Description Name J1 J2 J3 J18 2x10 pins male connector, 2.54 mm pitch, mounted on the bottom side 2x10 pins male connector, 2.54 mm pitch, mounted on the bottom side Micro USB female connector UFL female connector for RF antenna J2 Header J1 Header J3 Header Figure 6: Bottom View with J1, J2, and J3 Headers Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 13 / 30 Table 8 List of Switches Description Soft RESET Push the button to RESET the device BOOT0 Move the switch to the right to activate the bootloader V_ADC Move the switch to the right to supply external power to the ADC. Move the switch to the left to enable VCC to supply power to the ADC. VMAIN Move the switch to the right to enable low power mode and bypass the protection diode VBAT - Move the switch to the right to enable the PE IoT Engine to use externally supplied power

(such as from a battery). Move the switch to the left to enable VCC to supply power to the VBAT pin J18 Header PE IoT Engine Datasheet Name SW1 SW2 SW3 SW4 SW5 SW4 Switch SW3 Switch SW2 Switch SW1 Switch SW5 Switch Figure 7: Top View with J18 Header and SW1, SW2, SW3, SW4, and SW5 Switches Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 14 / 30 LD1 LED PE IoT Engine Datasheet Name LD1 Table 9 List of LEDs Description This LED is always ON if the PE IoT Engine is powered with 5 VDC or USB power. In other power configurations, the LED is OFF to save power. Figure 8: Top View LED LD1 Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 15 / 30 Table 10 Pinout of J1 Connector Name Type Description Reference V_BAT Power Optional external backup battery PE IoT Engine Datasheet PIN 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 GPIO_14 I2C SDL GPIO_9 GPIO_11 RXD GPIO_12 TXD GPIO_13 USB_N I2C SDA USB_P USB OTG SWDIO GPIO_8 SWCLK I/O I/O I/O I/O O I/O I I/O I/O I/O I/O I/O I/O I/O I I General purpose input/output I2C data General purpose input/output General purpose input/output Serial Interface for debugging General purpose input/output Serial Interface for receiving General purpose input/output USB data I2C clock USB data+

USB OTG Serial wire I/O General purpose input/output Serial wire clock GPIO_10 I/O General purpose input/output RESET Reset input, active low, internal pull-up PWR_MON O Power ON monitor, goes high if the module is powered on, goes low if the module is not powered GND Power Ground VBAT VDIGITAL VDIGITAL VDIGITAL VDIGITAL VDIGITAL VDIGITAL VDIGITAL VDIGITAL VDIGITAL VDIGITAL VDIGITAL VDIGITAL VDIGITAL VDIGITAL VRESET VDIGITAL

Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 16 / 30 PE IoT Engine Datasheet Table 11 Pinout of J2 Connector PIN 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 T

+5V_DB

+3.3V_DB GPIO_3 GPIO_7 ON/OFF

+5V_DB GPIO_5 GPIO_6 RX_AUX GPIO_2 TX_AUX GPIO_4 DTR GPIO_1 RI Name Type Description Reference Power 5V Input Voltage from external source VDD_5V Power 3.3V Input Voltage from external source VDD_3.3V, VDD_2V General purpose input/output UART1_RX HDLC Serial data input VDIGITAL Not 5 V tolerant) VDIGITAL ADC_INPUT_02 ADC input ADC_INPUT_01 ADC input General purpose input/output Input for switching ON or OFF the module Power 5V Input Voltage from external source General purpose input/output General purpose input/output Auxiliary serial data input for debug/test General purpose input/output Auxiliary serial data output for debug/test General purpose input/output Data terminal ready from DTE General-purpose input/output Ring indicator to DTE VDIGITAL VDIGITAL VDD_5V VDIGITAL VDIGITAL VDIGITAL VDIGITAL VANALOG VDIGITAL VDIGITAL VDIGITAL VDIGITAL VDIGITAL

UART1_TX HDLC Serial data output GND Power Ground VDIGITAL Not 5 V tolerant)

I/O I/O I/O I I/O I/O I/O I I/O I/O O I/O I I/O O I/O Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 17 / 30 PE IoT Engine Datasheet 8. Requirements of KDB 996369 D03 FCC certifications 47 CFR FCC part 15.247 , subpart C (radio) 47 CFR FCC 47 part 2 - 2.1093 (maximum permissible exposure) Section 2.2 List of applicable FCC rules The following standard apply to the module:

- KDB 558074 D01

- ANSI C63.10:2013

- Title 47 Part 1 Subpart I 1.1310

- Title 47 Part 2 Subpart J 2.1091

- ANSI C63.4:2014 8.1 8.2 Section 2.3 Summarize the specific operation use conditions The PE IoT Engine is used in the Internet of Things (IoT) and Smart Cities contexts. As a communications module, the PE IoT Engine is responsible for handling all network-layer events such as joining the 6LoWPAN mesh network. The module is required to be integrated into a 3rd party application equipment. In its standard use, it is not intended to be used in point-to-point applications. As a consequence, the typical antennas to be used are low-gain antenna. In addition, the maximum theoretical TX power is physically limited to 14 dBm. The FCC limit in the (902 928) MHz band 1 W (30 dBm) and it is not possible to overcome that limit. 8.3 Section 2.4 Limited module procedures Not applicable. 8.4 Section 2.5 Trace antenna design Not applicable, the radio module does not have any trace antenna design. Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 18 / 30 PE IoT Engine Datasheet 8.5 Section 2.6 RF exposure considerations The following tables summarize the results of the calculations carried out assuming no co-location or operation in conjunction with any other antenna or transmitter. It is also indicated the minimum distance to keep between antennas and the public:

Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 19 / 30 PE IoT Engine Datasheet Notice Changes or modifications made to this equipment not expressly approved by Paradox Engineering may void the users authority to operate this equipment. Radiofrequency radiation exposure information This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with minimum distance of 5mm between the radiator and your body. This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter. Product 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. 8.6 Section 2.7 Antennas The module has been certified with the following antennas:

The module is provided by a U.FL connector. 8.7 Section 2.8 Label and compliance information Linx Technologies, ANT-916-CW-HW (ANT-OUT-0027), dipole antenna, 1.2 dBi

- Molex, 2067640100 (ANT-IND-0006), patch antenna, 1.2 dBi According KDB 784748 the end-user or the integrator of this module shall use a physical label stating Contains Transmitter Module FCC ID: 2AKPNDWM005 or Contains FCC ID: 2AKPNDWM005. Page 20 / 30 Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

PE IoT Engine Datasheet 8.8 Section 2.9 Information on test modes and additional testing requirements See test report FCCTR_178784_0 and MPETR_178785_0. Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 21 / 30 PE IoT Engine Datasheet 8.9 Section 2.10 Additional testing, Part 15 Subpart B disclaimer Please refer to test report FCCTR_178784_0 and MPETR_178785_0. The module is FCC Part 15 Subpart B compliant and the modular transmitter is only FCC authorized for the specific rule parts listed on the grant. The host product manufacturer is responsible for compliance to any other FCC rules that apply to the host not covered by the modular transmitter grant of certification. The final host product still requires Part 15 Subpart B compliance testing with the modular transmitter installed. Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 22 / 30 PE IoT Engine Datasheet 9. Maximum Permissible Exposure (MPE) Limits The PE IoT Engine is compliant to Maximum Permissible Exposure (MPE) limits. 9.1 US United States See section 8.5 Section 2.6 RF exposure considerations. 9.2 EU Europe Table 12 MPE Limits 9.2.1 Maximum Permissible Exposure (MPE) Limits Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 23 / 30 PE IoT Engine Datasheet Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 24 / 30 PE IoT Engine Datasheet 9.2.2 EU Declaration of Conformity Paradox Engineering declares that PE IoT Engine is compliant within the 2014/53/EU directive. The full Declaration of Conformity is available at the following link:

hiips://www.pdxeng.ch/certification/t6Ybbh8ojS.pdf Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 25 / 30 PE IoT Engine Datasheet 10. Certifications 10.1 US United States 10.2 EU - Europe 2014/53/EU 2011/65/EU 2015/863/EU Standard ETSI EN 300 220-2 ETSI EN 301 489-1 ETSI EN 301 489-3 IEC EN 62368-1 EN 62311 Table 13 Reference Standards of the United States Standard Title FCC 47 CFR part 15 FCC 47 CFR Part 15, Subpart C - Intentional Radiators Table 14 Directives of Europe Directive Title Directive on the harmonization of the laws of the Member States relating to the making available on the market of radio equipment and repealing Directive 1999/5/EC DIRECTIVE 2011/65/EU OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 8 June 2011 on the restriction of the use of certain hazardous substances in electrical and electronic equipment Commission delegated directive amending Annex II to Directive 2011/65/EU of the European Parliament and of the Council as regards the list of restricted substances Table 15 Reference Standards of Europe Title Short Range Devices (SRD) operating in the frequency range 25 MHz to 1 000 MHz; Part 2: Harmonized Standard covering the essential requirements of article 3.2 of Directive 2014/53/EU for non specific radio equipment Electromagnetic Compatibility (EMC) standard for radio equipment and services Part 1: Common technical requirements; Harmonized Standard covering the essential requirements of article 3.1(b) of Directive 2014/53/EU and the essential requirements of article 6 of Directive 2014/30/EU Electromagnetic Compatibility (EMC) standard for radio equipment and services;

Part 3: Specific conditions for Short-Range Devices (SRD) operating on frequencies between 9 kHz and 246 GHz; Harmonized standard covering the essential requirements of article 3.1(b) of Directive 2014/53/EU Audio/video, information and communication technology equipment Part 1: Safety requirements Assessment of the compliance of low-power electronic and electrical equipment with the basic restrictions related to human exposure to electromagnetic fields

(10 MHz to 300 GHz) Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 26 / 30 PE IoT Engine Datasheet 10.3 Symbols and Approval Marks Approval Issued by Certificate No. Table 16 Approval Marks Declaration of Conformity: In progress In progress FCC ID: 2AKPQNDWM005 Table 17 Symbols Approval Description RoHS compliant, refer to [OD_1]

WEEE Directive compliant, refer to [OD_1]

Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 27 / 30 PE IoT Engine Datasheet 11. Ordering Codes Model Name Country code NDWM005 US US - United States NDWM005 EU EU - Europe NDWM005 CL CL Chile NDWM005 JP JP Japan NDWM005 TH TH Thailand NDWM005 KH KH Korea NDWM005 PH PH Philippines Table 18 Ordering Codes Part No. PRD-CMD-0002 PRD-CMD-0001 TBD TBD TBD TBD TBD Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 28 / 30 PE IoT Engine Datasheet 12. Related Documents Table 19 Related Documents Item Document Number Document Title/Description

[PD_1]

DOC-SW-ETC-2011 PE IoT Engine HDLC Interface Guide

[PD_2]

DOC-SW-AN-2017 LwM2M Reference Application

[OD_1]

EM10507 MinebeaMitsumi Group Green Procurement Standard Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 29 / 30 PE IoT Engine Datasheet 13. Revision History Revision Document No. Date Description 00 DOC-DAT-0023-00 M. Semmoloni 21.06.2019 First document release. 01 DOC-DAT-0023-01 12.11.2019 02 DOC-DAT-0023-02 12.05.2020 Added additional images 03 DOC-DAT-0023-03 11.12.2020 Updated all sections for PE IoT Engine Changed USB mini to micro Updated J1 and J2 headers for serial use Updated all sections for PE IoT Engine for the latest version. Included a new table for switches Updated all photos. Added a new section for the MPEs. Updated table 5, sub 1-GHz params. Added the EU directive. Updated the ordering codes. Updated Tables 1,2,3, 5, 9, 10 Added KDB 006360 D03 section to comply FCC certification Created by Verified by Approved by R. Palmiero G. Galabro B. Hopkins R. Palmiero M. Parnisari B. Hopkins R. Palmiero M. Parnisari B. Hopkins R. Palmiero M. Parnisari B. Hopkins R. Palmiero M. Parnisari 04 DOC-DAT-0023-04 04.03.2021 PARADOX ENGINEERING Via Passeggiata 7, CH-6883 Novazzano, Switzerland Email: info@pdxeng.ch Phone: +41 91 233 0100 Fax:+41 91 233 0101 Website: www.pdxeng.ch The information contained in this document is strictly confidential and intended for the addressee only. The information may be subject to change without notice. The unauthorized use, disclosure, copying, alteration or distribution of this document is strictly prohibited. Document No. [DOC-DAT-0023-04] Date of last revision [04.03.2021]

Page 30 / 30

FCC ID: 2AKPQNDWM005 Paradox Engineering SA Via Passeggiata 7, Novazzano, Switzerland Phone: +41 91 233 0100 info@pdxeng.ch www pdxeng ch

FCC ID: 2AKPQNDWM005 Paradox Engineering SA Via Passeggiata 7, Novazzano, Switzerland Phone: +41 91 233 0100 info@pdxeng.ch www pdxeng ch

> PARADSX ENGINEERING Minebeatiitsumi Group Authority to Act as Agent Date: 24.04. 2021 Subject: Authority to Act as Agent for: 2AKPQNDWM005 American Certification Body, Inc. 6731 Whittier Avenue Suite C110 McLean, VA 22101 To Whom It May Concern:

PRS Lab / Riccardo Pfeiffer is authorized to act on our behalf, until otherwise notified, for applications to American Certification Body, Inc. (ACB). We certify that we are not subject to denial of federal benefits, that includes FCC benefits, pursuant to Section 5301 of the Anti-Drug Abuse Act of 1988, 21 U.S.C. 862. Further, no party, as defined in 47 CFR 1.2002 (b), to the application is subject to denial of federal benefits, that includes FCC benefits. We also declare that the information provided to the FCC is true and correct to the best of our knowledge (47 CFR 2.911(d)) and we have been informed of the grantee responsibilities (47 CFR 2.909) with regard to certified equipment. Thank you, Agency Agreement Expiration Date: end of May 2021 By: f- Bee Giovanni Minetti Z pistatme) (Print name) Title: CEO On behalf of: Paradox Engineering SA Telephone: +41 91 233 0100

(> Paradox Engineering SA Via Passeggiata 7, Novazzano, Switzerland + Phone: +41 91 233 0100 info@pdxeng.ch: www.pdxeng.ch

Minebeatitsumi Group Request for Confidentiality Subject: Confidentiality Request for: 2AKPQNDWMO005 Pursuant to FCC 47 CRF 0.457(d) and 0.459 and IC RSP-100, Section 6.4, the applicant requests that a part of the subject FCC application be held confidential. Type of Confidentiality Requested Exhibit

(] Short Term Permanent Block Diagrams LJ Short Term External Photos

(Short Term (1 Permanent* Internal Photos

(J Short Term KX] Permanent Operation Description/Theory of Operation LJ Short Term KX] Permanent Parts List & Placement/BOM

(1 Short Term L_] Permanent Tune-Up Procedure

[_] Short Term XX] Permanent Schematics L_] Short Term Test Setup Photos

[] Short Term Permanent User's Manual Paradox Engineering SA has spent substantial effort in developing this product and it is one of the first of its kind in industry. Having the subject information easily available to "competition" would negate the advantage they have achieved by developing this product. Not protecting the details of the design will result in financial hardship. Permanent Confidentiality:

The applicant requests the exhibits listed above as permanently confidential be permanently withheld from public review due to materials that contain trade secrets and proprietary information not customarily released to the public. Short-Term Confidentiality:

The applicant requests the exhibits selected above as short term confidential be withheld from public view for a period of ___ (specify number of days not to exceed 180)?__ days from the date of the Grant of Equipment Authorization and prior to marketing. This is to avoid premature release of sensitive information prior to marketing or release of the product to the public. Applicant is also aware that they are responsible to notify ACB in the event information regarding the product or the product is made available to the public. ACB will then release the documents listed above for public disclosure pursuant to FCC Public Notice DA 04-1705. NOTE for Industry Canada Applications:

IC currently only distinguishes Permanent Confidentiality exhibits as shown above. Short Term confidentiality is not ome applicable to IC applications. Sincerely, Giovanni Minetti By: .

(Signature/Title?) (Print name)

- The asterisked items (*) require further information to be provided to ACB before permanent confidentiality will be extended to these exhibits. Please refer to FCC KDB 726920 and the specific Document link for D01 found at:

httos://apos.fec.gov/oetcf/kdb/forms/FTSSearchResultPage.cfm?switch=P&id=41731 and review section V regarding EXCEPTIONAL CIRCUMSTANCES. As of the October 2014 version of this document, TCBs can not authorize these requests. The applicant should petition the FCC by submitting an inquiry as directed. A copy of this inquiry and the FCC's response must be provided with the application.

? - Please refer to e/ fa com/do isc- Memo-Short-Term-Vs-Standard-Confidentiality.pdf for complete details. 2 - Must be signed by applicant contact given for applicant on the FCC site, or by the authorized agent if an appropriate authorized agent letter has been provided. Letters should be placed on appropriate letterhead. Paradox Engineering SA Via Passeggiata 7, Novazzano, Switzerland + Phone: +41 91 233 0100 + info@pdxeng.ch: www.pdxeng.ch

PARA DEX ENGINEERI MINEBEAMITSUMI {NG 1) The radio elements must have the radio frequency circuitry shielded. Physical components and tuning capacitor(s) may be located external to the shield, but must be on the module assembly The radio module elements have their own shielding as shown in the pictures below. 2) The module must have buffered modulation/data inputs to ensure that the device will comply with Part 15 requirements with any type of input signal;

The radio transmitter has buffered modulation/data inputs (if such inputs provided) to ensure that the module will comply with part 15 requirements under conditions of excessive data rates or over-modulation. 3) The modular transmitter must have its own power supply regulation. The radio module contains an own voltage regulation 4) The module must contain a permanently attached antenna, or contain a unique antenna connector, and be marketed and operated only with specific antenna(s), per 15.203, 15.204(b), 15.204(c), 15.212(a), 2.929(b);

The module complies with the antenna and transmission system requirements of 15.203, 15.204(b) and 15.204(c), an U.FL connector is used. 5) The module must demonstrate compliance in a stand-alone configuration;

The radio module meets the requirements under the operating conditions in which the transmitter will be used. The modular transmitter was tested in a stand-alone configuration. Any accessories, peripherals, or support equipment connected to the module during testing were unmodified and commercially available. 6) The module must be labeled with its permanently affixed FCC ID label, or use an electronic display

(see KDB Publication 784748);

The radio module is labelled with its own FCC ID number. 7) The module must comply with all specific rules applicable to the transmitter, including all the conditions provided in the integration instructions by the grantee;

The radio module is compliant with all applicable specific FCC rules or operating requirements that ordinarily apply to a complete transmitter. Detailed instructions are provided with the module to explain any such requirement 8) The module must comply with RF exposure requirements The modular transmitter complies with any applicable RF exposure requirements in its final gonfiguration. Date CU /M / Z020 Signature Paradox Engineering SA Registered & Head Office: web: www.pdxeng.ch Via Passeggiata 7 e-mail: info@pdxeng.ch CH-6883 Novazzano ph: +41 91 233 01 00 Switzerland fax: +41 91 233 01 00 Paradox Engineering SA Registered & Head Office:

la Passeggiata 7 6883 Novazzano Switzerland web:

Wwww.pdxeng.ch info@pdxeng.ch

- +471 91 233 01 OO fax: +41 91 233 01 00 PARADDX ENGINEERING MINEBEAMITSUMI GRouP aati lt

S eee ede)

ie