FCC ID: AZP-FEX02T Radio Control Module

Tentative FEX02TB (Increase Data) 2.4GHz FH-SS RF-module Instruction Manual 1 Tentative 1 2 3 4 5 6 7 8 Overview ................................................................................ 3 General Specification ................................................................... 3 2.1 High-frequency portion ................................................................ 3 2.2 External interface .................................................................... 3 2.3 Power supply .......................................................................... 4 2.4 Environmental specifications .......................................................... 4 2.5 Others ................................................................................ 4 2.6 External Terminal ..................................................................... 5 2.7 Reset terminal ........................................................................ 6 2.8 Initialization time ................................................................... 6 2.9 Appearance ............................................................................ 6 2.10 Antennas ............................................................................. 7 Communication Method .................................................................... 8 3.1 Frequency hopping ..................................................................... 8 3.2 Synchronization ....................................................................... 8 Communication procedure ................................................................. 9 4.1 Overview .............................................................................. 9 4.2 Send command .......................................................................... 9 4.3 Received data ......................................................................... 9 4.4 Master communication procedure ....................................................... 10 4.5 Slave communication procedure ........................................................ 10 4.6 Communication time ................................................................... 10 Other functions ........................................................................ 11 5.1 ID Registration ...................................................................... 11 Commands ............................................................................... 12 6.1 List of commands ..................................................................... 12 6.2 How to use commands .................................................................. 12 6.3 Command responses .................................................................... 12 6.3.1 Types of command responses ....................................................... 12 6.4 Details of the command functions ..................................................... 13 Memory register ........................................................................ 18 7.1 Memory register list ................................................................. 18 7.2 Memory register function detail ...................................................... 19 FCC&IC Warning ......................................................................... 23 8.1 FCC Label Compliance Statement ....................................................... 23 8.2 To assure continued FCC compliance ................................................... 23 8.3 Exposure to Radio Frequency Radiation ................................................ 23 2 Tentative 1 Overview

(1) 2.4 GHz band FH (frequency hopping) type wireless module.

(2) This module has adopted a communication protocol that is intended to be used as a wireless controller.

(3) Using the UART, it is set by the command input, and performs input and output operational data. Table 1FEX02TB Appearance photo ARIB STD-T66 FCC Part15.247 EN 300 328 1226mW Spread spectrum FH system 60MHz 2407.5MHz2467.5MHz frequency hopping (31 patterns, 31 waves) 128.143kbps outdoors 365m [TBD]

U.FL connector diversity (Tx/Rx) CRC-CCITT16bits molex 53780-1490(14pin) Mating connector 51146-1400 RS-232CDCE-mode input 3.3V CMOS-levelwith hysteresis output 3.3V CMOS-level

: full duplex

: start-stop synchronization method 115200bps none 7 bit/8 bit 3 2 General Specification 2.1 High-frequency portion Technical standards RF Output Power Communication method Spread bandwidth Radio frequency band Frequency control Data modulation rate Coverage area Antenna terminal Antenna Error detection function 2.2 External interface Physical interface Interface Communication method Synchronization method Baud rate Flow control Data length

(according to an external antenna, sight distance, and our measurement method) Tentative Stop bit Parity 2.3 Power supply 1 bit/2 bit even/odd/none Source voltage Consumption current 2.4 Environmental specifications DC 3.8V8.5V transmission 300mA or less reception 35mA or less average at communication 200 mA or less [TBD]

Temperature conditions Operating humidity limits Storage humidity range Anti-vibration Anti-shock 2.5 Others External dimensions Weight Operating temperature limits ambient temperature-20 to +60 Storage temperature range ambient temperature-30 to +70 90%RH or less (no condensing) 90%RH or less (no condensing) 50m/s2 (JIS-C-60068-2-6) 500m/s2 (JIS-C-60068-2-27) 63(W)35(D)3(H) mm about 14g 4 Tentative 2.6 External Terminal No. Terminal I/O Function Table 1Terminal function name NC RxD TxD NC GND CLK STE SDA SCL VCC RST 3.3V Reserved TEST 1 2 3 4 5 6 7 8 9 10 11 12 13 14 OUT IN IN IN IN IN IN OUT OUT IN UART RxD

(Response Output) UART TxD

(Command Input) signal ground reserved reserved reserved Reserved Power DC 3.88.5 CPU reset Test Reserved Test Internal terminal processing Pull-down Pull-down Pull-down Pull-down Low 5 Tentative 2.7 Reset terminal Resetting with the Reset terminal provides the pulse below. Minimus 1ms High Low Figure 2Reset pulse 2.8 Initialization time 2.9 Appearance

(1) The initialization time (after power up until accept command) is 90ms or less.

(2) The initialization time by the RST command input is 1200ms. Figure 3FEX02TB External view 6 Tentative 2.10 Antennas This radio transmitter (FCC ID: AZP-FEX02T, IC: 2914D-FEX02T) has been approved by Federal Communications Commission or Innovation, Science and Economic Development Canada to operate with the antenna types listed below with the maximum permissible gain indicated. Antenna types not included in this list, having a gain greater than the maximum gain indicated for any type listed are strictly prohibited for use with this device. Table 2Specification of antennas Antenna type Peak gain Connector type ANT-2.4-CW-RH-RPS ANT-2.4-CW-RH-SMA ANT-2.4-WRT-RPS ANT-2.4-WRT-SMA ANTB24-073A0 TNHW 2450 RP Omni-directional

(1/4 Wave Antenna) Omni-directional

(1/2 Wave Antenna) Omni-directional Omni-directional

(1/2 Wave Antenna)

-0.9dBi RP-SMA 3.5dBi SMA RP-SMA SMA Obtained certification FCC/IC CE, TELEC FCC/IC CE, TELEC 2.14dBi 2.4dBi MHF (I-PEX) TNC reverse FCC/IC, CE, TELEC FCC/IC, CE RD2458-5-OTDR Omni-directional 3.0dBi N male CE 7 Tentative 3 Communication Method 3.1 Frequency hopping This wireless module employs an FH system as a diffusion method. In the FH system, diffusion signals with a wide bandwidth are produced by hopping the frequency according to a certain pattern. The pattern is called a frequency hopping pattern. This device has 31 types of frequency hopping patterns. The same hopping pattern is set for the wireless machines that are intended to mutually communicate. f r e q u e n c y time figure 4frequency hopping Even when the hopping pattern is the same, mutual communication is impossible when a wireless module randomly hops the frequency. Therefore, in the frequency hopping system, one of the wireless machines works as a standard, while other wireless machines synchronize the frequency and hopping timing of each machine by receiving packets from the standard machine. This is called synchronization. 3.2 Synchronization The slave switches frequency while waiting for a wireless packet from the master. When a wireless packet is received, it switches to the next frequency and waits for a wireless packet again. When received, it is judged that the synchronization with the master was successful. After that, the slave matches the timing and sends wireless packets to the master. mastertransmitter No timeout is set, even for cases when synchronization is unsuccessful due to a poor communication environment. It continues receiving until synchronization succeeds. In the case when synchronization fails during communication for some reason, a maximum of 1000ms is required to re-synchronize. [TBD]

slavereceiver figure 5master and slave 8 Tentative 4 Communication procedure 4.1 Overview and is in an invalid state. Communication is done in the following manner

(1) Right after the power is turned on, the master and slave does not have wireless communication

(2) For sending/receiving a wireless packet, start the FH operation by inputting the @FHS command

(the master and the slave). The master initiates RF transmission and reception. The slave starts RF reception, wait for communication from the master.

(3) If FH synchronization acquisition, slave start also sent. After that, the slave will continue in automatic synchronization.

(4) By TLC command to set the data you want to send.

(5) In FH synchronization acquisition, it will receive the data periodically from the communication partner. If the synchronization is out, it does not receive the data.

(6) To stop sending/receiving a wireless packet, type the @FHE command and quit the FH operation. 4.2 Send command command. The command header is "@TLC", the terminator is CR+LF (0x0D 0x0A). There is no response to the Please send data as a binary data of 60-byte fixed. Radio transmission will be run every 20ms. By @TLC command, it will update the transmitted data. If @TLC command is not inputted, the previous data is wirelessly transmitted. If you also send command has not been entered once, the data of all 0 is wireless transmitted. Send (update) format

@TLC[Binary data 60 bytes][CRLF]

4.3 Received data The received data is appended "RLC" of 3 bytes as a header. The Received data is binary data of 60-byte fixed. Radio reception will be run every 20ms. In a state that can't be wireless communication, it will not be output to the wired. Reception formatRepeat RXT[Binary data 60 bytes]

9 Tentative 4.4 Master communication procedure

(1) After the power is turned on, the master does not perform the wireless communication.

(2) If you want to transmit and receive wireless packet, enter FHS command.

(3) As long as the FH synchronization acquisition, the data from the slave is output to the wired. The received data will be "RLC" header is added.

(4) If you send the data to the slave, enter the @TLC command. By sending @TLC command regularly, the transmitted data is updated.

(5) If you stop the wireless communication, enter the @ FHE command. 4.5 Slave communication procedure

(1) After the power is turned on, the slave does not perform the wireless communication.

(2) If you want to transmit and receive wireless packet, enter FHS command.

(3) As long as the FH synchronization acquisition, data from the master is output to the wired. The received data will be "RLC" header is added.

(4) If you send the data to the master, enter the @TLC command. By sending @TLC command regularly, the transmitted data is updated.

(5) If you stop the wireless communication, enter the @ FHE command. 4.6 Communication time Interval of the frequency hopping (switching frequency) is 20ms. This 20ms is one frame. The master wirelessly transmits (1 packet transmission) at the beginning of the frame. Communication time is about 5ms. The slave that is synchronized with the master wirelessly receives the packet at the beginning of the frame. The figure below shows the timing. 20ms 5ms 5ms 10 Figure 6FH communication timing Tentative 5 Other functions 5.1 ID Registration In order to associate the master and the slave, an ID code is used. Each wireless module has a unique value. For wireless communication, registration of the ID code of the communication partner is necessary. Wireless machines without ID code registration are unable to communicate. This prevents improper connections. To make the pairing, in a state in which the closer to the master / slave, and then run the @IDS command to both the master / slave. In the case of slave, it is possible to register up to two. Please refer to the description of @IDS command for how the second unit of the specified. If the pairing is successfully complete, "Pair" response is output, pairing ID code is written to the memory. In order to perform the normal communication, please do the once reset. If the pairing is not completed, approximately becomes a time-out within 5 seconds, it is returned N0 response. The slave is possible to register the master up to two. However, communication is carried out in a one-to-one, you will not be able to communicate from two masters. The slave keeps a connection with the master that initiated the first communication. 11 6 Commands 6.1 List of commands Tentative Table 3List of commands No. Command Function name ARG DBM ERR FHE FHS ID1 ID2 IDS INI ODA OEN REG RST TLC VER 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Display all register values Reference a reception intensity of received packet Reference error status End FH operation Start FH operation Reference and set pairing ID1 Reference and set pairing ID2 Start ID registration Initialize register values Reference and set register values Disable output Enable output Reset Set wireless data Display version 6.2 How to use commands

(1) When inputting a command to the wireless module, add 1 byte header for command recognition

(command header) at the beginning of the command, in order to differentiate from regular data. The command header is @ (40H).

(2) Command is case-sensitive.

(3) A 2-byte terminator is used to terminate a command. The terminator is [CRLF] (0DH: carriage return 0AH: line feed).

(4) The wireless module executes a command process after recognizing a command. For a command with a response, it returns the response to external devices after the process is completed.

(5) Do not input subsequent commands or data before getting a response.

(6) Command example

@ARG[CRLF]

6.3 Command responses 6.3.1 Types of command responses Command responses and their meanings are:

P0: normal termination P1: running command N0: command error N6: memory register writing error 12 Tentative 6.4 Details of the command functions

[ ] : Required input parameter/s

( ) : Optional input parameter/s The symbols used in this section have the following meaning:

Display all register values Format ARG Function Refers to all contents of memory register. Displays a two-digit hexadecimal number plus H at

: Reference the reception intensity of received packet Format Response Setting list display N0

: command error the end. DBM Response

-XXXdBm N0

: reception intensity

: command error Function Reads the reception intensity of the most recent, correctly received packet, and displays it in decibels. When none has been received after resetting, -134dBm is displayed. The signal strength indication is not absolute. It can be used for accurate relative measurements but should not be considered an absolute value. Reference error status Format Response ERR xxH N0 error status command error Function This command display the error information of the internal this module. If 00H is no error. bit21: memory (settings area) error bit11: memory (user area) error bit01: RF error 13

: End FH operation Format FHE Tentative Response P0 N0

: normal termination

: command error Function End FH operation. At this status, wireless transmission does not occur. Master/Slave stops radio transmission and reception. If state that FH synchronization acquisition, and then release it. Even when there is received data from a paired module, wired output does not occur. Starts FH operation Format FHS Response P0 N0

: normal termination

: command error Function Starts FH operation. Master/Slave starts radio transmission and reception. When there is received data from a paired master, wired output starts. If there is data received from pairing the communication partner, to start the output to the wired. Reference and set pairing ID1 Format ID2(:pairing ID code 1) pairing ID code 1 : xxxxxxxxx9-digit Response xxxxxxxxx P0 N0

: pairing ID code 1 (when when referencing)

: normal termination (when setting)

: command error Function References and sets the pairing ID code 1. By inputting only the command, currently set values can be referenced. Specify the ID code (9-digit Serial Number) of the module that is the communication partner. Both master and slave are valid. The setting becomes effective after a reset. 14 Tentative Reference and set pairing ID2 Format ID2(:pairing ID code 2) pairing ID code 2 : xxxxxxxxx9-digit Response xxxxxxxxx P0 N0

: pairing ID code 2 (when when referencing)

: normal termination (when setting)

: command error Function References and sets the pairing ID code 2. By inputting only the command, currently set values can be referenced. Specify the ID code (9-digit Serial Number) of the module that is the communication partner. Slave only is valid. The setting becomes effective after a reset. Start ID registration Format IDS:[pairing area]

pairing area Response

: x (1= pairing ID code 1, 2= pairing ID code 2) P0 Pair N0 N6

: normal termination

: pairing is completed

: command error, or pairing is not completed

: memory register writing error Function Starts pairing operation. In the case of master, please specify '1' to the pairing area. In the case of slave, please specify '1' or '2' to the pairing area.

: Initialize register value Format Function Resumes all contents of the memory register in the wireless module to the status at factory

: normal termination

: command error INI Response P0 N0 shipment. 15 Disable output Format ODA Tentative Response P0 N0 normal termination command error Function Disable the radio transmission and wired output. Temporarily used when you want to stop FH communication. If this module already has FH synchronization acquisition, also it will continue to maintain FH synchronization after executing this command. Output in the initial state is enabled. Slave only. Enable output Format OEN Response P0 N0 normal termination command error Function Enable the radio transmission and wired output. Output in the initial state is enabled. Slave only. Reference and set register values Format REG[register number](:set value) Register number Set value

: 00XX

: input a two-digit hexadecimal number with H at the end, or a three-digit decimal number without any suffix. Response XXX P0 N0 N6

: currently set value (when referencing)

: normal termination (when setting)

: command error

: memory register writing error Function References and sets the memory register. By inputting only a register number, currently set values can be referenced. The setting will be valid after reset. 16 Reset Format Tentative RST Response P0 N0

: normal termination

: command error Function This module will be reset. Set wireless data Format TLC[binary data]

Binary data

: 60-bytes fixed Function It specifies the data you want to send to the communication partner. It is 60-bytes fixed in In order to avoid the mixing of the received data, there is no response to this command. Input of this command, please as a 50ms interval at the shortest.[TBD]

: Display version Format Response None binary data. VER Response Program Version 1.000 N0

: display version

: command error Function Reads a program version of the wireless module. Improvements and bug fixes within a range of specifications Minor specification change Major specification change 17 Tentative 7 Memory register The memory register is a register that sets and memorizes operation modes and communication parameters for the wireless module. These values are read when the power is turned ON, and the module starts operating according to the setting. 7.1 Memory register list Register Function Default Default function Table 4Memory register list Wireless communication setting 1 Antenna diversity Wireless communication setting 2 Operation mode Reserve Frequency hopping pattern Reserve Reserve Reserve Wired communication setting 1 Wired communication setting 2 FH synchronization determination setting 1 FH synchronization determination setting 2 Detailed setting Reserve Pairing ID code 1 Reserve Pairing ID code 2 number REG00 REG01 REG02 REG03 REG04 REG05 REG06 REG07 REG08 REG09 REG10 REG11 REG12 REG13 REG14 REG15 REG16 REG17 REG18 REG19 REG20 REG21 REG22 REG23 REG24 REG25 Master 19200bps 00H 00H 00H 00H 08H 00H 00H 00H 01H 00H 00H 00H 08H 00H 00H 00H 00H 00H 00H 00H 00H 00H 00H 00H 00H 00H Reserve 18 Tentative 7.2 Memory register function detail Operation mode default

* Sets an operation mode (for the master or the slave). Table 5Operation mode 00H 01H Master (default) Slave Reserved default

* Not used in this wireless module. Leave default setting. Frequency hopping pattern default

* Sets the frequency hopping pattern. It can be set to 001E (030).

* Master only settings are valid. Slave sets the frequency hopping pattern automatically based

* In the initial state, a specific frequency hopping pattern is set. Because it is set to 00H on the information of the master. if you initialize, please set again.

* When using multiple systems within the same area, the frequency may periodically match and interfere with each other even when the frequency hopping patterns are different. Reserved default

* Not used in this wireless module. Leave default setting. Wireless communication setting 1 default Not used in this machine. Make sure to set to 0. Bit74Reserved

Bit3Antenna diversity Table 6Antenna diversity 0 1 Disable antenna diversity Enable antenna diversity default Enables/disables antenna diversity. When used with two antennas, set to 1 in this bit.

Bit2Antenna selection Table 7Antenna selection 0 1 Antenna is fixed to A default Antenna is fixed to B

At the non-diversity reception, decide the antenna terminal. 19 Tentative Not used in this machine. Make sure to set to 0. Bit10Reserved

Wireless communication setting 2 default

* Not used in this wireless module. Leave default setting. Reserved default

* Not used in this wireless module. Leave default setting. Reserved default

* Not used in this wireless module. Leave default setting. Wired communication setting 1 default Bit 7: data length Bit 6: parity bit Bit 5: Even/odd parity Bit4: Stop bit Bit3Reserved Table 8: Data length 0 1 8 bit data (default) 7 bit data Table 9: Parity bit 0 1 Without parity (default) With parity Table 10: Parity 0 1 Even parity (default) Odd parity Table 11: Stop bit 0 1 1 stop bit (default) 2 stop bit

* Invalid when without parity is set in bit 6.

* Not used in this machine. Make sure to set to 0. 20 Tentative Bit20Baud rate setting Table 12Baud rate Bit2 Bit1 Bit0 0 0 0 0 1 1 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 115200bps (default) Baud rate 19200bps Reserved Reserved Reserved Reserved Reserved Reserved Wired communication setting 2 default Bit75Reserved

* Not used in this machine. Make sure to set to 0. Bit4Addition and deletion of CRLF Table 13Addition and deletion of CRLF 0 1 Do not add the CR+LF code to the receive data. default Add the CR+LF code to the receive data.

* Sets whether adding the CRLF code or not to the received data. Bit30Reserved

* Not used in this machine. Make sure to set to 0. Reserved default

* Not used in this wireless module. Leave default setting. Detailed setting default Bit7Startup message output Table 14Startup message output 0 1 Disable startup message output default Enable startup message output When you want to output message at startup, set to 1 in this bit. At startup, Input command is output to the wired. By this message, you can recognize the activation timing. Bit64Reserved

Not used in this machine. Make sure to set to 0. No function assignment. 21 Tentative Bit3Receive level control Table 15Receive level control 0 1 Disable receive level control Enable receive level control default

* Receive level controlturns LNA Off and decreases the reception level when communication When used with Receive level control, set to 1 in this bit. at the short distance. Bit20Reserved

Reserved default Not used in this machine. Make sure to set to 0. No function assignment.

* Not used in this wireless module. Leave default setting. Pairing ID code 1 default

* Sets an ID code for a pairing machine.

* Both the master and slave use this. Reserved default

* Not used in this wireless module. Leave default setting. Pairing ID code 2 default

* Sets an ID code for a pairing machine.

* Only the slave use this. 22 Reserved default

* Not used in this wireless module. Leave default setting. Tentative 8 FCC Warning The final end product must be labeled in a visible area with the following:

Contains FCC ID: AZP-FEX02T, contains IC: 2914D-FEX02T. The grantee's FCC ID can be used only when all FCC/ IC compliance requirements are met. Manufacturers integrating the Radio Control Module into other devices should note the following:

The device is compliant with part 15.247 of Title 47 of the FCC rules. If the Radio Control Module is integrated into a new host product, the final host product still requires Part 15 Subpart B compliance testing with the modular transmitter installed. 8.1 FCC Label 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. 8.2 To assure continued FCC compliance Any changes or modifications not expressly approved by the grantee of this device could void the user's authority to operate the equipment. 8.3 Exposure to Radio Frequency Radiation This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment.

(1)When used as a master:

This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter.

(2)When used as a slave:

This equipment should be installed and operated with minimum distance 20cm between the radiator

& your body. 23 Tentative 9 IC Warning

(English) 9.1 IC Label Compliance Statement This device complies with Industry Canada license-exempt RSS standard(s). Operation is subject to the following two conditions: (1) this device may not cause interference, and (2) this device must accept any interference, including interference that may cause undesired operation of the device. 9.2 Exposure to Radio Frequency Radiation This equipment complies with IC radiation exposure limits set forth for an uncontrolled environment.

(1)When used as a master:

This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter.

(2)When used as a slave:

This equipment should be installed and operated with minimum distance 20cm between the radiator

& your body.

(French) 9.3 Dclaration de conformit l'tiquette IC Cet appareil radio est conforme au CNR dIndustrie Canada. Lutilisation de ce dispositif est autorise seulement aux deux conditions suivantes : (1) il ne doit pas produire de brouillage, et (2) lutilisateur du dispositif doit tre prt accepter tout brouillage radiolectrique reu, mme si ce brouillage est susceptible de compromettre le fonctionnement du dispositif. 9.4 Exposition au rayonnement radiofrquence Cet quipement est conforme aux limites d'exposition aux rayonnements IC dfinies pour un environnement non contrl.

(1)Lorsqu'il est utilis comme matre:

Cet metteur ne doit pas tre co-situ ou fonctionner conjointement avec une autre antenne ou metteur.

(2)Lorsqu'il est utilis comme esclave:

Cet quipement doit tre install et utilis avec un minimum de 20 cm de distance entre la source de rayonnement et votre corps. 24

FUTABA Corporation Radio Control Module Model : FEX02TB FCC ID/IC Label Location FCC ID/IC Label Placement Location FCC ID/IC Label Placement Location FCC ID/IC Label Format

THIS MUST BE SIGNED BY THE APPLICANT/AGENT AND SHOULD BE PLACED ON APPROPRIATE LETTERHEAD Request for Modular/Limited Modular Approval Date: May 20, 2020 Subject: Manufacturers Declaration for - Modular Approval Confidentiality Request for: ______AZP-FEX02T______

- Limited Modular Approval - Limited Split Modular Approval

- Split Modular Approval For Items Marked NO(*), the Limited Module Description Must be Filled Out on the Following Pages Modular Approval Requirement Requirement Met 8 Basic Requirements FCC Part 15.212(a)(1) 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.

- 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: All inputs to the modules are buffered through logic or microprocessor inputs.

- YES - NO(*) 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: The module contains its own power supply regulation. Please refer to schematic filed with this application

- YES - NO(*) 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 connects to its antenna using a TNC MALE REVERSE POLARITY/SMA/I-PEX connector which is considered a non-standard connector. A list of antennas tested and approved with this device may be found in user manual provided with the application

- YES - NO(*) 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(*) 053019-02a THIS MUST BE SIGNED BY THE APPLICANT/AGENT AND SHOULD BE PLACED ON APPROPRIATE LETTERHEAD 6. The modular transmitter must be labeled with its own FCC ID number, or use an electron display (see Modular Approval Requirement Requirement Met 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 Portable exclusion levels as shown in the RF exposure information filed with this application.

- YES - NO(*) 053019-02a THIS MUST BE SIGNED BY THE APPLICANT/AGENT AND SHOULD BE PLACED ON APPROPRIATE LETTERHEAD 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. 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: N/A

- Provided in Separate Cover Letter

- N/A 2. For Software Defined Radio (SDR) devices, transmitter module applications must provide a software security description; see KDB Publication 442812.

- 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: N/A

- Provided in Separate Cover Letter

- N/A Details: N/A Details: N/A 053019-02a THIS MUST BE SIGNED BY THE APPLICANT/AGENT AND SHOULD BE PLACED ON APPROPRIATE LETTERHEAD Requirement 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. 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. Sincerely, By:

053019-02a __________________________

(Signature/Title1) _______Ben Cheng_________

(Print name) 1 - 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.

Futaba FUTABA corporation Hobby Development Section Engineering Department System Solution Business Center 1080 Yabutsuka Chosei-mura, Chosei-gun, Chiba-ken, 299-4395, Japan Authority to Act as Agent Date: May 7, 2020 American Certification Body, Inc. 6731 Whittier Avenue Suite C110 McLean, VA 22101 To Whom It May Concern:

AUDIX Technology Corporation 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: May. 7, 2021 By: oS; Lowu Hot Toshikazu Hama

(Signature) (Print name) Title: Manager On behalf of: Futaba Corporation

(Company Name) Telephone: +81-475-30-1061

"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. 053019 12

Futaba FUTABA corporation Hobby Development Section Engineering Department System Solution Business Center 1080 Yabutsuka Chosei-mura, Chosei-gun, Chiba-ken, 299-4395, Japan Request_for Confidentiality Date: May 7, 2020 Subject: Confidentiality Request for: FCC ID: AZP-FEX02T, IC: 2914D-FEX02T Pursuant fo FCC 47 CFR 0.457(d) and 0.459 and IC RSP-100, Section 9.4, the applicant requests that a part of the subject FCC application be held confidential. Type of Confidentiality Requested Exhibit Short Term MPermanent Block Diagrams OC Short Term External Photos C) Short Term Permanent * Internal Photos C1 Short Term MPermanent Operation Description/Theory of Operation Short Term Permanent Parts List & Placement/BOM Short Term Permanent Tune-Up Procedure Short Term Permanent Schematics Short Term Test Setup Photos Short Term Permanent ** Users Manual ____ Futaba Corporation _ 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 before the requested period has expired. 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 considered applicable to IC applications. Sincerely, By: Teshibowe Ama, Toshikazu Hama

(Signature/Manager*) (Print name)

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

https://apps. fec.gov/oetef/kdb/forms/FTSSearchResultPage.cfm?switch=P&id=41731 and review section II, 3) regarding specific information that must accompany these requests.

> - Please refer to http://acbcert.com/documents/misc-docs/Memo-Short-Term-Vs-Standard-Confidentiality.pdf for complete details.

* _ 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. 053019 12