Re: [Tinyos-help] RF230 HW ACK: Driver uses undefined state transition RX_AACK_ON -> TX_ARET_ON?
I have seen many silicon bugs (both in the RF230 and SI4432) and bad documentation. Miklos On Wed, Mar 21, 2012 at 5:45 PM, Markus Jung wrote: > Hi Miklos, > > thanks for pointing this out. I did not simulate errata and ignored them > therefore - Until now. > I will have to think about how i can handle this very special behaviour > in my simulation. Silicon bugs suck. > > Regards, > Markus > > Am 21.03.2012 23:28, schrieb Miklos Maroti: >> Hi Markus, >> >> On page 89 of the datasheet there is a workaround that shows that you >> can switch between TRX_CMD=TX_START the to TRX_CMD=RX_ON and then to >> TRX_CMD=TX_ARET_ON. So even in the manual they use this (at lease in >> one of the published workarounds of an errata). I do not know how >> slower the "proper" way would be. Yes, this might be "undocumented", >> from all info I saw RX_AACK_ON is pretty much the same as RX_ON and >> TX_ARET_ON is pretty much the same as PLL_ON, and between RX_ON and >> PLL_ON you can switch, so this was a natural port of that behavior and >> it worked. If it makes you more confortable, I can happy to add a >> comment there :) >> >> Miklos >> >> On Wed, Mar 21, 2012 at 5:11 PM, Markus Jung >> wrote: >>> Hello, >>> >>> hardware-acknowledgements have been reported to work on real devices >>> (AFAIK), but while trying to simulate a TOS application using HWACK with >>> LPL, i stumbled upon following behaviour: >>> Phase A: The driver puts the radio into RX_AACK_ON mode. All is fine >>> until >>> Phase B: A transmission gets started. The driver issues a direct state >>> transition from RX_AACK_ON to TX_ARET_ON, which is not defined either by >>> the datasheet or the software programming manual. It is quite >>> interesting to observe real device accepting this (undocumented) state >>> transition. >>> >>> This behaviour has been observed in simulation protocols and can be >>> confirmed by the code in RF230DriverHwAckP (RadioSend.send). >>> >>> However: AFAIK, there is no official source which mentions a transition >>> RX_AACK_ON<->TX_ARET_ON. The only documented way is to use PLL_ON (or, >>> not recommended according to Atmels software programming manual, >>> TRX_OFF) as a intermediate-state. >>> For stability and compatibility reasons, the driver should not use >>> undocumented state transitions. >>> >>> Regards, >>> Markus >>> ___ >>> 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 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] RF230 HW ACK: Driver uses undefined state transition RX_AACK_ON -> TX_ARET_ON?
Hi Miklos, thanks for pointing this out. I did not simulate errata and ignored them therefore - Until now. I will have to think about how i can handle this very special behaviour in my simulation. Silicon bugs suck. Regards, Markus Am 21.03.2012 23:28, schrieb Miklos Maroti: > Hi Markus, > > On page 89 of the datasheet there is a workaround that shows that you > can switch between TRX_CMD=TX_START the to TRX_CMD=RX_ON and then to > TRX_CMD=TX_ARET_ON. So even in the manual they use this (at lease in > one of the published workarounds of an errata). I do not know how > slower the "proper" way would be. Yes, this might be "undocumented", > from all info I saw RX_AACK_ON is pretty much the same as RX_ON and > TX_ARET_ON is pretty much the same as PLL_ON, and between RX_ON and > PLL_ON you can switch, so this was a natural port of that behavior and > it worked. If it makes you more confortable, I can happy to add a > comment there :) > > Miklos > > On Wed, Mar 21, 2012 at 5:11 PM, Markus Jung > wrote: >> Hello, >> >> hardware-acknowledgements have been reported to work on real devices >> (AFAIK), but while trying to simulate a TOS application using HWACK with >> LPL, i stumbled upon following behaviour: >> Phase A: The driver puts the radio into RX_AACK_ON mode. All is fine >> until >> Phase B: A transmission gets started. The driver issues a direct state >> transition from RX_AACK_ON to TX_ARET_ON, which is not defined either by >> the datasheet or the software programming manual. It is quite >> interesting to observe real device accepting this (undocumented) state >> transition. >> >> This behaviour has been observed in simulation protocols and can be >> confirmed by the code in RF230DriverHwAckP (RadioSend.send). >> >> However: AFAIK, there is no official source which mentions a transition >> RX_AACK_ON<->TX_ARET_ON. The only documented way is to use PLL_ON (or, >> not recommended according to Atmels software programming manual, >> TRX_OFF) as a intermediate-state. >> For stability and compatibility reasons, the driver should not use >> undocumented state transitions. >> >> Regards, >> Markus >> ___ >> 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
Re: [Tinyos-help] RF230 HW ACK: Driver uses undefined state transition RX_AACK_ON -> TX_ARET_ON?
Hi Markus, On page 89 of the datasheet there is a workaround that shows that you can switch between TRX_CMD=TX_START the to TRX_CMD=RX_ON and then to TRX_CMD=TX_ARET_ON. So even in the manual they use this (at lease in one of the published workarounds of an errata). I do not know how slower the "proper" way would be. Yes, this might be "undocumented", from all info I saw RX_AACK_ON is pretty much the same as RX_ON and TX_ARET_ON is pretty much the same as PLL_ON, and between RX_ON and PLL_ON you can switch, so this was a natural port of that behavior and it worked. If it makes you more confortable, I can happy to add a comment there :) Miklos On Wed, Mar 21, 2012 at 5:11 PM, Markus Jung wrote: > Hello, > > hardware-acknowledgements have been reported to work on real devices > (AFAIK), but while trying to simulate a TOS application using HWACK with > LPL, i stumbled upon following behaviour: > Phase A: The driver puts the radio into RX_AACK_ON mode. All is fine > until > Phase B: A transmission gets started. The driver issues a direct state > transition from RX_AACK_ON to TX_ARET_ON, which is not defined either by > the datasheet or the software programming manual. It is quite > interesting to observe real device accepting this (undocumented) state > transition. > > This behaviour has been observed in simulation protocols and can be > confirmed by the code in RF230DriverHwAckP (RadioSend.send). > > However: AFAIK, there is no official source which mentions a transition > RX_AACK_ON<->TX_ARET_ON. The only documented way is to use PLL_ON (or, > not recommended according to Atmels software programming manual, > TRX_OFF) as a intermediate-state. > For stability and compatibility reasons, the driver should not use > undocumented state transitions. > > Regards, > Markus > ___ > 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
[Tinyos-help] RF230 HW ACK: Driver uses undefined state transition RX_AACK_ON -> TX_ARET_ON?
Hello, hardware-acknowledgements have been reported to work on real devices (AFAIK), but while trying to simulate a TOS application using HWACK with LPL, i stumbled upon following behaviour: Phase A: The driver puts the radio into RX_AACK_ON mode. All is fine until Phase B: A transmission gets started. The driver issues a direct state transition from RX_AACK_ON to TX_ARET_ON, which is not defined either by the datasheet or the software programming manual. It is quite interesting to observe real device accepting this (undocumented) state transition. This behaviour has been observed in simulation protocols and can be confirmed by the code in RF230DriverHwAckP (RadioSend.send). However: AFAIK, there is no official source which mentions a transition RX_AACK_ON<->TX_ARET_ON. The only documented way is to use PLL_ON (or, not recommended according to Atmels software programming manual, TRX_OFF) as a intermediate-state. For stability and compatibility reasons, the driver should not use undocumented state transitions. Regards, Markus ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Vanderbilt AcousticLocalization java.lang.ClassNotFoundException
To get to the actual TOS release for the nescc builds under T1, I think what you need is something like this in your environment (on Windows): # Set main pointers used by TOS build system to find files # TOSROOT is for external programs, TOSDIR for makefiles TV="tinyos-1.x" ## I use this to select specific TOS versions export TOSROOT=C:/cygwin/opt/$TV export TOSDIR=/opt/$TV/tos I believe TOSDIR gets transliterated into a "%T" variable in the Makefiles, i.e.: /opt/tinyos-1.x/tos This is also required, but you probably already have it set: export MAKERULES=/opt/$TV/tools/make/Makerules Then, if there are extra bits of added TOS goodness in other directories you can include them in the Makefile with PFLAGS (this is probably what the VUTOS variable is trying to do) like this: EXTRATOS=../tos ## or some %T/../contrib... directory PFLAGS += -I$(EXTRATOS)/platform/mica2 \ -I$(EXTRATOS)/interfaces \ -I$(EXTRATOS)/system By figuring out where the files that the compiler is whining about actually are you should be able to add the right directories. Another option is to put it all together in your main tos and apps directory structure, so you don't need the contrib searching... For the Java problem you need to add the jar or root directory tree that contains the classes of interest to your CLASSPATH, something like this: export CLASSPATH="$CLASSPATH;C:/whevever/your/files/are; Search for CLASSPATH for more info than you will ever need... MS giacomo_gioacch...@libero.it wrote: > Dear all, > I am using the AcousticLocalization app from the Vanderbilt University. > I am trying to run the java app AcousticLocalization as is described in the > README.txt file in: > tools/java/net/tinyos/acousticlocalization/ > I get stuck at the point LAUNCHING THE ACOUSTICLOCALIZATION MODULE. In the > AppLoader I enter the following command: > net.tinyos.acousticlocalization.AcousticLocalization > but I got the following error: > Could not Found module: java.lang.ClassNotFoundException: net.tinyos. > acousticlocalization.AcousticLocalization > Any ideas on how to fix the problem? > I'm quite newbbie in this subject, any help is greatly appreciated!! > Thanks in advance, > Giacomo > >> Messaggio originale >> Da: sal...@isis.vanderbilt.edu >> Data: 21/03/2012 17.39 >> A: "giacomo_gioacch...@libero.it" >> Ogg: Re: Re: [Tinyos-help] Vanderbilt AcousticLocalization >> >> This code is for tinyos-1.x, so that should not be the issue. >> >> Janos >> >> On Wed, Mar 21, 2012 at 10:30 AM, giacomo_gioacch...@libero.it >> wrote: >>> Hi Janos, >>> thanks for your answer. Actually the mote I am using is exactly the mica2 > and >>> I compile with the command make mica2. I am using TinyOS-1.x, could that be > the >>> problem? >>> Thanks, >>> Giacomo >>> Messaggio originale Da: sal...@isis.vanderbilt.edu Data: 21/03/2012 14.57 A: "giacomo_gioacch...@libero.it" Cc: "tinyos forum" Ogg: Re: [Tinyos-help] Vanderbilt AcousticLocalization Giacomo: The code in contrib/vu/apps/AcousticLocalization does compile for mica2. If you need to get it work on another platform, you'll have to figure how the makefiles need to be adapted to include the required interfaces. Please note that this code was written 10 years ago, that is, it predates micaz and iris. Janos On Wed, Mar 21, 2012 at 8:28 AM, giacomo_gioacch...@libero.it wrote: > Dear all, > I downloaded from sourceforge all the minitasks\02\vu\ CVS folder to try >>> the > AcousticLocalization application of ISIS Vanderbilt University. I have > put >>> the > folder vu in : > cygwin\opt\tinyos-1.x\contrib\vu\ > and I have set the environment variable VUTOS as explained in the ReadMe >>> file > with the command: > export VUTOS=/opt/tinyos-1.x/contrib/vu/tos > but when I try to compile the applications in the apps folder the system > is > unable to search interfaces and components in the correct folders. > Has someone else faced the same problem? > Hope to see some answers, > thanks in advance > Giacomo > > > ___ > 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 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Vanderbilt AcousticLocalization java.lang.ClassNotFoundException
Dear all, I am using the AcousticLocalization app from the Vanderbilt University. I am trying to run the java app AcousticLocalization as is described in the README.txt file in: tools/java/net/tinyos/acousticlocalization/ I get stuck at the point LAUNCHING THE ACOUSTICLOCALIZATION MODULE. In the AppLoader I enter the following command: net.tinyos.acousticlocalization.AcousticLocalization but I got the following error: Could not Found module: java.lang.ClassNotFoundException: net.tinyos. acousticlocalization.AcousticLocalization Any ideas on how to fix the problem? I'm quite newbbie in this subject, any help is greatly appreciated!! Thanks in advance, Giacomo >Messaggio originale >Da: sal...@isis.vanderbilt.edu >Data: 21/03/2012 17.39 >A: "giacomo_gioacch...@libero.it" >Ogg: Re: Re: [Tinyos-help] Vanderbilt AcousticLocalization > >This code is for tinyos-1.x, so that should not be the issue. > >Janos > >On Wed, Mar 21, 2012 at 10:30 AM, giacomo_gioacch...@libero.it > wrote: >> Hi Janos, >> thanks for your answer. Actually the mote I am using is exactly the mica2 and >> I compile with the command make mica2. I am using TinyOS-1.x, could that be the >> problem? >> Thanks, >> Giacomo >> >>>Messaggio originale >>>Da: sal...@isis.vanderbilt.edu >>>Data: 21/03/2012 14.57 >>>A: "giacomo_gioacch...@libero.it" >>>Cc: "tinyos forum" >>>Ogg: Re: [Tinyos-help] Vanderbilt AcousticLocalization >>> >>>Giacomo: >>> >>>The code in contrib/vu/apps/AcousticLocalization does compile for >>>mica2. If you need to get it work on another platform, you'll have to >>>figure how the makefiles need to be adapted to include the required >>>interfaces. >>> >>>Please note that this code was written 10 years ago, that is, it >>>predates micaz and iris. >>> >>>Janos >>> >>>On Wed, Mar 21, 2012 at 8:28 AM, giacomo_gioacch...@libero.it >>> wrote: Dear all, I downloaded from sourceforge all the minitasks\02\vu\ CVS folder to try >> the AcousticLocalization application of ISIS Vanderbilt University. I have put >> the folder vu in : cygwin\opt\tinyos-1.x\contrib\vu\ and I have set the environment variable VUTOS as explained in the ReadMe >> file with the command: export VUTOS=/opt/tinyos-1.x/contrib/vu/tos but when I try to compile the applications in the apps folder the system is unable to search interfaces and components in the correct folders. Has someone else faced the same problem? Hope to see some answers, thanks in advance Giacomo ___ 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
[Tinyos-help] CTP_OPT_ECN in CTP
Hi, I am a bit confuse. I am not really clear how a call to CtpInfo.setNeighborCongested(from, congested) can set the neighbor as congested (in the BeaconReceive.receive() event in CtpRoutingEngineP)?, because I found that a call to CtpRoutingPacket.getOption(msg, CTP_OPT_ECN) returns FALSE, therefore setting the 'congested' variable to FALSE as well. I guess, this will not set the neighbor 'from' as congested? Thanks Yusnaidi ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Vanderbilt AcousticLocalization
Giacomo: The code in contrib/vu/apps/AcousticLocalization does compile for mica2. If you need to get it work on another platform, you'll have to figure how the makefiles need to be adapted to include the required interfaces. Please note that this code was written 10 years ago, that is, it predates micaz and iris. Janos On Wed, Mar 21, 2012 at 8:28 AM, giacomo_gioacch...@libero.it wrote: > Dear all, > I downloaded from sourceforge all the minitasks\02\vu\ CVS folder to try the > AcousticLocalization application of ISIS Vanderbilt University. I have put the > folder vu in : > cygwin\opt\tinyos-1.x\contrib\vu\ > and I have set the environment variable VUTOS as explained in the ReadMe file > with the command: > export VUTOS=/opt/tinyos-1.x/contrib/vu/tos > but when I try to compile the applications in the apps folder the system is > unable to search interfaces and components in the correct folders. > Has someone else faced the same problem? > Hope to see some answers, > thanks in advance > Giacomo > > > ___ > 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
[Tinyos-help] Vanderbilt AcousticLocalization
Dear all, I downloaded from sourceforge all the minitasks\02\vu\ CVS folder to try the AcousticLocalization application of ISIS Vanderbilt University. I have put the folder vu in : cygwin\opt\tinyos-1.x\contrib\vu\ and I have set the environment variable VUTOS as explained in the ReadMe file with the command: export VUTOS=/opt/tinyos-1.x/contrib/vu/tos but when I try to compile the applications in the apps folder the system is unable to search interfaces and components in the correct folders. Has someone else faced the same problem? Hope to see some answers, thanks in advance Giacomo ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Error in integrating ADXL345 accelerometer with TelosB
No clue, I don't know what modifications you have made... around those lines there should be the components and wirings of the interruptions, did you define it? (see tos/platforms/z1/chips/adxl345) A more updated test example application for the ADXL345 accelerometer is already merged in TinyOS trunk under: apps/tests/z1/Accelerometer Hope it helps, --Antonio. On Wed, 2012-03-21 at 17:33 +0530, Prasanth P wrote: > Am trying to interface Telosb mote with ADXL345 accelerometer sensor. > Am using the sample program available from > http://zolertia.sourceforge.net/wiki/index.php/Mainpage:TOS_basic#Move_your_body.2C_sense_the_accelerometer > > > Have solved some initial errors while compiling. But not able to solve > this compilation error. > > $ make telosb > mkdir -p build/telosb > compiling AccelerometerAppC to a telosb binary > ncc -o build/telosb/main.exe -Os -O -mdisable-hwmul > -fnesc-separator=__ -Wall - > Wshadow -Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c > -board= -DDEFI > NED_TOS_AM_GROUP=0x22 -I/opt/tinyos-2.x/tos/lib/printf > -I/opt/tinyos-2.x/tos/chi > ps/adxl345 -DIDENT_APPNAME=\"AccelerometerAp\" -DIDENT_USERNAME= > \"Prasanth\" -DI > DENT_HOSTNAME=\"cdac-2b01fa\" -DIDENT_USERHASH=0x7de52accL > -DIDENT_TIMESTAMP > =0x4f69bc49L -DIDENT_UIDHASH=0x8b2c4d48L AccelerometerAppC.nc -lm > In file included from AccelerometerAppC.nc:17: > In component `ADXL345C': > /opt/tinyos-2.x/tos/chips/adxl345/ADXL345C.nc:71: syntax error before > `0x20' > /opt/tinyos-2.x/tos/chips/adxl345/ADXL345C.nc:72: syntax error before > `0x20' > /opt/tinyos-2.x/tos/chips/adxl345/ADXL345C.nc:73: syntax error before > `0x20' > /opt/tinyos-2.x/tos/chips/adxl345/ADXL345C.nc:74: syntax error before > `0x20' > make: *** [exe0] Error 1 > > > Am getting some "syntax error before `0x20' ADXL345C.nc" file. But > that file itself doesn't contain such a line. > > Have attached the ADXL345C.nc file. > > Anybody having some idea regarding this, please respond. All kinds of > suggestions are welcome. > > Thanks in Advance. > > > > -- > Regards > Prasanth.P > > ___ > 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
[Tinyos-help] Error in integrating ADXL345 accelerometer with TelosB
Am trying to interface Telosb mote with ADXL345 accelerometer sensor. Am using the sample program available from http://zolertia.sourceforge.net/wiki/index.php/Mainpage:TOS_basic#Move_your_body.2C_sense_the_accelerometer Have solved some initial errors while compiling. But not able to solve this compilation error. $ make telosb mkdir -p build/telosb compiling AccelerometerAppC to a telosb binary ncc -o build/telosb/main.exe -Os -O -mdisable-hwmul -fnesc-separator=__ -Wall - Wshadow -Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c -board= -DDEFI NED_TOS_AM_GROUP=0x22 -I/opt/tinyos-2.x/tos/lib/printf -I/opt/tinyos-2.x/tos/chi ps/adxl345 -DIDENT_APPNAME=\"AccelerometerAp\" -DIDENT_USERNAME=\"Prasanth\" -DI DENT_HOSTNAME=\"cdac-2b01fa\" -DIDENT_USERHASH=0x7de52accL -DIDENT_TIMESTAMP =0x4f69bc49L -DIDENT_UIDHASH=0x8b2c4d48L AccelerometerAppC.nc -lm In file included from AccelerometerAppC.nc:17: In component `ADXL345C': /opt/tinyos-2.x/tos/chips/adxl345/ADXL345C.nc:71: syntax error before `0x20' /opt/tinyos-2.x/tos/chips/adxl345/ADXL345C.nc:72: syntax error before `0x20' /opt/tinyos-2.x/tos/chips/adxl345/ADXL345C.nc:73: syntax error before `0x20' /opt/tinyos-2.x/tos/chips/adxl345/ADXL345C.nc:74: syntax error before `0x20' make: *** [exe0] Error 1 Am getting some "syntax error before `0x20' ADXL345C.nc" file. But that file itself doesn't contain such a line. Have attached the ADXL345C.nc file. Anybody having some idea regarding this, please respond. All kinds of suggestions are welcome. Thanks in Advance. -- Regards Prasanth.P ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Problems with how to send preamble and enable the software acknowlegements
hi I'm a student and I work on wns, I'm implementing a Mac protocol and I have some unclear concepts, help plz! 1)What is CC2420_TIME_ACK_TURNAROUND? and what is the difference between it and CC2420_ACK_WAIT_DELAY? 2)In my protocol I want to use the preamble, I read in the cc2420 datasheet that there is a physical preamble that its length can't be greater than 4 bytes. But how can I send mac preamble that its length is greater than 4 bytes? 3) how can I enable the software ack and in whitch component are the acknolegements generated ? wait for answers.thx in advance. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] LocalTime on TelosB skips back
I've been collecting data with TelosB motes for the past few days, and when I started to analyse the data, I found some weird points where calling LocalTime.get() would return values about ~1 earlier. Has anybody experienced this before, and is this an expected behaviour? I've been relying on it being strictly increasing (wrapping around at 32-bit). Thanks. Alex Koay ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
