[Tinyos-help] Hi about the Battery monitor function in RF230

[贾鹏]

Hi, there

For my experiment, the RF transmission power control is important. And the
battery voltage may drop all the way as the time elapses, I'm wondering
whether the transmission power can be inflected by the battery drop? or it
doesn't matter in a certain voltage range. I know there is a voltage
regulator in the RF230 can provide 1.8v power, but why the RF230 has the
Battery monitoring function and the threshold can set in different level?
Does this mean the power supply is essential to RF230. And I want to know
the default TinyOS RF230 driver use
this function and how the MCU handle this interruption?

Any reply is appreciated
sincerely
Peng
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Question about TestFTSP

[Hui Kang]

I searched in the directory for the definition of the topology, but 
failed. Could you point out where the file is. Also it seems the 
TimeSyncPollC, the dedicated beacon sender does not exist. 
TestTimeSyncMessage has to be changed for a dedicated beacon sender.

- Hui

Branislav Kusy wrote:
>> Hi,
>>
>> I'm looking at TestFTSP and it looks like it only works over a single 
>> hop. Is this correct or am I missing something? If so, are there any 
>> test applications that deal with FTSP over multiple hops?
>> 
> if you define CFLAGS += -DTIMESYNC_DEBUG in the Makefile, multihop will 
> be enforced in software depending on the node id. take a look at
> http://tinyos.cvs.sourceforge.net/tinyos/tinyos-2.x-contrib/stanford-lgl/apps/tests/TestFTSP/TestTimeSync.txt
> for more info (ie. how to set node ids).
>
> note that right now there are some problems with low level radio 
> timestamping which we are trying to iron out.
>
> brano
> ___
> 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] About the BER in RF230 chip

[贾鹏]

Hi there,

I've scrutinized some papers talking about the packet loss vs power and
distance etc. and try to model the routing metric. I am wondering that
whether I can investigate the Bit error rate using iris mote. I checked the
RF230 data sheet, it looks that in extended mode, when a packet CRC checking
is not right, the packet will discard. And what is the situation in basic
mode?

The trouble is, if I want to investigate the BER,  wrong packet = Packet
loss because of real loss.

anyone can give a hint?

Thanks

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

Re: [Tinyos-help] Providing and using the same interface in a module. Is this possible?

[Philip Levis]

On Aug 19, 2008, at 2:42 PM, Michael Schippling wrote:

> welcome to the club...
>
> Nicola Wegner wrote:
>> Hi,
>>
>> I found it. Stupid mistake :-(
>>
>> I have a configuration PermConfStorageC that wires  
>> PermConfStorageP. But
>> in the top level configuration I wired my app to PermConfStorageP
>> instead of PermConfStorageC. All these P's and C's confused me...
>>

http://www.tinyos.net/tinyos-2.x/doc/html/tep3.html#nesc-convention

# All public components should be suffixed with 'C'.
# All private components should be suffixed with 'P'.
# Avoid interfaces ending in 'C' or 'P'.

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

Re: [Tinyos-help] Providing and using the same interface in a module. Is this possible?

[Michael Schippling]

welcome to the club...

Nicola Wegner wrote:
> Hi,
> 
> I found it. Stupid mistake :-(
> 
> I have a configuration PermConfStorageC that wires PermConfStorageP. But 
> in the top level configuration I wired my app to PermConfStorageP 
> instead of PermConfStorageC. All these P's and C's confused me...
> 
> But thanks anyway!
> 
> Nicola
> 
> 
> 2008/8/19 Michael Schippling <[EMAIL PROTECTED] >
> 
> Are they connected in the config file?
> MS
> 
> 
> Nicola Wegner wrote:
> 
> Hi,
> 
> I have a module that uses and provides the interface Mount:
> uses interface Mount as UsedMount;
> provides interface Mount as ProvidedMount;
> 
> The implementation of ProvidedMount.mount() looks like this:
> command error_t ProvidedMount.mount() {
>  return call UsedMount.mount();
> }
> 
> I think this should be possible but I get the following error:
> PermConfStorageP.nc: In function `ProvidedMount.mount':
> PermConfStorageP.nc:72: UsedMount.mount not connected
> 
> Without the call UsedMount.mount() it compiles. I can even call
> UsedMount.mount() somewhere else in the code and it works.
> 
> Any explanations for this behavior?
> 
> Thanks Nicola
> 
> 
> 
> 
> 
> ___
> 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 mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] TinyOS 2.x Network ID

[Jim Fell]

Hello.  Does anyone know how to configure the PAN (or Network ID) in
TinyOS 2.x?  Is this the TINYOS_6LOWPAN_NETWORK_ID defined in cc2420.h?
If so, why am I seeing a PAN ID of 0x0022 with my IEEE 802.15.4 sniffer,
whereas the TINYOS_6LOWPAN_NETWORK_ID is defined as being 0x0.

 

Thanks,

 

-Jim

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

Re: [Tinyos-help] Providing and using the same interface in a module. Is this possible?

[Nicola Wegner]

Hi,

I found it. Stupid mistake :-(

I have a configuration PermConfStorageC that wires PermConfStorageP. But in
the top level configuration I wired my app to PermConfStorageP instead of
PermConfStorageC. All these P's and C's confused me...

But thanks anyway!

Nicola


2008/8/19 Michael Schippling <[EMAIL PROTECTED]>

> Are they connected in the config file?
> MS
>
>
> Nicola Wegner wrote:
>
>> Hi,
>>
>> I have a module that uses and provides the interface Mount:
>> uses interface Mount as UsedMount;
>> provides interface Mount as ProvidedMount;
>>
>> The implementation of ProvidedMount.mount() looks like this:
>> command error_t ProvidedMount.mount() {
>>  return call UsedMount.mount();
>> }
>>
>> I think this should be possible but I get the following error:
>> PermConfStorageP.nc: In function `ProvidedMount.mount':
>> PermConfStorageP.nc:72: UsedMount.mount not connected
>>
>> Without the call UsedMount.mount() it compiles. I can even call
>> UsedMount.mount() somewhere else in the code and it works.
>>
>> Any explanations for this behavior?
>>
>> Thanks Nicola
>>
>>
>> 
>>
>> ___
>> 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] Providing and using the same interface in a module. Is this possible?

[Michael Schippling]

Are they connected in the config file?
MS


Nicola Wegner wrote:
> Hi,
> 
> I have a module that uses and provides the interface Mount:
>  uses interface Mount as UsedMount;
>  provides interface Mount as ProvidedMount;
> 
> The implementation of ProvidedMount.mount() looks like this:
>  command error_t ProvidedMount.mount() {
>   return call UsedMount.mount();
>  }
> 
> I think this should be possible but I get the following error:
>  PermConfStorageP.nc: In function `ProvidedMount.mount':
>  PermConfStorageP.nc:72: UsedMount.mount not connected
> 
> Without the call UsedMount.mount() it compiles. I can even call 
> UsedMount.mount() somewhere else in the code and it works.
> 
> Any explanations for this behavior?
> 
> Thanks Nicola
> 
> 
> 
> 
> ___
> 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] Providing and using the same interface in a module. Is this possible?

[Nicola Wegner]

Hi,

I have a module that uses and provides the interface Mount:
 uses interface Mount as UsedMount;
 provides interface Mount as ProvidedMount;

The implementation of ProvidedMount.mount() looks like this:
 command error_t ProvidedMount.mount() {
  return call UsedMount.mount();
 }

I think this should be possible but I get the following error:
 PermConfStorageP.nc: In function `ProvidedMount.mount':
 PermConfStorageP.nc:72: UsedMount.mount not connected

Without the call UsedMount.mount() it compiles. I can even call
UsedMount.mount() somewhere else in the code and it works.

Any explanations for this behavior?

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

[Tinyos-help] telosb error

[maryam ebraheem]

--- On Tue, 8/19/08, maryam ebraheem <[EMAIL PROTECTED]> wrote:

From: maryam ebraheem <[EMAIL PROTECTED]>
Subject: telosb error
To: Tinyos-help@Millennium.Berkeley.EDU
Date: Tuesday, August 19, 2008, 1:56 PM







  
Hello 
I try to install my telosp but I got thi error 
After the command  make telosb 
couldn't execute msp430-gcc 
  
so I try to reinstall msp430-gcc again 
  
but when I watnt to execute this command again I couldn’t  and I got: 
$ make telosb 
make: *** No rule to make target `telosb'.  Stop. 
  
  
Need your help please , 
  
Thank you 
  
 



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

Re: [Tinyos-help] Mag.nc:65: error: 'result' redeclared as different kind of symbol

[Nicola Wegner]

Now the confusion is perfect. I can compile my code without errors in my
cygwin environment. The error only occurs when I use Ubuntu. Both
installations are in sync with the cvs repository. But this probably points
to a configuration error of my Ubuntu setup, doesn't it?


2008/8/19 Nicola Wegner <[EMAIL PROTECTED]>

> Hi,
>
> I use the MTS300 Sensorboard with micaz motes. I use the Read-interface
> implementations from SensorMts300C.
>
> My wiring:
> ===
> components new SensorMts300C();
> SensorReader0.Read -> SensorMts300C.Vref;
> SensorReader1.Read -> SensorMts300C.Temp;
>
> By now I do not use the magnetic sensor (I want to do so later). But I get
> a compile error that I don't understand from one of the TinyOS Files:
>
> And the error
> ==
> /opt/tinyos-2.x/tos/sensorboards/mts300/Mag.nc: In function
> 'MagP$Mag$gainAdjustXDone':
> /opt/tinyos-2.x/tos/sensorboards/mts300/Mag.nc:65: error: 'result'
> redeclared as different kind of symbol
> /opt/tinyos-2.x/tos/sensorboards/mts300/Mag.nc:65: error: previous
> definition of 'result' was here
> /opt/tinyos-2.x/tos/sensorboards/mts300/Mag.nc: In function
> 'MagP$Mag$gainAdjustYDone':
> /opt/tinyos-2.x/tos/sensorboards/mts300/Mag.nc:70: error: 'result'
> redeclared as different kind of symbol
> /opt/tinyos-2.x/tos/sensorboards/mts300/Mag.nc:70: error: previous
> definition of 'result' was here
>
> The according lines in the interface Mag (Mag.nc) are:
>
> 65:
>event error_t gainAdjustXDone(bool result);
>
> 70:
>   event error_t gainAdjustYDone(bool result);
>
>
> I have no idea what could be wrong with them :( Any hints?
>
> Thanks Nicola
>
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] LPL broadcasting

[Flavio Pompermaier]

Hi to all,
I've a question about the broadcasting of a message when using LPL.
>From what I see from the oscilloscope is that the packet is continuously 
>repeated
for all the receiver's LPL interval (plus some time). That's fine.
However, I do not understand why after a transmission there's always a 
listening phase.
How can I modify the duration of this listening period after a transmission and 
why 
this behaviour? Is it because the cc2420 goes automatically in RX mode after a 
TX (as
it seems from the CC2420 Finite state machine on datasheet..)?

Best regards,
FP


__
Do You Yahoo!?
Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto 
spazio gratuito per i tuoi file e i messaggi 
http://mail.yahoo.it 

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

[Tinyos-help] Mag.nc:65: error: 'result' redeclared as different kind of symbol

[Nicola Wegner]

Hi,

I use the MTS300 Sensorboard with micaz motes. I use the Read-interface
implementations from SensorMts300C.

My wiring:
===
components new SensorMts300C();
SensorReader0.Read -> SensorMts300C.Vref;
SensorReader1.Read -> SensorMts300C.Temp;

By now I do not use the magnetic sensor (I want to do so later). But I get a
compile error that I don't understand from one of the TinyOS Files:

And the error
==
/opt/tinyos-2.x/tos/sensorboards/mts300/Mag.nc: In function
'MagP$Mag$gainAdjustXDone':
/opt/tinyos-2.x/tos/sensorboards/mts300/Mag.nc:65: error: 'result'
redeclared as different kind of symbol
/opt/tinyos-2.x/tos/sensorboards/mts300/Mag.nc:65: error: previous
definition of 'result' was here
/opt/tinyos-2.x/tos/sensorboards/mts300/Mag.nc: In function
'MagP$Mag$gainAdjustYDone':
/opt/tinyos-2.x/tos/sensorboards/mts300/Mag.nc:70: error: 'result'
redeclared as different kind of symbol
/opt/tinyos-2.x/tos/sensorboards/mts300/Mag.nc:70: error: previous
definition of 'result' was here

The according lines in the interface Mag (Mag.nc) are:

65:
   event error_t gainAdjustXDone(bool result);

70:
  event error_t gainAdjustYDone(bool result);


I have no idea what could be wrong with them :( Any hints?

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

[Tinyos-help] Information on the radio send

[[EMAIL PROTECTED]]

Hi!
I have a problem with Tmote sky and its radio.
I made a nesC program that receives a fast stream of serial packets and 
forwards them to radio. My client app uses Java tools for TinyOS 2. Sometimes, 
the MoteIF.send method takes a lot longer than usual to execute: instead of a 
few milliseconds, sometimes this method takes more than 1 second to execute.
This strange delay seems to be absolutely random; maybe this problem is caused 
by radio sending on the tMote, but I don't know how to solve it. Also, this 
problem occurs even if I use BaseStation and TestSerial apps.
Could you please help me to solve the problem? Thanks!

Riccardo


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

Re: [Tinyos-help] cc2420 timing and TOSSIM (little) bugs?

[Flavio Pompermaier]

I apologize myself for errors I wrote in the previous email..I've used wrong 
jiffy duration in my
calculations...
Here it is the previous question but with correct values:

When I have to send a packet of length X, this is how the cc2420 should behave 
(in the current svn version of TinyOS 2.x):
1) Turn on the Voltage regulator and oscillator (0.61 + 0.86 (=1.47)ms 
repectively 
> 20 jiffies of CC2420_TIME_VREN + 0.86 of oscillator (from cc2420 
datasheet)
> 20* 0.0305 + 0.86 ms. 
Here the average current drain is quite low..it is about 0.020 mA, right?

2) Go into backoff (Collision Avoidance) (from 0.1525 to 0.61 ms 
> random number between 10 and 4*10 symbols 
> 5*(0.0305ms) and 20*(0.0305ms) respectively. 
Remark that in 1 jiffy I can transmit 2 symbols). 
What is the energy consumption of the backoff period? 
I think that in this phase the radio is listening to the channel..isn't it? 
In this case the (average) current drain would be about 20-21 mA (listen).

3) If Channel is free (CCA) then start transmit immediately.
What is the power consumption of CCA establishment? 
Is it really a passive measure??

4) At this point the radio start transmitting. 
If the payload has X bytes then, since from TinyOS 2.x CC2420 support variable 
payload lengths, we will have:
12 symbols (preamble, sfd, phy header i.e., 6bytes) +
 4 symbols (CRC i.e. 2 bytes)   +
   X*2 symbols (payload i.e., X bytes)  =
---> (12 + 4 + 2X)/2*0.0305ms = 1.098 ms for a payload of 28 bytes


5) Wait for an ACK reply:
> min: 12 symbols + 11bytes = 34 symbols
-> 34/2 * 0.0305 = 0.5185 ms
> max: 256 jiffies ->256 * 0.0305 ms = 7.808 ms
Also here, the radio is in listening state, right?

6) If no ack is received, repeat from point 3 but this time, 
if channel is free (CCA), wait CC2420_TIME_ACK_TURNAROUND jiffies 
just to be sure to not being waiting for an ACK. 
Thus wait others 7*0.0305ms--->0.2135 ms. 
Also here, what is the current drain of CCA measurement? Does it comes really
for free (as a register reading)??

7) Continue repeating steps from 3 to 6 (for all the duration of the receiver's 
sleep interval + 20 ms. Thus we will have an average periodic packetized wake-up
of period 1.69275 ms (for a data packet of 28 bytes)
{Calculated in this manner:
-> 0.2135(ack_turnaround_wait) + 
-> 1.098 (packet sending)+ 
-> ((0.61-0.1525)/2 + 0.1525) (Average backoff)
}. 
Voltage regulator and oscillator startup time are not taken into account because
they are present only at the first sending.
Althought the documentation says 
"The transmitters perform a message delivery by transmitting the full 
 packet over and over again for twice the duration of the receiver’s 
duty-cycle 
period", 

in the code (/opt/tinyos-2.x/tos/chips/cc2420/lpl/DefaultLplP.nc) what happens 
is:
 call SendDoneTimer.startOneShot(
 call LowPowerListening.getRxSleepInterval(currentSendMsg) + 20);
thus, this packetized wake-up has a maximum duration (if no ack is received or 
for broadcasted messages) of "receiver's sleep interval + 20 ms", as I said.
Right? Is documentation wrong..?

8) If during this process an ACK is received (only for unicast TX), 
then stop and go back to sleep only AFTER LISTENING to the channel f
or others DELAY_AFTER_RECEIVE/1024 seconds (in order to favour burst 
receptions/transmissions).

Is all this process right??
Bugs of Tossim are reported in the other mail
(http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2008-August/035658.html).
At least they are reported correctly...

Best regards,
FP



  Posta, news, sport, oroscopo: tutto in una sola pagina. 
Crea l'home page che piace a te!
www.yahoo.it/latuapagina

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