11.07.2015 Views

12th International Symposium on District Heating and Cooling

12th International Symposium on District Heating and Cooling

12th International Symposium on District Heating and Cooling

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

The <str<strong>on</strong>g>12th</str<strong>on</strong>g> <str<strong>on</strong>g>Internati<strong>on</strong>al</str<strong>on</strong>g> <str<strong>on</strong>g>Symposium</str<strong>on</strong>g> <strong>on</strong> <strong>District</strong> <strong>Heating</strong> <strong>and</strong> <strong>Cooling</strong>,September 5 th to September 7 th , 2010, Tallinn, Est<strong>on</strong>iaTo obtain IPv6/6LoWPAN functi<strong>on</strong>ality in the Mulles,the lightweight operating systems C<strong>on</strong>tiki [14] <strong>and</strong>TinyOS [15] have been successfully ported to the Mulleplatform. Both operating systems were specificallydesigned to be compatible with resource limitedembedded systems such as Mulle. Moreover, C<strong>on</strong>tiki<strong>and</strong> TinyOS both support IPv6 <strong>and</strong> 6LoWPAN.However, TinyOS was selected for this study becausestability issues due to edge-routing problems withC<strong>on</strong>tiki.Sensor platform energy usageObtaining an acceptable life expectancy is <strong>on</strong>e of thebiggest challenges to battery powered, wirelessdevices. In Sweden, heat meters are inspected every 5to 10 years, depending <strong>on</strong> the size of the meter. Thelife expectancy of wireless devices should beequivalent to the inspecti<strong>on</strong> period to avoid frequent<strong>and</strong> expensive battery replacements. All sensor nodesdo however not need to be battery powered. In thecase of available electric power in close proximity, e.g.for platforms mounted in pumps or valves there is noexplicit need for batteries since there are electricityavailable. At other sensor platforms, battery power isthe <strong>on</strong>ly feasible soluti<strong>on</strong>, for instance outdoortemperature sensors.To determine the amount of energy used by a wirelesssensing device, the current at the sensor platformassociated with IPv6/6LoWPAN communicati<strong>on</strong> wasmeasured. To measure the current used by the device,a 1 ohm high precisi<strong>on</strong> resistor was c<strong>on</strong>nected in seriesto the Mulle power c<strong>on</strong>nector. The voltage dropgenerated across the resistor was amplified 100 timeswith a MAX4372H amplifier circuit. Using an analogacquisiti<strong>on</strong> card, the amplified signal was measured<strong>and</strong> stored in an ordinary PC. Due to poor precisi<strong>on</strong> atvery low current, complementary measurements wereperformed with a high precisi<strong>on</strong> ampere-meter todetermine the current usage of the Mulle, when it wasin deep sleep mode.To evaluate the energy cost of transmitting datapackets with UDP <strong>on</strong> IPv6/6LoWPAN, packets withpayload sizes between 1 <strong>and</strong> 100 bytes weretransmitted, <strong>and</strong> the expected lifetime of the sensorwas calculated. Fig. 8 displays the expected lifetime ofa sensor with a 500 mA battery <strong>and</strong> a 15 minutetransmissi<strong>on</strong> interval. Out of curiosity, both TinyOS <strong>and</strong>C<strong>on</strong>tiki were programmed to transmit UDP packets ofdifferent sizes at c<strong>on</strong>secutive time intervals to observeany differences in energy usage between the two. Theresults indicated that the energy usage of 50 to 80-bytepayloads in C<strong>on</strong>tiki <strong>and</strong> Tiny OS were significantlydifferent. The observed difference between operatingsystems is most likely related to the method of headercompressi<strong>on</strong>. Specifically, C<strong>on</strong>tiki uses HC1, whileTinyOS is based <strong>on</strong> HC01. However, both methods area part of the 6LoWPAN st<strong>and</strong>ard. Additi<strong>on</strong>ally, TinyOSuses short addressing, while C<strong>on</strong>tiki employs l<strong>on</strong>gaddressing. The type of addressing <strong>and</strong> headercompressi<strong>on</strong> used by the OS can be changed, but inthis particular test, default settings were used.For payload sizes greater than 60/90 bytes, the IPpacket had to be divided into two separate 802.15.4frames because the maximum frame size of IEEE805.15.4 is 127 bytes. The separati<strong>on</strong> of IP packetsincreased energy usage <strong>and</strong> decreased the expectedlifetime of the sensor. Thus, software developersshould c<strong>on</strong>sider the maximum frame size if absolutemaximizati<strong>on</strong> of sensor lifetime targeted. Howeverincreased payload sizes can of course becompensated with a larger battery.As shown in Fig. 8, the fixed transmissi<strong>on</strong> interval wasset to 15 minutes, <strong>and</strong> the effect of transmissi<strong>on</strong>interval <strong>on</strong> the expected lifetime of the sensor wasanalyzed. Additi<strong>on</strong>ally, sensor lifetime was evaluated atvarious transmissi<strong>on</strong> frequencies <strong>and</strong> a fixed payloadof 80 bytes, as shown in Fig. 9. In accordance to theorythe results indicated that a low transmissi<strong>on</strong> frequencyhas a positive effect <strong>on</strong> sensor lifetime. In the case ofc<strong>on</strong>text aware sensors, which <strong>on</strong>ly transmit data whenrequired e.g. when a measured temperature exceeds aset threshold, sensor life expectancy will in most casesbe increased. However, the impact of thesleep/st<strong>and</strong>by energy usage will make up a largerpercentage of the total energy usage, which hence willmean that the importance of keeping the sleep currentlow will be even bigger.Fig. 8. The effect of payload size <strong>on</strong> the expected lifetimeof a sensor platform at a transmissi<strong>on</strong> rate of4 transmissi<strong>on</strong>s per hour (1 to 100 bytes).9

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!