<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Do not understand how to interpret IMU output (HEX) to (DEC).]]></title><description><![CDATA[<p>Hi,<br />
We are working with an OPENIMU300RI and trying to get the same values we see in NAVVIEW (acceleration/rate of gyro/temperature) using the HEX output directly from the sensor. For example:</p>
<p>We get this following characters:</p>
<p>5555 5331 18 <strong>fff2</strong>fffcf33400030003fffb280828082808280ed1eb0300 6a55</p>
<p>NavView hex value: ffff2<br />
Navview output: -1.0254g<br />
Decimal value we get after conversion: -2378</p>
<p>We are not sure how to convert from HEX to the values we see in NAVVIEW. After been playing with the IMU sensor we have identified acelerations + rate f gyro + temperature outputs, but we fail when try to get the proper values.</p>
<p>We are doing something wrong for sure. We are using the OpenIMU Documentation dated on Sep 27, 2019.</p>
<p>Thanks in advance!!!!</p>
<p><img src="http://navview.blob.core.windows.net/forum/upload/picture-k2nezjte.png" alt="picture.png" class="img-responsive img-markdown" /></p>
]]></description><link>https://forum.aceinna.com//topic/98/do-not-understand-how-to-interpret-imu-output-hex-to-dec</link><generator>RSS for Node</generator><lastBuildDate>Thu, 17 Sep 2026 01:07:27 GMT</lastBuildDate><atom:link href="https://forum.aceinna.com//topic/98.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 06 Nov 2019 15:06:22 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Do not understand how to interpret IMU output (HEX) to (DEC). on Wed, 06 Nov 2019 15:06:22 GMT]]></title><description><![CDATA[<p>Hi,<br />
We are working with an OPENIMU300RI and trying to get the same values we see in NAVVIEW (acceleration/rate of gyro/temperature) using the HEX output directly from the sensor. For example:</p>
<p>We get this following characters:</p>
<p>5555 5331 18 <strong>fff2</strong>fffcf33400030003fffb280828082808280ed1eb0300 6a55</p>
<p>NavView hex value: ffff2<br />
Navview output: -1.0254g<br />
Decimal value we get after conversion: -2378</p>
<p>We are not sure how to convert from HEX to the values we see in NAVVIEW. After been playing with the IMU sensor we have identified acelerations + rate f gyro + temperature outputs, but we fail when try to get the proper values.</p>
<p>We are doing something wrong for sure. We are using the OpenIMU Documentation dated on Sep 27, 2019.</p>
<p>Thanks in advance!!!!</p>
<p><img src="http://navview.blob.core.windows.net/forum/upload/picture-k2nezjte.png" alt="picture.png" class="img-responsive img-markdown" /></p>
]]></description><link>https://forum.aceinna.com//post/393</link><guid isPermaLink="true">https://forum.aceinna.com//post/393</guid><dc:creator><![CDATA[david]]></dc:creator><pubDate>Wed, 06 Nov 2019 15:06:22 GMT</pubDate></item><item><title><![CDATA[Reply to Do not understand how to interpret IMU output (HEX) to (DEC). on Thu, 07 Nov 2019 07:10:51 GMT]]></title><description><![CDATA[<p>Hi David, as for the OpenIMU300RI, the CAN interface is the first choose for customer, if you want to just use the UART interface , the OpenIMU300ZI unit is a better choose than OpenIMU300RI.  What kind of application that you want to intergate with IMU?</p>
]]></description><link>https://forum.aceinna.com//post/394</link><guid isPermaLink="true">https://forum.aceinna.com//post/394</guid><dc:creator><![CDATA[Li YiFan]]></dc:creator><pubDate>Thu, 07 Nov 2019 07:10:51 GMT</pubDate></item><item><title><![CDATA[Reply to Do not understand how to interpret IMU output (HEX) to (DEC). on Thu, 07 Nov 2019 07:57:00 GMT]]></title><description><![CDATA[<p>We are planning to install the OPENIMU300RI within a nacelle of a Wind Turbine. We want to measure the accelerations + rate of gyros when the WTG is under power production. For this purpose we want to connect the IMU to a DAS (Data adquisition System) that reads the HEX output data directly. When we want to translate it to DECIMAL we can not get the correct values that we see in NAVVIEW.</p>
]]></description><link>https://forum.aceinna.com//post/395</link><guid isPermaLink="true">https://forum.aceinna.com//post/395</guid><dc:creator><![CDATA[david]]></dc:creator><pubDate>Thu, 07 Nov 2019 07:57:00 GMT</pubDate></item><item><title><![CDATA[Reply to Do not understand how to interpret IMU output (HEX) to (DEC). on Fri, 08 Nov 2019 07:03:17 GMT]]></title><description><![CDATA[<p>Hi David, the usage from your side to measure the acc/gyro via uart interface, IMU381/OpenIMU300ZI/OpenIMU330BI could be better choices.</p>
<p>As for the S1 package, you could refer the page below:<br />
<img src="http://navview.blob.core.windows.net/forum/upload/2019-11-08_14h58_45-k2psivbr.jpg" alt="2019-11-08_14h58_45.jpg" class="img-responsive img-markdown" /></p>
]]></description><link>https://forum.aceinna.com//post/396</link><guid isPermaLink="true">https://forum.aceinna.com//post/396</guid><dc:creator><![CDATA[Li YiFan]]></dc:creator><pubDate>Fri, 08 Nov 2019 07:03:17 GMT</pubDate></item><item><title><![CDATA[Reply to Do not understand how to interpret IMU output (HEX) to (DEC). on Fri, 08 Nov 2019 08:58:36 GMT]]></title><description><![CDATA[<p>Please also notice that Big Endian (Most Significant Byte First) is used.</p>
]]></description><link>https://forum.aceinna.com//post/397</link><guid isPermaLink="true">https://forum.aceinna.com//post/397</guid><dc:creator><![CDATA[Dong xiaoguang]]></dc:creator><pubDate>Fri, 08 Nov 2019 08:58:36 GMT</pubDate></item><item><title><![CDATA[Reply to Do not understand how to interpret IMU output (HEX) to (DEC). on Mon, 11 Nov 2019 07:49:32 GMT]]></title><description><![CDATA[<p>Thanks for the fast response.  Issue solved.</p>
<p>Regards</p>
<p>David</p>
]]></description><link>https://forum.aceinna.com//post/401</link><guid isPermaLink="true">https://forum.aceinna.com//post/401</guid><dc:creator><![CDATA[david]]></dc:creator><pubDate>Mon, 11 Nov 2019 07:49:32 GMT</pubDate></item></channel></rss>