Low-Power RF ZigBee® Software & IEEE 802.15.4

Re: Coordinator send data to rooter

anik — Tue, 06 Oct 2009 13:25:00 GMT

In my code The coordinator and router will join the network after 30 sec without a switch event.

Still both the coordinator and router will open for binding.

they are going to binding state,binding success state ,and unbinding success state again binding state,binding success state ,and unbinding success state.

that is they are repeating like this

I want both devices to be open for binding , coordinator and router bind only once

i.e if a reset or power off I want to bind these agian

please give me a solution

Re: Z-Accel CC2480 + ZASA

simonb — Sat, 27 Jun 2009 11:00:22 GMT

That's what I thought and have decided to write my own aps_groups. I am implementing it on the cc2480 with msp430 has the host cpu.

Is this aps_groups.c file available anywhere?

Thanks for claryfying that.

Simon

Re: Z-Accel CC2480 + ZASA

xyzzy — Fri, 26 Jun 2009 19:57:27 GMT

The source for the aps_AddGroup() function is located in a file called aps_groups.c which is compiled into the library (EndDevice.lib or Router.lib).

Re: Z-Accel CC2480 + ZASA

simonb — Fri, 26 Jun 2009 18:52:32 GMT

Its good to talk.. Especially to yourself !!

Looking at the zstack source code where on earth is the aps_AddGroup source file. There are a number of calls to it but the source is nowhere.

Re: Z-Accel CC2480 + ZASA

simonb — Fri, 19 Jun 2009 16:38:30 GMT

I can see the need for logical cluster id's now that I have the full ZCL working on the cc2480/msp430.

Just just work todo on the AF layer(bindings etc) and then it's on to bulding some fully functioning home automation devices.. At last !!

Re: Z-Accel CC2480 + ZASA

simonb — Fri, 12 Jun 2009 18:44:36 GMT

I am now at the stage of having registered the endpoints with the AF layer and getting access to an incoming AF_MESSAGE.

processing the zcl packet is the biggest part of the jigsaw and looking through the z-stack source code and ha applications it seems that this is as I expected going to be an enormous task.

I don't understand the need to use logical cluster and not real cluster id's as this just bloats the source code.

Re: Coordinator send data to rooter

twincircuits — Sun, 24 May 2009 19:58:37 GMT

OK.... ;-) I got it fixed now. What I did was I had just the Router and ED operational. Once I lengthened the APP_JOIN_TIME to 60 I noticed that the ED was running which meant that it joined to the router.

THen I placed the Coord back into the network and set the devices to where the ED would have to join the network through the router. It joined, but I still was not receiving messages on the Coord. So I went into debug mode on the router and found out it was in fact receiving the message and basically throwing it away.

I then changed the ZB_BINDING_ADDR in the zb_SendDaateRequest statement to 0xFFFC so that a message will be sent from the ED to any router/coordinator. This solved the issue. You see when the ED bound to the router its ZB_BINDING_ADDR was the router so it was doing exactly what it was supposed to / but not what I wanted. Once I said send the message to all routers and the coord the message actually did make it back to the coordinator where I needed it.

All is well again!!!

Re: Coordinator send data to rooter

twincircuits — Sun, 24 May 2009 13:22:56 GMT

No.. It will not join to the router. I set this situation up just to see what would happen and it will not join. I know this because part of the programming sends whatever communications that the router would have received over the Com Port. I got nothing. I am using the new BIDI code that was discussed on the board a while back. So that the devices can send messages both ways. That works great. Now if I can just get a true mesh network up and running, this would solve the issues I have.

Talk to you later.

Re: Coordinator send data to rooter

Dirty Harry — Sat, 23 May 2009 00:58:27 GMT

Will your ZED join the ZR if you power off the ZC? If not, how do you know?

Re: Coordinator send data to rooter

twincircuits — Fri, 22 May 2009 21:14:34 GMT

Hello All,

My code is working better now, but I still have a question / concern. I have one device that is far enough away from the coordinator that it needs to join the network from 1 hop away (through a router....) The CC2480 is able to do this ... Right? If you know how then please point me in the right direction. I am using the sample temperture demo software as my starting point with CCv3....

Right now, my end device will not join the network unless it is brought up in the presense of the coordinator.

Twincircuits

Re: Coordinator send data to rooter

twincircuits — Fri, 08 May 2009 16:02:52 GMT

Thanks!!! I think I'll make a copy of the design and strart stripping out the button press software and other things that will simply be taking up space and sreamline it a litte. This may alliviate the problems.

Talk to you later.

Re: Coordinator send data to rooter

Dirty Harry — Fri, 08 May 2009 15:38:36 GMT

RE: How would you get devices to automatically go to join mode with no button press?

Look at sample_app.c line 770, appStart():

// And now allow the Z-Accel slave to NV restore and auto re-start on resets.
uint8 val = ZCD_STARTOPT_AUTO_START;
zb_WriteConfiguration(ZCD_NV_STARTUP_OPTION, 1, &val);

Don't ever change the auto start setting the way the sample code initialization does.

Hard-coding your devices to be either only ZED or only ZR would result in fantastically more simple, smaller, and easier to understand and follow source code - I recommend it.

Re: Coordinator send data to rooter

twincircuits — Fri, 08 May 2009 15:26:36 GMT

You know..... You may be right.... Recently I have even noticed my coordinator changing states which it should never do....

I added some firmware to get the system into join mode automatically. I did this because since these are line powered devices, if power drops, I want the network to come back up.. (No battery backup....) How would you get these devices to automatically go to join and stay in that mode without the aid of a button push? I played games with the halswcnt = 1; var.... Each device knows what it is supposed to be, I control that in firmware itself, so the button means nothing to me.

After it get's out of its first initialaztion routeen though this var is set back to 0 and I don't have anything else trying to trigger that event. unless of course the button is really pushed, which I can guarntee that it is not.

How much does humidity effect these devices? Do you think there is enough humidity in the air now that it thinks the button was pushed?

Re: Coordinator send data to rooter

Dirty Harry — Fri, 08 May 2009 15:17:02 GMT

Does your H/W suffer a spurious button press that would toggle the "allow join" state of the Routers (reference calls to appToggleJoin())?

Re: Coordinator send data to rooter

twincircuits — Fri, 08 May 2009 12:57:06 GMT

Hello All,

It seems I have broken my code and I don't know where I did it... Let me explain what is happening so that perhaps someone can point me in the right direction. I'm using CC Ver 3 as the compiler for the CC2480 demo kit and using the temperature demo firmware as my starting point. So the capabilites of a Mesh Network is possible with these devices.

In my network, I have a coordinator, router and several end devices. I can bring everything up and get them talking to the coordinator if I'm in the presense of the coordinator. I can then move the end devices away from the coordinator and they will automatically switch their communications to the router. If they ever loose communications they will never rejoin the network even though they are trying every 30 seconds. So, when I'm 1 hop away my end devices will not join the network through a router.

Any idea what area of code I need to look at?

Thanks for your help,

Twincircuits.