STM32duino
Replies: 10 comments 5 replies
-
Beta Was this translation helpful? Give feedback.
-
|
Thank you. Snippet:OutputWhen I wrote the debounce step from 10 to 2, reading it back does give me 2, so I'm unsure how one works but not the other. |
Beta Was this translation helpful? Give feedback.
-
|
Hello @voloved , |
Beta Was this translation helpful? Give feedback.
-
|
Hello @cparata , My board now has the LIS2DUX chip. I am getting correct WHO_IS, steps, accelerometer readings, etc with the LIS2DUX library, so I know it is installed correctly. Would you be able to revisit my questions with knowing that the LIS2DUX is the part that I am using? My apologies if I provided confusion on that. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @voloved , |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the advice! Tap ControlI did notice the ODR needed to by high-power 400 and disabled running the step counter during my original testing. I read back the ODR and confirmed it was set to 400. Here are my parameters: Step CounterI changed the debounce to 1 step from 10 yesterday after rereading the datasheet's explanation of the debounce. I did not read see the application notes and I'll start reading through them. else if (movement_state.has_lis2dux) {
LIS2DUXS12Sensor_Enable_X(&ctx);
LIS2DUXS12Sensor_Enable_Pedometer(&ctx, LIS2DUXS12_INT1_PIN);
+ lis2duxs12_stpcnt_debounce_set(&ctx, 1);
movement_state.counting_steps = true;
return true;It's set after Also, would you happen to know if there are any known issues with setting |
Beta Was this translation helpful? Give feedback.
-
|
Hello @voloved , Obviously, you need to adapt I2C instance and interrupt pin on your side, but in my case the sketch works as expected. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the great support and detail. I'll take some time tonight to give this a try. I see the difference in the code is that you're using As for the counts not reading after an hour, I found that I had a background task that turns of the pedometer after a certain time. The issue was on my end 😅. In the last hour, I tried these parameters after reading through the app notes: Afterwards, I tapped the watch once a second. i got a few tap responses, but they were extremely sporadic and didn't match my taps. But at least it shows that I can read taps! Here's the output of my console. I tap once a second, but only 2 of the seconds saw a tap: Latched vs PulsedI saw that the chip allows for pulsed (90us on) or latched mode. My code: Console Output: |
Beta Was this translation helpful? Give feedback.
-
|
Hi @voloved , |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for sharing that library. I have been rewriting C++ functions into C code as I needed them. I'll likely move over to it when I have the time since it allows for copying more functions over with no rewriting needed and has a more consistent style. However, when I looked over that library in order to see if there were any differences in how the pedometer is set up (since pedometer accuracy is my first goal), I only saw that the C library did differently was that it reset the chip right after reading it. Which I wouldn't expect to affect sensitivity of the counter. I have made a video of my step counter in action. It shows that it does count steps and that it's debounce is under 10. It's just not registering steps. Should I expect the accuracy of my step counter that's seen in the video? I double checked to make sure my ODR and range are the same as both the Arduino and C code examples |
Beta Was this translation helpful? Give feedback.
-
|
Hi @cparata , Did you get a chance to see the video I linked? Thank you, |
Beta Was this translation helpful? Give feedback.
-
|
Hello @voloved , |
Beta Was this translation helpful? Give feedback.
-
|
@cparata , I got it working! Thank you so much for your help, and sharing the C examples. I missed them in my search and using those made a huge difference. For others experiencing issues with the tap and step counter, here were the issues:
I'll still reach out to the ST Community to see if there is any more tuning that I can do, but I'm no longer missing a ton of steps. I have one last question:I notice that when I perform the following commands, the step count gets reset: I can see why a reset and deep-sleep can lead to that, but the application notes made it sound like only resetting the step count or a hard power-cycle would lead to the steps resetting. Is that not the case? If that's not an option, it's not a big deal, as I have the logic below to keep the step count summing up until I ask for a step reset. But I'd like to make sure there isn't a cleaner option. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @voloved ,
or the line:
I suggest to ask it on ST Community as well where an expert of the sensor can answer. |
Beta Was this translation helpful? Give feedback.
-
|
Discussion moved to ST Community: https://community.st.com/t5/others-hardware-and-software/lis2dux-step-counter-maximize-battery/m-p/856258#M32934 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I am working on adding a pedometer to the Sensorwatch project using this chip.
I added the logic found in this codebase to my repository and it's working fairly-well execpt for 2 issues:
Tap detection isn't working
The project currently has an LIS2DW chip, which allows for tap control. I'm trying to remake that logic with the LIS2DUX.
Here is the logic I used to set up tap control.
It's based off this section of the repo.
I was able to confirm that X,Y, and Z readings are updating correctly, and the interrupt does trigger on six_d events when I enable it, which leads me to believe that it must be the tap control parameters that I am setting up incorrectly.
Are there parameters that are recommended to prove that tap detection works?
Are there any other suggestions on why I don't see tap events?
The step counter is extremely insensitive and after about an hour, I stop seeing the step counter update at all.
The main reason I want the LIS2DUX is for the step counting feature. I ported the stm32duino code, and it works, but not well. It under-counts steps and I often see that I run for 100+ steps with nothing being read.
I often find that if I keep the pedometer running for a while, it just stops, and the only way to get it working again is to reset/cycle power to my board, as if the LIS2DUX just stops communicating after enough time passes.
I see in the datasheet that there is debounce and time delta settings that I can change, which may be able to help with the undercounting, but I don't know if it'll also address the chip just stopping communication over time. Since the base library doesn't mess with those settings, I'm hesitant on rabbit-holing too far without some guidance.
Are there parameters that are recommended to stop the LIS2DUX from stopping communication? Is that even what I'm seeing?
How do I make the step counter more sensative so it doesn't miss 100+ steps while running?
Are there any other suggestions on why I don't see tap events?
Enabling of the step counter in my code
The step Counter enable function itself
Based off this code from ST
Beta Was this translation helpful? Give feedback.
All reactions