You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be amazing to support Inertial Measurement Units (such as the LSM9DS1), and even other environmental sensors, such as UltraSound, Temperature sensors.
Prototyping these things takes time, and developing firmware for them takes time too.
Using a dataset means that it would be possible to test how your code reacts to contrived environmental conditions.... does the code work properly when the temperature sensor goes above/below certain thresholds?
Food for thought.
If the UI could react to moving these devices by click/drag operations to provide simulated values for Gyro and Accelerometer values.. that would be very very cool indeed. If not possible, how about the user provides a file with fake/empirical values over a timeline? It's a big ask, I know, but hey, let's think big here!
The text was updated successfully, but these errors were encountered:
We do have the MPU6050 IMU, how is the LSM9DS1 different?
In any case, feel free to open specific issues per device type, so it'll be easier to track the implementation of individual sensors. We're also working on a way for users to create their own custom parts/sensors, see #301 for details.
As for the UI, mind providing a mock/sketch of what you imagine it could look like?
It would be amazing to support Inertial Measurement Units (such as the LSM9DS1), and even other environmental sensors, such as UltraSound, Temperature sensors.
Prototyping these things takes time, and developing firmware for them takes time too.
Using a dataset means that it would be possible to test how your code reacts to contrived environmental conditions.... does the code work properly when the temperature sensor goes above/below certain thresholds?
Food for thought.
If the UI could react to moving these devices by click/drag operations to provide simulated values for Gyro and Accelerometer values.. that would be very very cool indeed. If not possible, how about the user provides a file with fake/empirical values over a timeline? It's a big ask, I know, but hey, let's think big here!
The text was updated successfully, but these errors were encountered: