The hardware is fairly deterministic: After issuing the STXON strobe the SFD will be transmitted with a constant delay. It's more efficient to take a timestamp when issuing STXON and adjust it with a constant TX_SFD_DELAY than servicing an SFD interrupt.
Janos On Mon, Dec 3, 2012 at 4:10 PM, Xiaohui Liu <xiao...@wayne.edu> wrote: > Hi, > > Thanks for clarifying the reception timestamping. > > Why is *TX_SFD_DELAY* accounted for during transmission, but not during > reception? Isn't *sfdTime* the time SFD byte has been transmitted so > there is no need to add *TX_SFD_DELAY*? > * // adjust time32 with the time elapsed since the SFD event* > * time -= sfdTime;* > * time32 -= time;* > * > * > * // adjust for delay between the STXON strobe and the transmission of > the SFD* > * time32 += TX_SFD_DELAY;* > * > * > * call PacketTimeStamp.set(msg, time32);* > > -Xiaohui > > On Mon, Dec 3, 2012 at 1:45 PM, Janos Sallai > <sal...@isis.vanderbilt.edu>wrote: > >> FALSE > > > > > -- > -Xiaohui Liu > TelosB > TinyOS 2.1.2 > www.cs.wayne.edu/xliu/ > >
_______________________________________________ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
