Hi,
I am receiving the following error, can anyone tell me what is the
problem?? I read in installation that we need to reboot the system when
we have installed the files for tinyos-2.x if there is such an error but
i have tried that as well, but its not compiling. The error is as follows:
$
Hi,
I've upgrated my tinyos tools in order to start working with telosb
platform. I can compile aplications with that platform but I'm not able to
install them in the motes. Here is prompt text:
/opt/tinyos-1.x/tools/make/msp/set-mote-id --objcopy msp430-objcopy
--objdump msp430-objdump --targe
Ok, I tried what you suggested and I found out, that there seemed to be
the Problem that this I2C.commandComplete() event was not signaled, so
everything after setStart failed. After playing around a little, I
changed the I2C.init function in HplAtm128I2CBusP.nc to:
if (TRUE) {//hasExternalPul
Dear all,
I've wrote the user program to display all serial packet from USB port in
Linux. (/dev/ttyUSB0)
One mote was programmed in Oscilloscope and the other was in BaseStation. (in
Tinyos 2.0)
Following is the received all serial data.
7E 45 00 FF FF FF FF 1C 00 93 00 00 8F
In my
Hi,
I am new to tinyos and I got some problems in using MultiHopRouter.
I need to implement a testing program which a node will send an integer to
other nodes, and other nodes will increase the number by 1 and then send
to other nodes again and again. A node will connect to the PC and display
the
You should use MultiHopLQI. See /opt/moteiv/apps/Delta for an example.
-Joe
On 12/29/06, YIP Chi Chung <[EMAIL PROTECTED]> wrote:
Hi,
I am new to tinyos and I got some problems in using MultiHopRouter.
I need to implement a testing program which a node will send an integer to
other nodes, and
I think this is a cygwin version problem,
search back on this list for "getreent"...
MS
Spidernet Lists wrote:
Hi,
I am receiving the following error, can anyone tell me what is the
problem?? I read in installation that we need to reboot the system when
we have installed the files for tinyos-
Also, cygwin apparently needs to have setup.exe run after an install to run
cleanup scripts.
So: setup, install, reboot; setup, scripts, reboot; reboot (just to be safe)
Now try it.
Remember the _Windows_Mantra_: "Reboot, Reboot, Reboot"
On Wed, January 3, 2007 1:24 pm, Michael Schippling said:
On Jan 3, 2007, at 9:04 AM, Joe Polastre wrote:
You should use MultiHopLQI. See /opt/moteiv/apps/Delta for an
example.
-Joe
On 12/29/06, YIP Chi Chung <[EMAIL PROTECTED]> wrote:
Hi,
I am new to tinyos and I got some problems in using MultiHopRouter.
I need to implement a testing program w
Hi again,
Would you mind if I ask you another question?
We have to write our program (wich communicates with the Mote Network)
in VB.net, so we are about to code some kind of message listener in
.net. Now we're hanging in decoding / encoding our messages. In
particular, building the checksum
I have a complex application with a half dozen timers. One of the timers is
used to count a clock once per second. The timer is set up with a call that
looks like this:
call TimerClock.start(TIMER_REPEAT,1000);
The timer is never stopped or changed.
I count a variable in the TimerClo
The timer system in TinyOS does not guarantee any particular accuracy, only
that "accuracy MUST remain reasonable", probably something like +/-10% of
the declared units. This is for various reasons including but not limited
to temperature, voltage, and manufacturing variations that affect hardwar
I actually discovered this problem when I started to implement a time
synchronization protocol. I am trying to log the time a sample was actually
taken on the mote and when that mote comes back in radio range report the
list of samples and times they were taken.
The problem is that my logs of whe
Chong Hui Kim wrote:
> Following is the received all serial data.
> 7E 45 00 FF FF FF FF 1C 00 93 00 00 8F
> In my thought,
> 7E - HDLC_FLAG_BYTE
> 45 - SERIAL_PROTO_PACKET_NOACK
> 00 - TOS_SERIAL_ACTIVE_MESSAGE_ID
> FF FF - DESTINATION ADDRESS
> FF FF - SOURCE ADDRESS
> 1C - LENGTH
> 0
Of course the device capable for some definition of capable. But the
keyword isn't capability but calibration: ensuring the mote records accurate
time across varying conditions and manufacture. Keep in mind that "varying
conditions" even includes things like turning on a high power sensor causin
For time counts driven by a crystal the types of errors you are talking
about should result in time variations of seconds per day. What I am seeing
is seconds per minute.
A repeating counter set to 1000 milliseconds should count seconds with some
jitter. I don't expect the events to be exactly on
Treat the clock in binary millieseconds (1024 Hz) instead of decimal
milliseconds (1000 Hz). With the clock is running at 1024 ticks per second,
then you lose about 1.5 seconds per minute if you wait 1000 ticks instead of
1024. - Cory
On 1/3/07, Michael Newman <[EMAIL PROTECTED]> wrote:
For
On Jan 3, 2007, at 4:41 PM, Michael Newman wrote:
For time counts driven by a crystal the types of errors you are
talking about should result in time variations of seconds per day.
What I am seeing is seconds per minute.
A repeating counter set to 1000 milliseconds should count seconds
wi
This seems to work much better. Where will I find it documented?
_
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cory
Sharp
Sent: Wednesday, January 03, 2007 7:53 PM
To: Michael Newman
Cc: tinyos-help@millennium.berkeley.edu
Subject: Re: [Tinyos-help] Time counting
Trea
It is documented
1) In the TinyOS 1.x Timer interface nesdoc
2) In the TinyOS 2.x Timer interface nesdoc
3) In TEP 102 Timers
4) In this tinyos-help mailing list
One major omission seems to be in the tutorials.
Cory
On 1/3/07, Michael Newman <[EMAIL PROTECTED]> wrote:
This seems to work muc
I was definitely led astray by the introductory material and the tutorials.
They all talk about milliseconds and provide examples such as Blink where
1000 milliseconds is used as a timer argument and is described as a 1 second
interval.
>From the blink code and readme:
Blink is a basic applica
On Jan 3, 2007, at 6:43 PM, Michael Newman wrote:
I was definitely led astray by the introductory material and the
tutorials. They all talk about milliseconds and provide examples
such as Blink where 1000 milliseconds is used as a timer argument
and is described as a 1 second interval.
Fr
I am a beginner in TinyOS (version 1.1.15). I hope someone would help me
answer the following questions. I am sorry for the long email.
1) We have some micaZ motes. With the default makefile of TinyOS (say for the
Blink apps), I couldn't "make micaz". So, I replaced the original TinyOS
m
On 1/3/07, Michael Newman <[EMAIL PROTECTED]> wrote:
command result_t StdControl.start() {
// Start a repeating timer that fires every 1000ms
return call Timer.start(TIMER_REPEAT, 1000);
}
It does fire every 1000ms. Every 1000 binary milliseconds to be precise.
RTM:
http://tiny
24 matches
Mail list logo
