Other NXP ProductsのトピックRe: RF4CE communications get stuck

RF4CE communications get stuck

mlopez — Tue, 16 Jul 2013 06:41:17 GMT

We are developing a product with protocol stack RF4CE, MC1323X and Beekit.

I've got one controller and one target devices.

i've found a problem when both controller and target try to send a message at the same time. If that occurs, both try to repeat the message at the same time the same number of times, get stuck during about 2 seconds and both messages fail.

How could I change the timing of the Beekit libraries so this doesn't occur?

Thanks in advance

Re: RF4CE communications get stuck

jasonchiang — Mon, 22 Jul 2013 01:44:12 GMT

Hello Mlopez,
I had similiar "communication fail " when using RF4CE with MC13233 device before, but I called it " no acknowledgement". I fix it by using new codebase release. To make sure if your problem is the smae as mine. Could you capture your log file through protocol analyzer inside the test tool ? I will see what is wrong in your setup.

Regards

Jason

Re: Re: RF4CE communications get stuck

mlopez — Mon, 22 Jul 2013 07:04:25 GMT

Hi,

I use Ubiqua protocol analyzer.

This is the log of the packets found when there is a problem.

Thanks,

mangel

Re: RF4CE communications get stuck

jasonchiang — Tue, 23 Jul 2013 06:09:11 GMT

Hello Mangel,

I open your attached file. It has no acknowledgement for most of packets. What product are you using ? MC13233 or MC13234 ? What is the RF4CE codebase are you using ? I saw this at codebase 1.5.0.

How much time will you see this no acknowledgement when you start to evaluate it ? Did you see this no acknowledgement when you finished pairing and sent lots message between controller and target device ?

Thanks !

Jason

Re: RF4CE communications get stuck

mlopez — Tue, 23 Jul 2013 07:02:17 GMT

Hello Jason,

The product is MC13233. I don't know which is the codebase where we started because it is an inherited project and the people who did it it's not here anymore. Where could I see this in the code? The zigbee libraries are dated in June 2011.

The attached file is a sample of packets. Normally it goes ok, but when one packet does not detect its acknowledge try to repeat it and the other node responds at the same time to the packet. Then both nodes try to repeat at the same time and the same number of times for a pair of seconds and both packets get lost.

This happens after the pairing process, when we are sending application messages.

I also found that sometimes the sender does not get the acknoledge and send the packet again, and I get repeated packets at the end.

There seems to be two different problems in my project: sometimes the sender does not receive the acknowledge, and if two nodes try to send packets at the same time both nodes try to repeat at the same time the same number of times and both packets get lost.

Could it be solved in the last version of the Beekit ?

Thanks,

mangel

Re: RF4CE communications get stuck

jasonchiang — Tue, 23 Jul 2013 09:14:59 GMT

Dear Mangel,

The latest RF4CE codebase 1.6.1 which was released in late 2012 is available in latest beekit 2.0.6. This should resolve your problem which you are encounting. I resolved un-acknowledgement using 1.6.x codebase in late 2012. The codebase you used maybe not the updated version if you used RF4CE codebase in 2011. I suggest you try the latest 1.6.1 codebase(some bugs was fixed).

Thanks !

Jason