<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Questions on the temperature sensor tutorial (temp conversion and decimal numbers)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/12997/questions-on-the-temperature-sensor-tutorial-temp-conversion-and-decimal-numbers</link><description>Hi all, i followed the tutorial &amp;quot; devzone.nordicsemi.com/.../&amp;quot; and did the challanges, however there is a detail i don&amp;#39;t understand (totally newbie here!): the value of temperature that i read on the master control panel (phone app) is in hexadecimal</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 05 Apr 2016 14:47:55 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/12997/questions-on-the-temperature-sensor-tutorial-temp-conversion-and-decimal-numbers" /><item><title>RE: Questions on the temperature sensor tutorial (temp conversion and decimal numbers)</title><link>https://devzone.nordicsemi.com/thread/49523?ContentTypeID=1</link><pubDate>Tue, 05 Apr 2016 14:47:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7d9fe190-c66b-468b-bc3d-7789881a7769</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Generally speaking there are no restrictions on how you represent your &lt;em&gt;value&lt;/em&gt; itself, if that is what you are asking. The Bluetooth SIG defined services and characteristics might be a bit confusing in the beginning. It might sound like you &lt;em&gt;have&lt;/em&gt; to comply with these definitions &lt;em&gt;always&lt;/em&gt;. But the deal with those is that if you are making e.g. a heart rate monitor belt then you can use these predefined standards so that all HRM applications for smart phones, for example, knows how to interpret the data. However, you are completely free to make whatever application you can imagine and represent your data however you want.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Questions on the temperature sensor tutorial (temp conversion and decimal numbers)</title><link>https://devzone.nordicsemi.com/thread/49526?ContentTypeID=1</link><pubDate>Tue, 05 Apr 2016 13:43:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2040fcf1-ca4c-4483-a60e-17addc358df4</guid><dc:creator>Revo</dc:creator><description>&lt;p&gt;Thank you very much, you can close the question! I&amp;#39;ll be asking soon for other applications!&lt;/p&gt;
&lt;p&gt;Edit: just to know for my future application, if i want to transmit the values of a sensor connected to the ADC (i convert the analog signal in digital, then send it bi BLE to a pc), there is a particular protocol to represent it on the pc or i just have to transimt for example the values returned in the ADC register?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Questions on the temperature sensor tutorial (temp conversion and decimal numbers)</title><link>https://devzone.nordicsemi.com/thread/49525?ContentTypeID=1</link><pubDate>Tue, 05 Apr 2016 13:28:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f5031e59-0e70-4991-96bd-27ac7a29a088</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;No worries. Unfortunately the MCP for PC cannot show you the decimal value. It will only show you the hex string. What you can do is to look at the &lt;em&gt;ble_app_hts&lt;/em&gt; example in the SDK (hts = Health Thermometer Service). In this example you will see how to represent a temperature value in compliance with the Bluetooth SIG defined temperature measurement characteristic. When you have a temperature characteristic configured correctly you can use MCP for Android or iPhone to see the decimal values. Just enable &amp;quot;Parse known characteristics&amp;quot; in the settings menu and MCP will format the numbers for you. Note that MCP for phones only parses the values for known Bluetooth SIG defined characteristics. So it won&amp;#39;t, e.g., parse the custom values we use in the tutorial.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Questions on the temperature sensor tutorial (temp conversion and decimal numbers)</title><link>https://devzone.nordicsemi.com/thread/49524?ContentTypeID=1</link><pubDate>Tue, 05 Apr 2016 11:58:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b8447962-9c65-43f6-b2d5-5770a87db61e</guid><dc:creator>Revo</dc:creator><description>&lt;p&gt;Great, thanks! And about getting the value in decimal instead of hexadecimal, on the control panel? Sorry for bothering!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Questions on the temperature sensor tutorial (temp conversion and decimal numbers)</title><link>https://devzone.nordicsemi.com/thread/49522?ContentTypeID=1</link><pubDate>Tue, 05 Apr 2016 11:43:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3e8dfc87-4e64-488a-aef3-f97b816bc54c</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;The result of the sd_temp_get() function is the nRF5 die temperature in 0.25 degrees celsius
as &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v2.0.0/group___n_r_f___s_o_c___f_u_n_c_t_i_o_n_s.html?resultof=%22%73%64%5f%74%65%6d%70%5f%67%65%74%22%20"&gt;documented here&lt;/a&gt;. So to get the real temperature you would have to divide the value by 4. Then you can convert it to fahrenheit by multiplying the temperature by 1.8 and finally add 32.&lt;/p&gt;
&lt;p&gt;Bluetooth SIG has also defined a &lt;a href="https://developer.bluetooth.org/gatt/characteristics/Pages/CharacteristicViewer.aspx?u=org.bluetooth.characteristic.temperature_measurement.xml"&gt;Temperature Measurement Characteristic&lt;/a&gt; with a standard way of representing the temperature. However, to make it simple and to show how to use vendor specific UUIDs I chose to do it differently and leave it up to the user to handle the conversion and representation.&lt;/p&gt;
&lt;p&gt;I should probably have made this clearer in the tutorial and I will try to get it updated.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>