I'm cc'ing this back to the help list to keep a record of my mistakes... Yes, TOS 1.1.10 is the version where "they" supported micaz and put an almost invisible clamp at 3ms in the Timer setting. 3ms should be way shorter than you need in your application, but it doesn't work below that.
As I usually say, everything is (im)possible with software. To the extent that you will be modifying .nc files you will need to do nesC coding, however changing a value in the Timer and doing a range comparison is basic C, so it shouldn't be too hard. Meaning: no config file mods. mica2's can send about 25 messages/sec so the minimum cycle is about 40 or 50 ms. That's why I suggested the range discriminator. Do your samples as fast as you can and then check them for some kind of on-off change and only send a message when that happens. The Oscope program aggregates a bunch of samples before sending so you'll probably want to change that behavior as well. It's a great adventure... MS Matthew Melucci wrote: > Thank you for your response. I am new to this stuff. First what is > T1.1.10? Is that the tinyos version? Also how can you find the message > transmit time? And one more question. With the Oscilloscope the data > is constantly changing. Even with the laser pointed at it. It never > stays constant but it does still stay in a certain area. Will the > discriminator still work for that? And will all this involve doing > nesC coding? Thank you so much for the response!! > > On Tue, Apr 8, 2008 at 1:47 PM, Michael Schippling <[EMAIL PROTECTED]> wrote: >> Look for this in OscilloscopeM.nc::start(): >> call Timer.start(TIMER_REPEAT, 125); >> >> The 125 argument is the number of "binary milli-seconds" to wait >> between sample cycles. If you are using >= T1.1.10 the minimum >> value for this is 3. However if you run that fast you will overrun >> the message transmit time, so you probably want to put a discriminator >> on the sampled data and only send a message when it changes. >> >> MS >> >> Matthew Melucci wrote: >>> >>> >>> Is there a way to speed up how fast it gets data and writes it? I use >>> mica2 and use Listen > output to write to a file. I have an app I >>> wrote that tracks people entering and exiting through an area. I point >>> a laser at the sensor and if it gets cut from someone walking through >>> it and breaking it I record it. But the problem is it only works if >>> they break the beam for so long. A quick break isn't recorded. Is >>> there a way to fix this? Thanks!!! >>> _______________________________________________ >>> Tinyos-help mailing list >>> [email protected] >>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >>> >> -- >> Platform: WinXP/Cygwin >> TinyOS version: 1.x, Boomerang >> Programmer: MIB510 >> Device(s): Mica2, MicaZ, Tmote >> Sensor board: homebrew >> >> -- Platform: WinXP/Cygwin TinyOS version: 1.x, Boomerang Programmer: MIB510 Device(s): Mica2, MicaZ, Tmote Sensor board: homebrew _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
