jobishjohn ips | 26 Mar 17:23 2015
Picon

SFD pin of CC2420 is NOT going into active state -during reception - telosb

Hi,

Sorry for the inconvenience due to a lengthy mail. Requesting you to spent 2 minutes on this issue.

I have assembled a telosB board with the help of layout given in http://www.tinyos.net/scoop/special/hardware to continue with my research studies.

Let me call this as “test telosb board”. I also have some other working telosb boards which are purchased from a local distributor.

The “test telosb” does not work either as transmitter or receiver. Please give me some directions to debug this board. My trials as listed below (I use tinyos 2.1.2 on Ubuntu).

Debugging method1

I have programmed one purchased telosb as transmitter and the “test telosb board” as receiver.

The transmitter is programmed to broadcast  periodic AM messages.

The receiver is programmed with the standard “Basestation” application. But the receiver is not receiving any data.

While debugging, I could find that the “SFD” pin of the cc2420 in the test board is NOT going into active state (high) at all.

The nesC program running on the transmitter & the receiver are tested using purchased telosb boards. In this case everything works fine.

Debugging method2:

I have a transmitter (test telosb board) and a receiver (purchased telosb).

Receiver is programmed with “Basesation” application. The transmitter is programmed to broadcast some periodic AM messages.

The nesC program running on the transmitter signals the event “AMSend.sendDone” with success.

In this case , the “SFD pin ” works as expected (Fig 15 in cc2420 data-sheet). Also I am able to measure a transmission power of approx. 0 dBm around 2.45GHz band using a spectrum analyzer.

But the receiver does not receive any data.

Other than radio, everything works fine in the test telosb board.

Thanks for your valuable time. 

Regards

John J




<div><div dir="ltr">

	
	
	
	

<p>Hi,</p>
<p>
</p>
<p>Sorry for the inconvenience due to a lengthy mail. Requesting you to spent 2 minutes on this issue. <br></p>
<p>
</p>
<p>I have assembled a telosB board with the help of layout given in 
<a href="http://www.tinyos.net/scoop/special/hardware">http://www.tinyos.net/scoop/special/hardware</a>
to continue with my research studies.</p>
<p>
</p>
<p>Let me call this as
&ldquo;test telosb board&rdquo;. I also have some
other working telosb boards which are purchased from a local
distributor.</p>
<p>
</p>
<p>The &ldquo;test telosb&rdquo;
does not work either as transmitter or receiver. Please give me some
directions to debug this board. My trials as listed below (I use tinyos 2.1.2
on Ubuntu).</p>
<p>
</p>
<p>Debugging method1

</p>

<p>I have programmed one
purchased telosb as transmitter and the &ldquo;test
telosb board&rdquo; as receiver.</p>
<p>
</p>
<p>The transmitter is programmed to broadcast&nbsp; periodic AM messages.</p>
<p>The receiver is
programmed with the standard &ldquo;Basestation&rdquo;  application. But the receiver
is not receiving any data.</p>
<p>
</p>
<p>While debugging, I
could find that the &ldquo;SFD&rdquo; pin  of the cc2420 in the test board is
NOT going into active state (high) at all.</p>
<p>
</p>
<p>The nesC program running on the transmitter &amp; the receiver
are tested using  purchased telosb boards. In this case everything
works fine.</p>
<p>Debugging
method2:</p>

<p>I have a transmitter
(test telosb board)  and a receiver (purchased telosb).</p>

<p>Receiver is
programmed with &ldquo;Basesation&rdquo; application. The transmitter is programmed to broadcast some periodic AM messages.</p>
<p>
</p>
<p>The nesC program 
running on the  transmitter signals the event  &ldquo;AMSend.sendDone&rdquo;
with
success.</p>
<p>
</p>
<p>In this case , the
&ldquo;SFD pin &rdquo; works as expected (Fig 15 in cc2420 data-sheet).  Also
I  am able to measure a transmission power of approx. 0 dBm around
2.45GHz band using a spectrum analyzer.</p>
<p>But the receiver
does not receive any data.</p>
<p>
</p>
<p>Other than radio,
everything works fine  in the test telosb board.</p>
<p>
</p>
<p>Thanks for your
valuable time.&nbsp; 
</p>
<p>
</p>
<p>Regards<br></p>
<p>John J</p>
<p><br></p>
<p><br></p>
<p><br></p>

</div></div>
Aruna Kurhade | 26 Mar 13:08 2015
Picon

Re: Tinyos-help Digest, Vol 143, Issue 10

tossim execution requires actual mote for execution of the program

On Thu, Mar 26, 2015 at 12:30 AM, <tinyos-help-request <at> millennium.berkeley.edu> wrote:
Send Tinyos-help mailing list submissions to
        tinyos-help <at> millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
        https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
        tinyos-help-request <at> millennium.berkeley.edu

You can reach the person managing the list at
        tinyos-help-owner <at> millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

   1. Workaround for Timer bug ( IRIS modules) (Roadstar Runner)


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

Message: 1
Date: Wed, 25 Mar 2015 00:46:58 -0400
From: Roadstar Runner <redstripeva2 <at> gmail.com>
Subject: [Tinyos-help] Workaround for Timer bug ( IRIS modules)
To: tinyos forum <tinyos-help <at> millennium.berkeley.edu>, Miklos Maroti
        <mmaroti <at> gmail.com>,    Janos Sallai <sallai <at> isis.vanderbilt.edu>, Eric
        Decker <cire831 <at> gmail.com>
Message-ID:
        <CAN3Ao+wg18yqiRvfDzaihbx8cO9x77m8CZ+Edd5e-4PA388_VA <at> mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

I recently cam across a possible bug in the Timer module for the IRIS
motes. I occasionally noticed that the timer would fire very late thus
causing a whole series of cascading failures in my modules.

After days of debugging, I traced the problem to the routine setInterrupt()
in the  module Atm1281AlarmAsyncP.
If the alarm is armed to fire after 1 TCNT tick, in some situations OCR2A
will be loaded with a value that will essentially be in the "past",  thus
requiring TCNT2 to wrap around for the compare to occur (about 255 ms late).
Since TCNT2 is a free running timer, if TCNT2 increments after the current
time is captured by the call to Counter.get(), the *fired *flag will not be
set, even though the alarm has technically expired. After this, under some
circumstances, the compare register can be loaded with a wrong value.
Consider the following situation when setInterrupt() is called


to = 24
dt = 1
TCNT2 =1
base = 23

now if TCNT increments (TCNT2 = 2)  after the current  time is captured
  uint32_t now = call Counter.get();

Then the following condition will fail
 /* Check if alarm expired */
   if ((uint32_t)(now - t0) >= dt)
The following variables will be updated as indicated below, to compute
 anew value for OCCR2A
alarm_in = 2
newOcr2A = 1

Since newOcr2A   =1  and TCNT2 =2 , When OCCR2A is loaded, it will delay
the next alarm by 255 ms.

As a quick workaround, i added the following code to force the timers to
fire after calling setOcr2A(newOcr2A);

//work around
if(newOcr2A >= TCNT)
{
diff =  newOcr2A - TCNT   ;
}
else
{
diff =  (0xFF - TCNT) + newOcr2A ;
}
if( diff   > MAXT)
{
fired = TRUE;
}
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20150325/ca091374/attachment-0001.htm

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

_______________________________________________
Tinyos-help mailing list
Tinyos-help <at> millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

End of Tinyos-help Digest, Vol 143, Issue 10
********************************************

<div>
<div dir="ltr">tossim execution requires actual mote for execution of the program</div>
<div class="gmail_extra">
<br><div class="gmail_quote">On Thu, Mar 26, 2015 at 12:30 AM,  <span dir="ltr">&lt;<a href="mailto:tinyos-help-request <at> millennium.berkeley.edu" target="_blank">tinyos-help-request <at> millennium.berkeley.edu</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">Send Tinyos-help mailing list submissions to<br>
&nbsp; &nbsp; &nbsp; &nbsp; <a href="mailto:tinyos-help <at> millennium.berkeley.edu">tinyos-help <at> millennium.berkeley.edu</a><br><br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
&nbsp; &nbsp; &nbsp; &nbsp; <a href="https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help" target="_blank">https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help</a><br><br>
or, via email, send a message with subject or body 'help' to<br>
&nbsp; &nbsp; &nbsp; &nbsp; <a href="mailto:tinyos-help-request <at> millennium.berkeley.edu">tinyos-help-request <at> millennium.berkeley.edu</a><br><br>
You can reach the person managing the list at<br>
&nbsp; &nbsp; &nbsp; &nbsp; <a href="mailto:tinyos-help-owner <at> millennium.berkeley.edu">tinyos-help-owner <at> millennium.berkeley.edu</a><br><br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Tinyos-help digest..."<br><br><br>
Today's Topics:<br><br>
&nbsp; &nbsp;1. Workaround for Timer bug ( IRIS modules) (Roadstar Runner)<br><br><br>
----------------------------------------------------------------------<br><br>
Message: 1<br>
Date: Wed, 25 Mar 2015 00:46:58 -0400<br>
From: Roadstar Runner &lt;<a href="mailto:redstripeva2 <at> gmail.com">redstripeva2 <at> gmail.com</a>&gt;<br>
Subject: [Tinyos-help] Workaround for Timer bug ( IRIS modules)<br>
To: tinyos forum &lt;<a href="mailto:tinyos-help <at> millennium.berkeley.edu">tinyos-help <at> millennium.berkeley.edu</a>&gt;, Miklos Maroti<br>
&nbsp; &nbsp; &nbsp; &nbsp; &lt;<a href="mailto:mmaroti <at> gmail.com">mmaroti <at> gmail.com</a>&gt;,&nbsp; &nbsp; Janos Sallai &lt;<a href="mailto:sallai <at> isis.vanderbilt.edu">sallai <at> isis.vanderbilt.edu</a>&gt;, Eric<br>
&nbsp; &nbsp; &nbsp; &nbsp; Decker &lt;<a href="mailto:cire831 <at> gmail.com">cire831 <at> gmail.com</a>&gt;<br>
Message-ID:<br>
&nbsp; &nbsp; &nbsp; &nbsp; &lt;<a href="mailto:CAN3Ao%2Bwg18yqiRvfDzaihbx8cO9x77m8CZ%2BEdd5e-4PA388_VA <at> mail.gmail.com">CAN3Ao+wg18yqiRvfDzaihbx8cO9x77m8CZ+Edd5e-4PA388_VA <at> mail.gmail.com</a>&gt;<br>
Content-Type: text/plain; charset="utf-8"<br><br>
I recently cam across a possible bug in the Timer module for the IRIS<br>
motes. I occasionally noticed that the timer would fire very late thus<br>
causing a whole series of cascading failures in my modules.<br><br>
After days of debugging, I traced the problem to the routine setInterrupt()<br>
in the&nbsp; module Atm1281AlarmAsyncP.<br>
If the alarm is armed to fire after 1 TCNT tick, in some situations OCR2A<br>
will be loaded with a value that will essentially be in the "past",&nbsp; thus<br>
requiring TCNT2 to wrap around for the compare to occur (about 255 ms late).<br>
Since TCNT2 is a free running timer, if TCNT2 increments after the current<br>
time is captured by the call to Counter.get(), the *fired *flag will not be<br>
set, even though the alarm has technically expired. After this, under some<br>
circumstances, the compare register can be loaded with a wrong value.<br>
Consider the following situation when setInterrupt() is called<br><br><br>
to = 24<br>
dt = 1<br>
TCNT2 =1<br>
base = 23<br><br>
now if TCNT increments (TCNT2 = 2)&nbsp; after the current&nbsp; time is captured<br>
&nbsp; uint32_t now = call Counter.get();<br><br>
Then the following condition will fail<br>
&nbsp;/* Check if alarm expired */<br>
&nbsp; &nbsp;if ((uint32_t)(now - t0) &gt;= dt)<br>
The following variables will be updated as indicated below, to compute<br>
&nbsp;anew value for OCCR2A<br>
alarm_in = 2<br>
newOcr2A = 1<br><br>
Since newOcr2A&nbsp; &nbsp;=1&nbsp; and TCNT2 =2 , When OCCR2A is loaded, it will delay<br>
the next alarm by 255 ms.<br><br>
As a quick workaround, i added the following code to force the timers to<br>
fire after calling setOcr2A(newOcr2A);<br><br>
//work around<br>
if(newOcr2A &gt;= TCNT)<br>
{<br>
diff =&nbsp; newOcr2A - TCNT&nbsp; &nbsp;;<br>
}<br>
else<br>
{<br>
diff =&nbsp; (0xFF - TCNT) + newOcr2A ;<br>
}<br>
if( diff&nbsp; &nbsp;&gt; MAXT)<br>
{<br>
fired = TRUE;<br>
}<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20150325/ca091374/attachment-0001.htm" target="_blank">https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20150325/ca091374/attachment-0001.htm</a><br><br>
------------------------------<br><br>
_______________________________________________<br>
Tinyos-help mailing list<br><a href="mailto:Tinyos-help <at> millennium.berkeley.edu">Tinyos-help <at> millennium.berkeley.edu</a><br><a href="https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help" target="_blank">https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help</a><br><br>
End of Tinyos-help Digest, Vol 143, Issue 10<br>
********************************************≤br>
</blockquote>
</div>
<br>
</div>
</div>
Roadstar Runner | 25 Mar 05:46 2015
Picon

Workaround for Timer bug ( IRIS modules)

I recently cam across a possible bug in the Timer module for the IRIS motes. I occasionally noticed that the timer would fire very late thus causing a whole series of cascading failures in my modules.

After days of debugging, I traced the problem to the routine setInterrupt() in the  module Atm1281AlarmAsyncP.
If the alarm is armed to fire after 1 TCNT tick, in some situations OCR2A will be loaded with a value that will essentially be in the "past",  thus requiring TCNT2 to wrap around for the compare to occur (about 255 ms late).
Since TCNT2 is a free running timer, if TCNT2 increments after the current time is captured by the call to Counter.get(), the fired flag will not be set, even though the alarm has technically expired. After this, under some circumstances, the compare register can be loaded with a wrong value.
Consider the following situation when setInterrupt() is called


to = 24
dt = 1
TCNT2 =1
base = 23

now if TCNT increments (TCNT2 = 2)  after the current  time is captured
  uint32_t now = call Counter.get();

Then the following condition will fail
 /* Check if alarm expired */
   if ((uint32_t)(now - t0) >= dt)
The following variables will be updated as indicated below, to compute  anew value for OCCR2A
alarm_in = 2
newOcr2A = 1

Since newOcr2A   =1  and TCNT2 =2 , When OCCR2A is loaded, it will delay the next alarm by 255 ms.

As a quick workaround, i added the following code to force the timers to fire after calling setOcr2A(newOcr2A);

//work around 
if(newOcr2A >= TCNT)
{
diff = newOcr2A - TCNT   ;
}
else
{
diff = (0xFF - TCNT) + newOcr2A ;
}
if( diff   > MAXT)
{
fired = TRUE;
}

<div><div dir="ltr">I recently cam across a possible bug in the Timer module for the IRIS motes. I occasionally noticed that the timer would fire very late thus causing a whole series of cascading failures in my modules.<div>
<br><div>After days of debugging, I traced the problem to the routine setInterrupt() in the &nbsp;module&nbsp;Atm1281AlarmAsyncP.</div>
<div>If the alarm is armed to fire after 1 TCNT tick, in some situations&nbsp;OCR2A will be loaded with a value that will essentially be in the "past", &nbsp;thus requiring TCNT2 to wrap around for the compare to occur (about 255 ms late).</div>
<div>Since TCNT2 is a free running timer, if TCNT2 increments after the current time is captured by the call to Counter.get(), the fired flag will not be set, even though the alarm has technically expired. After this, under some circumstances, the compare register can be loaded with a wrong value.</div>
</div>
<div>Consider the following situation when setInterrupt() is called</div>
<div><br></div>
<div><br></div>
<div>to = 24</div>
<div>dt = 1</div>
<div>TCNT2 =1</div>
<div>base = 23</div>
<div><br></div>
<div>now if TCNT increments (TCNT2 = 2) &nbsp;after the current &nbsp;time is captured</div>
<div><div>&nbsp; uint32_t now = call Counter.get();</div></div>
<div><br></div>
<div>Then the following condition will fail</div>
<div>
<div>&nbsp;/* Check if alarm expired */</div>
<div>&nbsp; &nbsp;if ((uint32_t)(now - t0) &gt;= dt)</div>
</div>
<div>The following variables will be updated as indicated below, to compute &nbsp;anew value for OCCR2A</div>
<div>alarm_in = 2<br>
</div>
<div>newOcr2A = 1<br>
</div>
<div><br></div>
<div>Since newOcr2A &nbsp; =1 &nbsp;and TCNT2 =2 , When OCCR2A is loaded, it will delay the next alarm by 255 ms.</div>
<div><br></div>
<div>As a quick workaround, i added the following code to force the timers to fire after calling&nbsp;setOcr2A(newOcr2A);</div>
<div><br></div>
<div>
<div>//work around&nbsp;</div>
<div>
<span class="">		</span>if(newOcr2A &gt;=<span class="">	</span> TCNT)</div>
<div>
<span class="">		</span>{</div>
<div>
<span class="">			</span>diff = <span class="">	</span> newOcr2A - TCNT &nbsp; ;</div>
<div>
<span class="">		</span>}</div>
<div>
<span class="">		</span>else<span class="">	</span>
</div>
<div>
<span class="">		</span>{<span class="">	</span> <span class="">		</span>
</div>
<div>
<span class="">			</span>diff = <span class="">	</span> (0xFF - TCNT) + newOcr2A ;<span class="">	</span>
</div>
<div>
<span class="">		</span>}</div>
<div>
<span class="">		</span>if( diff &nbsp; &gt; MAXT)</div>
<div>
<span class="">		</span>{</div>
<div>
<span class="">			</span>fired = TRUE;</div>
<div>
<span class="">		</span>}</div>
</div>
<div><br></div>
</div></div>
Chahrazed Baghdadli | 23 Mar 08:26 2015
Picon

(no subject)

hi,
i would like to send a packet with 6lowpan !but i used interface AmSend i don't think that it's right ,someone got any help to give me please
<div><div dir="ltr">hi,<br>i would like to send a packet with 6lowpan !but i used interface AmSend i don't think that it's right ,someone got any help to give me please</div></div>
jobishjohn ips | 23 Mar 08:18 2015
Picon

setting the local time of a mote

Hi,

I would like to to set the local time of a mote (telosb) using tinyos 2.1.2.

The interface  "LocalTime" provides a "get" command but not "set"

Is there some other interface through which the local time of a mote can be set to a particular value?.

Thanks in advance for your valuable time.

Regards
Jobish John
Research scholar
Indian Institute of Technology, Bombay


<div><div dir="ltr">
<div>
<div>Hi,<br><br>
</div>I would like to to set the local time of a mote (telosb) using tinyos 2.1.2.<br><br>
</div>
<div>The interface&nbsp; "LocalTime" provides a "get" command but not "set"<br><br>
</div>
<div>Is there some other interface through which the local time of a mote can be set to a particular value?.<br><br>
</div>
<div>Thanks in advance for your valuable time.<br>
</div>
<div>
<br>Regards<br>Jobish John<br>
</div>
<div>Research scholar<br>
</div>
<div>Indian Institute of Technology, Bombay<br>
</div>
<div><br></div>
<br>
</div></div>
Eleonora Borgia | 20 Mar 17:45 2015
Picon

CFP: Special Issue of Elsevier Computer Communications on the Internet of Things: Research challenges and Solutions

=============================================================================

Call for Papers 
Special Issue of Elsevier Computer Communications on the
Internet of Things: Research challenges and Solutions

=============================================================================

Scope 
-----

Internet of Things (IoT) refers to an emerging paradigm that seamlessly
integrates a large number of smart objects with the Internet interlinking the
physical and the cyber worlds and keeping them in a tight and continuous
interaction. The envisioned paradigm will need to address significant
complexity. On the one hand, billions of smart objects will be immersed in the
environment, sensing, interacting, and cooperating with each other to enable
efficient services that will bring tangible benefits to the environment, the
economy and the society as a whole. On the other hand, they will be extremely
diverse and heterogeneous in terms of resource capabilities, lifespan and
communication technologies, further complicating the scenario. As a result, new
problems and challenges arise spanning different areas: architecture,
communication, addressing, discovery, data and network management, power and
energy storage, security and privacy, to cite a few. Classic Internet approaches
are not sufficient to solve these unprecedented issues, and need to be revised
to address the complex requirements imposed by IoT. This paves the way for the
development of intelligent algorithms, novel network paradigms and new services.

The objective of this special issue is to seek high-quality and unpublished
papers that push the research in all the facets of IoT. Contributions may
present and solve open technical problems, integrate novel solutions
efficiently, and focus on the performance evaluation and comparison with
existing standards. Theoretical as well as experimental studies for typical IoT
use cases (e.g., smart city, smart home/building, smart grid, transportation,
eHealth/mHealth) are encouraged. High-quality review and survey papers are
welcomed.

Topics of interest include but are not limited to: 
o  Cyber-physical and other IoT systems architectures 
o  Network architecture and system design in IoT 
o  Addressing and naming in IoT o Programming models for the IoT 
o  IoT and Cloud computing o Integration with existing standards and protocols 
   (e.g., RPL, 6LoWPAN, CoAP, MQTT) 
o  Data management in IoT o Machine-to-machine (M2M) communications in IoT 
o  Energy efficient management and sustainable operation of IoT/M2M objects 
o  Information centric network for IoT o Social networks for IoT
o  Context-awareness for IoT o IoT traffic characterization 
o  Privacy, Security and Trust for IoT 
o  Modeling and simulation of large-scale IoT scenarios 
o  Testbed, prototype, and practical systems for IoT use cases

Schedule
--------

o  Title and abstract due date (by email to comcomsi_iot at iit.cnr.it):
   June 1, 2015 
o  Full paper submission deadline: June 15, 2015 
o  First author notification: October 15, 2015
o  Revised paper due: December 15, 2015
o  Final author notification: January 31, 2016 
o  Expected publication: Summer 2016

Guest Editors
------------- 

Eleonora Borgia, IIT-CNR, Italy 
Danielo G. Gomes, Universidade Federal do Ceara', Brazil 
Brent Lagesse, University of Washington, USA 
Rodger Lea, University of British Columbia, Canada 
Daniele Puccinelli, SUPSI, Switzerland

Instructions for submission 
---------------------------

Manuscripts must not have been previously published nor currently under review 
by other journals or conferences. If the paper was published in a conference, 
the submitted manuscript should be a substantial extension of the conference paper, 
with at least 30% of novel contributions.
Authors are also required to submit their published conference articles and a
summary document explaining the enhancements made in the journal version.

Papers must be submitted through the Computer Communications website at
http://ees.elsevier.com/comcom, where guidelines for the manuscript preparation
can also be found (see
http://www.elsevier.com/journals/computer-communications/0140-3664/guide-for-authors).
To ensure that all manuscripts are correctly identified for consideration by the
Special Issue, the authors should select "Special Issue: IoT Challenges" when
they reach the "Article Type" step in the submission process.

For further information, please contact the guest editors at comcomsi_iot at
iit.cnr.it
Dileepkumar Atche | 18 Mar 16:55 2015
Picon

DIFFERENCE BETWEEN RF230MESSAGEC AND IEEE154MESSAGEC


Dear all,


Please tell me difference between RF230MESSAGEC AND IEEE154MESSAGEC components present in tinyos.
--
Regards,
Dileepkumar Atche
M.Tech,
Communication and Signal processing,
Indian Institute of Technology Hyderabad.
<div><div dir="ltr">
<div>
<div><br clear="all"></div>Dear all,<br><br><br>
</div>Please tell me difference between RF230MESSAGEC AND IEEE154MESSAGEC components present in tinyos.<br><div><div><div>-- <br><div class="gmail_signature"><div dir="ltr">
<div>Regards,</div>
<div>Dileepkumar Atche<br>
</div>
<div>M.Tech,<br>
</div>
<div>Communication and Signal processing,<br>
</div>
<div>Indian Institute of Technology Hyderabad.<br>
</div>
</div></div>
</div></div></div>
</div></div>
Chahrazed Baghdadli | 18 Mar 10:25 2015
Picon

(no subject)

I want to use printf in Ppprouter wich works with blip ,but i can't do it !!!please help
<div><div dir="ltr">I want to use printf in Ppprouter wich works with blip ,but i can't do it !!!please help</div></div>
amina khatun | 18 Mar 08:52 2015
Picon

ctp protocol implementation

sir, plz help me how to implement CTP(Collection Tree Protocol ) in tinyos on Tossim. and how to calculate the ETX value.
<div><div dir="ltr">sir, plz help me how to implement CTP(Collection Tree Protocol ) in tinyos on Tossim. and how to calculate the ETX value.<br>
</div></div>
Elisabetta Biondi | 17 Mar 17:34 2015
Picon

IEEE WoWMoM 2015 Workshop on Autonomic and Opportunistic Communications (AOC) - DEADLINE EXTENDED

--------------------------------------------------------------------
Our apologies if you receive multiple copies of this CFP

Full manuscript due:            March 20, 2015 (EXTENDED)
Acceptance notification:        April 20, 2015
---------------------------------------------------------------------

                          CALL FOR PAPERS

               The Ninth IEEE International Workshop on
              Autonomic and Opportunistic Communications
                             (AOC 2015)

                   http://cnd.iit.cnr.it/aoc2015

                           sponsored by
                       IEEE Computer Society,
                        EU FP7 MOTO Project                           

                  June 14-17 2015, Boston, MA, USA

The diffusion of lightweight, powerful portable devices, also enriched with a
variety of sensing capabilities, is enabling new ways for users' communication,
and laying the foundation for realizing the ubiquitous networking idea. Acting
either as the main communication mode or as complement to existing mobile
network infrastructures, opportunistic networking can leverage the mobility of
end users and enhance their communication capabilities. The opportunistic
exploitation of extemporary contacts among the users of the network paves the
way to a number of applications but also poses new and challenging problems to
the networking research community. The AOC 2015 workshop aims at serving as a
meeting point for people working in the area and a forum for exchanging ideas,
discussing solutions, and sharing experiences among researchers, professionals,
and application developers, both from industry and academia.  As with the
previous eight editions of the AOC workshop series, the scope of this year's
workshop will remain on general issues related to opportunistic networking and
computing. Yet, AOC 2015 will have a primary interest in new directions of
opportunistic communications, such as mobile social networking, autonomous
solutions for smart cities, big data for autonomic and opportunistic systems
service composition techniques, scenarios of co-existence with infrastructure
networks, and insights to their operation coming from other disciplines such as
game theory and cognitive psychology. The workshop will solicit original papers
addressing theoretical and practical aspects of autonomic and opportunistic
communications but also papers describing prototype implementations and
deployments.

Topics of interest for AOC 2015 include, but are not limited to: 

- Techniques for data dissemination and replication
- Context and social awareness mechanisms and algorithms
- Autonomous and self-adaptive systems for smart cities
- Autonomous solutions for IoT and cyber-physical systems
- Big data for autonomic and opportunistic systems
- Mobile social networking algorithms and applications
- Co-existence of opportunistic networks with infrastructure mobile wireless
  networks
- Mobility models and statistical analysis of mobility traces
- Service composition in autonomic and opportunistic networks
- Cognition-driven information processing and decision making
- Performance modelling, scaling laws, and fundamental limits for autonomic and
  opportunistic communications
- Participatory and urban sensing in autonomic and opportunistic networks
- Game-theoretic insights to the operation of autonomic and opportunistic
  networks
- Trust, security, and reputation
- Autonomic and opportunistic communication testbeds and prototypes, measurement
  data from real experiments
- Socio-economic models for autonomic and opportunistic communications
- Autonomic and opportunistic solutions for mobile cloud applications
- Applications and middleware support
- Routing, transport, and reliability issues

PAPER SUBMISSION AND PUBLICATION
------------------------------------------------------------------------
All submissions must describe original research, not published or
currently under review for another workshop, conference, or journal.
Papers must be submitted electronically through EDAS. You can find
detailed submission instructions at:
http://cnd.iit.cnr.it/aoc2015/submission.html

IEEE AOC 2015 is using the EDAS Conference Management Software. 
Paper submission is possible via this link:
http://edas.info/N19275

Manuscripts are limited to 6 pages, single spacing, double column, and must strictly adhere to the IEEE
conference template format. Guidelines on paper submission and formatting are available at http://cnd.iit.cnr.it/aoc2015/submission.html

********************************************************************************
Submission implies the willingness of at least one author to attend the workshop 
and present the paper. Accepted papers will be included in the proceedings of 
IEEE WoWMoM 2015 and published in the IEEE Digital Library. Workshop organizers 
reserve the right to exclude a paper from distribution after the workshop 
(e.g., removal from IEEE Xplore) if the paper is not presented at the conference.

There will be no separate registration for workshop, but one single registration 
will cover both conference and workshops participation. At least one author of 
each accepted paper is required and present his/her work at the workshop.
********************************************************************************

EDITORIAL FOLLOW-UP
------------------------------------------------------------------------
Extended versions of workshop selected papers will be considered for possible
fast track publication on the Computer Communications Journal (Elsevier). 

IMPORTANT DATES (EXTENDED DEADLINES)
------------------------------------------------------------------------
- Full manuscript due:                  March 20, 2015 (EXTENDED)
- Acceptance notification:              April 20, 2015
- Camera Ready:                         May 7,    2015

CONTACTS
------------------------------------------------------------------------
For further information, please visit the conference website at 
http://cnd.iit.cnr.it/aoc2015, or contact the PC Chairs:
aoc2015 <at> iit.cnr.it

ORGANIZING COMMITTEE
------------------------------------------------------------------------
WORKSHOP Co-Chairs
Lorenzo Valerio, IIT-CNR, Italy 
Matteo Mordacchini, IIT-CNR, Italy

STEERING Committee
Marco Conti, IIT-CNR, Italy 
Silvia Giordano, SUPSI, Switzerland 
Ioannis Stavrakakis, University of Athens, Greece

PUBLICITY Chair
Elisabetta Biondi, IIT-CNR, Italy

PROGRAM Committee
Andreea Picu, ETH Zurich, Switzerland
Anna Forster, SUPSI, Switzerland
Chiara Boldrini, IIT-CNR, Italy
Christian Rohner, Uppsala University, Sweden
Daniele Miorandi, Create-net, Italy
Daniele Puccinelli, SUPSI, Switzerland
Eiko Yoneki, University of Cambridge, UK
Elena Pagani, University of Milano, Italy
Eleonora Borgia, IIT-CNR, Italy
Franck Legendre, ETH Zurich, Switzerland
Franco Zambonelli, University of Modena and Reggio Emilia, Italy
Gunnar Karlsson, KTH, Sweden
Hongyi Wu, University of Louisiana at Lafayette, USA
Jian-Nong Cao, Hong Kong Polytechnic University, HK
Jorg Ott, Aalto University, Finland
Katia Obraczka, University of California Santa Cruz, USA 
Konstantinos Oikonomou, Ionian University, Greece
Kyunghan Lee, North Carolina State University, USA
Michela Papandrea, SUSPSI, Switzerland
Melek Onen, EURECOM, France
Nils Aschenbruck, University of Osnabruck, Germany
Roger Whitaker, Cardiff University, UK
Sebastian Zander, Swinbourne University of Technology, Australia
Serge Fdida, UPMC Sorbonne Universites, France
Thrasyvoulos Spyropoulos, EURECOM, France
Tristan Henderson, University of St Andrews, United Kingdom
Valerio Arnaboldi, IIT-CNR, Italy
Valtteri Niemi, University of Turku, Finland
Vania Conan, Thales Communication and Security, France
Valerio Arnaboldi | 17 Mar 15:03 2015
Picon

CFP: (EXTENDED DEADLINE) IEEE SmartVehicles 2015 - new submission deadline is 22 March 2015!

Please accept our apologies if you receive multiple copies of this CFP.

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

Paper Registration Deadline:    March 22, 2015 (EXTENDED) 
Full manuscript due:            March 22, 2015 (EXTENDED)
Acceptance notification:        April 20, 2015

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

                                 CALL FOR PAPERS

                         The Second IEEE WoWMoM Workshop on 
         Smart Vehicles: Connectivity Technologies and ITS Applications 
                               (SmartVehicles 2015)
                        June 14-17, 2015, Boston, MA, USA
                        http://cnd.iit.cnr.it/smartvehicles2015

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

SCOPE AND OVERVIEW
--------------------------------
The development of smart vehicles and more sustainable transportation systems has emerged as one of the
most fundamental societal challenges of the next decade. At the same time, automotive manufacturers are
striving to make vehicles safer and more environmentally friendly to fulfil consumers' expectations
and new regulations. To revolutionise our mobile lifestyle towards a more sustainable and connected
future it is of paramount importance to develop innovative cooperative systems enabling road users and
other actors to exchange information in real time and in an autonomous manner, pervasive sensing to
monitor the status of vehicles and the surroundings, big data analytics for the processing of sheer
amount of data coming from the transportation infrastructure, middleware platforms for in
 formation management and sharing, and appropriate interaction interfaces between drivers and
vehicles. Clearly, the seamless integration between mobile devices, vehicular communication netw!
 orks, and information and transportation systems will face a number of technical, economical and
regulatory challenges.

Authors are encouraged to submit full papers presenting recent developments, current research
challenges and future directions in the use of networking, communications, data management, and
applications to realise vehicular mobility systems that are more connected, sustainable and safe.

Topics of interest for SmartVehicles 2015 include, but are not limited to:

+ Vehicular Network as a Sensor Network;
+ V2V, V2I and V2X communications
+ Vehicular mobility support in next-generation wireless technologies
+ Communications protocol design (MAC, routing, data dissemination)
+ Data storage, management, and retrieval in vehicular networks
+ Solutions to connect vehicles with the Internet
+ Big data analytics for ITS applications
+ Security and privacy in ITS applications
+ Multimedia applications, infotainment
+ Cooperative driving, autonomous and smart vehicles
+ Traffic management and efficiency applications
+ Electrification of transportation systems
+ Simulation environments, experimental testbeds, field operational tests
+ Mobile (smart) device integration in vehicles and transport systems
+ Integration of cloud technologies in ITS applications 

PAPER SUBMISSION AND PUBLICATION
--------------------------------
Submission will be managed electronically through EDAS (http://edas.info/N19487). 

Papers should neither have been published elsewhere nor being currently under review by another
conference or journal. Manuscripts are limited to 6 pages, single spacing, double column, and must
strictly adhere to the template format. Guidelines on paper submission and formatting are available at: http://cnd.iit.cnr.it/smartvehicles2015

Accepted papers will appear in the symposium proceedings published by IEEE. Workshop papers will be
included and indexed in the IEEE Digital Library (IEEEXplore), showing their affiliation with IEEE
WoWMoM. At least one author of each accepted paper is required to register and present his/her work at the
workshop in order for that paper to appear in the proceedings.

IMPORTANT DATES
---------------
Paper Registration Deadline:          March 22, 2015 (EXTENDED)
Paper Submission Deadline:            March 22, 2015 (EXTENDED)
Notification Deadline:                April 20, 2015
Workshop Date:                        June 14-17, 2015

ORGANISING COMMITTEE
--------------------

Workshop Co-Chairs 
    Raffaele Bruno, IIT, CNR, Italy
    Salil Kanhere, UNSW, Australia
    John B. Kenney, Toyota InfoTechnology Center, USA

Publicity Chair 
    Valerio Arnaboldi, IIT, CNR, Italy

Program Committee 
    Jose M. Barcelo-Ordinas, Universitat Politecnica de Catalunya, Spain 
    Gaurav Bansal, Toyota InfoTechnology Center, USA 
    Azzedine Boukerche, University of Ottawa, Canada 
    Maria Calderon, Universidad Carlos III de Madrid, Spain 
    David Eckhoff, University of Erlangen, Germany	
    Marco Di Felice, University of Bologna, Italy 
    Marco Fiore, IEIIT-CNR, Italy 
    Emma Fitzgerald, Lund University, Sweden 
    Raphael Frank, University of Luxembourg, Luxembourg 
    Javier Gozalvez, University Miguel Hernandez, Spain 
    Jerome Harri, EURECOM, France 
    Hannes Hartenstein, Karlsruhe Institute of Technology, Germany 
    Geert Heijenk, University of Twente, Netherlands 
    Daniel Jiang, Mercedes-Benz R&D North America, USA 
    Frank Kargl, Ulm University, Germany 
    Kun-chan Lan, National Cheng Kung University, Taiwan 
    Evangelos Mitsakis, Centre for Research and Technology Hellas, Greece 
    Radovan Miucic, Honda R&D, USA 
    Panagiotis Papadimitratos, KTH, Sweden 
    Yves Roudier, EURECOM, France 
    Robert Schmidt, Denso Automotive Dtld. GmbH, Germany 
    Katrin Sjoberg, Volvo, Sweden 
    Erik Strom, Chalmers University of Technology, Sweden 
    Alexey Vinel, Halmstad University, Sweden 
    Alberto Zanella, IEIIT-CNR, Italy


Gmane