Hi Michael, I think you are still not getting the problem I was having; I do really appreciate your help and responses. I am re-posting just to make the situation clear for future readers.
I was not trying to broadcast the packet I was sending over the serial port i.e. to use the mote as a relay. I simply wanted to send the packet to that mote on that serial port and for it to react e.g. flash some leds. The best analogy I can give is as follows: You have a host PC, A,with IP address 192.168.0.2/24 from which you want to send a packet to host B with address 192.168.0.3/24. What I believe I was doing, by sending to 0x7e (UART), was sending to localhost or 127.0.0.1 on host A; the correct thing to do is to send to either 192.168.0.3 (host B) or 192.168.0.255 i.e broadcast to the local network, in which case host B would process the packet. Given the port is connected to only one mote, it is safe enough to just use the broadcast address, in which the mote will process the packet. Clearly packets that come off the radio or the serial port obviously go through the same processing. Thanks again. -- Warm regards, Darren Bishop, MSc, BSc (Hons), MBCS On Sunday 30 July 2006 20:38, Michael Schippling wrote: > OK, if I understand the issue, you were sending a message from the host > to a (or all) mote and you used the UART addr as the destination in the > message, which makes a certain kind (but not the TOS kind of) sense. > That message was never sent, because it was addressed to the UART and > didn't need to be forwarded over the radio. The addressing model is > not entirely symmetrical in this case, and I think this is common to > all TOS platforms. There is no way to specify a radio address from the > host if you have to use that field to get the message over the serial > line to the base station. > > Sorry for my mis-reading of your original help request... > Glad you figured this one out and are now ready for some new sleep loss. > MS > > Darren Bishop wrote: > > Hello Michael, Lei, All, > > > > I have solved the problem. I had been doing everything write except for > > the address I was specifying. I had read in a Tinyos-help thread started > > by Lei Tang (post by Julia) that you had to specify the UART address as > > destination. This does not work for me (maybe due to telosb platform) and > > it is the one reason I have been loosing sleep for 2 weeks; you can > > specify either the broadcast address or the motes address. I have tested > > this both in C going via serial forwarder and in my direct python > > application. > > > > Lei: I could not tell if you ever solved your problem: like the advice I > > was getting from my supervisor, you may have moved on to a different > > task, to come back to this later. > > In my experience the crc does matter. I am using GenericComm and my > > component is not signalled if I deliberatly mangle the crc pc-side before > > sending. Look at Crc.java or serialsource.c for implementations of the > > crc algorithm. You maybe using a component/interface too low-level to > > benefit from the crc i.e. the check fails but you're working at a level > > where processing occurs regardless. Use GenericComm. _______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
