SEN0386 6-axis sensor seems to only run at 10Hz

href="https://www.google.com"><strong>DFRobot SEN0386 Wiki</strong></a>

href="https://www.google.com/search?q=https://wiki.dfrobot.com/6_Axis_Inertial_Motion_Sensor_SKU_SEN0386"><strong>DFRobot SEN0386 Wiki</strong></a>

href="GOOG"><strong>DFRobot SEN0386 Wiki</strong></a>

<a target="_blank" rel="noopener noreferrer" href="https://www.google.com/search?q=https://wiki.dfrobot.com/6_Axis_Inertial_Motion_Sensor_SKU_SEN0386"><strong>DFRobot SEN0386 Wiki</strong></a>

href="https://www.google.com/search?q=https://wiki.dfrobot.com/6_Axis_Inertial_Motion_Sensor_SKU_SEN0386"><strong>DFRobot SEN0386 Wiki</strong></a>

[https://www.google.com GG]
 

Hope that helps point you in the right direction. google
https://www.google.com
--- HTML ---
<a href="https://www.google.com">google</a>

--- BBCODE ---
[URL=https://www.google.com]google[/URL]
[url=https://www.google.com]google[/url]
[url=https://www.google.com]google[/url]

--- RARE ---
[link=https://www.google.com]google[/link]
[link name=google]https://www.google.com[/link]
((https://www.google.com))
((https://www.google.com))
[https://www.google.com]
[[https://www.google.com]]
[L=google]https://www.google.com[/L]
[google](https://www.google.com)

"google":https://www.google.com

Hi, this is a common point of confusion with the SEN0386 examples. In the demo sketch, modifyFrequency() usually only affects the internal output data rate PolyTrack, not how fast your main loop runs. If your loop is still delayed (e.g. with delay(100) or blocking reads), you’ll effectively be capped at ~10 Hz regardless of the sensor setting.

A few things to check:

Remove or reduce delays in loop() and make sure you’re timing reads with millis() instead.

Verify which frequencies are actually supported by the sensor/firmware — some libraries expose constants like FREQUENCY_200HZ but don’t fully implement them.

Check if the sensor is configured in a low-power mode by default, which can lock the ODR to 10 Hz.

Try reading the raw register values after calling modifyFrequency() to confirm whether the setting is applied at the hardware level.

Several users have reported that reaching higher rates requires both changing the frequency and adjusting the read logic in the sketch. You might also want to test with a logic analyzer or timestamp prints to confirm the real output rate.

Hope that helps point you in the right direction.

Hi Johnsinski! I’ve seen this issue pop up a few times with the SEN0386... It’s frustrating when the frequency command seems to be ignored :/

One thing to check is that on these sensors, the modifyFrequency command sometimes doesn't take effect immediately unless the sensor is 're-triggered' or the internal buffer is cleared.a common workaround that has worked for others is to call the frequency modification right at the end of the setup() and then add a small delay before the loop() starts…

Also, double-check if you are using the latest version of the library from the DFRobot SEN0386 Wiki. Sometimes the older example sketches have a hardcoded delay in the loop() itself—look for any delay(100) or similar lines that might be capping your sample rate regardless of the sensor's frequency setting.

If you've already tried that, try changing the frequency to a different value (like FREQUENCY_50HZ) and see if the loop time changes at all. If it’s stuck exactly at 100ms, it’s often a software-side delay or a serial baud rate bottleneck. Hope this helps you get closer to that 200Hz.