-
Notifications
You must be signed in to change notification settings - Fork 3
ConnectionWithZeyphr
- Clip your HxM device to your chest strap
- Put on your chest strap
- Putting the strap on will turn your HxM on.
- Taking the chest strap off will turn your HxM off. Note: In order to ensure a good connection, it might be necessary to sprinkle a small amount of water on the fabric sensors before wearing.
- Make sure you are wearing your HxM (so that it is turned on).
- You will need to first ‘pair’ your HxM with your Mobile Phone with passcode “1234”. (See your phone manual for BlueTooth pairing instructions) Following this, you’ll need to follow the instructions from the provider of the application you are using on your Phone. You should find this information on at (https://www.zephyranywhere.com/media/download/hxm1-ug-p-hxm-bt-user-guide-20130430-v01.pdf)
- Clip your device into the cradle. Connect your cradle to a USB port on your PC.
The ZephyrTM HxMTM Smart Heart Rate Monitor utilizes Bluetooth 4.0 also known as BluetoothTM Smart or BluetoothTM Low Energy. Works with iPhone 4s, iPhone 5 and certain Android based Smartphones. Official Android App : https://play.google.com/store/apps/details?id=com.woxthebox.zephyrsensor&hl=en
Once a Bluetooth connection has been established with the HxM, the data packets can be received by the connecting device. The following sequence diagram shows an example session:
The diagram shows that after the mobile device has connected to the HRM it receives a data packet from the HxM at 1 second intervals. The Heart Rate, Speed & Distance message cannot be disabled. The device will not respond to or acknowledge. Bluetooth Link HxM Heart Rate, Speed & Distance Packet 1 Second Mobile Device or PC. Communications Packet Structure Overview The serial communication between the HxM device and the paired device operates in a simplex mode. The HxM device transmits the HxM data packet and does not process any received data. Basic Message Format Figure
- STX -The STX field (Start of Text) is a standard ASCII control character (0x02) and denotes the start of the message. Although the protocol does not guarantee this value will not appear again within a message, it gives some delimiting to the message and therefore a start character to search for when receiving data.
- Msg ID -The Message ID uniquely identifies each message type and is in binary format. For the HxM the message ID is 0x26 for the standard HxM data packet.
- DLC -The Data Length Code is used to specify the number of bytes within the data payload field of the message. Valid values range between zero and 128 (inclusive). For the standard HxM data packet the DLC has a value of 0x37. 6.1.4.
- Data Payload -This field contains the actual data sent between the local and remote units and can contain anywhere between zero and 128 bytes of data. The number of bytes in this field is dictated by the DLC field.
- CRC -An 8-bit CRC is used and has a polynomial of 0x8C (CRC-8), with the accumulator being initialised to zero before the CRC calculation begins. The following source code indicates the required implementation:
- ETX -The ETX field (End of Text) is a standard ASCII control character (0x03) and denotes the end of the message.
https://www.zephyranywhere.com/resources/developer-user-tools https://www.zephyranywhere.com/media/download/hxm1-api-p-bluetooth-hxm-api-guide-20100722-v01.pdf