Bosch Shared
- Top Results
See all results
- About shiny
- About shiny
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About shiny
since
08-19-2020
09-04-2020
shiny
Member
4
Posts
0
Likes
1
Solution
08-27-2020
11:48 AM
Apologies, columns 2, 3, 4 are the X, Y, Z orientation output, 5-13 are the calibration parameters. There is indeed vibration, I am intentionally inducing it as its running on a test bed to replicate the robot. I practice there will be vibration as its mounted on a robot driving in rough terrain. There will be vibration from the following sources: Grips on the tyres interfacing with the ground Roughness of the terrain Sudden changes in direction Physical contact with objects Mechanical damping might be possible to an extent.
... View more
08-26-2020
10:02 AM
I have been logging data for the last while with heading, calibration parameters and calibration status. I have been testing the sensor on a test bed to apply constant roll or pitch motion for a specifc angle and frequency so that I can change parameters and see results for identical mechanical input. The motor frequency is around 490Hz, the sensor itself is about 35cm away from the motors. I have also put a compass in the area around where the sensor is mounted, I am not seeing any sudden deflections. I have a number of observations, I have included these in the data log too. I have found that the pauses you recommended do improve the result, 60 seconds is a bit too long, it still drifted. Pausing every 20s for a duration of 2s is good. There are about 250seconds of instability after (physical) calibration before it settles. There are about 55 seconds of "lag" where (manual, software) calibration values are programmed (during setup) before they are visible in the calibration data outputs. Sys reports zero for all that time and then it changes to 3 at which point everything works fine. In another scenario I apply the same calibration at regular intervals during a standard 15min test, it works fine with only one zero value before returning the correct heading. The lag I suspect is potentially due to my startup routine, I see other users on the forum talking about initialisation sequences for the sensor so I'm currently looking at that. While the pause approach helps significantly , ideally we don't want to pause the robot as when people are watching it operate it looks like something is wrong when it intermittently stops.
... View more
08-21-2020
10:48 AM
Currently operating in NDoF mode using the Yaw component for heading. There are two test areas (250km apart): - An open field (relatively smooth terrain, no metal, no concrete) - An enclosed shed (Metal everywhere, concrete floor, rough terrain). I'm seeing similar behavour in both locations (for the same route and distance travelled). How long do I need to stop the robot for to allow the sensors time to readjust?
... View more
08-19-2020
05:30 PM
I have been using the BMO055 for the last few months as a heading sensor in our robot. There is noticeable drift in the heading reading which seems to happen in a number of scenarios: Sudden Jolt/impact - This could happen in the first 5 seconds after operation throwing the heading off Duration - If the robot operates continuously the heading drifts over time Terrain - Depending on the roughness of the terrain the heading will drift from 30 to 90 degrees over the course of 5+ minutes These are some of the things I'm going to try Store calibration values and intermittently overwrite the new values loaded by the fusion algorithm Stop the robot moving at regular intervals to allow the sensors to recalibrate What other steps can I take to mitigate against these problems?
... View more
Still looking for something?
- Top Results
See all results