Fitness Modules ANT+ Application Note

Transcription

1 Fitness Modules ANT+ Application Note D Rev 3.0

2 Page 2 of 34 ANT+ Managed Network Document Fitness Modules Application Note Rev. 3.0 Copyright Information and Usage Notice This information disclosed herein is the exclusive property of Dynastream Innovations Inc. The recipient and user of this document must be an ANT+ Adopter pursuant to the ANT+ Adopter s Agreement and must use the information in this document according to the terms and conditions of the Adopter s Agreement and the following: a) You agree that any products or applications that you create using the ANT+ Documents and ANT+ Design Tools will comply with the minimum requirements for interoperability as defined in the ANT+ Documents and will not deviate from the standards described therein. b) You agree not to modify in any way the ANT+ Documents provided to you under this Agreement. c) You agree not to distribute, transfer, or provide any part of the ANT+ Documents or ANT+ Design Tools to any person or entity other than employees of your organization with a need to know. d) You agree to not claim any intellectual property rights or other rights in or to the ANT+ Documents, ANT+ Design Tools, or any other associated documentation and source code provided to you under this Agreement. Dynastream retains all right, title and interest in and to the ANT+ Documents, ANT+ Design Tools, associated documentation, and source code and you are not granted any rights in or to any of the foregoing except as expressly set forth in this Agreement. e) DYNASTREAM MAKES NO CONDITIONS, WARRANTIES OR REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, USABILITY, SECURITY, QUALITY, CAPACITY, PERFORMANCE, AVAILABILITY, TIMELINESS OR ACCURACY OF THE ANT+ DOCUMENTS, ANT+ DESIGN TOOLS OR ANY OTHER PRODUCTS OR SERVICES SUPPLIED UNDER THIS AGREEMENT OR THE NETWORKS OF THIRD PARTIES. DYNASTREAM EXPRESSLY DISCLAIMS ALL CONDITIONS, WARRANTIES AND REPRESENTATIONS, EXPRESS, IMPLIED OR STATUTORY INCLUDING, BUT NOT LIMITED TO, IMPLIED CONDITIONS OR WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, DURABILITY, TITLE AND NON-INFRINGEMENT, WHETHER ARISING BY USAGE OF TRADE, COURSE OF DEALING, COURSE OF PERFORMANCE OR OTHERWISE. f) You agree to indemnify and hold harmless Dynastream for claims, whether arising in tort or contract, against Dynastream, including legal fees, expenses, settlement amounts, and costs, arising out of the application, use or sale of your designs and/or products that use ANT, ANT+, ANT+ Documents, ANT+ Design Tools, or any other products or services supplied under this Agreement. If you are not an ANT+ Adopter, please visit our website at to become an ANT+ Adopter. Otherwise you must destroy this document immediately and have no right to use this document or any information included in this document. The information contained in this document is subject to change without notice and should not be construed as a commitment by Dynastream Innovations Inc. Products sold by DYNASTREAM are not designed for use in life support and/or safety equipment where malfunction of the Product can reasonably be expected to result in injury or death. You use or sell such products for use in life support and/or safety applications at your own risk and agree to defend, indemnify and hold harmless DYNASTREAM from any and all damages, claims, suits or expense resulting from such use Dynastream Innovations Inc. All Rights Reserved.

3 ANT+ Managed Network Document Fitness Modules Application Note Rev. 3.0 Page 3 of 34 Revision History Revision Effective Date Description 2.0 Mar 2010 Reformat and re-edits, new figures..fit to FIT and suggested revisions. In rush current condition 2.1 Feb 2011 Added more detail on FIT File transfers and how to process the burst messages 2.2 Feb 2011 Added mounting and labelling information 3.0 May 2013 Added FIT2 Module

4 Page 4 of 34 ANT+ Managed Network Document Fitness Modules Application Note Rev. 3.0 Table of Contents 1 Fitness Modules Overview Related Documents Abbreviations Proximity Pairing Overview Proximity Pairing Performance Channel Allocation Custom Channels Fitness Equipment Broadcast and Receive Channel (FE_Tx/Rx) Fitness Module Controlled Channels Communicating Fitness Equipment State Fitness Equipment States Fitness Equipment to Fitness Module State Messages DATA_ Example Fitness Modules Event Messages Active Search Timeout Event (0x60) Watch Pairing/Unpairing (0x61/0x62) Heart Rate Monitor Communications Example Flow of Information Heart Rate Data Reception Heart Rate Monitor Display Priority Reacquiring Heart Rate Monitors Watch Communications Overview Initiating Watch Communications ANT-FS Channel: FIT File Transfer Processing Burst Transfers to Obtain FIT Files FIT Files FIT Settings File Other FIT files FE_TX/RX Channel: Broadcasting FE Data Use Case: Watch Function Not Supporte Standalone Retrofit Application Description Asynchronous Serial Interface Description Asynchronous Port Control (RTS) Serial Interface Protocol Characteristics... 27

5 ANT+ Managed Network Document Fitness Modules Application Note Rev. 3.0 Page 5 of Message Structure Fitness Modules/ANT Messages Extended Data Messages Determining Heart Rate Source Proximity Pairing Details Factors Affecting Proximity Pairing Distance Adjusting Pairing Distance (0x8F) Settings APPENDIX A: Worked Example of Incoming Settings File FIT1e/FITx Event Messages FIT1e/FITx Download Header Packets FIT1e/FITx Download Data Packets FIT1e/FITx Download Footer Packet... 34

6 Page 6 of 34 ANT+ Managed Network Document Fitness Modules Application Note Rev. 3.0 List of Figures Figure 5-1. Proximity Pairing Procedure... 9 Figure 5-2. ANT+ Link Here Logo Figure 7-1. Fitness Equipment States Figure 7-2. Fitness Equipment State Messaging Figure 9-1. Example of Events and Messages Using the FIT1e/FITx with a Heart Rate Monitor Figure Initiating Watch Communication Figure ANT-FS Data Exchange during a Workout Session Figure FE_TX/RX Channel Message Flow Figure ANT Serial Message Structure Figure Example Message Data List of Tables Table 1-1. Fitness Module Features... 7 Table 3-1. Abbreviations... 8 Table 5-1. Proximity Pairing For ANT+ Devices... 9 Table 6-1. Channel Allocation of Fitness Modules Table 7-1. FE States and Corresponding Fitness Module Activities Table 7-2. RunScript Message Description Table 7-3. SET Message Data_2 Values and FIT1e/FITx Behaviour Table 8-1. Fitness Modules Serial Event Messages Table 9-1. Prioritization of Heart Rate Data by the FIT1e Table FIT File Burst Transfer Packets for FIT1e/FITx to FE Table Data Available from Fitness Equipment Broadcast Table Fitness Modules/ANT Serial Message Details Table ANT_OpenChannel Serial Message Contents Table Extended Message Content Table Pairing Parameters Table Pairing Settings Table Default Settings for Pairing... 32

7 ANT+ Managed Network Document Fitness Modules Application Note Rev. 3.0 Page 7 of 34 1 Fitness Modules Overview The fitness modules (FIT1, FIT1e and FIT2) are application specific ANT modules designed for use in fitness equipment (FE). This application note describes how the fitness modules integrate with fitness equipment to receive ANT+ information from heart rate monitors (HRMs) and exchange information with display devices such as watches. The FIT1e module offers a dual-compatibility interface allowing for reception of both ANT+ HRM and EM/5kHz legacy heart rate monitors (e.g. Polar ). The FIT1 and FIT2 modules offer a similar compatibility interface to the FIT1e but do not support EM/5kHz legacy heart rate monitors. Table 1-1 outlines the features of each fitness module. Table 1-1. Fitness Module Features Supported Features Fitness Modules FIT1e FIT1 FIT2 Proximity pairing for HRM and watches Automated file transfer for User Profile and user selected FIT files Automated file transfer speed 20kb/s 20kb/s Up to 60kb/s ANT+ FE Device Profile supported User configurable ANT+ channels (custom channels) User configurable channel proximity pairing supported 5KHz HRMs supported

8 Page 8 of 34 ANT+ Managed Network Document Fitness Modules Application Note Rev Related Documents It is strongly recommended that the following documents be read and understood prior to using this application note. Refer to current versions of the listed documents. To ensure you are using the current versions, check the ANT+ website at or contact your ANT+ representative. Fitness Modules Overview Sheet FIT1e Data Sheet FIT2 Data Sheet ANT Message Protocol and Usage ANT+ Fitness Equipment Device Profile ANT+ Heart Rate Device Profile ANT File Share (ANT-FS) Technical Specification Flexible and Interoperable Data Transfer (FIT) Protocol FIT File Types Addendum The ANT+ Link Here Branding and Labelling Requirements Fitness Modules Mounting and Labelling 3 Abbreviations Table 3-1 lists the abbreviations used throughout this document. Table 3-1. Abbreviations Abbreviation Meaning Description FE Fitness Equipment Includes cardio equipment such as treadmills, stationary bikes, ro wing machines, climbers, Nordic skiers and ellipticals. HRM Heart Rate Monitor Device worn by the user to sense and broadcast heart rate. ANT-FS ANT File Share This is a file transfer engine built on top of the ANT protocol that allows authenticated bulk data transfer, such as transferring user profiles PCB Printed Circuit Board The hardware which populated with electronic components. FITx Fitness modules including FIT1 and FIT2 Fitness modules excluding those with 5kHz HRM feature.

9 ANT+ Managed Network Document Fitness Modules Application Note Rev. 3.0 Page 9 of 34 4 Proximity Pairing Overview Fitness modules can automatically pair with ANT+ heart rate monitors and watches that are in close proximity to the fitness equipment using received signal strength. This seamless proximity pairing process avoids the need for user-based pairing operations and facilitates the use of ANT+ devices in group environments. Figure 4-1 illustrates the HRM and watch proximity pairing zones, as well as the tracking zone. The tracking zone is the zone within which the FE can communicate with devices during a workout. Step 1: Proximity Pairing 1 a) HRM only 1 b) Watch or watch with HRM Pairing zone Pairing zone FIT1e/FITx FIT1e/FITx Step 2: Workout Tracking zone Figure 4-1. Proximity Pairing Procedure 4.1 Proximity Pairing Performance The fitness modules are calibrated during manufacturing to provide nominal pairing performance as listed in Table 4-1. The actual pairing distance observed once the modules are integrated into fitness equipment will vary depending on how the fitness modules are assembled in relation to other objects in the fitness equipment console. Table 4-1. Proximity Pairing For ANT+ Devices Device Typical Pairing Time Pairing Distance ANT+ HRM ~3s cm ANT+ Watch ~5s 5-10 cm It is possible to adjust the pairing distance to accommodate some of the variance observed. See section 12.2 for details on adjusting pairing settings. The ANT+ Link Here logo shown in Figure 4-2 is used on fitness equipment to inform the user that a piece of fitness equipment is ANT+ compatible. It also provides an indication of the optimal location for proximity pairing. For more information on applying the logo, see the ANT+ Link Here addendum to the ANT+ Branding and Labelling Requirements document.

10 Page 10 of 34 ANT+ Managed Network Document Fitness Modules Application Note Rev. 3.0 Figure 4-2. ANT+ Link Here Logo Fitness equipment devices displaying the ANT+ Link Here logo must receive and display heart rate data from the fitness modules and support proximity pairing.

11 ANT+ Managed Network Document Fitness Modules Application Note Rev. 3.0 Page 11 of 34 5 Channel Allocation Table 5-1 lists the channel allocations for each fitness module. Table 5-1. Channel Allocation of Fitness Modules Fitness Modules Channel Function Configured By FIT1/FIT1e 0-1 Manufacturer (optional) Uses ANT+ Network Key by default. May use another Network Key if Custom 0-1 desired; however careful consideration is required if configuring slave FIT2 8-9 channel on non-ant+ network keys. Refer to section FE Tx/Rx with watch FITx/FIT1e 3-4 ANT+ HRM Rx FITx/FIT1e FITx/FIT1e 5-6 Watch ANT-FS FITx/FIT1e 7 Background Scan FITx/FIT1e 5.1 Custom Channels ANT fitness modules are equipped with customer configurable channels. FIT1 and FIT1e have two while FIT2 has four custom channels which may be configured for transmitting or receiving data from ANT+ devices other than HRMs or watches (e.g. bike cadence sensors). The use of these channels is optional. The behavior of these channels is not automatically handled by the fitness modules and must be initialized through the serial port using standard ANT commands, including proximity pairing configuration. In addition, users should be aware that the status of the custom channels is not dependent on the fitness modules state, (i.e. they can be opened and configured even in the ASLEEP state described in Section 6.1). It is intended that the custom channels (Channels 0-1 and Channel 8-9) be used with ANT+ devices. As such, the FIT1e or FITx s network key is initialized to network number 0. Refer to the ANT Message Protocol and Usage document for information on interfacing to, and controlling, ANT devices. Channel configuration and data transfer from specific ANT+ devices is described in the ANT+ device profiles. Private network keys may be assigned to these custom channels, allowing them to operate on networks other than ANT+. It should be noted that configuring custom channels as slave channels in a non ANT+ network is not recommended, as the fitness modules can only search for devices on a single network at a time. This means that while the fitness modules maintain a background search for ANT+ devices on the ANT+ network, they prevent a non ANT+ slave channel from searching for devices on a non ANT+ network. The ANT+ background search will not, however, affect custom channels from performing as master channels on a private network. Private network keys should be assigned a network number other than 0. NOTE: The automated fitness modules features described in this document do not apply to the custom channels. 5.2 Fitness Equipment Broadcast and Receive Channel (FE_Tx/Rx) After communication with an ANT+ enabled watch has been established, the FE may broadcast data from the session in progress. A treadmill, for example, may send FE data containing information such as the current speed and incline setting. The watch can display/save the received data which may be downloaded by the user. Refer to the ANT+ Fitness Equipment Device Profile for information regarding fitness equipment data formats. The fitness modules will automatically configure and open the FE_TX/RX channel after a watch has successfully paired with the FE. Once the channel is open, the FE must regularly provide the fitness module with data for broadcast. Data is broadcast from the module at 4 Hz for the duration of the watch/fe pairing. Watches may also send information to the FE in the reverse direction on this channel.

12 Page 12 of 34 ANT+ Managed Network Document Fitness Modules Application Note Rev. 3.0 If the fitness equipment does not support watch connections, this channel should be closed. Refer to Section 9 for more details. 5.3 Fitness Module Controlled Channels The remaining five channels are fitness module controlled channels only. The fitness modules use these channels for background searching/pairing, receiving heart rate and file sharing with the watch using ANT-FS. Once pairing is complete, heart rate data and watch file sharing data (if applicable) will arrive separately on two of these four channels (channel 3-6). The relationship between channel number and function is arbitrary. Channels are configured and established automatically and will remain unchanged for that session.

13 User ends session Sustained Inactivity ANT+ Managed Network Document Fitness Modules Application Note Rev. 3.0 Page 13 of 34 6 Communicating Fitness Equipment State It is important for the fitness modules to be informed of the fitness equipment state as it is the FE state that determines which operations the module will perform. For example, the state determines when the fitness module will search for devices or when to send control messages to a paired watch (i.e. start/stop). Functions such as these are handled by the module in order to: Simplify implementation for fitness equipment manufacturers Provide a consistent end-user experience across different FE implementations Provide optimal power management 6.1 Fitness Equipment States The fitness equipment states, including the user interactions required to change states are shown in Figure 6-1. ASLEEP (OFF) Equipment Turned ON User activity Equipment Turned OFF Inactivity READY User presses Start Sustained Activity IN USE Activity Stops User presses Stop User presses Start Activity Resumes FINISHED (PAUSED) Figure 6-1. Fitness Equipment States Initially the fitness equipment may be switched off, or in a low power state. This is the ASLEEP state. Typically, user activity such as pedaling will wake up the FE and activate the user interface. This would be an example of the FE progressing to the READY state. Some FE may never sleep, and would always default to the READY state when not in use. From READY, a button press or sustained activity begins a workout session and puts the FE into the IN USE state. At the end of the workout, a button press or user inactivity may end the session and put the FE into the FINISHED state. From FINISHED, another button press or elapsed time with no activity will return the FE to the READY or ASLEEP state. A summary of the fitness module operations for each FE state is given below in Table 6-1.

14 Page 14 of 34 ANT+ Managed Network Document Fitness Modules Application Note Rev. 3.0 Table 6-1. FE States and Corresponding Fitness Module Activities FE State FE State Descriptions Fitness Modules Activities ASLEEP READY IN USE FINISHED (PAUSED) Applies any time the fitness modules are turned off or in a power saving/sleep mode The fitness modules are turned on/activated, and are waiting for a user to initiate a workout session Corresponds to an active FE session. Chronometer is running Applies when the user stops a workout session. (Pausing or ending workout) The fitness modules are in low power mode. Automated fitness module features are not available. User channels 0-1 and channel 8-9 (FIT2) may be configured and opened. Fitness modules open background scanning channel to search for HRMs and watches to (proximity) pair to. Pairing search does not time out in ready state. If the module pairs to an ANT+ HRM: FE begins receiving heart rate data. If the module pairs to an ANT+ watch: FE will receive the user profile over ANT-FS and begin transmitting FE Data Pages on Channel 2. IN_USE to READY transition initiates a 30 second timer. Regardless of pairing, the fitness modules continue to background search until timer expires, at which point a message is sent to the FE. If the module pairs to an ANT+ HRM: FE begins receiving heart rate data. If the module pairs to an ANT+ watch: FE will receive the user profile over ANT-FS and begin transmitting FE Data Pages on Channel 2. Fitness modules remain paired. To a paired watch: the module sends a message to stop the watch s chronometer. FE should continue sending FE Data Pages to the watch in this state.

15 ANT+ Managed Network Document Fitness Modules Application Note Rev. 3.0 Page 15 of Fitness Equipment to Fitness Module State Messages The FE notifies the fitness module of state changes using one of four messages: FIT1e_OFF/FITx_OFF, FE_READY, FE_IN_USE, and FE_PAUSED. Figure 6-2 shows the relationships between these four messages and the FE State. SET: FIT1e_OFF / FITx_OFF SET: FE_READY SET: FE_READY ASLEEP (OFF) READY SET: FIT1e_OFF / FITx_OFF SET: FE_IN_USE IN USE SET: FE_PAUSED SET: FE_IN_USE FINISHED (PAUSED) Figure 6-2. Fitness Equipment State Messaging FE state messages are sent to the fitness module using a new ANT message definition, designed specifically for use with a fitness module. The ANT_RunScript usage and message format is as follows: ANT_RunScript (0x91) BOOL ANT_RunScript (UCHAR ucdata_1, UCHAR ucdata_2) Table 6-2. RunScript Message Description Byte # Name Length Data Description 0 SYNC 1 Byte 0xA4 SYNC is always 0xA4 1 LENGTH 1 Byte 0x01 Number of data bytes in this message = 1 2 ID 1 Byte 0x91 ANT_RunScript message ID is 0x91 3 DATA_1 1 Byte 0x00 Reserved. Set to 0x00 4 DATA_2 1 Byte See Table 6-3 below for values 5 CHECKSUM 1 Byte 0xEF XOR of all previous bytes including the SYNC byte

16 Page 16 of 34 ANT+ Managed Network Document Fitness Modules Application Note Rev DATA_2 The DATA_2 field is used to specify the FE state message to be sent, as described in Table 6-3. Table 6-3. SET Message Data_2 Values and FIT1e/FITx Behaviour DATA_2 Name Device Pairing Description 0 FIT1e_OFF/FITx_OFF None Resets module. Fitness module features turned off. 1 FE_READY Clear any previous pairing Infinite search 2 FE_IN_USE No Change Searches for 30s 3 FE_PAUSED No Change No change. Search timeout from FE_IN_USE may carry over into FE_PAUSED Example An example of using the runscript message to notify the FIT1e/FITx that the FE state has changed to READY is provided below: ANT_RunScript (0x00, FE_READY): [A4][02][91][00][01][36]

17 ANT+ Managed Network Document Fitness Modules Application Note Rev. 3.0 Page 17 of 34 7 Fitness Modules Event Messages Three serial event messages have been defined for the fitness modules to provide the FE with an awareness of pairing, such that the FE display may provide responsive feedback to the user. These event message codes are additional to the standard ANT Channel Response/Event messages (0x40) as outlined in the ANT Messaging Protocol and Usage document. Table 7-1 provides a detailed description of the three additional event message codes added to the standard ANT protocol, specifically for use with the fitness modules. Table 7-1. Fitness Modules Serial Event Messages Fitness Module Event Description Channel Event Example Active Search Timeout 7 0x60 [A4][03][40][07][01][60][81] FIT1e/FITx Watch Pairing Event 5 or 6 0x61 [A4][03][40][05][01][61][82] Watch Unpairing Event 5 or 6 0x62 [A4][03][40][05][01][62][81] 7.1 Active Search Timeout Event (0x60) To conserve power, the fitness modules will cease searching within 30 seconds of entering the IN_USE state. The fitness modules will notify the FE with the Active Search Timeout message when the 30 seconds has elapsed. This message is sent regardless of whether any pairing has occurred. If no device has been paired with by this time, the FE may alert the user that a pairing search is no longer available. Alternatively, if the FE is already paired to a watch or HRM, and it is receiving and displaying data, then this message may be ignored. The Active Search Timeout Event is sent thirty seconds after the fitness module has entered IN_USE state from READY state. If the fitness module has passed into the FINISHED state before thirty seconds elapses, the message is still sent. 7.2 Watch Pairing/Unpairing (0x61/0x62) The Watch Pairing and Unpairing event messages are sent to provide the FE with a rapid indication of the initiation or termination of pairing with a watch. This allows the fitness equipment to also provide rapid feedback to the user that the watch has been paired or unpaired.

18 Page 18 of 34 ANT+ Managed Network Document Fitness Modules Application Note Rev Heart Rate Monitor Communications 8.1 Example Flow of Information Figure 8-1 shows the typical use case of a user approaching an FE, pairing their HRM, and completing a workout. The FE, FIT1e/FITx and HRM interactions in this diagram are explained in the following sections. FE FIT1e/FITx HRM (ANT+ or EM/5kHz/ FE Turned ON FE system initialization Start FIT1e/FITx Functions FE_READY FIT1e/FITx leaves LoPwr mode Search channel opened HR data ignored HR Data HR Data User Puts On HRM HRM begins transmitting HR Data Rx and displayed ANT+ HR Data Proximity pairing occurs HR Data delivered to FE... strap brought into proximity zone User Starts Session FE Chrono Starts FE Administers Workout FE_IN_USE Active Search T/O 30s timer starts 30s elapses Search channel closed HR Data User Pauses Session FE Chrono Stops FE_PAUSED No effect on HR Data HR Data User Ends Session FE Session Cleared FE Turns off from inactivity FE_READY FE_OFF FIT1e/FITx Unpairs FIT1e/FITx enters LoPwr mode HR data ignored HR Data User Exits Figure 8-1. Example of Events and Messages Using the FIT1e/FITx with a Heart Rate Monitor 8.2 Heart Rate Data Reception Based on the FE state, the FIT1e/FITx automatically handles all HRM channel configuration and pairing. The FE need only be able to receive heart rate information from a paired HRM as it becomes available. The FE will receive heart rate data as serial data on one of the FIT1e/FITx channels [3-4 at approximately 4 Hz. It is a requirement that any FE displaying the ANT+ Link Here logo receive and display the heart rate information received from the FIT1e/FITx. The FIT1e is capable of receiving heart rate from both ANT+ and legacy EM/5kHz HRMs, and FITx is capable of receiving heart rate from only ANT+ HRMs. Heart rate data from either type of HRM is formatted into the same ANT+ serial message by the FIT1e/FITx and delivered to the FE. To indicate which type of heart rate monitor the data is being received from, the FIT1e will use device number = 0 when the data originates from an EM/5kHz heart rate monitor. Details for receiving and interpreting heart rate data are provided in the ANT+ Heart Rate Monitor Device Profile.

19 ANT+ Managed Network Document Fitness Modules Application Note Rev. 3.0 Page 19 of Heart Rate Monitor Display Priority Only ANT+ heart rate monitors can be paired using proximity pairing, as it is an ANT-based feature. Therefore, in cases where the FIT1e detects both ANT+ and EM/5kHz heart rate monitors, the FIT1e prioritizes the heart rate to display according to Table 8-1. Table 8-1. Prioritization of Heart Rate Data by the FIT1e HRMs In Range If ANT+ HRM is proximity paired If ANT+ HRM is not proximity paired ANT+ only FIT1e sends data from the ANT+ HRM that proximity paired. No data sent from the FIT1e. EM/5KHZ & ANT+ FIT1e sends data from the ANT+ HRM that proximity paired FIT1e sends data from EM/5kHz HRM. EM/5KHZ Only N/A FIT1e sends data from EM/5kHz HRM. Proximity pairing requires an intentional user action that can generally only be performed when the user is physically on that piece of FE. For this reason, ANT+ HRMs are given priority over EM/5kHz straps. 8.4 Reacquiring Heart Rate Monitors While in the READY state, or within the first 30 seconds of the IN_USE state, it is possible for an ANT+ HRM to be unpaired by moving out of the tracking zone (see Figure 4-1). Once unpaired, the FITx will resume searching for ANT+ straps and FIT1e will resume searching for ANT+ or EM/5kHz straps to pair to. After 30 seconds from the FIT1e/FITx transitioning to the IN_USE state, the HRM remains paired until the FIT1e/FITx is set to READY or OFF. While paired, and after the active search timeout, if reception from a paired ANT+ HRM is lost the FITx will attempt to reacquire the paired HRM only. The FE will not display HR data from other ANT+ or EM/5kHz strap.

20 Page 20 of 34 ANT+ Managed Network Document Fitness Modules Application Note Rev Watch Communications Overview The FIT1e/FITx provides for communication between FE and ANT+ FE-enabled watches. Watch communications take place on two channels: ANT-FS channel FE_TX/RX The ANT-FS channel is configured by the FIT1e/FITx on channel 5 or 6, and is used to receive FIT data files from the watch immediately after pairing. These files contain user profile information and workouts. After the initial file download, the ANT- FS channel is maintained for the duration of the workout. The FE_TX/RX channel is configured by the FIT1e/FITx on channel 2 and is used to transmit FE data pages at 4 Hz to the watch. For details on the FE data pages, refer to the ANT+ Fitness Equipment Device Profile. This is a bi-directional channel and can also receive information from the watch. Notes: The FE is not required to implement watch communications. See section 9.4. A baud rate setting higher than 9600 is required to receive FIT files from the watch. It is allowable for the FE to receive and use FIT files but not broadcast ANT+ FE messages. It is allowable for the FE to ignore incoming FIT files but still broadcast ANT+ FE messages. 9.1 Initiating Watch Communications The fitness modules use a background scanning channel to simultaneously search for ANT+ HRMs and watches in proximity. To establish communication with an FE, a watch will send an ANT-FS link beacon when put into a special mode by the user. The fitness modules can determine from the received beacon if the watch is close enough to the ANT+ Link Here logo on the FE. The broadcast power of the watch beacon shall be tuned such that the watch must be brought much closer to the ANT+ Link Here logo for pairing, compared to that of an HRM. Refer to the ANT+ Fitness Equipment Device Profile for watch implementation details. Figure 9-1 below illustrates the sequence of events for initiating watch pairing. FE FIT1e/FITx Watch (ANT+ FE enabled FE Turned ON FE system initialization Start FIT1e/FITx Functions FE_READY FIT1e/FITx leaves LoPwr mode Search channel opened beacon ignored Link Beacon Link Beacon User enters training mode Watch transmits ANT-FS Link Beacon Event: Watch Pairing Proximity pairing occurs... Link Beacon watch brought into proximity zone Link Beacon ANT-FS channel opened Session requested Link Cmd AUTH ANT-FS Session FE_TX opened Transport Beacon FE_RX opened Figure 9-1. Initiating Watch Communication

21 ANT+ Managed Network Document Fitness Modules Application Note Rev. 3.0 Page 21 of 34 Once the watch has paired with the FIT1e/FITx, the following occurs: The FIT1e/FITx opens the ANT-FS channel and requests a session with the watch. Once the ANT-FS session is established, the watch will send FIT files to the FE as burst data on one of the FIT1e/FITx channels (5 or 6). See Section 9.2. Once the ANT-FS channel has progressed through the authentication (AUTH) process to the ANT-FS transport state, the FIT1e/FITx and watch will open their respective FE_TX/RX channels. Real time session data is broadcast from the FE to the watch. The watch displays, summarizes, and stores data for later downloading to a PC. See Section 9.4. After files have been transferred from the watch to the FE, the watch beacon continues to beacon, maintaining the ANT-FS connection. While a watch is beaconing in the transport state, it is unavailable for pairing with other FE. The watch continues to transmit the beacon until the FIT1e/FITx disconnects from the watch. Refer to the ANT-FS technical specification for details on ANT-FS beacons and states. 9.2 ANT-FS Channel: FIT File Transfer After pairing occurs, the FIT1e/FITx establishes an ANT-FS session with the watch and automatically downloads up to 10 files, one of which may be a FIT settings file and, if applicable, any user-selected FIT files. Figure 9-2 below shows the sequence of events and the data flow between the FE, FIT1e/FITx and watch. FE FIT1e/FITx Watch (ANT+ FE enabled) Display pairing event Event: Watch Pairing Proximity pairing occurs ANT-FS channel opened Session requested Link Beacon Link Beacon Link Cmd watch brought into proximity zone AUTH Trans Beacon Download Cmd Receive download request Receive burst transfer Process FIT file User profile structure available to FE *burst msgs received Receive FIT file FIT file delivered to FE As series of burst messages Download Response *burst msgs Trans Beacon Send FIT files User starts session User pauses session User ends session FE_IN_USE... FE_PAUSED... FE_READY No effect on ANT-FS Close channels ANT-FS session maintained... Trans Beacon... Trans Beacon ANT-FS session maintained Event: Watch Unpairing ANT-FS session closed ANT-FS session closed Figure 9-2. ANT-FS Data Exchange during a Workout Session

22 Page 22 of 34 ANT+ Managed Network Document Fitness Modules Application Note Rev. 3.0 Once a watch is brought into close proximity, FE pairs with the watch, and opens the ANT-FS channel. On detecting the link beacon, the FIT1e/FITx requests the ANT-FS session using a link command. The ANT-FS session progresses through the authentication (AUTH) process, and the watch starts transmitting the transport (Trans ) beacon. It is at this point that the FIT1e/FITx requests the FIT file downloads. The FIT1e/FITx will automatically request the watch s ANT-FS directory and search for: a FIT settings File user selected FIT files The FIT1e/FITx will request the first settings file that appears in the directory, and the first 9 user selected FIT files that appear in the directory. If no settings file exists, the FIT1e/FITx module may request 10 user selected files. The FIT1e/FITx handles all of the ANT-FS implementation, and the ANT-FS message transactions are not passed to the FE. Instead, only the FIT files themselves are transferred to the FE as a series of burst messages Processing Burst Transfers to Obtain FIT Files Settings and user-selected FIT files are passed from the fitness module to the FE as a series of burst messages (Table 9-1). The first three packets (1:3) received are header packets, and contain information about the file from the ANT-FS directory and download response. Packets 4 through N contain the actual FIT file data, and the footer packet (N+1) contains the CRC, allowing the FE to verify that the file was correctly received. Table 9-1. FIT File Burst Transfer Packets for FIT1e/FITx to FE Packet Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 Bytes 8:12 1 File Index File Data Type (FIT=0x80) File Sub Type (e.g. settings=0x02) File Number FIT File Specific Flags General File Flags 2 File Date Total Remaining Data Length 3 Data Offset File Size 4 FIT File Header (Bytes 0:7) 5 FIT File Header (Bytes 8:11) FIT File data bytes N FIT File data bytes N CRC Ext Msg flag & Channel ID Note, if the FIT file size is not a multiple of 8 bytes, the final packet may contain some zero padding. For example, if a FIT file was 43 bytes, the final packet would contain the final 3 bytes of the file (in bytes 0:2), and five zero-padded bytes (bytes 3:7). Refer to section 13 to see a worked example of processing an incoming settings file. The fitness modules perform the CRC check; however, the FE should check that the footer packet was successfully received in order to determine that the full file was received without error. Note that a complete FIT file will result in a CRC value of 0x0000. Partial file downloads may return a non-zero CRC value in this field. The FE does not need to check the value in the CRC field, only that the footer packet was received. The FIT SDK (available on provides reference code for decoding the settings, workout and/or course files. The FE_DEMO application also provides an example and reference code for fitness equipment.

23 ANT+ Managed Network Document Fitness Modules Application Note Rev. 3.0 Page 23 of Partial File Downloads The FIT1e/FITx module also automatically performs retries on failed file downloads. In this case, the FIT1e/FITx will report an EVENT_TRANSFER_RX_FAIL. If the file transfer failed on CRC checking, then the FIT1e will request the entire transfer again. If the failure is due to RF loss, the FIT1e/FITx will request the data from the point of transfer (i.e. the last known good offset). In the case of partial transfers, the FE should always monitor the details in the header (such as file index, type, size etc) to ensure the file is processed correctly. The FIT1e/FITx will eventually cease retrying failed download of a file. At this point, the FIT1e/FITx will request the next available file for download (if applicable) or, if no other files exist, will simply stop sending any more requests. 9.3 FIT Files A FIT file is a binary file format. The files downloaded by the FIT1e/FITx may include: FIT settings file (including user profile and paired HRM information) User selected FIT file (such as course or workout file). Note, files must be selected on the watch prior to pairing with the FE The FIT files are transferred directly from the watch through the FIT1e/FITx to the FE as a burst transfer. Refer to the FIT SDK for reference code and examples of FIT files FIT Settings File The FIT settings file may include information about the user and device settings. The device settings information may indicate that there is an ANT+ HRM that is paired to the watch. If so, the device ID of that HRM is sent to the fitness module, enabling the module to open a channel and search for the specific HRM without having to perform any proximity pairing. The user profile information includes, but is not limited to: date, time, age, height and weight. For more information on FIT files, messages and fields, refer to the Flexible and Interoperable Data Transfer (FIT) Protocol and FIT File Types documents, and the FIT software development kit Other FIT files For information on other FIT file types supported by FE, refer to the ANT+ FE Device Profile.

24 Page 24 of 34 ANT+ Managed Network Document Fitness Modules Application Note Rev FE_TX/RX Channel: Broadcasting FE Data After pairing with a watch, the FIT1e/FITx provides FE with the ability to broadcast real-time workout data (e.g. time, distance, speed, or cadence). The message format for this data is detailed in the ANT+ Fitness Equipment Device Profile and summarized in Table 9-2. Data is broadcast at 4 Hz for the duration of FE and watch pairing. Data is stored on the watch and summarized on completion of the workout. Summary data can be viewed on the watch and also downloaded to a PC. Table 9-2. Data Available from Fitness Equipment Broadcast Data Page Type Description Requirement General FE Data Page Contains time, distance, speed, cadence, heart rate Required for all FE General Settings Page Contains resistance level, incline, stride/cycle length Optional for all FE. General FE Metabolic Data Page Calories, Calories/hr, METs Optional for all FE. Specific Treadmill Data Page Contains specific data for treadmills: Optional for treadmills. Cadence, vertical distance Not required on other FE Specific Elliptical Data Page Contains specific data for ellipticals: Optional for ellipticals. Vertical distance, stride count, cadence, Not required on other FE power Specific Bike Data Page Contains specific data for bikes: Optional for bikes. Cadence, power Not required on other FE Specific Rower Data Page Contains specific data for rowers: Optional for rowers. Stroke count, cadence, power Not required on other FE Specific Climber Data Page Contains specific data for climbers: Optional for climbers. Cycles, cadence, power Not required on other FE Specific Nordic Skier Data Page Contains specific data for Nordic skiers: Optional for Nordic skiers. Stride count, cadence, power Not required on other FE Manufacturer s information Common Page Contains manufacturer s information Required for all FE Product information Common Page Contains product information Required for all FE Detailed message formats including minimum requirements and additional options are described in the ANT+ Fitness Equipment Device Profile. The FE s state (as shown in Figure 6-1) is also included in every broadcast message to the watch. This state information is used by the watch to control its chronometer such that pressing START on the FE will start the watch s chronometer and, similarly, pressing PAUSE or STOP on the FE will stop the watch s chronometer. This ensures that the FE and watch are synchronized. Note that if broadcasting of data to a watch is not desired, this channel should be closed by the FE. Figure 9-3 shows the sequence of events for the FE_TX/RX channel following pairing.

25 ANT+ Managed Network Document Fitness Modules Application Note Rev. 3.0 Page 25 of 34 FE FIT1e/FITx Watch (ANT+ FE enabled) Proximity pairing occurs ANT-FS session established ANT-FS session established Receive event Send FE 4Hz TX_EVENT FE_Data FE_TX Channel Opened Broadcast 4Hz FE_Data FE_RX Channel Opened Receive 4Hz User starts session FE_IN_USE FE State: IN_USE FE_Data FE State: IN_USE Start chronometer... FE_Data User pauses session FE_PAUSED FE State: PAUSED FE_Data FE State: PAUSED Stop chronometer FE_Data... User ends session FE_READY Event: Watch Unpairing FE State: READY FE_TX Closed FIT1e/FITx unpairs FE_Data FE_RX times out closed Figure 9-3. FE_TX/RX Channel Message Flow 9.5 Use Case: Watch Function Not Supporte Fitness Equipment developers may choose not to implement the FIT1e/FITx watch features. The watch features will still be active on the FIT1e/FITx module, however, and it may pair with a watch that comes into proximity. To ensure consistent performance and good user experience the following details must be handled on the fitness equipment: When the Watch Paired serial event occurs, the fitness equipment should close the FE_TX channel (channel 2). This avoids broadcasting invalid data to the watch. Burst transfer events and burst transfer fail events should be ignored.

26 Page 26 of 34 ANT+ Managed Network Document Fitness Modules Application Note Rev Standalone Retrofit Application 10.1 Description The fitness modules have provision for a simple heart rate pulse output, which provides legacy fitness equipment with a retrofit capacity for EM/5.1KHz and ANT+ straps. This interface does not use the serial port, and as such, only heart rate data can be received. Watch functions, and both the ANT-FS and FE_TX channels are not available in standalone mode. Setting both Baud select pins high will disable the serial port and the FIT1e/FITx will start in FE_READY mode, which is a perpetually sustained search mode. There is no low power mode when the serial port is disabled. In standalone mode the FIT1e/FITx will still pair with watches but the data content of the messages will be empty. When a watch is paired with a FIT1e/FITx and detects empty messages, it should turn off the fitness beacon.

27 ANT+ Managed Network Document Fitness Modules Application Note Rev. 3.0 Page 27 of Asynchronous Serial Interface 11.1 Description The Host MCU and the fitness modules communicate using the asynchronous mode of the serial interface for non-retrofit applications. Please note that all UART communication settings are for one start bit, one stop bit, 8 bits of data and no parity. Data is sent and received LSBit first Asynchronous Port Control (RTS) In asynchronous mode, a full duplex asynchronous serial port is provided with flow control for data transmission from the Host to FIT1e/FITx module. Flow control is performed by the RTS signal, which conforms to standard hardware flow control CMOS signal levels. The signal may therefore be attached to a PC serial port (with use of an RS-232 level shifter), or to any other RS-232 device. The RTS signal is de-asserted for approximately 50 s after each correctly formatted message has been received. This RTS signal duration is independent of the baud rate. Incorrect messages or partial messages are not acknowledged. When the FIT1e/FITx module raises the RTS signal high, the Host MCU may not send any more data until the RTS signal is lowered again. There is no flow control for data being transmitted from the FIT1e/FITx to Host controller, and therefore the Host controller must be able to receive data at any time. NOTE: The RTS signal is raised by the FIT1e/FITx module after the last byte of a message has been received, and the FIT1e/FITx will therefore lose any bytes that were sent, or in the process of being sent, before the RTS signal is acted upon by the Host MCU, and transmission halted. To avoid this problem, either the messages need to be spaced apart by the Host MCU or 0-pad bytes need to be added to the end of each message being transmitted to handle whatever byte pipeline is in place. For example, when considering PC communication, two 0-bytes must be appended to every message, since PCs interpret CTS at the driver rather than the hardware level. The fitness modules will discard any 0-pad bytes received. This issue usually occurs only when using burst transfers from the Host to FIT1e/FITx and high data rates are expected Serial Interface Protocol Characteristics The FIT1e/FITx serial interface protocol follows the standard ANT interface protocol and has the following characteristics: Binary protocol Packets are of variable length Each packet contains an 8-bit Checksum Asynchronous data is transmitted with 1 start, 8 data bits,1 stop bit and no parity, with standard CMOS level signaling Full duplex serial port

28 Page 28 of 34 ANT+ Managed Network Document Fitness Modules Application Note Rev Message Structure The FIT1e/FITx and the Host MCU communicate by transmitting messages to each other. Each serial message is formatted as shown in Figure Sync Msg Length Msg ID Message Content (Bytes 0 (N-1)) Check sum Opt Zero Pad1 Opt Zero Pad2 Figure ANT Serial Message Structure Each variable-length message starts with the SYNC byte and ends with the CHECKSUM (optional zero pad bytes may be added after the checksum as mentioned in section 11.2). Bytes are sent LSBit first, and are detailed below in Table Table Fitness Modules/ANT Serial Message Details Byte # Name Length Description 0 SYNC 1 Byte Fixed SYNC field = (MSB:LSB) 1 LENGTH 1 Byte Number of Data bytes in this message 2 ID 1 Byte 3 N+2 MSG CONTENT_0 MSG CONTENT_N-1 N Bytes Message ID of the ANT Message sent/received 0: Invalid Content of the message N+3 CHECKSUM 1 Byte XOR of all previous bytes (including SYNC) N+4,N+5 Optional Zero PAD bytes 1 or 2 Bytes Zero PAD bytes may be required in conjunction with flow control when doing BURST transfers. The following is an example of how to encode/decode an ANT serial message. ANT_OpenChannel(1) -> SerialData (0xA4, 0x01, 0x4B, 0x01, 0xEF) The details of the contents of this example serial message are shown in the table below. Table ANT_OpenChannel Serial Message Contents Byte # Name Length Data Description 0 SYNC 1 Byte 0xA4 SYNC is always 0xA4 1 LENGTH 1 Byte 0x01 Number of message content bytes in this message = 1 2 ID 1 Byte 0x4B ANT_OpenChannel message ID is 0x4B 3 MSG CONTENT_0 1 Byte 0x01 There is 1 Message Content Byte in this message: This byte is Channel #. It has been set to Channel = 1 4 CHECKSUM 1 Byte 0xEF 0xA4 xor 0x01 xor 0x4B xor 0x01 = 0xEF 11.4 Fitness Modules/ANT Messages Refer to ANT Message Protocol and Usage document for details on the different types of messages and overall ANT protocol description.

29 ANT+ Managed Network Document Fitness Modules Application Note Rev. 3.0 Page 29 of Extended Data Messages The FIT1e/FITx module uses extended data messages when sending received data to the FE. This means that the channel ID of the device that transmitted the data is included in the serial message that the FIT1e/FITx sends to the FE, allowing the Fitness Equipment to identify the source. Extended messages have the following format: [SYNC][LENGTH][ID][CHANNEL][MESSAGE CONTENT 0-7][FLAG FIELD][CHANNEL ID][CHECKSUM] Each byte is outlined in Table Table Extended Message Content Byte # Name Length Description 0 SYNC 1 Byte SYNC is always 0xA4 1 LENGTH 1 Byte Number of Data bytes in this message 2 ID 1 Byte Message ID See ANT Protocol and Usage doc 3 CHANNEL 1 Byte ANT Channel that data originates on 4-11 MESSAGE CONTENT 8 Bytes 8 Byte ANT+ Data See the appropriate message definition for the device type 12 FLAG FIELD 1 Byte Bit field describing extended data: 0x80 4 byte Channel ID 13 Device Number LSB 14 Device Number MSB 2 Bytes Device Number of the ANT+ sensor that transmitted the received message 15 Device Type 1 Byte Device Type of the ANT+ sensor that transmitted the received message 16 Transmission Type 1 Byte Transmission Type of the ANT+ sensor that transmitted the received message 17 CHECKSUM XOR of all previous bytes Figure 11-2 shows an example serial message from the FIT1e/FITx to FE, in the extended data format. In this case, the message was sent from an ANT+ speed sensor and received by the FIT1e/FITx on custom channel 1. [A4] [0E] [4E] [01] [00] [00] [00] [00] [8F] [23] [B7] [ED] [80] [72] [02] [7B] [01] [99] Channel: 1 MSG ID: Broadcast Data ANT+ Data Page Contents Channel ID: Device #: 0x0272 Device Type: 0x7B Trans Type: 0x01 SIZE: 14 Bytes SYNC Flag Checksum Figure Example Message Data

30 Page 30 of 34 ANT+ Managed Network Document Fitness Modules Application Note Rev Determining Heart Rate Source The FIT1e is capable of receiving both ANT+ and EM/5KHz heart rate data. It is possible for the FE to distinguish heart rate received from an ANT+ device versus a heart rate received from an EM/5kHz device. EM heart rate data will only be received on Channel 3 of the FIT1e, and will have a channel ID field consisting entirely of zeros. For example: [A4][0E][4E][03][00][00][00][00][F6][02][08][5A][80][00][00][00][00][61]