[Tinyos-help] Problems with MicaHWVerify
I am having problems with MicaHWVerify. I program it on my mote (based on Mica2) and nothing happens. The LEDs are supposed to start counting once it has retrieved the ID from the serial ID chip. I assumed that the problem was something to do with this. To test it I put a Leds.redOn() in the StdControl.start() at the very start, before it calls HardwareId.read(). Surprisingly, nothing happened. So it seems like StdControl.start() is never getting called. I also placed Leds.redOn() in StdControl.init() and the LED turned on. So that's very strange. I have tried other programs like IntToLeds and ReverseUART and they work fine. I have tried two different PCBs and have tried programming with MIB510 (uisp) or the JTAG (AVR Studio). Is there any other (better?) way to test the serial ID and Flash? Any ideas? Thanks. Simon ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Modifying Oscilloscope
I tried swaping wherever sensor was with ADCC in the
Oscilloscope config file as seen below:
configuration Oscilloscope { }
implementation
{
components Main, OscilloscopeM
, TimerC
, LedsC
, DemoSensorC as Sensor
, ADCC
, GenericComm as Comm;
Main.StdControl -> OscilloscopeM;
Main.StdControl -> TimerC;
OscilloscopeM.Timer ->
TimerC.Timer[unique("Timer")];
OscilloscopeM.Leds -> LedsC;
OscilloscopeM.ADCControl -> ADCC.ADC[11];
OscilloscopeM.ADC -> ADCC.ADC[11];
OscilloscopeM.CommControl -> Comm;
OscilloscopeM.ResetCounterMsg ->
Comm.ReceiveMsg[AM_OSCOPERESETMSG];
OscilloscopeM.DataMsg -> Comm.SendMsg[AM_OSCOPEMSG];
}
but it gets a compile error when I try to use the
ADC11 and even if I take out the ".ADC[11]" it still
gives me errors. I looked at your code and am still a
little fuzzy as to how it works. I just need it to
read a value from the mote using the MDA300.
Thanks in advance,
Steve
--- Michael Schippling <[EMAIL PROTECTED]> wrote:
> You should be able to swap out the Sensor stuff in
> the
> config file and use ADCC instead. See how it's done
> in:
> tos\sensorboards\micasb\PhotoTemp.nc
> If you follow the O'scope silly-Sensor modules all
> the way
> down you get to the real ADCC...
>
> Or look in my code bolus at:
>
> http://www.etantdonnes.com/Motes/robocode.tar.gz
>
> MS
>
>
> Steve the Taiwanese wrote:
> > Hi, I am trying to make a wireless EKG. I want to
> try
> > to use Oscilloscope to graph the data from the ADC
> 11,
> > or ADC0. How can I change it from the photo sensor
> to
> > the ADC?
> >
> > Thanks,
> > Stephen Anderson
> >
> > __
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam
> protection around
> > http://mail.yahoo.com
> > ___
> > Tinyos-help mailing list
> > Tinyos-help@Millennium.Berkeley.EDU
> >
>
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Use SerialForwarder or MoteIF?
Don't know about forward portability, but the basic question boils down to: Do you want your Java code to connect directly to the serial port (meaning always run on the local host that has the programmer attached), or do you want to always have to start SerialForwarder on the local host and be able to connect your program from anywhere on the net (modulo firewalls etal). If your code is always local, use MoteIF or BuildSource. Otherwise you need SF to be your local intermediary. My personal belief system defines SF as an unnecessary and confusing annoyance, but YMMV. MS Conor Todd wrote: Hi. I'm writing a bit of Java code to run on a PC connected to mote network. I'm currently using TinyOS-1.x, but at some point I'm sure I'll move to TinyOS-2.x. For my java code, should I connect to a Serial Forwarder to receive packets, or should I use MoteIF to connect directly? The documentation in MoteIF would make it seem like it's far better than Serial Forwarder, and yet everyone seems to be using Serial Forwarder. Thanks! - Conor ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Problems with GenericComm and PWM
Oh, now you're going to make me work AND explain what I did...oy... First I stole my PWM stuff from Sarah B's cotsbots board code that uses different pins and a somewhat different idea, vis motor direction. I then left the direction pin defs in but never used them, so at least three layers of confusion can ensue...my code is for the mica cards themselves. Second here's a quote from a previous post that might help explain the macros: >> Ian Welch wrote: >> I was wondering where I could find the TOSH function commands. I'm going through the CC1000 modules in hopes to write my own drivers. Was wondering what command like " TOSH_MAKE_CC_CHP_OUT_INPUT() " and " TOSH_SET_CC_PCLK_PIN() " do. I have an idea on what these functions do but would I like to know the details. I'm guessing there is a file locate somewhere that gives all these function. Where I might I find this file. >> >> Thanks, >>Ian >> They are generated by a macro mechanism that run two or three levels deep, so there is basically no hope of finding the actual definition without searching on each _*_ sub-string. Good luck with that... In any case there is one more missing component you haven't stumbled over yet (this is not the real definition, I just pulled it out of a hat as an example): // assign the name "CC_CHP_OUT" to port C, pin 0 TOSH_ASSIGN_PIN( CC_CHP_OUT, C, 0 );// PC0 Then your initial puzzles: // set CC_CHP_OUT pin to Input mode (can also use _OUTPUT) TOSH_MAKE_CC_CHP_OUT_INPUT() // (after using TOSH_MAKE_CC_PCLK_OUTPUT) set pin to high TOSH_SET_CC_PCLK_PIN() // or, e.g., clear to low TOSH_CLR_CC_PCLK_PIN() The TOSers did a pretty good job of keeping the pin names the same as those on the schematic, which are of course slightly different from those in the ATMEGA manual. But once you get over the hump it's not too hard to intuit. MS So basically, from the above you should be able to intuit the TOS mechanism for assigning pins, names, and levels. So you need to make the PortB pins that can do PWM into outputs by diddling the right BITS on DDRB, which is done with the TOSH_MAKE_*_OUTPUT() macro, and do all the other PWM setup. This is done in the init() method of my HPLMotorIIM.nc file, but only so as to do the exact thing I wanted, so your pulse rates may change. Was that enough gobbledegook to get you going? MS BiBe wrote: Hi! Thanks a lot for your answer! With the DDRB register, I set the output pins for PWM. In your code, this is done by: TOSH_MAKE_MOTOR1PWM_OUTPUT(); TOSH_MAKE_MOTOR1DIR_OUTPUT(); TOSH_CLR_MOTOR1PWM_PIN(); TOSH_CLR_MOTOR1DIR_PIN(); Where are those functions defined and how can I use them to get PWM to Port OC1A and OC1B? Can I even use these functions without having the cotsbots-board? Furthermore I found that in a header file: /** after cotsbots motor/hardware.h for PWM output: **/ // it appears that the PWM and DIR appellations are reversed // and also that the pins assigned to PWM (sic) are not available // due to their being used by the radio: // PB1 -- SPI_SCK // PB2 -- SPI_MOSI // so gotta try somethong else TOSH_ASSIGN_PIN(MOTOR1DIR, C, 0); // PC0 TOSH_ASSIGN_PIN(MOTOR1PWM, B, 6); // PB6 TOSH_ASSIGN_PIN(MOTOR2DIR, C, 1); // PC1 TOSH_ASSIGN_PIN(MOTOR2PWM, B, 5); // PB5 So there seems to be problems to use radio and PWM together, because of corporate use of PB registers. Can I use TOSH_ASSIGN_PIN() without cotsbots-board in nesC? I tried to compile and there were no errors. But will it work expectedly or do I have to use any more header files like hardware.h? Thanks a lot, BiBe -Original Message- From: [EMAIL PROTECTED] [mailto:tinyos-help- [EMAIL PROTECTED] On Behalf Of Michael Schippling Sent: Tuesday, July 25, 2006 6:14 AM To: Birger Becker Cc: tinyos-help@Millennium.Berkeley.EDU Subject: Re: [Tinyos-help] Problems with GenericComm and PWM sbi() and cbi() should work fine, as long as you are careful to not touch pins used by the radio. I wouldn't go writing whole registers with outp() if there is any shared pins. Double check the schematic for the mote you are using to make sure. I have some PWM code in my code bolus: http://www.etantdonnes.com/Motes/robocode.tar.gz I forget what reg DDRB is, but I use the timer/counter pins on the ATMEGA 128 so either I did something right, or you don't need to touch DDRB... MS Birger Becker wrote: Hi! I'm currently programming PWM (pulse width modulation) on an ATMega 128 in a tinyOS-environment. Programming of PWM is ready, but now I wanted to remote control one Mote with the PWM by another, which is connected to a programming board. So I used TOSBASE and SimpleCmd for basic and put my PWM code in the command-process of SimpleCmd. The TOSBase-Mote is then administrated by programming board using UART and it sends commands via RadioCRCPacket to SimpleCommand, which receives them by GenericComm. The remote control works fine, I checked by LE
[Tinyos-help] Cannot run: make micaz sim
Hi,Can someone tell me why I cannot run "make micaz sim" in ubuntu? Thanks.[EMAIL PROTECTED]:/opt/tinyos-2.x/apps/Blink$ make micaz simmkdir -p build/micaz
placing object files in build/micaz writing XML schema to app.xml compiling BlinkAppC to object file sim.oncc -c -shared -fPIC -o build/micaz/sim.o -g -O0 -tossim -fnesc-nido-tosnodes=1000 -fnesc-simulate -fnesc-nido-motenumber=sim_node\(\) -finline-limit=10 -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=micaz -fnesc-cfile=build/micaz/app.c -board=micasb -Wno-nesc-data-race
BlinkAppC.nc -fnesc-dump=components -fnesc-dump=variables -fnesc-dump=constants -fnesc-dump=typedefs -fnesc-dump=interfacedefs -fnesc-dump=tags -fnesc-dumpfile=app.xml compiling Python support into pytossim.o and tossim.o
g++ -c -shared -fPIC -o build/micaz/pytossim.o -g -O0 /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx -I/usr/include/python2.3 -I/opt/tinyos-2.x/tos/lib/tossim -DHAVE_CONFIG_H/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:30:20: error:
Python.h: No such file or directory/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:375: error: ISO C++ forbids declaration of 'PyObject' with no type/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:375: error: expected ';' before '*' token
/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:376: error: 'PyObject' has not been declared/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:381: error: 'PyObject_HEAD' does not name a type/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:385: error: expected initializer before '*' token
/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:392: error: 'FILE' has not been declared/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function 'int swig_varlink_print(swig_varlinkobject*, int*, int)':/opt/tinyos-
2.x/tos/lib/tossim/tossim_wrap.cxx:395: error: 'fprintf' was not declared in this scope/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:396: error: 'struct swig_varlinkobject' has no member named 'vars'/opt/tinyos-2.x
/tos/lib/tossim/tossim_wrap.cxx: At global scope:/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:404: error: expected initializer before '*' token/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:418: error: 'PyObject' has not been declared
/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function 'int swig_varlink_setattr(swig_varlinkobject*, char*, int*)':/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:419: error: 'struct swig_varlinkobject' has no member named 'vars'
/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:426: error: 'PyExc_NameError' was not declared in this scope/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:426: error: 'PyErr_SetString' was not declared in this scope
/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: At global scope:/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:430: error: 'statichere' does not name a type/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:448: error: expected initializer before '*' token
/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:461: error: variable or field 'SWIG_Python_addvarlink' declared void/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:461: error: 'PyObject' was not declared in this scope
/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:461: error: 'p' was not declared in this scope/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:461: error: expected primary-_expression_ before 'char'/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:461: error: 'PyObject' was not declared in this scope
/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:461: error: 'get_attr' was not declared in this scope/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:461: error: expected primary-_expression_ before 'void'/opt/tinyos-
2.x/tos/lib/tossim/tossim_wrap.cxx:461: error: 'set_attr' was not declared in this scope/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:461: error: 'PyObject' was not declared in this scope/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:461: error: 'p' was not declared in this scope
/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:461: error: initializer _expression_ list treated as compound _expression_/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:461: error: expected ',' or ';' before '{' token
/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:476: error: 'PyObject' was not declared in this scope/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:476: error: 'obj' was not declared in this scope/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:476: error: expected primary-_expression_ before 'void'
/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:476: error: expected primary-_expression_ before '*' token/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:476: error: 'ty' was not declared in this scope/opt/tinyos-
2.x/tos/lib/tossim/tossim_wrap.cxx:476: error: expected primary-_expression_ before 'int'/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:476: error: initializer _expression_ list treated as compound _expression_/opt/tinyos-
2.x/tos/lib/tossim/tossim_wrap.cxx:476: error: expected ',' or ';' before '{' token/opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cx
Re: [Tinyos-help] Antenna gain on tmote
The height may be a factor. That is interesting. I tested it on the ground. My maximum distance in an open football field with PCB antenna is 25 meter ( 80 feet ?) that is similar result to 100 feet. In such a short distance the PCB antenna is not much helpful outdoor. Anybody knows the information of an amplifer with an external antenna? Can I connect a large external antenna like HDTV antenna on the mote? -Chang How high off the ground do you have the motes? To get good transmission distances I would recommend to you that you place them at least 1 yard off the ground, 2 yards is even better. I have done range testing with the standard antenna and some external antennas in an open hay field. We had similar results to what you are getting when they are on the ground. Matt[EMAIL PROTECTED] wrote: - To: Chang Li <[EMAIL PROTECTED]>From: Matt Thompson <[EMAIL PROTECTED]>Sent by: [EMAIL PROTECTED]Date: 07/24/2006 05:26PMcc: tinyos-help@Millennium.Berkeley.EDUSubject: Re: [Tinyos-help] Antenna gain on tmoteI have only had a max distance of 100 feet outdoor line of sight :(-MattChang Li wrote:> What is the maximum distance between two motes who can communicate > outside by your chip antenna?>>> Hi, Does anyone know the dBi gain of the PCB antenna on the tmote sky >> modules?? We have layed out a board with fractus 1dBi gain antennas, >> and we're not getting close to the range of the tmote antennas. >> Trying to figure out if this is due to lack of gain, or other >> design/manufacturing issues (unmatched impedance). Cheers,>> Matt>> ___>> Tinyos-help mailing list>> Tinyos-help@Millennium.Berkeley.EDU>> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help___Tinyos-help mailing listTinyos-help@Millennium.Berkeley.EDUhttps://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help= ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] MTS400 & Multihop routing
Hi, I've been working on a few tinyOS (1.x) projects, and investigating some of the various tools tinyOS provides. Couple of unrelated questions I'd like to ask people reading: 1) Does the MTS400 test program accurately report the calibration data? We've been looking at decoding the pressure readings and they're totally wrong. The code we have works out fine for the example output from the data sheets for the Sensiron, but the data we're getting from the MTS420 is totally bogus. 2) Is there any other example of using the higher level radio communication interfaces besides Surge? I've been meaning to get a better radio system working so we can sample various sensors at different rates cleanly, without worrying about the radio. All the examples work from GenericComm only, and everything I've looked at so far in contrib uses that or GenericCommPromiscuous. Justin Dugger Kansas State University ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Use SerialForwarder or MoteIF?
Hi. I'm writing a bit of Java code to run on a PC connected to mote network. I'm currently using TinyOS-1.x, but at some point I'm sure I'll move to TinyOS-2.x. For my java code, should I connect to a Serial Forwarder to receive packets, or should I use MoteIF to connect directly? The documentation in MoteIF would make it seem like it's far better than Serial Forwarder, and yet everyone seems to be using Serial Forwarder.Thanks! - Conor ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
RE: [Tinyos-help] Problems with GenericComm and PWM
Hi! Thanks a lot for your answer! With the DDRB register, I set the output pins for PWM. In your code, this is done by: TOSH_MAKE_MOTOR1PWM_OUTPUT(); TOSH_MAKE_MOTOR1DIR_OUTPUT(); TOSH_CLR_MOTOR1PWM_PIN(); TOSH_CLR_MOTOR1DIR_PIN(); Where are those functions defined and how can I use them to get PWM to Port OC1A and OC1B? Can I even use these functions without having the cotsbots-board? Furthermore I found that in a header file: /** after cotsbots motor/hardware.h for PWM output: **/ // it appears that the PWM and DIR appellations are reversed // and also that the pins assigned to PWM (sic) are not available // due to their being used by the radio: // PB1 -- SPI_SCK // PB2 -- SPI_MOSI // so gotta try somethong else TOSH_ASSIGN_PIN(MOTOR1DIR, C, 0); // PC0 TOSH_ASSIGN_PIN(MOTOR1PWM, B, 6); // PB6 TOSH_ASSIGN_PIN(MOTOR2DIR, C, 1); // PC1 TOSH_ASSIGN_PIN(MOTOR2PWM, B, 5); // PB5 So there seems to be problems to use radio and PWM together, because of corporate use of PB registers. Can I use TOSH_ASSIGN_PIN() without cotsbots-board in nesC? I tried to compile and there were no errors. But will it work expectedly or do I have to use any more header files like hardware.h? Thanks a lot, BiBe > -Original Message- > From: [EMAIL PROTECTED] [mailto:tinyos-help- > [EMAIL PROTECTED] On Behalf Of Michael Schippling > Sent: Tuesday, July 25, 2006 6:14 AM > To: Birger Becker > Cc: tinyos-help@Millennium.Berkeley.EDU > Subject: Re: [Tinyos-help] Problems with GenericComm and PWM > > sbi() and cbi() should work fine, as long as you are careful > to not touch pins used by the radio. I wouldn't go writing > whole registers with outp() if there is any shared pins. > Double check the schematic for the mote you are using to make sure. > > I have some PWM code in my code bolus: > http://www.etantdonnes.com/Motes/robocode.tar.gz > I forget what reg DDRB is, but I use the timer/counter pins > on the ATMEGA 128 so either I did something right, or you don't > need to touch DDRB... > > MS > > > > Birger Becker wrote: > > Hi! > > I'm currently programming PWM (pulse width modulation) on an ATMega 128 > in a > > tinyOS-environment. Programming of PWM is ready, but now I wanted to > remote > > control one Mote with the PWM by another, which is connected to a > > programming board. > > > > So I used TOSBASE and SimpleCmd for basic and put my PWM code in the > > command-process of SimpleCmd. The TOSBase-Mote is then administrated by > > programming board using UART and it sends commands via RadioCRCPacket to > > SimpleCommand, which receives them by GenericComm. The remote control > works > > fine, I checked by LEDs. > > > > To realize PWM, I used register DDRB of ATMega 128 to set output-Pins. > But > > when any bit of this register is set to 1, no Radio-Packets will be > received > > anymore. > > > > Code like outp(0x20, DDRB) (in tinyOS 1.1.0) and manually set bits by > sbi() > > and cbi() (in tinyOS 1.1.11) results the same curious effect. > > > > How does GenericComm or RadioCRCPacket use DDRB-register and how can I > use > > PWM-ports without getting every Radio-Connection crashed. > > > > Many thanks, > > BiBe > > > > > > ___ > > Tinyos-help mailing list > > Tinyos-help@Millennium.Berkeley.EDU > > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos- > help > ___ > Tinyos-help mailing list > Tinyos-help@Millennium.Berkeley.EDU > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] [tinyos2.0] event timer.fired() getting lost on telosb using BlinkToRadio apps.
Hi,
I've executed BlinkToRadio application with two telosb motes for about 3
hours after adding one line of code in VirtualizeTimerC.nc.
These two motes are still operating correctly without event timer.fired()
getting lost.
It seems that the bug's been fixed.
Thank you.
Inyong Park
> Whoah, it looks like I have a blatantly ugly bug in VirtualizeTimerC
> in lib/timer/ where the remaining time is not correctly calculated for
> an overdue periodic timer.
>
> Note, the radio does not play a significant role. If you take
> Jonathan's sample application, take out all the radio stuff, and
> busywait for 1ms in the fast timer, the problem still occurs. I'm
> surprised that other platforms report to not have this problem,
> because they should.
>
> As a quick hack to see if it solves the problem on your side of
> things, try adding this one line of code at around line 100 in
> VirtualizeTimerC.nc:
>
> else
> {
> // The remaining time is non-positive (the timer had fired).
> // So add dt to convert it to remaining for the next event.
> timer->t0 += timer->dt;
> remaining += timer->dt;
> if (remaining & 0x8000L) remaining = 0; // <-- ADD THIS
> LINE
> }
>
> If a couple of you can test that, then I'll try to mix up a cleaner
> solution and review the rest of the VirtualizeTimerC code.
>
> Thanks,
> Cory
>
> On 7/24/06, Cory Sharp <[EMAIL PROTECTED]> wrote:
>> Boomerang has no significant changes from the 2.x timer stack. We are
>> actively looking into this issue, now. - Cory
>>
>> On 7/23/06, Philip Levis <[EMAIL PROTECTED]> wrote:
>> > On Jul 23, 2006, at 11:37 AM, Jonathan Hui wrote:
>> >
>> > > After a little testing, it looks like the radio stack is still
>> alive.
>> > > I modified BlinkToRadio to maintain two timers (1ms and 1s period),
>> > > both of which attemps to send a message on each fire event. After a
>> > > few moments, the 1ms timer will fail to fire, but the 1s timer will
>> > > continue firing and sending messages. Even more interesting is that
>> > > the 1ms timer starts firing at the same period as the 1s timer.
>> > >
>> > > It's probably the case that the radio stack is somehow affecting the
>> > > operation of the msp430 timer stack and causing it to fail in
>> > > repeatedly firing the 1ms timer. Haven't dug too much into the timer
>> > > code to understand why this is.
>> > >
>> > > I've attached the modified app I used to test.
>> > >
>> > > Cory, do you have an ideas?
>> >
>> > Yeah, I should have given more background. I think it's definitely
>> > the case that it's the MSP430 timer stack, which runs into some
>> > issues when timers are at too fast a rate (e.g., 1ms). E.g., in the
>> > 2.0 tutorials, there's a part where you try using very long tasks of
>> > different length to show the run-to-completion semantics. On atm128
>> > platforms, a task that's too long causes you to lose timer events but
>> > things continue as expected; on msp430 ones, the timer stack can act
>> > erratically.
>> >
>> > Joe, Cory, does Boomerang 2.0.2 use the 2.x timer stack unchanged, or
>> > have you incorporated fixes?
>> >
>> > Phil
>> >
>>
> ___
> Tinyos-help mailing list
> Tinyos-help@Millennium.Berkeley.EDU
> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Help writing to telosb over UART in Python
I am writing a Pyhton software to manage our mote testbed; I must use Python
to integrate into the 'larger' system and I must use TinyOS-1.x.
I am having trouble writing to the motes over UART. I can read from them
perfectly i.e. I have implemented the HDLC-like framing and CRC calculation
and all is well. For example, I read the following from a telosb mote running
the Oscilloscope image:
rxpkt: 7e 42 0e 00 00 00 00 00 7d 5e 00 1b 7d 5d 00 00 8d 00 00 0d 9c dc 43 01
00 f6 00 08 66 3f 7e
[As an aisde, can anyone explain why the payload length is moved to rxpkt[2],
and where bytes rxpkt[3-7] come from?]
My goal here is to implement a 'command interpreter' on the mote, where
commands are sent from the PC.
The content of CommandMsg.h is as follows:
enum {
COMMAND = 1 << 15,
STATUS = 0 << 15,
INTERNAL = 1 << 14,
EXTERNAL = 0 << 14
};
struct CommandMsg
{
uint16_t cmd;
uint16_t mask;
uint16_t arg;
};
enum {
AM_COMMANDMSG = 20
};
The byte array (Python: array.array('B')) of data I want to send goes through
the following transformations:
Data: 0b 00 00 00 a3 08 (11, 0, 2211)
Message: 7e 00 1b 7d 0b 00 00 00 a3 08
Packet: 7e 42 06 00 00 00 00 00 7d 5e 00 14 7d 5d 0b 00 00 00 a3 08 f9 f0 7e
The final packet format reflects what I read of the wire i.e. Packet[2] is the
data length followed by 5 pad bytes.
I open the port with the following Python code (assume necessary modules are
imported):
def open(self):
self.__fd = os.open(self.__port, os.O_RDWR|os.O_NOCTTY)
iflag, oflag, cflag, lflag, ispeed, ospeed, cc = \
termios.tcgetattr(self.__fd)
cflag = termios.CS8 | termios.CLOCAL | termios.CREAD
iflag = termios.IGNPAR | termios.IGNBRK
oflag = 0 # saw this in serialsource.c
ispeed = termios.__dict__['B'+str(self.__baudrate)]
ospeed = termios.__dict__['B'+str(self.__baudrate)]
termios.tcflush(self.__fd, termios.TCIFLUSH);
termios.tcsetattr(self.__fd, termios.TCSANOW, \
[iflag, oflag, cflag, lflag, ispeed, ospeed, cc]);
When I write the packet, the little green LED by the mote-USB connector (not
the main 3-LEDS) flashes, but I do not get the desired result i.e. the main
red-LED does not switch on (as it is 'commanded' to).
Has anyone achieved writing to a (telosb?) mote in C or Python? Have I set the
wrong output flags (oflag) on the serial port maybe? Have I got the frame
format wrong?
Your help is appreciated.
--
Warm regards,
Darren Bishop, MSc, BSc (Hons), MBCS
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Re:setting node ID
hi, try use dot not comma: make mica2 install.1 mib510,com1 -- Alex Junyan Ma A804 Aviation Building Northwestern Polytechnical University Xi'an, Shaanxi, China P.R. EMAIL: alexmajy at gmail dot com MSN: alexmajy at hotmail dot com ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
RE: [Tinyos-help] setting node ID
Hi! For micaz node, i'm setting node-id by "make micaz install.1". So try your command with a dot instead of the comma. Birger > -Original Message- > From: [EMAIL PROTECTED] [mailto:tinyos-help- > [EMAIL PROTECTED] On Behalf Of jurin dan > Sent: Tuesday, July 25, 2006 7:11 PM > To: tinyos-help@Millennium.Berkeley.EDU > Subject: [Tinyos-help] setting node ID > > > hi, > > i'm using tinyos v.1.1.10 and i want to set a node ID. i used > this > command: > make mica2 install,1 mib510,com1 > message error was: > make:***No rule to make target '1'. Stop. > > is somebody aware of the right syntax of the command? > > thx > > _ > Play Q6 for your chance to WIN great prizes. > http://q6trivia.imagine-live.com/enca/landing > > ___ > Tinyos-help mailing list > Tinyos-help@Millennium.Berkeley.EDU > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] setting node ID
there was some debate about the use of a comma being ok, but I always use a dot: install.1 MS jurin dan wrote: hi, i'm using tinyos v.1.1.10 and i want to set a node ID. i used this command: make mica2 install,1 mib510,com1 message error was: make:***No rule to make target '1'. Stop. is somebody aware of the right syntax of the command? thx _ Play Q6 for your chance to WIN great prizes. http://q6trivia.imagine-live.com/enca/landing ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Question about lost of packets with MultiHop.
On Jul 25, 2006, at 12:03 AM, Munaretto, Daniel wrote: So what you mean is in tinyos-1.x is impossible to bypass this problem, isn'it? Or if there is a solution in 1.x, in my project would be really important, should you explain it? Of course it's not impossible: you can modify the stack. You want to modify the stack so that it does not flush the RXFIFO but instead spools out the packets. Phil ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] setting node ID
try: make mica2 install.1 mib510,/dev/ttyS0 note that I have used period one ".1" not comma one ",1" - Original Message - From: "jurin dan" <[EMAIL PROTECTED]> To: Sent: Tuesday, July 25, 2006 1:11 PM Subject: [Tinyos-help] setting node ID hi, i'm using tinyos v.1.1.10 and i want to set a node ID. i used this command: make mica2 install,1 mib510,com1 message error was: make:***No rule to make target '1'. Stop. is somebody aware of the right syntax of the command? thx _ Play Q6 for your chance to WIN great prizes. http://q6trivia.imagine-live.com/enca/landing ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Question about lost of packets with MultiHop.
On Jul 25, 2006, at 3:33 AM, Krisakorn Rerkrai wrote: Does this mean these two packets are both acknowledged but the second one in the FIFO is flushed out? Yes. Phil ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] TinyOS 1.x apps gives absurd result after installing TinyOS 2.x
On Jul 25, 2006, at 1:18 AM, Mohan Hambar wrote: I have tried by changing the environment variables. But even with the properly set environment variables, I got wrong results. I am not getting the reason behind that. For 1.x the variables are set as TOSROOT ="/opt/tinyos-1.x" TOSDIR="$TOSROOT/tos" CLASSPATH =`$TOSROOT/tools/java/javapath` MAKERULES ="$TOSROOT/tools/make/Makerules" and for 2.x TOSROOT ="/opt/tinyos-2.x" TOSDIR ="$TOSROOT/tos" CLASSPATH=`cygpath -w $TOSROOT/support/sdk/java/tinyos.jar;.` MAKERULES="$TOSROOT/support/make/Makerules" Without looking at your setup, it's hard to know exactly what is going on. But it seems pretty likely that it's a packet size mismatch problem. It seems that xlisten doesn't use any of the Java stuff, so it's hard to say exactly what's going on. You might want to use the Listen or ListenRaw tools to see what the packets coming out look like. Phil ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] setting node ID
hi, i'm using tinyos v.1.1.10 and i want to set a node ID. i used this command: make mica2 install,1 mib510,com1 message error was: make:***No rule to make target '1'. Stop. is somebody aware of the right syntax of the command? thx _ Play Q6 for your chance to WIN great prizes. http://q6trivia.imagine-live.com/enca/landing ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] question related to buf size of mate'
Hi All, Currently, I changed the buffer size of mate' vm, however, I encounter the following problems: 1. using the UART to send the buffer with the size 50 seems all right, however, the send_lqi result in an error. For example, I write an program to increase the buf size every time by one and transmit it. The UART can transmit correctly but the send_lqi will always generate an error before the buf reach its predefined max size (50 in my program) 2. I tested the max size I can use in my system and find that it is no more than 61, if I changed the buf size to 67 manually and run program with out sending any buf or even do not claim a buf variable in my tinyscript, the program can not be injected into the tmote sky at all. I guess the problem related to the DTOSH_DATA_LEN, it seems can not exceed 124+10. Could you give me some hint for the reason? Best Regards, Song Guo ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] switching on several analog input
Hi I try to connect on my TMote sky an analog sensor with 3 output, so I have to make acquisitions on 3 inputs, Is there a speed way for switching on several analog input (for example for each timer fired, change the configuration on the CAN..) Thank you for all. Nicoo ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Can classes be made in tinyos1.x
On Tuesday 25 July 2006 12:17 am, s bash wrote: > hi to all > i want to inquire that can we make classes and their instances in > Tinyos1.x? waiting for reply TinyOS is built on nesC, which is an extension to the C language. It is not object oriented and has no concept of classes or objects per se. One can define C structures in TinyOS, but the programming paradigm of creating "pseudo objects" in C structures won't work so well in TinyOS. Instead, you should construct your TinyOS programs using its core features: modules and configurations. Please read the excellent http://csl.stanford.edu/~pal/pubs/tinyos-programming.pdf for more information. Steve ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Question about lost of packets with MultiHop.
Does this mean these two packets are both acknowledged but the second one in the FIFO is flushed out?On 7/25/06, Philip Levis < [EMAIL PROTECTED]> wrote:On Jul 24, 2006, at 1:21 PM, José Ulloa wrote: > Hi, we are working with a network with six or more hops, and> tinyos-1.x. We have detected a lost of packet in a node, after> receiving the packet and sending the corresponding ACK.> ¿is this posible because the radio had two packet in the RXFIFO in > the moment of read?> I understand, when tinyos-1.x reads the first packet, the second> will be descarted by the call of flushRXFIFO from the CC2420RadioM> component. ¿is this really happening? ¿someone knows a solution for > this?Yes, this is really happening. It's a fairly nasty issue in the 1.xstack. The TinyOS 2.0 stack doesn't have this issue; it keeps trackof packets in the FIFO and spools them out one by one. If a packet can't fit in the FIFO, then the radio doesn't acknowledge it.Phil___Tinyos-help mailing listTinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Issue with CntToLedsAndRfm and RfmToLeds
There are some significant difference between the Makerules Marcin had on his machine and I had on my machine. I guess this files is generated while TinyOS is installed. Cheers, Alexandre Am Jul 25, 2006 um 12:54 AM schrieb Michael Schippling: well...yeah. What was the magic? MS Alexandre Bergel wrote: Marcin, our local TinyOS expert, gave me a new Makerule replacing the one in /opt/tinyos-1.x/apps. It works fine now. I can send it on request. Thanks Marcin! Cheers, Alexandre Am Jul 23, 2006 um 8:29 PM schrieb bhushan bhatt: I used tinyos 1.1.15 on XP. I was working with tmote and gave command "make tmote install 0" and and install 1. As far as i remember, u have to give id like 0 and 1. If you see in the program, the mote with id 1 would send a binary countdown sequence to mode with id 0. Try with 0 and 1 instead of 38 and 39. Let me know later how you figure out the problem. Bhushan Alexandre Bergel <[EMAIL PROTECTED]> wrote: Thank to Bhushan and you for your answer. I tried to assign different ID, but it still does not work. I also tried: cd MicaHWVerify make mica2 install.38 "On a first mote" cd TOSBase make mica2 install.39 "On a second mote" But still no blinking leds on the second mote... I will see an expert in mote (Marcin) on Monday. I hope to solve this problem. I use TinyOS 1.1.0. with Windows XP. Cheers, Alexandre Am Jul 23, 2006 um 1:21 AM schrieb Michael Schippling: > You don't say what version of TOS, but I had variable results > until I used v1.1.7 and above, _and_ moved the app to the contrib/xbow > tree (which is the only place I could make mica2 radio work very > well). > > You might try MicaHWVerify and TOSBase to see if you have any radio > communication at all. Make sure your antennas are well connected. > > Also, it probably doesn't matter in this case, but you should assign > different IDs to each mote, like install.38 and install.39 > > MS > > Alexandre Bergel wrote: >> Hello! >> I encounter some problem while trying to make two motes >> communicate each other. >> For instance, in the apps/CntToLedsAndRfm folder, I do a make >> mica2 install.38 >> Then I use another mote, and in apps/RfmToLeds I do a make mica2 >> install.38 >> I would expect to see the value of the leds of the first mote to >> appear on the second motes. But it does not. >> Is there something obvious that I did not see ? >> Thanks a lot! >> Alexandre >> --_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.cs.tcd.ie/Alexandre.Bergel >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> ___ >> Tinyos-help mailing list >> Tinyos-help@Millennium.Berkeley.EDU >> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/ >> tinyos-help --_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.cs.tcd.ie/Alexandre.Bergel ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/ tinyos-help See the all-new, redesigned Yahoo.com. Check it out. --_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.cs.tcd.ie/Alexandre.Bergel ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/ tinyos-help -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.cs.tcd.ie/Alexandre.Bergel ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Fwd: interface matlab java
Note: forwarded message attached. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --- Begin Message --- sir, I want to use matlab commands in my java program. I hav downloaded the file MatlabControl.java. But I cant compile it. the error is the package com.mathworks.jmi cannot found. How to get it done. What is classpath. where the program shouold be stored and run. Please reply in detail. usha jogalekar __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --- End Message --- ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] High resolution micaz timer in tinyos 1.x
Title: High resolution micaz timer in tinyos 1.x Hi, I'm trying to use a high resolution timer on my micaz. I know that there are compatibility issues with timer2 and the micaz radio both trying to use the int2 port. What exactly do I need to change? Has anyone successfully got it to work? I'm using Tinyos-1.x, will there be a new version of timer in 2.x which will not have this problem? Cheers, Mike ** Wireless Communications Enabling Metrology Division National Physical Laboratory Hampton road Teddington United Kingdom TW11 0LW 0208 943 6771 www.npl.co.uk ** --- This e-mail and any attachments may contain confidential and/or privileged material; it is for the intended addressee(s) only. If you are not a named addressee, you must not use, retain or disclose such information. NPL Management Ltd cannot guarantee that the e-mail or any attachments are free from viruses. NPL Management Ltd. Registered in England and Wales. No: 2937881 Registered Office: Serco House, 16 Bartley Wood Business Park, Hook, Hampshire, United Kingdom RG27 9UY --- ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: Re: [Tinyos-help] TinyOS 1.x apps gives absurd result after installing TinyOS 2.x
I have tried by changing the environment variables. But even with the properly set environment variables, I got wrong results. I am not getting the reason behind that. For 1.x the variables are set as TOSROOT ="/opt/tinyos-1.x" TOSDIR ="$TOSROOT/tos" CLASSPATH =`$TOSROOT/tools/java/javapath` MAKERULES ="$TOSROOT/tools/make/Makerules" and for 2.x TOSROOT ="/opt/tinyos-2.x" TOSDIR ="$TOSROOT/tos" CLASSPATH=`cygpath -w $TOSROOT/support/sdk/java/tinyos.jar;.` MAKERULES="$TOSROOT/support/make/Makerules" Thanks and Regards, Mohan On Tue, 25 Jul 2006 David Gay wrote : >On 7/24/06, Philip Levis <[EMAIL PROTECTED]> wrote: >>On Jul 24, 2006, at 4:24 AM, Mohan Hambar wrote: >> >> > Hi All, >> > >> > I have recently installed tinyos 2.x source tree on my windows >> > machine keeping tinyos 1.x. >> > >> > I am able to compile both (1.x and 2.x)apps. >> > >> > But after installing tinyos 2.x, tinyos 1.x apps like surge are giving >> > absurd results. >> > >> > Surge Result in xlisten: >> > >> > health: node id=1 parent=126 seq_no=8275984 >> > battery = 4969 mv >> > temperature = -273.15 degC >> > light: = 0 ADC mv >> > AccelX: = 1080.00 g, AccelY: = -9000.00 g >> > MagX: = 112.36 mgauss, MagY: = 68.06 mgauss >> > >> > Can anyone help in this regard? >> > >>TinyOS 1.x and 2.x use different serial packet formats. In TinyOS >>1.x, serial packet formats are platform-specific. In TinyOS 2.x, the >>serial stack supports having different packet formats, and the basic >>format is platform-independent (so you no longer need platform- >>specific message structures for the base case). You therefore need to >>change your CLASSPATH based on which version you are using. >> >>I've found that switching back and forth requires changing three >>variables: >> >>CLASSPATH, for java support >>TOSDIR, for the TinyOS source tree >>MAKERULES, for the make system > >It's a good idea to change TOSROOT too - it's used here and there. > >David Gay ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Using matchbox
Hi all, I'w know if matchbox writes only on RAM or also in FLASH. I'w tryed matchbox applications (like CopyIn e CopyOut) but when I reset the mote the file that I have written doesn't exist more. How can I write on flash using matchbox? Can someone help me? Thanks. Roberto ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
RE: [Tinyos-help] Question about lost of packets with MultiHop.
So what you mean is in tinyos-1.x is impossible to bypass this problem, isn'it? Or if there is a solution in 1.x, in my project would be really important, should you explain it? Thanks very much, Cheers Daniele -Original Message- From: Philip Levis [mailto:[EMAIL PROTECTED] Sent: Tue 7/25/2006 7:33 AM To: José Ulloa Cc: Tinyos-help@Millennium.Berkeley.EDU Subject: Re: [Tinyos-help] Question about lost of packets with MultiHop. On Jul 24, 2006, at 1:21 PM, José Ulloa wrote: > Hi, we are working with a network with six or more hops, and > tinyos-1.x. We have detected a lost of packet in a node, after > receiving the packet and sending the corresponding ACK. > ¿is this posible because the radio had two packet in the RXFIFO in > the moment of read? > I understand, when tinyos-1.x reads the first packet, the second > will be descarted by the call of flushRXFIFO from the CC2420RadioM > component. ¿is this really happening? ¿someone knows a solution for > this? Yes, this is really happening. It's a fairly nasty issue in the 1.x stack. The TinyOS 2.0 stack doesn't have this issue; it keeps track of packets in the FIFO and spools them out one by one. If a packet can't fit in the FIFO, then the radio doesn't acknowledge it. Phil ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
