• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 390 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

CCS/LAUNCHXL-CC1350: Ti 15.4 Stack Sensor/ collector example

CCS/LAUNCHXL-CC1350: Audio streaming using Sensor/Collector example

Samyukta Ramnath1
Intellectual 770 points
Part Number: LAUNCHXL-CC1350


Tool/software: Code Composer Studio

Hello,

Would it be possible to modify the sensor-collector example for the TI 15.4 stack? I want to stream audio packets in packet lengths of about 30 bytes at a time (but that can vary). I have gotten the sensor collector example to work and the sensor connects to the collector. I found the point in the code where it is sending the sensor data, and I added about 30 bytes of random numbers. I can see that for every message sent, there are about 56 bytes of configuration information sent with the message. Would this increase the overhead for audio streaming to a point where it would become very inefficient? In other words can I use this example for audio streaming, or would I have to use another example or write my own code entirely?

Warm regards,

Samyukta

  • 0
    TI__Mastermind 23636 points

    Hello Samyukta,

    You can use our SDK ecamples as base. I recommend you create a new message structure in the smgs.h file that directly correlates to your needs. You can also modify the datarate and how fast the data comes out in order to be able to send this data.

    Configuration data does not get sent everytime, only at the beginning of the joining process. 

    Regards.

    AB

  • 0 in reply to AB
    Intellectual 770 points

    Hi AB,

    I tried modifying the base example by adding a buffer in the Smsgs_sensormsg_t struct and trying to send over some dummy data ... I am not able to see the data come over to the collector like the temperature data.

    I added just a test uint8_t value to the Smsgs_sensormsg_t struct, and added it everywhere I saw the other fields (such as tempSensor and lightSensor fields) in the sensor and collector codes. I added a dummy temperature value in the sensor code and a dummy test value of 20.  I was able to see the temperature of 56 on the other side on the collector in the received message, however the test value was zero. That means the temperature value made it over from sensor to collector, but the other values which I added to the struct did not make it from sensor to collector. 

    I added another field to the tempSensor struct and that test value however made it from the sensor to the collector.

    How do I ensure that the data makes it from the sensor to the collector, and also how do I test that the data has made it over?

    And one specific question : what is the purpose of sending the messages LSB first? I can see this being done in the sensor. My audio data buffer is made up of unsigned chars so each is only a byte long, so I did not do anything to that array after populating it.

    Warm regards,

    Samyukta