Hi Richard,
I'm more familiar with TinyOS 2.x, so I'm not sure how it would best
work in TinyOS 1.x. It looks like there might be a module implementing
access to the sensirion sensors in the contrib folder, but I'm not sure
for which platform this was written. Have a look at the code in:
Hi Richard,
I didn't see the HumidityC.nc file (as I said I'm not that familiar with
TinyOS 1.x). Did you wire the StdControl interface? What do you mean
when you say it did not work properly? Does it not compile (if so, can
you give us the exact error message)? Or do you get values that seem
1. command error_t send(message_t* msg,uint8_t len)
command error_t cancel(message* msg)
command errot_t StdControl.start()
command errot_t StdControl.stop()
..
What is the error_ for?
2. I cann't unstand the sentences:
SUCCESS was a non-zero error code in TinyOS 1.x, while
hello,
I have noticed that in TOSSIM, if a mote is busy receiving a packet, then a
newly received packet will be discarded, however, the fisrt packet will be
received successfuly. Does this means that collissions are not possible in
TOSSIM? attached is the code from the CpmModelC.nc file
In T1 you should have:
tos/platform/msp430/MSP430GeneralIOM.nc
to do about the same thing...
Or I think you can go deeper and use the TOSH_ASSIGN_PIN() route.
Search this list for my missives on usage of the above.
Also for the transistor part, google for common emitter and
open collector
What is the error_ for?
When you call a command, that command returns error type.
The command return value can tell you
- there was no error
- error, you did something wrong
- error, I did something wrong
- error, I am not turned on
- error, argument was wrong
etc
'error_t' is for
AMSend.send() is not successful sometimes. What are some possible causes
for an unsuccessful send?
We have tried restarting the radio (i.e. turning it off, then turning it
back on) when a send is unsuccessful, but it hasn't helped.
Is it possible that the radio fails to turn on/off even if the it
John Griessen wrote:
I am figuring out how to compile form contrib and have a question:
I found docs on makerules that answered my question.
John G
--
Ecosensory
tinyOS devel on: ubuntu Linux; tinyOS v2.0.2; telosb ecosens1
___
Tinyos-help
Hi all,
Is there a list of all available routing protocols for TinyOS 2
somewhere? I'd like to write a paper that suggests what routing
protocol most compliments what topology. From what I can see, there
are only four available: Collection Tree, Collection (is this the same
as CTP?),
Hey thanks for helping me out before.
Still using xmda300 on an iris mote.
Im trying to talk to the digital channels, it says in the datasheet they can
be used as inputs and outputs. How can i write to them? and how can I read
from them without calling the sampler?
Thanks again
El
Dear all,
I am currently working on the using Matlab with TinyOS, and I can read
the received raw data from the base station(which is attached to the
computer via the UART) and display them on the command window in the
Matlab. I am wondering what is the best way to save the received data
Hi everybody,
When I try to run the Listen application to see the raw packets i get the
following error. I have set the MOTECOM=serial@/dev/ttyUSB0:mica2
, as I am using the /dev/ttyUSB0 to program the motes. (I am running tinyos
1.1.14 on Xubuntu)
java net.tinyos.tools.Listen
Error on
be aware that Collection and Dissemination are two complement services
provided by TinyOS. In terms of doing a survey on routing protocols, I
will suggest you to search some research papers from IEEE or ACM.
regards;
Peizhao
Daniel Galvin wrote:
Hi all,
Is there a list of all available
Hi,
We are implementing a time synchronization algorithm on micaZ platform.
To enable cpu to enter sleep mode when there is no communication, we use timer0
(32.768KHz) to get localtime.
But we noticed that the micaZ mote occasionally miss the clock interrupt which
causes the localtime to
Hi,
For the output 3, this should be /opt/tinyos-2.x/support/make/Makerules.
Make sure your make directory is inside the support directory.
If it still doesn't work, it would look like some sort of
misconfiguration. Are you running this on cygwin? If so there might be a
problem with
Hi,
To summarize your problem, you're running Linux natively on your
computer. You are using TinyOS 1.x. When trying to access the serial
port with the TinyOS 1.x Java APIs, you get errors saying that you
should use Windows-style port names. Is this correct?
If so, did you install by accident
16 matches
Mail list logo
