Hello,
we were redirected by a asktexas staffmember to get technical support on the CC3000, which we plan to use for a research project. Here is our problem description and need for tech support:
In our research projects, we develop and analyze wireless sensor network systems for industrial applications. One of our major topics in that WSN field is localization and navigation solutions. Since now we were working with CC2430 and CC2530 and developed an hybrid localization system combining a ZigBee radio and an MEMS based IMU. Our localization system is manly working with RSSI values, but we also work on TwTOF measurements to increase accuracy.
Although WLan is consuming more power than ZigBee, it makes sense from our point of view for many applications to ream our system with a WLan radio to take advantage of existing WLan networks. For evaluation purposes we bought an CC3000 Eval-Kit. We liked allot the easy way of getting started into WLan technology, but for further and our specific use we got stuck. Unfortunately the documentation and API functionality is not as broad as we need it to be.
For the start we would like to acquire RSS values of messages being broadcasted from an AP.
How can we read out the RSSI values for each data packed we receive?
Although this is not 100% what we need, we tried and managed to get RSS values with the API function “wlan_ioctl_get_scan_results”.
With the CC3000 Radio Tool we get at least one RSSI value per second displayed, but on the one hand it is not clear how the RSS value is calculated (Is it the value of one broadcast beacon form an AP?) on the other hand in order to use that RSS value in our localization system we would need the protocol of the serial communication. (Which registers are read out to get those RSS values?) Is it possible to get more information on the CC3000 radio core, the registers and the firmware its using?
In addition we are interested in further WLan protocol stack information which is provided only through the debug pins at the CC3000 and only in an binary code with no decoding information. For our use cases we have to analyze the stack information in real-time. Is there a way to get information on the protocol of the debug log?
Thank you very much and best regards
Frank Hartmann
