When using the ziddongle example application from the RemoTI stack 1.3, the software is unable to receive any discovery request frame from a Remote Control. In the old stack 1.2, the messages are received. The application uses the code in appConfig to setup the RTI parameter fields and calls RTI_AllowPairReq to allow incoming messages, but none are recieved in RCN_CbackEvent..
The RF3CE sniffer detects the frames send by the remote control correctly, so there is something in the air, why doesn't the 1.3 stack receive the data? What filtering in the stack is used for these frames? What has been changed in V1.3 in this respect?
Would you please share the Discovery Request message from the trace?
Helps us tracking and improving the quality of our support to the community:
if you were satisfied with the answer and of the support, could you please click on 'Verify this post'?
I tried to include a saved trace from the packet sniffer but that didn't work as expected, so now I have included the result in text.
Here is the frame's content as shown in the generic packet sniffer
Packet index: 1Length: 50Raw data (hex): 41 C8 2B FF FF FF FF CF C0 04 01 00 4B 12 00 2A 14 E5 05 00 01 00 34 12 50 68 69 6C 69 70 73 13 75 57 61 6E 64 00 00 00 00 00 00 00 00 00 00 01 01 FFRSSI [dBm]: -63CRC OK: 1
The RF4CE packet sniffer decodes it as follows:
RX = 1; Time = 0; Length = 52
FCF = 0b01000001; Seq = 2B
DPAN = FFFF; DADDR = FFFF; SADDR=00124B000104C0Cf
NWKFCF = CMD 01 NONE; NWKFCNT = 0005E514; Cmd=Discovery Request; Node capa = 00
App capa=13; UString=uWand; DevTypeLst = 01; ProfileIDList = 01; ReqDevType = FF
LQI=216; FCS = OK
I hope this will help locating the problem.
When investigaing the problem I also ran into a sentence in the module rti.c of the RemoTI stack // Discovery indication will not occur ignored in ZRC discovery procedure.I 'm not sure if it has anything to do with it, but it triggered a bad feeling
I believe the problem is that the NodeCapabilities is set to 0x00. For ZRC security must be enabled. Channel normalization is not required.
uint8 pValue; // node capabilities: Controller, battery-powered, security-capable, ch-norm-incapable pValue = RTI_BUILD_NODE_CAPABILITIES( 0, 0, 1, 1 );
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.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.