I am using tinyOS 1.x. I have seen that blip and tymo are implemented with
tinyOS 2.0.
> Date: Thu, 23 Jul 2009 07:54:01 -0700
> Subject: Re: [Tinyos-help] How to send a msg from the base to other motes
> using the route library
> From: gnaw...@usc.edu
> To: aparicioso...@hotmail.com
> CC: tin
>From header file
---
typedef nx_struct SensorMessage1 {
nx_int32_t reading1;
nx_int32_t reading2;
nx_int32_t reading3;
nx_int32_t reading4;
nx_int32_t reading5;
} SensorMessage1_t;
Hi All,
In the contrib cvs you can find an initial release of the msp430X support
for tinyos. (
http://tinyos.cvs.sourceforge.net/viewvc/tinyos/tinyos-2.x-contrib/dexma/tos/chips/msp430X/
).
The main diferences between the msp430 (msp430F1611) an msp430X
(msp430F2617) are related to the USCI modu
Hi,
The variable out should be a pointer. Hence
Instead of
SensorMessage1_t out;
Use
SensorMessage1_t* out;
best regards,
Faisal Aslam
himanshu barve wrote:
> From header file
> ---
> typedef nx_struct SensorMessag
Hi,
I'm tryng to connect PCF8563 real time clock to Iris using I2C.
http://www.datasheetcatalog.com/datasheets_pdf/P/C/F/8/PCF8563.shtml
I'm not sure how to read and write time values.
Here is a tutorial how to do it with bus pirate:
http://hackaday.com/2009/06/26/parts-i2c-real-time-clock-cale
Hello All,
I have been reading through the mailing list and relative papers on
multi-hop routing in TinyOS and I am hoping someone can suggest a good and
simple implementation. I am using tinyos-2.x with mica2 motes and the
options for routing aren't always applicable to both 2.x and mica2. This is
I will say use tinyOS implementation of Dymo routing
(http://docs.tinyos.net/index.php/Tymo). They called it Tymo.
Dymo is modified form of AODV. They remove the routes after sometimes if
it is not used and there is some timeout for each route maintained.
However, you could modify it to fulfill y
Hi Faisal,
Thanks for the suggestion. I had tried briefly to install Dymo before but
found I was missing some key wirings, among other problems. Do you know if
there is an available code example that works (along with .h, config and
implementation files)?
Also, right now all 20 motes can talk to e
I have the same problem. I have followed the instructions in the tutorial,
but the result is exactly the same.
I don't know what possibly goes wrong! :S
Any one (except us) had the same problem?
Cumps,
--
Ricardo
___
Tinyos-help mailing list
Tinyos-hel
Andres,
I2CPacket.read and I2CPacket.write are split phase operations. You
have to wait for the corresponding readDone or writeDone events before
issuing the next read or write, otherwise the subsequent operations
may fail.
Janos
On Wed, Jul 29, 2009 at 7:22 AM, Andres Vahter wrote:
> Hi,
> I'm
On Jul 29, 2009, at 8:31 AM, Ricardo . wrote:
> I have the same problem. I have followed the instructions in the
> tutorial, but the result is exactly the same.
> I don't know what possibly goes wrong! :S
>
> Any one (except us) had the same problem?
What version of TinyOS are you using? 2.1.0
I have not used Tymo myself. I hope someone else in the list could help you.
best regards,
Faisal Aslam
Ellen Shlossberg wrote:
> Hi Faisal,
>
> Thanks for the suggestion. I had tried briefly to install Dymo before
> but found I was missing some key wirings, among other problems. Do you
> know
On Jul 29, 2009, at 7:10 AM, Ellen Shlossberg wrote:
> Hello All,
>
> I have been reading through the mailing list and relative papers on
> multi-hop routing in TinyOS and I am hoping someone can suggest a
> good and simple implementation. I am using tinyos-2.x with mica2
> motes and the op
Thank you for all the advice. I am using the modified Collection protocol
from the tutorial. I'm still not sure of how it gathers a tree from the
program, but I used the Listen function and found that each packet received
at the root will include the id of a mote it has found since being turned
on.
On Wed, Jul 29, 2009 at 2:53 PM, Ellen Shlossberg wrote:
> Thank you for all the advice. I am using the modified Collection protocol
> from the tutorial. I'm still not sure of how it gathers a tree from the
> program, but I used the Listen function and found that each packet received
> at the root
On Tue, Jul 28, 2009 at 12:10 AM, sofia
aparicio wrote:
>
> Hello,
>
> I have a problem with Route library in tinyos1.x. I am using 2 motes and 1
> base station.
> If I put this 2 motes close to the base station then I receive the
> information from both motes. But if I put mote 2 out of the radio
Hi，
I am recently doing some test using Moteview2.0, the programme has went
through the TinyViz and serialforward, it works fine and got the result
suppose to be.
But when I follow the steps described in the mannual of moteview,I only saw
the server message: [MV]:unknown packet:
0x0a011a0
Hi All,
I am wondering if someone happen to have the old nesc compiler (meant for
TinyOs-1.x) which is :
nesc-1.1-1.i386.rpm...
I need to have this rpm for a new installation of TinyOS-1.x in the Linux
machine (Fedora).
I have searched all over the web esp at the
http://webs.cs.berkeley.edu/t
On Mon, Jul 27, 2009 at 5:45 AM, bharat naik wrote:
> Hi,
>
> Could someone tell me what is the purpose of the piece of code at the
> start of selectRoute() in MultiHopLEPSM.nc i.e when it tries to seed the
> network. I tried writing an alternate selectRoute() without this part and
> the code
19 matches
Mail list logo
