> I got the accelerometer interfaced to the ADC via the following > instructions on the website: http://www.moteiv.com/community/ > Connecting_External_Sensors. However, this binds a single analog > port to the ADC, and this seems to be the single-channel-single- > conversion mode. In order to get it working I had to put a > semaphore-like block around the getData call to my three ADC > interfaces, sort of like a sendMsg call (i.e. you can only be > converting X, Y, or Z axis port at one time). This works, but is a > bit sluggish. For the three axis accelerometer I would prefer the > ADC to continuously translate the voltage on the x, y, and z ports. > This sounds like the repeat sequence-of-channels mode. I haven't > found any tinyOS documentation that talks about the ADC in depth to > touch on different conversion modes. My code is very similar to the > code on the website above. > > I was wondering if tinyOS 2.x had anything in place to support > other ADC conversion modes.
Yes - have a look at the Msp430Adc12MultiChannel interface provided by tos/chips/msp430/adc12/Msp430Adc12ClientC.nc. (I'm going extend the tos/chips/msp430/adc12/README.txt with an example.) Jan
The best person to ask would be Jan Heinrich-Hauer, who wrote the MSP430 ADC system; I think TEP 101 goes into some details. I'm not that familiar with all of the details. There is an interface that sounds promising, though, Msp430Adc12MultiChannel: http://tinyos.cvs.sourceforge.net/tinyos/tinyos-2.x/tos/chips/msp430/ adc12/Msp430Adc12MultiChannel.nc?revision=1.2&view=markup Phil _______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
