Hope someone can help me soon! I seem to have problems with TimeSyncM.nc when I try to compile an application in low power mode. During the compile I get the following warnings:
/opt/Moteworks/tos/radio/cc1000lp/bin/TimerM.nc:213:warning: 'RadioTimer.fired' called asynchronously from 'Clock.fire' /opt/Moteworks/tos/lib/TimeSync/TimeSyncM.nc:138:warning: 'Timer.ticksLeft' called asynchronously from 'Time.getLow32' /opt/Moteworks/tos/lib/TimeSync/TimeSyncM.nc:119:warning: 'Timer.ticksLeft' called asynchronously from 'Time.get' /opt/Moteworks/tos/platform/mica2/ADCREFM.nc:278:warning: 'Timer.stop' called asynchronously from 'ADCControl.autoCalibrate' /opt/Moteworks/tos/platform/mica2/ADCREFM.nc:281:warning: 'Timer.start' called asynchronously from 'ADCControl.autoCalibrate' /opt/Moteworks/tos/lib/TimeSync/TimeSyncM.nc:143:warning: non-atomic access to shared variable 'fill_pending': /opt/Moteworks/tos/lib/TimeSync/TimeSyncM.nc:191:warning: non-atomic write /opt/Moteworks/tos/lib/TimeSync/TimeSyncM.nc:70:warning: non-atomic access to shared variable 'skiew': /opt/Moteworks/tos/lib/TimeSync/TimeSyncM.nc:207:warning: non-atomic read /opt/Moteworks/tos/lib/TimeSync/TimeSyncM.nc:208:warning: non-atomic read /opt/Moteworks/tos/lib/TimeSync/TimeSyncM.nc:72:warning: non-atomic access to shared variable 'authority' /opt/Moteworks/tos/lib/TimeSync/TimeSyncM.nc:296:warning: non-atomic read /opt/Moteworks/tos/lib/TimeSync/TimeSyncM.nc:297:warning: non-atomic read /opt/Moteworks/tos/lib/TimeSync/TimeSyncM.nc:303:warning: non-atomic write C:\Crossbow\cygwin\opt\Moteworks\tos\lib\TimeSync\TimeSyncM.nc: In function 'TimeSyncM$Time$getLow32': C:\Crossbow\cygwin\opt\Moteworks\tos\lib\TimeSync\TimeSyncM.nc:133:warning: unused variable 't' However the compiler still completes and I can programme a mote with the image, but when running the motes they do not seem to work as desired. I have modified XMeshCountToLedsandRfm so that it uses upstream end-to-end acknowledgement, and if the source does not receive an acknowledgement from the base within a given period of time it retransmits the message. This application works fine in High Power mode, but when I load the compiled Low Power image from above; using XSniffer I can see acknowledgements being returned to the source within the designated time period, but then when the period expires the source still retransmits the message. I can only assume this is because the source is not receiving the acknowledgement back from the base (or its intermediate node when a mesh is formed) due to the nodes not being correctly time synchronized. Therefore I was wondering if there were any newer versions of TimeSync (mine was written in 2004) that correct this error, or if anyone can give me any advice on how to adjust the code to correct it myself. Thank You in Advance, Alan Wade _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
