SLAU292G November   2009  – July 2015

 

  1.   Read This First
    1.     If You Need Assistance
    2.     Related Documentation from Texas Instruments
    3.     FCC, IC, and Other Geographical Radio Use Restrictions
    4.     Environmental Operating Conditions
    5.     Export Control Regulations
    6.     Patents
    7.     Trademarks
  2. 1eZ430-Chronos™ Overview
    1. 1.1 Overview
    2. 1.2 eZ430-Chronos Features
    3. 1.3 Kit Contents
  3. 2Getting Started
    1. 2.1 Using the eZ430-Chronos Wrist Module Stand Alone
      1. 2.1.1 Setting the Time
      2. 2.1.2 Setting the Date
      3. 2.1.3 Feature Overview and Menu Structure
    2. 2.2 Install Demo Application, Drivers and Firmware
      1. 2.2.1 Windows® Installation
      2. 2.2.2 Linux® Installation
    3. 2.3 Using the eZ430-Chronos Wrist Module With a PC
      1. 2.3.1 Transmission of Acceleration Data and Button Pushes
        1. 2.3.1.1 PC Mouse Control
        2. 2.3.1.2 PowerPoint Control
  4. 3eZ430-Chronos Software
    1. 3.1 Overview
    2. 3.2 eZ430-Chronos Demo Software
      1. 3.2.1 Detailed Feature Overview - Modes Using the Top LCD Line
        1. 3.2.1.1 Time Mode
        2. 3.2.1.2 Alarm Mode
        3. 3.2.1.3 Temperature Mode
        4. 3.2.1.4 Altimeter Mode
        5. 3.2.1.5 Heart Rate Mode - RF Additional accessory or eZ430-Chronos Control Center heart rate simulation required.
        6. 3.2.1.6 Speed Mode - RF Additional accessory or eZ430-Chronos Control Center heart rate simulation required.
        7. 3.2.1.7 Tilt Mode
      2. 3.2.2 Detailed Feature Overview - Modes Using the Bottom LCD Line
        1. 3.2.2.1 Date Mode
        2. 3.2.2.2 Stopwatch Mode
        3. 3.2.2.3 Battery Voltage Mode
        4. 3.2.2.4 Acceleration Mode - RF
        5. 3.2.2.5 PowerPoint Mode - RF
        6. 3.2.2.6 Sync Mode - RF
        7. 3.2.2.7 Calorie/Distance Mode - RF Additional accessory or eZ430-Chronos Control Center heart rate simulation required.
        8. 3.2.2.8 Wireless Update - RF
    3. 3.3 eZ430-Chronos Control Center PC Software
      1. 3.3.1 SimpliciTI Acc/PPT Tab (Mouse and PowerPoint Control)
        1. 3.3.1.1 Acc Mode
        2. 3.3.1.2 PPT Mode
      2. 3.3.2 Key Configuration Tab
      3. 3.3.3 SimpliciTI™ Sync
      4. 3.3.4 BlueRobin™ Heart Rate Simulator
      5. 3.3.5 Wireless Update
    4. 3.4 eZ430-Chronos Data Logger
      1. 3.4.1 Detailed Feature Overview
        1. 3.4.1.1 Data Logger Mode
    5. 3.5 Data Logger PC Software
      1. 3.5.1 SimpliciTI Data Logger
      2. 3.5.2 Wireless Update
    6. 3.6 eZ430-Chronos Software Projects
      1. 3.6.1 IDE Installation
      2. 3.6.2 eZ430-Chronos Software Flow
      3. 3.6.3 eZ430-Chronos Wireless Update Feature
        1. 3.6.3.1 Overview and Components of the Wireless Update Feature
        2. 3.6.3.2 Detailed Description of the Wireless Update Feature
        3. 3.6.3.3 Error Handling
        4. 3.6.3.4 Upgrading Existing eZ430-Chronos Kits
          1. 3.6.3.4.1 RF Access Point Update
            1. 3.6.3.4.1.1 Access Point Based on MSP430F5509 Microcontroller and CC1101 Transceiver
            2. 3.6.3.4.1.2 Access Point Based on CC1111
          2. 3.6.3.4.2 eZ430-Chronos Wrist Module Update
            1. 3.6.3.4.2.1 eZ430-Chronos Wrist Module Update Using IAR
      4. 3.6.4 eZ430-Chronos Firmware
        1. 3.6.4.1 Using Code Composer Studio™ v5.5
        2. 3.6.4.2 Using IAR Embedded Workbench™
      5. 3.6.5 eZ430-Chronos GUI Sources
        1. 3.6.5.1 eZ430-Chronos GUI for Windows
          1. 3.6.5.1.1 TCL/TK Handling
          2. 3.6.5.1.2 Control Center DLL
        2. 3.6.5.2 eZ430-Chronos GUI for Linux
  5. 4eZ430-Chronos Hardware
    1. 4.1 Programming the eZ430-Chronos Wrist Module: Disassembly and Assembly of the Housing
      1. 4.1.1 Disassembly of eZ430-Chronos Wrist Module
      2. 4.1.2 Assembly of eZ430-Chronos Wrist Module
    2. 4.2 Functional Description of the eZ430-Chronos Wrist Module
    3. 4.3 Functional Description of the eZ430-Chronos RF Access Point
      1. 4.3.1 Access Point With Black PCB
      2. 4.3.2 Access Point With White PCB
    4. 4.4 Functional Description of the eZ430-Chronos Debug Interface
      1. 4.4.1 MSP430 Application UART
    5. 4.5 Schematics, Layout, BOM, and LCD
      1. 4.5.1 eZ430-Chronos-433 Wrist Module With Black PCB
      2. 4.5.2 eZ430-Chronos-433 Wrist Module With White PCB
      3. 4.5.3 eZ430-Chronos-868 and -915 Wrist Modules With Black PCB
      4. 4.5.4 eZ430-Chronos-868 and -915 Wrist Modules With White PCB
      5. 4.5.5 LCD
    6. 4.6 Access Point Schematics, Layout, and BOM
      1. 4.6.1 eZ430-Chronos-433 With Black PCB RF Access Point
      2. 4.6.2 eZ430-Chronos-433 With White PCB RF Access Point
      3. 4.6.3 eZ430-Chronos-868 and -915 With Black PCB RF Access Point
      4. 4.6.4 eZ430-Chronos-868 and -915 With White PCB RF Access Point
      5. 4.6.5 Debugging Interface Schematics and Layout
  6. AFrequently Asked Questions
    1. A.1 FAQs
  7. BDetailed Hardware Driver Installation Guide
    1. B.1 Overview
    2. B.2 eZ430-Chronos RF Access Point
    3. B.3 eZ430-RF Debug Interface
  8.   Revision History

FAQs

  1. How Do I visually identify the wrist module's PCB version?
  2. To identify the PCB version, remove the enclosure from the wrist housing and check the PCB color around the pressure sensor or the area around the JTAG connector P1.

  3. My eZ430-Chronos wrist module doesn't respond when I push buttons, instead it shows "Loct" in the LCD?
  4. "Loct" on the 7-segment LCD stands for "Lock" and indicates that the keylock is active. By holding # and DOWN for three seconds simultaneously unlocks or locks the buttons. The LCDs shows "oPEn" when the keylock is disabled.

  5. Why doesn't my eZ430-Chronos wrist module always respond when buttons are pushed?
  6. If buttons are pushed slowly (that is, held down too long), button pushes are ignored.

  7. Why doesn't my eZ430-Chronos wrist module respond when I try to push buttons in short intervals in PPT or ACC mode?
  8. Especially in PPT mode it is important to avoid bouncing of the buttons. Therefore, an artificial delay on the receiver side is implemented. Button pushes are translated into keystrokes or mouse clicks only if there is at least 0.5 seconds between two of them.

  9. Is my eZ430-Chronos waterproof?
  10. Yes, it is 30-m waterproof. This indicates that it resists splashes and rain. However, it cannot be used while taking a shower, swimming, diving, surfing, snorkeling or any other water sports. Set the Chronos module before exposing it to excessive water. Pressing the buttons in water or heavy rainstorms may cause water to enter the Chronos module.

  11. The reported temperature is incorrect, how can I calibrate the sensor?
  12. A temperature offset is stored in Flash, which is calibrated at production. If the offset is erased or is incorrect, it can be changed to an appropriate level; see Section 3.2.1.3 for details.

  13. The reported altitude is incorrect, why is that and how can I calibrate the sensor?
  14. The altitude is determined from barometric pressure. Therefore, the altimeter needs to be recalibrated as the pressure changes with the weather. See Section 3.2.1.4 for details on how to calibrate the altimeter. Moreover, the altitude is a function of the temperature in addition to the barometric pressure. Therefore, the Chronos module needs to have ambient temperature, wearing it on the arm or close to the body may cause inaccurate measurements.

  15. Why is there a timeout for the altimeter?
  16. The altimeter algorithm is implemented according to an application report from VTI. It is not optimized for ultra-low current consumption. For enhanced battery life, the altimeter stops operation after one hour. It can be reactivated by pushing the UP button.

  17. Why are the backchannel pins not connected on the eZ430-Chronos PCB despite the fact that the eZ430-Chronos debug interface supports the backchannel?
  18. All pins of the CC430 were used for the LCD, buttons, or sensors.

  19. Why is there no JTAG connector on the RF access point with black PCB?
  20. The access point is designed to be production ready and as small as possible. Therefore, no debug connector is added. However, it may be programmed by attaching a TI low-power wireless debug interface to the corresponding pads on the bottom of the PCB or by using TI's CC1111EMK868-915.

  21. When I try to compile the source code with IAR KickStart, I get the following error:
    Fatal Error[e89]: Too much object code produced (more than 0x4000 bytes) for this package
  22. IAR KickStart currently has a 16KB code size limitation, and the project being compiled is larger than 16KB (0x4000 = 16384). Select the limited project version in the Workspace pulldown menu of the IDE or use a full license version IAR Embedded Workbench. A 30-day evaluation version of IAR is available from http://supp.iar.com/Download/SW/?item=EW430-EVAL.

  23. When I try to compile the source code with Code Composer Studio v5.5, I get the following error:
    error: output file "eZ430_chronos_ISM_xxx.out exceeds code size limit
  24. Code Composer Studio v5.5 Core Edition is limited to 16KB of code size, and the project being compiled is larger than 16KB. Select the limited project version in the Build Property Configuration pulldown menu of the IDE or use the Platinum Edition of CCS. A 30-day evaluation version is available from http://tiexpressdsp.com/index.php/Category:Code_Composer_Studio_v5

  25. What is the range of the eZ430-Chronos kit?
  26. In free field, distances of up to 100 m (328 ft) have been measured. The range in other conditions, especially within buildings, is difficult to predict and also depends on the protocol stack that is used.

  27. A button fell of the eZ430-Chronos housing after I reassembled it.
  28. The buttons of the eZ430-Chronos module housing are held by small C-clips. If the metal strips for the buttons of the Chronos module bent and stuck at the wrist housing buttons, they could have removed the C-clip. Open the wrist housing, locate the C-clip, and reassemble the button.

  29. How do I know whether I have a 915-MHz, 868-MHz, or 433-MHz kit?
  30. Each eZ430-Chronos kit has a sticker on the box that includes the part number and frequency. The 915-MHz and 868-MHz wrist modules are the same for both frequencies from a hardware perspective. The USB access points are slightly different. The 868-MHz version has a 0-Ω resistor next to the antenna, and the 915-MHz version does not. The 433-MHz wrist modules and access points (with blue antenna and larger than the 915-MHz and 868-MHz versions) are different from a hardware and software perspective and cannot be used for other frequencies.

  31. How do I restore the original software on my eZ430-Chronos wrist module?
  32. The eZ430-Chronos software on the PC contains source code projects as well as flash images, which may be used to restore the original software state of the wrist module. The .txt files are located in C:\Program Files\Texas Instruments\eZ430-Chronos\Recovery. To program the .txt flash images tool such as the Flash Pro Lite software from Elprotronic (www.elprotronic.com) can be used. Ensure that the information memory block D is not erased, as it contains calibration data and the ID of the Chronos module.

  33. I have erased the Chronos module ID and calibration data. What happens now?
  34. If information memory block D was erased, default values for the calibration data and ID are used. See function read_calibration_values() in main.c for details.

  35. I have more than one eZ430-Chronos wrist module connecting to one access point at the same time. How can I prevent this?
  36. Each eZ430-Chronos kit has a unique ID stored in information memory block D. If this block was erased, the ID is equal on all Chronos modules. See FAQ item 17 about restoring the ID value.

  37. Can I purchase the eZ430-Chronos kit or components of it in quantities? Can I get a customized version?
  38. Yes, our partner BM innovations (http://www.bm-innovations.com) provides all components of the eZ430-Chronos kit in volume as well as a range of other products.

  39. Which version of SimpliciTI is used with eZ430-Chronos?
  40. The current software release used SimpliciTI 1.1.1.

  41. The LCD of my eZ430-Chronos remains blank after a wireless update. What can I do?
  42. In case of an error during the wireless update, the Chronos module does not go back to the previous software version as its Flash memory was deleted. To reduce current consumption, the Chronos module is put in low-power mode (LPM4) and the LCD is turned off. As the wireless update software is still active, the update procedure can be started again despite the fact that the LCD remains blank. This can be done, by selecting a flash image (.txt file) on the wireless update tabs of the eZ430-Chronos Control Center PC software and clicking Update eZ430-Chronos Watch. To start the update on the Chronos module, press the DOWN button. The update is started. For details, see Section 3.6.3.

  43. The wireless update procedure always returns an error while downloading to flash.
  44. Make sure that the file you are trying to download does not include data outside the main flash boundaries, which are 0x8000 to 0xFFFF. This protection mechanism avoids writing of data to non-existent or restricted addresses. Try to download one of the original example project’s .txt files, which are available for Windows in C:\Program Files\Texas Instruments\eZ430-Chronos\Recovery\Chronos Watch\Applications and for Linux in /home/<user name>/Texas Instruments/eZ430-Chronos/Recovery/Chronos Watch/Applications. If the update still does not work, the RAM-based update software may be corrupted; see the next question.

  45. The wireless update always returns an error while downloading to RAM.
  46. Make sure that the file named ram_based_updater.txt, which is located on the working directory of your Control Center or Data Logger GUI has not been changed. If so, reinstall the eZ430-Chronos Software to restore the original file.

  47. I get an error message right after I start the wireless update on the PC.
    Failed to start Wireless Update.
  48. Check if the RF access point contains right software version. Kits older than 04/2010 (date code can be found on bottom of the eZ430-Chronos box) require a manual update as described in Section 3.6.3.

  49. Activating the rFbSL mode on the Chronos module always results in a rest.
  50. This is normal. Whenever the wireless update was activated on the Chronos module, it returns to the main application with a reset, regardless if an update was performed or not. Time, data, alarm, and other RAM-based data is lost. For details, see Section 3.6.3.

  51. The buzzer doesn't work when the Chronos module is not inside the housing. What's wrong?
  52. This is normal as the buzzer is located on the metal back of the wrist housing. It is only connected to the Chronos module when the metal back is mounted.