<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Sensors中的主题 Re: about gyro calibration</title>
    <link>https://community.nxp.com/t5/Sensors/about-gyro-calibration/m-p/415154#M1831</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm sorry I have one more question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tested the board(9-axis) and measured a time to stabilize Yaw(compass) values.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="color: #000000; font-size: 12px; font-family: 굴림, gulim, helvetica, sans-serif;"&gt;scenario ::&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;movement -&amp;gt; stop -&amp;gt; measuring a time until Yaw values is fixed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and it takes 10~15sec. i am sure that the board was moving sufficiently before measurement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="en"&gt;Why did it take a long time to stabilize ? it is problem of magnetic sensor or gyro sensor?&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 23 Oct 2015 01:31:11 GMT</pubDate>
    <dc:creator>josol</dc:creator>
    <dc:date>2015-10-23T01:31:11Z</dc:date>
    <item>
      <title>about gyro calibration</title>
      <link>https://community.nxp.com/t5/Sensors/about-gyro-calibration/m-p/415151#M1828</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Hi. I am using FXAS2100X with &lt;SPAN style="color: #545454; font-family: 'Apple SD Gothic Neo', arial, sans-serif;"&gt;Accelerometer and &lt;SPAN style="color: #545454; font-family: 'Apple SD Gothic Neo', arial, sans-serif;"&gt;magnetic sensor to get a roll, pitch, yaw.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;and I want to decrease gyro sensor drift error as much as i can.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Question :&lt;/P&gt;&lt;P&gt;I found that &lt;SPAN style="font-size: 13.3333px;"&gt;FXAS2100X(gyro) has resister to initiate drift offset. and if i use this register p&lt;SPAN lang="en"&gt;eriodically, can i reduce a offset error slightly??&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="89979_89979.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/120718i55659E5923EE4475/image-size/large?v=v2&amp;amp;px=999" role="button" title="89979_89979.png" alt="89979_89979.png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/26675iA6BAA80834A7D564/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Feb 2026 21:02:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Sensors/about-gyro-calibration/m-p/415151#M1828</guid>
      <dc:creator>josol</dc:creator>
      <dc:date>2026-02-03T21:02:08Z</dc:date>
    </item>
    <item>
      <title>Re: about gyro calibration</title>
      <link>https://community.nxp.com/t5/Sensors/about-gyro-calibration/m-p/415152#M1829</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This feature simply makes a measurement of the gyro rate and then subtracts it off from future measurements. Of course, you have to be absolutely sure that the gyro is not rotating when this feature is used. From a user interface viewpoint, users may not like the extra step of ensuring the unit is stationary and then pressing a button.&lt;/P&gt;&lt;P&gt;It also doesn't fundamentally solve the problem of gyro integration over long periods of time. The gyro offset is temperature, orientation and acceleration dependent and software integration errors will also add up over time. So you'll still need to use a Kalman or other filter to stabilize the orientation to the gravity and geomagnetic vectors.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Oct 2015 16:22:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Sensors/about-gyro-calibration/m-p/415152#M1829</guid>
      <dc:creator>markpedley</dc:creator>
      <dc:date>2015-10-21T16:22:49Z</dc:date>
    </item>
    <item>
      <title>Re: about gyro calibration</title>
      <link>https://community.nxp.com/t5/Sensors/about-gyro-calibration/m-p/415153#M1830</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks a lot.&lt;/P&gt;&lt;P&gt;have a great day!:smileyhappy:&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Oct 2015 23:10:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Sensors/about-gyro-calibration/m-p/415153#M1830</guid>
      <dc:creator>josol</dc:creator>
      <dc:date>2015-10-21T23:10:00Z</dc:date>
    </item>
    <item>
      <title>Re: about gyro calibration</title>
      <link>https://community.nxp.com/t5/Sensors/about-gyro-calibration/m-p/415154#M1831</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm sorry I have one more question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tested the board(9-axis) and measured a time to stabilize Yaw(compass) values.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="color: #000000; font-size: 12px; font-family: 굴림, gulim, helvetica, sans-serif;"&gt;scenario ::&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;movement -&amp;gt; stop -&amp;gt; measuring a time until Yaw values is fixed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and it takes 10~15sec. i am sure that the board was moving sufficiently before measurement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="en"&gt;Why did it take a long time to stabilize ? it is problem of magnetic sensor or gyro sensor?&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Oct 2015 01:31:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Sensors/about-gyro-calibration/m-p/415154#M1831</guid>
      <dc:creator>josol</dc:creator>
      <dc:date>2015-10-23T01:31:11Z</dc:date>
    </item>
    <item>
      <title>Re: about gyro calibration</title>
      <link>https://community.nxp.com/t5/Sensors/about-gyro-calibration/m-p/415155#M1832</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The answer is that everything is a tradeoff.&lt;/P&gt;&lt;P&gt;On power up, we have no knowledge of the offset for the gyro sensor so we assume zero and let the Kalman filter decide on the value. This takes tens of seconds but is much safer than using the initial gyro reading and assuming that is the offset. The user could be rotating the PCB at up to 2000 deg per sec so we don’t want to assume that the board is stationary. So zero deg offset is a sensible initial value.&lt;/P&gt;&lt;P&gt;After power up, the gyro offset is very slowly varying. It’s essentially constant apart from some second order dependence on temperature and gravity (orientation). We don’t want it to change very quickly after power up and of course that makes the initial convergence at power up take tens of seconds.&lt;/P&gt;&lt;P&gt;If the power up convergence was faster then the gyro offset would be affected by aggressive hand motion during gaming applications.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Oct 2015 02:16:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Sensors/about-gyro-calibration/m-p/415155#M1832</guid>
      <dc:creator>markpedley</dc:creator>
      <dc:date>2015-10-23T02:16:43Z</dc:date>
    </item>
    <item>
      <title>Re: about gyro calibration</title>
      <link>https://community.nxp.com/t5/Sensors/about-gyro-calibration/m-p/415156#M1833</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;and I am sorry about continuous questions, i am short of sensor knowledge, it is very difficult&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if i understood correctly, &lt;/P&gt;&lt;P&gt;1. power up&lt;/P&gt;&lt;P&gt;2. Give information to kalman filter &lt;SPAN style="color: #51626f; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt;sufficiently by moving the board for a long time&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt;3. And Let &lt;SPAN style="color: #51626f; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt;the board be stationary.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt;after 3 steps, is it nomal operation to take 10 sec for fixing the Yaw values? &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt;I thought that if i gave enough gyro values to kalman filter, it is natural to find fixed yaw value fast because it is not right after power up &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt;and I thought magnetic sensor helps to find &lt;SPAN style="color: #51626f; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt;fixed yaw value &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt;Is there a way to &lt;SPAN style="color: #51626f; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt;change the values quickly?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt;Thank you&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Oct 2015 04:44:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Sensors/about-gyro-calibration/m-p/415156#M1833</guid>
      <dc:creator>josol</dc:creator>
      <dc:date>2015-10-23T04:44:28Z</dc:date>
    </item>
    <item>
      <title>Re: about gyro calibration</title>
      <link>https://community.nxp.com/t5/Sensors/about-gyro-calibration/m-p/415157#M1834</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A balance must be found between power on estimation of the gyro offset and tracking of the gyro offset drift over time.&lt;/P&gt;&lt;P&gt;One solution would be to ask the end user to place the PCB stationary and then use that value to estimate the gyro offset.&lt;/P&gt;&lt;P&gt;And then the gyro offset could be saved to non-volatile memory and then read on power up.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Oct 2015 16:06:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Sensors/about-gyro-calibration/m-p/415157#M1834</guid>
      <dc:creator>markpedley</dc:creator>
      <dc:date>2015-10-23T16:06:33Z</dc:date>
    </item>
  </channel>
</rss>

