Elisabetta Biondi | 25 Feb 11:34 2015
Picon

IEEE WoWMoM 2015 Workshop on Autonomic and Opportunistic Communications (AOC) - Abstract Registration Deadline 7th March 2015

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

Abstract submission deadline:   March 7,  2015 
Full manuscript due:            March 14, 2015
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
(Continue reading)

Alexander | 22 Feb 07:55 2015
Picon

error 53 on writing to telosb

Hello All,

I’ve got a problem. I installed cygwin and tinyos according to manual - http://tinyos.stanford.edu/tinyos-wiki/index.php/Installing_TinyOS_2.1
I can compile apps but when I try to write to TmoteSky I am getting error
$ make telosb reinstall bsl,3 cp build/telosb/main.ihex build/telosb/main.ihex.out installing telosb binary using bsl tos-bsl --telosb -c 3 -r -e -I -p build/telosb/main.ihex.out make: *** [program] Error 53
I tried on different systems (WinXP, WinXP on Macbook via VirtualBox, Win7) and different laptops but everywhere I am getting the same error.

Please help me to find out what is the problem.

Thank you.

Alex.
<div>Hello All,<div><br></div>
<div>I&rsquo;ve got a problem. I installed cygwin and tinyos according to manual -&nbsp;<a href="http://tinyos.stanford.edu/tinyos-wiki/index.php/Installing_TinyOS_2.1">http://tinyos.stanford.edu/tinyos-wiki/index.php/Installing_TinyOS_2.1</a>
</div>
<div>I can compile apps but when I try to write to TmoteSky I am getting error</div>
<div>$ make telosb reinstall bsl,3
cp build/telosb/main.ihex build/telosb/main.ihex.out
    installing telosb binary using bsl
tos-bsl --telosb -c 3 -r -e -I -p build/telosb/main.ihex.out
make: *** [program] Error 53<div>I tried on different systems (WinXP, WinXP on Macbook via VirtualBox, Win7) and different laptops but everywhere I am getting the same error.</div>
</div>
<div><br></div>
<div>Please help me to find out what is the problem.</div>
<div><br></div>
<div>Thank you.</div>
<div><br></div>
<div>Alex.</div>
</div>
Manvinderjeet Kaur | 18 Feb 23:24 2015
Picon

Tiny Os Radio and Serial Communication

Hi all,

My name is Manvinder Jeet Kaur, i am doing my project using TinyOS and I'm trying to make a communication between one mote to basestation using MicaZ. The Scenario is that one mote will receive the information from the sensor on to UART port and will send that information wirelessely to base station that is connected to the computer using USB cable. Then the message will be displayed onto the computer. 

It will be really appreciated if someone can guide me what are the interface and components that will be used and if someone have source code about using UART port.

Thank you so much for help in advance. 

Manvinder jeet Kaur 

<div><div>
<div dir="ltr" class="">Hi all,</div>
<div dir="ltr" class=""><br class=""></div>
<div dir="ltr" class="">My name is Manvinder Jeet Kaur, i am doing my project using TinyOS and I'm trying to make a communication between one mote to basestation using MicaZ. The Scenario is that one mote will receive the information from the sensor on to UART port and will send that information wirelessely to base station that is connected to the computer using USB cable. Then the message will be displayed onto the computer.&nbsp;</div>
<div dir="ltr" class=""><br></div>
<div dir="ltr" class="">It will be really appreciated if someone can guide me what are the interface and components that will be used and if someone have source code about using UART port.</div>
<div dir="ltr" class=""><br></div>
<div dir="ltr" class="">Thank you so much for help in advance.&nbsp;</div>
<div dir="ltr" class=""><br></div>
<div dir="ltr" class="">Manvinder jeet Kaur&nbsp;</div>
<div dir="ltr" class=""><br class=""></div>
</div></div>
laptopcss | 17 Feb 14:40 2015
Picon
Picon

TinyOS 2.1.1 - IP-tunnel shuts down unexpectedly

Hallo together,
 
I currently run TinyOS 2.1.1 in Ubuntu 10.4 in Virtual Box.
After upgrading virtualbox to 4.3.22 I have trouble with TinyOS.
 
My code runs blip and uses the common IP-Tunnel.
The IP-tunnel now aborts latest every 5 minutes without any error messages.
 
Does anyone have the same problem or have ideas how to solve it?
 
Regards,
Conny
<div><div>
<div>Hallo together,</div>

<div>&nbsp;</div>

<div>I currently run TinyOS 2.1.1 in Ubuntu 10.4 in Virtual Box.</div>

<div>After upgrading virtualbox to 4.3.22 I have trouble with TinyOS.</div>

<div>&nbsp;</div>

<div>My code runs blip and uses the common IP-Tunnel.</div>

<div>The IP-tunnel now aborts latest every 5 minutes without any error messages.</div>

<div>&nbsp;</div>

<div>Does anyone have the same problem or have ideas how to solve it?</div>

<div>&nbsp;</div>

<div>Regards,</div>

<div>Conny</div>
</div></div>
Valerio Arnaboldi | 14 Feb 16:34 2015
Picon

CFP: IEEE WoWMoM 2015 workshop on Smart Vehicles: Connectivity Technologies and ITS Applications -- Paper Registration Deadline: 7 March, 2015

Please accept our apologies if you receive multiple copies of this CFP.
----------------------------------------------------------------------
                                 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

          **** Paper Registration Deadline --- March 7, 2015 ****
          **** Paper Submission Deadline   --- March 14, 2015 ****

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

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 7, 2015 (recommended)
Paper Submission Deadline:            March 14, 2015
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 
    Gaurav Bansal, Toyota InfoTechnology Center, USA
    Azzedine Boukerche, University of Ottawa, Canada
    Marco Di Felice, University of Bologna, Italy
    Marco Fiore, IEIIT-CNR, Italy
    Emma Fitzgerald, Lund University, Sweden
    Javier Gozalvez, University Miguel Hernandez, Spain
    Jerome Harri, EURECOM, France
    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
    Katrin Sjoberg, Volvo, Sweden
    Erik Strom, Chalmers University of Technology, Sweden
    Alexey Vinel, Halmstad University, Sweden
    Alberto Zanella, IEIIT-CNR, Italy 

jobishjohn ips | 14 Feb 09:12 2015
Picon

ADC input pin drawing high current

Hi all,

Please consider me as a beginner and request you kindly help me.

When I am sampling the external pin, ADC0 of a telosb mote, if no other analog pins are connected (other analog pins in the 10-pin expansion connector are kept open), I am able to sample ADC0 correctly and the current drawn from ADC0 source is less than 1mA. The interface and the corresponding wiring is given below.

interface Read<uint16_t> as voltageread;   


const msp430adc12_channel_config_t config = {
                                                    inch: INPUT_CHANNEL_A0,
                                                    sref: REFERENCE_VREFplus_AVss,
                                                    ref2_5v: REFVOLT_LEVEL_2_5,
                                                    adc12ssel: SHT_SOURCE_ACLK,
                                                    adc12div: SHT_CLOCK_DIV_1,
                                                    sht: SAMPLE_HOLD_4_CYCLES,
                                                    sampcon_ssel: SAMPCON_SOURCE_SMCLK,
                                                    sampcon_id: SAMPCON_CLOCK_DIV_1
                                                };

 async command const msp430adc12_channel_config_t * VoltageConfigure.getConfiguration()
 {
        return &config;
 }

and

components new AdcReadClientC()
App.voltageread -> AdcReadClientC;
AdcReadClientC.AdcConfigure -> App.VoltageConfigure;

The ADC0 is sampled whenever a periodic timer of 1 second fires. This works perfectly fine.The same case holds true for ADC1 or ADC2(only one ADC pin is connected and sampled).

Assume that we are sampling ADC0. Now if I am connecting another analog voltage to any other analog pins ( eg: ADC1 or ADC2 or ADC3 of 10 pin expansion connector of telosb), a high current ( >25mA) is drawn from that voltage source which is connected to ADC1 or ADC2 or ADC3.

Please note that my nesc module and configuration file is the same as previous one.(Does not contain any cofiguration/reading other than ADC0)

Please help me to find out the reason behind this.

Thanks
Jobish John



<div><div dir="ltr">
<div>Hi all,<br><br>Please consider me as a beginner and request you kindly help me.<br><br>
</div>
<div>When I am sampling the external pin, ADC0 of a telosb mote, if no other analog pins are connected (other analog pins in the 10-pin expansion connector are kept open), I am able to sample ADC0 correctly and the current drawn from ADC0 source is less than 1mA. The interface and the corresponding wiring is given below.<br><br>interface Read&lt;uint16_t&gt; as voltageread;&nbsp;&nbsp;&nbsp; <br><br><br>const msp430adc12_channel_config_t config = {<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; inch: INPUT_CHANNEL_A0,<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; sref: REFERENCE_VREFplus_AVss,<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; ref2_5v: REFVOLT_LEVEL_2_5,<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; adc12ssel: SHT_SOURCE_ACLK,<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; adc12div: SHT_CLOCK_DIV_1,<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; sht: SAMPLE_HOLD_4_CYCLES,<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; sampcon_ssel: SAMPCON_SOURCE_SMCLK,<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; sampcon_id: SAMPCON_CLOCK_DIV_1<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; };<br><br>&nbsp;async command const msp430adc12_channel_config_t * VoltageConfigure.getConfiguration()<br>&nbsp;{<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; return &amp;config;<br>&nbsp;}<br><br>
</div>
<div>and <br>
</div>
<div>
<br>components new AdcReadClientC()<br>App.voltageread -&gt; AdcReadClientC;<br>AdcReadClientC.AdcConfigure -&gt; App.VoltageConfigure;<br><br>
</div>
<div>The ADC0 is sampled whenever a periodic timer of 1 second fires. This works perfectly fine.The same case holds true for ADC1 or ADC2(only one ADC pin is connected and sampled).<br>
</div>
<div>
<br> Assume that we are sampling ADC0. Now if I am connecting another analog voltage to any other analog pins ( eg: ADC1 or ADC2 or ADC3 of 10 pin expansion connector of telosb), a high current ( &gt;25mA) is drawn from that voltage source which is connected to ADC1 or ADC2 or ADC3. <br><br>
</div>
<div>Please note that my nesc module and configuration file is the same as previous one.(Does not contain any cofiguration/reading other than ADC0)<br><br>
</div>
<div>Please help me to find out the reason behind this.<br><br>
</div>
<div>Thanks<br>
</div>
<div>Jobish John<br>
</div>
<div><br></div>
<br><div><br></div>
</div></div>
Amanda Hendrick | 14 Feb 09:00 2015
Picon

My email id

hendrickamanda.90 <at> gmail.com

<div><p dir="ltr"><a href="mailto:hendrickamanda.90 <at> gmail.com">hendrickamanda.90 <at> gmail.com</a></p></div>
Kiing Ing Wong | 13 Feb 11:10 2015
Picon

reading adxl345 accelerometer through SPI with Tinynode

Hello everyone,

 

I am intended to read acceleration signals from adxl345 through SPI. I am using Tinynode platform (which does not have any I2C output port). Therefore I have to use SPI.

 

When I read the DevID of the adxl345, I get  0xF2 instead of 0xE5. So what I get is 11110010 and what I expect is 11100101 .

 

When I google, I find people (who are not using TinyOS) also have similar problem that can be see here: http://e2e.ti.com/support/microcontrollers/msp430/f/166/t/52871. I must admit I can not understand the code there.

 

My question number ONE is how to fix the problem above.

 

I am calling the SPI using SpiPacket.send() function. I am referring and modifying the code of ADE7753 chip for my application. I have another question on the code below (which belongs to ADE7753P):

async event void SpiPacket.sendDone(uint8_t* txBuf, uint8_t* rxBuf, uint16_t len, error_t spi_error ) {

 

    uint32_t val;

    error_t error = spi_error;

 

    call SPIFRM.set(); // CS HIGH

 

    atomic {

      switch (mState) {

        case STATE_GETREG:

          mState = STATE_IDLE;

          // repack

          switch (len) {

            case 2:

              val = rxBuf[1];

              break;

            case 3:

              val = ((uint32_t)rxBuf[1])<<8 | rxBuf[2];

              break;

            case 4:

              val = ((uint32_t)rxBuf[1])<<16 | ((uint32_t)rxBuf[2])<<8 | rxBuf[3];

              break;

            default:

              val = 0xF0F0F0F0;

              break;

          }

          signal ADE7753.getRegDone(error, (txBuf[0] & 0x7F), val, len);

          break;

 

The question number TWO is why rxB[0] is not read? I test the code above I found out that I need to read rxBuf[0] as the lower byte of the X-axis data.

 

My third question is how to cover 2s complement to uint16_t data, so that I can send through wireless and display on PC screen using Oscilloscope app .

 

My best attempt is as shown below:

async event void SpiPacket.sendDone(uint8_t* txBuf, uint8_t* rxBuf, uint16_t len, error_t spi_error ) {

   int16_t sigval; //sign value

    uint16_t val; //unsign value

 

    error_t error = spi_error;

 

    call SPIFRM.set(); // CS HIGH

 

    atomic {

      switch (mState) {

        case STATE_GETREG:

          mState = STATE_IDLE;

          // repack

          switch (len) {

            case 2:

              val = rxBuf[0];

              break;

            case 3:

             sigval = ((uint16_t)rxBuf[1])<<8 | rxBuf[0];

              //  val = ((uint16_t)rxBuf[2])<<8 | rxBuf[1];// I m not sure if I should use this

            Val=(uint16_t)(sigval+32768); //level shift the sig value.

              break;

            default:

              val = 0xF0F0F0F0;

              break;

          }

          signal ADE7753.getRegDone(error, (txBuf[0] & 0x7F), val, len);

          break;

 

But, when I rotates the accel, the upper half the sin wave is at the bottom of the graph and the lower half sine wave is at the top of the graph. Please help.

 

Regards, Wong Kiing Ing

 

 

 

 

 

 

 

 

 

DISCLAIMER: The information contained in this e-mail and any attachments is confidential and may be legally privileged. If the recipient of this message is not the intended addressee, be advised that you have received this message in error and that legal professional privilege is not waived and you are requested to re-send to the sender and promptly delete this e-mail and any attachments. If you are not the intended addressee, you are strictly prohibited from using, reproducing, disclosing or distributing the information contained in this e-mail and any attached files. Curtin University, Sarawak Malaysia ("Curtin Sarawak") advises that this e-mail and any attached files should be scanned to detect viruses. Curtin Sarawak does not represent or warrant that this e-mail including any attachments is free from computer viruses or defects. Curtin Sarawak shall not be responsible for any loss or damage incurred in their use.
<div>
<div class="WordSection1">
<p class="MsoNormal">Hello everyone,<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">I am intended to read acceleration signals from adxl345 through SPI. I am using Tinynode platform (which does not have any I2C output port). Therefore I have to use SPI.<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">When I read the DevID of the adxl345, I get &nbsp;0xF2 instead of 0xE5. So what I get is 11110010 and what I expect is 11100101 .
<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">When I google, I find people (who are not using TinyOS) also have similar problem that can be see here:
<a href="http://e2e.ti.com/support/microcontrollers/msp430/f/166/t/52871">http://e2e.ti.com/support/microcontrollers/msp430/f/166/t/52871</a>. I must admit I can not understand the code there.<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">My question number ONE is how to fix the problem above.<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">I am calling the SPI using SpiPacket.send() function. I am referring and modifying the code of ADE7753 chip for my application. I have another question on the code below (which belongs to ADE7753P):<p></p></p>
<p class="MsoNormal"><span>async event void SpiPacket.sendDone(uint8_t* txBuf, uint8_t* rxBuf, uint16_t len, error_t spi_error ) {<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; uint32_t val;<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; error_t error = spi_error;<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; call SPIFRM.set(); // CS HIGH<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; atomic {<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; switch (mState) {<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; case STATE_GETREG:<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mState = STATE_IDLE;<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // repack<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; switch (len) {<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; case 2:<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;val = rxBuf[1];<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; break;<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; case 3:<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; val = ((uint32_t)rxBuf[1])&lt;&lt;8 | rxBuf[2];<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; break;<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; case 4:<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; val = ((uint32_t)rxBuf[1])&lt;&lt;16 | ((uint32_t)rxBuf[2])&lt;&lt;8 | rxBuf[3];<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; break;<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; default:<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; val = 0xF0F0F0F0;<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; break;<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; signal ADE7753.getRegDone(error, (txBuf[0] &amp; 0x7F), val, len);<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; break;
<p></p></span></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">The question number TWO is why rxB[0] is not read? I test the code above I found out that I need to read rxBuf[0] as the lower byte of the X-axis data.<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">My third question is how to cover 2s complement to uint16_t data, so that I can send through wireless and display on PC screen using Oscilloscope app .
<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">My best attempt is as shown below:<p></p></p>
<p class="MsoNormal"><span>async event void SpiPacket.sendDone(uint8_t* txBuf, uint8_t* rxBuf, uint16_t len, error_t spi_error ) {<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;int16_t sigval; //sign value<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; uint16_t val; //unsign value<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; error_t error = spi_error;<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; call SPIFRM.set(); // CS HIGH<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; atomic {<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; switch (mState) {<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; case STATE_GETREG:<p></p></span></p>
<p class="MsoNormal"><span>&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;mState = STATE_IDLE;<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // repack<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; switch (len) {<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; case 2:<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; val = rxBuf[0];<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; break;<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; case 3:<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sigval = ((uint16_t)rxBuf[1])&lt;&lt;8 | rxBuf[0];<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;//&nbsp; val = ((uint16_t)rxBuf[2])&lt;&lt;8 | rxBuf[1];// I m not sure if I should use this<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Val=(uint16_t)(sigval+32768); //level shift the sig value.<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; break;<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; default:<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; val = 0xF0F0F0F0;<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; break;<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; signal ADE7753.getRegDone(error, (txBuf[0] &amp; 0x7F), val, len);<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; break;<p></p></span></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">But, when I rotates the accel, the upper half the sin wave is at the bottom of the graph and the lower half sine wave is at the top of the graph. Please help.<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Regards, Wong Kiing Ing<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
DISCLAIMER: The information contained in this e-mail and any attachments is confidential and may be legally privileged. If the recipient of this message is not the intended addressee, be advised that you have received this message in error and that legal professional
 privilege is not waived and you are requested to re-send to the sender and promptly delete this e-mail and any attachments. If you are not the intended addressee, you are strictly prohibited from using, reproducing, disclosing or distributing the information
 contained in this e-mail and any attached files. Curtin University, Sarawak Malaysia ("Curtin Sarawak") advises that this e-mail and any attached files should be scanned to detect viruses. Curtin Sarawak does not represent or warrant that this e-mail including
 any attachments is free from computer viruses or defects. Curtin Sarawak shall not be responsible for any loss or damage incurred in their use.
</div>
Xiaoyang Zhong | 11 Feb 22:49 2015
Picon

How to use MPS-2 water potential sensor

Hi all,

We have been using Decagon's water potential sensor MPS-1 for years to record the water potential of the soil. However, the MPS-1 is no longer available.

Decagon has replaced their MPS-1 water potential sensor with MPS-2. We are very confused about how to power the MPS-2 sensor.

We are using TelosB motes since the MPS-2 senor's output needs to be read through the UART port. We also used a 5V booster converter so that the excitation voltage can meet the sensors requirements (between 3.6 ~ 12 V).

However, as we found, the MPS-2 sensor must be powered twice to output a reading. For example, if we only power it for 200 ms, we get no reading; but if we power it for 50 ms, then remove the power, then power it again for 150 ms, we can sometimes get readings. This is very strange, and we don't know whether this power method is correct. 

When we get readings, the values (<-2000 kPa) are very different from what we get from the MPS-1 sensor (-150 ~ 0 kPa). 

Does anyone has anything experience on the MPS-2 sensor? We really need some help.

Thank you very much.


Best,
Xiaoyang Zhong
<div><div dir="ltr">Hi all,<div><br></div>
<div>We have been using Decagon's water potential sensor MPS-1 for years to record the water potential of the soil. However, the MPS-1 is no longer available.</div>
<div><br></div>
<div>Decagon has replaced their MPS-1 water potential sensor with MPS-2. We are very confused about how to power the MPS-2 sensor.</div>
<div><br></div>
<div>We are using TelosB motes since the MPS-2 senor's output needs to be read through the UART port. We also used a 5V booster converter so that the excitation voltage can meet the sensors requirements (between 3.6 ~ 12 V).</div>
<div><br></div>
<div>However, as we found, the MPS-2 sensor must be powered twice to output a reading. For example, if we only power it for 200 ms, we get no reading; but if we power it for 50 ms, then remove the power, then power it again for 150 ms, we can sometimes get readings. This is very strange, and we don't know whether this power method is correct.&nbsp;</div>
<div><br></div>
<div>When we get readings, the values (&lt;-2000 kPa) are very different from what we get from the MPS-1 sensor (-150 ~ 0 kPa).&nbsp;</div>
<div><br></div>
<div>Does anyone has anything experience on the MPS-2 sensor? We really need some help.</div>
<div><br></div>
<div>Thank you very much.</div>
<div><br></div>
<div><br></div>
<div>Best,</div>
<div>Xiaoyang Zhong</div>
</div></div>
Picon

CFP: The Seventh International Symposium on Applications of Ad hoc and Sensor Networks (AASNET'15)

The Seventh International Symposium on  Applications of Ad hoc and Sensor Networks (AASNET'15) will be held in conjunction with the 6th International Conference on Emerging Ubiquitous Systems and Pervasive Networks (EUSPN-2015) in Berlin, Germany on September 27-30, 2015.

Wireless mobile ad hoc and sensor network nodes have limited battery capacity. Hence, they tend to be energy conservative. Many MAC, routing protocols, scheduling scheme were proposed to promote energy conservation without degrading the performance of the network. Nonetheless, nowadays, many real-time applications have been proposed and developed using ad hoc and sensor networks.

The aim of this symposium is to provide a forum for academic and industry professionals to discuss recent progress and challenges in the area of real time applications in ad hoc and sensor networks. We encourage contributions that describe innovative work and results on AASNET. The topics of interest include but are not limited to:

  • Energy-aware routing protocols

  • Energy-aware scheduling techniques

  • Energy-aware MAC protocols

  • Artificial intelligence applications in ad hoc and sensor networks

  • Sensor networks for oil and gas industry

  • Mobility tracking schemes in ad hoc networks

  • Voice over ad hoc networks

  • Multimedia over sensor networks

  • Machine leaning schemes for ad hoc and sensor networks

  • Intrusion detection systems in ad hoc and sensor networks

  • Telehealth monitoring system using ad hoc and sensor networks



Publication

 

Only original papers will be considered that have neither been published nor submitted for publication elsewhere, including web publication. All submissions will be handled electronically. The length of the paper is limited to 6 pages. All papers will be reviewed by at least two independent reviewers.


All accepted papers will be printed in the conference proceedings published by Elsevier Science in the open-access Procedia Computer Science series on-line. Procedia Computer Sciences is hosted on www.Elsevier.com and on Elsevier content platform ScienceDirect (www.sciencedirect.com), and will be freely available worldwide. All papers in Procedia will be indexed by Scopus (www.scopus.com) and by Thomson Reuters' Conference Proceeding Citation Index http://thomsonreuters.com/conference-proceedings-citation-index/. The papers will contain linked references, XML versions and citable DOI numbers. You will be able to provide a hyperlink to all delegates and direct your conference website visitors to your proceedings. All accepted papers will also be indexed in DBLP (http://dblp.uni-trier.de/).

May 7, 2015    Submission Deadline
May 30, 2015Author Notification
July 26, 2015  Final Manuscript Due


Contact Us

Please send an email to: aasnet09 <at> gmail.com


<div>
<div class="sites-layout-tile sites-tile-name-header">
<div dir="ltr">
<p align="justify">The Seventh International Symposium on&nbsp; Applications of Ad hoc and Sensor Networks (AASNET'15) will
 be held in conjunction&nbsp;with&nbsp;the&nbsp;<span>6th International Conference on Emerging Ubiquitous
 Systems and Pervasive Networks (EUSPN-2015)&nbsp;</span><span>in&nbsp;</span><span>Berlin,
 Germany on September 27-30, 2015</span><span>.</span></p>
<p align="justify">Wireless mobile ad hoc and sensor network nodes have limited battery capacity. Hence, they
 tend to be energy conservative. Many MAC, routing protocols, scheduling scheme were proposed to promote energy conservation without degrading the performance of the network. Nonetheless, nowadays, many real-time applications have been proposed and developed
 using ad hoc and sensor networks.</p>
<p align="justify">The aim of this symposium is to provide a forum for academic and industry professionals to
 discuss recent progress and challenges in the area of real time applications in ad hoc and sensor networks. We encourage contributions that describe innovative work and results on AASNET. The topics of interest include but are not limited to:</p>
<ul>
<li>
<p align="left">Energy-aware routing protocols</p>
</li>
<li>
<p align="left">Energy-aware scheduling techniques</p>
</li>
<li>
<p align="left">Energy-aware MAC protocols</p>
</li>
<li>
<p align="left">Artificial intelligence applications in ad hoc and sensor networks</p>
</li>
<li>
<p align="left">Sensor networks for oil and gas industry</p>
</li>
<li>
<p align="left">Mobility tracking schemes in ad hoc networks</p>
</li>
<li>
<p align="left">Voice over ad hoc networks</p>
</li>
<li>
<p align="left">Multimedia over sensor networks</p>
</li>
<li>
<p align="left">Machine leaning schemes for ad hoc and sensor networks</p>
</li>
<li>
<p align="left">Intrusion detection systems in ad hoc and sensor networks</p>
</li>
<li>
<p align="left">Telehealth monitoring system using ad hoc and sensor networks</p>
</li>
</ul>
<div><br></div>
<div>
<br><p align="justify"><span lang="en-ca">Publication</span></p>
<p align="justify">&nbsp;</p>
<p align="justify"><span lang="en-ca">Only original papers will be considered that have neither been published nor submitted for publication elsewhere, including web publication. All
 submissions&nbsp;</span><span>will be handled electronically. The length of the paper is limited to 6 pages. All papers will be reviewed by at least two independent reviewers.</span></p>
<p align="justify"><span><br></span></p>
<p align="justify"><span>All accepted papers&nbsp;</span><span>will
 be printed in the conference proceedings published by Elsevier Science in the open-access Procedia Computer Science series on-line. Procedia Computer Sciences is hosted on&nbsp;</span><a href="http://www.journals.elsevier.com/procedia-computer-science" target="_blank" rel="nofollow">www.Elsevier.com</a><span>&nbsp;and
 on Elsevier content platform ScienceDirect (</span><a href="http://www.sciencedirect.com/science/journal/18770509" target="_blank" rel="nofollow">www.sciencedirect.com</a><span>),
 and will be freely available worldwide. All papers in Procedia will be indexed by Scopus (</span><a href="http://www.scopus.com/" target="_blank" rel="nofollow">www.scopus.com</a><span>)
 and by Thomson Reuters' Conference Proceeding Citation Index&nbsp;</span><a href="http://thomsonreuters.com/conference-proceedings-citation-index/" target="_blank" rel="nofollow">http://thomsonreuters.com/conference-proceedings-citation-index/</a><span>.
 The papers will contain linked references, XML versions and citable DOI numbers. You will be able to provide a hyperlink to all delegates and direct your conference website visitors to your proceedings. All accepted papers will also be indexed in DBLP (</span><a href="http://dblp.uni-trier.de/db/journals/procedia/procedia5.html#ShakshukiY11" rel="nofollow">http://dblp.uni-trier.de/</a><span>).</span></p>
</div>
</div>
</div>
<div class="sites-layout-tile sites-tile-name-content-1">
<div dir="ltr"><span></span></div>
</div>
<p><span>May 7, 2015&nbsp;
 &nbsp; Submission Deadline</span><br><span>May 30, 2015Author Notification</span><br><span>July 26, 2015 &nbsp;Final Manuscript Due</span><br></p>
<p><br></p>
<h3 xmlns="http://www.w3.org/1999/xhtml" align="left">
<span dir="ltr" tabindex="-1">Contact Us</span>
</h3>
<div class="sites-canvas-main">
<div>
<table xmlns="http://www.w3.org/1999/xhtml" cellspacing="0" class="sites-layout-name-one-column sites-layout-hbox"><tr>
<td class="sites-layout-tile sites-tile-name-content-1">
<div dir="ltr">
<span>Please se</span><span>nd an email to:&nbsp;</span><span><a href="mailto:aasnet09 <at> gmail.com">aasnet09 <at> gmail.com</a>&#8203;</span>
</div>
</td>
</tr></table>
</div>
</div>
<p><br></p>
</div>
Elisabetta Biondi | 6 Feb 11:34 2015
Picon

CFP: IEEE WoWMoM 2015 Workshop on Autonomic and Opportunistic Communications (IEEE AOC 2015)

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

Abstract submission deadline:   March 7,  2015 
Full manuscript due:            March 14, 2015
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)
------------------------------------------------------------------------
- Abstract submission deadline:   	March 7,  2015 
- Full manuscript due:                  March 14, 2015 
- 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
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

Gmane