Hi Zhiyi,
the original telosb doesn't have an accelerometer, but in general you
can contribute by putting your code in tinyos-2.x-contrib [1]. If it
is only about the msp430adc12_channel_config_t you might as well just
send that code snippet to tinyos-help mailing list.
Jan
[1]
Sorry for kicking the old dirts. I followed this thread but have not
found what I needed.
I have the similar problem with ADC: I can't read proper data from
light sensors or any sensor on the sensor board EM1000.
I have tried Oscilloscope and it works for the InternalTemperature and
Jan,
Thanks for help. My program works now. Actually it is a bit
embarrassed to say the reason was that the sensor board was not
plugged tightly enough on the mote.
Also I noticed there was no adc12 modules for accelerometers on
telosb. Could I make such a module and contribute to the code
Your configuration seems identical to the telosa/b configuration
(S1087-01 light sensor on port A5). There is already a component (have
you tried it?) -
tinyos-main/tos/platforms/telosa/chips/s10871/HamamatsuS10871TsrC.nc
Jan
On Sun, Nov 27, 2011 at 11:52 PM, zhiyi zhu...@cs.otago.ac.nz wrote:
Are there any of the standard telosb external sensors
(Humidity/Temperature/Light) available on your telosb ? Can you test
whether they give you good readings (or test your code with the
internal sensors of the msp430).
2) open tinyos-2.x/tos/chips/msp430/adc12/Msp430Adc12.h and comment
out
What hardware (MCU, sensor) are you using ?
MCU - platform
if you are reading
temperature, then there obviously should not be such spikes, so it
looks like there is a problem with reading data from the sensor. I
just re-ran Oscilloscope for all external sensors on telos and it
worked
- what is the search path for components?
I'd like to create, as you write above, my own TemperatureClientC class,
HumidityClientC, for code-reuse and also for code clarity. If I just
create an TemperatureClientC.nc file, where do I have to put it so that
the build process finds it?
You can
Jan,
You can for example (1) put it in your application folder, (2) create
a new folder and include it with CFLAGS in you Makefile, (3) put it in
-Ifolder_name would do the trick?
any of the directories contained in your tos/platform/.platform file
or (4) if it is a driver for a new
Jan,
As I said, an app does not actively configure the ADC but only
provides an event handler returning its configuration. Your
application could look like this:
configuration MyAppC {
} implementation {
components AppC, new AdcReadClientC(), MyConfigC;
AppC.Read - AdcReadClientC;
Jan,
If the Read interfaces are not good enough, take a look at
tinyos-2.x/tos/chips/msp430/adc12/Msp430Adc12Client*.nc. These
components export the msp430 specific functionality. If you use them
your code will not be so portable anymore, but you can do things like
high-frequency sampling of
Did deeper into DemoSensor. First of course you have to figure out
which one and where it is...I don't (yet) have a tmote dev environment,
but for the Mica's it's in tos/sensorboards/micasb/DemoSensorC.nc
DemoSensorC on telosb simply calls the internal voltage sensor - it's not
related to any
Well, yeah...But doesn't every platform also have the raw ADC
implementation
which provides exactly the same interface, with a (well, to my low-level
mind)
more straightforward connection to the external world? Admittedly there
are
some 'tricks' that need to be performed to get, e.g., the
I looked at the document - and it contains a partial sample code. Still,
is there a complete application sample somewhere that configures and reads
from and ADC on telosb, and does something with it? Like TestAdc, just for
real? By that I mean that it really configures the ADC, specifies which
Well, look at the micasb version. It wraps Photo (or Temp, I never remember)
which further wraps ADC (which does actually do something in-between...).
I'm going to assume that the telosb internal voltage sensor is implemented
as some kind of ADC as well. The basic pattern is:
// in some
The top (HIL) ADC layer uses the AdcConfigure interface and provides
the Read, ReadNow and ReadStream interfaces - AdcConfigure is for ADC
configuration (e.g input channel), the others are for reading out
data. AdcConfigure is *called* by the ADC stack every time a client
has asked for ADC data
Hi,
I'm trying to read the analogue input channels from my T-Mote Sky mote
(telosb platform), but even though I read through the sensor tutorial, I
don't really know how. Can someone give me some help?
I saw that there's an ADC interface, as defined in TEP 101. And on the
telosb platfrom, I
Did deeper into DemoSensor. First of course you have to figure out
which one and where it is...I don't (yet) have a tmote dev environment,
but for the Mica's it's in tos/sensorboards/micasb/DemoSensorC.nc
What you will find is that it is a dimly veiled layer over an ADC input,
which, IMHO, just
What you will find is that it is a dimly veiled layer over an ADC input,
which, IMHO, just obscures and obfuscates the usage...
Yes, however every platform has a DemoSensor, which allows demos (not
applications) to be written and compiled irregardless of the platform
(thus the prefix Demo)
Well, yeah...But doesn't every platform also have the raw ADC implementation
which provides exactly the same interface, with a (well, to my low-level mind)
more straightforward connection to the external world? Admittedly there are
some 'tricks' that need to be performed to get, e.g., the micasb
19 matches
Mail list logo
