<![CDATA[StickC - SH200Q Acceleration Range]]>How to init the acceleration range to 16g for Sh200q on StickC with the MicroPython code?

]]>https://community.m5stack.com/topic/1051/stickc-sh200q-acceleration-rangeRSS for NodeWed, 29 Apr 2026 23:33:35 GMTMon, 03 Jun 2019 03:27:53 GMT60<![CDATA[Reply to StickC - SH200Q Acceleration Range on Mon, 03 Feb 2020 14:20:24 GMT]]>@zhufu86 Hey, I came along to look for python support for the sh200q. Seems that you use it in python with the hardware module.
May sound stupid but I'm unsure where to find the module... (Very new to m5Stick / m5Stack) I am using the m5Stick.

Best regards,
klaas

]]>https://community.m5stack.com/post/7298https://community.m5stack.com/post/7298Mon, 03 Feb 2020 14:20:24 GMT<![CDATA[Reply to StickC - SH200Q Acceleration Range on Tue, 04 Jun 2019 06:16:10 GMT]]>I know, it a bug..., will fix it

]]>https://community.m5stack.com/post/4521https://community.m5stack.com/post/4521Tue, 04 Jun 2019 06:16:10 GMT<![CDATA[Reply to StickC - SH200Q Acceleration Range on Tue, 04 Jun 2019 06:10:59 GMT]]>@property def acceleration(self): so = self._accel_so data = self._regThreeShort(0x00) return tuple([round(value / so, 3) for value in data])

output data is not raw data, and ACCEL_FS_SEL_16G only measuring range, does not affect the value of acceleration

]]>https://community.m5stack.com/post/4520https://community.m5stack.com/post/4520Tue, 04 Jun 2019 06:10:59 GMT<![CDATA[Reply to StickC - SH200Q Acceleration Range on Tue, 04 Jun 2019 02:38:55 GMT]]>@zhufu86

Finally, I had it solved.

It seems I need to write the correct configuration into the SH200Q register manually.

0_1559615580846_8a54c136-0046-4424-b9d2-026b230adbd8-image.png

Here is how to....

MicroPython ESP32_LoBo_v3.2.24 - 2018-09-06 on M5Stack with ESP32
Type "help()" for more information.
>>> from hardware import sh200q
>>> imu = sh200q.Sh200q(accel_fs=sh200q.ACCEL_FS_SEL_16G)
>>> imu.acceleration[0]
4.332
>>> imu.i2c.readfrom_mem(108,0x16,1)
b'\x10'
>>> imu.i2c.writeto_mem(108,0x16,'\x12')
1
>>> imu.acceleration[0]
1.086
>>>

Is it a bug in module "hardware.sh200q"?

]]>https://community.m5stack.com/post/4517https://community.m5stack.com/post/4517Tue, 04 Jun 2019 02:38:55 GMT<![CDATA[Reply to StickC - SH200Q Acceleration Range on Mon, 03 Jun 2019 13:19:19 GMT]]>@zhufu86 said in StickC - SH200Q Acceleration Range:

imu._accel_so=8192

Update...
No matter how I initiate SH200Q, I can not get the range larger than 4g.
Need more investigation.

]]>https://community.m5stack.com/post/4513https://community.m5stack.com/post/4513Mon, 03 Jun 2019 13:19:19 GMT<![CDATA[Reply to StickC - SH200Q Acceleration Range on Mon, 03 Jun 2019 05:36:15 GMT]]>@zhufu86 said in StickC - SH200Q Acceleration Range:

imu = sh200q.Sh200q(accel_fs=sh200q.ACCEL_FS_SEL_16G)

I tried the codes in the StickC and got the acceleration value four times as big as the value before. So I suppose SH200Q is initiated with 4g range if lack of accel_fs setting.
For temporary solution I devide the returned acceleration value by 4.

  x = imu.acceleration[0]/4
  y = imu.acceleration[1]/4
  z = imu.acceleration[2]/4

I also did some tests as below. No clue...

>>> imu = sh200q.Sh200q()
>>> imu._accel_so
8192
>>> imu.acceleration[2]
0.995
>>> imu = sh200q.Sh200q(accel_fs=sh200q.ACCEL_FS_SEL_16G)
>>> imu._accel_so
2048
>>> imu.acceleration[2]
4.058
>>> imu.acceleration[2]/4
0.9985
>>> imu._accel_so=8192
>>> imu.acceleration[2]
0.999
>>>
]]>https://community.m5stack.com/post/4511https://community.m5stack.com/post/4511Mon, 03 Jun 2019 05:36:15 GMT<![CDATA[Reply to StickC - SH200Q Acceleration Range on Mon, 03 Jun 2019 04:53:42 GMT]]>@zhufu86

I tried the code blow. But I don't know whether it is correct.

from hardware import sh200q
imu = sh200q.Sh200q(accel_fs=sh200q.ACCEL_FS_SEL_16G)
]]>https://community.m5stack.com/post/4510https://community.m5stack.com/post/4510Mon, 03 Jun 2019 04:53:42 GMT