FCC ID: AYV-AGLU01 AirGlu Module

UserManualv1.0 AirGlu module KeyFeatures TheAirGlumodulehighlightedfeaturesarelistedbelow:

WirelessSyncandControl ConfigurableSyncandControlmoduleforsyncandcontrolof professionalcameras,recordersandaudiodevices BuiltinTimecodeGenerator,with0.5ppmVCTCXO TimecodeInputandTimecodeoutputmodes MasterorSlaveoperationmodes GenlockandWordClocksyncoutputs SyncandControlwirelessusingsubGHzprotocol,transmitand receive.InternalAntenna. Additionalconnectivitytoapps,using2.4GHzBluetoothLE.Internal Antenna. 2.0vand3.3vregulatedinputs UARTtohostequipmentwithbuffereddatainputs SimpleserialUARTAPIforallmenuandcontrolfunctions SinglepowerandI/Oport UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK SystemOverview Introduction TheAirGlumoduleisanenergyfriendly,compactsolutionfor providingwirelesssyncandcontrolcapabilitiestoaprofessional camera,recorderoraudiodevice. ItcombinesintegratedMCU,FPGAandSubGHzand2.4GHzradio transceivers. Ahighlyaccurate0.5ppmTCXOprovidesstabletimecodeandsync outputs. ItcancommunicateviaSubGHzradiotootherAirGlumodulesor to3rdpartyapplicationsusingthe2.4GHzBluetoothLEradio. Ithasinternalantennasandarobustmultipinconnectortothehost equipment. Itiscompactat20mmx40mm. UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK SystemOverview ModuleConnections AirGlu module PIN 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 InterfaceI/O Function EXTSCK GND EXTMOSI MCURESET EXTGPIO NC EXTMISO NC GND GENLOCKOUT 2V0IN GND 3V3IN EXTVSYNC EXTHSYNC GND UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK SystemOverview SerialUARTAPIS1CCommands API V5.4 Getting/Changing Configuration Settings of S1C enable devices All commands are formed normally using text-based strings and communicated to the device by one of the following methods. A bi-directional serial link. The link will currently be based around a logic level serial port with or without CTS/RTS handshake with a default baud rate of 57600. Note that TCS standard serial I/O will not tolerate full RS232 voltage levels, also RS232 has inverse logic. For Bluetooth Low Energy enabled devices. The method to be used to read or change values with the System One Controller

(S1C) using simple control request messages. These requests can be to retrieve information or to change settings. The S1C will respond back the requested data or acknowledgment of changes made. All control messages and replies can be checked using simple terminal software, i.e. Teraterm for serial links Command Syntax Commands and replies are formed as readable ASCII strings. Commands/queries/replies start with a #, this start character is followed by the command/query string which is then followed by a ? for queries or an = for commands/replies. All commands and queries are case sensitive, currently all upper-case and 4 ASCII characters long - excluding #, = or ?. All commands and queries must be terminated with a <LF> or a <CR>+<LF> (0x0a or 0x0d,0x0a)[\n or \r\n]. All non-binary replies will be terminated with a single

<LF>

Command value strings must not exceed 112 bytes to be compatible with the BLink network. UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK

#BCMD>Length+Binary Data\n Binary set (same as text commands =) Binary get (same as text commands ?) Binary Commands Commands or queries requiring binary data are identified with different assignment characters as follows.

>

<

Following the assignment character is a single length byte which denotes the length of the following binary data. If there is no binary data to follow then this length byte should be zero. The length byte should then be followed by the first byte of the binary data. The binary data (or zero length byte) still requires to be followed with a

\n termination character. Multiple Commands per line Multiple commands can be placed on a single command line. This is most useful for BLink commands/queries to a single remote device as multiple commands on a single line will be transmitted to the remote device in a single frame period i.e. quicker. Multiple commands should be separated with the : (full colon) character. Each line, not each command, should be started with the # character and terminated with a \n. Replies to multiple commands may be returned separately. It must be remembered that there is a line length limit of 112 characters. BLink Network Commands BLink network device addressing is slightly different, please see later section on Blink Networks for full details.

#TCTM?:TCUB?:RFTX=1:BINC>\04****\n UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK TCTM?

0 = Internal (free run) 1 = External RF Returns the current timecode source as a string TCSC=n where n is an 3 = External LTC 4 = External LTC (Cont) Free run if signal removed Sets the timecode source to the value n as in the list below. The S1C 0 = Internal 1 = External RF 2 = External RF (Cont) 3 = External LTC 4 = External LTC (Cont) 5 = Jam once to RF then go to Internal mode 6 = Jam once to LTC then go to Internal mode Timecode Source TCSC?

ASCII 0 through 2 where;

2 = External RF (Cont) Free run between sync packets. TCSC=n will reply with the currently set source where;

Timecode TCTM=hhmmssff User-Bits TCUB=uuuuuuuu Sets the current User Bits (only if in Internal Mode or RF userbits switch (RFUB) is off) Broadcast Timecode *

TCBC=n Will configure the unit to broadcast on the serial output a

#TCTM=hhmmssff string periodically. TCBC =1 offset adjustment to what is used/displayed. Timecode Run/Freeze *

When the Timecode source is set to a non-continuous mode the output Timecode will freeze until the incoming signal is seen, triggering a running the Timecode. Whereas continuous modes will continue to run the Timecode in the absence of and external signal and then soft-lock when the signal is re-established. These functions can override the standard behaviour. TCBC=0 Send Timecode once a second on frame 10. Frame 10 allows easy TCTM=hhmmssff Sets the current Timecode (only if in Internal Mode) Returns whether Timecode is running (=1) or frozen (=0). Returns the current timecode as a string Returns the current User Bits Send Timecode every frame.

(also see RF Userbits) Turn off broadcast TCBC=2 TCRN?

TCUB?

UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK TCRN=n Returns the current frame rate (Frames per Second) and whether using Sets the Timecode to run (n=1) or freeze (n=0). Frame Rate *

TCFR?

Drop-Frame encoding of the timecode data. Returns TCFR=n,d where n is the FPS value*1001 and d is a flag of whether using drop-frame encoding or not;

24000,0 = 23.98 fps (Non Drop-Frame) 24024,0 = 24 fps 25025,0 = 25 fps 30000,0 = 29.97 fps 30000,1 = 29.97 fps Drop-Frame 30030,0 = 30 fps 30030,1 = 30 fps Drop-Frame The function will accept double frame rates, as follows but will return the standard rate value in response and for subsequent queries. 48000,0 = 47.96 fps (Non Drop-Frame) 48048,0 = 48 fps 50050,0 = 50 fps 60000,0 = 59.94 fps 60000,1 = 99.94 fps Drop-Frame 60060,0 = 60 fps 60060,1 = 60 fps Drop-Frame TCFR=n,d Sets the current frame rate & drop frame to the values n,d as in the list above. The return value must be checked as illegal values will be ignored or changed to the nearest value. If changing the frame rate then the TV Sync standard may also change. It is important that the TV Sync value must be read and displayed after any changes to the FPS. Genlock or Sync Standard GLSD?

where n is an ASCII 0 through 13 where;

0 = Off 1 = PAL 2 = NTSC 3 = 720p 4 = 720p x2 (double rate) 5 = 1080i 6 = 1080p 7 = 1080p x2 8 = LTC (Timecode) 9 = 44.1 KHz Wordclock 10 = 88.2 KHz Wordclock 11 = 48 KHz Wordclock 12 = 96 KHz Wordclock 13 = 192 KHz Wordclock Returns the current TV sync (Genlock) method as a string GLSD=n UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK RFCN?

GLOP=n Sets the TV Sync output as per the table above Return Current Country/Area setting for the ISM band Returns the current TV sync level GLOP=n where n is an ascii Returns the current RF channel number as RFCH=n. Channel Sets the current TV Sync method to the value n as in the list above. If Sets the current RF channel number. The reply must be decoded and

(75 Ohm)

(2 x 75 Ohm = 37.5 Ohm for 3D camera rigs) GLSD=n the sync standard is not supported for the current frame rate the reply may not be the same as the request. The reply must be decoded and displayed as certain TV sync methods cannot be used with certain frame rates. Genlock or Sync Level GLOP?

character 0 or 1 where;

0 = Normal 1 = High RF Channel Number *

RFCH?

number range is 1 through to a maximum of 14, but will depend on country/area. RFCH=n displayed as certain channels cannot be used within some areas. Country/Area Setting *

transceiver RFCN=n Sets the current Country/Area setting. If changing the country then the RF channel number may also change, so the RF channel number must be read and displayed after any changes to the country/area. 0 = CEPT (EU/UK) 865.050-868.050MHz 1 = FCC (US/AU) 915.050-918.650MHz 2 = ARIB (JP) 920.600-923.600MHz RF Signal Strength RFSI? Returns the current signal strength (0 to 99) and whether the unit is locked to an RF timecode signal. RF Userbits RFUB?

not syncd to master, 1 if on i.e. synchronised. RFUB=n Transmitter On/Off *

The return will be something like;

Means the current signal strength is 68 and the unit is locked. Whereas;

Means the current signal strength is 14 and the unit is unlocked. Returns the status of the Transmitter, 0(zero) if off, 1 if on. Sets the Transmitter on/off, where n = 0(off) or 1(on) Returns the RF Receive User-Bits on/off switch value, 0(zero) if off or Sets the RF User-Bits on/off switch, where n = 0(off) or 1(on) RFTX?

RFTX=n

#RFSI=68,1

#RFSI=14,0 UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK Note:

Returns the current units device type as a text string such as Returns the current units text name string. This string is user definable Sets the text name of the unit. The maximum length is 11 characters. The transmitter will be automatically turned off if the Timecode Source is switched to External RF mode. It will not be automatically re-enabled when switched back. Device Type Name STTN?

SystemOne OEM. Device Definable Name STNM?

and is used to represent a friendly name for the unit i.e. Camera 1. STNM=

Display Brightness (only useful if used with display) STBT?

(Deprecated Use STBR) Returns the current brightness setting as STBT=n where n is an ascii character representing the current display brightness value 0 to 7 STBT=n Revision STVS?

lists the program type/revision and the FPGA type/revision separated by a semi-

colon ; followed by the S1C Protocol revision. STVP?

STVF?

STVC?

Device Status STST?

Returns the current state of the device. The statuses will be returned as an ASCII string with each status vertical bar (|, 0x7C) delimited on each line. The status to be returned will be:-

Returns the Program revision * 100 Returns the FPGA revision * 100 Returns the S1C Protocol revision Returns the current version as a string STVS=<string> where <string>

(Deprecated use STSS/STSP) Sets the display brightness. 1. UserBits UUUUUUUU 2. Sync Mode (0=INT, 1=Ext RF.. see TCRC command) 3. Ext Sync Std (0=Off, 1=PAL see GLSD command) 4. FPS (0=25,1=23.98,2=24,3=29.97, 4=30) 5. Country (see RFCN command) 6. RF Channel (see RFCH command) 7. Brightness level (see STBT command) 8. Battery (1-5) 9. On PSU (0 or 1) 10. Device Name (if any) 11. SSID (string) (if any) A typical return from this request will be:-

STST=12ABCD78|0|0|23,030|1|14|60|3|0|D Name|Wave077<LF>

UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK Individual Device Static Data STSS?

delimited on each line. The status to be returned will be:-

(For use with individual device Use BLSS=n if through BLink master) The current status will be returned as an ASCII string with each status comma 1. Unit Type 2. Unit Device Type Name 3. Firmware Revision * 100 4. FPGA Revision * 100 5. Ext Revision * 100 6. S1C Revision 7. Device Capability Flags See Appendix The device capability flags state what functions can be used with the device, such as if a display is fitted, has Wifi capability, or external Sync port etc. This is denoted using a 32bit hexadecimal number. A typical return from this request will be:-

Individual Device Poll Changing Data STSP?

Poll for changing status information from the current device. The status will be returned as an ASCII string with each status comma delimited on each line. The status to be returned will be:-

(For use with individual device Use BLSP=n if through BLink master) STSS=11,UltraSyncBLU,201,106,0,5,E0F07040<LF>

1. Current Assigned Network Group Number 0/A F 2. Current UserBits UUUUUUUU 3. Data changed flags (8bit hex) - see below 4. Ext Sync Std (0=Off, 1=PAL see GLSD command) 5. Battery Percentage 6. On PSU (0 or 1) 7. RF Signal Strength (0 to 99) 8. Friendly name 0. Main Static data Changed use BLSS? to get changes 1. Main Polloing data Changed use BLSP? to get changes 2. Attached device static data changed use GCSS?

3. Attached device polling data changed use GCSP?

4-7 Undefined Data changed flags Bit definitions;

A typical return from this request will be:-

BLSP=1,B,65,CAFEF00D,05,40,0,65,UltraSync 1<LF>

STSP=0 Clear Data Changed flags UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK Set BLE into pairing mode Pairing sequence is idle Searching Stop any pairing sequence Initiate pairing sequence look for devices wishing to pair with us Connect to device Obtain current pairing information Bluetooth Low Energy (BLE) Commands BTPR=

Return values;

BTPR=0 BTPR=1 BTPR=2 BTPR?

Return Values BTPR=0 BTPR=1 BTPR=2,<Device> <Device> is waiting to pair BTST?

This request returns the number of available connection slots followed by a list of currently connected device names and signal strengths. i.e. BTST=1,name1,85,name2,80,,0,,0 Signifying currently two devices connected and just one slot available for a new pairing to another currently unknown device. BTST=

Delete pairing information BTST=0 Obtain current status of BLE devices Delete whole pairing table UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK Request the current transport control status Device Control and Status Generic Commands GCMD?

This command is a method of getting connected device. As well as returning the device Family type it also returns the model number. As BLST only returns the Family Type this function returns both this and the model connected as a string. The query returns a CSV string where the first value is the Family Type of the connected device followed by a string denoting the devices model number. If only one value is returned, i.e. no comma and no second value, then a family connecting lead is plugged in but no device was detected connected to the lead. Device Types

-1 = Nothing connected 0 = Sound Devices 1 = Canon OK 2 = GoPro GCCT?

Returned values:-

-1 = Nothing connected/Offline 0 = Unknown 1 = Stopped 2 = Recording 3 = Playback 4 = Pause 5 = Rewind 6 = Fast Forward GCCT=n As above but command to change the state of the device to n status as per list above. GCVR?

Requests the firmware version for the attached device and returned as an ASCII string GCBT?

GCON?

GCDV?

<drive_id>

<units>

0 = CF Card 1 = SD Card 2 = Internal Hard Disk 3 = External drive Returns the battery level in percentage units 0 through 100 Media Status. GCDV=<drive_id>,<value>,<units>

0 = minutes 1 = percentage Power status 1=On, 0=Off UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK 2 = Mbytes Attached Device Status and Control These new commands form a combination of the old individual commands but split into just two functions, one to get static data that rarely changes, and one to get data that can change or be set. GCXS?

Returns a series of fields that define the attached device and its capabilities. The fields are returned comma delimited. Get attached devices static data. 1. Manufacturers name - ASCII text value 2. Manufacturers model - ASCII text value 3. Capability Flags 32bit hexadecimal number See appendix 4. Storage unit #1 Name (ASCII string) 5. Storage unit #1 Capacity (integer value) 6. Storage unit #1 Units 0 = Empty/Unknown,1 = MB, 2 = GB, 3=TB 7. Storage unit #2 Name 8. Storage unit #2 Capacity 9. Storage unit #2 Units 10. Storage unit #3 etc. GCXP?

Returns a series of fields denoting the attached devices current status The fields are comma delimited. Get the attached devices changing data 1. Current transport status See appendix 2. Current frame rate numerator 3. Current frame rate denominator 4. Rate Flags (8bit Hex) Bit 0 = Drop Frame, others unused 5. Current battery level percentage 6. External power applied/battery charging flag 7. Current clip/file name 8. Storage unit currently selected or in use 9. Storage unit #1 media remaining time in minutes 10. Storage unit #1 media remaining size 11. Storage unit #2 media remaining time in minutes 12. Storage unit #2 media remaining size 13. Storage unit #3 etc. Used to set the attached devices transport status or frame rate. GCXP=

This command can only change the transport control state or the frame rate. The command need only supply the first field if just controlling the transport state or optionally two fields if also controlling the frame rate. 1. Current transport status See appendix 2. Current frame/bit rate Numerator (optional) 3. Current frame/bit rate Denominator (optional) UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK BLink networks BLink is a method of connecting client/slave devices to a master controlling device via the TCS proprietary long-range RF link. The master device MUST be the device that the clients are connected to for RF Timecode synchronisation. All S1C commands are initially sent to the master device and then relayed to the BLink client via the RF link. Responses from the BLink client are then replied back through the RF link to the master and then back to the command originator. Generally, all commands/requests are replied to but it must be noted some replies may take over a second to be returned. If no reply is heard within, say 2 seconds, the original request should be re-sent. The master device continually polls the BLink network both obtaining basic status information which is stored in a local table for fast responses to requests The BLink master also looks for new devices being connected to the network. New devices are auto allocated a new BLink ID which corresponds to a table entry of status information. New clients will generally be allocated an empty table position but if these get used up then entries from clients not heard from will be re-used. This table may change as BLink devices come and go from the network. New devices may re-use table entries of devices that have disappeared. Table entries may exist of devices that have not been heard from for a long time. Returning devices may be allocated a new BLink network ID and therefore a different position in the table, therefore reference to Unique ID must be maintained.

#@1;GLSD?\n Requests Sync standard of Blink device 1

#@42;GLSD=0\n Sets Sync standard of Blink device 42 to The BLink system can be configured for in excess of 1000 clients but currently restricted to around 50 clients depending upon the TCS device used as BLink master. It must be considered that more BLink clients do reduce the speed of the network. Command use with BLink network Example addressing of individual unit within BLink network Off. Note; #@0;GLSD?\n result in the same as #GLSD?\n Broadcast commands to all units will be for a restricted set of commands/settings only (not requests) and will be addresses using #@; prefix i.e. device number missing. Broadcast messages are NOT responded to by the clients and there is no way of knowing without checking that a command has been heard or actioned. There are also Group addressing commands that can address groups of units that are assigned to a particular group. There are 6 groups named A through to F and should be addressed as #@A; for instance, to address group A devices. Requests the Sync standard of the Blink Master and will UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK Returns the BLink group the slave belongs. Slave devices can be Sets the slave unit to belong to a particular group of slaves. Values S1C is designed to address either the Master device or any of the devices listening to the Master device. The master device will be the device that all S1C communications are directed for access to the BLink network. S1C may also be used directly with devices that are currently a client within another master devices BLink network, in this instance access to the BLink network is not possible. This would be used locally to ask for current information of that particular device, such as Timecode etc. BLID? Retrieves the current BLink ID for the device. The BLink ID is determined by the BLink master and cannot be set otherwise. BLGR?

addressed individually or within groups. There are six groups so the reply will be an A through F dependant on current group or will return 0 (zero) if slave does not belong to any group. BLGR=

should be an ASCII A through to F or a 0 if to remove the slave from all groups. Sending user defined data to BLink slave devices DASP=<string>

The command should be used along with the formatting required to address slave units individually or globally. i.e.

#@7;DASP=Hello\n

#@;DASP=To All\n This command will also work with binary data such as

#@3;DASP>Length+Data\n Will send Length+Data to slave ID #3 The overall length of the command should be kept as short as reasonably possible and must not exceed 112 bytes. Sending user defined data from slave devices back to the master. DAMP=<string>

i.e. DAMP=Hello\n Will send DASP=Hello to slave ID #7 Will send DASP=To All to every slave Send a user-defined <string> to the serial port on the master device. Will arrive at the master as #@n;DAMP=Hello - where n = slave ID Send a user-defined <string> to the serial port on the slave devices. UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK All the following commands should be directed to the master device only

(Deprecated use BLSS/BLSP) BLST?

Returns the number of known BLink devices on the network and a number or sequence of numbers that represent a bitmap of which slave devices are active. A reply of BLST=5, 91 means there are currently 5 devices online, and if the 91

(decimal) if converted to a binary value i.e. 1011011 will give a bitmap representation of active devices where bit 0 represents device 1, bit 1 represents device 2, and so on. In this instance devices 1, 2, 4, 5, & 7 are all active. Each bitmap number represents 8 devices so a third number in the reply represents the bitmap of devices 9 through to 16 and so on. This request should then be followed with individual requests for a particular devices current status. BLST Command must be used direct to the connected master device. Addressing a slave device such as #@3:BLST? will return nothing. BLST=n n is the index into the table of stored devices. For instance; BLST=1 will reply with the details of the first device in the table, and BLST=2 will reply with the details of the second device in the table, and so on. The statuses will be returned as an ASCII string with each status comma delimited on each line. The status to be returned will be:-

Retrieve basic status information from a BLink network device. Where 1. ID (Table Index) 2. Unique ID (hex form of 32 bit number i.e. 8 characters) 3. Unit Type 4. Last Reply (how long since last reply from client [x10mS]) 5. Replied Timecode HHMMSSFF 6. Replied UserBits UUUUUUUU 7. Sync Mode (0=INT, 1=Ext RF.. see TCSC command) 8. FPS (0=25,1=23.98,2=24,,,etc) 9. Ext Sync Std (0=Off, 1=PAL see GLSD command) 10. Locked to Timecode Source (0 or 1) 11. Battery (1-5) 12. On PSU (0 or 1) 13. UserBits Lock (1=User Settable 0=Locked to RF Master) 14. Attached Device Type See GCMD command 15. Current Assigned Group Number 0 if none 16. Attached Device Flags. Value should be broken into binary bits A typical return from this request will be:-

BLST=1,12ABCD78,6,121,00043410,00000000,1,1,0,1,3,0,0,2,0,3<LF>

We may wish to expand this list in the future so currently ignore any subsequent statuses. UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK Returns a bitmap of known BLink devices on the network. The statuses are only updated around twice per second maximum. So this command should only be used infrequently. Initial Connect Static Data BLSS?

The bitmap is broken down into 32-bit hexadecimal values that represent a bitmap of which slave devices are active. If say there is the reply BLST=0000005B if now the reply is broken into binary, each bit represents a device present or not (1 or 0). Thus, the hex value of 0000005B breaks down to binary 0...0001011011 and shows there are 5 bits set, thus there are currently 5 devices online, also the bits that are set gives a representation of active devices where bit 0 represents device 1, bit 1 represents device 2, and so on. In this instance devices 1, 2, 4, 5, & 7 are all active. Each bitmap number represents 32 devices so additional values in the reply represents the bitmap of devices 33 through to 64 and so on. The BLSS Command must be used direct to the connected master device. Addressing a slave device such as #@3:BLSS? will return nothing. BLSS=n table of stored devices. The statuses will be returned as an ASCII string with each status comma delimited on each line. The status to be returned will be:-

Returns the slave devices static data, where n is the index into the 1. Blink ID 2. Unique ID (32bit Hexadecimal) 3. Unit Type 4. Unit Device Type Name 5. Firmware Revision * 100 6. FPGA Revision * 100 7. Ext Revision * 100 8. S1C Revision 9. Device Capability Flags (See appendix) The device capability flags will let the Hub know what functions can be used with the device, such as if a display is fitted, has Wifi capability, or external Sync port etc. It is proposed to use a 32bit hexadecimal number. A typical return from this request will be:-

There could be confusion when parsing the returned values from the above two requests as they both return BLSS=<reply>. To differentiate between the two the length of the first <reply> field will determine which request the reply was from. If the first field has a length of 8 characters is can be determined that the reply is for the BLSS? query, otherwise it is a reply to the BLSS=n query. BLSS=1,12ABCD78,11,UltraSyncBLU,201,106,0,5, E0F07040<LF>

UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK Same as BLSS? command see above. Retrieve status information from a BLink network device. Slave Poll BLSP?

BLSP=n Where n denotes the index into the table of stored devices. For instance; BLSP=1 will reply with the details of the first device in the table, and BLSP=2 will reply with the details of the second device in the table, and so on. The statuses will be returned as an ASCII string with each status comma delimited on each line. The status to be returned will be:-

1. Blink ID 2. Current Assigned Group Number 0/A F 3. Last Reply (time since last reply x10mS). Zero if unheard. 4. Current UserBits UUUUUUUU 5. Data changed flags (8bit hex) - see below 6. Ext Sync Std (0=Off, 1=PAL see GLSD command) 7. Battery Percentage 8. On PSU (0 or 1) 9. RF Signal Strength (0 to 99) 10. Friendly name Field 5 Data changed flags Bit definitions;

0 Main Static data Changed use BLSS? to get changes 1 Main Polling data Changed use BLSP? to get changes 2 Attached device static data changed use BLXS?

3 Attached device polling data changed use BLXP?

4-7 Undefined Similar to BLCG command but only flags changes once the master The changed flags are automatically reset after this query. A typical return from this request will be:-

BLSP=1,B,65,CAFEF00D,05,40,0,65,UltraSync 1<LF>

Devices with changed information BLCH?

device has updated its records with the changes. The map returned is the same as the BLSS? command above i.e. hexadecimal not decimal. BLCH=0 BLCG?

Returns the number of BLink network slave devices that have changed details plus a bitmap of the affected devices. BLCG=0 Reset BLCG bits.

(Deprecated use BLCH) Reset BLCH bits. UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK Slaves Attached Device Status These commands should be used to get information regarding a device attached to a slave unit, directly from the master device. There is one query to get static data that rarely changes, and one to get data that can frequently change. BLXS=n Returns a series of CSV fields that define the attached device and its capabilities. The fields are returned comma delimited. Get the slave devices static data where n = slaves BLink ID. 1. Blink ID 2. Manufacturers name - ASCII text value 3. Manufacturers model - ASCII text value 4. Capability Flags 32bit hexadecimal number See appendix 5. Storage unit #1 Name (ASCII string) 6. Storage unit #1 Capacity (integer value 0 - 65535) 7. Storage unit #1 Units 0 = Empty/Unknown,1 = KB, 2 = MB, 3 =

GB 8. Storage unit #2 Name 9. Storage unit #2 Capacity 10. Storage unit #2 Units 11. Storage unit #3 etc. BLXP=n Returns a series of CSV fields denoting the attached devices current status The fields are comma delimited. Get the slave devices changing data where n = slaves BLink ID. 1. Blink ID 2. Current transport status See appendix 3. Current frame rate numerator 4. Current frame rate denominator 5. Rate Flags (8bit Hex) Bit 0 = Drop Frame, others unused 6. Current battery level percentage 7. External power applied/battery charging flag 8. Current clip/file name 9. Storage unit currently selected or in use 10. Storage unit #1 media remaining time in minutes 11. Storage unit #1 media remaining size 12. Storage unit #2 media remaining time in minutes 13. Storage unit #2 media remaining size 14. Storage unit #3 etc. UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK type 0=unknown, 1=main FW, 2=FPGA, 3=Ext version = update version * 100 Updating Firmware UFCK>length(=0x0A)+First ten bytes of update file+\n Binary command with an ASCII response to check the version of an update file. The update type and version are held within the first ten bytes of the update file so these need to be included in the query. The response will be UFCK=type, version, flag flag 0=Cant use, 1=Ok to proceed, 2=same version, 3=older version than current UFST=n Initiate a firmware update where n = overall size of update file to be transferred. The response will give the maximum size of update data that can be transferred in each UFDA block. i.e. UFST=106. Currently this is limited to a 106 byte maximum but, in the future and if transferred locally using say the serial interface, this may be increased. This command may take up to 3 seconds to complete depending on the size of the update. Please use this command sparingly as each call forces an erase of the internal Flash memory update buffer. UFDA>length + address + data-block + checksum + \n This is a binary command where blocks of data are sent sequentially starting at address zero and progressing through until all the file is transferred. The data is sent in binary format, where;

length is a single byte length of the entire message to follow (not including the final \n). Therefore, it is the length of the data block plus five (address and checksum bytes). Currently the length value should not exceed 111(0x6f). With the final \n character this is the current maximum total of 112bytes of data following the length byte. address is a three-byte, little endian, relative address of the data block from start of file. data-block is the block of data from the file checksum is a 2s compliment 16bit modular checksum of each of the address and data-block bytes. This is computed by successive addition of each of the (8-bit) bytes starting with the address bytes and ending with the final data byte and discarding any overflow beyond 16 bits. The resultant 16bit word is then twos complimented and appended, little endian, to the end as the last two bytes of the message. The responses are as follows UFDA=0 UFDA=1 UFDA=2 UFDA=3 UFDA=4 All fine ready for next block All fine Transfer complete Checksum error - Please Repeat message Address out of sequence Length error or UFST has not been issued UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK Update has been completed. There may be many seconds delay UFGO=checksum This command initiates the update process once all the data has been transferred where checksum is a 2s compliment 16 bit checksum of the entire file and presented in decimal. See UFDA command for method of calculation. Responses are as follows UFGO=0 Only for main firmware update. Flag to specify that all was fine and now proceeding with update. The communications will be lost for a short time and when complete a UFGO=1 will be sent;

UFGO=1 before this is issued. UFGO=2 UFGO=3 UFGO=4 UFGO=-n Negative return values during update represent update failure. Each type of update should be done separately i.e. Main Code, FPGA, and BLE updates, we always need to update main code first. We will be providing updates as three separate files where one or more may be needed to be updated at any one time. The AirGlu can determine what each update is for from the contents, you do not have to retain the filenames. Data is not yet complete Checksum does match stored data Old or same update version UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK Appendix TCS Device Capabilities Flags as used in BLSS=n and STSS? requests Capability Has LTC Output function Has LTC Input function Has Genlock Output function Has Word-Clock Output function Has Wi-Fi capability Has BLE capability Has Serial port Bit 0 1 2 3 4 5 6 7-11 Currently unallocated with zero default Has a built-in display and can control brightness Has button control Has internal rechargeable battery Can do zero brightness display setting Can do zero brightness LED flash Can do BLink master 12 13 14 15-19 Currently unallocated with 0 default 20-23 Currently unallocated with 1 default 24 25 26 27-28 Currently unallocated with 0 default 29-31 Currently unallocated with 1 default External Device Capability Flags as used in BLXS=n and GCXS? Requests Bit 0/1 Number of fitted Media Storage units 2 3 4 5-9 Currently unallocated default =0 10-15 Unallocated default =1 16-23 Unallocated default =0 24-31 Unallocated default =1 Transport state can be controlled Can be controlled On or Off Predominantly Video device using FPS (=0) or Audio Bitrate device (=1) Capability UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK Certifications CE TheAirGlumoduleisinconformitywiththeessentialrequirementsandotherrelevant requirementsoftheRadioEquipmentDirective(RED)(2014/53/EU).Pleasenotethatevery applicationusingtheAirGlumodulewillneedtoperformtheradioEMCtestsontheendproduct accordingtoEN30148917.Theconducedtestresultscanbeinheritedfromthemodulestest reporttothetestreportoftheendproductusingAirGlumodule.EN300328radiatedspurious emissiontestmustberepeatedwiththeendproductassembly.Testdocumentationandsoftware fortheEN300328radiatedspuriousemissionstestingcanberequestedfromtheTimecodeSystems support. UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK FCC ThisdevicecomplieswithPart15oftheFCCRules.Operationissubjecttothefollowingtwo conditions:

Thisdevicemaynotcauseharmfulinterference,and Thisdevicemustacceptanyinterferencereceived,includinginterferencethatmaycause undesirableoperation. AnychangesormodificationsnotexpresslyapprovedbyTimecodeSystemscouldvoidtheusers authoritytooperatetheequipment. FCCRFRadiationExposureStatement:

ThisequipmentcomplieswithFCCradiationexposurelimitssetforthforanuncontrolled environment.EndusersmustfollowthespecificoperatinginstructionsforsatisfyingRFexposure compliance.ThistransmittermeetsbothportableandmobilelimitsasdemonstratedintheRF ExposureAnalysisandSARtestreport.Thistransmittermustnotbecolocatedoroperatingin conjunctionwithanyotherantennaortransmitterexceptinaccordancewithFCCmultitransmitter productprocedures.OEMResponsibilitiestocomplywithFCCRegulations:Thetransmittermodule mustnotbecolocatedoroperatinginconjunctionwithanyotherantennaortransmitterexceptin accordancewithFCCmultitransmitterproductprocedures.Eachnewhostwillrequirereassessment ofradiatedspuriousemissionsandapermissivechangetothecertification.ForAirGlumodulethe minimumseparationdistancetohumanbodyis6mm.Iftheseparationdistancefromtheantenna tohumanbodyis6mmormore,SARtestingisnotneeded.Incasetheseparationdistanceto humanbodyislessthan6mm,thenOEMintegratorisresponsibletotesttheSARwiththeend productassembly.OEMintegratorisresponsiblefortestingtheirendproductforanyadditional compliancerequirementsrequiredwiththismoduleinstalled(forexample,digitaldeviceemissions, PCperipheralrequirements,etc.).ImportantNote:Intheeventthatthisconditioncannotbemet

(forcertainconfigurationsorcolocationwithanothertransmitter),thentheFCCauthorizationisno longerconsideredvalidandtheFCCIDcannotbeusedonthefinalproduct.Inthesecircumstances, theOEMintegratorwillberesponsibleforreevaluatingtheendproduct(includingthetransmitter) andobtainingaseparateFCCauthorization. EndProductLabeling TheAirGlumodulenotlabeledwithitsownFCCIDduetoitsphysicalsize.IftheFCCIDisnot visiblewhenthemoduleisinstalledinsideanotherdevice,thentheoutsideofthedeviceintowhich themoduleisinstalledmustalsodisplayalabelreferringtotheenclosedmodule.Inthatcase,the finalendproductmustbelabeledinavisibleareawiththefollowing:

"ContainsTransmitterModuleFCCID:AYVAGLU01"

Or

"ContainsFCCID:AYVAGLU01"

TheOEMintegratormustnotprovideinformationtotheenduserregardinghowtoinstallor removethisRFmoduleorchangeRFrelatedparametersintheusermanualoftheendproduct. UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK ISEDCanada ISEDCanada(English) ThisradiotransmitterhasbeenapprovedbyIndustryCanadatooperatewithitsembedded antenna.Otherantennatypesarestrictlyprohibitedforusewiththisdevice.Thisdevicecomplies withIndustryCanadaslicenseexemptRSSstandards.Operationissubjecttothefollowingtwo conditions:

1.Thisdevicemaynotcauseinterference;and 2.Thisdevicemustacceptanyinterference,includinginterferencethatmaycauseundesired operationofthedevice. RFExposureStatement ExceptionfromroutineSARevaluationlimitsaregiveninRSS102Issue5.AirGlumodulemeetsthe givenrequirementswhentheminimumseparationdistancetohumanbodyislessthanequalto15 mm.RFexposureorSARevaluationisnotrequiredwhentheseparationdistanceis15mmormore. AirGlumodulehasbeentestedforworstcaseRFexposure.AsdemonstratedintheSARtest report,AirGlucanbemountedintouchwithhumanbodywithoutfurtherSARevaluation.Ifthe separationdistanceofAirGluislessthan15mmtheOEMintegratorisresponsibleforevaluating theSAR. OEMResponsibilitiestocomplywithICRegulations Thetransmittermodulemustnotbecolocatedoroperatinginconjunctionwithanyotherantenna ortransmitter.RadiatedemissionmustbetestedwitheachnewhostproductandISEDCmustbe notifiedwithaClass4PermissiveChange.OEMintegratorisresponsiblefortestingtheirend productforanyadditionalcompliancerequirementsrequiredwiththismoduleinstalled(for example,digitaldeviceemissions,PCperipheralrequirements,etc.). Importantnote Intheeventthattheseconditionscannotbemet(forcertainconfigurationsorcolocationwith anothertransmitter),thentheICauthorizationisnolongerconsideredvalidandtheICIDcannotbe usedonthefinalproduct.Inthesecircumstances,theOEMintegratorwillberesponsibleforre evaluatingtheendproduct(includingthetransmitter)andobtainingaseparateICauthorization. EndProductLabeling TheAirGlumoduleisnotlabeledwithICIDbecauseofitssmallphysicalsize.Thefinalendproduct mustbelabeledinavisibleareawiththefollowing:

ContainsTransmitterModuleIC:10427AAGLU01 Or ContainsIC:10427AAGLU01 TheOEMintegratorhastobeawarenottoprovideinformationtotheenduserregardinghowto installorremovethisRFmoduleorchangeRFrelatedparametersintheusermanualoftheend product. UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK ISEDCanada(Franais) Cetmetteurradio(IC:10427AAGLU01)areul'approbationd'IndustrieCanadapourune exploitationavecl'antennepuceincorpore.Ileststrictementinterditd'utiliserd'autrestypes d'antenneaveccetappareil.LeprsentappareilestconformeauxCNRdIndustrieCanada applicablesauxappareilsradioexemptsdelicence.Lexploitationestautoriseauxdeuxconditions suivantes:1.Lappareilnedoitpasproduiredebrouillage;et2.Lappareildoitacceptertout brouillageradiolectriquesubi,mmesilebrouillageestsusceptibledeprovoquerun fonctionnementnondsirdelappareil.Dclarationrelativel'expositionauxradiofrquences(RF) LeslimitesapplicableslexemptiondelvaluationcouranteduDASsontnoncesdansleCNR 102,5edition.LemoduleAirGlurpondauxexigencesdonnesquandladistancedesparation minimumparrapportaucorpshumainestde15mm.L'valuationdel'expositionauxRFouduDAS n'estpasrequisequandladistancedesparationestde15mmouplus.Siladistancedesparation estinfrieure15mm,ilincombel'intgrateurFEOd'valuerleDAS.ResponsabilitsduFEOayant traitlaconformitaveclesrglementsICLeModuleAirGluatcertifipouruneintgrationdans desproduitsuniquementparlesintgrateursFEOdanslesconditionssuivantes:Laoulesantennes doiventtreinstallesdetellefaonqu'unedistancedesparationminimumde15mmsoit maintenueentreleradiateur(antenne)ettoutepersonnetoutmoment.Lemodulemetteurne doitpastreinstallaummeendroitoufonctionnerconjointementavectouteautreantenneou metteur.Dslorsquelesdeuxconditionscidessussontrespectes,aucuntestsupplmentairede lmetteurnestobligatoire.Cependant,ilincombetoujoursl'intgrateurFEOdetesterla conformitdesonproduitfinalvisvisdetouteexigencesupplmentairerequiseaveccemodule install(parexemple,missionsdedispositifsnumriques,exigencesrelativesauxmatriels priphriquesPC,etc).Note:S'ils'avrequecesconditionsnepeuventtrerespectes(pour certainesconfigurationsoulacolocationavecunautremetteur),alorsl'autorisationICn'estplus considrecommevalideetl'identifiantICnepeutplustreemploysurleproduitfinal.Dansces circonstances,l'intgrateurFEOauralaresponsabilitdervaluerleproduitfinal(ycompris l'metteur)etd'obteniruneautorisationICdistincte.tiquetageduproduitfinalL'tiquettedu ModuleAirGluportesonpropreidentifiantIC.Sil'identifiantICn'estpasvisiblequandlemoduleest installl'intrieurd'unautreappareil,alorsl'extrieurdel'appareildanslequellemoduleest installdoitaussiporterunetiquettefaisantrfrenceaumodulequ'ilcontient.Danscecas,une tiquettecomportantlesinformationssuivantesdoittreapposesurunepartievisibleduproduit final."ContientlemodulemetteurIC:10427AAGLU01"ou"ContientIC:10427AAGLU01"

L'intgrateurFEOdoittreconscientdenepasfournird'informationsl'utilisateurfinalpermettant d'installerouderetirercemoduleRFoudechangerlesparamtreslisauxRFdanslemode d'emploiduproduitfinal. UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK JAPAN TheAirGlumoduleiscertifiedinJapanwithcertificationnumberxxxyyyyyy Important ThemoduledoesisnotlabeledwithJapancertificationmarkandIDbecauseofthesmallphysical size.Manufacturerwhointegratesaradiomoduleintheirhostequipmentmustplacethe certificationmarkandcertificationnumberontheoutsideofthehostequipment. ThecertificationmarkandcertificationnumbermustbeplacedclosetothetextintheJapanese languagewhichisprovidedbelow. Translation:

ThisequipmentcontainsspecifiedradioequipmentthathasbeencertifiedtotheTechnical RegulationConformityCertificationundertheRadioLaw. UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR26NJ. UK

AirGlu module photos 2.4GHz Bluetooth LE module Silicon Labs BGM 121 Sub GHz transceiver Silicon labs Si4463 2.4GHz BLE INTERNAL ANTENNA Sub GHz radio EXTERNAL ANTENNA 28.8MHz TCXO AirGlu module photos ProAnt PRO-OB-471 PIFA Antenna 868-915MHz Sub GHz radio EXTERNAL PIFA ANTENNA AirGlu module photos 2.4GHz Bluetooth LE module Silicon Labs BGM 121 Sub GHz transceiver Silicon labs Si4463 REAR PCB

AtomX Sync - Label and position FCC ID and Industry NTT aa Tn MTT al 209-J00371 Contains: & 209-J00226 j Contains: FCC 1D: AYV-AGLUO1 erie AALS NETL a ee Ata

| Input : 6.2V-16.8V DC =

BC CCL SU Lorelt cate Sic fa

(itis KF01107- =~ Q-CO unlonideaienaa aA beorietcnt om ti iW = a AtomX Sync - Label and position FCC ID and Industry AtomX Sync - Label and position FCC ID and Industry a le KF01107 Q-

| it 61 uatttilnartialuntiidtorth eee eee eee

Page | 1 Application note Rev 2.3 2018-06-07 Application note and implementation guideline for 902 - 928 MHz operation OnBoard SMD 868/915 antenna www.proant.se Proant AB Grddvgen 15A, 90620 Ume, Sweden Patent: SE537042 + Pending Phone: +46 (0)90 40150 Page | 2 Application note Rev 2.3 2018-06-07 Table of contents 1. General ........................................................................................................................... 3 2. Intended applications ....................................................................................................... 3 3. Technical data ................................................................................................................. 4 4. Mechanical dimensions ................................................................................................... 5 5. PCB layout ...................................................................................................................... 6 6. Electrical performance ..................................................................................................... 7 7. Radiation pattern ............................................................................................................. 9 8. OnBoard SMD 915 Evaluation board ..............................................................................10 9. General implementation guidelines .................................................................................10 10. Package dimensions ...................................................................................................12 11. Part marking ...............................................................................................................13 12. Disclaimer ...................................................................................................................13 13. Ordering information ...................................................................................................13 www.proant.se Proant AB Grddvgen 15A, 90620 Ume, Sweden Phone: +46 (0)90 40150 Page | 3 Application note Rev 2.3 2018-06-07 1. General This document is a guideline for implementation of the OnBoard SMD 868/915 antenna. The antenna is a combination of small size, low cost and high performance. Integration of embedded antennas is a task that involves tradeoff of different aspects, and this document aims to help when optimizing the performance of the antenna solution. 2. Intended applications The antenna is optimized for the 860 870 MHz and 902 - 928 MHz license free bands. This application note covers 902 928 MHz operation. The frequency optimization to each band is performed by tuning components. ZigBee EnOcean Z-Wave IEEE 802.15.4 902-928 MHz ISO/IEC 14543-3-10 902-928 MHz 900-921MHz www.proant.se Proant AB Grddvgen 15A, 90620 Ume, Sweden Phone: +46 (0)90 40150 Page | 4 Application note Rev 2.3 2018-06-07 3. Technical data Part number Frequency1 Impedance1 Return loss1 Total efficiency1 Dimensions (LxBxH) Assembly Soldering Packing PRO-OB-471 902 - 928 MHz 50

<-6 dB

> 59% (-2.3dB) 34 x 11.6 x 5.0 mm (1.34 x 0.46 x 0.20 in) Pick and place Reflow or equivalent Tape and reel Storage temperature

-40 to +125C Operating temperature

-40 to +125C Maximum temperature 400C RoHS status Compliant with EU directive 2011/65/EU (RoHS 2) Shelf life MSL 10 years Level 1, unlimited Mechanical resistance2 Immunity to vibrations IEC/EN 60068-2-6, Fc test Immunity to shock IEC/EN 60068-2-27, Ea test 1) Measured on the Proant evaluation board 902 928 MHz, PRO- EB-476 2) The product has been tested according to the standard IEC 60721-3-5 Class 5M3 (road vehicles in areas without well-developed road systems, light-weighted vehicles, tracked vehicles and self-propelled machines) www.proant.se Proant AB Grddvgen 15A, 90620 Ume, Sweden Phone: +46 (0)90 40150 Page | 5 Application note Rev 2.3 2018-06-07 4. Mechanical dimensions Antenna pins and keep-out block. Above dimensions are given in millimeter. Antenna drawing. Above dimensions are given in millimeter. www.proant.se Proant AB Grddvgen 15A, 90620 Ume, Sweden Phone: +46 (0)90 40150 Page | 6 Application note Rev 2.3 2018-06-07 5. PCB layout The antenna is developed for optimum performance when mounted on a ground plane, and is therefore very suitably mounted on a printed circuit board, where all empty space in the layout shall be filled solid copper. This also means that no ground cutout area is required under the antenna. If there are several layers in the PCB, there is an advantage to add via holes for interconnection of the ground areas. It is also very important that there is a ground clearance around the NC pads and the RF feed pad, through all layers of the PCB. Otherwise there will be capacitive coupling which may detune the antenna. Pin configuration PCB Layout (from evaluation board) The antenna is preferably positioned along one side of the PCB ground plane, where pin 1 shall be as close as possible to the layout corner. It is also recommended to implement a pi-matching network as seen in the PCB layout to compensate for eventual mismatch due to the practical implementation. The components can be positioned below the antenna next to the feed pad. See chapter 8 for more details. Clearance through all layers www.proant.se Proant AB Grddvgen 15A, 90620 Ume, Sweden Phone: +46 (0)90 40150 Page | 7 Application note Rev 2.3 2018-06-07 6. Electrical performance All results are measured with the antenna mounted on the evaluation board. Return Loss www.proant.se Proant AB Grddvgen 15A, 90620 Ume, Sweden Phone: +46 (0)90 40150 Page | 8 Application note Rev 2.3 2018-06-07 www.proant.se Proant AB Grddvgen 15A, 90620 Ume, Sweden Phone: +46 (0)90 40150 Page | 9 Application note Rev 2.3 2018-06-07 7. Radiation pattern All results are measured at 915 MHz with antenna mounted on the evaluation board. The figure to the right shows the corresponding antenna position for each chart. Gain values are given in dBi. VP = Vertical Polarization, HP = Horizontal Polarization www.proant.se Proant AB Grddvgen 15A, 90620 Ume, Sweden Phone: +46 (0)90 40150 Page | 10 Application note Rev 2.3 2018-06-07 8. OnBoard SMD 915 Evaluation board The evaluation board is developed to simplify antenna testing and evaluation. It has an arbitrary size of 120 x 50 mm and includes an SMA connector. The purpose is to give a reference design for an optimal antenna implementation. The evaluation board can also be used to test other implementations by cutting and soldering the PCB into any device. Evaluation board outline The evaluation board has a matching circuit implemented next to the antenna. This is aimed to enable optimization possibilities for the user. The component positions are sized for 0402 (1005 metric) SMD components. Transmission line C5 C6 C4 Antenna feed Matching circuit C5 C6 C4 The antenna needs a matching circuit to adjust the resonant frequency balance. When delivered, the evaluation board is tuned for optimum balance at the 902-928 MHz frequency band. The component values for this setup are:

C4 = N/A C5 = 1.5nH (Murata LQW15AN1N5B00) C6 = 5.6pF (Murata GJM1555C1H5R6WB01) However, it is common that the resonant frequency will shift during implementation in an arbitrary device. Therefore, this matching may be changed for compensation of such effects. This is further described in chapter 9. www.proant.se Proant AB Grddvgen 15A, 90620 Ume, Sweden Phone: +46 (0)90 40150 Page | 11 Application note Rev 2.3 2018-06-07 9. General implementation guidelines The antenna can be positioned in many ways, although there are some positions which are more beneficial. Below picture shows a typical PCB with two possible antenna positions that give good radiation performance. 2 1

= feed section (pin 1 & pin 2) The antenna should be aligned with the PCB edge if possible. It is also important to align pin 1 & 2 along the outer side of the PCB, and even more preferably close to a corner. The OnBoard SMD 868/915 antenna enables that small electrical components are mounted inside the antenna keep-out block. This may have an impact on the antenna tuning and radiated performance, but is fully possible if there is limited space on the PCB. Another general aspect on surface mounted antennas is regarding the PCB population. If other electrical components are positioned in the surrounding area of the antenna, some impact on the antenna tuning and radiated performance may be expected. It is recommended that such components are distributed below a topographical slope that starts on PCB level at the antenna keep-out block, and slowly increases the height. It shall also be highlighted that plastic and metal parts in the near proximity of antennas may influence the antenna tuning and/or performance. This aspect should be noted as a general guideline for all antennas. The effects are difficult to estimate without detailed information, but it is common that a plastic housing above the antenna shifts the resonant frequency down. It is recommended to measure the antenna in the actual device after implementation. www.proant.se Proant AB Grddvgen 15A, 90620 Ume, Sweden Phone: +46 (0)90 40150 Page | 12 Application note Rev 2.3 2018-06-07 10. Package dimensions The antenna is delivered on tape and reel according to following specifications. The quantity per 13 reel is 250 pcs. 0 B P1 3 13 5

. 4 4 5.50 0 B F 1.50 A0 250 www.proant.se Proant AB Grddvgen 15A, 90620 Ume, Sweden Phone: +46 (0)90 40150 Page | 13 Application note Rev 2.3 2018-06-07 11. Part marking The top marking of the antenna is arranged according to the following illustration. Example top marking 12. Disclaimer The information given in this application note shall in no event be regarded as a guarantee of conditions or characteristics. With respect to any examples or hints given herein, any typical values stated herein and/or any information regarding the application of the device, Proant AB hereby disclaims any and all warranties and liabilities of any kind, including without limitation, warranties of non-infringement of intellectual property rights of any third party. 13. Ordering information For information on sales, delivery terms and conditions and prices, please visit the Proant website

(www.proant.se) for a complete list of distributors. Proant offers consultation with design-in of the OnBoard SMD antennas, as well as design of matching network and transmission lines. Proant have all necessary capabilities for antenna design including anechoic chamber and prototype workshop. Please send your requests to info@proant.se. www.proant.se Proant AB Grddvgen 15A, 90620 Ume, Sweden Phone: +46 (0)90 40150

Cover letter for FCC application FCC ID: AYV-AGLU01 AirGlu module Dear Sirs The AirGlu module contains two radios, a 15.247 FHSS radio operating in the 902 -

928 MHz band and a 15.247 2.4 GHz DTS BLE radio. Sub GHz transceiver, Silicon Labs Si4463, Part No. SI4463-C2A-GM 2.4GHz BLE module, Silicon Labs BGM121, Part No. BGM121A256V2 The approval required is:

Original Certification and Limited modular approval The host device that was used to pursue the Limited modular approval is called the AtomX SYNC. This product by the manufacturer Atomos, uses the AirGlu module for wireless connectivity and also has its own internal battery. Element test reports TMEC0007.8 and TMEC0002.2 are used to demonstrate compliance with FCC 15.247. The output power and spurious radiated emissions portions of TMEC0007.8 supersede those of TMEC0002.2. All other portions of test report TMEC0002.2 are valid except for output power and spurious radiated emissions. Best regards Paul Scurrell CEO Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester. WR2 6NJ. UK www.timecodesystems.com | +44 (0) 1700 808 600 Company No: 726 3683 VAT: 100 7232 75 DocuSign Envelope ID: DE4BB66C-D285-4975-B424-4268965C049D9/2/2019

8th May 2019 Dear Application Examiner:

[Timecode Systems Limited, AirGlu module, FCC ID AYV-AGLU01] is seeking limited modular approval. The radio meets the requirements for modular approval as detailed in FCC 15.212. Compliance to each of the requirements is described below:

1. The modular transmitter must have buffered modulation/data inputs. The EUT has buffered data inputs to insure compliance with Part 15 requirements under conditions of excessive data rates or over-modulation. Please see the Schematics exhibit. 2. The modular transmitter must have its own power supply regulation. The EUT has its own power supply regulation to insure compliance with Part 15 requirements regardless of the quality or level of external DC supplying the module from the host unit. Please see Schematics exhibit. Also, the technical report exhibit contains AC power line conducted emissions data taken with the EUT powered from a linear power supply that contains no EMC suppression components. 3. The modular transmitter must comply with the antenna requirements of Section 15.203 and 15.204(c). The EUT meets the FCC antenna requirements. Please see Antenna information exhibit and internal photos exhibit. 4. The modular transmitter must be tested in a stand-alone configuration. The EUT was tested in an Atomos Atom X SYNC host system. Because of the lack of RF shielding over the radio RF sections of the AirGlu module, this requirement will be met by pursuing limited modular approval with specific host system instead of full modular approval. This Atom X SYNC specific host system is shown in the External Photos. The SYNC X contains a motherboard with a pass-through connector, battery charging circuit and its own Li-Polymer battery. 5. The modular transmitter must be labeled with its own FCC ID number. The EUT is labeled with its own FCC ID number. Please see FCC ID label & location exhibit. If the FCC ID number will not be visible when the module is installed inside a host device, another label with the FCC ID will be applied to the exterior of the host device. 6. The modular transmitter must comply with any specific rule or operating requirements applicable to the transmitter and the manufacturer must provide adequate instructions along with the module to explain any such requirements. The EUT is compliant with all applicable FCC rules. Detail instructions for maintaining compliance are given in the User Manual. 7. The modular transmitter must comply with any applicable RF exposure requirements. The EUT is compliant with all applicable RF exposure requirements. Please see RF Exposure Exhibit. DocuSign Envelope ID: F9A4380B-E519-4DAA-93AC-52A874A9F3A3 Please contact me if you have additional questions. Your attention to this matter is greatly appreciated. Best regards, Paul Scurrell, CEO DocuSign Envelope ID: F9A4380B-E519-4DAA-93AC-52A874A9F3A3

Federal Communications Commission Authorization and Evaluation Division 7435 Oakland Mills Road Columbia, Maryland 21046 Re: Request for confidentiality FCC ID: AYV-AGLU01 To whom it may concern, We hereby respectfully request that under the provision of 47 CFR 0.459 and 0.457(d) the documents listed below and attached with this application for certification be provided with confidential status. AirGlu module_Schematics.pdf AirGlu module_FCC and IC Operational and Technical Description.pdf AirGlu module_Frequency Block Diagrams.pdf Any exhibit / information for which we have requested confidentiality, but which may not be accorded such treatment by the FCC, should be returned to us. The documents listed above contain trade secrets that are treated as confidential by us. Substantial competitive harm to us could result should they be made available to the public. Sincerely, Timecode Systems Limited, Unit 6 Elgar Business Centre, Hallow, Worcester, WR2 6NJ, UK CEO5/8/2019Paul Scurrell