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

Control Center DLL

The sources for the DLL are available in the eZ430-Chronos Windows package and can be found in C:\Program Files\Texas Instruments\eZ430-Chronos\Control Center\GUI Sources\DLL.

The eZ430-Chronos Windows DLL has been developed using Microsoft Visual C++ 2008 Express Edition. In order to rebuild the DLL file the Microsoft Visual Studio must be installed, since the registry enumeration code uses MFC functions. If Microsoft Visual Studio is not present, it is still possible to rebuild the DLL, but the "enumser" source code part needs to be removed from the project. Therefore, the BM_GetCOM() function won’t work anymore.

The DLL has two interface sections, one that exports standard C functions, and a second one exporting TCL-compliant functions. These TCL-compliant functions are used by the graphical user interface. Hence, when compiling the DLL, TCL needs to be present in the default directory (C:\Tcl); otherwise, the reference to the TCL libraries (tcl85.lib, tclstub85.lib) is invalid. If the DLL is compiled without the TCL interface, the respective source code file and the references to the TCL libraries must be deleted.

COM Port Management

  1. Opening the COM port
  2. Prior to any communication, the COM port where the RF access point is connected must be opened. The hardware is powered up immediately after the unit is connected. Some parts of the hardware require a startup time of several hundred milliseconds. As a result, any access to the hardware should not be done within one second after connecting the device.

    NOTE

    To address COM ports higher than COM9 in Windows, precede the "COMxx" string with the sequence "\\.\".

    The COM port is opened with the following function:

    bool BM_OpenCOM( char * strPortName, DWORD dwBaudrate = 115200, WORD wTimeout = 30, bool bRTS = false, bool bDTR = false);

    Parameters

    strPortName

    Name of the COM port (for example, "\\.\COM11").

    wTimeout

    Time in milliseconds a reply to a command is expected; default value is 30 ms, should not be changed

    dwBaudrate

    Baudrate for the serial interface; default is 115200 Baud, should not be changed

    bRTS

    State of RTS line during normal operation; default is false (=GND), should not be changed

    bDTR

    State of DTR line during normal operation; default is false (=GND), should not be changed

    Return Value

    Returns true if COM port could be opened, otherwise returns false.

  3. Closing the COM port
  4. A successfully opened COM port must be closed when quitting the application to release all allocated memory and the port itself.

    The COM port is closed with the following function:

    void BM_CloseCOM(void);
  5. Locating the RF access point
  6. This function checks the Windows registry for the friendly name "TI CC1111 Low-Power RF to USB CDC Serial Port" or "eZ430-ChronosAP" and returns the COM port number if the device was found.

    bool BM_GetCOM(unsigned char& bPortNb);

    Parameters

    bPortNb

    Number of the COM port (for example, „11")

    Return Value

    Returns true if device was found, otherwise returns false.

  7. Resetting the RF access point
  8. After power-up, the hardware is not automatically reset. Use the following function to initialize the RF access point hardware. This function can also be used during normal operation if an error condition was detected.

    bool BM_Reset(void);

    Return Value

    Returns true if RF access point could be initialized successfully and false if the reset failed.

  9. Read status from RF access point
  10. This command returns the current RF access point status.

    bool BM_GetStatus(WORD& wStatus);

    Parameters

    wStatus

    Current status of RF access point HW_IDLE, HW_SIMPLICITI_STOPPED, HW_SIMPLICITI_TRYING_TO_LINK, HW_SIMPLICITI_LINKED, HW_BLUEROBIN_STOPPED, HW_BLUEROBIN_TRANSMITTING, HW_ERROR, HW_NO_ERROR, HW_NOT_CONNECTED

    Return Value

    Returns true if command could be executed and false if the command execution failed.

BlueRobin Functions

  1. Set BlueRobin Heart Rate
  2. This command sets the heart rate value that is transmitted in each BlueRobin packet.

    bool BM_BR_SetHeartrate(WORD wHeartrate);

    Parameters

    wHeartrate

    Heart rate in bpm

    Return Value

    Returns true if command could be executed and false if the command execution failed.

  3. Set BlueRobin ID
  4. This command sets the transmitter ID for BlueRobin transmission.

    bool BM_BR_SetID(DWORD dwID);

    Parameters

    dwID

    24-bit transmitter ID

    Return Value

    Returns true if command could be executed and false if the command execution failed.

  5. Read BlueRobin ID
  6. This command reads the transmitter ID for BlueRobin transmission.

    bool BM_BR_GetID(DWORD& dwID);

    Parameters

    dwID

    24-bit transmitter ID

    Return Value

    Returns true if command could be executed and false if the command execution failed.

  7. Start BlueRobin transmission
  8. This command starts the BlueRobin transmission.

    bool BM_BR_Start(void);

    Return Value

    Returns true if command could be executed and false if the command execution failed.

  9. Stop BlueRobin transmission
  10. This command stops the BlueRobin transmission.

    bool BM_BR_Stop(void);

    Return Value

    Returns true if command could be executed and false if the command execution failed.

SimpliciTI Functions

  1. Start SimpliciTI in acc/ppt mode
  2. This command starts SimpliciTI in acc/ppt mode.

    bool BM_SPL_Start(void);

    Return Value

    Returns true if command could be executed and false if the command execution failed.

  3. Start SimpliciTI in sync mode
  4. This command starts SimpliciTI in sync mode.

    bool BM_SYNC_Start(void);

    Return Value

    Returns true if command could be executed and false if the command execution failed.

  5. Stop SimpliciTI
  6. This command exits the SimpliciTI stack.

    bool BM_SPL_Stop(void);

    Return Value

    Returns true if command could be executed and false if the command execution failed.

  7. Read SimpliciTI acc/ppt data
  8. This command reads the received data from the RF access point buffer.

    bool BM_SPL_GetData(DWORD& wData);

    Parameters

    wData

    4 byte data (byte3, byte2, byte1, byte0)

    byte3 = Acceleration value Z-axis

    byte2 = Acceleration value Y-axis

    byte1 = Acceleration value X-axis

    byte0 = 0x11 → Left mouse click (acc mode)

    byte0 = 0x21 → Left mouse double-click (acc mode)

    byte0 = 0x31 → Right mouse click (acc mode)

    byte0 = 0x12 → Button * (ppt mode)

    byte0 = 0x22 → Button # (ppt mode)

    byte0 = 0x32 → Button ↑ (ppt mode)

    byte0 = 0xFF → Data has been read before

    Return Value

    Returns true if command could be executed and false if the command execution failed.

  9. Read SimpliciTI sync buffer status
  10. This command reads the buffer status during sync mode from the RF access point buffer.

    bool BM_SYNC_GetBufferStatus(WORD& wStatus);

    Parameters

    wStatus

    Buffer status

    0 = Buffer empty

    1 = Data available for download

    Return Value

    Returns true if command could be executed and false if the command execution failed.

  11. Read SimpliciTI sync buffer
  12. This command reads the buffer content during sync mode.

    bool BM_SYNC_ReadBuffer(BYTE * bData);

    Parameters

    bData

    19-byte SimpliciTI data Packet content defined Chronos module sending routine

    Return Value

    Returns true if command could be executed and false if the command execution failed.

Wireless Update Functions

  1. Start wireless update
  2. This command starts SimpliciTI in acc/ppt mode.

    BR_COMM_API bool BM_WBSL_Start(void)

    Return Value

    Returns true if command could be executed and false if the command execution failed.

  3. Stop wireless update
  4. This command exits the SimpliciTI stack.

    BR_COMM_API bool BM_WBSL_Stop(void)

    Return Value

    Returns true if command could be executed and false if the command execution failed.

  5. Get status of update
  6. This command reads the buffer status during sync mode from the RF access point buffer.

    BR_COMM_API bool BM_WBSL_GetStatus(DWORD& wData)

    Parameters

    dwData

    Status

    1 = linking

    2 = linked

    4 = error

    Return Value

    Returns true if command could be executed and false if the command execution failed.

  7. Send Data (Text File parts) to the End Device
  8. This command reads the buffer status during sync mode from the RF access point buffer.

    BR_COMM_API bool BM_WBSL_Send_Data(BYTE * data, int len, DWORD& dwData)

    Parameters

    data

    Pointer to byte array

    len

    Array length

    dwData

    Return value

    Return Value

    dwData = Length of last transmitted package.

  9. Get status of packet (checks if a new packet needs to be sent from the GUI)
  10. This command reads the buffer status during sync mode from the RF access point buffer.

    BR_COMM_API bool BM_WBSL_GetPacketStatus(DWORD& wData)

    Return Value

    dwData

    0x80 = error

    0x01 = disabled

    0x02 = processing packet

    0x04 = send info packet

    0x08 = send new data packet