Hi Kim,Thanks for your suggestion. I was going through the MultiHopRouteM.nc and MultiHopLEPSM.nc modules for the Surge application. I followed your previous post at http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2004-November/006625.html and made the following changes:I commented the entire chooseParent() function and also the chooseParent() call in TimerTask() in MultiHopLEPSM.I added this switch statement in StdControl.init():switch (TOS_LOCAL_ADDRESS) {
case 0: // Parent of mote 0 is the UART
gpCurrentParent->id = TOS_UART_ADDR;
break;
case 1: // Parent of mote 1 is mote 0
gpCurrentParent->id = 0;
break;
case 2: // Parent of mote 2 is mote 1
gpCurrentParent->id = 1;
break;
case 3: // Parent of mote 3 is mote 1
gpCurrentParent->id = 1;
break;
case 4: // Parent of mote 4 is mote 2
gpCurrentParent->id = 2;
break;
case 5: // Parent of mote 5 is mote 3
gpCurrentParent->id = 3;
break;
case 6: // Par! ent of mote 6 is mote 4
gpCurrentParent->id = 4;
break;
}I did a make pc in the Surge directory and it went through fine. The TinyViz GUI started and it showed all the nodes, BUT then suddenly it shut down on its own without running for even a second and gave me this error:tossim-serial @ localhost died - restarting (java io.EOFException)I dont know why is it not working. You were suggesting to have a TableEntry struct that is the static parent for the nodes. I havent done that, because the id is already a part of the existing struct. But can that be the reason for the error?I was able to change the TestTinyViz application and make nodes send their data to specific nodes that I want. But then I realized that I need to have things like receiving the message, re-addressing the message to the receiving mote's parent, resending if it doesn't get acknowledged, etc. like you said. So I will have to work with the MultiHopRouteM.nc and MultiHopLEPSM.nc modules.Can you please advice me on how should I go about solving this issue. Thanks a lot for your time and help.Regards,Yogesh.
Kim Nico <[EMAIL PROTECTED]> wrote:Yogesh,
I can't think off the top of my head how to give static routes without
using some kind of "multihop" algorithm that yields them. The static
route in particular implies a multihop usage --- that packets sent
from the farthest away will be intended to be received eventually at
mote 0. In essence, it would be a good abstraction to write a
"multihop" algorithm that just specifies a table of fixed parents.
The other stuff the algorithm does, you will probably also want to do,
like receiving the message, re-addressing the message to the receiving
mote's parent, resending if it doesn't get acknowledged, etc. This is
why I suggest modifying an existing algorithm. if you are concerned
about having too much in the multihop header, you probably don't need
the hopcount and could modify the data structure accordingly.
Hope this helps,
-Kim.
On Tue, Dec 21, 2004 at 04:20:29PM -0800, Yogesh Iyer wrote:
> Hi Kim,
>
> I saw some of your replies on implementing a fixed route in TOSSIM and hope you would be able to help me. I am new to TOSSIM, so your suggestions will really help me.
>
> I read your replies on: http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2004-November/006625.html
>
> Can you suggest how do I write my own module where I specify all the static routes, instead of using any other module like MultiHopLEPSM or MultiHopRouteM.
>
> Thanks,
> Yogesh.
>
>
> ---------------------------------
> Do you Yahoo!?
> Send holiday email and support a worthy cause. Do good.
Do you Yahoo!?
All your favorites on one personal page � Try My Yahoo!
Do you Yahoo!?
All your favorites on one personal page � Try My Yahoo!
_______________________________________________ Tinyos-users mailing list [email protected] http://mail.Millennium.Berkeley.EDU/mailman/listinfo/tinyos-users
