[Tinyos-help] IPv6 and serialforwarder/TinyOS

[Mansour, Mostafa]

Hi,

I want to connect a sensor to an IPv6 host. I thought there is an IPv6
version of serialforwarder, but I was unable to find it. Could anyone
please send me a link to the IPv6 open source serialforwarder?

 

Also, is there any other method that I can use to connect sensors to
IPv6 hosts beside the serialforwarder.

 

Thank you,

Mostafa

 

 

 

 

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] backoff & CSMA

[Jeong Kwanhee]

Hello all!!

 

I want to increase about throughput in micaz's surge application.

So, I'm currently doing to remove backoff and ack.

However, I don't know how to disable backoff. (I found how to disable ack.)

 

I think that I have to use CC2420Radio or CC2420Control. Is right? I can't
find and do this.

Give me a hint. 

 

My experiment is using micaz, tinyos 1.x.x.

 

Regards.

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] RE: BlackBook File System, BFileWrite interface

[David Moss]

Hi Mayur -

 

You're right - that is pretty inconsistent.  I think it's left over from one
of the first implementations of Blackbook on TinyOS 1.x, and I forgot to
update the interface's comments.

 

There is a major design issue with allowing the event to give you back the
filename, which is why it was removed.  The issue is the filename is never
stored anywhere in Blackbook except on non-volatile memory.  The first thing
Blackbook does when you pass in a filename is it converts the filename to a
CRC and uses the CRC as a hash to refer to the filename.  The actual
filename itself is written directly to flash one time, and forgotten about
until you absolutely want to know what it is.

 

Having the ability to recall the filename from an event requires one of
three things to happen:

 

1.  Each operation that signals an event that supplies the filename must
do a read from flash to determine what the filename was.  This is not
optimal because each flash interaction costs lots of time and energy.
2.  Each operation that signals an event that supplies the filename must
maintain the filename in RAM. This is not optimal for some applications that
are limited on RAM.
3.  The external application layer must supply Blackbook with a filename
to open; therefore, the application layer knows what the filename should be
at some point.  By forcing the application layer of an application to store
the filename in RAM, it prevents all applications that use Blackbook from
paying a filename penalty when they don't need that functionality.

 

Each particular instantiated interface into Blackbook should be able to
handle only one open file at a time, so if you're dealing with multiple open
files you'll also be dealing with multiple copies of interfaces into
Blackbook.  Therefore, at the time you call BFileWhatever.open(.) you could
also store the filename into your own application's "openFileName" buffer
for that particular interface. Btw, BlackbookUtil.filenameCpy(..) is an easy
method to copy a char * filename into a given filename_t buffer.

 

Hope that explains some details.  I need to go fix those comments, thanks
for pointing them out.

-David

 

 

 

  _  

From: Mayur Maheshwari [mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 19, 2007 1:50 PM
To: tinyos-help@millennium.berkeley.edu; David Moss
Cc: Suvesh Malhotra
Subject: BlackBook File System, BFileWrite interface

 

Hi David

 

I had a chance to test the BBFS on my telosb mote running TOS2 and I ran a
small app to use BFileWrite and BFileRead interfaces and they worked as
expected. 

 

However, while bulding up an advanced application I required to know the
name of the file whenever I opened one (with BFileWrite or BFileRead) and I
found that the comments and the actual implementation are inconsistent. 

 

For eg. in the interface BFileWrite
http://tinyos.cvs.sourceforge.net/tinyos/tinyos-2.x-contrib/rincon/tos/lib/b
lackbook/interfaces/BFileWrite.nc?view=markup  starting line 94:


 / * Signaled when a file has been opened, with the errors
   * @param fileName - the name of the opened write file 
   * @param len - The total reserved length of the file
   * @param error - SUCCSES if the file was opened successfully
   */
  event void opened(uint32_t len, error_t error);
 
The parameter fileName is absent from the event implementation. For
cross-checking I saw the BFileWriteP.nc in
\opt\tinyos-2.x-contrib\rincon\tos\lib\blackbook\core and found that the
fileName is not present in the actual implementation too. The same situation
is present with the events like appended, saved, closed. 

 

Is it possible to include the fileName parameter when these events signal.
This would enable us to handle multiple opened files.egards

 

Regards
-- 
Mayur Maheshwari([EMAIL PROTECTED])

"Karmanye Vadhikaraste Ma Phaleshu Kadachana,
Ma Karma Phala Hetur Bhurmatey Sangostva Akarmani" 

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] BlackBook File System, BFileWrite interface

[Mayur Maheshwari]

Hi David

I had a chance to test the BBFS on my telosb mote running TOS2 and I ran a
small app to use BFileWrite and BFileRead interfaces and they worked as
expected.

However, while bulding up an advanced application I required to know the
name of the file whenever I opened one (with BFileWrite or BFileRead) and I
found that the comments and the actual implementation are inconsistent.

For eg. in the interface BFileWrite
http://tinyos.cvs.sourceforge.net/tinyos/tinyos-2.x-contrib/rincon/tos/lib/blackbook/interfaces/BFileWrite.nc?view=markup
starting
line 94:

/ * Signaled when a file has been opened, with the errors
  * @param fileName - the name of the opened write file
  * @param len - The total reserved length of the file
  * @param error - SUCCSES if the file was opened successfully
  */
 event void opened(uint32_t len, error_t error);

The parameter fileName is absent from the event implementation. For
cross-checking I saw the BFileWriteP.nc in \opt\tinyos-
2.x-contrib\rincon\tos\lib\blackbook\core and found that the fileName is not
present in the actual implementation too. The same situation is present with
the events like appended, saved, closed.

Is it possible to include the fileName parameter when these events signal.
This would enable us to handle multiple opened files.egards

Regards
--
Mayur Maheshwari([EMAIL PROTECTED])

"Karmanye Vadhikaraste Ma Phaleshu Kadachana,
Ma Karma Phala Hetur Bhurmatey Sangostva Akarmani"
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Re: CC2420 micaz real data rate?different from MIB manual

[Michael Schippling]

My much referenced but never replicated report is at:
http://www.etantdonnes.com/Motes/report_micaz/

I thought I was thinking clearly when I did it, but cannot
recover the process without re-reading it every time...
There is a major non-clarity: The 66 message number
refers to a call and response message pair, so the
total on the air is 2x or 132 messages/sec.

There are around 35 bytes (probably more...) per message,
so that puts us in the 45000 bits/sec range.

I now suspect that my test was limited by the serial UART
bandwidth, so the micaz results should not be taken at
face value. I did however find that a 10ms pause between
message cycles greatly reduced the dropped message rate
and 20ms eliminated drops altogether...in my test situation.

This was all done with two Z's, one base and one re-mote,
so CDMA effects couldn't be evaluated.

MS


Munaretto, Daniele wrote:

Hi all,

I was wondering if someone of u has some experience on the real MicaZ data rate.

The MIB manual says 250Kbit/s as MAX data rate, but it will mean that if u have 
a packet of 127 bytes to transmit, your transmission time is around 4 ms.
However I feel the transmission time has to be quite larger than this one, 
because I get a lot of collisions in my experiments, that can be explained with 
a transmission time greater than ~20 ms per packet(127 bytes).

In the mailing list I saw about mica2 experiments, where the real data rate is 25 messages of 29 bytes (or 36 bytes with header and CRC?) per second, which means ~725 bytes per second, so 5.66 Kbit/s. While in the MIB manual is 38.4 Kbit/s. 


While for MicaZ I found in the mailing list by Michael Schippling:

'..
Without ACKs, in a point-to-point mode, under ideal conditions where there 
is little chance of transmit overlap and CSMA backoff, successful messages 
are around 66 per second with almost no failures.

..'

Does it mean 66 messages of 29 bytes of payload? In a scheme with broadcast is 
it still valid?
 


Any suggestion, explanation and help will be really appreciated!
Thank u very much
Cheers

 

 
Daniele Munaretto

Researcher
 
DoCoMo Communications Laboratories Europe GmbH

Landsbergerstraße 312  80687 Munich  Germany
 
Mobile  :   +49- 162-  2919-218

Office   :   +49-  89- 56824-218
Fax  :   +49-  89- 56824-300
 
[EMAIL PROTECTED]
visit us in http://www.docomolab-euro.com 
 
Managing Directors (Geschäftsführer): 
Dr. Toru Otsu, Dr. Narumi Umeda, Kazushige Yoshida

Amtsgericht München, HRB 132967

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Fw: configuring PW pins as both input and output pins

[Michael Schippling]

Search back on this list for "TOSH_ASSIGN_PIN schip"
( http://www.moteiv.com/community/TinyOS_Information is a good start)
and you will find many of my deathless posts on the use of DIO with TOS1.x
Specifically these two:
https://mail.millennium.berkeley.edu/pipermail/tinyos-help/2006-November/020879.html
https://mail.millennium.berkeley.edu/pipermail/tinyos-help/2006-January/014114.html

I don't know what you mean by 'not sampling', but there is no
automagic way to connect inputs to radio. For the most part you
want to set up some kind of timer driven code to read the port,
make a message, and post it to the radio send(). The OscilloscopeRF
demo app is a good model for this.

MS

Dipti wrote:

Hi all,
 
I am trying to implement an application in which a mica2 mote receives 
digital data on pins PW0-PW3 and forwards the same on the RF link.

I have a few doubts regarding the application.
 
1> Is it possible to configure pin nos PW0-PW3 as input pins and the 
pins PW4-PW7 as the output pins.
 (I have already set the same in the hardware.h file located under 
\platform\mica2) but will this enable me to use a set of

PW pins as input and another set as output in the same application.
 
2> I dont want to sample the incoming digital data but want to forward 
the same continuously on the RF. Is it possible to do the same?
 
3> The data coming on PW0-PW3 pins has to be sent to RF. How do i read 
PW0-PW3 pins continuosly.
 
Kindly help,

Regards
Dipti




___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] UART ReceiveMsg

[Michael Schippling]

I think the sync bytes are covered in the octavetech doc.
Each message is preceeded and succeeded (bracketed) by a
0x7E byte so the receiving code can figure out where it
is in the stream. All other 7E's in the message are
"escaped", which at least triples the complicatedness
of the system. But it seems to work.

If you are sending a raw stream out of the PC without
benefit of any TOS code (like Packetizer.java) you need
to add the 7E's, or not delete them.

MS

Inderjit Singh wrote:
Thanks for the suggestions lad. Very appreciated. Most of them I have 
already thought of. The code was only written to test that the 
communication is working. That's it. But It's good to be confirmed on 
the issue. Thanks.


However, Michael, what do you mean by "you need to leave the 7E's alone 
as well" ? I don't understand. And what is this "bracketed with the sync 
byte"? Could you give an example please?


Inderjit


On 4/18/07, *Michael Schippling* < [EMAIL PROTECTED] 
> wrote:


I think you need to leave the 7E's alone as well.
If it's going to GenericComm, the full message
should be bracketed with the sync bytes. If that
doesn't work it may be due to having to swap a
source address or something...

Structure alignment shouldn't be a problem if you
are dealing with a char array that was structured
correctly to start with. You might check that your
pc serial driver is not trying to "help" by adding
line-feeds or something...it should be raw I/O.

Hopefully you've seen the octavetech doc:

http://www.octavetech.com/pubs/TB5-01%20Deciphering%20TinyOS%20Serial%20Packets.pdf



MS

Inderjit Singh wrote:
>  Thanks Ben,
>
>  I tried something very simple:
>
>  1. I get the byte stream from usb sent from the TMote like:
>   7e 42 xx xx xx xx 7e
>
>  2. I remove the 7e from the stream and send it back as it is (42 xx xx
>  xx xx). But I still don't get it. C/C++ should be able to handle this
>  no?
>
>  Is there any doc on how the serial communication should be
>  established. I have gone through the java code for sending but still
>  it would help with a doc.
>
>  Indy
>
>
>  On 4/11/07, Ben Buckner < [EMAIL PROTECTED]
> wrote:
> > > Hi,
> > >
> > > I have trouble sending msg from laptop (using c++) code to tmote.
> > All the
> > > code is at the bottom. I have no problem reading the data from the
> > serial
> > > but sending it back dooesn't seam to work. Anyone knows why?
Thanks.
> > >
> > > Indy
> > [...]
> > > memcpy(output_buffer, &msgOUT, sizeof(msgOUT));
> >
> > Out of the dozens of things that could be wrong, it might be worth
> > pointing
> > out that C does not guarantee that structures can be serialized by
> > copying
> > bytewise out of memory like that. It can work, but you never
know. The
> > most
> > usual reason why that would fail is if the compiler tries to
align the
> > members of the structure and inserts padding (which it almost
always does
> > with odd-sized byte fields). At any rate, it would be a good idea
to make
> > sure that the code really generates the byte stream that you
think it's
> > generating.
> >
> > Ben B.
> >
> >
> >
> > ___
> > Tinyos-help mailing list
> > Tinyos-help@Millennium.Berkeley.EDU

> >
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> >
>  ___
>  Tinyos-help mailing list
>  Tinyos-help@Millennium.Berkeley.EDU

>
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help






___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] transmission using cricket problem

[Abhishek Trivedi]

Hello All,

I have a problem with the crossbow cricket. I am able to use it as 
beacon,listener and receiver but the transmission through it is not working. 
The transmit function is like this..



event result_t RadioSend.sendDone(TOS_MsgPtr data, result_t success) {
   //if(CricketConfig.run_mode != MODE_RADIO) {
   // call RadioControl.stop();
call Leds.yellowToggle();
//}


return success;
 }
task void datatrans()
{
CricketRadioSend * message = (CricketRadioSend *) pTxBuffer->data;

call BeaconsControl.stop();
CricketConfig.run_mode = MODE_RADIO;
TOSH_SET_US_IN_EN_PIN();
TOSH_CLR_BAT_MON_PIN();
TOSH_uwait(500);
TOSH_CLR_US_IN_EN_PIN();
TOSH_SET_BAT_MON_PIN();
call RadioControl.start();
call BeaconTimer.stop();


atomic {
pTxBuffer->length = 4;
message->buffer[0] = '9';
message->buffer[1] = d1;
message->buffer[2] = t1;
   }


call RadioSend.send(&mTxBuffer);
call Leds.greenToggle();
}

d1 & t1 are one byte character and integer data. ptxbuffer is pointer to the 
buffer.


Similar code is working for mica2.

I don't know if i am missing something or am i doing something wrong.

if someone can help me on this or provide some code snippet for transmission 
through cricket.


Thanx nd regards
abhishek



Abhishek

ARRI

_
MSN is giving away a trip to Vegas to see Elton John.  Enter to win today. 
http://msnconcertcontest.com?icid-nceltontagline


___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Micaz TOS_DATA_LENGTH change

[Benjamin Madore]

On Thu, April 19, 2007 5:41 am, Alan Medlar said:
> If my understanding of what you are doing is correct and you want to send
> packets of length TOSH_DATA_LENGTH, then the actual call to 'send' has to
> falsely state that the length of the packet payload is TOSH_DATA_LENGTH.
> (eg: call Send.send(ADDRESS, TOSH_DATA_LENGTH, &buf)  as opposed to  call
> Send.send(ADDRESS, sizeof(type_in_payload_t), &buf)  )
>
> Just setting the variable somewhere simply sets the maximum that a packet
> can be, (ie: to save ram if you have a pool of statically allocated TOS_Msg
> structs).
>
> Changing the value is AM.h will have no more effect than setting it in a
> Makefile as the definition of this is " #ifndef ".
>
>
> Alan
>
>> Hi all,
>>
>> I am using micaz fro my application and the default size of TOS_Msg
>> structure is 36byte(?).
>>
>> In order to change the massage packet size, I added
>>
>> CFLAGS += -DTOSH_DATA_LENGTH=64
>>
>> to Makelocal
>>
>> After that, I want to know actually whether its size is 64 or not.
>>
>> I used tiniViz.
>>
>> When I debug using tiniViz, I can see '[4] Sent Message 
>> [addr  ] and so on.
>>
>> However, Length is always expressed 0xc.
>>
0xC would be hexadecimal. The prefix 0x is used in many languages to
identify that. It would be 13 in decimal. It also was probably expressed
0x0C, since that would cover the full 8-bit value, if you meant 0xC0 it
would be 192. Each hex number only covers 4 bits, and it is common to group
them in pairs to prevent confusion, even if one digit is zero.

See: http://www.onlineconversion.com/base.htm

Also: 64 is 0x40.

-Ben M
-- 
The difference between the right word and the almost right word is really a
large matter- it's the difference between a lightning bug and the lightning.
-Twain

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Simple question on Timer

[Philip Levis]

On Apr 19, 2007, at 7:37 AM, Steve McKown wrote:


H

In case you're wondering why it's set up this way: converting  
between powers
of 2 needs only fast bit shifts.  Far more efficient than, say,  
dividing by

1000.



Actually, the reason has more to do with error and the effort/cost it  
would take to handle it. If you want 1kHz rather than 1.024kHz units,  
then you need to convert. Here's a modified version of a post I sent  
to the EmStar list a while back, when someone suggested just doing  
this ((timer * 1024) / 1000):


The issue is whether you want precise 1024Hz timers or imprecise  
1000Hz timers. You can get reasonably precise 1000Hz timers, but only  
if you are willing to do a bit of bookkeeping to keep track of  
partial ticks.


E.g., imagine a user specifies a 999ms timer. The closest thing in  
1024Hz (the underlying clock) is 1023 ticks. So your timer starts  
firing every 1023/1024 ticks. Now imagine another component asks for  
a 111ms timer. The closest thing is 114 ticks. But 114 * 9 = 1026;  
the two timers will slowly move out of phase, although 999 mod 111 = 0.


Now imagine a frequency hopping scheme that (for some reason...) has  
a period of 999ms and breaks it up into 9 slots of 111ms. A node that  
is active for all slots and so fires a periodic timer every 111 ms  
will have time progress differently than a node which is wake for one  
slot and fires a timer every 999ms. Even if you could calibrate the  
crystals and figure out the temperature-to-skew function (poster on  
this at SenSys this year), you still have timer shifts that are  
*dependent on the values you pass to the timer* rather than the nodes  
themselves.


You can get rid of these imprecisions by tabulating the fact that  
111ms is actually 123.64 ticks, and so keep track of partial ticks.  
But for the complex cases, I would expect that this is enough cycles  
that it slows down your maximum timer firing rate. And any tiny  
errors will creep over time.


Besides interoperability with devices that operate with true  
millisecond granularity, it's not clear to me what the benefit of  
having a interval-1000 timer is, besides the comfort of thinking in  
decimal rather than binary.


Phil

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Tmote Invent Potentiometer

[Andrew Redfern]

Hi Jon,

Take a look at the PhotoDriver component located in
$MOTEIV_DIR/tos/sensorboards/invent/.

Andrew

On 4/18/07, Jon <[EMAIL PROTECTED]> wrote:


The photo potentiometer.

On 4/19/07, Andrew Redfern <[EMAIL PROTECTED]> wrote:
> Hi Jon,
>
> What potentiometer are you trying to set?
>
> Andrew
>
>
> On 4/18/07, Jon <[EMAIL PROTECTED] > wrote:
> >
> > How do I set the potentiometer of a Tmote Invent?  I am very new to
> > this programming language (and event programming in general); so I
> > have had quite a few snags.  I've looked at several examples, but none
> > have seemed to work on the Tmote Invent.  I've looked at several
> > online resources, but none have seemed to even mention setting the
> > potentiometer of any mote in general.
> > ___
> > Tinyos-help mailing list
> > Tinyos-help@Millennium.Berkeley.EDU
> >
>
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> >
>
>

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Complete Novice Question: Installing TinyOS and Compiling on MacOSX 10.4 for MICA

[Greg Turnipseed]

Yes, I have avr-objcopy and avr-gcc installed.  They¹re located in the
/usr/local/bin directory.
TOSDIR=/Users/greg/Documents/Sources/tinyos-1.x/tos
TOSROOT=/users/greg/Documents/Sources/tinyos-1.x

These are correct, as far as I can tell.  Inside the TOSDIR path are the
folders ³interfaces²,²lib²,²platform²,²sensorboards²,²system², and ³types².
TOSROOT just points to my tinyos directory, like yours does.

MIB520=/dev/tty.usbserial-XBPSJ9TXA
MOTECOM=/dev/tty.usbserial-XBPSJ9TXB

I¹m using the USB version (MIB520), and so I think that part¹s correct.
It¹s just supposed to point to where the serial port is, correct?  What
about MOTECOM?

What does this mean as far as not being able to find ³Timer²,²Leds², etc.?

Thanks,
Greg Turnipseed

From: Sarfraz Nawaz <[EMAIL PROTECTED]>
Date: Tue, 17 Apr 2007 11:21:01 +1000
To: Michael Schippling <[EMAIL PROTECTED]>
Cc: Greg Turnipseed <[EMAIL PROTECTED]>, tinyos-help

Subject: ***SPAM*** Re: [Tinyos-help] Complete Novice Question: Installing
TinyOS and Compiling on MacOSX 10.4 for MICA

Greg,

avr-objcopy is a part of avr-binutils. Did you install the avr-binutils and
avr-gcc? If yes, can you find out where it lives in your filesystem. You
should also carefully check your environment variables and see if they are
setup properly and are pointing to correct places.


On 4/17/07, Michael Schippling <[EMAIL PROTECTED]> wrote:
> now it's gettin weird again...
> those interface defs are in tos/interfaces
> 
> Perhaps you do not have the pointers to the tos code setup correctly.
> I have these two env vars:
> 
> TOSDIR=/cygdrive/C/cygwin/opt/tinyos- 1.1.7/tos
> TOSROOT=C:/cygwin/opt/tinyos-1.1.7
> 
> At least one is the result of cygwin trying to help us poor Widows
> abusers by imitating (sort of almost kinda) the UNIX file structure.
> Perhaps both should be set to point to your installation...
> 
> And just to be forward looking I have these two vars for downloading
> and talking to the MIB510 that I use. I don't know what you will use
> for downloading, but it'll probably be another struggle:
> 
> MIB510=COM3
> [EMAIL PROTECTED]:mica2
> 
> 
> MS
> 
> Greg Turnipseed wrote:
>> > It started with me trying to use "make mica", and it gives me the error
>> that
>> > there's no rule to make target 'mica.'  This, along with a host of other
>> > errors (including not being able to correctly read the Makerules file in
>> > tinyos-1.x/apps), led me to find another way of compiling the code.  After
>> > browsing the Internet for hours, I learned the ncc command.  Then that had
>> > its own problems, and I ended up needing to reinstall nescc (and thanks to
>> > you guys' help), change ncc to point to the right place.  Now I'm able to
>> > make ncc work...kind of.  I can see that it's calling nescc, but now
>> nescc's 
>> > having problems.  You were right (I think) about the board.  I changed it
>> to
>> > micaz, and now it gives me compilation errors.  Lots of complaining about
>> > undeclared variables and such, but the most troublesome things are as
>> > follows:
>> >
>> > Blink.nc:44  : cannot find `StdControl'
>> > Blink.nc:45  : cannot find `Timer'
>> > Blink.nc:46  : cannot find `Leds'
>> >
>> > Since the latter two are built-in functions, I wonder if I'm supposed to
>> > have compiled something else before running ncc?
>> >
>> > Thanks again.
>> > -Greg Turnipseed
>> >
>> >
>>> >> From: Michael Schippling <[EMAIL PROTECTED]>
>>> >> Date: Mon, 16 Apr 2007 13:48:35 -0600
>>> >> To: Greg Turnipseed < [EMAIL PROTECTED]>
>>> >> Cc: Sarfraz Nawaz <[EMAIL PROTECTED]>, tinyos-help
>>> >> < tinyos-help@Millennium.Berkeley.EDU>
>>> >> Subject: Re: [Tinyos-help] Complete Novice Question: Installing TinyOS
>>> and
>>> >> Compiling on MacOSX 10.4 for MICA
>>> >>
>>> >> hmm...I'll bet ya a dollar you don't have a "mica" board...
>>> >> So you want probably mica2 or micaz as in "make mica2".
>>> >>
>>> >> But: Yay! you are getting someplace. Why it was trying to exec
>>> >> stuff in (I assume) your own directory tree is a mystery that
>>> >> may re-bite you someplace else. But: Onward.
>>> >>
>>> >> In general ncc will put the results in build/[platform]
>>> >> so your main.exe ought to be there with app.c (which is the
>>> >> nescc 'preprocessor' output -- all the TOS and app source
>>> >> munged together in one file to be compiled to object code).
>>> >>
>>> >> What you want finally is the .srec file to be downloaded to
>>> >> the micaX card. There is another step in-between that puts
>>> >> the moteID into the .srec...all of these things _should_
>>> >> be executed from the makefile in the right order. I think
>>> >> that's where this all started though, right?
>>> >>
>>> >> MS
>>> >>

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Regarding Surge application

[vinay murthy]

Hi ankur it comes with Mutihop enabled.
   
  cheers,vinay.

ankur jain <[EMAIL PROTECTED]> wrote:
Hi all,
I want to know whether the Surge applications that lies within 
contrib/xbow/apps folder comes with multi-hop routing enabled or disabled by 
default.Since in the apps config. files ,the lines corresponding to multi-hop  
routing are commented in my case. I am sending you the config. file below for 
your reference. Also let me know that if it really means that multi-hop routing 
would become enabled if i uncomment those lines.
  Please help me out as i am really stuck up with it.
includes Surge;
  includes SurgeCmd;
  includes MultiHop;
   
  configuration Surge {
  }
  implementation {
  components Main, SurgeM, TimerC, LedsC, NoLeds, Photo, RandomLFSR,
  GenericCommPromiscuous as Comm, Bcast, MultiHopRouter as multihopM, 
QueuedSend, Sounder;
  Main.StdControl -> SurgeM.StdControl;
  Main.StdControl -> Photo;
  Main.StdControl -> Bcast.StdControl;
  Main.StdControl -> multihopM.StdControl;
  Main.StdControl -> QueuedSend.StdControl;
  Main.StdControl -> TimerC;
  Main.StdControl -> Comm;
  // multihopM.CommControl -> Comm; 
  SurgeM.ADC -> Photo;
  SurgeM.Timer -> TimerC.Timer[unique("Timer")];
  SurgeM.Leds -> LedsC; // NoLeds;
  SurgeM.Sounder -> Sounder;
  SurgeM.Bcast -> Bcast.Receive[AM_SURGECMDMSG];
  Bcast.ReceiveMsg[AM_SURGECMDMSG] -> Comm.ReceiveMsg[AM_SURGECMDMSG];
  SurgeM.RouteControl -> multihopM;
  SurgeM.Send -> multihopM.Send[AM_SURGEMSG];
  multihopM.ReceiveMsg[AM_SURGEMSG] -> Comm.ReceiveMsg[AM_SURGEMSG];
  //multihopM.ReceiveMsg[AM_MULTIHOPMSG] -> Comm.ReceiveMsg[AM_MULTIHOPMSG];
  }
So what does these 2 commented lines really meant for if at all present
thanks 
Ankur jain

-
  Check out what you're missing if you're not on Yahoo! Messenger 
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

   
-
Ahhh...imagining that irresistible "new car" smell?
 Check outnew cars at Yahoo! Autos.___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] How to change TimerA to TimerB

[Firat TARAKTAS]

 
Hi Steve,

I am mailing you according to statement below (Timer components uses 
Timer A). Do you inform me about how to make Timer to use TimerB instead of 
Timer A. Thanks for your help.

Firat TARAKTAS


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve McKown
Sent: Thursday, April 19, 2007 5:37 PM
To: tinyos-help@Millennium.Berkeley.EDU
Subject: Re: [Tinyos-help] Simple question on Timer

Hi,

On Thursday 19 April 2007 05:53, Muhammad Azhar wrote:
> Hi all,
>    I apologise if this is a rather basic question, but to set a timer 
> to fire exactly 1s periodically (using Timer), do I input
> startPeriodic(1000) or startPeriodic(1024)?  'Coz all the while, I've 
> always used the former, but I realised that it's never 1 sec, always 
> faster than that.  A colleague told me that using 1024 would make the 
> timer fire every 1 sec, but didn't explain why.  Thus, I'd like to 
> clarify with you guys.  How exactly does the 1024 convert to 1s?  What 
> if I'd like a timer of 1min then? Many thanks for your help.

On the msp430 platforms, the millisecond virtual timer servicing Timer 
components uses Timer A.  Timer A is configured to use SMCLK, which is set to 
DCO/4.  The DCO is calibrated to 4*2^20 Hz, so Timer A's "1MHz" timer is in 
fact 2^20 Hz.  Because the conversion from microseconds to milliseconds in the 
timer code effectively uses a 10-bit shift, 1 second is 2^10 ticks, or 1024.  
So, 1024 ticks/sec * 60 secs/min = 61440 ticks/min.

In case you're wondering why it's set up this way: converting between powers of 
2 needs only fast bit shifts.  Far more efficient than, say, dividing by 1000.

Cheers,
Steve

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Microphone on a mts300 sensorboard - tone detector, raw data and Resource.request() problem (and workaround)

[Hugo Sousa]

Using: TinyOs 2.x (CVS updated), cygwin, crossbow micaz motes, mts300ca
sensorboard

The initial problem while using MicC to access the microphone tone detection
was that the microphone seemed to be always "detecting" the 4khz tone, even
if no tone was present. I tried reading the code "below" (MicP, MicDeviceP,
MicReadP, etc) and got to the conclusion that there was no (that I could
find) Resource.request() to access the mic tone detection, and that solved
part of the tone detection problem. The second issue is that it seems that
when a tone is detected, the interrupts aren't disabled like it says in
MicSetting, so a "call MicSetting.disable()" is needed inside the "async
event error_t MicSetting.toneDetected()" implementation.

After solving the tone detection I went to the raw data mode, it seemed to
work ok, but a little sluggish. Reading the code "below" ( MicC, MicReadP,
ArbitratedReadC), I saw that for each Read.read() a Resource.request() is
called, and after Read.readDone() a Resource.release() is also called. In my
motes the time from a Resource.request() to a .granted() is very high, 1
second wouldn't be an exageration (I would like to know your experiences on
this), so the solution was write my own module and configuration (similiar
to MicC, but not using MicReadP), wiring myModule.Read interface directly to
AdcReadClientC (check MicC.nc), and do not release() the resource after a
readDone().

I hope this helps someone, I've seen many mails with problems with the tone
detection, but I have some questions. Am I doing something unadvisable by
not using ArbitratedReadC (thus not releasing the resource)? Can the
resource be "stolen" by some other piece of code? Should I use MicStreamC
(haven't tried it yet) for periodic sound sampling? My interest is not the
actual sound it self, but whether or not there is noise.
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Regarding Surge application

[ankur jain]

Hi all,
I want to know whether the Surge applications that lies within 
contrib/xbow/apps folder comes with multi-hop routing enabled or disabled by 
default.Since in the apps config. files ,the lines corresponding to multi-hop  
routing are commented in my case. I am sending you the config. file below for 
your reference. Also let me know that if it really means that multi-hop routing 
would become enabled if i uncomment those lines.
  Please help me out as i am really stuck up with it.
includes Surge;
  includes SurgeCmd;
  includes MultiHop;
   
  configuration Surge {
  }
  implementation {
  components Main, SurgeM, TimerC, LedsC, NoLeds, Photo, RandomLFSR,
  GenericCommPromiscuous as Comm, Bcast, MultiHopRouter as multihopM, 
QueuedSend, Sounder;
  Main.StdControl -> SurgeM.StdControl;
  Main.StdControl -> Photo;
  Main.StdControl -> Bcast.StdControl;
  Main.StdControl -> multihopM.StdControl;
  Main.StdControl -> QueuedSend.StdControl;
  Main.StdControl -> TimerC;
  Main.StdControl -> Comm;
  // multihopM.CommControl -> Comm; 
  SurgeM.ADC -> Photo;
  SurgeM.Timer -> TimerC.Timer[unique("Timer")];
  SurgeM.Leds -> LedsC; // NoLeds;
  SurgeM.Sounder -> Sounder;
  SurgeM.Bcast -> Bcast.Receive[AM_SURGECMDMSG];
  Bcast.ReceiveMsg[AM_SURGECMDMSG] -> Comm.ReceiveMsg[AM_SURGECMDMSG];
  SurgeM.RouteControl -> multihopM;
  SurgeM.Send -> multihopM.Send[AM_SURGEMSG];
  multihopM.ReceiveMsg[AM_SURGEMSG] -> Comm.ReceiveMsg[AM_SURGEMSG];
  //multihopM.ReceiveMsg[AM_MULTIHOPMSG] -> Comm.ReceiveMsg[AM_MULTIHOPMSG];
  }
So what does these 2 commented lines really meant for if at all present
thanks 
Ankur jain

   
-
 Check out what you're missing if you're not on Yahoo! Messenger ___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Surge application

[mehmet kaplan]

Hi all,
I searched mail archives, but i couldn't find anything. I am trying to load 
Surge application to a node in Sensenode TinyOS 1.15. But there is an error 
like "implicit declaration of function qsort" in MultiHopLEPSM. I couldn't 
solve the problem. I suppose it is so simple, but i'm beginner in TinyOS.
Thanks for your help.

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com ___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Simple question on Timer

[Urs Hunkeler]

Hi,

Usually a clock on a microcontroller is implemented by using a clock
crystal on an asynchronous counter. When the counter overflows (or
reaches 0) it generates an interrupt, which is then used to update the
clock. A typical frequency for such a crystal would be 32.768 kHz, which
is 2^15.

The obvious assumption would be that TinyOS sets the asynchronous
counter such that it generates an interrupt every 32 crystal cycles, or
in other words every 1/1024th of a second. This is quite close to, but
not exactly, 1ms. For this reason you'll have to specify 1024 to get a
1s timer. To get a 1min timer, it would be 60*1024 = 61440.

Cheers,
Urs


Muhammad Azhar schrieb:
> Hi all,
> 
>I apologise if this is a rather basic question, but to set a timer to fire 
> exactly 1s periodically (using Timer), do I input startPeriodic(1000) 
> or 
> startPeriodic(1024)?  'Coz all the while, I've always used the former, but I 
> realised that it's never 1 sec, always faster than that.  A colleague told me 
> that using 1024 would make the timer fire every 1 sec, but didn't explain 
> why.  
> Thus, I'd like to clarify with you guys.  How exactly does the 1024 convert 
> to 
> 1s?  What if I'd like a timer of 1min then?
> 
>Many thanks for your help.
> 
> Regards,
> Azhar
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] CC2420 micaz real data rate?different from MIB manual

[Munaretto, Daniele]

Hi all,

I was wondering if someone of u has some experience on the real MicaZ data rate.

The MIB manual says 250Kbit/s as MAX data rate, but it will mean that if u have 
a packet of 127 bytes to transmit, your transmission time is around 4 ms.
However I feel the transmission time has to be quite larger than this one, 
because I get a lot of collisions in my experiments, that can be explained with 
a transmission time greater than ~20 ms per packet(127 bytes).

In the mailing list I saw about mica2 experiments, where the real data rate is 
25 messages of 29 bytes (or 36 bytes with header and CRC?) per second, which 
means ~725 bytes per second, so 5.66 Kbit/s. While in the MIB manual is 38.4 
Kbit/s. 

While for MicaZ I found in the mailing list by Michael Schippling:

'..
Without ACKs, in a point-to-point mode, under ideal conditions where there 
is little chance of transmit overlap and CSMA backoff, successful messages 
are around 66 per second with almost no failures.
..'

Does it mean 66 messages of 29 bytes of payload? In a scheme with broadcast is 
it still valid?
 

Any suggestion, explanation and help will be really appreciated!
Thank u very much
Cheers

 

 
Daniele Munaretto
Researcher
 
DoCoMo Communications Laboratories Europe GmbH
Landsbergerstraße 312  80687 Munich  Germany
 
Mobile  :   +49- 162-  2919-218
Office   :   +49-  89- 56824-218
Fax  :   +49-  89- 56824-300
 
[EMAIL PROTECTED]
visit us in http://www.docomolab-euro.com 
 
Managing Directors (Geschäftsführer): 
Dr. Toru Otsu, Dr. Narumi Umeda, Kazushige Yoshida
Amtsgericht München, HRB 132967

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Simple question on Timer

[Steve McKown]

Hi,

On Thursday 19 April 2007 05:53, Muhammad Azhar wrote:
> Hi all,
>    I apologise if this is a rather basic question, but to set a timer to
> fire exactly 1s periodically (using Timer), do I input
> startPeriodic(1000) or startPeriodic(1024)?  'Coz all the while, I've
> always used the former, but I realised that it's never 1 sec, always faster
> than that.  A colleague told me that using 1024 would make the timer fire
> every 1 sec, but didn't explain why.  Thus, I'd like to clarify with you
> guys.  How exactly does the 1024 convert to 1s?  What if I'd like a timer
> of 1min then? Many thanks for your help.

On the msp430 platforms, the millisecond virtual timer servicing Timer 
components uses Timer A.  Timer A is configured to use SMCLK, which is set to 
DCO/4.  The DCO is calibrated to 4*2^20 Hz, so Timer A's "1MHz" timer is in 
fact 2^20 Hz.  Because the conversion from microseconds to milliseconds in 
the timer code effectively uses a 10-bit shift, 1 second is 2^10 ticks, or 
1024.  So, 1024 ticks/sec * 60 secs/min = 61440 ticks/min.

In case you're wondering why it's set up this way: converting between powers 
of 2 needs only fast bit shifts.  Far more efficient than, say, dividing by 
1000.

Cheers,
Steve

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] surge performance

[Hui KANG]

This is the link.
http://www.moteiv.com/community/Change_the_default_UART_baud_rate

On 4/19/2007, "Michael Schippling" <[EMAIL PROTECTED]> wrote:

>If the destination is the pc you may be limited by the serial port speed.
>There are some instructions for changing that speed, someplace...
>I probably have a link, but searching the list might find it.
>
>In my testing at:  http://www.etantdonnes.com/Motes/report_micaz/
>I may have made that same mistake, and got about the same results as you.
>
>MS
>
>
>Jeong Kwanhee wrote:
>> Hello all,
>>
>>
>>
>> Currently, I�m testing performance using micaz.
>>
>> I�m doing using surge program and I manipulated data size, pps(packet
>> per sec).
>>
>> I sent 190kbps from source to destination(1hop), but I gained only
>> 57kbps to destination.
>>
>> I don�t know why this happening is. I think micaz hardward specification
>> is appeared 250kbps.
>>
>>
>>
>> What am I doing about this happening??
>>
>> Anybody help me.
>>
>>
>> 
>>
>> ___
>> Tinyos-help mailing list
>> Tinyos-help@Millennium.Berkeley.EDU
>> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>___
>Tinyos-help mailing list
>Tinyos-help@Millennium.Berkeley.EDU
>https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] How do I only operate as the relay mote on Surge program?

[Jeong Kwanhee]

 

Hello all,

Currently, I do test multihop using the surge program by micaz..

Environment is this:

Computer ß base mote node 0  ß mote 1 ß mote2 ß mote3

Moreover, I’m trying to act only relay except source node(mote3) and mote 0.

Mote1 and mote2 act only to relay what it received child mote.

 

So, I modified my Surge application source.

[SurgeM.nc]

command result_t StdControl.start() {   

if( TOS_LOCAL_ADDRESS == 3 ){

   call Timer.start(TIMER_REPEAT, timer_rate);

}

return SUCCESS;

}

 

I made it send only mote 3.

The other motes received and relay to parent node.

(i.e. sensing mote is only mote 3)

 

However, it works not well. Is this method right?

If I am wrong, send me more good answer.

 

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] NetSync in Boomerang

[John Hendrie]

Hello,

I'm looking at NetSync in Boomerang and I can't see how NetWakeM is
actually used. Only NetSync wires to NetWake and NetSync doesn't
actually call any functions inside of NetWake. All functionality seems
to start at ReceiveMsg.receive() but from what I can see nothing
triggers a send in NetWake except a receive event. Am I missing
something?

-- John.
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Simple question on Timer

[Muhammad Azhar]

Hi all,
   I apologise if this is a rather basic question, but to set a timer to fire exactly 1s periodically (using Timer), do I input startPeriodic(1000) or startPeriodic(1024)?  'Coz all the while, I've always used the former, but I realised that it's never 1 sec, always faster than that.  A colleague told me that using 1024 would make the timer fire every 1 sec, but didn't explain why.  Thus, I'd like to clarify with you guys.  How exactly does the 1024 convert to 1s?  What if I'd like a timer of 1min then?
   Many thanks for your help.
Regards,Azhar

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Ubuntu & TinyOS & Existing AVR libs

[Anne van Rossum]

Of course, this problem is not Ubuntu specific. It exist on every system
where there is an existing AVR toolchain.

If there are no hardcoded dependencies, I can rename the folders and
file names in the following way:

  * dpkg-deb -x avr-binutils_2.15tinyos-4_i386.deb
avr-binutils-tinyos 
  * dpkg-deb -e avr-binutils_2.15tinyos-4_i386.deb
avr-binutils-tinyos/DEBIAN 
  * gedit avr-binutils-tinyos/DEBIAN/control  (to change
description) 
  * cd avr-binutils-tinyos 
  * mv avr avr-tinyos 
  * cd usr/bin 
  * for file in avr-*; do mv $file ${file/#avr-/avr-tinyos-}; done 
  * (don't do it twice: the match #avr-[!tinyos] does not work, so
can't prevent tinyos-tinyos rewritings in that case, to undo
use: for file in avr-*; do mv $file ${file/#avr-tinyos-/avr-};
done) 
  * cd usr/share/doc 
  * mv avr-binutils avr-tinyos-binutils 
  * cd usr/share/man/man1 
  * for file in avr-*; do mv $file ${file/#avr-/avr-tinyos-}; done 
  * cd avr-binutils-tinyos/ 
  * find . -name '*' -exec md5sum {} \; 2> /dev/null | grep -v
DEBIAN > DEBIAN/md5sums 
  * cd .. 
  * dpkg-deb -b avr-binutils-tinyos
avr-binutils_2.15atinyos-4_i386.deb

Quite a lot of work. And actually useless if I do not have the sources,
because it's quite certain that they refer to each other (and thus use
hardcoded file names).

http://forums.xandros.com/viewtopic.php?p=193397&sid=7cabaf9daef11d692e1678200897978d
http://staff.washington.edu/dittrich/misc/faqs/unix.rename.wildcard
http://www.nongnu.org/lpi-manuals/lpi-102/html/ch07s04.html#bashfor

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Install tinyos(Tmote Tools) on Linux

[Alexander Becher]

* [EMAIL PROTECTED]:
> I was wondering if anyone knows where I can get the file mspgcc-cvs.tar.gz
> 
> I have been trying to follow the installtion guide for installing tiny 
> OS (Tmote Tools) on Linux. I'm stuck at the bit where I have to install 
> MSP-GCC. There's a script in there that's meant to download and install 
> everything.
> 
> However the cvs doesn't work. So I tried to manually download all the 
> files I needed. I have found everything except mspgcc-cvs.tar.gz and I 
> am not sure where to find it. Has anyone had much success installing 
> Tmote Tools on Linux? If so, do they have this file in their folder:
> 
> /opt/tinyos-1.x/tools/src/mspgcc/archive/mspgcc-cvs.tar.gz?

I think you are following an outdated set of instructions.

Try a normal version of mspgcc, I think you do not need the CVS version.

Regards,
Alexander

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Fw: configuring PW pins as both input and output pins

[Dipti]

Hi all,

I am trying to implement an application in which a mica2 mote receives digital 
data on pins PW0-PW3 and forwards the same on the RF link. 
I have a few doubts regarding the application.

1> Is it possible to configure pin nos PW0-PW3 as input pins and the pins 
PW4-PW7 as the output pins.
 (I have already set the same in the hardware.h file located under 
\platform\mica2) but will this enable me to use a set of 
PW pins as input and another set as output in the same application.

2> I dont want to sample the incoming digital data but want to forward the same 
continuously on the RF. Is it possible to do the same?

3> The data coming on PW0-PW3 pins has to be sent to RF. How do i read PW0-PW3 
pins continuosly.

Kindly help,
Regards
Dipti ___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Has anyone installed on Linux? Please reply if you have

[Alan Medlar]

Could you be less vague? What file? What verion of tinyos? (or boomerang if
this is something to do with moteiv)?


On 19/04/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:


Hi,

I was just wondering if anyone has installed Moteiv's Tmote tools or
tinyos on linux. If so, please reply I need a file which I cannot find
on the cvs.

Regards

Keerthi


___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Micaz TOS_DATA_LENGTH change

[Alan Medlar]

If my understanding of what you are doing is correct and you want to send
packets of length TOSH_DATA_LENGTH, then the actual call to 'send' has to
falsely state that the length of the packet payload is TOSH_DATA_LENGTH.
(eg: call Send.send(ADDRESS, TOSH_DATA_LENGTH, &buf)  as opposed to  call
Send.send(ADDRESS, sizeof(type_in_payload_t), &buf)  )

Just setting the variable somewhere simply sets the maximum that a packet
can be, (ie: to save ram if you have a pool of statically allocated TOS_Msg
structs).

Changing the value is AM.h will have no more effect than setting it in a
Makefile as the definition of this is " #ifndef ".


Alan

On 19/04/07, Munaretto, Daniele <[EMAIL PROTECTED]> wrote:


 Try changing the length in the AM.h file. It should be fine.

Cheers

Daniele







*Daniele Munaretto*

Researcher

* *

*DoCoMo Communications Laboratories Europe GmbH*

Landsbergerstraße 312  80687 Munich  Germany



Mobile  :   +49- 162-  2919-218

Office   :   +49-  89- 56824-218

Fax  :   +49-  89- 56824-300



[EMAIL PROTECTED]

visit us in http://www.docomolab-euro.com



Managing Directors (Geschäftsführer):

Dr. Toru Otsu, Dr. Narumi Umeda, Kazushige Yoshida

Amtsgericht München, HRB 132967
   --

*From:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *Jeong Kwanhee
*Sent:* Wednesday, April 18, 2007 1:06 PM
*To:* tinyos-help@Millennium.Berkeley.EDU
*Subject:* [Tinyos-help] Micaz TOS_DATA_LENGTH change



Hi all,

I am using micaz fro my application and the default size of TOS_Msg
structure is 36byte(?).

In order to change the massage packet size, I added

CFLAGS += -DTOSH_DATA_LENGTH=64

to Makelocal

After that, I want to know actually whether its size is 64 or not.

I used tiniViz.

When I debug using tiniViz, I can see '[4] Sent Message 
[addr  ] and so on.

However, Length is always expressed 0xc.



I used surge application for multihop routing.

Help me



This method is right??



___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] surge performance

[Alan Medlar]

The radio hardware can send at 250kb/s and indeed every packet is being sent
at that speed, however your throughput over time between two motes cannot be
that high (time spent in backoff, loading buffers, time in the application
code, etc).

The most I have ever managed to get out of tinyos-1.x was approaching 80kb/s
and that was doing nothing else other than sending. Not only that, but the
tos1 cc2420 stack can source packets faster than it can receive them (though
my experience was using the maximum MTU), and I have, anecdotally read
similar things on this mailing list.



On 19/04/07, Michael Schippling <[EMAIL PROTECTED]> wrote:


If the destination is the pc you may be limited by the serial port speed.
There are some instructions for changing that speed, someplace...
I probably have a link, but searching the list might find it.

In my testing at:  http://www.etantdonnes.com/Motes/report_micaz/
I may have made that same mistake, and got about the same results as you.

MS


Jeong Kwanhee wrote:
> Hello all,
>
>
>
> Currently, I'm testing performance using micaz.
>
> I'm doing using surge program and I manipulated data size, pps(packet
> per sec).
>
> I sent 190kbps from source to destination(1hop), but I gained only
> 57kbps to destination.
>
> I don't know why this happening is. I think micaz hardward specification
> is appeared 250kbps.
>
>
>
> What am I doing about this happening??
>
> Anybody help me.
>
>
> 
>
> ___
> Tinyos-help mailing list
> Tinyos-help@Millennium.Berkeley.EDU
>
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] UART ReceiveMsg

[Inderjit Singh]

Thanks for the suggestions lad. Very appreciated. Most of them I have
already thought of. The code was only written to test that the communication
is working. That's it. But It's good to be confirmed on the issue. Thanks.

However, Michael, what do you mean by "you need to leave the 7E's alone as
well" ? I don't understand. And what is this "bracketed with the sync byte"?
Could you give an example please?

Inderjit

On 4/18/07, Michael Schippling <[EMAIL PROTECTED]> wrote:


I think you need to leave the 7E's alone as well.
If it's going to GenericComm, the full message
should be bracketed with the sync bytes. If that
doesn't work it may be due to having to swap a
source address or something...

Structure alignment shouldn't be a problem if you
are dealing with a char array that was structured
correctly to start with. You might check that your
pc serial driver is not trying to "help" by adding
line-feeds or something...it should be raw I/O.

Hopefully you've seen the octavetech doc:
http://www.octavetech.com/pubs/TB5-01%20Deciphering%20TinyOS%20Serial%20Packets.pdf


MS

Inderjit Singh wrote:
> Thanks Ben,
>
> I tried something very simple:
>
> 1. I get the byte stream from usb sent from the TMote like:
>   7e 42 xx xx xx xx 7e
>
> 2. I remove the 7e from the stream and send it back as it is (42 xx xx
> xx xx). But I still don't get it. C/C++ should be able to handle this
> no?
>
> Is there any doc on how the serial communication should be
> established. I have gone through the java code for sending but still
> it would help with a doc.
>
> Indy
>
>
> On 4/11/07, Ben Buckner < [EMAIL PROTECTED]> wrote:
>> > Hi,
>> >
>> > I have trouble sending msg from laptop (using c++) code to tmote.
>> All the
>> > code is at the bottom. I have no problem reading the data from the
>> serial
>> > but sending it back dooesn't seam to work. Anyone knows why? Thanks.
>> >
>> > Indy
>> [...]
>> > memcpy(output_buffer, &msgOUT, sizeof(msgOUT));
>>
>> Out of the dozens of things that could be wrong, it might be worth
>> pointing
>> out that C does not guarantee that structures can be serialized by
>> copying
>> bytewise out of memory like that. It can work, but you never know. The
>> most
>> usual reason why that would fail is if the compiler tries to align the
>> members of the structure and inserts padding (which it almost always
does
>> with odd-sized byte fields). At any rate, it would be a good idea to
make
>> sure that the code really generates the byte stream that you think it's
>> generating.
>>
>> Ben B.
>>
>>
>>
>> ___
>> Tinyos-help mailing list
>> Tinyos-help@Millennium.Berkeley.EDU
>>
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>>
> ___
> Tinyos-help mailing list
> Tinyos-help@Millennium.Berkeley.EDU
>
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Tuning the radio Ouput power

[Romain Thouvenin]

On 4/19/07, Philip Levis <[EMAIL PROTECTED]> wrote:

On Apr 18, 2007, at 8:44 AM, Fabrizio Stefani wrote:

> R
>> Also, I've found a CC2420Packet.setPower(message_t *, uint8_t),
>> but it
>> only applies to one packet.
>
> Changing power for each packet?
> Interesting... streams... power modulation depending on data
> value... low-power audio/video tx...
> Stop! wake up!
> Sorry, just playing with some ideas...
>
> And what about setting the value once?
> I don't think that it is resetted after each packet transmission.
>

Yes, it's per-packet so different network protocols can individually
control their TX power. Otherwise protocol A turns the power down,
protocol B breaks... e.g., MultihopLqi (which will be in the 2.0.1
release) breaks if there are large power differentials between nodes.

Phil



OK, thank you.

Romain
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] why the time values that I got are multiples of 32?

[Michael Schippling]

what are you using to sync the clocks?
I found by accident, and posted a link to an analysis
of sync mechanisms a few days ago which might help.
MS


ke tian wrote:

Hi,all

I wrote a program that used to get different time between two
motes.But I wonder why the figures that i got are multiples of 32,
like 32,64, 96, 128, 160 

I get time with LogicalTime.Time.get(). And I adapt TimeM.nc, as follow
//return call Clock.setRate(mInterval, mScale) ;
return call Clock.setRate(TOS_I1PS, TOS_S1024PS) ;

Please tell me why! I wanna get more accurate time.In addition, I am
useing micaz with tinyos 1.15 ,can i usetimestamp()? How to do ?

Thanks in advance.
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Has anyone installed on Linux? Please reply if you have

[keerthii]

Hi,

I was just wondering if anyone has installed Moteiv's Tmote tools or 
tinyos on linux. If so, please reply I need a file which I cannot find 
on the cvs.


Regards

Keerthi


___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

RE: [Tinyos-help] Micaz TOS_DATA_LENGTH change

[Munaretto, Daniele]

Try changing the length in the AM.h file. It should be fine.

Cheers

Daniele

 

 

 

Daniele Munaretto

Researcher

 

DoCoMo Communications Laboratories Europe GmbH

Landsbergerstraße 312  80687 Munich  Germany

 

Mobile  :   +49- 162-  2919-218

Office   :   +49-  89- 56824-218

Fax  :   +49-  89- 56824-300

 

[EMAIL PROTECTED]

visit us in http://www.docomolab-euro.com   

 

Managing Directors (Geschäftsführer): 

Dr. Toru Otsu, Dr. Narumi Umeda, Kazushige Yoshida

Amtsgericht München, HRB 132967



From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeong Kwanhee
Sent: Wednesday, April 18, 2007 1:06 PM
To: tinyos-help@Millennium.Berkeley.EDU
Subject: [Tinyos-help] Micaz TOS_DATA_LENGTH change

 

Hi all,

I am using micaz fro my application and the default size of TOS_Msg structure 
is 36byte(?).

In order to change the massage packet size, I added 

CFLAGS += -DTOSH_DATA_LENGTH=64 

to Makelocal

After that, I want to know actually whether its size is 64 or not.

I used tiniViz.

When I debug using tiniViz, I can see '[4] Sent Message  [addr  ] 
and so on.

However, Length is always expressed 0xc.

 

I used surge application for multihop routing.

Help me

 

This method is right??

 

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help