How to implement SMPL_Init(), SMPL_link, unlink in an infinite loop?

Hi,

I am having a similar problem. I have a device A that connects to device B every time a button is pressed on device A. When device A and Device B have finished communicating they break the link using the SMPL_Unlink command. This all works fine but I have found that I can only connect device A to device B 3 times and the SMPL_Link fails on the 4th attempt. Have you found that the link always fails after a certain number of connections. 

Dave

Hi,

I found the solution to my problem which may be a possible solution to your problem. I did not include Extended API in the Device B software, (It was included in Device A software which is the code that calls SMPL_Unlink) so Device B was not acting on the Unlink command. Enabling Extended API in the Device B fixed the problem.

Dave

Hi Dave,

Thanks for your sharing. My links works only 7 times, also a fixed number.

As you deiscribed, your device A should be ED and B should be AP. RIght? You mentioned enable the Extened API in AP. How to do that?

Thanks,

Sun Li

Hi.

What is the returned status for the failing SMPL_Link()?
Can you try to capture exactly what is happening on the AP side. Have not used CCE, but you should be able to set a breakpoint in the Mrfi_SyncPinRxIsr and then step through the code from there to see what the AP does with this link request.

Regards,
Kjetil

Hi Kjetil,

Thanks very much for your reply. I changed the program. It seems work now, but i did not check the returned status of failing SMPL_Link(). Is there simple function in CCE that i can check this status directly? I always do it step byu step manually.

I just write the following simple test program and did not put it in the whole program. I'd like to check with you whether the program is right or not. 

void

Hi Sun Li,

My device A and device b are both ED's. Sorry I should have mentioned this. To enable the extended API open the file smpl_nwk_config.dat and remove the x in the link -DxEXTENDED_API.

Dave

Hi Dave,

I've tried to use the function SMPL_Unlink, but it come out:  Error[e46]: Undefined external "SMPL_Unlink" referred in demo_ED ( C:\Users\minqian\Desktop\project\code\slac139b changed3\eZ430-RF2500 

Hi,

Are you using the SimpliciTI library (i.e. the .lib file) in your project of are you using the full simpliciTI source. I'm using the full simpliciTI source because as far as I know, and I could be incorrect here, so please anyone correct if I am, the .lib file does not have extended API.

To get Extended API using the full source take a look at the following project:

C:\Texas Instruments\SimpliciTI-IAR-1.1.0\Projects\Examples\EXP461x\Simple_Peer_to_Peer\IAR

You will need to copy most of this code into your project. Make sure you also copy the project settings aswell. You will need to change some of the bsp files to suit your hardware.

Now, to include extended API open the file smpl_nwk_config.dat which is in the Configuration folder and on line 68 remove the x from -DxEXTENDED_API. This will enable extended API.

Hope this helps,

Dave

I am also triing to implement such kind of loop with "Init, Link, Unlink, Do something else with RF (!), Init, Link, Unlink...." with "AP as data hub" scenario on CC430. But I always receive a SMPL_TIMEOUT when calling SMPL_Unlink(sLinkID) on ED even just after successful link. Problem generally is not the timeout, but the fact that ED remains in the table of AP as linked device.

It is not obvious from documentation if SMPL_Unlink may be called from ED or AP or both and whether it is necessary on AP to add some action in the code for Unlink to be successful. Does anybody succeeded with unlinking already?

BTW: I had to modify the SMPL_Unlink call to set sInit_done=0 otherwise the subsequent Init would skip the setup of RF, effectively failing if you use RF for something else in between.

OK, the TIMEOUT is my fault - have to put sInit_done=0 after nwk_unlink...