|
Hello everybody,
I’ve tested the FTSP Protocol into my MicaZ Motes. After I used PrintDiagMsgs and first, it starts printing the messages: NodeId | SeqPolling | GlobalTime | LocalTime | Skew | Synched? | Rootid | Seq | Msgstored 2 1 0 0 0.0 0 65536 0 0 3 1 0 0 0.0 0 65536 0 0 4 1 0 0 0.0 0 65536 0 0 2 3 0 0 0.0 0 65536 0 0 3 3 0 0 0.0 0 65536 0 0 4 3 0 0 0.0 0 65536 0 0 2 6 0 0 0.0 0 65536 0 0 3 6 0 0 0.0 0 65536 0 0 4 6 0 0 0.0 0 65536 0 0 2 9 0 0 0.0 0 65536 0 0 3 9 0 0 0.0 0 65536 0 0 4 9 0 0 0.0 0 65536 0 0 … And After 2 minutes, the regression lines are built and it became synchronised, I obtained: 2 243 0 0 0.0 1 4 1 1 3 243 0 0 0.0 1 4 1 2 4 243 0 0 0.0 1 4 1 1 2 245 0 0 0.0 1 4 2 0 3 245 0 0 0.0 1 4 1 1 4 245 0 0 0.0 1 4 1 2 ……. So it's strange because my LocalTime = GlobalTime = 0000 and motes seems perfectly synchronised (the motes are able to obtain the SeqPolling and “synched?” bit = 1) So, I’m searching into the program files why the values of LocalTime from receiver Motes are not displayed and don’t change… (GlobalTime = LocalTime)?
Somebody have any idea about the no value of LocalTime???
Perhaps Problem using interface TimeStamp when call the function ( call TimeStamping.getStamp() ) in the timesyncdebuggerm.nc file? or incompatibility with MicaZMotes??
Somebody have a Vu directory with the good TimeStamp interface or TestTimeSync Application tested on MicaZ?
Thanks for your reply and your helps
Sincerely
Matt |
_______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
