[Tinyos-help] DELUGE in TOSSIM

[Micfox Micfox]

Hi,
 After struggling with the environmental setting for TOSSIM, I finally got 
it to Deluge... However, when I attempted to run the main.exe (even with 
one node). I still got the eeprom errors (It seems the size of required 
eeprom is bigger than the presetting one):


===
./build/pc/main.exe -l=1 1

SIM: EEPROM system initialized.
SIM: event queue initialized.
SIM: Random seed is 769588
SIM: Initializing sockets
SIM: Created server socket listening on port 10584.
SIM: Created server socket listening on port 10585.
SIM: Time for mote 0 initialized to 39672702.
SIM: eventAcceptThread running.
SIM: commandReadThread running.

(it puased here around 3-5 seconds, then the following errors come out. I 
could not capture the error message between the upper half and lower half 
since these error message pop out quick and extensively)

..
0: ERROR: Tried to read EEPROM address 0xf03ca of mote when its max EEPROM 
address is 0x8.
0: ERROR: Tried to read EEPROM address 0xf03cb of mote when its max EEPROM 
address is 0x8.
0: ERROR: Tried to read EEPROM address 0xf03cc of mote when its max EEPROM 
address is 0x8.
0: ERROR: Tried to read EEPROM address 0xf03cd of mote when its max EEPROM 
address is 0x8.
0: ERROR: Tried to read EEPROM address 0xf03ce of mote when its max EEPROM 
address is 0x8.
0: ERROR: Tried to read EEPROM address 0xf03cf of mote when its max EEPROM 
address is 0x8.
0: ERROR: Tried to read EEPROM address 0xf03d0 of mote when its max EEPROM 
address is 0x8.
0: ERROR: Tried to read EEPROM address 0xf03d1 of mote when its max EEPROM 
address is 0x8.
0: ERROR: Tried to read EEPROM address 0xf03d2 of mote when its max EEPROM 
address is 0x8.
0: ERROR: Tried to read EEPROM address 0xf03d3 of mote when its max EEPROM 
address is 0x8.
0: ERROR: Tried to read EEPROM address 0xf03d4 of mote when its max EEPROM 
address is 0x8.
0: ERROR: Tried to read EEPROM address 0xf03d5 of mote when its max EEPROM 
address is 0x8.
0: ERROR: Tried to read EEPROM address 0xf03d6 of mote when its max EEPROM 
address is 0x8.
0: ERROR: Tried to read EEPROM address 0xf03d7 of mote when its max EEPROM 
address is 0x8.



=

Please advise how I could set this up properly so that the eeprom size 
would not be complained...


_
与世界各地的朋友进行交流，免费下载  Live Messenger; 
http://get.live.com/messenger/overview 


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

Re: [Tinyos-help] Broadcast via Tython

[Sarfraz Nawaz]

It seems that it is not possible to broadcast a packet since the
RadioMsgSendCommand is sent to one mote at a time that has been specified by
the moteID in comm.sendRadioMessage command.

On 6/15/07, Faisal Karim <[EMAIL PROTECTED]> wrote:


Hi All

I want to send broadcacst message from tython. The method
comm.sendRadioMessage(mote ID, time, msg) is working only when i specify
any mote ID. I tried comm.sendRadioMessage(TOS_BCAST_ADDR, 0, msg), it is
not working. I also used comm.sendRadioMessage(0x, 0, msg) and
comm.sendRadioMessage(65535, 0, msg) but in vain.

For comm.sendRadioMessage(TOS_BCAST_ADDR, 0, msg) tython gave error for
not recognizing TOS_BCAST_ADDR so i tried to import the package where this
variable resides. From documentation from somewhere i found that it reside
in global package COMM
http://www.tinyos.net/tinyos-1.x/doc/tutorial/matlab.html .  Can someone
put some light how to import it? Or there is some way around for
broadcasting via tython.

Regards
Faisal Karim



--
Don't pick lemons.
See all the new 2007 
carsat
 Yahoo!
Autos.

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

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

RE: [Tinyos-help] TOSSIM: lossless radio model

[Roland Tembo Hendel]

There is no such thing as a lossless radio link. This is a function of
Physics. The only question that remains is where to put the retransmission
logic. There are two common answers to this question:
1) between adjacent nodes (data-link/network layer)
2) between communication end-points (transport/session/application layer)

The path you choose depends on many factors and is the subject of
considerable study (common to wire-line transmission theory).

For example, TCP/IP performs retransmission between network endpoints in the
transport (TCP) layer, while IP remains lossy.

Usually, for RF links option #2 is the prudent approach. So, if you want to
approximate a "lossless" radio model, you might consider applying
retransmission logic to your application.

R~




> -Original Message-
> From: [EMAIL PROTECTED] [mailto:tinyos-help-
> [EMAIL PROTECTED] On Behalf Of Anu Singh
> Sent: Friday, June 15, 2007 6:57 PM
> To: tinyos-help@Millennium.Berkeley.EDU
> Subject: [Tinyos-help] TOSSIM: lossless radio model
> 
> 
> Hi,
>   I am using tinyos-2.0. Is there a way to specify the radio model used in
> TOSSIM as simple or lossless so that there are no message loss (either
> because of collisions or lossy links)?  By default the radio model is
> lossy.  I have also specified all links with gain 0.0 (maximum gain).
> 
> thanks,
> -Anu
> ___
> Tinyos-help mailing list
> Tinyos-help@Millennium.Berkeley.EDU
> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


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

[Tinyos-help] TOSSIM: lossless radio model

[Anu Singh]

Hi,
  I am using tinyos-2.0. Is there a way to specify the radio model used in
TOSSIM as simple or lossless so that there are no message loss (either
because of collisions or lossy links)?  By default the radio model is
lossy.  I have also specified all links with gain 0.0 (maximum gain).

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

RE: [Tinyos-help] Timer and Atomic Help (Ian Welch)

[Ben Buckner]

On Jun 15, 2007, at 4:16 PM, Ben Buckner wrote:

>>> From: "Ian Welch" <[EMAIL PROTECTED]>
>>> Subject: [Tinyos-help] Timer and Atomic Help
>>>
>>> Hello,
>>>   I'm implementing a clock on my mote and it seems to drift, I  
>>> think the
>>> issue is to to too many or too long atomic sections. I was  
>>> wondering if
>>> someone could explain to me how atomic sections effect interrupts  
>>> (events)
>>> from the timer module.
>>
>> This is more a general microprocessor programming question than a  
>> TinyOS
>> question, but, as the documentation says, an atomic section prevents
>> interrupt execution, so if your timer fires an interrupt during  
>> execution of
>> atomic code, the interrupt will either not be processed or (less  
>> likely)
>> will be queued until the atomic section is finished. I don't know  
>> of TinyOS
>> being implemented on a controller that can queue interrupts, so it  
>> will
>> probably be lost (definitely lost on Mica*s), but that could be a  
>> platform
>> dependent behavior.

>Almost all processors today (and all for the sake of this discussion)  
>work in a simple way:
>
>1) when a condition to cause an interrupt occurs, the processor sets  
>the interrupt pending bit in a control register
>
>2) if an interrupt is enabled and its pending bit it set, the  
>interrupt fires and the handler executes
>   2a) depending on the hardware and interrupt source, the pending  
>bit may be automatically cleared when the interrupt fires
>
>So you only lose an interrupt if it is disabled long enough that the  
>pending bit is already set when the condition occurs again. In  
>essence, the processor has a 1-deep queue for each interrupt source.
...
>Phil

I'm reading the ATMega docs more closely, and that is true for some
interrupts on it but not all. 

"There are basically two types of interrupts. The first type is triggered by
an event that sets the interrupt flag. For these interrupts, the Program
Counter is vectored to the actual interrupt vector in order to execute the
interrupt handling routine, and hardware clears the corresponding interrupt
flag. Interrupt flags can also be cleared by writing a logic one to the flag
bit position(s) to be cleared. If an interrupt condition occurs while the
corresponding interrupt enable bit is cleared, the interrupt flag will be
set and remembered until the interrupt is enabled, or the flag is cleared by
software. Similarly, if one or more interrupt conditions occur while the
global interrupt enable bit is cleared, the corresponding interrupt flag(s)
will be set and remembered until the global interrupt enable bit is set, and
will then be executed by order of priority."

"The second type of interrupts will trigger as long as the interrupt
condition is present. These interrupts do not necessarily have interrupt
flags. If the interrupt condition disappears before the interrupt is
enabled, the interrupt will not be triggered." (p 13 ATmega 128L manual) 

This particular counter interrupt could perhaps be this vaguely described
non queuing kind. I would have thought that if any interrupt was going to be
queuable, it would be a counter output compare (and the non-queuables would
more likely be something like level-triggered external interrupts), but I
don't see anything in the timer section that says anything definitive. I'm
pretty sure I have lost OC interrupts on a Mica2 though. When I timed the
ADC near its max sampling rate, I would get occasional and suspiciously
periodic drops when I didn't have all the other counters shut off, but I
guess that could have just been the extra latency pushing it into the next
counter cycle. Easy enough to test.

Regards,
Ben Buckner




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

Re: [Tinyos-help] Timer and Atomic Help (Ian Welch)

[Philip Levis]

On Jun 15, 2007, at 4:16 PM, Ben Buckner wrote:


From: "Ian Welch" <[EMAIL PROTECTED]>
Subject: [Tinyos-help] Timer and Atomic Help

Hello,
  I'm implementing a clock on my mote and it seems to drift, I  
think the
issue is to to too many or too long atomic sections. I was  
wondering if
someone could explain to me how atomic sections effect interrupts  
(events)

from the timer module.


This is more a general microprocessor programming question than a  
TinyOS

question, but, as the documentation says, an atomic section prevents
interrupt execution, so if your timer fires an interrupt during  
execution of
atomic code, the interrupt will either not be processed or (less  
likely)
will be queued until the atomic section is finished. I don't know  
of TinyOS
being implemented on a controller that can queue interrupts, so it  
will
probably be lost (definitely lost on Mica*s), but that could be a  
platform

dependent behavior.


Almost all processors today (and all for the sake of this discussion)  
work in a simple way:


1) when a condition to cause an interrupt occurs, the processor sets  
the interrupt pending bit in a control register


2) if an interrupt is enabled and its pending bit it set, the  
interrupt fires and the handler executes
  2a) depending on the hardware and interrupt source, the pending  
bit may be automatically cleared when the interrupt fires


So you only lose an interrupt if it is disabled long enough that the  
pending bit is already set when the condition occurs again. In  
essence, the processor has a 1-deep queue for each interrupt source.




The TinyOS reference docs may define this behavior - I
don't know, might be worth checking. Consequently, atomic sections  
may have
to be synchronously designed so that interrupts will be guaranteed  
to be
enabled during a clock tick. That could be doable on a mote  
platform, but
good luck doing it. Another approach is to poll the counter state  
coming out
of every atomic section to determine whether the clock fired while  
you were
in it. Does that scare you? It should. I recommend finding an  
alternative to

building a real time software clock.


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

RE: [Tinyos-help] Timer and Atomic Help (Ian Welch)

[Ben Buckner]

> From: "Ian Welch" <[EMAIL PROTECTED]>
> Subject: [Tinyos-help] Timer and Atomic Help
>
> Hello,
>   I'm implementing a clock on my mote and it seems to drift, I think the
> issue is to to too many or too long atomic sections. I was wondering if
> someone could explain to me how atomic sections effect interrupts (events)
> from the timer module.

This is more a general microprocessor programming question than a TinyOS
question, but, as the documentation says, an atomic section prevents
interrupt execution, so if your timer fires an interrupt during execution of
atomic code, the interrupt will either not be processed or (less likely)
will be queued until the atomic section is finished. I don't know of TinyOS
being implemented on a controller that can queue interrupts, so it will
probably be lost (definitely lost on Mica*s), but that could be a platform
dependent behavior. The TinyOS reference docs may define this behavior - I
don't know, might be worth checking. Consequently, atomic sections may have
to be synchronously designed so that interrupts will be guaranteed to be
enabled during a clock tick. That could be doable on a mote platform, but
good luck doing it. Another approach is to poll the counter state coming out
of every atomic section to determine whether the clock fired while you were
in it. Does that scare you? It should. I recommend finding an alternative to
building a real time software clock.

Regards,
Ben Buckner



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

[Tinyos-help] Radio (loss) model support for TOSSIM CC2420?

[Ray Wang]

Hi,

I'm wondering whether TOSSIM for CC2420 can support a lossy file?  From the
source code in Tinyos-1.x beta, it seems the CC2420 TOSSIM employs a
different lossy mechanism from CC1000Radio, which can use the -rf option to
input the node connectivity/lossy model.

Thanks.

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

[Tinyos-help] CC2420 lossy module in TOSSIM

[Yang Peng]

Hi all,

I am trying to use TOSSIM to do simulation for telosb in tinyos1.x, but I
can not use lossy module to do build multihop topology...
Does anyone use "run -rf=yourlossyfile.nss nodeNUM" ?

It seems like my lossy.nss file does not work, seems like it is not
read(I use lossyBuilder to generate this file)
Can anyone give me some suggestions?

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

[Tinyos-help] avoid mac layer

[roberto pagliari]

Hi All,
I need to send and receive short pulses, without the mac layer. Does anyone
know how do that? ultrasound is too directive, while the microphone
available for micaz doesnt allow to send short pulses. Can I find something
better?


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

[Tinyos-help] Timer and Atomic Help

[Ian Welch]

Hello,
  I'm implementing a clock on my mote and it seems to drift, I think the
issue is to to too many or too long atomic sections. I was wondering if
someone could explain to me how atomic sections effect interrupts (events)
from the timer module.

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

Re: [Tinyos-help] How to build generic nesdoc?

[David Gay]

On 6/15/07, Ken Bannister <[EMAIL PROTECTED]> wrote:

I understand how to build nesdoc for an application. How can I run nesdoc to
include all available system components and interfaces? My goal is to easily
see everything available for use, not to document what I've written. I use
the latest CVS, so I'd like to perform this locally.

To approximate this goal I run "make  docs" on all the
subdirectories of $TOSROOT/apps/tests. All the docs are dumped into
$TOSROOT/doc/nesdoc. Is there a better way?


No, that's what we do... (except you probably want to do start at
$TOSROOT/apps).

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

Re: [Tinyos-help] MTS310 SENSOR BOARD

[David Gay]

On 6/15/07, Bernardo Avila Pires <[EMAIL PROTECTED]> wrote:

I supposed so. Thanks.
BTW, is this timer problem general or only in TOSSIM? The fixes I saw
in the install instructions suggested it affected only the simulator.


I think those instructions relate to a bug in the 2.0.1 release. The
bug in the 2.0 mica timers is unrelated and makes them misbehave
(pretty badly in some cases).

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

[Tinyos-help] Problem to receive correct custom message

[projet19 projet19]

Hi,

We have made a custom message for messages that our computer send for our motes 
( MoteAppCmdMsg ).
This message is defined by this struct :

**


typedef struct MoteAppCmdMsg {
  uint8_t type;
  union {
// FOR MOTEAPP_TYPE_SETRATE
uint32_t newrate;

// FOR MOTEAPP_TYPE_SLEEP 
uint16_t sleepaddr;

uint16_t thresaddr;

struct 
{
uint16_t thres_light;
uint16_t thres_temp;

}threshold;

 // pour MOTEAPP_TYPE_SETPOSITION
struct
{
uint16_t  X_pos;
   uint16_t  Y_pos;
   uint16_t  Z_pos;
  
 
   }position;

  } args;

} __attribute__ ((packed)) MoteAppCmdMsg;

enum {
  AM_MOTEAPPCMDMSG = 0x21 //33
};

**


So on our computer application, we fill the differents field of the
message, and so the type field of our message with the lines :

**


moteAppCmdMsg = new MoteAppCmdMsg();
moteAppCmdMsg.set_type(MOTEAPP_TYPE_GETTHRESHOLD); //0x6
mote.send(net.tinyos.message.MoteIF.TOS_BCAST_ADDR, moteAppCmdMsg);

**


All motes receive the message, and create a Bcast.receive event on our nesC 
application with the line :

**


  event TOS_MsgPtr Bcast.receive(TOS_MsgPtr pMsg, void* payload, uint16_t 
payloadLen)
   {
 
  MoteAppCmdMsg *pCmdMsg = (MoteAppCmdMsg *)payload; 
  call Leds.greenToggle();
 dbg(Debug, "MoteAppM: Bcast  0x%02x\n", pCmdMsg->type); 

if (pCmdMsg->type == MOTEAPP_TYPE_GETTHRESHOLD) //  0x6
{
}

**

So
the problem is that we don't enter on the " if structure ", even we
have previously sent a moteAppCmdMsg with type field filled with 0x6
(MOTEAPP_TYPE_GETTHRESHOLD).

We don't know where is the problem,

Can you help us ?

Best regards,

Tony GOMES and Ahmed
 DEHBI



   

Sick sense of humor? Visit Yahoo! TV's 
Comedy with an Edge to see what's on, when. 
http://tv.yahoo.com/collections/222___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] How to build generic nesdoc?

[Ken Bannister]

I understand how to build nesdoc for an application. How can I run nesdoc to 
include all available system components and interfaces? My goal is to easily 
see everything available for use, not to document what I've written. I use 
the latest CVS, so I'd like to perform this locally.


To approximate this goal I run "make  docs" on all the 
subdirectories of $TOSROOT/apps/tests. All the docs are dumped into 
$TOSROOT/doc/nesdoc. Is there a better way?


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

Re: [Tinyos-help] MTS310 SENSOR BOARD

[Bernardo Avila Pires]

I supposed so. Thanks.
BTW, is this timer problem general or only in TOSSIM? The fixes I saw
in the install instructions suggested it affected only the simulator.

2007/6/15, David Gay <[EMAIL PROTECTED]>:

On 6/15/07, Bernardo Avila Pires <[EMAIL PROTECTED]> wrote:
> I've updated from the CVS, but how do I check my tree version?

CVS trees don't have any automatic numbering. But more or less by
definition (ok, branches do complicate life), if you're at the head of
CVS, your more recent than the most recent release... If you do want
to call it something, it's "CVS as of June 15 2007"...

David Gay




--
"The truth shall set you free"
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] MTS310 SENSOR BOARD

[David Gay]

On 6/15/07, Bernardo Avila Pires <[EMAIL PROTECTED]> wrote:

I've updated from the CVS, but how do I check my tree version?


CVS trees don't have any automatic numbering. But more or less by
definition (ok, branches do complicate life), if you're at the head of
CVS, your more recent than the most recent release... If you do want
to call it something, it's "CVS as of June 15 2007"...

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

Re: [Tinyos-help] MTS310 SENSOR BOARD

[mai naaom]

"I've updated from the CVS, but how do I check my tree version?" am asking
same question as Bernardo
mai naaom


On 6/15/07, Bernardo Avila Pires <[EMAIL PROTECTED]> wrote:


I've updated from the CVS, but how do I check my tree version?

2007/6/15, David Gay <[EMAIL PROTECTED]>:
> On 6/15/07, Christian Hermann <[EMAIL PROTECTED]> wrote:
> > It is supported. If you got the actual CVS-snapshot the driver located
> > in tos\sensorboards\mts300 does actually support mts310 as well.
>
> This driver is in the TinyOS 2.0.1 release (which you definitely want
> if using mica* motes, because of a timer problem in 2.0).
>
> David Gay
> ___
> Tinyos-help mailing list
> Tinyos-help@Millennium.Berkeley.EDU
>
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>


--
"The truth shall set you free"

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

Re: [Tinyos-help] MTS310 SENSOR BOARD

[Bernardo Avila Pires]

I've updated from the CVS, but how do I check my tree version?

2007/6/15, David Gay <[EMAIL PROTECTED]>:

On 6/15/07, Christian Hermann <[EMAIL PROTECTED]> wrote:
> It is supported. If you got the actual CVS-snapshot the driver located
> in tos\sensorboards\mts300 does actually support mts310 as well.

This driver is in the TinyOS 2.0.1 release (which you definitely want
if using mica* motes, because of a timer problem in 2.0).

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




--
"The truth shall set you free"
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Multichannel Adc sampling and DMA

[Philip Levis]

On Jun 15, 2007, at 1:46 AM, Oussama Chougna wrote:


Hi Phil,


Are you sure about this:


Timer.fired() {
call Channe1One.read();
call ChannelTwo.read();
call ChannelThree.read();
call ChannelFour.read();
call ChannelFive.read();
call ChannelSix.read();
}


Is the first approach only possible with the HIL ADC component
ADCReadClientC? Because with the (msp430) HAL interfaces the client  
should
do resource arbitration. (request() , configure() , getData(),  
dataReady() ,
release() ). So you cannot call getData() of each channel one after  
the

other in the timer.fired() event?



Ah, then what you what to do is

acquire resource
sample 1
sample 2
sample 3
sample 4
sample 5
sample 6
release resource

Basically, for maximum efficiency you don't want the lock (resource)  
to go idle. That's why enqueueing all the requests as I showed with  
the HIL is desirable. The lock won't be released until the sixth  
channel is read.





Which would you recommend for 100 Hz sampling? (HIL or HAL)


You want to sample all 6 sensors at 100Hz? I'd say try using the HIL  
(it's simpler) and if it can't do the job use the HAL. The one thing  
to be careful of is that if you let the ADC go idle long enough, it  
might power down the voltage reference, which has a 17ms warmup time.


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

Re: [Tinyos-help] MTS310 SENSOR BOARD

[David Gay]

On 6/15/07, mai naaom <[EMAIL PROTECTED]> wrote:

am using TinyOS 2.0 ,not 2.0.1 so please tell me what is this timer problem
and how can i solve it
thanks in advance


To solve it, install TinyOS 2.0.1 (seriously).

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

Re: [Tinyos-help] tinyos-1.x vs tinyos-2.x: radio communication compatibility

[Philip Levis]

On Jun 15, 2007, at 12:56 AM, Jordi Vilaseca wrote:


Hi,

We're interested in communicating one node running tinyos-1.x with  
another running tinyos-2.x. Physically the platform is the same  
(micaz), so the chip radio is the same. I understood tinyos-2.x is  
802.15.4 MAC layer compliant, but tinyos-1.x is not. Is that the  
reason why the nodes cannot communicate? If we use any IEEE stack  
implementation in tinyos1-x, such as modules in contrib directory,  
will we be able to communicate the motes?


Thanks

Jordi Vilaseca
Universitat Politècnica de Catalunya
_


Both are compliant at the link layer. Neither is compliant at the MAC  
layer. That is, the packet formats are 802.15.4, but the CSMA isn't.


The major difference between 1.x and 2.x is that 2.x includes layer-2  
source addresses in the packets while 1.x does not. If you modified  
the 1.x stack slightly to include source addresses (including the  
bits in the FCF field), then you should be OK.


Phil


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

Re: [Tinyos-help] Documentation regarding exact contents of the MACProtocol Data Unit frame

[Pedro Almeida]

Hello, Benjamin;

I'm not sure how I can be of any help, I still don't understand the contents
of the message...

On 6/15/07, Benjamin Madore <[EMAIL PROTECTED]> wrote:


Pedro,

Would you mind adding all that information to:
http://tinyoscommunity.elwiki.com/Radio_FAQ
and helping others out?

On Wed, June 13, 2007 10:38 pm, Pedro Almeida said:
> David,
>
> Thank you for that attention call!
> So it's not the Packet Format Dispatched Byte that is out, it's the
Sequence
> Number Byte. Makes a lot more sense than my previous "disregard". One
more
> byte we're sure of!
>
> Thanks!
>
> Pedro
>


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


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

Re: [Tinyos-help] MTS310 SENSOR BOARD

[mai naaom]

am using TinyOS 2.0 ,not 2.0.1 so please tell me what is this timer problem
and how can i solve it
thanks in advance

mai naaom


On 6/15/07, David Gay <[EMAIL PROTECTED]> wrote:


On 6/15/07, Christian Hermann <[EMAIL PROTECTED]> wrote:
> It is supported. If you got the actual CVS-snapshot the driver located
> in tos\sensorboards\mts300 does actually support mts310 as well.

This driver is in the TinyOS 2.0.1 release (which you definitely want
if using mica* motes, because of a timer problem in 2.0).

David Gay

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

Re: [Tinyos-help] tos-install-jni can not locate java in cygwin

[Benjamin Madore]

On Fri, June 15, 2007 2:35 am, Ahmed Said said:
> Hi,
>
> I am using a cygwin environment, the problem is that after I install
> java  and I type "which java"
> I get "/cygdrive/c/windows/system32/", I think this is the reason for
> getting java not found error when I type "tos-install-jni", does
> anyone know how to displace this version of java by the one i
> installed to be able to install the JNI code?

Did you install your java in the C:\cygwin\ (or equivalent) folder with no
spaces in the path?

Then right-click on "My Computer", go to the "Advanced" tab, find "Path",
"path", or "PATH" in the system variables list, and append your path to the
front of the variable value. If your java is in C:\cygwin\ then you would
add "C:\cygwin\jdk1.4.2_00\j2sdk1.4.2_00\bin;" to the front, with no white
space. Make sure your version number is correct.

-Ben

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

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

Re: [Tinyos-help] MTS310 SENSOR BOARD

[David Gay]

On 6/15/07, Christian Hermann <[EMAIL PROTECTED]> wrote:

It is supported. If you got the actual CVS-snapshot the driver located
in tos\sensorboards\mts300 does actually support mts310 as well.


This driver is in the TinyOS 2.0.1 release (which you definitely want
if using mica* motes, because of a timer problem in 2.0).

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

[Tinyos-help] Sampling ADC

[Benjamin Madore]

I have never used the ADC channels directly, however since you are would you
be willing to add what you know and are finding out to the new wiki? It
would be of great help to those following in your footsteps.

-Ben

On Sat, June 9, 2007 3:45 pm, vipin kashyap said:
> Well Friend,
>
> I, perhaps, am not the only one with an unenviable predicament. Many others
> have probably spent sleepless nights trying to resolve the mystery of
> sampling Analog ADC channels.
>
> Here, I would like to place a link to ian's blog at tinyos.net
> http://www.tinyos.net/scoop/story/2005/6/5/10256/38159
>
> Read the first para at the page and it will become clear that dealing with
> adc(analog channels) is like learning black magic. Though difficult to do
> the first time but easy to repeat often.
>
> Anyway, my intent was not to belittle efforts of those who have developed a
> wonderful world of sensor networks with endless possibilities. But
> proliferation of this technology can only be achieved through encouraging
> and responsive support-mailing-lists.
>
> On the flip-side, i am closer to cracking the adc mystery for mica2. Pretty
> soon I might just post the replies to my own questions.
>
> Thanks a lot for all the help.
>
> Regards,
> Vipin Kashyap


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

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

Re: [Tinyos-help] Send Multiple Custom Messages in nesC

[Benjamin Madore]

On Thu, June 14, 2007 2:41 pm, projet19 projet19 said:
> We have done a nesC application capable of  sending  multiple custom
messages ( MoteAppMsg,  PositionMsg,  ThresholdMsg) that are defined in a
header file like that :
> ***

> ***
We did all MIG for all custom messages successfully,
>
> but it appears that when we send a MoteAppMsg with the line "call
Send.send(pMsgBuf,sizeof(struct MoteAppMsg))" to our computer Application,
the nesC program always send all types of messages...

>***
>Mote_AppM.Send -> multihopM.Send[AM_MOTEAPPMSG];
>
>  Mote_AppM.Send -> multihopM.Send[AM_POSITIONMSG];
>
>  Mote_AppM.Send -> multihopM.Send[AM_THRESHOLDMSG];
>

> So how can we modify nesC Application that when we send a MoteAppMsg, the
nesC
> Code send only a MoteAppMsg, and when we send a PositionMsg, the nesC Code
only
> send a PositionMsg ?
>
> Or, can anybody explain us a simple nesC application which utilise
multiple
> Custom Message ?

You have wired all your sends together. Try:
  Mote_AppM.SendApp   -> multihopM.Send[AM_MOTEAPPMSG];
  Mote_AppM.SendPosition  -> multihopM.Send[AM_POSITIONMSG];
  Mote_AppM.SendThreshold -> multihopM.Send[AM_THRESHOLDMSG];

Your going to have to add an interface for each:
  uses interface Send as SendApp
and call each separately. Your receives may have to be altered to fit the
pattern also. Do not worry, wiring is one of the most difficult new concepts
in NesC.

-Ben


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




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

Re: [Tinyos-help] Anyone used TinyOS 2.0 with TMote Sky

[Erwing Sánchez]

Hi.
I've been using tos2 for a while with Tmote Sky and everything is just
perfect so far.
You should take a deep look to the TinyOs 2 tutorials that provide a
lot of information. And remember that telosb is basically the same as
tmote, so you should be able to compile and load your programs by
typing "telosb" instead of "tmote"
If you're using a linux machine, consider taking a look to the
installation tutorials that you find in the moteiv site. They work
very good. Besides, it is also possible to install a couple of scripts
that let you change tinyOS versions, so you can start exploring TinyOS
2 while maintaining the advantages of Boomerang.
Regards,
Erwing

On 6/14/07, leonardo <[EMAIL PROTECTED]> wrote:

Hi


I would be very interested in using tmote sky on TinyOs 2. I apologize for the 
following trivial question but I am a new tinyos2 user.
I would like to make and upload the blink application, what have I to do?
For instance for a telos mote I have just to write make telos install and ncc, 
msp430-objcopy and tos-bsl are invoked.

I have downloaded the standard tinyos 2 installation and I did not find any 
tmote sky platform.
Moreover, I tried to look at the moteiv web site 
(http://www.moteiv.com/software/)
and download the boomerang software but It does not seem to contain tinyos 2 
support.

Please may you help me?

Thanks a lot

Leonardo

  _

From: tinyos-help-bounces at Millennium.Berkeley.EDU 

[mailto:tinyos-help-bounces at Millennium.Berkeley.EDU 
] On 
Behalf Of Oussama
Chougna
Sent: Friday, June 01, 2007 1:40 PM
To: tinyos-help at Millennium.Berkeley.EDU 

Subject: [Tinyos-help] Anyone used TinyOS 2.0 with TMote Sky


Hi there,



Does anyone have experience with using TinyOS 2 with the Tmote sky from
Moteiv?





Thanks in advance,





O.Chougna

-- next part --
An HTML attachment was scrubbed...
URL: 
http://mail.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20070601/f8260228/attachment.html

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


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

Re: [Tinyos-help] Documentation regarding exact contents of the MACProtocol Data Unit frame

[Benjamin Madore]

Pedro,

Would you mind adding all that information to:
http://tinyoscommunity.elwiki.com/Radio_FAQ
and helping others out?

On Wed, June 13, 2007 10:38 pm, Pedro Almeida said:
> David,
>
> Thank you for that attention call!
> So it's not the Packet Format Dispatched Byte that is out, it's the Sequence
> Number Byte. Makes a lot more sense than my previous "disregard". One more
> byte we're sure of!
>
> Thanks!
>
> Pedro
>


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

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

Re: [Tinyos-help] How to include multiple files in the makefile

[Benjamin Madore]

On Thu, June 14, 2007 7:51 am, Romain Thouvenin said:
> When you want to add personal compilation options, use PFLAGS+=...
> In your code, you wrote PFLAGS=..., which destroys what you added before.
>
> Romain

Correct

> On 6/14/07, Bibudh Lahiri <[EMAIL PROTECTED]> wrote:
>> Hi,
>>   Can anyone throw some light on what is the best way (syntactically) to
>> include multiple files in the makefile? I need to include the following
>> files for one application:
>>
>>/usr/include/math.h
>>/opt/tinyos-1.x/tos/interfaces/Random.nc
>>
>>  and two header files (config.h and nMotesMsg.h) from my own application
>> folder (which is
>> /opt/tinyos-1.x/apps/FlajoletMartin/BaseStation).
>>
>>  I tried the following:
>>
>>   COMPONENT=BaseStation
>>   PFLAGS=-I/usr/include
>>   PFLAGS=-I%T/interfaces
>>   PFLAGS=-I../Library
>>   include ../../Makerules
>>
You can also use:
PFLAGS += -I/usr/include -I%T/interfaces -I../Library

Whitespace in the makefile may be included for clarity.

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

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

Re: [Tinyos-help] MTS310 SENSOR BOARD

[Bernardo Avila Pires]

That's it... I'll try it this afternoon. Thanks for the hint.

2007/6/15, Christian Hermann <[EMAIL PROTECTED]>:


Post more details, I don't get your problem. Maybe the following?
I don't use SensorMts300C.nc but the single sensorC's directly.
Also because I've got no voltageC component in the whole TinyOS-2.x-dist
so this component(SensorMts300C.nc) can't compile correctly.
Christian

Bernardo Avila Pires schrieb:
> I think I've had bus problems when I tried to do this, but I also had
> a compilation problem due to wrong interface names. How did you solve
> it?
>
> 2007/6/15, Christian Hermann <[EMAIL PROTECTED]>:
>> It is supported. If you got the actual CVS-snapshot the driver located
>> in tos\sensorboards\mts300 does actually support mts310 as well. I'm
>> using it successfully (just the sound sensor doesn't cover my needs)
>> If you find some way to record audio-streams with 16khz or if you're
>> able to use the tone-detector please tell me! I got no answers to
>> these problems so far...
>> regards
>> Christian
>>
>> mai naaom schrieb:
>> > hi
>> > Am working on  mts310 sensor board (it is used for micaA2
>> motes)how
>> > can i compile this sensorboard with TinyOS-2.
>> > It is not supported by it so should i switch to TinyOS-1 or what i
>> have to
>> > do?
>> > please someone help
>> > thanks in advance
>> >
>> > regards,
>> > Mai
>> >
>> >
>> >
>>

>> >
>> > ___
>> > Tinyos-help mailing list
>> > Tinyos-help@Millennium.Berkeley.EDU
>> >
>>
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>>
>> --
>> 
>> Christian Hermann
>>
>> Am Weinberg 9
>> 08529 Plauen
>> Fax +49 3741 470159
>> Tel +49 173 4020035
>>
>> [EMAIL PROTECTED]
>> http://www.christian-hermann.de
>> ___
>> Tinyos-help mailing list
>> Tinyos-help@Millennium.Berkeley.EDU
>>
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>>
>
>

--

Christian Hermann

Am Weinberg 9
08529 Plauen
Fax +49 3741 470159
Tel +49 173 4020035

[EMAIL PROTECTED]
http://www.christian-hermann.de





--
"The truth shall set you free"
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Regarding battery Life

[R. Steve McKown]

On Thursday 14 June 2007 13:35:40 manu suryavansh wrote:
> Hi,
> The tmote sky system can work from 2.1V to 3.6V. In that case when the
> battery voltage drops to below 2.1V it will stop working and the remaining
> energy stored in the battery will not be used, so if the battery has
> 2200mAh of energy not all of it will be used, is this correct?. Is there
> any voltage up converter present on the system? Thank you
> Manu Suryavansh

You are correct about battery energy, but note the minimum voltage for the AA 
cells you are using.  At 2.1v, each cell is providing 1.05v, which is at or 
near the 'end voltage' for many chemistries.  I wouldn't be surprised if the 
energy cost of additional power conditioning (the parts would draw power 
themselves) exceeds what little extra you can scavenge out of the cells.

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

Re: [Tinyos-help] Regarding battery Life

[Joe Polastre]

The cut-off voltage for AA batteries is 1.8V, so there is only a
marginal amount of energy actually left in the batteries when the
system reaches 2.1V.  You may want to check out the battery curves for
AA batteries and learn more in general about how alkaline batteries
perform under load.  A good places to get started is
http://data.energizer.com/

There is no voltage boost on the Tmote Sky, because the voltage boost
from 1.8V to 2.1V would actually have very little to no effect because
the amount of energy required to perform the boost is larger than the
amount of remaining energy in the batteries.

-Joe

On 6/14/07, manu suryavansh <[EMAIL PROTECTED]> wrote:

Hi,
The tmote sky system can work from 2.1V to 3.6V. In that case when the
battery voltage drops to below 2.1V it will stop working and the remaining
energy stored in the battery will not be used, so if the battery has 2200mAh
of energy not all of it will be used, is this correct?. Is there any voltage
up converter present on the system?
Thank you
Manu Suryavansh


 
Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on,
when.


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


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

[Tinyos-help] Broadcast via Tython

[Faisal Karim]

Hi All

I want to send broadcacst message from tython. The method  
comm.sendRadioMessage(mote ID, time, msg) is working only when i specify any 
mote ID. I tried comm.sendRadioMessage(TOS_BCAST_ADDR, 0, msg), it is not 
working. I also
used comm.sendRadioMessage(0x, 0, msg) and
comm.sendRadioMessage(65535, 0, msg) but in vain.


For comm.sendRadioMessage(TOS_BCAST_ADDR, 0, msg) tython gave
error for not recognizing TOS_BCAST_ADDR so i tried to import the
package where this variable resides. From documentation from somewhere
i found that it reside in global package COMM
http://www.tinyos.net/tinyos-1.x/doc/tutorial/matlab.html .  Can someone put
some light how to import it? Or there is some way around for
broadcasting via tython.




Regards 
Faisal Karim 
 




   

Get the Yahoo! toolbar and be alerted to new email wherever you're surfing.
http://new.toolbar.yahoo.com/toolbar/features/mail/index.php___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] MTS310 SENSOR BOARD

[Christian Hermann]

Post more details, I don't get your problem. Maybe the following?
I don't use SensorMts300C.nc but the single sensorC's directly.
Also because I've got no voltageC component in the whole TinyOS-2.x-dist
so this component(SensorMts300C.nc) can't compile correctly.
Christian

Bernardo Avila Pires schrieb:
> I think I've had bus problems when I tried to do this, but I also had
> a compilation problem due to wrong interface names. How did you solve
> it?
> 
> 2007/6/15, Christian Hermann <[EMAIL PROTECTED]>:
>> It is supported. If you got the actual CVS-snapshot the driver located
>> in tos\sensorboards\mts300 does actually support mts310 as well. I'm
>> using it successfully (just the sound sensor doesn't cover my needs)
>> If you find some way to record audio-streams with 16khz or if you're
>> able to use the tone-detector please tell me! I got no answers to
>> these problems so far...
>> regards
>> Christian
>>
>> mai naaom schrieb:
>> > hi
>> > Am working on  mts310 sensor board (it is used for micaA2
>> motes)how
>> > can i compile this sensorboard with TinyOS-2.
>> > It is not supported by it so should i switch to TinyOS-1 or what i
>> have to
>> > do?
>> > please someone help
>> > thanks in advance
>> >
>> > regards,
>> > Mai
>> >
>> >
>> >
>> 
>> >
>> > ___
>> > Tinyos-help mailing list
>> > Tinyos-help@Millennium.Berkeley.EDU
>> >
>> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>>
>> -- 
>> 
>> Christian Hermann
>>
>> Am Weinberg 9
>> 08529 Plauen
>> Fax +49 3741 470159
>> Tel +49 173 4020035
>>
>> [EMAIL PROTECTED]
>> http://www.christian-hermann.de
>> ___
>> Tinyos-help mailing list
>> Tinyos-help@Millennium.Berkeley.EDU
>> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>>
> 
> 

-- 

Christian Hermann

Am Weinberg 9
08529 Plauen
Fax +49 3741 470159
Tel +49 173 4020035

[EMAIL PROTECTED]
http://www.christian-hermann.de
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] MTS310 SENSOR BOARD

[Bernardo Avila Pires]

I think I've had bus problems when I tried to do this, but I also had
a compilation problem due to wrong interface names. How did you solve
it?

2007/6/15, Christian Hermann <[EMAIL PROTECTED]>:

It is supported. If you got the actual CVS-snapshot the driver located
in tos\sensorboards\mts300 does actually support mts310 as well. I'm
using it successfully (just the sound sensor doesn't cover my needs)
If you find some way to record audio-streams with 16khz or if you're
able to use the tone-detector please tell me! I got no answers to
these problems so far...
regards
Christian

mai naaom schrieb:
> hi
> Am working on  mts310 sensor board (it is used for micaA2 motes)how
> can i compile this sensorboard with TinyOS-2.
> It is not supported by it so should i switch to TinyOS-1 or what i have to
> do?
> please someone help
> thanks in advance
>
> regards,
> Mai
>
>
> 
>
> ___
> Tinyos-help mailing list
> Tinyos-help@Millennium.Berkeley.EDU
> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

--

Christian Hermann

Am Weinberg 9
08529 Plauen
Fax +49 3741 470159
Tel +49 173 4020035

[EMAIL PROTECTED]
http://www.christian-hermann.de
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help




--
"The truth shall set you free"
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] MTS310 SENSOR BOARD

[Christian Hermann]

It is supported. If you got the actual CVS-snapshot the driver located
in tos\sensorboards\mts300 does actually support mts310 as well. I'm
using it successfully (just the sound sensor doesn't cover my needs)
If you find some way to record audio-streams with 16khz or if you're
able to use the tone-detector please tell me! I got no answers to
these problems so far...
regards
Christian

mai naaom schrieb:
> hi
> Am working on  mts310 sensor board (it is used for micaA2 motes)how
> can i compile this sensorboard with TinyOS-2.
> It is not supported by it so should i switch to TinyOS-1 or what i have to
> do?
> please someone help
> thanks in advance
> 
> regards,
> Mai
> 
> 
> 
> 
> ___
> Tinyos-help mailing list
> Tinyos-help@Millennium.Berkeley.EDU
> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

-- 

Christian Hermann

Am Weinberg 9
08529 Plauen
Fax +49 3741 470159
Tel +49 173 4020035

[EMAIL PROTECTED]
http://www.christian-hermann.de
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] MTS310 SENSOR BOARD

[mai naaom]

hi
Am working on  mts310 sensor board (it is used for micaA2 motes)how
can i compile this sensorboard with TinyOS-2.
It is not supported by it so should i switch to TinyOS-1 or what i have to
do?
please someone help
thanks in advance

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

RE: [Tinyos-help] Multichannel Adc sampling and DMA

[Oussama Chougna]

Hi Phil,


Are you sure about this:

>   Timer.fired() {
>   call Channe1One.read();
>   call ChannelTwo.read();
>   call ChannelThree.read();
>   call ChannelFour.read();
>   call ChannelFive.read();
>   call ChannelSix.read();
>   }
>
>   rather than:
>
>   ChannelOne.readDone() {
>
>   call ChannelTwo.read();
>   }
>
>   ChannelTwo.readDone() {
>   call ChannelThree.read();
>   }
>
>   The latter gives the OS flexibility in how to schedule the
I/O  
>   operations. One thing we've been talking about in core is
how >   TinyOS  
>   can best optimize for energy efficiency through intelligent
I/O  
>   scheduling.

Is the first approach only possible with the HIL ADC component
ADCReadClientC? Because with the (msp430) HAL interfaces the client should
do resource arbitration. (request() , configure() , getData(), dataReady() ,
release() ). So you cannot call getData() of each channel one after the
other in the timer.fired() event?

Which would you recommend for 100 Hz sampling? (HIL or HAL)


Thank you.


Chougna


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Philip
Levis
Sent: donderdag 14 juni 2007 19:23
To: Nicolas Esteves
Cc: tinyos-help@Millennium.Berkeley.EDU
Subject: Re: [Tinyos-help] Multichannel Adc sampling and DMA

On Jun 14, 2007, at 6:19 AM, Nicolas Esteves wrote:

> Hi,
>
> Is there a particular reason for the multi channel sampling methods  
> to be unavailable in the AdcReadClient/AdcReadNowClient/ 
> AdcReadStreamClient whereas these methods are implemented in  
> Msp430Adc12Impl. Is is for portability?

Yes. The assumption is that you're using multi-channel sampling, you  
can use the chip-specific HAL.

> I also found that no constant is available to use  
> Msp430Adc12ClientAutoDMA_RVGC or Msp430Adc12ClientAutoDMAC in  
> AdcReadClient/AdcReadNowClient/AdcReadStreamClient. Is it on  
> purpose and why? My last question is why Msp430Adc12DMAP dont  
> provide Msp430Adc12MultiChannel? is this a DMA limitation?

I'd defer to the implementers, but my guess is it's just that not  
every piece of hardware functionality currently has a software  
implementation. For example, on the atmega128, there aren't drivers  
for PWM.


>
> I would like to sample 6 Adc12 channels and store them before  
> sending data by radio so I thought that creating a component which  
> does the same thing than Msp430Adc12DMAP does but with MultiChannel  
> and then linking it into Msp430Adc12AutoDMA_RVGC, so is this a good  
> idea or should i continue with sampling the channels separately?

It's up to you; if you really need to optimize for efficiency,  
chances are you want to set up the DMA for multichannel. If the extra  
time to sample the sensors one by one is OK, then it might not be  
worth the effort to write the driver. One note: if you are going to  
sample 6 channels, then it's a good idea to write code like this:

Timer.fired() {
   call Channe1One.read();
   call ChannelTwo.read();
   call ChannelThree.read();
   call ChannelFour.read();
   call ChannelFive.read();
   call ChannelSix.read();
}

rather than:

ChannelOne.readDone() {
   call ChannelTwo.read();
}

ChannelTwo.readDone() {
   call ChannelThree.read();
}

The latter gives the OS flexibility in how to schedule the I/O  
operations. One thing we've been talking about in core is how TinyOS  
can best optimize for energy efficiency through intelligent I/O  
scheduling.

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

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

Re: [Tinyos-help] tos-install-jni can not locate java in cygwin

[Jeonghoon Kang]

If you used TinyOS install shield,
you have Java 1.4.2. at /cygdirve/c/~~~/cygwin/java

Your PATH variable defines /cygdrive/c/windows/system32/ before proper
JAVA dir.
Try *env | grep PATH*
and you can change the PATH using *unset* & *export* in the cygwin shell.

Why don't you change the name like below in windows file explorer.
c:\windows\system32\java.exe
to
c:\windows\system32\java_tinyos.exe

-jh.kang


2007/6/15, Ahmed Said <[EMAIL PROTECTED]>:

Hi,

I am using a cygwin environment, the problem is that after I install
java  and I type "which java"
I get "/cygdrive/c/windows/system32/", I think this is the reason for
getting java not found error when I type "tos-install-jni", does
anyone know how to displace this version of java by the one i
installed to be able to install the JNI code?

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




--
Jeonghoon Kang
Senior Researcher
at Korea Electronics Technology Institute(www.keti.re.kr) ;
TinyOS Korea Forum Administrator; www.tinyos.or.kr ;
work = [EMAIL PROTECTED] ;
private = [EMAIL PROTECTED] ;
www.pinkfloyd.re.kr/rnd/ ;
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Regarding battery Life

[manu suryavansh]

Hi,
The tmote sky system can work from 2.1V to 3.6V. In that case when the battery 
voltage drops to below 2.1V it will stop working and the remaining energy 
stored in the battery will not be used, so if the battery has 2200mAh of energy 
not all of it will be used, is this correct?. Is there any voltage up converter 
present on the system?
Thank you
Manu Suryavansh

   
-
Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on, 
when. ___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

RE: [Tinyos-help] Anyone used TinyOS 2.0 with TMote Sky

[Oussama Chougna]

Hello,

I'm using tinyos2 with Tmote Sky. So far, it is working well and much better
than tinyos1. Instead of tmote you have to use Telosb, that's the same
platform and thus hardware. Also read the tinyos2 tutorials, there are lots
of changes in tinyos2.

For example:

Make telosb install,x bsl,y 


For the components and interfaces documentation:

http://www.tinyos.net/tinyos-2.x/doc/html/nesdoc/telosb/


Good luck,



Chougna

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of leonardo
Sent: donderdag 14 juni 2007 18:19
To: tinyos-help@Millennium.Berkeley.EDU
Subject: Re: [Tinyos-help] Anyone used TinyOS 2.0 with TMote Sky

Hi 


I would be very interested in using tmote sky on TinyOs 2. I apologize for
the following trivial question but I am a new tinyos2 user.
I would like to make and upload the blink application, what have I to do? 
For instance for a telos mote I have just to write make telos install and
ncc, msp430-objcopy and tos-bsl are invoked. 

I have downloaded the standard tinyos 2 installation and I did not find any
tmote sky platform. 
Moreover, I tried to look at the moteiv web site
(http://www.moteiv.com/software/)
and download the boomerang software but It does not seem to contain tinyos 2
support.

Please may you help me?

Thanks a lot

Leonardo

  _  

From: tinyos-help-bounces at Millennium.Berkeley.EDU

[mailto:tinyos-help-bounces at Millennium.Berkeley.EDU
]
On Behalf Of Oussama
Chougna
Sent: Friday, June 01, 2007 1:40 PM
To: tinyos-help at Millennium.Berkeley.EDU

Subject: [Tinyos-help] Anyone used TinyOS 2.0 with TMote Sky


Hi there,

 

Does anyone have experience with using TinyOS 2 with the Tmote sky from
Moteiv?

 

 

Thanks in advance,

 

 

O.Chougna

-- next part --
An HTML attachment was scrubbed...
URL:
http://mail.millennium.berkeley.edu/pipermail/tinyos-help/attachments/200706
01/f8260228/attachment.html

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

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

[Tinyos-help] tinyos-1.x vs tinyos-2.x: radio communication compatibility

[Jordi Vilaseca]

Hi,

We're interested in communicating one node running tinyos-1.x with another
running tinyos-2.x. Physically the platform is the same (micaz), so the chip
radio is the same. I understood tinyos-2.x is 802.15.4 MAC layer compliant,
but tinyos-1.x is not. Is that the reason why the nodes cannot communicate?
If we use any IEEE stack implementation in tinyos1-x, such as modules in
contrib directory, will we be able to communicate the motes?

Thanks

Jordi Vilaseca
Universitat Politècnica de Catalunya
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help