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.

I've some troubles RF Comunication with EM430F6137RF900 Rev. 3.2 EB1

Other Parts Discussed in Thread: SIMPLICITI

Hi,

I've have some troubles with the RF comunication with simpliciTi . I've have a evaluation board EM430F6137RF900 Rev. 3.2 EB1  without watch 32KHz crystals installed.

RF communication works properly with SmartRF 1.5.0. Since SmartRF uses SimpliciTI protocol I tried to comunicate on it with SimpliciTI versión 1.1.1 and the Simple Peer To Peer aplication throught  Code Compose Studio  Version: 4.2.4.00033.

After extensive testing with Simple Peer To Peer Aplication, I found that if I download on the project evaluation board as a transmitter packages (compiling the project with the file main_LinkTo.c), SmartRF receives  packets perfectlyHowever, if I put SmartRF as transmitter and the evaluation board as receiver (compiling file main_LinkListen.c and download on evaluation board ), GETS NOTHING!


I could see is that the firmware updates for SmartRF evaluation board is 2.4.7.1.01. At CCS firmware's version is 2.4.8.02.

 

It would be greatful your help, thanks :)


  • SmartRF Studio does not operate using the SimpliciTI protocol per se.  Instead, you can create packets which are compatible with the SimpliciTI protocol and send them.  Also, SmartRF Studio will receive many kinds of protocol packets as it operates in a much more generic snese overall.

    The reason you see packets with the LinkTo and not with the LinkListen projects are because the SimpliciTI protocol requires a link process be completed before communications can take place.  To accomplish a link, the LinkTo project sends a link request to the LinkListen project.  Since the LinkListen project only listens for the link request before it does any sending of information, you will never see any data sent from it unitl it receives an appropriate link request from another radio.  In this case, you could send it a link request manually in the SmartRF Studio software but you would never be able to change the software back to RX before the LinkListen responded to your link request.

    If you really want to see the packets from both radios, you need to get a third radio.  Use the first two to setup the complete SimpliciTI project, one with the LinkTo code and the other with the LinkListen code.  Then setup the third radio to use SmartRF Studio in RX mode to watch the packets being communicated between the other two radios.  This cause SmartRF Studio to operate in a sniffer mode.  However, a much better solution for this would be to use the SmartRF Sniffer tool available here http://www.ti.com/tool/packet-sniffer.  This software fully understands the SimpliciTI packet architecture and will display the different nwk application layer and user layer packets.

    Jim Noxon

  • Jim,

    Sorry for the delay in response. I stopped using "simplicities" because it uses too much space. We downloaded an example of your company, then, we have tested and works perfect. The only problem we had was not transmitted, because the "SmartRF" saves 0x18 value radio state. Putting a 0x10 and it worked ok

    Anyway, thanks for your reply Jim, I know I can trust with your support.

    Regards from Barcelona