LAUNCHXL-CC1352R1: Asynchronous message from 15.4 Sensor to Collector

Yash 101

Hello,

I am using 15.4 Collector and Sensor in FH mode.

I aim to send Asynchronous messages from Sensor to the Collector. I have appended my message to the buffer which sends the temperature and the Message statistics.

Keeping that into account following are my questions -

1) I figured that calling the process processSensorMsgEvt() on button press fulfills my requirement. But, Is there a better/more efficient way to send messages from Sensor to Collector asynchronously?

2) Calling the function processSensorMsgEvt() on button press sends the complete buffer(including temperature and message stats) to the Collector. I wish to send a user-defined buffer asynchronously while not interfering the buffer that is being sent on reporting interval. Any ideas on how I might be able to do that?

Any help is appreciated.

Thanks and Regards,

Yash.

over 6 years ago

0 Ryan Brown1 over 6 years ago

TI__Guru**** 218637 points

Hello Yash,

I recommend that you create your own Sensor event ID in sensor.h (0x0080 is available) which is set when the key is pressed and uses a different function (independent of processSensorMsgEvt) to send your custom message. You can use processSensorMsgEvt -> sendSensorMessage ->Sensor_sendMsg as a reference for your message framework but in the end it is ApiMac_mcpsDataReq which is used to send the message. http://dev.ti.com/tirex/content/simplelink_cc13x2_26x2_sdk_3_20_00_68/docs/ti154stack/html/ti154stack/frequency-hopping-mode.html#data-exchange

Regards,
Ryan

0 Yash 101 over 6 years ago in reply to Ryan Brown1

Expert 1130 points

Hello Ryan,

Thank you for your quick reply.

Will try that and get back to you.

Thanks and Regards,

Yash.

0 Yash 101 over 6 years ago in reply to Ryan Brown1

Expert 1130 points

Hi Ryan,

First of all sorry for replying so late.

I tried what you suggested but I am still stuck. Will you please elaborate why would I be needing a Sensor event ID? Is it because the WSN node is sleepy?

Also, how will the Collector know that it is going to receive a message? I can see that the buffer sent on Reporting interval is created using frame controls, a Destination address, Pan-ID, etc. So do I have to append the user message being sent asynchronously in a similar way?

In addition to that, what changes do I have to make on the Collector side for receiving the same?

I noticed this line (To transmit an asynchronous frame, ApiMac_mlmeWSAsyncReq should be used.) in the link you provided. I am confused if I have to use ApiMac_mcpsDataReq or ApiMac_mlmeWSAsyncReq ?

Any help is appreciated.

Thanks and Regards,

Yash.

0 Ryan Brown1 over 6 years ago in reply to Yash 101

TI__Guru**** 218637 points

This is the recommended procedure to quickly leave the key callback and allow for the processing of other events/callbacks and is demonstrated in the examples. Data is received in dataIndCB of collector.c similar to configuration and tracking responses as well as sensor data. You can refer to Sensor_sendMsg to see how the sensor project sends sensor data to the collector. The difference in APIs is explained in the Data Exchange section of the Frequency Hopping documentation and you can further refer to the 15.4-Stack MAC API: http://dev.ti.com/tirex/content/simplelink_cc13x2_26x2_sdk_3_20_00_68/docs/ti154stack/mac_api/html/index.html

Regards,
Ryan

Sub-1 GHz

Sub-1 GHz forum

LAUNCHXL-CC1352R1: Asynchronous message from 15.4 Sensor to Collector