FCC ID: 2APCX-TNLFIW10 WIFI-BLE-NFC IOTIZE MODULE

Standardized secure, turnkey solutions for management of IoT connectivity TapNLink TnL-FIW10x

(Wi-Fi, BLE, NFC) Datasheet 12 November 2019 Version 1.3 Contents 1 Introduction.......................................................................................................................................... 4 2 Summary............................................................................................................................................. 5 3 Block schematic................................................................................................................................... 6 4 Development environment................................................................................................................... 7 4.1 TapNLink module configuration.................................................................................................... 7 4.2 Mobile device software................................................................................................................. 7 5 Features.............................................................................................................................................. 8 5.1 Communication channels.............................................................................................................. 8 5.1.1 Near Field Communication (NFC).......................................................................................... 8 5.1.2 Wi-Fi...................................................................................................................................... 8 5.1.3 Bluetooth Low enrgy (BLE).................................................................................................... 8 5.2 Target system interface................................................................................................................ 8 5.3 Security features........................................................................................................................... 9 5.3.1 Access control configuration.................................................................................................. 9 5.4 Electrical characteristics............................................................................................................... 9 5.4.1 Power supply......................................................................................................................... 9 5.4.2 Digital levels........................................................................................................................... 9 5.5 RF specifications.......................................................................................................................... 9 5.6 Mobile device support................................................................................................................. 10 5.7 Cloud support............................................................................................................................. 10 5.8 Operating temperature range...................................................................................................... 10 6 Pin assignment.................................................................................................................................. 11 6.1 J1 pinout..................................................................................................................................... 11 6.2 J3 pinout..................................................................................................................................... 12 6.3 P1 extension connector.............................................................................................................. 12 7 Regulatory compliance...................................................................................................................... 13 7.1 CE certification (Europe)............................................................................................................. 13 7.2 FCC (USA) and IC (Canada)...................................................................................................... 13 7.2.1 FCC Part 15 compliance statement.....................................................................................13 7.2.2 ISED - Industry Canada Licence-Exempt Radio Apparatus.................................................13 7.2.3 ISED - Industrie Canada appareil radio exempts de licence................................................14 7.2.4 Radio Frequency (RF) Exposure Compliance of Radio communication for mobile Apparatus

...................................................................................................................................................... 14 7.2.5 Conformit lexposition aux champs RF des quipements radio mobiles.........................14 7.2.6 End Product Labeling........................................................................................................... 14 7.2.6.1 FCC Certification...........................................................................................................14 TnL-FIW103 Datasheet 2 7.2.6.2 ISED Certification..........................................................................................................14 7.2.7 End Product Users Manual:................................................................................................ 14 8 Mechanical characteristics................................................................................................................. 15 8.1 Module dimensions..................................................................................................................... 15 8.2 Standard plastic case.................................................................................................................. 15 8.3 Ordering Codes and Options...................................................................................................... 16 TnL-FIW103 Datasheet 3 1 Introduction IoTize offers a complete solution for instant integration of wireless connectivity that links electronics to mobile devices and the Cloud. This solution is inspired by the advantages of adding network connectivity without redesigning existing systems or recoding their firmware. It supports integrators with software and features for instant creation of customized Human Machine Interfaces (HMI) that run on mobile devices, configurable access control, security and Cloud integration. The TapNLink line uses technologies and techniques that are typically reserved for system programming and debugging to connect directly the target systems microcontroller. This unique approach makes it possible to add connectivity without redesigning the system. It speeds integration, eliminates risks and delivers design flexibility through encapsulation of complex wireless communication, network and security technologies. This facilitates the initial integration, but also makes it possible to easily evolve the wireless connection to meet future needs or technology evolutions... and still without ever recoding the system's original software. TapNLink provides fully qualified wireless implementations. These allow local connection to mobile devices (smartphones, PDAs, tablets, PCs, etc.) allowing users to monitor or update a system and transfer data to the Cloud if/when necessary. Depending on the connectivity channels on the module, TapNLink can also enable connection to WAN or LPWAN for remote supervision and remote access control from the Cloud. For the embedded application, TapNLink enables:

Mobile device-based HMI Data transfer to the internet TapNLink provides software and hardware encapsulation of the mobile device / target application communication. It manages communication with:

Target application via hardware module RF interface(s) and communication co-

processor Mobile devices via a low-level service application TnL-FIW103 Datasheet 4 2 Summary The TapNLink Wi-Fi, Bluetooth Low Energy (BLE), NFC module (Part N: TnL-FIW103) offers instant integration of contactless/radio interfaces to enable the connection of a microcontroller-

based target system to a local information appliance (smartphones, PDAs, tablets, PCs, etc.). TapNLink connects directly the microcontroller of the target system and allows non-intrusive read and/or write access to variables in the target microcontrollers memory. The data addresses and access parameters for the target system are configured in the TapNLink. No coding of the target systems native functionality is required to connect TapNLink to the target microcontroller. TapNLink supports local connection to mobile devices (Android or iOS, Windows 10), where data can be viewed and modified via a graphical user interface created by the target system designer. The solution includes MQTT infrastructure to enable data transmission via the local mobile device to any Cloud-based IoT platform. Data that is read by the TapNLink can be transmitted via the mobile devices data or network connection when available. For this, IoTize provides an MQTT-base relay with IoT Cloud platform translators. This MQTT infrastructure is open source software that target system designers can install on servers and adapt to any private or public IoT Cloud platform. Communication Channels Near Field Communication (NFC) Type5 tag (ISO/IEC 15693) Wi-Fi 802.11b/g/n Bluetooth Low Energy (BLE) 4.2 Target system interface protocols SWD debugging/programming interface protocol Software Secure Serial Port (S3P) Security features Configurable access profiles Configurable, encrypted passwords AES-128 module-level data encryption Configurable secure pairing with NFC Configurable target memory access controls Accessible data addresses:

up to ~ 500 User profiles:

up to ~ 100 Access capabilities:

Read or Write or Read/Write Electrical characteristics Input voltage:

2.3V to 3.6V Low power consumption:

Standby:

NFC:

o Wi-Fi Rx:

o Wi-Fi Tx:

o o o 100 A 7 mA 50 mA 110 mA (802.11g) Mechanical characteristics BLE Tx/Rx:

65 mA Dimensions:

28 x 38 x 3 mm Package options Bare board Plastic casing (IP44) Silicone resin (IP65) Operating temperature range

-20C, +55C Acceptance CE (Europe), FCC (USA), IC (Canada). REACH and RoHS compliant TnL-FIW103 Datasheet 5 3 Block schematic The TapNLink Wi-Fi, BLE, NFC module is equipped with an ESP32 microcontroller that executes:

1. The main program 2. Manages the upper level protocols 3. Manages the configuration and access control 4. Manages the Wi-Fi or BLE stack and acts as a simple transmitter. The circuitry for both the NFC and the Wi-Fi/BLE antennas are outside of the shielding case. The NFC antenna is a trace at the periphery of the printed circuit board. The 2.45 GHz antenna is a ceramic device located close to the L slot in the printed circuit board. Internal 2.45GHz RF antenna Shielding case Flash RF Matching ST25 Internal 13.56MHz NFC antenna Extension connectors ESP32 Target connectors TnL-FIW103 Datasheet 6 4 Development environment 4.1 TapNLink module configuration TapNLink is implemented by configuration only using the free IoTize Studio software environment, which is available on the IoTize website. IoTize Studio provides a simple yet complete interface for managing the configuration of IoTize radio modules so that they interface correctly with the target system. IoTize Studio provides:

Drag-and-drop configuration of target data addresses using the target systems source code (ELF files) Instant configuration transfer without extensive hardware installations Immediate configuration verification on the designers PC and mobile device When creating the TapNLink configuration, the designer imports the target system's firmware source (ELF file). Designating the addresses to access via TapNLink is as easy as dragging-

and-dropping them into the configuration project. All variable information (address, type, etc.) is copied directly from the firmware source file, greatly reducing the risk of configuration errors. IoTize Studio also notifies the designer if the firmware source file is modified after the configuration has been created. IoTize Studio allows users to transfer their configuration for testing and deployment with just the click of a button. No complicated or expensive hardware is required. After configuration, the designer can connect to the module and visualize in IoTize Studio the results of the configuration. The integrated app viewer in IoTize Studio shows the resulting user app exactly as it would display on a mobile device. When the designer is satisfied with the configuration, visualizing the result on a mobile device requires only that the designer connect it to the TapNLink via one of the supported radio interfaces. IoTize Studio and TapNLink are designed to allow the transfer of the Designers configuration using a direct Wi-Fi or BLE connection with the designers PC, or via a mobile device connection either directly with the designer's PC or IoTizes Cloud-based MQTT relay. Thanks to this implementation no additional hardware is required during the design phase. 4.2 Mobile device software Various application notes are available at the IoTize website to describe how to design HTML pages to monitor the TapNlink from a mobile device. APIs for native programs are also available. TnL-FIW103 Datasheet 7 5 Features The TapNLink NFC, Wi-Fi, BLE module (root part number: TnL-FIW103) offers instant integration of contactless/wireless radio interfaces to enable the connection of a microcontroller-

based target system to a local mobile device (smartphone, PDA, tablet, PC, etc.). TapNLink connects directly to two GPIOs on the microcontroller in the target system. These GPIOs can be either the target microcontrollers debugging/programming port (ex. SWD) or any pair of GPIOs enabled by the IoTize S3P protocol (application relinking is required). The connection to the target microcontroller is non-intrusive and allows read and/or write access to variables in the target microcontrollers memory. The data addresses and access parameters for the target system are configured in the TapNLink using the IoTize Studio configuration environment. TapNLink communicates with local mobile devices via their NFC and/or Wi-Fi or BLE interfaces. The Tap Manager app (Android or iOS) on the mobile device manages its communication interfaces, thus eliminating the need for the target-system designers to code or validate these mechanisms. Designers instead focus on creating the user interface for the target system. With TapNLink NFC, Wi-Fi, BLE modules, a local mobile device can serve as a network gateway to bring data to or retrieve data from the Cloud. Data that is read by the TapNLink can be transmitted via the mobile devices data or network connection when available. For this, IoTize provides an MQTT-based relay with IoT Cloud platform translators. This MQTT infrastructure is open source software that designers can install on servers and adapt to any private or public IoT Cloud platform. 5.1 Communication channels 5.1.1 Near Field Communication (NFC) Data transmission rate1:

Range2:

Supports use of NFC for dynamic wakeup and pairing of the Wi-Fi interface. 2 kilobytes per second to 4 centimeters 5.1.2 Wi-Fi Max power:

Data transmission rate1: DSSS, 1Mbps ; OFDM, 54 Mbps ;

Range2:

16 dBm (Conducted power) to 30 meters 5.1.3 Bluetooth Low enrgy (BLE) Max power: 3 dBm (Conducted power) Data transmission rate1:

0.5 kilobytes per second Range2:

to 30 meters Notes:

1. Average speed while acquiring 1000 times 220 bytes from the target. 2. Measured line-of-site in an environment free of obstructions and rebound effects. 5.2 Target system interface Requires 2 GPIO enabled by the target microcontrollers debug protocol or IoTize Simulated Secure Serial Port (S3P). TnL-FIW103 Datasheet 8 5.3 Security features Customized firmware allows differentiated algorithms for each application. The communication chain is fully secured using classic techniques such as:

Authentication:

secured passwords or signed tokens Encryption:

AES-128 When implementing on GPIO that are enabled by the target microcontrollers debug protocol, data encryption is enabled to the level of the TapNLink module. When implementing with S3P protocol, security features can be implemented on the target microcontroller. Features include data encryption and filtering of accessible addresses in the targets memory space. 5.3.1 Access control configuration IoTize stores access control data in 2KB of EPROM:

Accessible data addresses:

User profiles:

up to ~ 500 up to ~ 100 Read/Write Access rights:

Plus 3 predefined profiles of up to 96 characters. 5.4 Electrical characteristics 5.4.1 Power supply Maximum DC supply voltage DC supply voltage 3.6V 2.3V to 3.6V Low power consumption:

o Standby:

o NFC:

o Wi-Fi Rx:

o Wi-Fi Tx:

o BLE 100 A 7 mA 50 mA 110 mA (802.11g) Tx/Rx:

65 mA When in standby mode, wake up of the Tap is possible using NFC. 5.4.2 Digital levels Maximum voltage on input/output Minimum voltage on input/output Vcc + 0.3V

- 0.3V Input low voltage (max) Input high voltage (min) 0.25 x Vcc 0.75 x Vcc 5.5 RF specifications For details, see ESP32 specifications. Parameter Frequency range Rx sensitivity(1) Wi-fi Output power(1) range Wi-fi RX sensitivity BLE @0.1% BER Output power range BLE

(1) Typical value, depend type of modulation. Min 2402 Typ

-93 16.0

-94 3.0 Max 2480 17.0 Unit MHz dBm dBm dBm dBm TnL-FIW103 Datasheet 9 5.6 Mobile device support TapNLink includes radio implementations for NFC, Wi-Fi and BLE, which are compatible with a wide range of mobile devices running Android or iOS operating systems. The Tap Manager app manages the radio interfaces on mobile devices running Android v4.0.3 and iOS v10 or later versions. 5.7 Cloud support TapNLink includes an open source MQTT relay. Designers using TapNLink are free to copy and adapt this to meet their specific requirements for data exchanges with IoT Cloud platforms. Full information about IoTize Cloud support for TapNLink is provided in the IoTize MQTT Relay User Manual. 5.8 Operating temperature range The behavior and the radio characteristics have been tested to guarantee a correct operation in the range [-20C, +55C]. TnL-FIW103 Datasheet 10 6 Pin assignment The TapNLink Wi-Fi/NFC module has 3 connectors:

J1 (2x5 in 1.27mm steps) which connects the TapNLink to the debug connector (ARM-

SWD standard) of the target board via a flex cable (in 0.635mm steps). J3 (1x5 in 2.54mm steps) which connects the TapNLink to the target board using free wires that need not be grouped in a ribbon cable or with a single end connector. Note that J3 is a subset of J1. P1 extension connector which is composed of two rows of contacts (P1A and P1B) with 2mm spacing. This connector is mainly reserved for the addition of expansion cards and is only briefly described in this document. The following figure shows (bottom view) the signals connected to J1 and J3:

6.1 J1 pinout This connection corresponds to the format specified by ARM for Cortex-M microcontrollers Vcc 1 2 S3PIO/SWDIO (TMS) Gnd 3 4 S3PCLK/SWDCLK (TCK) Gnd 5 6 SWO (TDO) Not connected 7 8

-- (TDI) Gnd 9 10 nRST Note:

The names in parentheses correspond to the JTAG protocol. In general, it is advisable to priviledge using SWD over JTAG for Cortex M-based microcontrollers. For any other microcontroller, use the S3P protocol. The signals to be connected in SWD or S3P are:

Gnd Vcc (the target must provide the TapNLink power), S3PIO/SWDIO, a bi-directional data signal. S3PCLK/SWDCLK, the clock signal, bi-directional in S3P. NRST: Reset signal of the target processor. Its connection is optional. It should be maintained if you want to use the reset command, or if you want to use TapNLink as a programmer (the reset signal is required in some programming situations). TnL-FIW103 Datasheet 11 6.2 J3 pinout J3 was added for practical reasons. The 2.54 mm step connectors are cheaper and more robust and can connect to a wide range of other connectors. It is easier to use this connector to connect to the 20-point ARM 2.54mm-step standard. J3 does not correspond to a standard. It contains the main signals necessary for the S3P and SWD protocols:

Vcc 1 Gnd 2 S3PIO/SWDIO 3 S3PCK/SWDCK 4 nRST 5 6.3 P1 extension connector P1 extension connector is composed of two mechanically independent parts:

PA1 has 12 points PA2 has 12 points. The two additional points are used exclusively for initial programming. Most of the signals on the expansion connector are reserved for extensions proposed by IoTize, so this connector will only be used in exceptional situations, for example, if it is necessary to control the reset of the TAP. The figure below shows the position of the TapNLinks power, reset and wakeup points. GND/PA1.12 PA2.12 /VCC PA1.11 PA1.10 PA1.9 PA1.8 PA1.7 PA1.6 PA1.4 PA1.3 PA1.2 Vcc / PA1.1 Tap_nRST / PA1.5 PA2.11 PA2.10 PA2.9 PA2.8 PA2.7 PA2.6 PA2.5 PA2.4 PA2.3 / Tap_Wakeup PA2.2 PA2.1 / GND TnL-FIW103 Datasheet 12 7 Regulatory compliance Changes or modifications not expressly approved by IOTIZE S.A.S. could void the users authority to operate the equipment. TapNLink TnL-FIW10x is tested and qualified under the following standards:

7.1 CE certification (Europe) The TapNLink TnL-FIW10x operating range corresponds to:

o Frequency Band: 2402-2480MHz (BLE) / 2412-2472MHz (WIFI) o Maximum Transmitting Power: Wi-fi 17.4mW and BLE 0.5mW (EIRP) This device has been tested and certified for use in the European Union and IOTIZE hereby declares that the device TapNLink TnL-FIW10x is in conformity with the essential requirements of Directive RED 2014/53/EU. The complete Declaration of Conformity can be found at:

o Appendix 1 of the present notice, o www.iotize.com for the electronic version. If this device is used in a product, the OEM is responsible for verifying compliance of the final product with the relevant EU standards. A Declaration of Conformity must be issued and kept on file. The CE mark must be placed on the OEM product per the labeling requirements of the Directive. 7.2 FCC (USA) and IC (Canada) 7.2.1 FCC Part 15 compliance statement

- 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.

- This module has been approved under FCC part 15C 15.247. This modular transmitter is only FCC authorized for this specific rule part.

- The module is limited to OEM installation ONLY.

- The OEM integrator is responsible for ensuring that the end-user has no manual instruction to remove or install module.

- 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. (For example, Part 15 Subpart B)

- If testing of the host product with this transmitter installed and operating is necessary (to verify that the host product meets all the applicable FCC rules), a test mode for this specific module is available upon request to IOTIZE.

- Trace antenna design, list of antenna type approved and professional installation is not applicable to this modular certification. 7.2.2 ISED - Industry Canada Licence-Exempt Radio Apparatus This device contains licence-exempt transmitter(s)/receivers(s) that comply with Innovation, Science and Economic Development Candas licence-exempt RSS(s). Operation is subject to the following two conditions:

1. This device may not cause interference. 2. This device must accept any interference, including interference that may cause undesired operation of the device. TnL-FIW103 Datasheet 13 7.2.3 ISED - Industrie Canada appareil radio exempts de licence Lmetteur/rcepteur exempt de licence contenu dans le prsent appareil est conforme aux CNR dinnovation, Sciences et Dveloppement conomique Canada applicables aux appareils radio exempts de licence. Lexploitation est autorise aux deux conditions suivantes :

1. Lappareil ne doit pas produire de brouillage;

2. Lappareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible den compromettre le fonctionnement. 7.2.4 Radio Frequency (RF) Exposure Compliance of Radio communication for mobile Apparatus To satisfy FCC and IC RF Exposure requirements , a separation distance of 30mm or more should be maintained between the antenna of this device and persons during operation. To ensure compliance, operation at a closer distance than this is not recommended. This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter. 7.2.5 Conformit lexposition aux champs RF des quipements radio mobiles Pour satisfaire aux exigences FCC et IC concernant lexposition aux champs RF, une distance de sparation de 30mm ou plus doit tre maintenu entre lantenne de ce dispositif et les personnes pendant le fonctionnement. Pour assurer la conformit, il est dconseill dutiliser cet quipement une distance infrieure. Cet metteur ne doit pas tre co-situ ou fonctionner conjointement avec une autre antenne ou un autre metteur. 7.2.6 End Product Labeling 7.2.6.1 FCC Certification The final end product must be labeled in a visible area with the following:

Contains Transmitter Module FCC ID: 2APCX-TNLFIW10 or Contains FCC ID: 2APCX-TNLFIW10 7.2.6.2 ISED Certification The final end product must be labeled in a visible area with the following:

Lquipement final doit tre tiquet sur un endroit visible avec le texte suivant :

Contains IC: 23741-TNLFIW10 7.2.7 End Product Users Manual:

The user manual for end users must include the following information in a prominent location:

To satisfy FCC and ISED RF Exposure requirements, a separation distance of 30mm or more should be maintained between the antenna of this device and persons during operation. To ensure compliance, operation at a closer distance than this is not recommended. This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter. Pour satisfaire aux exigences FCC et ISDE concernant lexposition aux champs RF, une distance de sparation de 30mm ou plus doit tre maintenu entre lantenne de ce dispositif et les personnes pendant le fonctionnement. Pour assurer la conformit, il est dconseill dutiliser cet quipement une distance infrieure. Cet metteur ne doit pas tre co-situ ou fonctionner conjointement avec une autre antenne ou un autre metteur. TnL-FIW103 Datasheet 14 8 Mechanical characteristics 8.1 Module dimensions The main dimensions are noted in the diagram below (bottom view):

Dimensions3:

Weight:

28 x 38 x 3 mm 3 g 8.2 Standard plastic case An optional plastic casing is available from IoTize (see dimensions below):

TnL-FIW103 Datasheet 15 8.3 Ordering Codes and Options Base part number: TnL-FIW10x Available part numbers:

TnL-FIW103 Product Line TnL Use Mode F Physical Interface Radio Interface1 Product Prefix Security I W 10 3 Casing Type

-0 Power Supply

-TO Product Lines:

Use Mode:

Physical interface:

Radio interface:

Security:

Casing Type2:

Power Supply:

TnL = TapNLink1 F = Fixed (powered by target system) I = SWD/S3P W = Wi-Fi/BLE, T = NFC Only, R = BLE, B = Bluetooth Classic, L = BLE, LoRa 1 = Primer, 2 = Low, 3 = software based, 5 = hardware based with embedded secure element.

-0 = No casing option selected

-TO = Powered by target system only Notes:

1. The features of the part number shown in the table are indicated in bold. 2. The ABS plastic casing is available as an option with its specific type number. TnL-FIW103 Datasheet 16 1 Appendices TnL-FIW103 Datasheet 17 TnL-FIW103 Datasheet 18 2 History Date Version Author Modification May 10th 2019 June 14th 2019 June 27th 2019 November 8th 2019 1.0 1.1 1.2 1.3 AM SG PF First release version. Product photo updates Add BLE features PF, SG Text revisions and corrections Disclaimer on the part of the author(s). Information in this document is subject to change without notice and does not represent a commitment No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval systems, for any purpose other than the development of the IoTize technology, without prior written permission from IoTize SAS and the IoTize consortium members. Every effort has been made to ensure the accuracy of this manual and to give appropriate credit to persons, companies and trademarks referenced herein. This document exists in electronic form (pdf) only. Copyright IoTize All rights reserved IoTize is a registered trademark of IoTize SAS. All other registered names and trademarks are the property of their respective owners. TnL-FIW103 Datasheet 19

loTize SAS 960 chemin de la Croix Verte 38330 Montbonnot-Saint-Martin FRANCE Date: July 19, 2019 Authority to Act as Agent Certification Body, Inc. American 6731 Whittier Suite C110 Avenue Mclean, VA 22101 To Whom lt May Concern:

SMEE (Mr. Laurent on our behalf,

(ACB). Chapus, ZI des Blanchisseries, F-38500 notified, for applications to American Voiron, France) Certification Body, Inc. is authorized to act until otherwise We certify pursuant as defined includes FCC benefits. that we are not subject to de niai of fedeiral benefits, that includes FCC benefits, to Section 5301 of the Anti-Drug Abuse Act of 1988, 21 U.S.C. 862. Further, no party, in 47 CFR 1.2002 (b), to the application is subject to denial of federal benefits, that Thank you, xpiration Date: December 315\ 2020 By:

Mr. Francis Lamotte Title: President

Head Office 960 chemin de la Croix Verte 38330 Montbonnot-Saint-Martin, Tel: +33 (0)4 76 41 87 99 Email:

contact@iotize.com FRANCE Il S.A,S. R.C.S, V.A.T. au capital de Grenoble 825 33S 896 number:

1000000 FR S682533S896

loTize SAS 960 chemin de la Croix Verte 38330 Montbonnot-Saint-Martin FRANCE Request for Confidentiality Date: July 19, 2019 Subject: Confidentiality Request for FCC ID: 2APCX-TNLFIW10 IC: 23741-TNLFIWl0 to FCC 47 CFR 0.457(d) and 0.459 and IC RSP-100, Section 12.4, the applicant requests that a part of the Pursuant subject FCC application be held confidenti al. Type of Confidentiality Requested Exhibit D ShortTerm f8] Permanent Block Diagrams D ShortTerm External Photos D Shorterm D Permanent

""1 Internai Photos D ShortTerm Permanent Ope ration Description/Theory of Operation D Shorterm D Permanent Parts List & Placement/BOM D Shorterm D Permanent Tune-Up Procedure D Shorterm Permanent Schematics D ShortTerm Test Setup Photos D Shorterm D Permanent*

3 User's Manual IOTIZE subject this product. has spent substantial information easily in developing this product to "competition"

would negate will result available the details of the design Not protecting effort and it is one of the first the advantage in financial hardship. of its kind in industry. Having the they have achieved by developing Permanent permanently customarily withheld released Confidentiality:

review to the public. from public The applicant the exhibits requests due to materials listed above as permanently confidential be that contain trade secrets and proprietary information not The applicant of 150 days from the date of the Grant of Equipment the exhibits selected requests Confidentiality:

view for a period This is to avoid premature Applicant Short-Term from public marketing. the public. product the documents above for public or the product listed is made available is also aware that they are responsible to the public disclosure before pursuant to notify the requested Notice to FCC Public release of sensitive information prior to marketing ACB in the event information of the product regarding or release the to period has expired. ACB will then release above as short term confidential be withheld Authorization and prior to DA 04-1705. Head Office 960 chemin de la Croix Verte 38330 Montbonnot-Saint-Martin, Tel: +33 (0)4 76 41 87 99 Email: contact@iotize.com FRANCE

au capital de 825 335 896 S.A.S. R.C.S. Grenoble V.A.T. number:

1000000 FR 56825335896

Request for Modular/Limited Modular Approval Date: January 15, 2020 Subject: Manufacturers Declaration for - Modular Approval Confidentiality Request for: ___________

- Limited Modular Approval - Limited Split Modular Approval

- Split Modular Approval 8 Basic Requirements FCC Part 15.212(a)(1) For Items Marked NO(*), the Limited Module Description Must be Filled Out on the Following Pages Modular Approval Requirement Requirement Met 1. The modular transmitter must have its own RF shielding. This is intended to ensure that the module does not have to rely upon the shielding provided by the device into which it is installed in order for all modular transmitter emissions to comply with FCC limits. It is also intended to prevent coupling between the RF circuitry of the module and any wires or circuits in the device into which the module is installed. Such coupling may result in non-compliant operation. The physical crystal and tuning capacitors may be located external to the shielded radio elements. 15.212(a)(1)(i) Details: The module contains a metal shield which covers all RF components and circuitry. The shield is located on the top of the board next to antenna.

- YES - NO(*) 2. The modular transmitter must have buffered modulation/data inputs (if such inputs are provided) to ensure that the module will comply with FCC requirements under conditions of excessive data rates or over-modulation. 15.212(a)(1)(ii) Details: SWD or S3P bus used 3. The modular transmitter must have its own power supply regulation on the module. This is intended to ensure that the module will comply with FCC requirements regardless of the design of the power supplying circuitry in the device into which the module is installed. 15.212(a)(1)(iii) Details: MCU / RF IC (ESP32) have internal regulator 4. The modular transmitter must comply with the antenna and transmission system requirements of 15.203, 15.204(b), 15.204(c), 15.212(a), and 2.929(b). The antenna must either be permanently attached or employ a unique antenna coupler (at all connections between the module and the antenna, including the cable). The professional installation provision of 15.203 is not applicable to modules but can apply to limited modular approvals under paragraph 15.212(b). 15.212(a)(1)(iv) Details: The module has its own antenna soldered on the PCB 5. The modular transmitter must be tested in a stand-alone configuration, i.e., the module must not be inside another device during testing. This is intended to demonstrate that the module is capable of complying with Part 15 emission limits regardless of the device into which it is eventually installed. Unless the transmitter module will be battery powered, it must comply with the AC line conducted requirements found in Section 15.207. AC or DC power lines and data input/output lines connected to the module must not contain ferrites, unless they will be marketed with the module (see Section 15.27(a)). The length of these lines shall be length typical of actual use or, if that length is unknown, at least 10 centimeters to insure that there is no coupling between the case of the module and supporting equipment. Any accessories, peripherals, or support equipment connected to the module during testing shall be unmodified or commercially available (see Section 15.31(i)). 15.212(a)(1)(v) Details: The module was tested stand-alone as shown in test setup photographs filed with this application

- YES - NO(*)

- YES - NO(*)

- YES - NO(*)

- YES - NO(*) 6. The modular transmitter must be labeled with its own FCC ID number, or use an electron display Modular Approval Requirement Requirement Met

(see KDB Publication 784748). If using a permanently affixed label with its own FCC ID number, if the FCC ID is not visible when the module is installed inside another device, then the outside of the device into which the module is installed must also display a label referring to the enclosed module. This exterior label can use wording such as the following: Contains Transmitter Module FCC ID: XYZMODEL1 or Contains FCC ID: XYZMODEL1. Any similar wording that expresses the same meaning may be used. The Grantee may either provide such a label, an example of which must be included in the application for equipment authorization, or, must provide adequate instructions along with the module which explain this requirement. In the latter case, a copy of these instructions must be included in the application for equipment authorization. If the modular transmitter uses an electronic display of the FCC identification number, the information must be readily accessible and visible on the modular transmitter or on the device in which it is installed. If the module is installed inside another device, then the outside of the device into which the module is installed must display a label referring to the enclosed module. This exterior label can use wording such as the following: Contains FCC certified transmitter module(s). Any similar wording that expresses the same meaning may be used. The user manual must include instructions on how to access the electronic display. A copy of these instructions must be included in the application for equipment authorization. 15.212(a)(1)(vi) Details: There is a label on the module as shown in the labeling exhibit filed with this application. Host specific labeling instructions are shown in the installation manual filed with this application.

- YES - NO(*) 7. The modular transmitter must comply with all specific rule or operating requirements applicable to the transmitter, including all the conditions provided in the integration instructions by the grantee. A copy of these instructions must be included in the application for equipment authorization. For example, there are very strict operational and timing requirements that must be met before a transmitter is authorized for operation under Section 15.231. For instance, data transmission is prohibited, except for operation under Section 15.231(e), in which case there are separate field strength level and timing requirements. Compliance with these requirements must be assured. 15.212(a)(1)(vii) Details: The module complies with FCC Part 15C requirements. Instructions to the OEM installer are provided in the installation manual filed with this application.

- YES - NO(*) 8. The modular transmitter must comply with any applicable RF exposure requirements. For example, FCC Rules in Sections 2.1091, 2.1093 and specific Sections of Part 15, including 15.319(i), 15.407(f), 15.253(f) and 15.255(g), require that Unlicensed PCS, UNII and millimeter wave devices perform routine environmental evaluation for RF Exposure to demonstrate compliance. In addition, spread spectrum transmitters operating under Section 15.247 are required to address RF Exposure compliance in accordance with Section 15.247(b)(4). Modular transmitters approved under other Sections of Part 15, when necessary, may also need to address certain RF Exposure concerns, typically by providing specific installation and operating instructions for users, installers and other interested parties to ensure compliance. 15.212(a)(1)(viii) Details: The module meets mobile exclusion levels as shown in the RF exposure information filed with this application.

- YES - NO(*) Limited Module Description When Applicable

* If a module does NOT meet one or more of the above 8 requirements, the applicant may request Limited Modular Approval (LMA). This Limited Modular Approval (LMA) is applied with the understanding that the applicant will demonstrate and will retain control over the final installation of the device, such that compliance of the end product is always assured. The operating condition(s) for the LMA; the module is only approved for use when installed in devices produced by grantee. A description regarding how control of the end product, into which the module will be installed, will be maintained by the applicant/manufacturer, such that full compliance of the end product is always ensured should be provided here. Details: N/A Software Considerations KDB 594280 / KDB 442812 (One of the following 2 items must be applied) Requirement Requirement Met 1. For non-Software Defined Radio transmitter modules where software is used to ensure compliance of the device, technical description must be provided about how such control is implemented to ensure prevention of third-party modification; see KDB Publication 594280. Details: The firmware of the device can not be modified or adjusted by the end user. 2. For Software Defined Radio (SDR) devices, transmitter module applications must provide a software security description; see KDB Publication 442812. Details: <example N/A>

- Provided in Separate Cover Letter

- N/A

- Provided in Separate Cover Letter

- N/A Split Modular Requirements Requirement Provided in Manual 1. For split modular transmitters, specific descriptions for secure communications between front-end and control sections, including authentication and restrictions on third-party modifications; also, instructions to third-party integrators on how control is maintained. Details: <example N/A >

- Provided in Separate Cover Letter

- N/A OEM Integration Manual Guidance KDB 996369 D03 Section 2 Clear and Specific Instructions Describing the Conditions, Limitations, and Procedures for third-parties to use and/or integrate the module into a host device. Requirement Is this module intended for sale to third parties?

- YES

- No, If No, and LMA applies, the applicant can optionally choose to not make the following detailed info public. However there still needs to be basic integration instructions for a users manual and the information below must still be included in the operational description. If the applicant wishes to keep this info confidential, this will require a separate statement cover letter explaining the module is not for sale to third parties and that integration instructions are internal confidential documents. Items required to be in the manual See KDB 996369 D03, Section 2 As of May 1, 2019, the FCC requires ALL the following information to be in the installation manual. Modular transmitter applicants should include information in their instructions for all these items indicating clearly when they are not applicable. For example information on trace antenna design could indicate Not Applicable. Also if a module is limited to only a grantees own products and not intended for sale to third parties, the user instructions may not need to be detailed and the following items can be placed in the operational description, but this should include a cover letter as cited above. 1. List of applicable FCC rules. KDB 996369 D03, Section 2.2 a. Only list rules related to the transmitter. 2. Summarize the specific operational use conditions. KDB 996369 D03, Section 2.3 a. Conditions such as limits on antennas, cable loss, reduction of power for point to point 3. Limited Module Procedures. KDB 996369 D03, Section 2.4 systems, professional installation info a. Describe alternative means that the grantee uses to verify the host meets the necessary limiting conditions b. When RF exposure evaluation is necessary, state how control will be maintained such that compliance is ensured, such as Class II for new hosts, etc. 4. Trace antenna designs. KDB 996369 D03, Section 2.5 a. Layout of trace design, parts list, antenna, connectors, isolation requirements, tests for design verification, and production test procedures for ensuring compliance. If confidential, the method used to keep confidential must be identified and information provided in the operational description. 5. RF exposure considerations. KDB 996369 D03, Section 2.6 a. Clearly and explicitly state conditions that allow host manufacturers to use the module. Two types of instructions are necessary: first to the host manufacturer to define conditions (mobile, portable xx cm from body) and second additional text needed to be provided to the end user in the host product manuals. 6. Antennas. KDB 996369 D03, Section 2.7 a. List of antennas included in the application and all applicable professional installer instructions when applicable. The antenna list shall also identify the antenna types

(monopole, PIFA, dipole, etc note that omni-directional is not considered a type) 7. Label and compliance information. KDB 996369 D03, Section 2.8 a. Advice to host integrators that they need to provide a physical or e-label stating Contains FCC ID: with their finished product 8. Information on test modes and additional testing requirements. KDB 996369 D03, Section 2.9 a. Test modes that should be taken into consideration by host integrators including clarifications necessary for stand-alone and simultaneous configurations. b. Provide information on how to configure test modes for evaluation 9. Additional testing, Part 15 Subpart B disclaimer. KDB 996369 D03, Section 2.10

- All Items shown to the left are provided in the Modular Integration Guide (or UM) for Full Modular Approval

(MA) or LMA.

- An LMA applies and is approved ONLY for use by the grantee in their own products, and not intended for sale to 3rd parties as provided in a separate cover letter. Therefore the information shown to the left is found in the theory of operation. Filled by:

Laurent CHAPUS (Agent for this device) SMEE Rue de Taille ZI des Blanchisseries 38500 Voiron - France laurent.chapus@smee.fr FCC Registration Number: 0020356952 (FRN) Applicant for this device:

IOTIZE 960 chemin de la Croix Verte 38330 Montbonnot - FRANCE francis.lamotte@iotize.com Francis Lamotte President Tel : +33 (0)4 76 41 87 99