• Join
  • Sign In with my.TI Login
Texas Instruments
  • Products
  • Applications
  • Tools & Software
  • Support & Community
  • Sample & Buy
  • About TI
Sample & Purchase Cart Sample & Purchase Cart
  • Search
  • Advanced
TI E2E™ Community
  • Support Forums
  • Blogs
  • Groups
  • Videos
  • 简体中文
  • More ...
TI Home » TI E2E Community » Support Forums » Low Power RF & Wireless Connectivity » Low Power RF Proprietary Software & SimpliciTI Forum » Using CC1111EMK dongle to sniff chronos data
Share
Low Power RF & Wireless Connectivity
  • Forums
  • Announcements
  • Files
  • E2E Wiki
Options
  • Subscribe via RSS

Using CC1111EMK dongle to sniff chronos data

Using CC1111EMK dongle to sniff chronos data

This question is not answered
homer12354117
Posted by homer12354117
on Oct 02 2011 09:35 AM
Prodigy80 points

Hi

I am trying to use the CC1111 dongle to sniff the data from chronos watch. I verified that the packet sniffer and dongle is working correctly by successfully sniffing data from a CC1110 module. I am also verified that the watch is transmitting data because the CC1111 that comes with the watch has its LED blinking and the acceleration data on the screen in the control center software.

But, when I turn on the packet sniffer I dont see any data. The RF settings I am using for the dongle are

 

# Deviation = 32.226562

 

# Base frequency = 905.998901

# Carrier frequency = 905.998901

# Channel number = 0

# Carrier frequency = 905.998901

# Modulated = true

# Modulation format = GFSK

# Manchester enable = false

# Sync word qualifier mode = 30/32 sync word bits detected

# Preamble count = 4

# Channel spacing = 199.951172

# Carrier frequency = 905.998901

# Data rate = 76.7212

# RX filter BW = 300.000000

# Packet length mode = Variable packet length mode. Packet length configured by the first byte after sync word

# CRC enable = true

# Packet length = 255

# Device address = 0

# Address config = No address check

# PA ramping = false

# TX power = 0

#---------------------------------------------------

# Packet sniffer settings for: CC1111

#

PKTCTRL0 | 0xDF04|0x05|Packet Automation Control

FSCTRL1 | 0xDF07|0x06|Frequency Synthesizer Control

FREQ2 | 0xDF09|0x25|Frequency Control Word, High Byte

FREQ1 | 0xDF0A|0xBF|Frequency Control Word, Middle Byte

FREQ0 | 0xDF0B|0xFD|Frequency Control Word, Low Byte

MDMCFG4 | 0xDF0C|0x5B|Modem configuration

MDMCFG3 | 0xDF0D|0xA3|Modem Configuration

MDMCFG2 | 0xDF0E|0x13|Modem Configuration

MDMCFG1 | 0xDF0F|0x23|Modem Configuration

MDMCFG0 | 0xDF10|0x11|Modem Configuration

DEVIATN | 0xDF11|0x43|Modem Deviation Setting

MCSM0 | 0xDF14|0x18|Main Radio Control State Machine Configuration

FOCCFG | 0xDF15|0x17|Frequency Offset Compensation Configuration

FSCAL3 | 0xDF1C|0xEA|Frequency Synthesizer Calibration

FSCAL2 | 0xDF1D|0x2A|Frequency Synthesizer Calibration

FSCAL1 | 0xDF1E|0x00|Frequency Synthesizer Calibration

FSCAL0 | 0xDF1F|0x1F|Frequency Synthesizer Calibration

TEST2 | 0xDF23|0x81|Various Test Settings

TEST1 | 0xDF24|0x35|Various Test Settings

TEST0 | 0xDF25|0x09|Various Test Settings

PA_TABLE0| 0xDF2E|0x8E|PA Power Setting 0

 

I obtained these settings from the file SMARTRF_CC430.H in the chronos directory. I generated the above  settings using the SmartRF tool by running it in the offline mode for the cc1111 and exporting the data. But I still dont see any data. Any idea what could be wrong ?

 

Report Abuse
  • Reply
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
All Replies
  • ym lu
    Posted by ym lu
    on Oct 06 2011 09:09 AM
    Prodigy65 points

    Hi homer ,

    I have got the same problem:

    CC1111 EMK dongle programmed as Packet Sniffer, but can't capture the packets I want.

    I try to use Packet Sniffer to capture packets between a pair of eZ430 Chrono Watch and Access Point (CC1111 that comes with the watch). But I captured some strange packets instead.

    Here is how I did it, please advise if anything might be wrong.

    1) I programmed a CC1111 usb dongle as a Packet Sniffer use the firmware image<sniffer_fw_ccxx11.hex> use SmartRF Flash Programmer

    2) I power up and configured eZ430 Chrono Watch and AP to transmit under the ACC mode, so that I can see the real time acceleration data sent from the watch use Control Center.

    Problem: 

    I Can't see the packets that contains Acceleration data/Application payloads, Instead, the packet sniffer captures 1 packet every 3~9 mins. All captured packet has a FCS error

    Please help and advise on this.

    ming

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Gerry Simmons
    Posted by Gerry Simmons
    on Mar 28 2012 19:08 PM
    Intellectual850 points

    I just got this to work myself. The clues were in the Chronos Watch Software. Deep in the source -> Software Projects\Chronos Watch\CCS\Sports Watch\simpliciti there is a file called simpliciti.h. in the header comments:

    // SimpliciTI packet size (TX only mode)
    // -------------------------------------
    //
    //   * packet rate   (100/3) packets/second = 33.3 packets/second    
    //  * packet length   28 bytes
    //  * packet structure  4 bytes  preamble
    //        4 bytes  sync
    //        1 bytes  length
    //        1 bytes  address
    //        16 bytes  data
    //          12 byte network data
    //          4  byte user data
    //        2 bytes  crc
    //
    // SimpliciTI frequency overview
    // -----------------------------
    //
    // CC430_End_Device_433MHz.lib (433MHz ISM band)
    //
    //  * base frequency  433.92 MHz
    //  * deviation    32 kHz
    //  * channel spacing  25 kHz
    //  * used channel number 0 (frequency agility/hopping disabled)
    //  * data rate    76.8 kBaud
    //  * output power   1.4 dBm
    //  * duty     9,6% (TX only mode, 32 packets / second)
    //
    // CC430_End_Device_868MHz.lib (868MHz ISM band)
    //
    //  * base frequency  869.525 MHz
    //  * deviation    32 kHz
    //  * channel spacing  25 kHz
    //  * used channel number 0 (frequency agility/hopping disabled)
    //  * data rate    76.8 kBaud
    //  * output power   1.1 dBm
    //  * duty     9,6% (TX only mode, 32 packets / second)
    //
    // CC430_End_Device_915MHz.lib (915MHz ISM band)
    //
    //  * base frequency  902.000 MHz
    //  * deviation    32 kHz
    //  * channel spacing  200 kHz
    //  * used channel number 20 (frequency agility/hopping disabled)
    //  * data rate    76.8 kBaud
    //  * output power   1.3 dBm
    //  * duty     9.6% (TX only mode, 32 packets / second)

    I then brought up SmartRF Studio 7, double-clicked on CC1111, left it in Easy Mode, but clicked the check box for displaying the registers and RF parameters. I plugged in the 915MHz parametrics for the watch, left the crystal at 48MHz. I also set the Filter BW to  around 3X niquist of the data rate.

    I selected simpliciTi 1.1.0 as the protocol in the SmartRF Packet Sniffer S/W. Entered all the register values from SmartRF Studio, WROTE a chronos_watch_sniffer.prs file (important step!) and Voila!  Packets from my Watch and Access point started streaming by.

    My register settings in Packet Sniffer S/W w/ CC1111EMK

    PKTCTRL0 | 0xDF04|0x05|Packet Automation Control

    FSCTRL1 | 0xDF07|0x0C|Frequency Synthesizer Control

    FREQ2 | 0xDF09|0x25|Frequency Control Word, High Byte

    FREQ1 | 0xDF0A|0x95|Frequency Control Word, Middle Byte

    FREQ0 | 0xDF0B|0x55|Frequency Control Word, Low Byte

    MDMCFG4 | 0xDF0C|0x7B|Modem Configuration

    MDMCFG3 | 0xDF0D|0xA3|Modem Configuration

    MDMCFG2 | 0xDF0E|0x13|Modem Configuration

    MDMCFG1 | 0xDF0F|0x23|Modem Configuration

    MDMCFG0 | 0xDF10|0x11|Modem Configuration

    DEVIATN | 0xDF11|0x43|Modem Deviation Setting

    MCSM0 | 0xDF14|0x18|Main Radio Control State Machine Configuration

    FOCCFG | 0xDF15|0x1D|Frequency Offset Compensation Configuration

    BSCFG | 0xDF16|0x1C|Bit Synchronization configuration

    AGCCTRL2 | 0xDF17|0xC7|AGC control

    AGCCTRL1 | 0xDF18|0x00|AGC control

    AGCCTRL0 | 0xDF19|0xB0|AGC control

    FREND1 | 0xDF1A|0xB6|Front end RX configuration

    FSCAL3 | 0xDF1C|0xEA|Frequency Synthesizer Calibration

    FSCAL2 | 0xDF1D|0x2A|Frequency Synthesizer Calibration

    FSCAL1 | 0xDF1E|0x00|Frequency Synthesizer Calibration

    FSCAL0 | 0xDF1F|0x1F|Frequency Synthesizer Calibration

    TEST1 | 0xDF24|0x31|Various Test Settings

    TEST0 | 0xDF25|0x09|Various Test Settings

    PA_TABLE0| 0xDF2E|0x8E|PA Power Setting 0

    IOCFG0 | 0xDF31|0x06|Radio Test Signal Configuration

    CC1111 Packet Sniffer CC430 chronos
    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Paolo Di Prodi95235
    Posted by Paolo Di Prodi95235
    on Aug 01 2012 07:57 AM
    Prodigy130 points

    The latest firmware has changed in the channel spacing I have noticed from my file, for example the EU parameters are now:

    // ISM_EU configuration
    //
    // Chipcon
    // Product = CC1101
    // Chip version = A   (VERSION = 0x04)
    // Crystal accuracy = 10 ppm
    // X-tal frequency = 26 MHz
    // RF output power = 0 dBm
    // RX filterbandwidth = 232.142857 kHz
    // Deviation = 32 kHz
    // Datarate = 76.766968 kBaud
    // Modulation = (1) GFSK
    // Manchester enable = (0) Manchester disabled
    // RF Frequency = 869.524963 MHz
    // Channel spacing = 199.951172 kHz
    // Channel number = 0
    // Optimization = -
    // Sync mode = (3) 30/32 sync word bits detected
    // Format of RX/TX data = (0) Normal mode, use FIFOs for RX and TX
    // CRC operation = (1) CRC calculation in TX and CRC check in RX enabled
    // Forward Error Correction = (0) FEC disabled
    // Length configuration = (1) Variable length packets, packet length configured by the first received byte after sync word.
    // Packetlength = 255
    // Preamble count = (2)  4 bytes
    // Append status = 1
    // Address check = (0) No address check
    // FIFO autoflush = 0
    // Device address = 0
    // GDO0 signal selection = ( 6) Asserts when sync word has been sent / received, and de-asserts at the end of the packet
    // GDO2 signal selection = (41) CHIP_RDY

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
TI E2E™ Community
  • Support Forums
  • Blogs
  • Videos
  • Groups
  • Site Support & Feedback
  • Settings
TI E2E™ Community Groups
  • TI University Program
  • Make the Switch
  • Microcontroller Projects
  • Motor Drive & Control
Other Communities
  • Deyisupport
  • Designsomething.org
  • beagleboard.org
  • TI on Element 14
  • TI on TechXchangeSM
Other Technical & Support Resources
  • WEBENCH® Design Center
  • Product Information Centers
  • Technical Documents
  • TI Design Network
  • TI Technical Articles
  • TI Training

All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.

Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI, its suppliers and providers of content reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

Follow Us Texas Instruments on Facebook Texas Instruments on Twitter Texas Instruments on LinkedIn Texas Instruments on Google+
TI Worldwide | Contact Us | my.TI Login | Site Map | Corporate Citizenship | mobile m.ti.com (Mobile Version)

TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs and
embedded processors, along with software, tools and the industry’s largest sales/support staff.

© Copyright 1995-2013 Texas Instruments Incorporated. All rights reserved.
Trademarks | Privacy Policy | Terms of Use