There is some indication that the mica ADCs (at least) will queue getData() requests on different channels and fire them sequentially. However I'm not a trusting sort, so I chain them by starting a new conversion from the dataReady() of the previous.
The actual conversion time depends on the setting of the pre-scale clock (again in micas, but I think tmotes have a similar feature). IIRC the slowest mica2 conversion is about 1/3 milli-sec and the fastest is on the order of 256x faster. Theres a table in T1 mica2/ADCControl.nc that shows something or other like this. MS Eric Keller wrote: > What hardware are you using? I suspect that it will not work as written, but > if it does, the data will be returned in the order you call the get > data. I think you have to > trace through the calls that you have made and see what is actually done when > you make the calls. It's a lot of work. > Eric > > > > On Mon, May 5, 2008 at 2:07 PM, subhash nemani <[EMAIL PROTECTED]> wrote: >> hi >> In this code i'm calling all of the sensors connected to the ADC >> ports simultaneously >> what will be the time lag between the data acquisition from the ADC ports? >> will i get all the samples simultaneously???????? >> please give me reply as soon as possible. >> >> >> _______________________________________________ >> Tinyos-help mailing list >> [email protected] >> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >> > _______________________________________________ > 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 _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
