from:"Michael Schippling"


Near as I can tell the TimerM code uses timer0, via the Clock module.

Then under mica2 there is a SysTime module that uses Timer3.

And under micaz there are HPLTimer1 and HPLTimer2 modules,
plus a TimerJiffy that uses HPLTimer2.

The micaz code should work fine on mica2 as well, so you shouldn't
have to reinvent the wheel...and no, I don't know why it's only
available under micaz...

I also have a bit of, perhaps redundant, Timer3 code that may help
bootstrapping in:
http://www.etantdonnes.com/Motes/AVR128timers.zip

MS

Tao Wu wrote:

Hi,

Currently, I am implementing a high frequency timer (like 32KHz). I
plan to use the 16 bits timer3 in ATmega128.
The question is that I am not very sure what timers TinyOS 1.X  has used so far.
I think the Timer component uses timer0, but I do not know what timers
other components might use.
Can anyone confirm the compatibility of timers?
Thank you very much.

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

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

Re: [Tinyos-help] About MoteIV support information


Try searching around on
http://docs.tinyos.net/index.php/Boomerang
Most, if not all, of the tmote support pages got put there.
MS


manu suryavansh wrote:

Hi,

I am looking for tmote message format (that is the packet structure), it 
was earlier available at this link -

http://www.moteiv.com/support/tmote-message-format.html
If somebody knows where I can find this information please respond.

Thank you
Manu Suryavansh

*/Cory Sharp <[EMAIL PROTECTED]>/* wrote:

Oh, and all of the datasheets are here
http://www.sentilla.com/moteiv-endoflife.html .

On Nov 8, 2007 1:29 AM, Cory Sharp wrote:
 > You can find the Moteiv Community Wiki articles here
 > http://docs.tinyos.net/index.php/Boomerang announced from Joe's blog
 > post here
http://blog.sentilla.com/2007/10/sentilla-beta-update-and-docum.php
 > . - Cory
 >
 >
 >
 > On Nov 8, 2007 1:15 AM, Urs Hunkeler wrote:
 > > It might be possible to access large parts of the original web site
 > > through this link:
 > > http://web.archive.org/web/20070715062122/http://moteiv.com/
 > >
 > > However the archive is relatively slow and some parts might not be
 > > included (especially the areas where a subscription was
required). Also
 > > the most recent information might not be available (though
google cache
 > > might help there) I haven't checked yet. Maybe we should use
the archive
 > > to make a local copy somewhere?
 > >
 > > Cheers,
 > > Urs
 > >
 > >
 > > Peizhao Hu schrieb:
 > > > Dear All Tmote Sky Users;
 > > >
 > > > Anyone has a backup of all moteiv support information from
the web site?
 > > > As the sudden shutdown of MoteIV support web site, we lost
all this
 > > > information. It will be really graceful to have a copy for future
 > > > reference. :-)
 > > >
 > >
 > >
 > > ___
 > > Tinyos-help mailing list
 > > Tinyos-help@Millennium.Berkeley.EDU
 > >
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
 > >
 >
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help



Never miss a thing. Make Yahoo your homepage. 






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

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

Re: [Tinyos-help] (yet another) Question about signal


I guess if I took the time to read and understand all the NESCC design/doc,
rather than wasting it on trying to make my own projects work, I wouldn't
be asking so many seemingly redundant questions. I expect the whole thing
has to do with using "async" as a flag to force race-condition evaluation,
which then blossomed into a chain of fix-the-boundary-cases keywords.

thanks for the answer
MS


Michiel Konstapel wrote:

OK, good. Then another stupid question: "signal" == noop?


Not a stupid question at all, because yes, that's basically true. If you
look at the generated C code in build/$PLATFORM/app.c you'll see both "call
Foo.bar()" and "signal Foo.bar()" get turned into an ordinary C function
call.

Here's an example taken from Blink:

nesC:
event void Timer0.fired()
{
  call Leds.led0Toggle();
}

C:
static inline  void BlinkC$Timer0$fired(void)
{
  ;
  BlinkC$Leds$led0Toggle();
}

The code that fires the timer event from VirtualizeTimerC is a bit messy
because of the generic components involved, but eventually firing the event
just turns into a regular call to BlinkC$Timer0$fired().


HTH,
Michiel

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

Re: [Tinyos-help] (yet another) Question about signal


OK, so I found
nesC 1.1 Language Reference Manual (2003)
and
The nesC Language:... (2003)

but in a quick search I don't find _what_ is the meaning of "signal",
except that it seems to be prefixed to calling functions labeled "event".
Do I need to really read the whole thing to get the idea, or is there
some summary that explains the hierarchy and impetus behind these keywords?
Or do I have to re-remember BNF?

thx
MS

Philip Levis wrote:


On Nov 14, 2007, at 10:05 AM, Michael Schippling wrote:

I guess if I took the time to read and understand all the NESCC 
design/doc,

rather than wasting it on trying to make my own projects work, I wouldn't
be asking so many seemingly redundant questions. I expect the whole thing
has to do with using "async" as a flag to force race-condition 
evaluation,

which then blossomed into a chain of fix-the-boundary-cases keywords.


Not at all. The async keyword wasn't introduced until TinyOS 1.1.

Phil

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

Re: [Tinyos-help] TinyOS1.x timer


I believe the JiffyTimer is 32KHz using Timer2
so you may be able to use it directly.
MS


Tao Wu wrote:

Thanks a lot for the reply.
I have this question is because I need a high frequency timer, like 32KHz.
So far, the TimerM does not provide such granularity.
Actually, it is not very difficult, as long as understanding how to
write ISR in C.
I really appreciate your reply


On Nov 14, 2007 12:56 PM, Michael Schippling <[EMAIL PROTECTED]> wrote:

Near as I can tell the TimerM code uses timer0, via the Clock module.

Then under mica2 there is a SysTime module that uses Timer3.

And under micaz there are HPLTimer1 and HPLTimer2 modules,
plus a TimerJiffy that uses HPLTimer2.

The micaz code should work fine on mica2 as well, so you shouldn't
have to reinvent the wheel...and no, I don't know why it's only
available under micaz...

I also have a bit of, perhaps redundant, Timer3 code that may help
bootstrapping in:
 http://www.etantdonnes.com/Motes/AVR128timers.zip

MS


Tao Wu wrote:

Hi,

Currently, I am implementing a high frequency timer (like 32KHz). I
plan to use the 16 bits timer3 in ATmega128.
The question is that I am not very sure what timers TinyOS 1.X  has used so far.
I think the Timer component uses timer0, but I do not know what timers
other components might use.
Can anyone confirm the compatibility of timers?
Thank you very much.

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

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

Re: [Tinyos-help] Failed dependencies: libc.so.6(GLIBC_2.3.4) is needed by nesc-1.2.8a-1


The quick and dirty approach is to install with "rpm --nodeps"
and then see if anything works.
MS


Виталий Юркин wrote:

Hello :)

We have an issue with installtion of tinyOs, on the 4th step of 
installtion (4th step according to TinyOs 2.0.2 manual) when 
nesc-1.2.8a-1.i386.rpm is needed to be inastalled we've got:


error: Failed dependecies: libc.so.6(GLIBC_2.3.4) is needed by nesc-1.2.8a-1

We have Red Hat 9 (2.4.20-8) installed. We couldn't correctly install 
GLIBC_2.3.4.

So, we have 2 questions:

1) If there is any ways to resolve error with libc.so.6
2) Can we install TinyOs on Suse 10.3? Are there any known issues about it?

Best regards, Student Vitaly :)




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

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

Re: [Tinyos-help] How to read->send an entire log very fast


hmm, about 48,000 log records? My measurements of radio rates
indicate about 20 msg/sec for the 2000 (mica2) and 100-200 for
the 2420 (micaz, tmote). If you put one record in each message
that makes about 2400 sec for the mica2 and (absolute best case)
240 sec for the micaz. You should do a bit of timing analysis --
say, flash leds to indicate log-read and transmit cycles -- to
see if there is any room for improvement before you spend a lot
of time trying to improve things...

MS

Ariel Mauricio Nunez Gomez wrote:

Hello everyone,

I'm using the LogStorage abstraction on tinyos2-x with a tmote sky, my 
application fills a very large log (960Kb) and I'm using the same 
routine used in PacketParrot. 

Each Log entry is about 20 bytes and the whole read/send to Base Station 
takes about 15 minutes.


I guess the bottle neck is on the Flash read and I'm about to start 
making my log entries bigger and then splitting before sending.


I would like to know what you think about the problem. What is the the 
best time I should expect to achieve to get all the data from the flash 
and send it via the radio?


Thanks in advance,

Ariel.




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

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

Re: [Tinyos-help] Minimum Timer Interval of mica2


The TimerC period is in "binary" milli-secs, I think 1024/second,
which comes out to about 1.4 sec/min skew...using that you should
be able to do accurate time measurements within the unpredictability
of interrupt interleaving, etc...

For T1 versions above .10, the min Timer count is 3. I'm not clear
why that was hacked in at that point, but probably something to do
with the micaz...

To send messages as fast as things can go, skip the timer thing and
just start a new message from the sendDone() of the previous.

MS

Tao Wu wrote:

According to TinyOS1.x TimerC and ClockC' s implementation,
for a repeated timer, the min Timer interval is about 2 or 3 ms.
And my experiment measure shows that for 1000 ms interval,
there are about 1 sec bias per minute.
If you want to do it more accurately, try to use ISR directly.

Tao

On Nov 15, 2007 9:10 AM, RamKishore <[EMAIL PROTECTED]> wrote:

Hi all,
I fire timer at 100msec.For each firing, I transmit a packet.To
increase the Rate of transmission, Timer's time-period can be
decreased.what factors should be included in estimating the timer's time
period? and Whats the min. Time period that can be achieved?


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


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

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

Re: [Tinyos-help] TinyOS1.x timer


Are you sure Systime uses Timer2? I see a lot of this in the code:
outp(0x00, TCCR3A);

And I would guess that the HPL code is used underneath the 2420
radio functions you describe.

Sure would be nice to have a list of what controller functionality
is used where though, wouldn't it?

MS


Jeongyeup Paek wrote:


Below is where each atmega clocks are used:
* Timer0: 32KHz Timebase for TinyOS Timer functions(components). Remains 
active during all sleep modes.
* Timer1: CPUClk derived timebase for measuring send/receive time of 
radio packets (SFD)
* Timer2: CPUClk derived timebase for "jiffy" timing - IEEE802.15.4 
radio timing delays.

* Timer3: not used

If are willing to hack, then you can always hack into TimerM
and make it a 32khz timer since TimerM uses a underlying 32khz clock.

The 'SysTime' component uses Timer2, which is a CPU Clk
(sleeps when CPU sleeps) and it's freq is (I think) 7.xxMHz.
The problem is that, if you play around with Timer2,
the CC2420 stack on micaz might be disrupted.
:No problem on mica2, and it was designed for mica2 originally,
until micaz started to use Timer2 for CC2420 timing stuff...

I don't know about HPLTimer1/2 on micaz...
maybe there is something that resolves the conflict with cc2420?
But by just looking at their file names, I don't think they are for
public use... maybe they are used internally by cc2420 stack. In this
case, you should not touch them... or communication might not work.

Thanks

- jpaek


Tao Wu wrote:

Thanks a lot for the reply.
I have this question is because I need a high frequency timer, like 
32KHz.

So far, the TimerM does not provide such granularity.
Actually, it is not very difficult, as long as understanding how to
write ISR in C.
I really appreciate your reply


On Nov 14, 2007 12:56 PM, Michael Schippling <[EMAIL PROTECTED]> wrote:

Near as I can tell the TimerM code uses timer0, via the Clock module.

Then under mica2 there is a SysTime module that uses Timer3.

And under micaz there are HPLTimer1 and HPLTimer2 modules,
plus a TimerJiffy that uses HPLTimer2.

The micaz code should work fine on mica2 as well, so you shouldn't
have to reinvent the wheel...and no, I don't know why it's only
available under micaz...

I also have a bit of, perhaps redundant, Timer3 code that may help
bootstrapping in:
 http://www.etantdonnes.com/Motes/AVR128timers.zip

MS


Tao Wu wrote:

Hi,

Currently, I am implementing a high frequency timer (like 32KHz). I
plan to use the 16 bits timer3 in ATmega128.
The question is that I am not very sure what timers TinyOS 1.X  has 
used so far.

I think the Timer component uses timer0, but I do not know what timers
other components might use.
Can anyone confirm the compatibility of timers?
Thank you very much.

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


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



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

Re: [Tinyos-help] (yet another) Question about signal


Yes that makes a lost of sense, logically. It just seems odd, to me,
to have a bunch of redundant keywords cluttering up my code when the
intent is (almost?) always implicit in the usage...

Now, if "signal" actually fired off code in a different interrupt-like
context...that would be both logical and reasonable.

thx
MS

Jeongyeup Paek wrote:


I see 'call' and 'signal' as a type-checking mechanism with 'noop',
where 'command' and 'event' can be regarded as
'INPUT' and 'OUTPUT' tags is VHDL language.
Type checking (and a word of memo for the programmer)
helps you to use INPUT and OUTPUT properly.
They tell you the 'direction' in which you should call a function.

In fact, although some people say 'nesC is dialect of 'C' with
notoriously strange add-ons such as command/event/component/modules,
I see it more close to VHDL, with the internals written in C.
You must wire an input pin with an output pin, and vice versa,
for an interface between components. You must output a value on
an output pin, and you must read a value on an input pin.
Thus, compile-time type-checking mechanisms such as
'call' & 'signal' are very useful.

And... 'async' is just another type-checking,
that let's you distinguish sequences of function calls
that came/didn't come from a hardware interrupt.

This is how I understood it through couple years of playing around..

Thanks

- jpaek


Michael Schippling wrote:

OK, so I found
nesC 1.1 Language Reference Manual (2003)
and
The nesC Language:... (2003)

but in a quick search I don't find _what_ is the meaning of "signal",
except that it seems to be prefixed to calling functions labeled "event".
Do I need to really read the whole thing to get the idea, or is there
some summary that explains the hierarchy and impetus behind these 
keywords?

Or do I have to re-remember BNF?

thx
MS

Philip Levis wrote:


On Nov 14, 2007, at 10:05 AM, Michael Schippling wrote:

I guess if I took the time to read and understand all the NESCC 
design/doc,
rather than wasting it on trying to make my own projects work, I 
wouldn't
be asking so many seemingly redundant questions. I expect the whole 
thing
has to do with using "async" as a flag to force race-condition 
evaluation,

which then blossomed into a chain of fix-the-boundary-cases keywords.


Not at all. The async keyword wasn't introduced until TinyOS 1.1.

Phil

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



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

Re: [Tinyos-help] Oscilloscope Application


You should get data, if not information, w/o a sensor attached.
If you are using the T1 Oscope app that goes directly to the
UART port you should see something on the PC side no matter.
Check that you are using the right port and MOTECOM variable.
I forget what platform you are on, if you have a MIB510 host-
adapter make sure the silly-slide-switch opposite the serial
conn is in the OFF position.

MS


Abdullah Kadri wrote:
I have a problem with oscilloscope application. When I run the Listen 
process I do not see any traffic. And even when I open the Oscilloscope 
GUI I do not see any signal. The Leds on the board are blinking and I am 
using Micaz board. I do not have a photo sensor onboard. Does this 
affect the process?


 


Abdullah Kadri, P.Eng., Ph.D. Candidate
The University of Western Ontario
Department of Electrical and Computer Engineering
Phone: (519) 661-2111 ext. 81271

 





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

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

Re: [Tinyos-help] (yet another) Question about signal


ah, History...

So klueska...is there a good place in the new improved TOSwiki
to put your clear and concise description of interface contracts?

thanks
MS


Philip Levis wrote:


On Nov 15, 2007, at 12:18 PM, Michael Schippling wrote:


Yes that makes a lost of sense, logically. It just seems odd, to me,
to have a bunch of redundant keywords cluttering up my code when the
intent is (almost?) always implicit in the usage...

Now, if "signal" actually fired off code in a different interrupt-like
context...that would be both logical and reasonable.


Originally, when TinyOS was Perl scripts that munged some cpp macros, 
there were two macros:


TOS_CALL_COMMAND()
TOS_SIGNAL_EVENT()

They needed to be distinct because

TOS_COMMAND() and
TOS_EVENT()

led to different names.

Phil

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

Re: [Tinyos-help] Minimum Timer Interval of mica2


I think the original question had to do with how fast
one could send messages...anyway, that's where we are now...

I forgot about the 'throttling' I needed in my radio tests,
which bear out your assertion that messages get lost if you
go as fast as possible. I throttled on the PC side with a
command/response mechanism, so my minimum was 10ms. I never
looked any deeper, why do you think the receiver is the bottleneck?

MS

Jeongyeup Paek wrote:

Was Kishore's original question about
"how fast can you send packets?" ? or
"how fast can you trigger timer?" ?

For the Timer, as Michael said, 3ms is the min.
Otherwise you 'might' lose a timer.fired event.

For the packet rate, it depends on the pkt size.
But one thing I know:
although sending immediately after sendDone events
without any timer is fastest logically,
it loses far more packets than slowing it down a little.
If the sender sends packets back-to-back,
the receiver is not fast enough to process them and drops some packets.
For example, in one of my experience (I forgot the pkt size),
sending every 9ms achieved far greater goodput than
sending back-to-back.
Also, if you do it with Timer firing every say 3ms,
then at least some of calls to Send.send will return FAIL
b/c it is processing the previous pkt. So your actual
sending interval can be 6 or 9 or 12...

So... you need to figure out your self for you pkt size.

Thanks

- jpaek


Michael Schippling wrote:

The TimerC period is in "binary" milli-secs, I think 1024/second,
which comes out to about 1.4 sec/min skew...using that you should
be able to do accurate time measurements within the unpredictability
of interrupt interleaving, etc...

For T1 versions above .10, the min Timer count is 3. I'm not clear
why that was hacked in at that point, but probably something to do
with the micaz...

To send messages as fast as things can go, skip the timer thing and
just start a new message from the sendDone() of the previous.

MS

Tao Wu wrote:

According to TinyOS1.x TimerC and ClockC' s implementation,
for a repeated timer, the min Timer interval is about 2 or 3 ms.
And my experiment measure shows that for 1000 ms interval,
there are about 1 sec bias per minute.
If you want to do it more accurately, try to use ISR directly.

Tao

On Nov 15, 2007 9:10 AM, RamKishore <[EMAIL PROTECTED]> wrote:

Hi all,
I fire timer at 100msec.For each firing, I transmit a packet.To
increase the Rate of transmission, Timer's time-period can be
decreased.what factors should be included in estimating the timer's 
time

period? and Whats the min. Time period that can be achieved?


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




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

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



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

Re: [Tinyos-help] Oscilloscope Application


How do you connect a micaz directly to a USB port?
MS

Abdullah Kadri wrote:
I am not getting any information at all only "re-synchronizing..." I am 
using micaz with Atmega128L on-board. I am using COM6 and 
MOTECOM variable is correct.i do not have MIB, just the board connected 
directly to the USB port. The Oscilloscope GUI opens without any data on 
screen. Please any hint.


- Original Message -----
From: Michael Schippling <[EMAIL PROTECTED]>
Date: Thursday, November 15, 2007 5:02 pm
Subject: Re: [Tinyos-help] Oscilloscope Application
To: Abdullah Kadri <[EMAIL PROTECTED]>
Cc: tinyos-help@Millennium.Berkeley.EDU

 > You should get data, if not information, w/o a sensor attached.
 > If you are using the T1 Oscope app that goes directly to the
 > UART port you should see something on the PC side no matter.
 > Check that you are using the right port and MOTECOM variable.
 > I forget what platform you are on, if you have a MIB510 host-
 > adapter make sure the silly-slide-switch opposite the serial
 > conn is in the OFF position.
 >
 > MS
 >
 >
 > Abdullah Kadri wrote:
 > > I have a problem with oscilloscope application. When I run the
 > Listen
 > > process I do not see any traffic. And even when I open the
 > Oscilloscope
 > > GUI I do not see any signal. The Leds on the board are
 > blinking and I am
 > > using Micaz board. I do not have a photo sensor onboard. Does
 > this
 > > affect the process?
 > >
 > > 
 > >

 > > Abdullah Kadri, P.Eng., Ph.D. Candidate
 > > The University of Western Ontario
 > > Department of Electrical and Computer Engineering
 > > Phone: (519) 661-2111 ext. 81271
 > >
 > > 
 > >

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


Abdullah Kadri, P.Eng., Ph.D. Candidate
The University of Western Ontario
Department of Electrical and Computer Engineering
Phone: (519) 661-2111 ext. 81271


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

Re: [Tinyos-help] TelosB

2007-11-17 Thread Michael Schippling


You did install the MSP tools rpms, right?
If so, does it work from the command line?
Perhaps you need to put them in the global PATH
variable so Eclipse can find them.

Which Eclipse plugin are you using? I've never been successful
in getting one to work.
MS


antonio gonga wrote:

Hey all,
I've some problems with TelosB motes, First I was using MICAz platform, 
now I'd like to use TelosB without changing my tinyoS installation.
whenever I try to compile and install an application to a telosB mode I 
get the following message: Note That I'm using Eclipse Plugin fo TinyOS.


"make -C "/cygdrive/c/DOCUME~1/cmboy/WORKSP~1/TELOSB" telosb -board=none 
bsl.com3 install.10  "

make: Entering directory `/cygdrive/c/DOCUME~1/cmboy/WORKSP~1/TELOSB'
mkdir -p build/telosb
compiling Blink to a telosb binary
ncc -o build/telosb/main.exe -Os -mdisable-hwmul 
-I/opt/tinyos-1.x/tos/lib/CC2420Radio 
-I/opt/tinyos-1.x/tos/../beta/STM25P -Wall -Wshadow 
-DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=telosb 
-fnesc-cfile=build/telosb/app.c -board= -DIDENT_PROGRAM_NAME="Blink" 
-DIDENT_PROGRAM_NAME_BYTES="66,108,105,110,107,0" 
-DIDENT_USER_HASH=0xb0922a80L -DIDENT_UNIX_TIME=0x473ecebcL Blink.nc -lm

Couldn't execute msp430-gcc
make: *** [exe0] Error 2
make: Leaving directory `/cygdrive/c/DOCUME~1/cmboy/WORKSP~1/TELOSB'


thanks in advance



Share life as it happens with the new Windows Live. Share now! 






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

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

Re: [Tinyos-help] no output when i run TinyDBApp

2007-11-18 Thread Michael Schippling


Do you have the jar (not just the directory) which contains
TinyDBMain in your CLASSPATH?
MS

allen john wrote:

when i run TinyDBApp in mica2 mote and run tools/java
java net.tinyos.tinydb.TinyDBMain

this message come

Exception in thread "main"
java.lang.NoClassDefFoundError:net/tinyos/tinydb/TinyDBMain

the packages are available in /opt/tinyos-1.x/tools/java/jars

what is the problem please tell me


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

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

Re: [Tinyos-help] string.h

2007-11-18 Thread Michael Schippling


hmm, it's usually "string.h", all lower-case.

What versions of what platforms are you using?
MS

Vijayant Bhatnagar wrote:

Hi,
Please let me know if string.h is supported in nesC ?

I am getting this error  "RadioCountToLedsC.nc:34:20: error: String.h:
No such file or directory".

thanks,
Vijayant Bhatnagar
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

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

Re: [Tinyos-help] unicasting message

2007-11-18 Thread Michael Schippling


read more of the tutorial.

But the quick answer is: use the destination moteID instead of BCAST
as the send() address argument.

MS

Vijayant Bhatnagar wrote:

Hi,
I am right now doing broadcast using the reference from tinyos
tutorials using AM_BROADCAST_ADDR. Can you please tell me how can i
unicast message ? What address should be given for that ?

Help  appreciated.

thanks,
Vijayant Bhatnagar
Rutgers Univ.
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

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

Re: [Tinyos-help] string.h


actually I was also interested in what development platform,
since Widows (used to be) case-insensitive...it may be that
you found something that works on windows but not linux or
somesuch...
MS

Vijayant Bhatnagar wrote:

Hey Michael,
I am using tinyos 2.0.2.

Thanks,
Vijayant.

On Nov 18, 2007 10:08 PM, Michael Schippling <[EMAIL PROTECTED]> wrote:

hmm, it's usually "string.h", all lower-case.

What versions of what platforms are you using?
MS


Vijayant Bhatnagar wrote:

Hi,
Please let me know if string.h is supported in nesC ?

I am getting this error  "RadioCountToLedsC.nc:34:20: error: String.h:
No such file or directory".

thanks,
Vijayant Bhatnagar
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

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

Re: [Tinyos-help] Where is all sensor components of Telos B located?


Well, there's stuff like:
tos/platform/telos/HumidityM.nc
and
tos/platform/msp430/InternalTempM.nc

Both those directories get searched when you do a telosb compile...

MS


Derek Tarm wrote:
Hi all. I am writing a program that read the humidity, temperature and 
light sensors data periodically from telosb sensors. But I couldn't find 
their components. Could you please tell me or show me some doc about 
this? Thank you!





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

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

Re: [Tinyos-help] PATH Setting


The Widows EnvVar panel does support a PATH variable (or any other
arbitrary name you like). Our old favorite MSDOGS command.com uses
PATH just like bash. And the separator is semi-colon ';'...

When cygwin bash starts-up it converts the 'global' PATH to it's own
liking by replacing C: with /cygdrive/c, inverting the backslashes,
and converting the semi's to full colons ':'. (Although a quick
experiment just now indicates that either semi or full seems to work...)

You may create your own PATH, or add to it using the syntax that uhu
indicated, but note, it's "cygdrive" not "dirv"... and if you have
any spaces in directory names, like "Program Files", you should put
the whole thing in quotes: "xxx" -- this was I think your original
problem. Also the trailing period is not Latinate syntax, but means
the current directory -- so do this:

export PATH="$PATH;/cygdrive/c/Program Files/java/jre1.6.0_03/bin;."

However, some other little caviets...putting the JRE in your path is
less than ideal since you probably want to compile Java files using
the JDK. And the whole idea of putting the JDK in "Program Files"
gives me the willies when trying access it with the danged space.
I usually force Java installs to go to something like C:/JAVA just
to avoid the headache.

MS

Urs Hunkeler wrote:

Hi,

I think that the Windows Environment Variables dialog does not know
about $PATH. It seems that you have overwritten the old path settings.
You probably have to locate your java installation and add the path to
your java executables manually to the path again. In the Windows
Environment Variables dialog, don't use the special word $PATH but write
all paths individually, separating them with a semi-colon (;).

Once your path settings work again, if you need to add paths in cygwin,
use the command like (note that it uses now semi-colons (;) instead of
colons (:)) :

export PATH=$PATH;/cygdirve/c/Program Files/java/jre1.6.0_03/bin;.

Cheers,
Urs


Ittipong Khemapech schrieb:

Hi,

I typed:

export PATH=$PATH:/cygdirve/c/Program Files/java/jre1.6.0_03/bin:

and got:

bash: export: 'Files/java/jre1.6.0_03/bin:': not a valid identifier

I set PATH variable in the Environment Variables by selecting Properties of
My Computer (under Advanced tab). I followed all suggested in
http://www.tinyos.net/tinyos-2.x/doc/html/install-tinyos.html.

After I typed echo $PATH, I got:

/opt/msp430/bin:/usr/local/bin:/usr/bin:/usrX11R6/bin:/opt/msp430/bin:$PATH

Many thanks,
Ittipong

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

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

Re: [Tinyos-help] tmote sky docs ...

You did look under:
http://docs.tinyos.net/index.php/Boomerang
right? I was under the impression that all of the Moteiv support
pages had been transfered there, but maybe they shorted us some...

If you want the actual Boomerang message structs, look at:
moteiv/apps/Delta/Delta.h
and
moteiv/tos/lib/MultiHopLQI/MultiHop.h

Note, looking at the latter just solved one of my mysteries...
There are 3 different multi-hop message types defined there.
I couldn't figure out why I was getting different messages
with Listen connected to the Delta system...

MS

manu suryavansh wrote:

Hi,

I am using the Delta application from Moteiv and I am looking for the 
Delta application packet structure. It was earlier available at 
http://www.moteiv.com/support/tmote-message-format.html, but that link 
is no longer working and I have looked at following links

http://docs.tinyos.net
http://www.sentilla.com/moteiv-endoflife.html
http://tinyos.cvs.sourceforge.net/tinyos/tinyos-1.x/contrib/boomerang/
http://www.cems.uvm.edu/~aobrien/tmote/

and it is not available at any of the above links.

If anybody knows where I can find this information please respond.

Thank you
Manu
UFL

*/Joe Polastre <[EMAIL PROTECTED]>/* wrote:

FYI, All the documentation is available at
http://www.sentilla.com/moteiv-endoflife.html
and
http://docs.tinyos.net

The code is now checked into TinyOS CVS
http://tinyos.cvs.sourceforge.net/tinyos/tinyos-1.x/contrib/boomerang/

-Joe

On Nov 8, 2007 8:23 AM, Andrew Parson O'Brien wrote:
 > Hello,
 >
 > here
 >
 > http://www.cems.uvm.edu/~aobrien/tmote/
 >
 > you can find ISO images of the driver and documentation CDs, data
 > sheets for the tmote-sky and tmote-connect as well as the quickstart
 > guide for the tmote-sky.
 >
 > Thanks go to Charley Robinson here at UVM for having the good
sense to
 > d/l them.
 >
 > Cheers,
 > Andy
 >
 >
 >
 >
 > ___
 > Tinyos-help mailing list
 > Tinyos-help@Millennium.Berkeley.EDU
 >
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
 >
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Be a better sports nut! Let your teams follow you with Yahoo Mobile. Try 
it now. 

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

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

Re: [Tinyos-help] Sequence Number?


Figuring that out will probably require some Code Archaeology...
It's possible that Multi-Hop is documented someplace, but I don't
know where. May the Google be with you.
MS



manu suryavansh wrote:

Hi,

Thanks for the information. I have one more question - there are various 
sequence number  transmitted in the packet (seqno, originalseqno etc). I 
am trying to find out the number of packets lost based on the sequence 
number- which sequence number should I use and what does the other 
sequence number signify. Below is one of the packet structure I found on 
the help-list and I think the Delta has similar structure and there are 
multiple sequence number in there.
 


ByteTOS_Msg

01length

02fcfhi

03fcflo

04dsn

05-06   destpan

07-08   addr

09   
 type


10group

/*- the next group of elements is stored in TOS_Msg.data 
---*/


11-12  sourceaddr

13-14  originaddr

15-16  seqno

17-18 
 originseqno


19ttl

20id

/*-  the next group of elements is stored in TOS_MHopMsg.data */

   DeltaMsgBeaconMsg

21seqno  parent

22seqno  parent

23seqno  cost

24seqno  cost

25readinghopcount

26readinghopcount

27parent timestamp

28parent timestamp

29neighborsizetimestamp

30retransmissionstimestamp

31neighbors

32   
 neighbors


34neighbors

35neighbors

36neighbors

37neighbors

38quality

39quality

40quality

41quality

42quality

43quality



Thank you
Manu Suryavansh
UFL
*/Michael Schippling <[EMAIL PROTECTED]>/* wrote:

You did look under:
http://docs.tinyos.net/index.php/Boomerang
right? I was under the impression that all of the Moteiv support
pages had been transfered there, but maybe they shorted us some...

If you want the actual Boomerang message structs, look at:
moteiv/apps/Delta/Delta.h
and
moteiv/tos/lib/MultiHopLQI/MultiHop.h

Note, looking at the latter just solved one of my mysteries...
There are 3 different multi-hop message types defined there.
I couldn't figure out why I was getting different messages
with Listen connected to the Delta system...

MS



manu suryavansh wrote:
 > Hi,
 >
 > I am using the Delta application from Moteiv and I am looking for
the
 > Delta application packet structure. It was earlier available at
 > http://www.moteiv.com/support/tmote-message-format.html, but that
link
 > is no longer working and I have looked at following links
 > http://docs.tinyos.net
 > http://www.sentilla.com/moteiv-endoflife.html
 >
http://tinyos.cvs.sourceforge.net/tinyos/tinyos-1.x/contrib/boomerang/
 > http://www.cems.uvm.edu/~aobrien/tmote/
 >
 > and it is not available at any of the above links.
 > If anybody knows where I can find this information please respond.
 >
 > Thank you
 > Manu
 > UFL
 >
 > */Joe Polastre /* wrote:
 >
 > FYI, All the documentation is available at
 > http://www.sentilla.com/moteiv-endoflife.html
 > and
 > http://docs.tinyos.net
 >
 > The code is now checked into TinyOS CVS
 >
http://tinyos.cvs.sourceforge.net/tinyos/tinyos-1.x/contrib/boomerang/
 >
 > -Joe
 >
 > On Nov 8, 2007 8:23 AM, Andrew Parson O'Brien wrote:
 > > Hello,
 > >
 > > here
 > >
 > > http://www.cems.uvm.edu/~aobrien/tmote/
 > >
 > > you can find ISO images of the driver and documentation CDs, data
 > > sheets for the tmote-sky and tmote-connect as well as the
quickstart
 > > guide for the tmote-sky.
 > >
 > > Thanks go to Charley Robinson here at UVM for having the good
 > sense to
 > > d/l them.
 > >
 > > Cheers,
 > > Andy
 > >
 > >
 > >
 > >
 > > ___
 > > Tinyos-help mailing list
 > > Tinyos-help@Millennium.Berkeley.EDU
 > >
 >
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
 > >
 > ___
 > Tinyos-help mailing list
 > Tinyos-help@Millen

Re: [Tinyos-help] conrol motor using micaz?

2007-11-20 Thread Michael Schippling


What kind of motor? And how small?

Most motors that are not REALLY small will draw more current
than can be supplied directly from the controller I/O pin, and
they may have inductive kicks that could have unfortunate
consequences to the controller.

If you are talking about just turning something on and off,
you can use a transistor common emitter circuit to scale the
current up and isolate the inductive effects. Programming such
a thing is "just" a matter of setting an I/O pin to digital
output and toggling it on and off. I just sent some T1 advice
to this list about how to do that, search for "TOSH_ASSIGN_PIN".

But if you want to control motor direction and speed things get
more complicated...

MS

[EMAIL PROTECTED] wrote:
I need to control a small motor that use 3V using the micaZ mote, I 
think to connect it using the I/O pins(PW0-7 and INT-03 ), but I don't 
know how to code it, do you have any idea that could help me pleas





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

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

Re: [Tinyos-help] RAM and ROM variables

2007-11-20 Thread Michael Schippling


Being too lazy to go search the entire code tree...

Shouldn't "const uint8_t" work on all platforms?
I mean, wouldn't that be what the full avr-gcc
typedef boils down to?

As to accessing in ROM, the AVR has LPM and SPM instructions to
transfer both ways, but they take an extra clock cycle compared
to RAM access. I'm not yet familiar enough with the MSP
instruction set, but I'd expect there's something similar.

MS

Michiel Konstapel wrote:

That depends on your compiler :-)

For avr-gcc, there are special types defined that are put in ROM, like
const_uint8_t, const_uint16_t, etc. You can access them as regular variables
(though you can't assign to them, of course). For example,
const_uint8_t settings[4] = { 1, 2, 3, 4 };
puts an array of 4 bytes into ROM. 


For msp430-gcc, it's almost the same but you use the normal types and the
const keyword:
const uint8_t settings[4] = { 1, 2, 3, 4 };

I *think* they may even be writable depending on which section of ROM
they're in, but I couldn't tell you how to do that off the top of my head.
Michiel



-Original Message-
From: [EMAIL PROTECTED] [mailto:tinyos-help-
[EMAIL PROTECTED] On Behalf Of Victor Shia
Sent: dinsdag 20 november 2007 1:34
To: tinyos-help@millennium.berkeley.edu
Subject: [Tinyos-help] RAM and ROM variables

Hi,
Is it possible to tell the compiler to put a variable in ROM  as
opposed to RAM?
I have alot of data that I would like to place in the mote's ROM when
I flash it.
Also, how would I access the variable if it is possible to do this?

Thanks,
Victor Shia


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

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

Re: [Tinyos-help] RAM and ROM variables

2007-11-20 Thread Michael Schippling


Yes, thanks, that was an interesting article.
I was confusing my PIC compiler with a "real" one.
There 'const' puts stuff in ROM.
MS


Janos Sallai wrote:

Being too lazy to go search the entire code tree...

Shouldn't "const uint8_t" work on all platforms?
I mean, wouldn't that be what the full avr-gcc
typedef boils down to?


No, a simple const wouldn't be enough. What you need is
__attribute__((__progmem__)) what you need.

Regarding the available macros, typedefs, and functions related to data
stored in ROM, check the documentation of pgmspace.h at
http://www.nongnu.org/avr-libc/user-manual/group__avr__pgmspace.html


Janos

Michiel Konstapel wrote:

That depends on your compiler :-)

For avr-gcc, there are special types defined that are put in ROM, like
const_uint8_t, const_uint16_t, etc. You can access them as regular

variables

(though you can't assign to them, of course). For example,
const_uint8_t settings[4] = { 1, 2, 3, 4 };
puts an array of 4 bytes into ROM.

For msp430-gcc, it's almost the same but you use the normal types and

the

const keyword:
const uint8_t settings[4] = { 1, 2, 3, 4 };

I *think* they may even be writable depending on which section of ROM
they're in, but I couldn't tell you how to do that off the top of my

head.

Michiel



-Original Message-
From: [EMAIL PROTECTED] [mailto:tinyos-help-
[EMAIL PROTECTED] On Behalf Of Victor Shia
Sent: dinsdag 20 november 2007 1:34
To: tinyos-help@millennium.berkeley.edu
Subject: [Tinyos-help] RAM and ROM variables

Hi,
Is it possible to tell the compiler to put a variable in ROM  as
opposed to RAM?
I have alot of data that I would like to place in the mote's ROM when
I flash it.
Also, how would I access the variable if it is possible to do this?

Thanks,
Victor Shia

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

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

No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.16.1/1140 - Release Date:
11/19/2007 7:05 PM


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

Re: [Tinyos-help] SendData by Oscilloscope

2007-11-21 Thread Michael Schippling


Without looking at your code...

Check that each real send() returns SUCCESS, if you try to stack
them up too fast they will refuse to post the message. The usual
way to deal with that is to have a state variable that indicates
when sendDone() has been called.

MS


Chan kenniel wrote:

Dear all,

I rewrote the Oscilloscpe application as a component, in order that my 
own application can send data to the TOSSIM.
I also wrote an interface called SendTestData.nc, there's one function 
SendData(char *) in it. and this interface is provided by
the OscilloscopeM.nc. This component works fine on many cases, but if I 
try to call the send function ( SendData(string str)) too often, for 
example, if I call the SendData(string str) immediately one after 
another, like:


...
SendData("one");
SendData("two");
...

then the second time the string "two" cannot be received, but I print it 
out my application did call the senddata("two"),
dont know why the receiver side can not receive it. So because the 
SendData function is wrote in the Timer.fired() part,

so everytime, Timer.fired() is invoked, all I get is
...
one
one
one
one
...

I don't know why. Can anybody help me out with this. Those are my 
attached files... Should be easy to read because I didn't change

too much. Thanks in advanced.




--
Best wishes,
Kenneth Chan


Wish you have a good day!




// $Id: OscopeMsg.h,v 1.2 2003/10/07 21:44:58 idgay Exp $

/*  tab:4
 * "Copyright (c) 2000-2003 The Regents of the University  of California.  
 * All rights reserved.

 *
 * Permission to use, copy, modify, and distribute this software and its
 * documentation for any purpose, without fee, and without written agreement is
 * hereby granted, provided that the above copyright notice, the following
 * two paragraphs and the author appear in all copies of this software.
 * 
 * IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR

 * DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT
 * OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF
 * CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 * 
 * THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES,

 * INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
 * AND FITNESS FOR A PARTICULAR PURPOSE.  THE SOFTWARE PROVIDED HEREUNDER IS
 * ON AN "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATION TO
 * PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS."
 *
 * Copyright (c) 2002-2003 Intel Corporation
 * All rights reserved.
 *
 * This file is distributed under the terms in the attached INTEL-LICENSE 
 * file. If you do not find these files, copies can be found by writing to
 * Intel Research Berkeley, 2150 Shattuck Avenue, Suite 1300, Berkeley, CA, 
 * 94704.  Attention:  Intel License Inquiry.

 */
/*
 * Authors: Nelson Lee
 * Date last modified:  6/27/02
 *
 */

/* Message types used by Oscope. */

/**
 * @author Nelson Lee
 */

enum {
  BUFFER_SIZE = 40
};

struct OscopeMsg
{
uint16_t sourceMoteID;
uint16_t lastSampleNumber;
uint16_t channel;
char data[1][BUFFER_SIZE];
uint8_t datalength;
};

struct OscopeResetMsg
{
/* Empty payload! */
};

enum {
  AM_OSCOPEMSG = 40,
  AM_OSCOPERESETMSG = 32
};




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

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

Re: [Tinyos-help] accesssing source address in main

2007-11-21 Thread Michael Schippling


The source moteID is not part of any standard message header,
but is often included in specific 'payload' structures, like
Oscilloscope's OscopeMsg. Once you have the message, in any
standard receive() method looking at the ID is just a matter
of software

And there is plenty of information about the packet structure
laying around. Try searching this list for "TOS_Msg" and see:
http://www.octavetech.com/pubs/TB5-01%20Deciphering%20TinyOS%20Serial%20Packets.pdf

MS

Sourabh Shah wrote:

Hello all

I want to access source address in main at base station. Can any one 
tell me how can I do that. I couldnt get much info about cracking 
received packet and accessing  Node id  of  source  node.  The thing  
is  I  want  to  receive  messages  from  specific  nodes  at  some  
instances. 



Get easy, one-click access to your favorites. Make Yahoo! your homepage. 






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

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

Re: [Tinyos-help] The string becomes unrecoginizable after some string operation


Can you send some examples of the corruption, with the original as well?
Also how are you printing it? Is this under a simulator?
And make sure your OriginalData is shorter than 50 chars and null
terminated.

MS

[EMAIL PROTECTED] wrote:

Dear all,

I found that the string under nesc, once being processed by some string 
functions, for example, strcat() and strcpy(), will become totoally 
disordered and unrecognizable.


for example:
aFunction(*OriginalData)
{
  char DataToSend[50];
  strcpy(DataToSend,OriginalData);
  strcat(DataToSend,"}"};
  //here if I print DataToSend out, it is totally disordered, but 
DataToSend if fine.

 ...
}

I am wondering if there is any restrictions on string processing? Or 
this does not happen to any of you?


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

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

Re: [Tinyos-help] accesssing source address in main

I'm cc'ing this back to the list to keep a record...

I'm not sure what you mean by "main". Can you post your code
and the errors that you get?

MS

Sourabh Shah wrote:

hello sir,
   I have already tried to use source address in main. But its 
giving lots of errors if I include Multihop.h in my file.

*/Michael Schippling <[EMAIL PROTECTED]>/* wrote:

The source moteID is not part of any standard message header,
but is often included in specific 'payload' structures, like
Oscilloscope's OscopeMsg. Once you have the message, in any
standard receive() method looking at the ID is just a matter
of software

And there is plenty of information about the packet structure
laying around. Try searching this list for "TOS_Msg" and see:

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

MS

Sourabh Shah wrote:
 > Hello all
 >
 > I want to access source address in main at base station. Can any one
 > tell me how can I do that. I couldnt get much info about cracking
 > received packet and accessing Node id of source node. The thing
 > is I want to receive messages from specific nodes at some
 > instances.
 >
 >

 > Get easy, one-click access to your favorites. Make Yahoo! your
homepage.
 >
 >
 >
 >

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

Get easy, one-click access to your favorites. Make Yahoo! your homepage. 
<http://us.rd.yahoo.com/evt=51443/*http://www.yahoo.com/r/hs>

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

Re: [Tinyos-help] Pulse detection in T2 TMote port



You probably have two problems. The first one is interference
from the WiFi signal which may be due to poor grounding/shielding
or using too low a signal at your input pin. The second is that
it's fairly dicy trying to detect a 1ms pulse with a 1ms timer...
nyquist says you need to sample at at least twice the frequency
of what you want to resolve.

So you want to use a faster timer or perhaps a Capture input.
Look at the MSP manual for some (too much) info on Capture.
For drivers, I don't know what is available in T2, but T1 has:
   tos\platform\msp430\MSP430TimerC.nc
and Boomerang:
tos\platform\msp430\timer\Counter32khzC.nc
which may exist in some form in T2 as well.

As to how many interrupts you can process, it pretty much depends on
how much each int does. Off the top of my head I think the telosb runs
at 4Mhz with one or two clocks per instruction, so say two...that makes
about 2000 instructions in 1ms.

MS


André Miguel de Almeida Marrão Rodrigues wrote:

Hi

I just sent it again because is seems the first one did not appear in 
the list.


André

- Original Message - From: "André Miguel de Almeida Marrão 
Rodrigues" <[EMAIL PROTECTED]>

To: 
Sent: Wednesday, November 21, 2007 10:15 PM
Subject: Pulse detection in T2 TMote port



Hi

I need do detect a digital 1ms width pulse in tmote port.

I have modified the TEP 109 - Binary Pin-Connected Sensor in order to 
detect the rising
edge of the sinal (a square sinal with 1ms width) and that worked 
perfect until the day
that I get the node with my device near a WIFI router. Somehow noise 
introduced in the

circuit and there are a few false pulses.

So now I want to detected the raising edge and the failing edge (using 
the TEP 109 code) and
measure the time between them, which should be arround 1ms. First 
things become complicated
because I'm not sure how to get the uS timer on TMote (so I use the ms 
timer...) and perhaps most importante I'm not sure
if I can process 2 interrupts (with the associated code on the driver 
and on the program) in a 1ms timeframe.


The code for the driver is the one from the TEP109 (user button); my 
code is:


event void Notify.notify(bool val) {

uint32_t begin;

uint32_t now;


if (val == FALSE) {

 call Timer1ms.startOneShot(2); //just to count the time from the 
raising edge


}

else { //so it's a falling edge

begin = call Timer1ms.gett0();

now = call Timer1ms.getNow();

if ((now - begin)< 2000 ){

...> a true pulse was detected
Any advice or ideas are much appreciated.

Regards,

André Rodrigues




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

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

Re: [Tinyos-help] Pulse detection in T2 TMote port


perhaps a little ferrite bead on your signal wire would
kill some RF interference...
MS


André Miguel de Almeida Marrão Rodrigues wrote:

Hi

I will try to find another high resolution timer or the capture. Indeed 
because
of the low resolution of the timer I campared with < and > operators and 
some tolerance.


I can't do much about the noise (grounding is ok, but there is no 
shielding) and the signal has only a 1K resistor in serie,

so it should be enougth for the MSP430 ports.

And yes, you are right 2000 instructions is a lot including the OS code.

Thanks,

André Rodrigues

- Original Message ----- From: "Michael Schippling" <[EMAIL PROTECTED]>
To: "André Miguel de Almeida Marrão Rodrigues" 
<[EMAIL PROTECTED]>

Cc: 
Sent: Thursday, November 22, 2007 6:27 PM
Subject: Re: [Tinyos-help] Pulse detection in T2 TMote port




You probably have two problems. The first one is interference
from the WiFi signal which may be due to poor grounding/shielding
or using too low a signal at your input pin. The second is that
it's fairly dicy trying to detect a 1ms pulse with a 1ms timer...
nyquist says you need to sample at at least twice the frequency
of what you want to resolve.

So you want to use a faster timer or perhaps a Capture input.
Look at the MSP manual for some (too much) info on Capture.
For drivers, I don't know what is available in T2, but T1 has:
   tos\platform\msp430\MSP430TimerC.nc
and Boomerang:
tos\platform\msp430\timer\Counter32khzC.nc
which may exist in some form in T2 as well.

As to how many interrupts you can process, it pretty much depends on
how much each int does. Off the top of my head I think the telosb runs
at 4Mhz with one or two clocks per instruction, so say two...that makes
about 2000 instructions in 1ms.

MS


André Miguel de Almeida Marrão Rodrigues wrote:

Hi

I just sent it again because is seems the first one did not appear in 
the list.


André

- Original Message - From: "André Miguel de Almeida Marrão 
Rodrigues" <[EMAIL PROTECTED]>

To: 
Sent: Wednesday, November 21, 2007 10:15 PM
Subject: Pulse detection in T2 TMote port



Hi

I need do detect a digital 1ms width pulse in tmote port.

I have modified the TEP 109 - Binary Pin-Connected Sensor in order 
to detect the rising
edge of the sinal (a square sinal with 1ms width) and that worked 
perfect until the day
that I get the node with my device near a WIFI router. Somehow noise 
introduced in the

circuit and there are a few false pulses.

So now I want to detected the raising edge and the failing edge 
(using the TEP 109 code) and
measure the time between them, which should be arround 1ms. First 
things become complicated
because I'm not sure how to get the uS timer on TMote (so I use the 
ms timer...) and perhaps most importante I'm not sure
if I can process 2 interrupts (with the associated code on the 
driver and on the program) in a 1ms timeframe.


The code for the driver is the one from the TEP109 (user button); my 
code is:


event void Notify.notify(bool val) {

uint32_t begin;

uint32_t now;


if (val == FALSE) {

 call Timer1ms.startOneShot(2); //just to count the time from the 
raising edge


}

else { //so it's a falling edge

begin = call Timer1ms.gett0();

now = call Timer1ms.getNow();

if ((now - begin)< 2000 ){

...> a true pulse was detected
Any advice or ideas are much appreciated.

Regards,

André Rodrigues




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

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

Re: [Tinyos-help] accesssing source address in main

2007-11-23 Thread Michael Schippling

What version of TOS are you using?
I have this program:
contrib/xbow/apps/XSensorMDA300/XSensorMDA300M.nc
but don't find a file named "XMDA300M.nc" in T1.

MS

Sourabh Shah wrote:

Thank you very much Michael

Well by main I wanted to say my application program. For eg. XMDA300M.nc etc
I am totally new to tiny os. All I want is to  check teh node Id of 
source node and decide whether to accept the data or not. For testing I 
am using XMDA300 application. I am not getting where to ckeck this 
source address and how?

*/Michael Schippling <[EMAIL PROTECTED]>/* wrote:

I'm cc'ing this back to the list to keep a record...

I'm not sure what you mean by "main". Can you post your code
and the errors that you get?

MS

Sourabh Shah wrote:
 > hello sir,
 > I have already tried to use source address in main. But its
 > giving lots of errors if I include Multihop.h in my file.
 >
 > */Michael Schippling /* wrote:
 >
 > The source moteID is not part of any standard message header,
 > but is often included in specific 'payload' structures, like
 > Oscilloscope's OscopeMsg. Once you have the message, in any
 > standard receive() method looking at the ID is just a matter
 > of software
 >
 > And there is plenty of information about the packet structure
 > laying around. Try searching this list for "TOS_Msg" and see:
 >

http://www.octavetech.com/pubs/TB5-01%20Deciphering%20TinyOS%20Serial%20Packets.pdf
 >
 > MS
 >
 > Sourabh Shah wrote:
 > > Hello all
 > >
 > > I want to access source address in main at base station. Can
any one
 > > tell me how can I do that. I couldnt get much info about cracking
 > > received packet and accessing Node id of source node. The thing
 > > is I want to receive messages from specific nodes at some
 > > instances.
 > >
 > >
 >

 > > Get easy, one-click access to your favorites. Make Yahoo! your
 > homepage.
 > >
 > >
 > >
 > >
 >

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

 > Get easy, one-click access to your favorites. Make Yahoo! your
homepage.
 >

Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See 
how. <http://us.rd.yahoo.com/evt=51732/*http://overview.mail.yahoo.com/>

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

Re: [Tinyos-help] How to make tinyos application under ecclipse

2007-11-25 Thread Michael Schippling


There are two TOS plugins for eclipse that purport to do compiles under
eclipse control. I have not been successful in getting either to work as
advertised, but I'm bad at following instructions...take a look at:

http://www.dcg.ethz.ch/~rschuler/installation.htm
http://www.tinydt.net/links.html

The latter has a sourceforge presence so you may find your solution
in their source.

MS


[EMAIL PROTECTED] wrote:

Dear all,

I am writing a program for ecclipse under windows.
Part of this program will make the tinyos application automatically to 
exe file, making use of the 'make' application provided by the tinyos 
package.

Now my approach is to call 'make' as an external program using

Process P=Runtime.getRuntime().exec("cmd /c ..

of Java. But the problem is 'make' should be run under cygwin 
environment. Thus I have no idea how to run it, because I do not know 
how should I treat the Process, as command prompt window or sth.


Could you be kind enough to tell me some opinion, like how to execute 
make system, or any make application under java, etc?


Thank you to all of you. My project is about to finish due to your help.

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


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

[Tinyos-help] Re: help

2007-11-25 Thread Michael Schippling


I'm cc'ing this to the help list to keep a record.
Please send messages there instead of directly to me.

I'm getting the feeling that you haven't been through the
whole tutorial. That would help some. Also try some simpler
host side programs like tools/java/net/tinyos/tools/Listen.java
to get a better understanding of what is going on under the hood.

You should be able to run MIG on the tos/lib/Counters/IntMsg.h
file to get a java class that knows how to interpret the message
correctly (if that hasn't been done someplace already). Then you
can follow the model of Listen to open a connection to a
base-station and receive messages, which you can use the IntMsg
class to print or dump or process to your hearts desire.

Also see my code bolus for some handrolled, non-MIG, examples:
http://www.etantdonnes.com/Motes/robocode.tar.gz

MS



allen john wrote:

hello

i have run SenseToRfm application

if i want to take this values in pc what i have to do

i am doing like this
tools/java
java net.tinyos.mcenter.MessageCenter

In the Serial Connector i click "Start Port".
In the "App Loader" window i  enter "net.tinyos.mcenter.MessageTable"
and click the "LoadApp" button.  and then other
"net.tinyos.mcenter.AllMSGDisplay these commands are running without
error but i want to get mote readings but i want to take SenseToRfm
readings what i have to do.

my main question is

i attatched nesc application that takes multiple light intensity
readings (from the sensor board's photo sensor on Mica motes ).
if i want to take light readings in pc what i have to do  which
command will provide me light readings of sensors in pc

please guide me and tell me my appication is right.can this
application give me light readings of sensors.and for light readings
what i have to do.


please guide me i shall be very thankful to you.please tell me


thanks

Allen


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] Fwd: Changing TX_POWER

2007-11-27 Thread Michael Schippling


That all kind of depends on what version of what platform you are using.
In T1 for mica2 there is SetRFPower(uint8_t power) in
tos/platform/mica2/CC1000Control.nc

Try searching for similar names online and in the code for your platform.

MS


Vijayant Bhatnagar wrote:

Hi,
Is there any command to change this parameter. Basically, we wish to 
change the transmitter signal strength. Please let us know how to do this.


Help appreciated.

Thanks,
Vijayant  Bhatnagar
Rutgers.


-- Forwarded message --
From: *Vijayant Bhatnagar* <[EMAIL PROTECTED] 
>

Date: Nov 27, 2007 7:41 PM
Subject: Changing TX_POWER
To: tinyos-help@millennium.berkeley.edu 




Hi,
We wish to change TX_Power of the mote. Please let us know how to do 
this. We are stuck at this stage.


Any help appreciated.

Warm regards,
Vijayant




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


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] tutorial lesson 6 oscilloscope


If you're using TOS 1.x, try using "[EMAIL PROTECTED]:mica2"...I know it makes
no sense, but what you're interested in is the serial packet structure
which defaults to the mica2 version...And in T1, the non-RF version
of Oscope connects directly to the serial port and eliminates the
problem of radio comm for initial testing.

Make sure you are using the right COM port number. Try using Listen and
ListenRaw to see if you get anything at all on the port. You may need
to debug into the Java code to see where it is failing.

MS

cyberkiwy wrote:

hi!
we're doing the lesson 6 of tinyos tutorial, we have installed the 
oscilloscopeRF application on a mote, and the TOSbase on another mote 
(MTS400) that is connected to the pc by USB.

their leds works fine, but we can't use the application serialforwarder

 java net.tinyos.sf.SerialForwarder -comm [EMAIL PROTECTED]:57600
or 
java net.tinyos.sf.SerialForwarder -comm [EMAIL PROTECTED]:micaz <-- should it work?


it says

Listening to [EMAIL PROTECTED]:57600
Shutting down all client connections
Closing source
Closing socket
--

but it doesn't show anything else..
any ideas?


--
Cyb3rk1wy!!




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


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] Need Help with Temp in Tinyos-1.x


You might try putting the sendData() in a separate task. I think fired()
runs in an interrupt context and send... may take a while to run. Also
try it with a fixed and small Timer count value, you may be setting
things in correctly with the Random calculation.

MS

Chao Sun wrote:

Hi,
I'm writing a simple program on a micaz mote, which receive the query 
from another mote, sense the environment, and transmit the data back to 
that mote.
I used the PhotoTemp module in the tinyos-1.x, and when I wire the ADC 
interface to Photo, the program works OK.
However, when I wire the ADC interface to Temp, it seems that the 
program receive the query just for the first time. Afterwards, it can 
not receive any query, and the program is halted.

Could someone help me to solve this problem? Many thanks!

Chao

The core part of my program is as follow:

task void dataTask()
  {
  uint16_t count;
  count = call Random.rand();
  count = (count/65535) * 1000;
  atomic{
  DataPtr->sourceID =  TOS_LOCAL_ADDRESS;
  DataPtr->type = currentDataType;
  }
  call fireTimer.start(TIMER_ONE_SHOT, count);
  }


  event result_t fireTimer.fired()
  {
  if (destID != TOS_LOCAL_ADDRESS)
  {call sendData.send(destID, sizeof(struct 
DataMsg), &data_packet);

  call Leds.greenToggle();
  }
  return SUCCESS;
  }

  event TOS_MsgPtr recvReq.receive(TOS_MsgPtr m)
  {
  uint16_t temp;
  call Leds.redToggle();
  ReqPtr = (struct ReqMsg*)m->data;
  temp = ReqPtr->seqNo;
  if (temp != lastSeq)
  {
  lastSeq = temp;
  destID = ReqPtr->sourceID;
  currentDataType = DT_TEMP;call  
tempADC.getData();

   }return m;
  }

  async event result_t tempADC.dataReady(uint16_t data)
  {
   atomic{
  DataPtr = (struct DataMsg*)data_packet.data;
  DataPtr->data = data;
  post dataTask();
   }
  return SUCCESS;
  }
event result_t sendData.sendDone(TOS_MsgPtr msg, bool success)
  {
  return SUCCESS;
  }

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


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

[Tinyos-help] Tmote comm on AppleMac?


Rather than doing extensive online research, and because I don't have
the hardware to test it anyway, I'm hoping someone can point me to the
right places to JustGet(TM) what I need.

Not being a Macintoshiteer I have no idea what this entails:
I have a project that will want to use a Mac to talk to a TmoteSky using
my Java code. I don't know what version of what yet, I suspect late OSX,
but I don't know if it's gonna be Intel or PowerPC.

I assume that I need and can get a modern JRE (from Sun?), but I also
need the javax.comm and FTDI stuff. I've googled some refs to various
sources for both of the above but none of them seem to agree. And all
seem to believe that I will be doing the development on the Mac so they
concentrate on installing compilers and building tools...

Surely there is an existing comm package that I can just install?
It would also be nice if I could download new code to the Tmote with
a standalone msp430-bsl. Does that exist in binary someplace?

Any advice greatly appreciated.
thx
MS

--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] Tmote comm on AppleMac?


thanks...I'm using T1 and the target is a client's computer so I only
want to install the minimum to do communication and, for bonus points,
re-Mote software upgrades. The difficulty with the "build and package"
option is that, without finding an appropriate Mac and installing a
full dev system, I have nothing on which to build and package...

On the subject of the new-improved-T2-comm-library...is it interface
compatible with the old-useful-Sun version?

MS


Greg Hackmann wrote:

Michael Schippling wrote:

Rather than doing extensive online research, and because I don't have
the hardware to test it anyway, I'm hoping someone can point me to the
right places to JustGet(TM) what I need.

Not being a Macintoshiteer I have no idea what this entails:
I have a project that will want to use a Mac to talk to a TmoteSky using
my Java code. I don't know what version of what yet, I suspect late OSX,
but I don't know if it's gonna be Intel or PowerPC.

I assume that I need and can get a modern JRE (from Sun?), but I also
need the javax.comm and FTDI stuff. I've googled some refs to various
sources for both of the above but none of them seem to agree. And all
seem to believe that I will be doing the development on the Mac so they
concentrate on installing compilers and building tools...

Surely there is an existing comm package that I can just install?
It would also be nice if I could download new code to the Tmote with
a standalone msp430-bsl. Does that exist in binary someplace?

Any advice greatly appreciated.
thx
MS



Are you using TinyOS 1.x or TinyOS 2.x?  TinyOS 2.x now ships with its
own serial library, so you don't need to install Sun's CommAPI library
if that's the version you're using.  You should be able to just follow
steps 1-4 and 8-9 of Kevin Klues's tutorial
(http://docs.tinyos.net/index.php/Installing_tinyos-2.x_on_Mac_OS_X_(Tiger))
to get everything installed, including a Java environment and the TinyOS
SDK.

TinyOS 1.x should be largely the same, except that you'll need to
install RXTX 2.0 (http://www.rxtx.org) as a drop-in replacement for
CommAPI.  I'm not sure if there are prebuilt binaries for it anywhere,
but the source distribution includes a script that can build and package
it for you.

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


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] API of MSP430 ?


If you're asking about the chip itself, here's the TI link:
   http://focus.ti.com/docs/prod/folders/print/msp430f1611.html

If you mean the TOS interfaces, I doubt that any such document exists.
MS


mejda chouaieb wrote:

Hello All,
 
 Do some one know where I can find the API of MSP430 ?

 I need the complete API of MSP430.

Thanks


  

Yahoo! Mail innove : interface hyper pratique, messenger intégré, couleurs - 
http://mail.yahoo.fr

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

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

Re: [Tinyos-help] using tinyos-2.x-contrib, running code


CFLAGS are passed to a C compiler, usually GCC in our case,
so the behavior depends on what gcc wants to do with arguments.
In the case of -I the common behavior is to add a directory to
the compile-time include-file search path. Directories are (usually)
searched in the order listed until the desired file is found,
and (again usually) it's not an error if the dir doesn't exist.
If the full path of search dir is the same as that of another
search dir, then they are the same dir...but I think what you
asked is if you have "mychip/chip" and "tos/chip" the first
file found will be used, so it depends on what order the dirs
are specified.

My belief is that PFLAGS in TOS makefiles does the same thing for NCC
(Preprocessor) and again include dirs are searched in the order speced.
NESCC has a bunch of (partially) hidden search dirs that it sticks
onto the end of whatever PFLAGS specifies. Those "hidden" dirs
may be found in the .platform file in later T1's, or reverse
engineered using the -v flag (which you can stick into PFLAGS).

MS


John Griessen wrote:

I am wanting to start using tinyos-2.x-contrib/ecosensory
as my tested code, and have a question about CFLAGS += -I

I see Makefile lines like:

CFLAGS += -I../../../tos/lib/extended_storage

and in that case,

ll ../../../tos/lib/extended_storage

finds something, but some contribs I browsed seem incomplete.

How will this extra includes search work?
I assume it wants unique dir names not found in the tinyos-2.x tree, 
right?  For instance, if I put a new platform in 
tinyos-2.x-contrib/ecosensory/tos/platforms/ecosens1 directory I think

I will get a compilation that finds the ecosens1 platform directory,
but what about a chips dir?

What happens when a contributor puts a Makefile include to search out
another chips dir they have and with a chip of the same name as in the 
tinyos-2.x tree?


John Griessen
Still merging code in with the tinyos-2.x tree to run it...

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

Re: [Tinyos-help] where can i find the javacomm package


I have q squirreled away copy:
http://www.etantdonnes.com/TMP/javacomm20-win32.zip
MS


Nashwa Abo Elneel wrote:

Hi,

I am trying to install TinyOs 1.x using RPMs as explained on the 
Tinyos.net website however i cannot fine the javacomm package for 
windows. the Sun website has it only for Linux and Solaris. Can anyone help?


Nashwa


Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See 
how. 





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

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

Re: [Tinyos-help] Oscilloscope application and data rate


My experience is that the data rate is limited, first by the "UART"
speed (for tmote using USB, I think this is not an issue, but micaz's
over serial are possibly baud-rate bound) and then by the radio
packet cycle time...for the most part I think 200 standard sized
messages a sec is the practical limit. Mica2's are limited to about
25 msg/sec by the radio speed itself.

Search back on this list for the logic of 29 byte payloads,
and advice about increasing such.

MS

Nashwa Abo Elneel wrote:

Hi,

I have a question regarding the oscilloscope application in lesson 6 of 
TinyOs 1.x tutorial. the application states that the maximum Payload 
size of a TinyOS frame is 29 bytes however it doesn't put any limitation 
regarding the serial data forwarder. does this mean that the maximum 
data rate achieved by the serial forwarder is equal to the UART chosen 
baud rate. and if each packet has about 34 Bytes as explained in detail 
down then the serial forwarder can achieve a data rate of about 200 
packets per second?


Does anyone know why the payload size was limited to 29 bytes only? can 
it be increased?


The high data rate is necessary for me since i am having a high data 
rate application and would like to achieve a reasonable packets per size 
which are not supported by the Xserve application of Moteworks which 
limits the packets to 5 packets per second making it unsuitable for my 
application.


anybody has ideas?

Regards,
Nashwa


Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See 
how. 





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

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

Re: [Tinyos-help] Effect of packet size

2007-11-30 Thread Michael Schippling


Search this list for "TOS_Msg" "packet size"...

Short story: The bigger it is the more likely it will have a CRC error.

MS

manu suryavansh wrote:

Hi,

 From information on the list I found out that the tmotes can perform 
well at 100 packets per second and also there is the 250kbps data rate 
limit of the transceiver, so in order to achieve higher sampling rate in 
a multihop application it was suggested to put more reading in one 
packet there by increasing the packet size and getting more efficiency 
in terms of data.
I want to know is there any disadvantage of using a very large packet 
size as long as the total data rate is less than 250kbps?


Thank you
Manu Suryavansh
University of Florida


Never miss a thing. Make Yahoo your homepage. 






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


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] Adding Java to an existing TinyOs installation

2007-11-30 Thread Michael Schippling


Ignoring the question of _how_ you got a T1 install w/o tools...

You should be able to just copy the directories of interest into
your existing TOS tree and blithly continue. Two places to look:

snapshots of various "releases":
http://www.tinyos.net/dist-1.1.0/

CVS:
http://sourceforge.net/projects/tinyos/

note that toscheck is not a Java tool but lives in tools/scripts.
MS



Nashwa Abo Elneel wrote:

Hi all,

I have a current TinyOs 1.x installation which doesn't include the Java 
tools (like serial forwarder, TinyViz, Toscheck,...etc.) below its root 
directory. Is it possible to add these tools to the current installation 
without reinstalling the whole TinyOS? How? and from where to get them 
separately?


anybody has ideas?

Thanks,
Nashwa


Get easy, one-click access to your favorites. Make Yahoo! your homepage. 






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


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] GPIO lines??

2007-12-01 Thread Michael Schippling


If you are on T1 search this list for just about any message from "schip"
with content "TOSH_ASSIGN_PIN". I send out the how-to about every 3-6 mos.
I don't know if T2 uses the same defines, but it should be "similar".
MS


[EMAIL PROTECTED] wrote:

Hi all...

Does any one have any code to control external device using the GPIO 
Lines (on Micaz INT0, INT1, INT2...) or any such application???


Is there any documentation to deal with these lines???

Ashraf

 





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


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] Is Byte Transmission possible?

2007-12-02 Thread Michael Schippling


nope...it's an all or nothing packet oriented interface.
You can however send 5 separate 2 byte messages if you've
got the bandwidth.

MS

RamKishore wrote:

Hi all,
  I have message of 10 bytes. I send using GenericComm 
component's send interface as:

 call sendMsg.send(TOS_BCAST_ADDR,10, &Msg);

can I transmit byte by byte or group of atleast 2 bytes in 5 transmissions?

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

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

Re: [TINYOS-HELP]: cp: cannot stat `build/telosb/main.ihex': No such file or directory

I think the problem is an older version of cygwin,
but I'm pretty sure the answer is somewhere in the
help archive...Search for "getreent"

MS


Urs Hunkeler wrote:
> Hi Sam,
> 
> The first error probably means that it did not compile the telosb
> binary, possibly because of the second problem that you describe just below.
> 
> The second problem looks to me more like a problem with cygwin. I rarely
> use cygwin so I can't really help you there. Search the mailing list for
> the keywords cygwin and dll, or even directly for __getreent. Maybe
> updating cygwin could help.
> 
> Cheers,
> Urs
> 
> Renee Azhen schrieb:
>> Dear all:
>>   I updated my tinyos from V 1.x to version 2.02 with the updating 
>> instruction.
>>   But an error occured when upload the Blink to my telosb node:
>>   here is the info:
>>   [EMAIL PROTECTED] /opt/tinyos-2.x/apps/Blink
>> $ make telosb reinstall
>> cp build/telosb/main.ihex build/telosb/main.ihex.out
>> cp: cannot stat `build/telosb/main.ihex': No such file or directory
>> make: *** [setid] Error 1
>>
>>   dear all, could you tell me how to fix this problem?
>>   and  if I type command: make telosb, another error occured:
>>   here is the output info:
>>   [EMAIL PROTECTED] /opt/tinyos-2.x/apps/Blink
>> $ make telosb
>> mkdir -p build/telosb
>> compiling BlinkAppC to a telosb binary
>> ncc -o build/telosb/main.exe -Os -O -mdisable-hwmul -Wall -Wshadow 
>> -DDEF_TOS_AM_
>> GROUP=0x7d -Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c -board= 
>> -DI
>> DENT_PROGRAM_NAME=\"BlinkAppC\" -DIDENT_USER_ID=\"ibm\" 
>> -DIDENT_HOSTNAME=\"ibm-v
>> s2a1bhcns0\" -DIDENT_USER_HASH=0x245ca709L -DIDENT_UNIX_TIME=0x4753f4d0L 
>> -DIDENT
>> _UID_HASH=0xa83bc5e1L  BlinkAppC.nc -lm
>> make: *** [exe0] Error 57
>>
>>   And a warning box poped up:
>>   "the procedure entry point __getreent could not be located in the dynamic 
>> link library cygwin1.dll"
>>
>>   I think maybe something wrong with the NesC tool, so I changed the NesC 
>> rpm from nesc-1.2.8a-1.cygwin.i386.rpm to nesc-1.2.8b-1.cygwin.i386.rpm. But 
>> still the same error occured.
>>
>>   I have spent 12 hours for this problem, but still no progress achieved.
>>
>>   Is there any nice guy can help me?
>>   Wating for your help!
>>
>>   Best Regards &Thanks
>>   Sam
> ___
> Tinyos-help mailing list
> Tinyos-help@Millennium.Berkeley.EDU
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

-- 
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] Reading the raw data from the receiver on the PC over the UART!


In TOS1.x the OscilloscopeRF and SenseToRfm demo apps send ADC readings
over the radio. TOSBase is used at the PC receiving end to forward the
messages through the UART into the host PC. Oscope has a host side display
program, or you can use the tools/java/net/tinyos/tools/Listen.java program
to peek at the messages themselves. You shouldn't have to fiddle with
any code to get this working and they provide a reasonable basis for
your own development.

You should also read through the doc/tutorial where most of this is covered.

MS


Ruoshui Liu wrote:

Dear all,

Currently, I have implemented a single transmission link containing one 
transmitter and one receiver. What I want to do next is to use the PC or 
laptop to read the received raw data from the receiver over the UART 
channel. I know I have to plug the receiver to the programming board 
acting as the basestation, and I think the start point is probably to 
modify the TOSBase. However, there are many other functions included in 
the TOSBase application. What I want to do is just the simple job to 
send the raw data back to the PC via UART. Could anyone tell me how to 
simplify this? I mean what is the core part or key function I should use 
in order to read the raw data. Thank you very much!


Best regards,
Ruoshui Liu
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] Reading the raw data from the receiver on the PC over the UART!

I don't use T2 so this should be taken under advisement...

It may be that the dest addr is  because it gets overwritten
with the UART address when being forwarded. There is no src addr
in the standard header (unless this changed in T2), but it is
often included in the message body. If that is getting overwritten
all bets are off. In T1, the UART message format is the mica2 format
in tos/types/AM.h. TOSBase converts from micaz to mica2 format unless
you do some special magic, and the 2420 radio fields (lqi, etc) are
dropped. Tmotes with Boomerang do not do this, so the behavior is
different on different platforms/versions. RSSI is tagged on to the
end of messages in receive() but is not part of the UART forwarded
message so you have no way to see it on the PC side. Folks have fixed
this by modifying the receive() in the base-station to grab the RSSI
and overwrite some field in the message before forwarding.

So I guess the message is that you'll have to dig through your base-
station code to see what it is really doing...also search this list
for RSSI grabbing advice.

MS

Ittipong Khemapech wrote:

Hi,

I am trying to do the same thing but in TinyOS 2.x. I am modifying 
BlinkToRadio and BaseStation to vart transmission power level (TX) and 
see how RSSI changes. I have successfully change the TX.

I've been using the tools/java/net/tinyos/tools/Listen.java program by 
following Lesson 4 in the tutorial. There are several problems that I am 
having:

1. I've got FF FF for both source and destination addresses.
2. I have no clue where to start getting RSSI and LQI readings.

Any suggestions would be appreciated.

Best wishes,
Ittipong

On 03/12/2007, *Michael Schippling* <[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>> wrote:

In TOS1.x the OscilloscopeRF and SenseToRfm demo apps send ADC readings
over the radio. TOSBase is used at the PC receiving end to forward the
messages through the UART into the host PC. Oscope has a host side
display
program, or you can use the tools/java/net/tinyos/tools/Listen.java
program
to peek at the messages themselves. You shouldn't have to fiddle with
any code to get this working and they provide a reasonable basis for
your own development.

You should also read through the doc/tutorial where most of this is
covered.

MS

Ruoshui Liu wrote:
 > Dear all,
 >
 > Currently, I have implemented a single transmission link
containing one
 > transmitter and one receiver. What I want to do next is to use
the PC or
 > laptop to read the received raw data from the receiver over the UART
 > channel. I know I have to plug the receiver to the programming board
 > acting as the basestation, and I think the start point is probably to
 > modify the TOSBase. However, there are many other functions
included in
 > the TOSBase application. What I want to do is just the simple job to
 > send the raw data back to the PC via UART. Could anyone tell me
how to
 > simplify this? I mean what is the core part or key function I
should use
 > in order to read the raw data. Thank you very much!
 >
 > Best regards,
 > Ruoshui Liu
 > ___
 > Tinyos-help mailing list
 > Tinyos-help@Millennium.Berkeley.EDU
<mailto:Tinyos-help@Millennium.Berkeley.EDU>
 >
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] Reading the raw data from the receiver on the PC over the UART!

That should work. Just be aware that you can have only one send() active
at a time, so if you are transmitting on the radio from that node you
need to interleave the calls using a state variable in sendDone() or
something similar.
MS

Ruoshui Liu wrote:
As you said in ur reply that "You shouldn't have to fiddle with any code 
to get this working and they provide a reasonable basis for your own 
development", but the thing is I have one application already installed 
in the receiver. Therefore, in this case, I need to modify the TOSBase 
to be adaptable with my application in the receiver. Do you think so?

I know my thought is obviously naive, but I have to say that can I just 
simply call:

call DataMsg.send(TOS_UART_ADDR, sizeof(CountMsg_t), &msg);

to ask the receiver to send the received raw data to the host PC via 
UART while it is receiving the data from the transmitter?

Thank you very much!

Best regards,
Ruoshui

Michael Schippling wrote:

I don't use T2 so this should be taken under advisement...

It may be that the dest addr is  because it gets overwritten
with the UART address when being forwarded. There is no src addr
in the standard header (unless this changed in T2), but it is
often included in the message body. If that is getting overwritten
all bets are off. In T1, the UART message format is the mica2 format
in tos/types/AM.h. TOSBase converts from micaz to mica2 format unless
you do some special magic, and the 2420 radio fields (lqi, etc) are
dropped. Tmotes with Boomerang do not do this, so the behavior is
different on different platforms/versions. RSSI is tagged on to the
end of messages in receive() but is not part of the UART forwarded
message so you have no way to see it on the PC side. Folks have fixed
this by modifying the receive() in the base-station to grab the RSSI
and overwrite some field in the message before forwarding.

So I guess the message is that you'll have to dig through your base-
station code to see what it is really doing...also search this list
for RSSI grabbing advice.

MS

Ittipong Khemapech wrote:

Hi,

I am trying to do the same thing but in TinyOS 2.x. I am modifying 
BlinkToRadio and BaseStation to vart transmission power level (TX) 
and see how RSSI changes. I have successfully change the TX.

I've been using the tools/java/net/tinyos/tools/Listen.java program 
by following Lesson 4 in the tutorial. There are several problems 
that I am having:

1. I've got FF FF for both source and destination addresses.
2. I have no clue where to start getting RSSI and LQI readings.

Any suggestions would be appreciated.

Best wishes,
Ittipong

On 03/12/2007, *Michael Schippling* <[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>> wrote:

In TOS1.x the OscilloscopeRF and SenseToRfm demo apps send ADC 
readings
over the radio. TOSBase is used at the PC receiving end to 
forward the

messages through the UART into the host PC. Oscope has a host side
display
program, or you can use the tools/java/net/tinyos/tools/Listen.java
program
to peek at the messages themselves. You shouldn't have to fiddle 
with

any code to get this working and they provide a reasonable basis for
your own development.

You should also read through the doc/tutorial where most of this is
covered.

MS

Ruoshui Liu wrote:
 > Dear all,
 >
 > Currently, I have implemented a single transmission link
containing one
 > transmitter and one receiver. What I want to do next is to use
the PC or
 > laptop to read the received raw data from the receiver over 
the UART
 > channel. I know I have to plug the receiver to the programming 
board
 > acting as the basestation, and I think the start point is 
probably to

 > modify the TOSBase. However, there are many other functions
included in
 > the TOSBase application. What I want to do is just the simple 
job to

 > send the raw data back to the PC via UART. Could anyone tell me
how to
 > simplify this? I mean what is the core part or key function I
should use
 > in order to read the raw data. Thank you very much!
 >
 > Best regards,
 > Ruoshui Liu
 > ___
 > Tinyos-help mailing list
 > Tinyos-help@Millennium.Berkeley.EDU
<mailto:Tinyos-help@Millennium.Berkeley.EDU>
 >

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

--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
<mailto:Tinyos-help@Millennium.Berkeley.EDU>

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

Re: [TinyOS-Help]: Surge.Mainclass error & when staring SerialForwarder, how to set the baud rate??

2007-12-04 Thread Michael Schippling

For baud rate you usually use the name of the mote platform, like:
[EMAIL PROTECTED]:mica2  or [EMAIL PROTECTED]:tmote
that also handles some message formatting issues internally.

The error message means exactly what it says: the port is in use.
Some other process on your computer has COM1 open already...it could
be a mouse or something like that.

But I notice, now, that you want to run the simulator "tossim",
not a real system. According to:
http://www.tinyos.net/tinyos-1.x/doc/serialcomm/index.html
you can use something like "[EMAIL PROTECTED]" instead of
the COMx spec.

MS


Renee Azhen wrote:
> Dear all:
> I want to use tossim to simulate the Surge application, but faced two 
> problems:
> 1. when staring SerialForwarder, how to set the baud rate??  I am using a  
> laptop
> here is the command:
> java net.tinyos.sf.SerialForwarder -comm [EMAIL PROTECTED]: 
> 2. I use the default baud rate, 19200, but when start the Java 
> application Sure.Mainclass, an error occured, here is the screening shot:
> C:\Program Files\UCB\cygwin\opt\tinyos-1.x\tools\java>java 
> net.tinyos.surge.Main
> Class 125
> Using AM group ID 125 (0x7d)
> Starting mote listener...
> java.io.IOException: Port COM1 busy
> at 
> net.tinyos.packet.SerialByteSource.openStreams(SerialByteSource.java:
> 69)
> at net.tinyos.packet.StreamByteSource.open(StreamByteSource.java:52)
> at net.tinyos.packet.Packetizer.openSource(Packetizer.java:119)
> at net.tinyos.packet.AbstractSource.open(AbstractSource.java:77)
> at net.tinyos.packet.Packetizer.open(Packetizer.java:114)
> at net.tinyos.packet.PhoenixSource.run(PhoenixSource.java:167)
> java.io.IOException: Port COM1 busy
> at 
> net.tinyos.packet.SerialByteSource.openStreams(SerialByteSource.java:
> 69)
> at net.tinyos.packet.StreamByteSource.open(StreamByteSource.java:52)
> at net.tinyos.packet.Packetizer.openSource(Packetizer.java:119)
> at net.tinyos.packet.AbstractSource.open(AbstractSource.java:77)
> at net.tinyos.packet.Packetizer.open(Packetizer.java:114)
> at net.tinyos.packet.PhoenixSource.run(PhoenixSource.java:167)
> [EMAIL PROTECTED]:19200  died - exiting 
> (java.io.IOException: Port COM1 busy)
>  
>  
> Dear all, could you help me to resolve these two problems??
> really thanks
> Sam
> 
> 
> 
> 进入雅虎游戏嘉年华，赢取液晶显示器！ 
> 
> 
> 
> 
> 
> ___
> Tinyos-help mailing list
> Tinyos-help@Millennium.Berkeley.EDU
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

-- 
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] - A mote capture and send the message to two other

2007-12-06 Thread Michael Schippling


You need to wait for the sendDone() of the first message
before posting the send of the second, do the "post send03()"
for withing sendDone().

MS

Tiago Wanderley wrote:

Hi,

first, I would warn that my English is not good. =D

I'am with problem, captured a date e turn on leds if this value is 
greater than 0x300. After I sent the value for other two motes, using 
the tasks send02() and send03(). The task send02() is executed with 
success, the mote of id 02 receive the message,but the send03 () was not 
executed, consequently the mote of id 03 has not received the message. 
Below the part of the code involved:


  task void send03()
  {
SenseMessage *message3 = (SenseMessage *)data3.data;
if (!pending) {
atomic {
pending = TRUE;
message3->value = value;
}
message3->source = TOS_LOCAL_ADDRESS;
if (! call SendMsg.send(03, sizeof(SenseMessage), &data3))  
   
pending = FALSE;

  }
  }
 
  task void send02()

  {
SenseMessage *message = (SenseMessage *)data.data;
if (!pending) {
atomic {
pending = TRUE;
message->value = value;
}
message->source = TOS_LOCAL_ADDRESS;
if (! call SendMsg.send(02, sizeof(SenseMessage), &data))  
   
pending = FALSE;

  }
  } 
 
  async event result_t ADC.dataReady(uint16_t val) {

atomic value = val;
post send02();
pending = FALSE;
post send03();
display(val);
return SUCCESS;
  }

Help-me... =D





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


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] Support Vector Machine on sensors

2007-12-06 Thread Michael Schippling


If you can do it with a 16 bit integer multiply
using less than 4KB of RAM you can do it on a Micaz...

MS

AIGroup wrote:

Hi all.

I'm interested to develop Support Vector Machines using Micaz motes and 
TinyOs

But, I have any doubts about power of computation of these sensors.
Does anybody have an experience about this topic?
Thanks in advance

Roberto




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


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help]： Which file has the de finition of TOS_LOCAL_ADDRESS??

2007-12-07 Thread Michael Schippling

a quick file find turns up:  tos/system/tos.h
MS

Renee Azhen wrote:
> Dear all:
> Could anyone tell me:
> In which file "TOS_LOCAL_ADDRESS" was declared and defined??
> Really Thanks
> Sam
> 
> 
> 进入雅虎游戏嘉年华，赢取液晶显示器！ 
> 
> 
> 
> 
> 
> ___
> Tinyos-help mailing list
> Tinyos-help@Millennium.Berkeley.EDU
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

-- 
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] what's the prefix "TOSH_" stand for? I

2007-12-08 Thread Michael Schippling


TOSH is probably something like TinyOSHardware,
it's an arbitrary string used to distinguish
internal defines.

And yes, "tos" is tinyos.

MS


zhiyong yang wrote:
1,what's the prefix "TOSH_" stand for? I have seen it used in many 
macros,e.g. TOSH_sched_entry_T;

TOSH_MAX_TASKS = 1 << TOSH_MAX_TASKS_LOG2;TOSH_SET_PIN_DIRECTIONS();..
2,Does the " tos" in \Crossbow\cygwin\opt\MoteWorks\tos\system  stand 
for tinyOS?

thank you!




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


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] what's the prefix "TOSH_" stand for? I

2007-12-08 Thread Michael Schippling


wow, I guessed something about tos correctly...
that koolaide must be working.
MS


Philip Levis wrote:


On Dec 8, 2007, at 6:08 AM, Michael Schippling wrote:


TOSH is probably something like TinyOSHardware,
it's an arbitrary string used to distinguish
internal defines.

And yes, "tos" is tinyos.



That's correct; TOSH was originally an acronym for TinyOSHardware.

Phil


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] Installing JNI gives an error on XUBUNTU

2007-12-08 Thread Michael Schippling


Assuming that the .so was generated, you can just move it to the JRE bin --
I think bin is the right place -- Or you can hack around and see why the
target dir is not set - at all - in the makefile.

MS

Prashanth Shenoy wrote:

Hi everybody,

I am using X-ubuntu and tinyOS-1.1.14

I am trying to use the Listen application provided in the tinyos Tuto.

When I do 
 java net.tinyos.tools.Listen 


I get the followinfg error

 getenv JNI library not found. Env.getenv will not work
 (please consult installation directions in
 tinyos-1.x/tools/java/net/tinyos/util/Env.INSTALL)
 Error on [EMAIL PROTECTED]:9001: java.net.ConnectException: 
Connection refused

So  int the $TOSROOT/tools/java/jni I tried make install but i get the 
following error

sudo make install ( as suggested in the Env.INSTALL )

make -f Makefile.Linux "JDK=." "JNI=" install
make[1]: Entering directory `/opt/tinyos-1.1.14/tools/java/jni'
install libgetenv.so ""
install: target `' is not a directory: No such file or directory
make[1]: *** [install] Error 1
make[1]: Leaving directory `/opt/tinyos-1.1.14/tools/java/jni'
make: *** [install] Error 2

I dont know what could be the problem... I have the right PATH variables for 
JAVAHOME/jre

I even tried the alternative suggested in nv.INSTALL about libgetenv.so. This 
dosent work too.

Any suggestions
_
Put your friends on the big screen with Windows Vista® + Windows Live™.
http://www.microsoft.com/windows/shop/specialoffers.mspx?ocid=TXT_TAGLM_CPC_MediaCtr_bigscreen_102007
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] how to trigger a transistor

2007-12-09 Thread Michael Schippling


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" circuits to see the easiest connection option.

MS


Urs Hunkeler wrote:

Hi,

I don't know about the tmotesky kit. I was referring to TinyOS 2.x. For 
TinyOS 1.x have a look at how they control the LEDs. Interesting files 
would be tos/system/LedsC.nc and tos/platform/telosb/hardware.h.


Cheers,
Urs


n subhash wrote:

but those components are not available
i'm using tmotesky kit can u just any method for tmotesky kit


On Dec 8, 2007 6:48 PM, n subhash <[EMAIL PROTECTED]> wrote:


thanq alot i'll try to implement


On Dec 8, 2007 4:52 PM, Urs Hunkeler <[EMAIL PROTECTED]> wrote:


Hi,

Use the GeneralIO interface. You can use, for example, the set(),
clear() and toggle() functions to control the pin. The pins are defined
in the HplMsp430GpioC module. Wire the pin you want from this module to
the module Msp430GpioC.HplGeneralIO. The wiring will probably look
something like:

---
components new Msp430GpioC();
components HplMsp430GeneralIOC;

Msp430GpioC.HplGeneralIO -> HplMsp430GeneralIOC.Port62 ;
YourModule.YourTransistorInterface -> Msp430GpioC;
---

where YourModule is the module where you run your code. This module
should use an interface of type GeneralIO (here called
YourTransistorInterface).

Look at the tmote datasheet which pin is connected on port 6.2 (hint:
it's on the 10-pin connector).

Cheers,
Urs


n subhash wrote:

please me how to trigger an external  transistor by using tmotesky







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


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] problem running java tools


I've never seen that error before. Perhaps your Java install is bad.

First make sure your PATH points to the correct Java. You said (later)
that it's in C:/program files/java so your PATH should contain something
like:  C:/program files/java/jdk1.5.0_07/bin
I dislike putting Java in "Program Files" because the space in the
directory name causes problems without very careful quoted name management,
so you might also try reinstalling in, say, C:/Java...

Anyway, try:  type javac
and make sure it comes up with the right one.
Then try hand compiling a simple java file:  javac somefile.java
and see if you get the same problem.

MS

Nashwa Abo Elneel wrote:

Hi,

I am trying to run the oscilloscope example in lesson 6 (the 
installation on the mote was successful), however when i start the 
normal procedure by typing "make" in the java directory i get a lot of 
errors like:


exception in thread "main" java.lang.NoClassDefFoundError: 
com/sun/tools/javac/main


does anybody have an idea how to solve such error?
i am using jdk1.5 installation and i have installed the javax.comm 
package in the same way as the installation steps


Regards,
Nashwa


Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try 
it now. 






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


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] message using UART


There are a few problems with your use of send(), but you should still
receive a message and toggle the Leds. 1) you need to specify the size
of the payload, not the size of the whole TOS_Msg, 2) when receive()
returns the message pointer, it may be freed or overwritten before it
can be resent so you should copy it before send()ing, 3) I'm hesitant
to call send() from an event so I always post a new task to do it.

What are you using to generate the actual message?
If the CRC is not calculated correctly it may be dropped.

Also you can cut out the SerialForwarder middleman and just use you message
send program and/or Listen to talk directly to the serial port.

For an example of something that works, sort of like what you want but is
probably more complicated than necessary, see my old code:
 http://www.etantdonnes.com/Motes/robocode.tar.gz

MS

[EMAIL PROTECTED] wrote:
i have write the following small program (with name sendreceive) that i 
expect work like this:
1- send a packet from SerialForwarder to a directly connected mote 
(micaz) via serial port (COM,mib510)

2- the micaz response by toggling the red led on it
3- then resend the same packet back to the SerialForwarder
4- and toggle the green led
 
i bush a all 1s data packet with destination address of "FF" and handler 
ID of "0A"

but there is no response at all
it neither toggle red nor green led and no packet returned to 
SerialForwarder
 
please help
 
 
//sendreceive.nc

configuration sendreceive { }
implementation
{
components Main, sendreceiveM, LedsC, UARTComm as Comm;
Main.StdControl -> sendreceiveM;
sendreceiveM.Leds -> LedsC;
sendreceiveM.CommControl -> Comm;
sendreceiveM.ReceiveMsg -> Comm.ReceiveMsg[32];
sendreceiveM.SendMsg -> Comm.SendMsg[10];
}
 
 
//sendreceiveM.nc

module sendreceiveM{
provides interface StdControl;
uses {
interface Leds;
interface StdControl as CommControl;
interface SendMsg;
interface ReceiveMsg;
}
}
implementation
{
command result_t StdControl.init() {
call Leds.init();
call CommControl.init();
return SUCCESS;
}
command result_t StdControl.start() {
call CommControl.start();
return SUCCESS;
}
command result_t StdControl.stop() {
call CommControl.stop();
return SUCCESS;
}
event result_t SendMsg.sendDone(TOS_MsgPtr sent, result_t success) {
call Leds.greenToggle();
return SUCCESS;
}
event TOS_MsgPtr ReceiveMsg.receive(TOS_MsgPtr m) {
call Leds.redToggle();
call SendMsg.send(TOS_UART_ADDR, sizeof(*m),m);
return m;
}
}




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


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] Tunit setup on osx: serial port in tos-bsl problem


Does motelist work? I think the BSL program uses some moral equiv of such
to find the tmote port.

MS

Matthias Woehrle wrote:

Hi,

I got a problem concerning setting up Tunit on my macbook (osx-tiger). I 
run Kevin Klues' setup 
(_http://docs.google.com/View?docid=ajjph9mvqk3z_bchp66xkmgk6n&pli=1_ 
).


The specific problem is that when the bootstraploader is executed, the 
serial port is not set (in my case: /dev/tty.usbserial-M4AJRG09, a tmote).


 [java] installing telosb binary using bsl
 [java] tos-bsl --telosb -c  -r -e -I -p build/telosb/main.ihex.out-0
...
 [java] MSP430 Bootstrap Loader Version: 1.39-telos-8

 [java] An error occoured:
 [java] could not open port: [Errno 2] No such file or directory: '-r'
 [java] make: *** [program] Error 1

However, serial forwarder initialization works before that:
[java] 160 [main] DEBUG com.rincon.tunit.run.TestRunManager  - 
Creating serial forwarder serial@/dev/tty.usbserial-M4AJRG09:telosb
 [java] 205 [Thread-1] DEBUG com.rincon.tunit.sf.Sf  - 
serial@/dev/tty.usbserial-M4AJRG09:telosb.9100: 
serial@/dev/tty.usbserial-M4AJRG09:115200: resynchronising
 [java] 205 [Thread-1] DEBUG com.rincon.tunit.run.TestRunManager  - 
serial@/dev/tty.usbserial-M4AJRG09:115200: resynchronising
 [java] 208 [main] DEBUG com.rincon.tunit.run.TestRunManager  - 
Disconnecting all serial forwarders
 [java] 2220 [Thread-0] DEBUG com.rincon.tunit.sf.Sf  - 
serial@/dev/tty.usbserial-M4AJRG09:telosb.9100: server stopped
 [java] 3221 [main] DEBUG com.rincon.tunit.run.TestRunManager  - 
Serial forwarders initialized successfully


Some output from the ant execution is attached for debug as well as my 
build.xml and the tunit.xml.
Note that the build.xml is patched with a fork in order 
to accommodate for a problem with osx's AquaLookAndFeel.












  

  














  












  


































  


  













































Note that when I would do this manually, everything works just fine, so 
I guess it might be something in the parser.

Anybody has this running on osx?

Regards,

Matthias




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


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] how to trigger a transistor


I'm cc'ing this back to the help list to keep a record...

Follow the trail of  tos/platform/{tmote,telosb}/UserButton*.nc to
get a general idea of how MSP430GeneralIO works, for input at least.

But, luckily enough, I just finished a tmote program that twiddles
a bunch of inputs and output transistors to run a set of stepper motors.
So the basic idea is:

In the config file, do something like this --

  components MSP430GeneralIOM;
  PanTiltP.USOut0 -> MSP430GeneralIOM.Port66;

where PanTiltP.USOut0 is your module and arbitrary port name, and
Port66 is the GIO name for port-6 bit-6 which just happens to be
pin 1 of the 6 pin expansion connector...I just uploaded my tmote
pinout cheat sheet:  http://www.etantdonnes.com/Motes/TMOTEpins.txt
if anyone has any comments, changes, or additions please tell me.

Then in your actual code module (PanTiltP.nc in my case) do this --

  uses interface MSP430GeneralIO as USOut0; // PORT66

// init the port as output
call USOut0.makeOutput();  // or makeInput() to go the other way...
call USOut0.selectIOFunc();

// toggle it
call USOut0.setLow();
call USOut0.setHigh();

// extra credit, to use as input:
boolean x = call USIn0.get();


MS

n subhash wrote:

yes i saw tos/platform/msp430/MSP430GeneralIOM.nc  but how to use it
for triggerring a transistor














On 12/9/07, Michael Schippling <[EMAIL PROTECTED]> wrote:

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" circuits to see the easiest connection option.

MS


Urs Hunkeler wrote:

Hi,

I don't know about the tmotesky kit. I was referring to TinyOS 2.x. For
TinyOS 1.x have a look at how they control the LEDs. Interesting files
would be tos/system/LedsC.nc and tos/platform/telosb/hardware.h.

Cheers,
Urs


n subhash wrote:

but those components are not available
i'm using tmotesky kit can u just any method for tmotesky kit


On Dec 8, 2007 6:48 PM, n subhash <[EMAIL PROTECTED]> wrote:


thanq alot i'll try to implement


On Dec 8, 2007 4:52 PM, Urs Hunkeler <[EMAIL PROTECTED]> wrote:


Hi,

Use the GeneralIO interface. You can use, for example, the set(),
clear() and toggle() functions to control the pin. The pins are defined
in the HplMsp430GpioC module. Wire the pin you want from this module to
the module Msp430GpioC.HplGeneralIO. The wiring will probably look
something like:

---
components new Msp430GpioC();
components HplMsp430GeneralIOC;

Msp430GpioC.HplGeneralIO -> HplMsp430GeneralIOC.Port62 ;
YourModule.YourTransistorInterface -> Msp430GpioC;
---

where YourModule is the module where you run your code. This module
should use an interface of type GeneralIO (here called
YourTransistorInterface).

Look at the tmote datasheet which pin is connected on port 6.2 (hint:
it's on the 10-pin connector).

Cheers,
Urs


n subhash wrote:

please me how to trigger an external  transistor by using tmotesky



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

--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew


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

Re: [Tinyos-help] Random number


I "think" that the nodeID is used as the random seed so each
node should get a different sequence of values. However they
probably won't change from run to run. You might need to hack
into the random() function and add some noise from an open ADC
channel or something...

MS

Paul wrote:

Hi all

I need to, during startup decides out of NUM_NODES nodes, which of the 
NUM_TASKERS nodes will perform certain tasks.


Previously, I have identified these NUM_TASKERS inside the Makefile 
using -DTASK_NODE=1, -DTASK_NODE=6, 


However, I want the task nodes to be different for each run.

But, using Random () on each node might not work correctly here since 
the seeds for each node is different?


What is the  proper way to do this?

Thanks.
 
Regards,

Paul




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


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] TinyOS and standard C libraries


If you have the source for the libs you should be able to
compile them for which ever controller you are using. There
is standard C lib function support, meaning most of "libc".
But you might have to stub some things out, like printf()
probably.

Search this list for advice on linking in C functions,
I seem to remember there are a few hoops to negotiate.

Be aware that all Float math is done in software
and you don't have much RAM to work with, so don't
expect blinding performance.

MS

Ville-Pekka Seppä wrote:

Hi,

I would like to do some basic signal processing on the a telosb mote and 
was wondering if I could use Gnu Scientific Library (GSL) with TinyOS. 
Is it possible to use any standard C libraries (math.h?) with TinyOS at 
all, because they don't provide "interfaces" or other NesC stuff ?


Ville

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


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] using math.h in tinyos 2 for telosb or micaz


For the MSP there is:
opt/msp430/msp430/include/math.h
which contains:
extern float sqrtf _PARAMS((float));
(note the 'f' for float rather than double)... however it is in a
"#ifndef _REENT_ONLY" block which may or may not be def'ed...

And for the AVR:
usr/avr/include/math.h
has:
extern double sqrt(double __x) __ATTR_CONST__;
although I "thought" the ATMEGA only supported floats as well...

MS

SANG Junjun wrote:

It seems that there is no sqrt support for msp430.

On Dec 11, 2007 2:47 PM, prashan wanigasekara <[EMAIL PROTECTED]> wrote:

Hi everyone,

This is my first post to the forum. I am programming in tinyos-2.x. and
using micaz, telosb motes. My problem is

1. How to use math.h in tinyos-2.x?  I cannot find a suitable header file
anywhere. Could you recommend a place to download it ?
2. I want to use sqrt (square root) function. Is there way to use this
without using math.h?
3. Is math.h even implemented in tinyos-2.x for micaz?
4. Is the math.h (tinyos-2.x) for micaz different from telosb? (Platform
dependant?)


I would greatly appreciate your help.

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







--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] Listen program and statistics ?


Anything is (im)possible with software...just a little Java-foo is needed.

Look into the MIG tool for generating message classes, I believe it is
covered in the tutorial. With the right class you can parse the message
and send data to any file you like using standard Java streams.

Or you can hack Listen itself. If I remember, it uses a "Dump" class
to write bytes and you can change that class to write anything you like.
If it was me, I would just modify it to print a header and converted
decimal value to stdout (as it pretty much does now)...say:
A 563
B 36916
A ...
and redirect the output into a file like:
java Listen > data.txt

Note that the two-byte hex values that you show are in little-endian
order (usuallynx_g types are big-endian), so "33 02" is probably
0x0233, which is 563 decimal.

Then you can manipulate the text file however you like (see: sort) and
load it into Excessell...

MS

Mona.baher wrote:

Hi All,
As you know that Listem program create a packet source and  prints out
every packet coming from the mote like:
00 FF FF 02 33 09 00 A0 A0 B2 34 90 33 02

So my question  is how to break this fields of date into 2 bytes each
and store each 2 bytes into  separate xls files for analyses ? Is
there any tool for statistics which does that? or what do you think ?
 I want to achieve the following :  Store the 33 02 in file A  and 34
90 in file B and  so on for all the packets.

Thank you for any help
  Mona
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] Help: UART rx function


I'm not sure exactly how the UART works, or whether it's different for
various platforms...but...I think there is an event you can implement
to get bytes as they arrive so you don't have to do your own interrupt
checking...e.g. tos/interfaces/HPLUART.nc has put() and get() that hides
the lowlevel implementation. Perhaps that will help?

MS


[EMAIL PROTECTED] wrote:
Hello! 

I have to send and receive with the UART extention of my tmote-sky. I have a functionaly interfate that change the TTL signal 


with the RS-232 standard of the pc.
To send data from the tmote there aren't problems. 
There are some problems with the receive the packet of byte...

This program below send a packet of byte and receive one single byte perfectly:

event void ResourceCmd.granted(uint8_t rh)
{
int i;
bool rx = FALSE;

// Make any necessary UART changes
call UartControl.setClockSource(SSEL_SMCLK);
call UartControl.setClockRate(UBR_SMCLK_9600, UMCTL_SMCLK_9600);

// Send a packet
for (i = 0; i < 10; i++)
{
call UartControl.tx( READ_DATA[i] );
while (! call UartControl.isTxEmpty() );
}

// rx a single byte
while (! call UartControl.isRxIntrPending())
{//wait for data in rx buffer

field_string[0] = call UartControl.rx();
if (field_string[0] == 'A')
call Leds.greenToggle();
}
call ResourceCmd.release();
}

Since I haven't to receive a single byte but a packet of byte, I think to insert in the rx while cicle field_string[i] with a 

for cicle that increment the variable i. 
In a simple manner I try to receice 2 byte.

I try with somuch type of solution but with bad results.
A solution that seem functionally is:


// rx a packet of 2 byte
while (! call UartControl.isRxIntrPending() && rx == FALSE)
{
//wait for data in rx buffer

code[0] = call UartControl.rx();

if (code[0] == 0x41)
{
call Leds.greenToggle();
rx = TRUE;
}
}
rx = FALSE;
while (! call UartControl.isRxIntrPending() && rx == FALSE)
{
//wait for data in rx buffer

code[1] = call UartControl.rx();

if (code[1] == 0x0D)
{
call Leds.redToggle();
rx = TRUE;
}
}

for (i = 0; i < 12; i++)
code[i]= 0x00;

call ResourceCmd.release();
rx = FALSE;

From the pc I send to the mote with "free serial port monitor" this packet "0x41, 0x0D" and the red and green led doesn't 


turn on forever, but only sometimes. Sometimes the green led turn on, sometimes the red led, sometimes all the led and 


sometimes no one.

This method can function with some change?
If someone know a metod to receive and save a string of byte can help me, 
please?

Thank you so much



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


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] Radio files


To get a better view of where stuff comes from
(assuming your program compiles...) put this in the Makefile:
PFLAGS += -v
then ncc will print all the source (but not header...g)
files with their full path in the order they are used.

MS

Michiel Konstapel wrote:

The nesC compiler looks for components in several directories:

-  The current directory

-  Include directories passed on the command line 
(-I), often by setting the CFLAGS variable in the Makefile


-  Directories specified in your platform’s .platform file @includes

-  $TOSDIR/system

 

I think that’s all but I might’ve missed something. I guess you’re using 
a mica2? Then those files come from $TOSDIR/platforms/mica2. If you look 
at $TOSDIR/platforms/mica2/.platform, you’ll see what directories get 
added to the search path (%T is replaced by $TOSDIR):


  %T/platforms/mica

  %T/platforms/mica2/chips/cc1000

  %T/chips/cc1000

  %T/platforms/mica2/chips/at45db

  %T/platforms/mica/chips/at45db

  %T/chips/at45db

  %T/chips/atm128

  %T/chips/atm128/adc

  %T/chips/atm128/i2c

  %T/chips/atm128/pins

  %T/chips/atm128/spi

  %T/chips/atm128/timer

  %T/lib/timer

  %T/lib/serial

  %T/lib/power

 


HTH,

Michiel

 


*SOWNet logo_KL ***

* *

*Michiel Konstapel*

Software Engineer

 


T: +31 (0)15 26 00 44 6

F: +31 (0)15 26 00 40 5

W: www.sownet.nl 

 

 

 

*From:* [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] *On Behalf Of *Khew 
U-Wei

*Sent:* dinsdag 11 december 2007 3:16
*To:* tinyos-help@Millennium.Berkeley.EDU
*Subject:* [Tinyos-help] Radio files

 


Hi Everyone,

 

I am using a file, RipsDataCollectionC.nc which uses the LedsC, 
CC1000ControlM, CC1000RadioC, ADCC and HPLCC1000M files.



However, I am working in the directory which does not have these radio 
files. How is it possible?


Hope to hear from you soon. THank you.

BEst regards,
U-Wei




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


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] message using UART


BCastInject _should_ format messages correctly and do the CRC,
but I've not used it so I can't swear to how to go about it.

As I said I suspect there is something wrong with your message
formatting, so check though the whole thing. SerialForwarder,
to my knowledge does just that, forward, so if the message is
not correct to start with it won't get better. You can see how
I went about sending and receiving messages in the Java portion
of the code I refed, which is mostly based on Listen.java.

MS

[EMAIL PROTECTED] wrote:

Thank you Michael…

I appreciate your help …

 .

 

Regarding the middleman.. I have peevishly cutoff the serial forwarder 
and I  used my own C# application but I couldn’t calculate the CRC, 
therefore I faced many problems.


So I want to use serial forwarder  I guess that .. I shouldn’t calculate 
the CRC.


 


Regarding the actual message I am using to generate it the BcastInject .

 

Also I update the code to the below one, and tested it but nothing 
worked.. exactly I removed the two lines


call SendMsg.send(TOS_UART_ADDR, sizeof(*m),m);

call Leds.greenToggle();

from it .

 


//sendreceive.nc

configuration sendreceive { }

implementation

{

components Main, sendreceiveM, LedsC, UARTComm as Comm;

Main.StdControl -> sendreceiveM;

sendreceiveM.Leds -> LedsC;

sendreceiveM.CommControl -> Comm;

sendreceiveM.ReceiveMsg -> Comm.ReceiveMsg[32];

sendreceiveM.SendMsg -> Comm.SendMsg[10];

}

 

 


//sendreceiveM.nc

module sendreceiveM{

provides interface StdControl;

uses {

interface Leds;

interface StdControl as CommControl;

interface SendMsg;

interface ReceiveMsg;

}

}

implementation

{

command result_t StdControl.init() {

call Leds.init();

call CommControl.init();

return SUCCESS;

}

command result_t StdControl.start() {

call CommControl.start();

return SUCCESS;

}

command result_t StdControl.stop() {

call CommControl.stop();

return SUCCESS;

}

event result_t SendMsg.sendDone(TOS_MsgPtr sent, result_t success) {

return SUCCESS;

}

event TOS_MsgPtr ReceiveMsg.receive(TOS_MsgPtr m) {

call Leds.redToggle();

 


return m;

}

}

 




- Original Message -
From: Michael Schippling
Date: Monday, December 10, 2007 9:50 am
Subject: Re: [Tinyos-help] message using UART

 > There are a few problems with your use of send(), but you should still
 > receive a message and toggle the Leds. 1) you need to specify
 > the size
 > of the payload, not the size of the whole TOS_Msg, 2) when receive()
 > returns the message pointer, it may be freed or overwritten
 > before it
 > can be resent so you should copy it before send()ing, 3) I'm hesitant
 > to call send() from an event so I always post a new task to do it.
 >
 > What are you using to generate the actual message?
 > If the CRC is not calculated correctly it may be dropped.
 >
 > Also you can cut out the SerialForwarder middleman and just use
 > you message
 > send program and/or Listen to talk directly to the serial port.
 >
 > For an example of something that works, sort of like what you
 > want but is
 > probably more complicated than necessary, see my old code:
 > http://www.etantdonnes.com/Motes/robocode.tar.gz
 >
 > MS
 >
 > [EMAIL PROTECTED] wrote:
 > > i have write the following small program (with name
 > sendreceive) that i
 > > expect work like this:
 > > 1- send a packet from SerialForwarder to a directly connected
 > mote
 > > (micaz) via serial port (COM,mib510)
 > > 2- the micaz response by toggling the red led on it
 > > 3- then resend the same packet back to the SerialForwarder
 > > 4- and toggle the green led
 > >
 > > i bush a all 1s data packet with destination address of "FF"
 > and handler
 > > ID of "0A"
 > > but there is no response at all
 > > it neither toggle red nor green led and no packet returned to
 > > SerialForwarder
 > >
 > > please help
 > >
 > >
 > > //sendreceive.nc
 > > configuration sendreceive { }
 > > implementation
 > > {
 > > components Main, sendreceiveM, LedsC, UARTComm as Comm;
 > > Main.StdControl -> sendreceiveM;
 > > sendreceiveM.Leds -> LedsC;
 > > sendreceiveM.CommControl -> Comm;
 > > sendreceiveM.ReceiveMsg -> Comm.ReceiveMsg[32];
 > > sendreceiveM.SendMsg -> Comm.SendMsg[10];
 > > }
 > >
 > >
 > > //sendreceiveM.nc
 > > module sendreceiveM{
 > > provides interface StdControl;
 > > uses {
 > > interface Leds;
 > > interface StdControl as CommControl;
 > > interface SendMsg;
 > > interface ReceiveMsg;
 > > }
 > > }
 > > implementation
 > > {
 > > command result_t StdControl.init() {
 > > call Leds.init();
 > > call CommControl.init(

Re: [Tinyos-help] tinyos-1.x-tools.rpm cannot locate java


search this list for advice on "locate-jre" which never seems to
work correctly. That's how the installers usually find java.

Also, I'm not too happy with /usr/bin/java unless it is a link to
something like "...jdk1.5.0_07/bin/java", because one usually has
a specific JDK installed someplace other than bin.

MS

rodolfo de paz wrote:

Hello all,

I have change my OS to Suse Linux 10.3 and when I am trying to install 
tinyos-1.x I have the following error:


rpm output:
Cannot locate java - is it installed?
error: %post(tinyos-tools-1.1.0-1.i386) scriptlet failed, exit status 1

I don't know where it the problem. I checked the system with the command 
"type java" and I obtained


java is /usr/bin/java

So it seems to be fine... do you have any idea??

Thanks in advance,

--
Rodolfo




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


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] can I use pin 8 (I2C Data) on Tmote as Digital I/O pin?


Unfortunately the two I2C pins are shared with the radio
so it's best (IMHO) to avoid using them...if you need more
I/O the SVS "connector" has one more usable pin and you
could solder into where the onboard sensors go too.

MS

yicheng wrote:

Hi Folks,

 

I want to use pin 8, which is I2C data pin on Tmote sky as a digital I/O 
pin, is it possible? Here is my code example:


 


Configuration file:

Myapp.digitOut -> MSP430GeneralIOC.Port31;

 


Implementation file:

uses interface MSP430GeneralIO as digitOut;

 


init function:

  call digitOut.setLow();

  call digitOut.makeOutput();

  call digitOut.selectIOFunc();

 


What does “I2C data” pin mean?

 


Thanks!
Yicheng




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


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

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

Re: [Tinyos-help] Input stuck high


You have configured it as an input, right?
Search this list for TOSH_ASSIGN_PIN if you don't know how...

Otherwise, as Urs says, how are you toggling it hardwarewise?

MS


Elle Mills wrote:
Im using D0 input on mda300, but it seems to be stuck high. Why would an 
input be stuck high? How do I clear it so I can use it?


Thanks




___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help]: how to read message from the serial port of a pc??

Along with the tutorials, look at the SimpleCmd
demo app for reading and writing of messages.
MS


Renee Azhen wrote:
> Dear all:
> I want to transmit image via my sensor node
> the image was stored in a pc which is connectted to a telosb node,
> so I want to install a program into the node to read image from the pc, 
> and then tranmit it via the wsn network to another node.
> but now I don't know how to read message from a pc.
> could anyone give me some suggestion??
> thanks
> Sam
>  
> 
> 
> 
> 天生购物狂，狂抢购物券，你还等什么！ 
> 
>  
> 
> 
> 
> 
> 
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

-- 
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] recording sound with micasb


Assuming you have received and collated the data on a PC of some sort,
look into the java media lib/jars for ways to create standard audio
file formats, like .WAV or .AIF. Also some editing programs, like
Adobe Audition, allow you to import raw text files -- but I've not
tried it myself.
MS


Diaz Cerio Unai wrote:

Hello
 
I'm working with a micaz and a micasb and I want to record sound and 
voice with the microphone of the micasb.
I'm taking measures of the microphone in a high frecuency, but I don't 
know how to convert them in a audio file.

If nobody knows how to do I will be very pleased.
Thank you and excuse me if my english is bad.
 
Bye.





___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] recording sound with micasb


I was trying to be polite...heh...

With the micas at least, you can sample at an early-telephone audio
rate if you can work out the timer issues (which the original poster
indicated was a fact). But you can only store a short sample period,
and then it takes _forever_ to transmit -- although a back-o-env
calculation indicates that one could keep up with something like
5-6k 8 bit samples a sec on a micaz. And I would be somewhat
willing to bet that the AVR doesn't have the HP to do any sort
of compression in real time, so there you have it...

MS


John Griessen wrote:

Michael Schippling wrote:
Assuming you have received and collated the data 


That's a hard one.  The sampling rate gets you low frequency audio only.
Audio is not really a MSP430 function, and needs external A2D, or 
digital mics,

and data reduction at the mote before it will be practical.

Anyone developing such?

John Griessen



--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] How can I calculate the Packet Error Rate with a telosb motes link using tinyos-2 ?


I did something like this with micas under 1.x.
You can see my results at: http://www.etantdonnes.com/Motes/report_micaz/

MS


sergio mena doce wrote:

Hello,
 
I'm working with telosb motes using tinyos-2.x and I'm trying to 
calculate the Packet Error Rate. I would like to know if there is an 
specific tinyos application for calculate the packet error rate or what 
tinyos application can you advice me to modify for that goal? I'm trying 
to calculate the packet error rate between several motes by modifying 
the application tinyos-2.x/apps/tests/cc2420/TestPacketLink; if you 
want, request me my modified application code to send you to see and 
give me your opinion.
 
Thanks for reading.
 
I hope your reply.
 
Sergio.



Sigue al minuto las principales noticias de tu ciudad MSN Deportes 






___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] can I use pin 8 (I2C Data) on Tmote as Digital I/O pin?


It's underneath the USB connector on the 'back' side of the board.
See the tmote manual for location...
However I couldn't find anything that says which pin is which, so:
The pin nearest the + battery connection is: #2 SVSout PORT57

MS

[EMAIL PROTECTED] wrote:

Hi Michael,

Thanks for your reply. Could you tell me where the SVS "connector" is in Tmote?

Best,
Yicheng
==Original message text===
On Wed, 12 Dec 2007 12:21:37 am + Michael Schippling wrote:

Unfortunately the two I2C pins are shared with the radio
so it's best (IMHO) to avoid using them...if you need more
I/O the SVS "connector" has one more usable pin and you
could solder into where the onboard sensors go too.

MS

yicheng wrote:

Hi Folks,

 

I want to use pin 8, which is I2C data pin on Tmote sky as a digital I/O 
pin, is it possible? Here is my code example:


 


Configuration file:

Myapp.digitOut -> MSP430GeneralIOC.Port31;

 


Implementation file:

uses interface MSP430GeneralIO as digitOut;

 


init function:

  call digitOut.setLow();

  call digitOut.makeOutput();

  call digitOut.selectIOFunc();

 


What does “I2C data?pin mean?

 


Thanks!
Yicheng




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




--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] recording sound with micasb


What I was thinking is that one could sample at around 6K and
get a whopping 1/2sec buffer at around a 3Khz bandwidth, which is
quite adequate for voice...But I don't know if you could send
sustained TOS_Msg's fast enough to 'stream'...

MS

MS

Janos Sallai wrote:

That's a hard one.  The sampling rate gets you low frequency audio only.


On the ATMega128, you can safely sample with setting the ADC prescaler to
5, which gives a sampling rate of 17723Hz (assuming the ADC clock freq is
7372800). Of course, you will need to make sure that interrupts are not
disabled for too long, otherwise you will lose samples.

Another question is how you store the audio samples. With 4k of RAM, out
of which 2.5-3k can be used as a sample buffer, you can roughly one sixth
of a second (assuming the 10-bit samples are trimmed to 8 bits).
Obviously, at this sampling rate, streaming audio data over the radio is
not an option.

Janos




___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: Tr : Re : [Tinyos-help] linking problems

My guess would be that there is a 'hidden' main() component
that sets the entry address "_start". The tos/system/RealMain.nc
might have something to do with this, but probably something needs
to be defined into the compiler or assembler to tie it all together...

Of course, if your controller's entry address IS 0x,
it's might JustWork(TM) as is.

mejda chouaieb wrote:

Hello,
i´m trying to compile the Null application, I type ´make isense´
when I compile because my new platform is called isense
yes when I commit out this line the program is not compiled. what do
you mean by a problem with the software setup?
I didn´t try to compile Blink right now, I want first to compile the
Null application for that platform.
Thanks

- Message d'origine
De : Urs Hunkeler <[EMAIL PROTECTED]>
À : mejda chouaieb <[EMAIL PROTECTED]>
Cc : tinyos-help@millennium.berkeley.edu
Envoyé le : Vendredi, 14 Décembre 2007, 9h58mn 07s
Objet : Re: [Tinyos-help] linking problems

Hi,

You probably won't get any errors anymore because the program is not
being compiled. I would guess that this line is the single most
important line in the whole Makefile :-)

I don't know the detailed meaning of this line, but the $(LDFLAGS) is
usually the set of flags specific for linking.

Your warning seems to indicate a problem with your software setup. What
is the exact command you use to compile? What application are you
trying
to compile? Do you manage to compile the Null application for the
desired platform? If so, what about Blink?

Cheers,
Urs

mejda chouaieb schrieb:

Hello All,
can someone please expalin to me the meaning of this line and if

something for linking is present here :

$(NCC) -o $(MAIN_EXE) $(OPTFLAGS) $(PFLAGS) $(CFLAGS)

$(WIRING_CHECK_FLAGS) $(COMPONENT).nc $(LIBS) $(LDFLAGS)

because when i copile for my new platform I have a linking error from

the toolchain:

/ba-elf/bin/../lib/gcc/ba-elf/4.1.2/../../../../ba-elf/bin/ld:

warning: cannot find entry symbol _start; defaulting to

and when I put # in front of this line this warning disappears !!!
Thanks for help

Yahoo! Mail innove : interface hyper pratique, messenger intégré,
couleurs - http://mail.yahoo.fr

_
Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail http://mail.yahoo.fr

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: 回复： Re: [Tinyos-help] How to get t he Sample code which is suitable to telosb pla tform?

There is a dreaded DemoSensor impl in the T1 msp430 directory
so that should handle the demo apps which use such, like O'scope.
After that, it's probably an exercise for the reader of the
tutorial to swap out sensors.

Other than the specifics of sensing devices, which would
necessarily be application dependent anyway, TOS _should_
hide platform details (or else one of it's design criteria
is a moot point). Did you have specific errors with some
of the apps?

MS

Urs Hunkeler wrote:
> Hi Sam,
> 
> You could try boomerang from the former Moteiv. Their Tmote Skys should
> be compatible with the telosb platform.
> 
> http://docs.tinyos.net/index.php/Boomerang
> 
> Cheers,
> Urs
> 
> 
> Renee Azhen schrieb:
>> dear friend:
>>   yeah, but my sensor can not use the Photo mudule, it is only humidity 
>> senses.
>>   many samples in /apps if installed into my sensor will occur an error. I 
>> found that most of the sample code is only suitable to mica/micasb, so do 
>> you know where I can get the corresponding code for my telosb node?
>>
>>   thanks
>>   Sam 
>>
>> Urs Hunkeler <[EMAIL PROTECTED]> 写道：
>>   Hi Sam,
>>
>> The MicaZ uses the same radio chip (cc2420). Usually applications for
>> the MicaZ also work on the Telosb platforms. The main differences are
>> the sensors, but they should be relatively straight forward to change.
>> Of course the Telosb platform use a different microcontroller (msp430
>> instead of an ATmega), but most differences should be handled
>> transparently by the compiler.
>>
>> The examples in the tutorials should work. I have the impression that
>> there are more examples for Telosb in TinyOS 2.x.
>>
>> Cheers,
>> Urs
>>
>> Renee Azhen schrieb:
>>> dear all:
>>> My platform is a telosb node.
>>> Most Sample code in /opt/tinyos 1.x/apps/ is for mica&mica2, then can not 
>>> work on telosb platform.
>>>
>>> so I want to get some sample application that are suitable to telosb 
>>> platform, could you tell me where and how I can get them??(Website, link or 
>>> )
>>>
>>> Thanks
>>> Sam
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

-- 
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] how much to include in a new platform, how much to reference


You should be able to use the .platform file to back reference to
other directories or explicitly add them with -I at NCC time.
Of course everything else will be included if you 'accidentally'
use modules which your platform doesn't support.

MS


John Griessen wrote:

 For instance:

for a file,

/tos/platforms/intelmote2/chips/cc2420/HplCC2420SpiC.nc
./tos/platforms/micaz/chips/cc2420/HplCC2420SpiC.nc
./tos/platforms/telosa/chips/cc2420/HplCC2420SpiC.nc

where I want to use the telosa version, since it is the same in the
ecosens1 platform:

HPL implementation of the SPI bus for the ChipCon CC2420 radio
 * connected to a TI MSP430 processor.
 *
 * @author Jonathan Hui <[EMAIL PROTECTED]>
 * @version $Revision: 1.4 $ $Date: 2006/12/12 18:23:44 $


should I reference instead of copying?  How do I reference?
telosb does it, but I'm not sure how...

Same question for the whole tos/platforms/telosa/chips/cc2420 dir.

Thanks,

John Griessen



--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: Re : Tr : Re : [Tinyos-help] linking problems

 bytes in ROM
   4 bytes in RAM
ba-elf-objcopy --output-target=ihex build/isense/main.exe build/isense/main.ihex
writing TOS image
_____

Thanks
- Message d'origine 
De : Michael Schippling <[EMAIL PROTECTED]>
À : mejda chouaieb <[EMAIL PROTECTED]>
Cc : tinyos-help@millennium.berkeley.edu
Envoyé le : Vendredi, 14 Décembre 2007, 18h48mn 09s
Objet : Re: Tr : Re : [Tinyos-help] linking problems

My guess would be that there is a 'hidden' main() component
that sets the entry address "_start". The tos/system/RealMain.nc
might have something to do with this, but probably something needs
to be defined into the compiler or assembler to tie it all together...

Of course, if your controller's entry address IS 0x,
it's might JustWork(TM) as is.

MS

mejda chouaieb wrote:

Hello,
i´m trying to compile the Null application, I type ´make isense´
 when I compile because my new platform is called isense
yes when I commit out this line the program is not compiled. what do
 you mean by a problem with the software setup?
I didn´t try to compile Blink right now, I want first to compile the
 Null application for that platform.
Thanks



- Message d'origine 
De : Urs Hunkeler <[EMAIL PROTECTED]>
À : mejda chouaieb <[EMAIL PROTECTED]>
Cc : tinyos-help@millennium.berkeley.edu
Envoyé le : Vendredi, 14 Décembre 2007, 9h58mn 07s
Objet : Re: [Tinyos-help] linking problems

Hi,

You probably won't get any errors anymore because the program is not
being compiled. I would guess that this line is the single most
important line in the whole Makefile :-)

I don't know the detailed meaning of this line, but the $(LDFLAGS) is
usually the set of flags specific for linking.

Your warning seems to indicate a problem with your software setup. What
is the exact command you use to compile? What application are you
 trying
to compile? Do you manage to compile the Null application for the
desired platform? If so, what about Blink?

Cheers,
Urs


mejda chouaieb schrieb:

Hello All,
can someone please expalin to me the meaning of this line and if

 something for linking is present here :

$(NCC) -o $(MAIN_EXE) $(OPTFLAGS) $(PFLAGS) $(CFLAGS)

 $(WIRING_CHECK_FLAGS) $(COMPONENT).nc $(LIBS) $(LDFLAGS)

because when i copile for my new platform I have a linking error from

 the toolchain:

/ba-elf/bin/../lib/gcc/ba-elf/4.1.2/../../../../ba-elf/bin/ld:

 warning: cannot find entry symbol _start; defaulting to 

and when I put # in front of this line this warning disappears !!!
Thanks for help






   
 

Yahoo! Mail innove : interface hyper pratique, messenger intégré,
 couleurs - http://mail.yahoo.fr





 _ 
Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail http://mail.yahoo.fr


___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help




--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] global function in nesc

2007-12-15 Thread Michael Schippling

Won't that make multiple copies of the 'global' function,
with module specific extended names, in the final code?
MS

Kevin Klues wrote:
Again, bad style, but there's nothing really preventing you from just 
creating a c-style function in a header file, and then #including it in 
any component you wish to use it in. 

You can even declare it in a header file, #include that file in any 
components you wish to use it, and then implement it within the body of 
one of your TinyOS modules so that it will have access to the variables 
defined in that module.  To go this route, you need to add some nesC 
attributes to your function definition though.  Take a look at the 
defintiion of uart_putchar() in tos/lib/printf/PrintfP.nc for an 
example.  And take a look at chapter 9 of the TinyOS programming Manual 
to understand what these attributes are doing.

http://csl.stanford.edu/~pal/pubs/tinyos-programming.pdf

Kevin

On Dec 14, 2007 8:12 AM, Greg Hackmann < [EMAIL PROTECTED] 
> wrote:

Michiel Konstapel wrote:
 >> I'm wondering whether I can define global function.
 >> The global function mean, I define a function in
 >> component A, and I can call this function in component
 >> B without using interface, just call the function directly?
 >
 > No, all interaction between components has to go through the
commands and
 > events they define in their interfaces. Well, you could probably
hack your
 > way there, but you're not really supposed to.

Actually, you can have components provide and use commands and events
that aren't tied to any interfaces; e.g.:

module SomeComponentP {
 provides command bool someCommand(uint8_t param);
}
implementation {
 command bool someCommand(uint8_t param) {
   ...
 }
}

This feature is used in a handful of places in TinyOS 2.0, like the
TOSSIM ActiveMessage layer.  See
tos/lib/tossim/ActiveMessageAddressC.nc and
tos/lib/tossim/TossimActiveMessageP.nc for an example.

Doing this is arguably bad style, but it's possible nonetheless.

Greg Hackmann
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu

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

--
~Kevin

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] How to get the Sample code which is suitable to telosb platform?

Well, isn't this nice... "portable" TOS demo apps have
some platform dependencies defined into them...

SimpleCmd uses a "Pot" component that is specific to the
mica (NOT mica2 or micaz, _mica_) platform. You may be able
to just go edit out references to "Pot", since it was used
to adjust the radio output of the mica. Or you can copy the
Pot*.nc files into a telos platform directory and stub them.

There's no replacement for repeated-head-banging experimentation
when working with TOS.

Lovely.

I'll move on to your other questions under separate cover...
MS

Renee Azhen wrote:
> yeah, when I am uploding the sapmle
>  /opt/tinyos-1.x/apps/SimpleCmd
> I use this comman: make telosb install
> and following info was output in the screenshot:
> mkdir -p build/telosb
> compiling SimpleCmd to a telosb binary
> ncc -o build/telosb/main.exe -O -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d 
> -Wnesc-al
> l -target=telosb -fnesc-cfile=build/telosb/app.c -board= -I%T/lib/Deluge 
> -Wl,--s
> ection-start=.text=0x4800,--defsym=_reset_vector__=0x4000 
> -DIDENT_PROGRAM_NAME=\
> "SimpleCmd\" -DIDENT_USER_ID=\"ibm\" 
> -DIDENT_HOSTNAME=\"ibm-vs2a1bhcns0\" -DIDEN
> T_USER_HASH=0x245ca709L -DIDENT_UNIX_TIME=0x4764c622L 
> -DIDENT_UID_HASH=0x629f1f3
> 3L -mdisable-hwmul -I/opt/tinyos-1.x/tos/lib/CC2420Radio SimpleCmd.nc -lm
> C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/system/PotC.nc:90: component 
> HPLPotC n
> ot found
> C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/system/PotC.nc:93: no match
> make: *** [exe0] Error 1
> I want to demo the SimpleCmd sample in the node, so do you know how to 
> fix this problem??
> thanks
> Sam
> */Michael Schippling <[EMAIL PROTECTED]>/* 写道：
> 
> There is a dreaded DemoSensor impl in the T1 msp430 directory
> so that should handle the demo apps which use such, like O'scope.
> After that, it's probably an exercise for the reader of the
> tutorial to swap out sensors.
> 
> Other than the specifics of sensing devices, which would
> necessarily be application dependent anyway, TOS _should_
> hide platform details (or else one of it's design criteria
> is a moot point). Did you have specific errors with some
> of the apps?
> 
> MS
> 
> Urs Hunkeler wrote:
>  > Hi Sam,
>  >
>  > You could try boomerang from the former Moteiv. Their Tmote Skys
> should
>  > be compatible with the telosb platform.
>  >
>  > http://docs.tinyos.net/index.php/Boomerang
>  >
>  > Cheers,
>  > Urs
>  >
>  >
>  > Renee Azhen schrieb:
>  >> dear friend:
>  >> yeah, but my sensor can not use the Photo mudule, it is only
> humidity senses.
>  >> many samples in /apps if installed into my sensor will occur an
> error. I found that most of the sample code is only suitable to
> mica/micasb, so do you know where I can get the corresponding code
> for my telosb node?
>  >>
>  >> thanks
>  >> Sam
>  >>
>  >> Urs Hunkeler 写道：
>  >> Hi Sam,
>  >>
>  >> The MicaZ uses the same radio chip (cc2420). Usually
> applications for
>  >> the MicaZ also work on the Telosb platforms. The main
> differences are
>  >> the sensors, but they should be relatively straight forward to
> change.
>  >> Of course the Telosb platform use a different microcontroller
> (msp430
>  >> instead of an ATmega), but most differences should be handled
>  >> transparently by the compiler.
>  >>
>  >> The examples in the tutorials should work. I have the impression
> that
>  >> there are more examples for Telosb in TinyOS 2.x.
>  >>
>  >> Cheers,
>  >> Urs
>  >>
>  >> Renee Azhen schrieb:
>  >>> dear all:
>  >>> My platform is a telosb node.
>  >>> Most Sample code in /opt/tinyos 1.x/apps/ is for mica&mica2,
> then can not work on telosb platform.
>  >>>
>  >>> so I want to get some sample application that are suitable to
> telosb platform, could you tell me where and how I can get
> them??(Website, link or )
>  >>>
>  >>> Thanks
>  >>> Sam
>  > ___
>  > Tinyos-help mailing list
>  > Tinyos-help@millennium.berkeley.edu
>  >
> https://www.millennium.berkeley.edu/cgi-bin/mai

Re: [Tinyos-help]: No message was outputed when using Oscilloscope and

First try using   [EMAIL PROTECTED]:telosb   or "tmote"
since I think 19.2 is the wrong baud rate and the platform
name may also select some message parsing "features".
But I would expect to see some garbage from Listen even
with the wrong settings.

I believe Oscope blinks an LED when it transmits. Do you
see any action on the mote? If you have access to the Boomerang
code from ex-Moteiv, there is a set of Count demos, one being
CountUart which eliminates a lot of excess baggage when testing.
I don't think there is an equivalent in the regular apps.

The SENSORBOARD thing is specific to micaX's so you can safely
do nothing when using telos's. Oscope and other demos use
platform/msp430/DemoSensorC.nc which is connected to ADC port
10 (INTERNAL_TEMPERATURE), which provides almost no interesting
data, but at least does something...

And, no, neither you nor most anybody else needs SerialForwarder.
The Port Busy message usually means that some other program has
that port open. You may still have a Listen running or something.
With the MOTECOM setting as shown above, Listen should connect
directly to the right USB port, on Windows anyway (assuming that
motelist shows that COMx for your device). I think there was some
FTDI driver stuff that had to be installed to get to the USB.
I did for tmotes anyway...

Also...I hope you are looking at the help list in general
because all my sends to yahoo's get bounced right away...

MS

Renee Azhen wrote:
> dear all,
> mine using is tinyos 1.x, I have uploaded the apps/Oscilloscope code 
> into to a telosb platform, and then use Command java 
> net.tinyos.tools.Listen to start the Listening program, but only
> $ java net.tinyos.tools.Listen
> [EMAIL PROTECTED]:19200 : resynchronising
> no more info was outputted.
>  
> when using "motelist", only COM9 was connectted to a node, so I set
> export  
> [EMAIL PROTECTED]:192 
> 00
>  
> in the tutorial Lesson 6, there is word:
> Remember to set the SENSORBOARD option in apps/Oscilloscope/Makefile 
> 
>  
> to either micasb or basicsb depending on the type of sensor board you have.
> my sensor node is a telosb node, I don't know whether it is because is 
> neither micasb either basicsb, there was no output message.
>  
> Could you help me? I will really be thanksful for your help
> thanks
> Sam
> 
> 
> 天生购物狂，狂抢购物券，你还等什么！ 
> 
>  
> 
> 
> 
> 
> 
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

-- 
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help]: No message was outputed when using Oscilloscope and

Yes, the Archive, and just reading everything on the help list
is what I was referring to...but mostly, when I reply to some
yahoo addresses (I think outside the USofA), my messages get
refused at the receiver (or something like that)...so I was
hoping that you weren't waiting for a direct reply...

Anyway, you're understanding of baud is pretty much right, it's
"symbols per second" -- see wikipedia for excruciating detail.
But 57.6 is three times the rate of 19.2 which seems pretty
different to me. A UART set to 19.2 might think that 57.6 data
is just noise on the line...

MS

Renee Azhen wrote:
> You are so greatful, Michael, you guy are so experienced in this area, I 
> am thankful to your help so much.
>  
> I search in the *Mailing List Archive*(*Is this the help list in general 
> you mensioned??*), and find another guy once had the same problem, and 
> he told that the telosb baud rate is 57600, not 19200. and I made this 
> changet, all things goes all right:)
>  
> *I am quite understand the baud rate here*, in my mind, baud rate means 
> the number of times a signal in a communications channel changes state 
> or varies. so here, why using 57600 and 19200 so different??
>  
> really appreciated your help
> Sam
> 
> */Michael Schippling <[EMAIL PROTECTED]>/* 写道：
> 
> First try using [EMAIL PROTECTED]:telosb or "tmote"
> since I think 19.2 is the wrong baud rate and the platform
> name may also select some message parsing "features".
> But I would expect to see some garbage from Listen even
> with the wrong settings.
> 
> I believe Oscope blinks an LED when it transmits. Do you
> see any action on the mote? If you have access to the Boomerang
> code from ex-Moteiv, there is a set of Count demos, one being
> CountUart which eliminates a lot of excess baggage when testing.
> I don't think there is an equivalent in the regular apps.
> 
> The SENSORBOARD thing is specific to micaX's so you can safely
> do nothing when using telos's. Oscope and other demos use
> platform/msp430/DemoSensorC.nc which is connected to ADC port
> 10 (INTERNAL_TEMPERATURE), which provides almost no interesting
> data, but at least does something...
> 
> And, no, neither you nor most anybody else needs SerialForwarder.
> The Port Busy message usually means that some other program has
> that port open. You may still have a Listen running or something.
> With the MOTECOM setting as shown above, Listen should connect
> directly to the right USB port, on Windows anyway (assuming that
> motelist shows that COMx for your device). I think there was some
> FTDI driver stuff that had to be installed to get to the USB.
> I did for tmotes anyway...
> 
> Also...I hope you are looking at the help list in general
> because all my sends to yahoo's get bounced right away...
> 
> MS
> 
> 
> 
> Renee Azhen wrote:
>  > dear all,
>  > mine using is tinyos 1.x, I have uploaded the apps/Oscilloscope code
>  > into to a telosb platform, and then use Command java
>  > net.tinyos.tools.Listen to start the Listening program, but only
>  > $ java net.tinyos.tools.Listen
>  > [EMAIL PROTECTED]:19200 : resynchronising
>  > no more info was outputted.
>  >
>  > when using "motelist", only COM9 was connectted to a node, so I set
>  > export
>  > [EMAIL PROTECTED]:192
>  > 00
>  >
>  > in the tutorial Lesson 6, there is word:
>  > Remember to set the SENSORBOARD option in apps/Oscilloscope/Makefile
>  >
>  > to either micasb or basicsb depending on the type of sensor board
> you have.
>  > my sensor node is a telosb node, I don't know whether it is
> because is
>  > neither micasb either basicsb, there was no output message.
>  >
>  > Could you help me? I will really be thanksful for your help
>  > thanks
>  > Sam
>  >
>  >
> 
>  > 天生购物狂，狂抢购物券，你还等什么！
>  >
>  >
>  >
>  >
>  >
> 
>  >
>  > ___
>  > Tinyos-help mailing list
>  > Tinyos-help@millennium.berkeley.edu
>  >
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> 
> -- 
> Platform: WinXP/Cygwin
> TinyOS version: 1.x, Boomerang

[Tinyos-help] Re: Problems with tinyos-1.x vs. 2.x

In my humble, humbling, and limited experience with academically
driven software, upgrading to the new-improved version of something
generally exposes one to the Latest Software Engineering Paradigms,
since such software is generally developed by grad-students who
need thesis topics, without actually providing much in the way of
functionality to those of us who ply the trade without benefit
of publication opportunities...

So, aside from applying my rusty hermeneutic skills to the TEPS,
is there someplace I can find a good description of the advantages
of re-experiencing the TOS learning cliff under T2? I mean, if I
port my working systems to some-slightly-different-but-almost-
the-same--except-oh-yeah-we-forgot--that version, what's in it
for me and mine?

MS


Kevin Klues wrote:
> "In response to an email posted on tinyos-help"
> 
> I think one problem with all of these issues that seem to come up in 
> tinyos-1.x is that no one is really maintaining that tree much anymore. 
> There are no new releases, and whenever a bug is discovered, it doesn't 
> get fixed, and everyone has to follow some workaround procedure that 
> they discover from searching the tinyos help list. 
> 
> In fact, since June of 2006, less than 20 commits have been made to the 
> baseline tinyos-1.x tree, and none of these have been reflected in any 
> sort of release that people actually use.  I'm sure there have been lots 
> of commits to the contrib tree, but this code tends to be even less 
> documented than the standard tinyos tree (which admittedly is not all 
> that great to begin with), and some users don't even know that it exists. 
> 
> My solution to all this would be to try and convince everyone to switch 
> over to tinyos-2.x, but I realize that some people are reluctant to do 
> so right away.  Many of the crossbow sensor drivers only exist for 
> tinyos-1.x , and many users have written code for their own applications 
> that relies on the way the 1.x task scheduler operates (which is quite 
> different than the 2.x task scheduler).  Code between the two versions 
> is therefore unfortunately not backwards compatible.  So whats the right 
> answer here?  Do we need someone who is really invested in tinyos-1.x to 
> step up and become the official maintainer of the tinyos-1.x tree -- 
> fixing bugs, etc. as they come in and pushing out new releases that have 
> the bug fixes in them?  Or would it be better to start motivating people 
> to start porting everything over to tinyos-2.x, so that their reliance 
> on 1.x slowly fades away?
> 
> As with most things, the real problem is motivation and time.  People 
> who have been working with tinyos for quite awhile only tend to port 
> things in an on demand fashion when they realize that they need 
> something that existed in tinyos-1.x but doesn't in 2.x.  This leaves 
> unexperienced users that may not have the know-how to do a port stuck 
> with using tinyos-1.x rather than switching to the much more stable, and 
> much better maintained codebase of 2.x. In in ideal world, everything 
> that runs on 1.x would already be ported over to 2.x, and new users 
> could jump right in without every having thought about using 1.x.  This 
> is not an ideal world, however, and none of us are getting paid to do 
> any of these ports, hence they are not getting done in a timely fashion. 
> 
> Maybe money would be a good incentive to get some of these things ported 
> over though.  If there are any companies out there that really feel they 
> would benefit from using 2.x rather than 1.x, but don't want to deal 
> with the complexities of digging into the code base and doing the 
> porting themselves, maybe they could hire out consultants to do the work 
> for them.  I'm sure plenty of people on this list would be willing to 
> take some time to do these ports if they knew they could get a little 
> extra cash for it.  Just a thought...
> 
> Kevin
> 
> On Dec 16, 2007 9:35 AM, Michael Schippling <[EMAIL PROTECTED] 
> <mailto:[EMAIL PROTECTED]>> wrote:
> 
> Well, isn't this nice... "portable" TOS demo apps have
> some platform dependencies defined into them...
> 
> SimpleCmd uses a "Pot" component that is specific to the
> mica (NOT mica2 or micaz, _mica_) platform. You may be able
> to just go edit out references to "Pot", since it was used
> to adjust the radio output of the mica. Or you can copy the
> Pot*.nc files into a telos platform directory and stub them.
> 
> There's no replacement for repeated-head-banging experimentation
> when working with TOS.
> 
> Lovely.
> 
> I'll move on to your other questions under separate c

Re: [Tinyos-help] How to get the Sample code which is suitable to telosb platform?


I'm not clear on what is improved:
 a) the demo apps are better written;
 b) there's no way to include platform specific code at the app level;
 c) there's no more head-banging required.

???
MS

ps...Agreed. Some new-fangled enginnering ideas are probably
good (in the long run) AND advantageous (even in the short),
and further, that a second full pass over a system _should_
at least step-wise improve the product. And of course:
It's free (or conversely, you get what you pay for).

Philip Levis wrote:

On Dec 16, 2007, at 9:35 AM, Michael Schippling wrote:


Well, isn't this nice... "portable" TOS demo apps have
some platform dependencies defined into them...

SimpleCmd uses a "Pot" component that is specific to the
mica (NOT mica2 or micaz, _mica_) platform. You may be able
to just go edit out references to "Pot", since it was used
to adjust the radio output of the mica. Or you can copy the
Pot*.nc files into a telos platform directory and stub them.

There's no replacement for repeated-head-banging experimentation
when working with TOS.

Lovely.


You were asking about benefits about moving to 2.x?

Phil


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Re: Problems with tinyos-1.x vs. 2.x


Excellent...thank you...

A couple questions...
One of my projects relies on ATMEGA Timers1&3 for PWM output and
time capture. Have these been preempted by internals or can I
still use them with impunity?
The same project also uses PortC and all the ADC's, round robin
sampling on a 1ms Timer[] (which is one reason I can't upgrade
beyond 1.1.7, due to the (silly?) 3ms throttle in the Timer[]).
Any estimate of the pain level involved in upgrading and
back-hacking this?

MS

Philip Levis wrote:


On Dec 16, 2007, at 3:39 PM, Michael Schippling wrote:


So, aside from applying my rusty hermeneutic skills to the TEPS,
is there someplace I can find a good description of the advantages
of re-experiencing the TOS learning cliff under T2?


http://www.tinyos.net/tinyos-2.x/doc/html/overview.html

Phil


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Re: Problems with tinyos-1.x vs. 2.x

static building: meaning a link phase so you can include
regular 'C' code without hoop-jumping? or...?
thx
MS



John Griessen wrote:
> Michael Schippling wrote:
>> In my humble, humbling, and limited experience with academically
>> driven software, upgrading to the new-improved version of something
>> generally exposes one to the Latest Software Engineering Paradigms,
>> since such software is generally developed by grad-students who
>> need thesis topics, without actually providing much in the way of
>> functionality
> 
> [What are]
> the advantages
>> of re-experiencing the TOS learning cliff under T2?
> 
> My understanding is:  The formal T2 tasks queue for "synch" commands,
> and the schedule queue for "async" commands keeps all commands going,
> and saves you from competing function collisions if you do it right,
> plus static building get you ability to add to an existing base
> with much less debugging.
> 
> Have I got it right?
> 
> John Griessen
> 

-- 
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Re: Problems with tinyos-1.x vs. 2.x


Great papers...have these been in stealth mode or did I just miss
the announcement? Are they linked in to the new improved TOSdoc wiki?
MS


Vlado Handziski wrote:

...

I would not say that the relation between T2 and T1 can be characterized 
by "almost-the-same--except-oh-yeah-we-forgot-that-version". For more 
info on the T2 philosophy and how it differs from what we had in 1.x, 
you can check for example the T2 technical report and the HAA and "power 
locks" papers:


http://www.tkn.tu-berlin.de/publications/papers/T2_TR.pdf
http://www.tkn.tu-berlin.de/publications/papers/flexible_hardware_abstraction.pdf
http://www.tkn.tu-berlin.de/publications/papers/sosp186-klues.pdf

Vlado


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] .platform question


Along these lines...is there a doc that describes the structure of
the TOS devel trees and their position dependencies? I've discovered
by wanton experimentation that I can set TOSDIR/TOSROOT (but, hmm,
which one, and using which (cygwin-hack C:/opt) syntax?) in order to
use different T1 version trees -- but strangely, boomerang has a
little finger reaching into "tinyos-1.x" to get Makerules -- and
I surely would like to put my own personal apps in my own personal
dev tree (just so I can keep them together with their host programs
and backup everything at once), say pointed to by "contrib" or something.
But I haven't been brave enough to try compiling TOS apps outside the
/opt/tinyos* umbrella because I just know there's going to be a
"../../.." in a Makefile someplace.

This is not entirely wishful thinking because of a quirk in Eclipse
which prevents (my simple minded attempts at) having more than one
project -- even of different types -- in the same directory tree.

MS



Kevin Klues wrote:

I do. Why should contrib -- a social construction that happens to be
the way it is mostly due to sourceforge licensing and CVS checkout
structure -- determine parameters to the compiler? If contrib were in
tinyos-2.x (as it is in 1.x), then this would not be necessary. 



Why even have the %T then?  You can always use $TOSDIR or explicitly 
write out the path each time you want to reference it.  Its there purely 
for convenience (its not in fact a 'parameter' to the compiler in the 
sense of a command line parameter.  Look at how ncc deals with the %T... 
it just looks up what TOSDIR is and replaces it). 



It might make more sense to define a variable in Makerules that
derives contrib from TOSDIR/TOSROOT. Application makefiles can
override it, etc.


While I agree it might be a social construct that contrib is in a 
separate tree in T2, that doesn't mean we can ignore this fact.  When 
someone checks out contrib from sourceforge they have the freedom to 
place it anywhere in their directory heirarchy that they like.  The only 
way we could have makerules 'derive' contrib from TOSROOT is if we force 
users to place their contrib directory at some location underneath the 
tinyos-2.x tree heirarchy.  I personally, like to leave it 
outside..  To deal with this, I simply set a new environment 
variable that points to my TOSCONTRIBROOT and reference everything from 
there.  Adding the %C to ncc would just allow %C to stand in place of 
$TOSCONTRIBROOT just like %T stands in place of $TOSDIR.  I personally 
don't see anything wrong with doing this.


Kevin




___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: 回复： Re: [Tinyos-help] How to get t he Sample code which is suitable to telosb pla tform?

In my opinion I don't know if the demos are better,
that's what I was asking Phil...Folks seem to think
they are, so maybe your best approach is to just go
directly to T2 and don't pass Go.

On the other hand, trying to get T1 apps working is
a good learning exercise...heh

MS

Renee Azhen wrote:
> hi, Michael,
> to your opinion a) teh demo apps are better written,
> where is the demo apps??
> thanks
> Sam 
> 
> */Michael Schippling <[EMAIL PROTECTED]>/* 写道：
> 
> I'm not clear on what is improved:
> a) the demo apps are better written;
> b) there's no way to include platform specific code at the app level;
> c) there's no more head-banging required.
> 
> ???
> MS
> 
> ps...Agreed. Some new-fangled enginnering ideas are probably
> good (in the long run) AND advantageous (even in the short),
> and further, that a second full pass over a system _should_
> at least step-wise improve the product. And of course:
> It's free (or conversely, you get what you pay for).
> 
> Philip Levis wrote:
>  > On Dec 16, 2007, at 9:35 AM, Michael Schippling wrote:
>  >
>  >> Well, isn't this nice... "portable" TOS demo apps have
>  >> some platform dependencies defined into them...
>  >>
>  >> SimpleCmd uses a "Pot" component that is specific to the
>  >> mica (NOT mica2 or micaz, _mica_) platform. You may be able
>  >> to just go edit out references to "Pot", since it was used
>  >> to adjust the radio output of the mica. Or you can copy the
>  >> Pot*.nc files into a telos platform directory and stub them.
>  >>
>  >> There's no replacement for repeated-head-banging experimentation
>  >> when working with TOS.
>  >>
>  >> Lovely.
>  >
>  > You were asking about benefits about moving to 2.x?
>  >
>  > Phil
> 
> -- 
> Platform: WinXP/Cygwin
> TinyOS version: 1.x, Boomerang
> Programmer: MIB510
> Device(s): Mica2, MicaZ, Tmote
> Sensor board: homebrew
> 
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> 
> 
> 
> 天生购物狂，狂抢购物券，你还等什么！ 
> <http://cn.mail.yahoo.com/promo/taobao20/index.php?souce=mail_mailletter_tagline>
>  
> 

-- 
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: 回复： Re: 回复： Re: [Tinyos-help] H ow to get the Sample code which is suitable to telosb platform?