Alpha Gama | 20 Jun 13:55 2013
Picon

default generation rate CTP

Hi all, please can anybody tell me what's the default packet generation rate in CTP.
thank you 
<div><div>
<div>
<span>Hi all, please can anybody tell me what's the default packet generation rate in CTP.</span><br>
</div>
<div><span>thank you&nbsp;</span></div>
</div></div>
fatouma nour | 18 Jun 23:36 2013
Picon

hello

please help me 



user <at> 7-ede445eed82f4 ~
$   cd /opt/tinyos-1.x/apps/V

user <at> 7-ede445eed82f4 /opt/tinyos-1.x/apps/V
$ make pc
mkdir -p build/pc
    compiling MHECHERPRouter to a pc binary
ncc -o build/pc/main.exe -g -O0 -pthread -fnesc-nido-tosnodes=1000 -fnesc-simu
te -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=pc -fnesc-cfile=b
ld/pc/app.c -board=micasb -DIDENT_PROGRAM_NAME=\"MHECHERPRouter\" -DIDENT_USER
D=\"user\" -DIDENT_HOSTNAME=\"7-ede445eed82f4\" -DIDENT_USER_HASH=0x6969d503L
IDENT_UNIX_TIME=0x51c0c434L -DIDENT_UID_HASH=0xf6406790L MHECHERPRouter.nc -lm
MHECHERPPSM.nc: In function `Envoie':
MHECHERPPSM.nc:123: parse error before `float'
GaussianEliminationM.nc: In function `LinearSystem.solve':
GaussianEliminationM.nc:43: implicit declaration of function `ivector'
GaussianEliminationM.nc:43: warning: assignment makes pointer from integer wit
ut a cast
GaussianEliminationM.nc:44: warning: assignment makes pointer from integer wit
ut a cast
GaussianEliminationM.nc:45: warning: assignment makes pointer from integer wit
ut a cast
GaussianEliminationM.nc:87: implicit declaration of function `free_ivector'
make: *** [exe0] Error 1

user <at> 7-ede445eed82f4 /opt/tinyos-1.x/apps/V
$

<div><div dir="ltr">please help me&nbsp;<div><br></div>
<div><br></div>
<div>
<div><br></div>
<div>user <at> 7-ede445eed82f4 ~</div>
<div>$ &nbsp; cd /opt/tinyos-1.x/apps/V</div>
<div><br></div>
<div>user <at> 7-ede445eed82f4 /opt/tinyos-1.x/apps/V</div>
<div>$ make pc</div>
<div>mkdir -p build/pc</div>
<div>&nbsp; &nbsp; compiling MHECHERPRouter to a pc binary</div>
<div>ncc -o build/pc/main.exe -g -O0 -pthread -fnesc-nido-tosnodes=1000 -fnesc-simu</div>
<div>te -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=pc -fnesc-cfile=b</div>
<div>ld/pc/app.c -board=micasb -DIDENT_PROGRAM_NAME=\"MHECHERPRouter\" -DIDENT_USER</div>
<div>D=\"user\" -DIDENT_HOSTNAME=\"7-ede445eed82f4\" -DIDENT_USER_HASH=0x6969d503L</div>
<div>IDENT_UNIX_TIME=0x51c0c434L -DIDENT_UID_HASH=0xf6406790L MHECHERPRouter.nc -lm</div>
<div>MHECHERPPSM.nc: In function `Envoie':</div>
<div>MHECHERPPSM.nc:123: parse error before `float'</div>
<div>GaussianEliminationM.nc: In function `LinearSystem.solve':</div>
<div>GaussianEliminationM.nc:43: implicit declaration of function `ivector'</div>
<div>GaussianEliminationM.nc:43: warning: assignment makes pointer from integer wit</div>
<div>ut a cast</div>
<div>GaussianEliminationM.nc:44: warning: assignment makes pointer from integer wit</div>
<div>ut a cast</div>
<div>GaussianEliminationM.nc:45: warning: assignment makes pointer from integer wit</div>
<div>ut a cast</div>
<div>GaussianEliminationM.nc:87: implicit declaration of function `free_ivector'</div>
<div>make: *** [exe0] Error 1</div>
<div><br></div>
<div>user <at> 7-ede445eed82f4 /opt/tinyos-1.x/apps/V</div>
<div>$</div>
<div><br></div>
</div> 		 	   		  </div></div>
Syed Abdul basir | 18 Jun 23:10 2013
Picon

tinyos(tossim) please help thanks

mkdir -p simbuild/micaz
  placing object files in simbuild/micaz
  writing XML schema to app.xml
  compiling myProtocolAppC to object file sim.o
ncc -c -shared -fPIC -o simbuild/micaz/sim.o -g -O0 -tossim -fnesc-nido-tosnodes=1000 -fnesc-simulate -fnesc-nido-motenumber=sim_node\(\) -fnesc-gcc=gcc -Wall -Wshadow -Wnesc-all -target=micaz -fnesc-cfile=simbuild/micaz/app.c -board=micasb -DDEFINED_TOS_AM_GROUP=0x22 --param max-inline-insns-single=100000 -DIDENT_APPNAME=\"myProtocolAppC\" -DIDENT_USERNAME=\"root\" -DIDENT_HOSTNAME=\"basir-SVT1312C4\" -DIDENT_USERHASH=0x3db05e06L -DIDENT_TIMESTAMP=0x51c0c20eL -DIDENT_UIDHASH=0x9d4bc979L -Wno-nesc-data-race myProtocolAppC.nc   -fnesc-dump=components -fnesc-dump=variables -fnesc-dump=constants -fnesc-dump=typedefs -fnesc-dump=interfacedefs -fnesc-dump=tags -fnesc-dumpfile=app.xml
In file included from /opt/tinyos-2.1.0/tos/chips/cc2420/packet/sim/CC2420PacketC.nc:25,
                 from /opt/tinyos-2.1.0/tos/chips/cc2420/csma/sim/CC2420CsmaC.nc:16,
                 from /opt/tinyos-2.1.0/tos/chips/cc2420/sim/CC2420RadioC.nc:63,
                 from /opt/tinyos-2.1.0/tos/chips/cc2420/sim/CC2420ActiveMessageC.nc:75,
                 from /opt/tinyos-2.1.0/tos/platforms/micaz/sim/ActiveMessageC.nc:61,
                 from myProtocolAppC.nc:20:
In component `CC2420PacketP':
/opt/tinyos-2.1.0/tos/chips/cc2420/packet/sim/CC2420PacketP.nc: In function `getNetwork':
/opt/tinyos-2.1.0/tos/chips/cc2420/packet/sim/CC2420PacketP.nc:66: warning: initialization from incompatible pointer type
/opt/tinyos-2.1.0/tos/chips/cc2420/lpl/DummyLplC.nc:39:2: warning: #warning "*** LOW POWER COMMUNICATIONS DISABLED ***"
In component `myProtocolAppC':
myProtocolAppC.nc: At top level:
myProtocolAppC.nc:51: cannot find `TimerACK'
myProtocolAppC.nc:55: cannot find `AMSenderC'
make: *** [sim-exe] Error 1
root <at> basir-SVT1312C4E:/opt/tinyos-2.1.0/apps/Proposed Protocol# gedit myProtocolAppC.nc
root <at> basir-SVT1312C4E:/opt/tinyos-2.1.0/apps/Proposed Protocol# gedit myProtocolAppC.nc
root <at> basir-SVT1312C4E:/opt/tinyos-2.1.0/apps/Proposed Protocol# make micaz sim
mkdir -p simbuild/micaz
  placing object files in simbuild/micaz
  writing XML schema to app.xml
  compiling myProtocolAppC to object file sim.o
ncc -c -shared -fPIC -o simbuild/micaz/sim.o -g -O0 -tossim -fnesc-nido-tosnodes=1000 -fnesc-simulate -fnesc-nido-motenumber=sim_node\(\) -fnesc-gcc=gcc -Wall -Wshadow -Wnesc-all -target=micaz -fnesc-cfile=simbuild/micaz/app.c -board=micasb -DDEFINED_TOS_AM_GROUP=0x22 --param max-inline-insns-single=100000 -DIDENT_APPNAME=\"myProtocolAppC\" -DIDENT_USERNAME=\"root\" -DIDENT_HOSTNAME=\"basir-SVT1312C4\" -DIDENT_USERHASH=0x3db05e06L -DIDENT_TIMESTAMP=0x51c0c712L -DIDENT_UIDHASH=0xaf3e228eL -Wno-nesc-data-race myProtocolAppC.nc   -fnesc-dump=components -fnesc-dump=variables -fnesc-dump=constants -fnesc-dump=typedefs -fnesc-dump=interfacedefs -fnesc-dump=tags -fnesc-dumpfile=app.xml
In file included from /opt/tinyos-2.1.0/tos/chips/cc2420/packet/sim/CC2420PacketC.nc:25,
                 from /opt/tinyos-2.1.0/tos/chips/cc2420/csma/sim/CC2420CsmaC.nc:16,
                 from /opt/tinyos-2.1.0/tos/chips/cc2420/sim/CC2420RadioC.nc:63,
                 from /opt/tinyos-2.1.0/tos/chips/cc2420/sim/CC2420ActiveMessageC.nc:75,
                 from /opt/tinyos-2.1.0/tos/platforms/micaz/sim/ActiveMessageC.nc:61,
                 from myProtocolAppC.nc:20:
In component `CC2420PacketP':
/opt/tinyos-2.1.0/tos/chips/cc2420/packet/sim/CC2420PacketP.nc: In function `getNetwork':
/opt/tinyos-2.1.0/tos/chips/cc2420/packet/sim/CC2420PacketP.nc:66: warning: initialization from incompatible pointer type
/opt/tinyos-2.1.0/tos/chips/cc2420/lpl/DummyLplC.nc:39:2: warning: #warning "*** LOW POWER COMMUNICATIONS DISABLED ***"
In component `myProtocolAppC':
myProtocolAppC.nc: At top level:
myProtocolAppC.nc:21: component AlarmMilli32C not found
myProtocolAppC.nc:21: component `AlarmMilli32C' is not generic
myProtocolAppC.nc:40: no match
myProtocolAppC.nc:51: cannot find `TimerACK'
myProtocolAppC.nc:55: cannot find `AMSenderC'
make: *** [sim-exe] Error 1
root <at> abcdefg:/opt/tinyos-2.1.0/apps/Proposed Protocol# myProtocolAppC.nc:21: component AlarmMilli32C not found
myProtocolAppC.nc:21:: command not found


<div><div>mkdir -p simbuild/micaz<br>&nbsp; placing object files in simbuild/micaz<br>&nbsp; writing XML schema to app.xml<br>&nbsp; compiling myProtocolAppC to object file sim.o<br>ncc -c -shared -fPIC -o simbuild/micaz/sim.o -g -O0 -tossim -fnesc-nido-tosnodes=1000 -fnesc-simulate -fnesc-nido-motenumber=sim_node\(\) -fnesc-gcc=gcc -Wall -Wshadow -Wnesc-all -target=micaz -fnesc-cfile=simbuild/micaz/app.c -board=micasb -DDEFINED_TOS_AM_GROUP=0x22 --param max-inline-insns-single=100000 -DIDENT_APPNAME=\"myProtocolAppC\" -DIDENT_USERNAME=\"root\" -DIDENT_HOSTNAME=\"basir-SVT1312C4\" -DIDENT_USERHASH=0x3db05e06L -DIDENT_TIMESTAMP=0x51c0c20eL -DIDENT_UIDHASH=0x9d4bc979L -Wno-nesc-data-race myProtocolAppC.nc&nbsp;&nbsp; -fnesc-dump=components -fnesc-dump=variables -fnesc-dump=constants -fnesc-dump=typedefs -fnesc-dump=interfacedefs
 -fnesc-dump=tags -fnesc-dumpfile=app.xml<br>In file included from /opt/tinyos-2.1.0/tos/chips/cc2420/packet/sim/CC2420PacketC.nc:25,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from /opt/tinyos-2.1.0/tos/chips/cc2420/csma/sim/CC2420CsmaC.nc:16,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from /opt/tinyos-2.1.0/tos/chips/cc2420/sim/CC2420RadioC.nc:63,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from /opt/tinyos-2.1.0/tos/chips/cc2420/sim/CC2420ActiveMessageC.nc:75,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from /opt/tinyos-2.1.0/tos/platforms/micaz/sim/ActiveMessageC.nc:61,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from myProtocolAppC.nc:20:<br>In component
 `CC2420PacketP':<br>/opt/tinyos-2.1.0/tos/chips/cc2420/packet/sim/CC2420PacketP.nc: In function `getNetwork':<br>/opt/tinyos-2.1.0/tos/chips/cc2420/packet/sim/CC2420PacketP.nc:66: warning: initialization from incompatible pointer type<br>/opt/tinyos-2.1.0/tos/chips/cc2420/lpl/DummyLplC.nc:39:2: warning: #warning "*** LOW POWER COMMUNICATIONS DISABLED ***"<br>In component `myProtocolAppC':<br>myProtocolAppC.nc: At top level:<br>myProtocolAppC.nc:51: cannot find `TimerACK'<br>myProtocolAppC.nc:55: cannot find `AMSenderC'<br>make: *** [sim-exe] Error 1<br>root <at> basir-SVT1312C4E:/opt/tinyos-2.1.0/apps/Proposed Protocol# gedit myProtocolAppC.nc<br>root <at> basir-SVT1312C4E:/opt/tinyos-2.1.0/apps/Proposed Protocol# gedit myProtocolAppC.nc<br>root <at> basir-SVT1312C4E:/opt/tinyos-2.1.0/apps/Proposed Protocol# make micaz sim<br>mkdir -p simbuild/micaz<br>&nbsp; placing object files in simbuild/micaz<br>&nbsp; writing XML schema to app.xml<br>&nbsp; compiling
 myProtocolAppC to object file sim.o<br>ncc -c -shared -fPIC -o simbuild/micaz/sim.o -g -O0 -tossim -fnesc-nido-tosnodes=1000 -fnesc-simulate -fnesc-nido-motenumber=sim_node\(\) -fnesc-gcc=gcc -Wall -Wshadow -Wnesc-all -target=micaz -fnesc-cfile=simbuild/micaz/app.c -board=micasb -DDEFINED_TOS_AM_GROUP=0x22 --param max-inline-insns-single=100000 -DIDENT_APPNAME=\"myProtocolAppC\" -DIDENT_USERNAME=\"root\" -DIDENT_HOSTNAME=\"basir-SVT1312C4\" -DIDENT_USERHASH=0x3db05e06L -DIDENT_TIMESTAMP=0x51c0c712L -DIDENT_UIDHASH=0xaf3e228eL -Wno-nesc-data-race myProtocolAppC.nc&nbsp;&nbsp; -fnesc-dump=components -fnesc-dump=variables -fnesc-dump=constants -fnesc-dump=typedefs -fnesc-dump=interfacedefs -fnesc-dump=tags -fnesc-dumpfile=app.xml<br>In file included from /opt/tinyos-2.1.0/tos/chips/cc2420/packet/sim/CC2420PacketC.nc:25,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from
 /opt/tinyos-2.1.0/tos/chips/cc2420/csma/sim/CC2420CsmaC.nc:16,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from /opt/tinyos-2.1.0/tos/chips/cc2420/sim/CC2420RadioC.nc:63,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from /opt/tinyos-2.1.0/tos/chips/cc2420/sim/CC2420ActiveMessageC.nc:75,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from /opt/tinyos-2.1.0/tos/platforms/micaz/sim/ActiveMessageC.nc:61,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from myProtocolAppC.nc:20:<br>In component `CC2420PacketP':<br>/opt/tinyos-2.1.0/tos/chips/cc2420/packet/sim/CC2420PacketP.nc: In function `getNetwork':<br>/opt/tinyos-2.1.0/tos/chips/cc2420/packet/sim/CC2420PacketP.nc:66: warning: initialization from incompatible pointer
 type<br>/opt/tinyos-2.1.0/tos/chips/cc2420/lpl/DummyLplC.nc:39:2: warning: #warning "*** LOW POWER COMMUNICATIONS DISABLED ***"<br>In component `myProtocolAppC':<br>myProtocolAppC.nc: At top level:<br>myProtocolAppC.nc:21: component AlarmMilli32C not found<br>myProtocolAppC.nc:21: component `AlarmMilli32C' is not generic<br>myProtocolAppC.nc:40: no match<br>myProtocolAppC.nc:51: cannot find `TimerACK'<br>myProtocolAppC.nc:55: cannot find `AMSenderC'<br>make: *** [sim-exe] Error 1<br>root <at> abcdefg:/opt/tinyos-2.1.0/apps/Proposed Protocol# myProtocolAppC.nc:21: component AlarmMilli32C not found<br>myProtocolAppC.nc:21:: command not found<br><br><div><br></div>
</div></div>
TinyUser | 18 Jun 18:23 2013
Picon

XM1000 and I2C

Hello everybody!
   I started a new project which involves working on an Advanticsys XM1000
mote ( http://www.advanticsys.com/wiki/index.php?title=XM1000 which runs
TinyOS) and I2C sensors. For now I just have one MCP9800 temperature sensor
( http://ww1.microchip.com/downloads/en/DeviceDoc/21909d.pdf ). Since I
couldn't find any tutorial/example about I2C + TinyOS i was wondering if
some of you had already worked on something like that. Basically I was
trying to retrieve the temperature (I would be satisfied even just
retrieving the raw bit data from the sensor's register) from the sensor but
I can't find anything online. 

(Yes, I know that the mote already has a temp sensor. I'm just trying to
learn how to work with I2C since i'm planning to expand the mote with
accelerometer/gyroscope sensors soon)

--
View this message in context: http://tinyos-help.10906.n7.nabble.com/XM1000-and-I2C-tp23281.html
Sent from the TinyOS - Help mailing list archive at Nabble.com.
sarahgros | 18 Jun 18:19 2013
Picon

communicate with base


Hello,

I would like to know which interface(s) I have to use to allow a node
communicate with a base who read temperature. Thanks of that, I would like to
read these temperatures in a database (PostgreSQL).

Is interface "SendMsg" enough ? I have added these lines at the end of my
program :
 event result_t SendMsg.sendDone(TOS_MsgPtr sent, result_t success) {

           return SUCCESS;

Have I to use tasks or other events ?

I am using sensor mts310, iris platform.

Thank you.

Muhammad Aamir Shah | 14 Jun 22:11 2013
Picon

Implementation of CTP and Multihop LQI in TOSSIM

Dear all,
I am a beginner, I have gone through the manual. Now i want to evaluate the performance of CTP and Multihop LQI in TOSSIM. I know i have to write a simple application for that purpose but how can i include CTP or Multihop LQI in my application. Both components are available in tos/lib/net but i dont know how to include those components in my application. Should i write a top level configuration for those components. I am very confused. Any help here will be immensely appreciated. Thanks in advance

<div><div dir="ltr">Dear all,<div>I am a beginner, I have gone through the manual. Now i want to evaluate the performance of CTP and Multihop LQI in TOSSIM. I know i have to write a simple application for that purpose but how can i include CTP or Multihop LQI in my application. Both components are available in tos/lib/net but i dont know how to include those components in my application. Should i write a top level configuration for those components. I am very confused. Any help here will be immensely appreciated. Thanks in advance<br><div>
<div><div dir="ltr"><br></div></div>
</div>
</div>
</div></div>
Mariana Segovia | 14 Jun 18:59 2013
Picon

TinyOS simulator

Hi,

I want to implement different routing attacks to CTP.
Is there any open source TinyOS simulator where I could specify different code to run in
different nodes? For example, multiple nodes running an application that uses 
CTP as the routing protocol and a node that runs a different routing protocol (CTP with
modifications in order to attract traffic to it).

Best Regards,

Mariana Segovia.
<div>
    <span>Hi,</span>
    <div><br></div>
    <div>I want to implement
      different routing attacks to CTP.</div>
    <div>Is there any open source
      TinyOS simulator where I could specify different code to run in</div>
    <div>different nodes? For
      example, multiple nodes running an application that uses&nbsp;</div>
    <div>CTP as the routing protocol
      and a node that runs a different routing protocol (CTP with</div>
    <div>modifications in order to
      attract traffic to it).</div>
    <div><br></div>
    <div>Best Regards,</div>
    <div><br></div>
    <div>Mariana Segovia.</div>
  </div>
Sascha Hevelke | 14 Jun 17:31 2013
Picon

simple code problem, need help understanding compiler error

Hi everyone,

I am currently working on an implementation of a simple interface. My 
code looks as following:

module CorrectionMessageC {

     provides interface CorrectionValueInterface;
}
implementation {

     command void 
CorrectionValueInterface.generateOutlierMessage(uint16_t xVals[], 
uint16_t* yVals[], uint16_t valC) {

         uint8_t dataLength = 16;
         uint16_t countVals = 2*valC;
         uint16_t arraySize =countVals * dataLength / 7;;

         uint16_t currIndex = 0;
         uint8_t message[arraySize];
     }
}

Until here everything is fine, it compiles without errors. Now if i 
alter the code and add e.g. an if statement like so:

command void CorrectionValueInterface.generateOutlierMessage(uint16_t 
xVals[], uint16_t yVals[], uint16_t valC) {

         uint8_t dataLength = 16;
         uint16_t countVals = 2*valC;
         uint16_t arraySize =countVals * dataLength / 7;

         if (1==1) {
         }

         uint16_t currIndex = 0;
         uint8_t message[arraySize];
}

the compiler says 'CorrectionMessageC.nc:18: syntax error before 
`currIndex''. I don't see what is wrong here, am I overseeing something 
here?

Thanks in advance

P.S.: I'm using tinyos 2.1.0 and telosb motes if that makes a difference
Thomas Pötsch | 13 Jun 14:49 2013
Picon
Picon

6LoWPAN Plugtest at IETF Berlin July 27-28th

Hello all,

there is a 6LoWPAN interoperability test coming up in July in Berlin, cf. the 
email below. Is anyone of the blip/6LoWPAN contributors planning to 
join?

The main purpose of this test is to check inter-working when the HC is enabled 
(as in RFC 4944 & 6775) and disabled. The nodes are set to communicate 
directly with EUI 16 bits and 64 bits LL addressing. ICMP messages are used as 
applications.

Viele Grüße,
Thomas Pötsch

------------------------------------------------
Thomas Pötsch, M.Sc.
Ph.D Student

Communication Networks Group - FB 1
University of Bremen
Otto-Hahn-Allee 1
28359 Bremen
Germany

Tel.: +49 421 218 62376
Fax: +49 421 218 62750
E-Mail: thp <at> comnets.uni-bremen.de
Web: http://www.comnets.uni-bremen.de/~thp
Building: NW1 Room: N2260

----------  Forwarded Message  ----------

Subject: [6lowpan] 6LoWPAN Plugtest at IETF Berlin July 27-28th
Date: Thursday 28 March 2013, 08:52:29
From: Zach Shelby <zach <at> sensinode.com>
To: 6lowpan <at> ietf.org WG <6lowpan <at> ietf.org>

ETSI, the IPSO Alliance and IPv6 Forum have now announced the first 6LoWPAN 
Plugtest to be held this summer in conjunction with the IETF in Berlin on July 
27th and 28th. This Plugtest continues the successful series of open industry 
Internet of Things Plugtests, previously two CoAP Plugtests have been held.

http://www.etsi.org/news-events/events/663-2013-6lowpan-plugtest

We encourage anyone involved with 6LoWPAN stacks, or using 6LoWPAN in 
products, to participate in this event. The event is free, and completely open 
to both industry and academia, there is no requirement to be an IPSO or ETSI 
member. Please pass the word around!

The event focuses on testing of 6LoWPAN Header Compression (RFC6282) and 
6LoWPAN Neighbour Discovery (RFC6775) in a Host - Border Router configuration. 
The IPSO Alliance is specifying 802.15.4-2006 and 802.15.4g 868MHz interop 
configurations for the event. Other PHY/MAC combinations (e.g. PLC, Z-Wave, 
BT-LE, DECT ULP etc.) can also be tested by bringing the needed adaptation 
equipment.

Zach

--

-- 
Zach Shelby, Chief Nerd, Sensinode Ltd.
http://www.sensinode.com  <at> SensinodeIoT
Mobile: +358 40 7796297
Twitter:  <at> zach_shelby
LinkedIn: http://fi.linkedin.com/in/zachshelby
6LoWPAN Book: http://6lowpan.net

_______________________________________________
6lowpan mailing list
6lowpan <at> ietf.org
https://www.ietf.org/mailman/listinfo/6lowpan

-----------------------------------------

Sean Dekker | 11 Jun 18:50 2013
Picon

Real ADC values from SHT11 sensor on TelosB

Hi all,

Can someone please tell me what is the range of RAW data from the temparature sensor on TelosB? I was thinking it should be 0-4096 but I am getting values like 6553 or so...Am I doing something wrong?

Also, for the conversion formula...is the conversion formula different when the TelosB is powered via USB compared when its powered by AA batteries?


Regards,
Sean.
<div><span><span>Hi all,<br><br>Can someone please tell me what is the range of RAW data from the temparature sensor on TelosB? I was thinking it should be 0-4096 but I am getting values like 6553 or so...Am I doing something wrong?<br><br>Also, for the conversion formula...is the conversion formula different when the TelosB is powered via USB compared when its powered by AA batteries?<br><br><br>Regards,<br>Sean.</span></span></div>
Mikhail Afanasov | 11 Jun 14:03 2013
Picon

CfP: Int. Workshop on Real-world Wireless Sensor Networks - Submission approaching!

Call for Papers: The Fifth Workshop on Real-World Wireless Sensor Networks
==========================================================================

                        19-20 September 2013
                         Como Lake (Italy)
       http://realwsn.deib.polimi.it
                 Follow REALWSN on Twitter:  <at> RealWSN!

We are excited to announce that the fifth Workshop on Real-World
Wireless Sensor will be held at the Como Lake, Italy in September 2013.

The purpose of the fifth Workshop on Real-World Wireless Sensor
Networks (REALWSN) is to bring together researchers and practitioners
working in the area of sensor networks, with focus on real-world
experiments or deployments. Included are, nontheless, new forms
of sensing such as those that leverage smart phones, Internet of
Things, RFIDs, and robots.

When working with real-world experiments or deployments, many new
issues arise: the network environment may be composed of a variety of
different technologies, leading to very heterogeneous network
structures; software development for large scale networks poses new
types of problems; prototype networks may differ significantly from
the deployed system; actual sensor network deployments may need a
complex combination of autonomous and manual
configuration. Furthermore, results obtained through simulation are
typically not directly applicable to operational networks and it is
therefore imperative for the community to produce results from
experimental research.

Authors are invited to submit papers (12 pages, Springer format, 10
point font size) for presentation at the workshop. Papers will be
selected based on originality, technical merit, and
relevance. Submissions must be fully anonimized, as REALWSN will apply
a double-blind review process. Accepted papers will be published by
Springer in the Lecture Notes on Electrical Engineering series and
indexed by all major digital libraries (e.g., ISI, Scopus, Google
Scholar, ...).

All topics pertaining to real-world wireless sensor networks and modern
forms of sensing are of interest, including but not limited to:
    * Experiences with real-world deployments
    * Mining real-world sensor network data
    * Sensor systems leveraging smart phones (crowd sensing)
    * Sensors systems involving Internet of Things (IoT), RFIDs, robots
    * Experimental validation/refutation of previous simulation
      results obtained by others
    * Real-world performance of self-organization and self-management
    * Debugging, testing, validation, and management
    * Deployment and configuration
    * Applications in medicine, industry, science, environmental monitoring
    * Security and trust
    * Scalability in practice
    * Development and prototyping platforms
    * Operating systems, sensor network programming paradigms, and languages
    * Middleware for heterogeneous networks
    * Real-time and dependability issues
    * Hardware support for real-world sensor networks
    * Robustness at all levels: communication, software, hardware
    * Energy efficient protocols
    * Hardware and software methods for energy measurement and profiling

Important dates:
    * Electronic submissions due: June 21st, 2013
    * Notification of acceptance: August 8th, 2013
    * Camera-ready copy due: August 30th, 2013
    * Workshop: 19-20 September 2013

We will organize a poster and demo session as well. The deadline will
be August 15th 2013, notification August 22nd 2013. A separate call
will be distributed.

Organizers:

Workshop Chair:
    * Luca Mottola, Politecnico di Milano, Italy and SICS, Sweden

Program committee chairs:
    * Koen Langendoen, TUD, The Netherlands
    * Wen Hu CSIRO, Australia

Poster/demo chairs:
    * Thiemo Voigt, Uppsala University and SICS, Sweden
    * Silvia Santini, TU Darmstadt, Germany

Program committee:
    * Nirupama Bulusu, Portland State University, USA
    * Per Gunningberg, Uppsala University, Sweden
    * Chamath Keppitiyagame, University of Colombo, Sri Lanka
    * Gian Pietro Picco, University of Trento, Italy
    * Utz Rödig, University of Lancaster, UK
    * Christian Rohner, Uppsala University, Sweden
    * Kay Römer, ETH Zürich, Switzerland
    * Jochen Schiller, FU Berlin, Germany
    * Cormac Sreenan, UC Cork, Ireland
    * Tim Wark, CSIRO, Australia
    * Neal Patwari, University of Utah, USA
    * Omprakash Gnawali, University of Houston, USA
    * Yu (Jason) Gu, Singapore University of Technology and Design,
Singapore
    * Olga Saukh, ETH Zürich, Switzerland
    * Niki Trigoni, University of Oxford, UK
    * Marco Zuniga, TU Delft, The Netherlands
    * Prasant Misra, SICS, Sweden
    * Chiara Petrioli, University of Rome, Italy
    * Philipp Sommer, CSIRO, Australia
    * Gianluca Dini, University of Pisa, Italy
    * Wang Jiliang, Hong Kong University of Science and Technology, Hong
Kong
    * Geoffrey Challen, University at Buffalo, USA
    * Marcus Chang, JHU, USA

Gmane