Hello Mr Jan Hauer!
Thank you so much for your detailed explanation. It help me to understand more.
(*) I tried to make the code for n2. (MLME_START executed immediately after
MLME_SCAN)
- Firstly, n2 scan network with MLME_SCAN (at MLME_RESET.confirm), if scan is
successful,
then n2 synchronize to n1 with MLME_SYNC, after that transfer data to n1 with
MCPS_DATA.request.
- Secondly,n2 start network with MLME_START (at MLME_RESET.confirm) and
transmits periodic beacons
itself and wait for incoming data frames from n3 by MCPS_DATA.indication
(*) So, now my code can run but it doesn't work efficiently. The delay time for
received frame from n3 and
transfer frame to n1 so big. And I think in n2 occur the collision but not sure.
(*) Do you have any solution for that? Please give me some advice to improve my
code. Once again, thanks for
your reply. Looking forward to hearing from you!
With my best regard!
Sincerly yours,
Dzung Vu Anh
NGN LAB - Computer Engineering
AnDong National University - Andong si - South Korea
Tel: +82 54 -820 -7944
Mobile: 010-6427-1983
> Date: Fri, 26 Mar 2010 10:35:10 +0000
> Subject: Re: [Tinyos-help] Please Help me with TKN154! Thanks in advance.
> From: [email protected]
> To: [email protected]
> CC: [email protected]; [email protected]
>
> > (*My problem*) To join and transfer message to the network of Coordinator is
> > ok, but in part of start another network by using MLME_START.request
> > is not running. and Cluster head cannot start a new network, communicate
> > with Sensor node. The Responsibility of Cluster head is dual
> > function: one for Sensor node and another one for Coordinator.
>
> It sounds like you want to build a multihop network in a
> beacon-enabled PAN. The simplest would be a 3-node topology n1 <-> n2
> <-> n3, i.e. n3 should reach n1 only via n2. Assuming that n1 is you
> PAN coordinator, it would start the network with MLME_START. n2 would
> first scan for/track the beacons of n1 (MLME_SYNC) and afterwards
> transmit periodic beacons itself (MLME_START with an appropriate
> StartTime parameter). Finally n3 would scan for/track the beacons of
> n2 (MLME_SYNC). Before you try this, make sure that you use the latest
> cvs version, because there were some fixes lately.
> http://sourceforge.net/projects/tinyos/develop
>
> > (*) I have some questions:
> > - How can I use multi channel in one device such as Coordinator and Cluster
> > head?
>
> Do you mean multiple channels (RF frequencies) in the same PAN? This
> is not supported in IEEE 802.15.4-2006.
>
> > - How can I make the Cluster head has dual function for Coordinator and
> > Sensor node?
>
> This would be n2 (see above)
>
> > - In the Makefile, what's meaning of CFLAGS += -DIEEE154_BEACON_TX_DISABLED,
> > PFLAGS += -DIEEE154_BEACON_SYNC_DISABLED -DIEEE154_SCAN_DISAB! LED?
> > and where can I find DIEEE154_BEACON_TX_DISABLED?
>
> These flags disable some modules to save memory. See
> tinyos-2.x/tos/lib/mac/tkn154/TKN154.h (line 233 and below)
>
> Jan
>
> 2010/3/24 Anh Dung Vu <[email protected]>:
> > Hello everyone!
> >
> > Now I feel very confusing about the TKN154. I appreciate any answer for me,
> > this will help me much!
> >
> >
> > (*) First time: I can make the code to communication and transfer data
> > between Coor and SN. (It's running ok)
> > - Coordinator interfaces: MLME_RESET, MLME_START, MCPS_DATA, MLME_ASSOCIATE,
> > MLME_SET, MLME_GET...
> > Coordinator start network and receive message from Sensor node and then send
> > another message to sensor node.
> > - Sensor node interfaces: MLME_RESET, MLME_SCAN, MCPS_DATA, MLME_ASSOCIATE,
> > MLME_SET, MLME_GET...
> > Sensor node join to the network of coordinator, send message to coordinator
> > and then receive message from coordinator
> >
> > (*) Now I want to build the system including: Coordinator (Coor), Cluster
> > head (CLH) and Sensor node (SN). I want to
> > build Cluster head (CLH) to do this thing as follow:
> > - firstly, Cluster head join to the network of Coordinator by using
> > MLME_SCAN, MLME_ASSOCIATE
> > - Secondly, if j! oining network is successful, Cluster head will start
> > another network for Sensor node by using MLME_START
> > - Thirdly, Cluster head receive message from Coordinator and then forward to
> > Sensor Node, after that Cluster head receive
> > message from Sensor node and forward to Coordinator.
> > (*My problem*) To join and transfer message to the network of Coordinator is
> > ok, but in part of start another network by using MLME_START.request
> > is not running. and Cluster head cannot start a new network, communicate
> > with Sensor node. The Responsibility of Cluster head is dual
> > function: one for Sensor node and another one for Coordinator.
> >
> > (*) I have some questions:
> > - How can I use multi channel in one device such as Coordinator and Cluster
> > head?
> > - How can I make the Cluster head has dual function for Coordinator and
> > Sensor node?
> > - In the Makefile, what's meaning of CFLAGS += -DIEEE154_BEACON_TX_DISABLED,
> > PFLAGS += -DIEEE154_BEACON_SYNC_DISABLED -DIEEE154_SCAN_DISAB! LED?
> > and where can I find DIEEE154_BEACON_TX_DISABLED?
> >
> > Do yo u have any solution or some suggestion for that? Please help me right
> > now and check my source code, It's very important for me.
> >
> > Thank you so much for your consideration.
> >
> > Dzung Vu Anh.
> >
> > NGN LAB - Computer Engineering
> > AnDong National University - Andong si - South Korea
> > Tel: +82 54 -820 -7944
> > Mobile: 010-6427-1983
> >
> >
> > ________________________________
> > Hotmail: Powerful Free email with security by Microsoft. Get it now.
> > _______________________________________________
> > Tinyos-help mailing list
> > [email protected]
> > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> >
_________________________________________________________________
Hotmail: Powerful Free email with security by Microsoft.
https://signup.live.com/signup.aspx?id=60969_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
