Thanks Michael, But the MoteWorks IDE that i'm using doesn not have "raw" UART support. So, i'm stuck with using a single receive function for both. Any suggestions for continuing in the same IDE, or do i have to shift to some thing else??
Always Yours Tejovanth Tj n Spook On Thu, Jun 9, 2011 at 11:55 PM, Michael Schippling <sc...@santafe.edu>wrote: > The MultihopMsg struct contains: > uint16_t sourceaddr; > uint16_t originaddr; > which you may be able to use to determine where the > message came from. > > But you may be using the "raw" uart code to communicate > between a micaz and some other device. Then you won't be > using AM or MultiHop messages, so the interfaces will be > different anyway. > > MS > > TJ wrote: > >> I am using MicaZ with MoteWorks on Windows XP. >> >> I am trying to implement a network bridge where the mote has to >> communicate over UART to a attached device (a micro controller running some >> algorithms) and also communicate with other similar mote-device setups. >> >> By my understanding, there are two send interfaces which i can use for the >> wireless and UART channels respectively. But there is only one receive >> interface that has to handle both. >> >> My doubt is this - how do i differentiate where the packet is coming from >> if this is the case?? As MoteWorks seems very restricted in terms of the >> library files it contains. >> >> Always Yours >> Tejovanth >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Tinyos-help mailing list >> Tinyos-help@millennium.berkeley.edu >> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >> >
_______________________________________________ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
