sorry for the previous email (it was in italian but was only a draft that i wanted to save as reminder but i've sent it indeed.)
yesterday i've started dig into the collection module and i've seen exactly what you told me after a while, in your answer. sadly, my 2 cluster need to communicate, through another collection. so i'm thinking to build a generic collection module that use AM ID as parameter. so i can build different tree... it will be faisible or is there something under this module that i'm missing that can be an obstacle? On Friday 01 August 2008 18:12:17 Omprakash Gnawali wrote: > On Fri, Aug 1, 2008 at 1:06 AM, De-MonHell <[EMAIL PROTECTED]> wrote: > > yeah, i made a typo in my question (more than one, i see), but you've > > right understood however. > > > > now i have another question: doing as you suggest to me, it's better to > > work on a modified version of the already existing CollectionC module or > > it's better to take the basic components and write/wire a new component > > from scratch. > > > > anyway, that's a bad news for me, because i've based a more than a month > > work for my thesis on this idea (different-id ==> different roots). > > I don't blame the wiki for this, because maybe it's only my bad english > > or my poor experience with tinyos (this is my real first work with it), > > but i think some more examples, maybe with some schemas showing the tree > > build up in a scenario like mine, will be useful for future newbie. > > If the two clusters don't need to communicate with each other, you can > compile one cluster with one AM ID and another cluster with a > different AM ID. The AM ID is specified in CtpP.nc. > > We will improve the documentation based on user feedback. > > - om_p
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
