adafruit / adafruit/Adafruit_Wippersnapper_Arduino
Support I2C devices with a vector event data (in v1 ideally as already supported in v2)
- Dominant language
- C++
- Stars
- 54
- Forks
- 56
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 11
Description
**Is your feature request related to a problem? Please describe.**
V1 of WipperSnapper has no support for the vector sensor types in Adafruit Sensor, although the event type is in theory part of the spec. This means the following cannot be supported currently:
```
wippersnapper_i2c_v1_SensorType_SENSOR_TYPE_ACCELEROMETER = 1,
wippersnapper_i2c_v1_SensorType_SENSOR_TYPE_MAGNETIC_FIELD = 2,
wippersnapper_i2c_v1_SensorType_SENSOR_TYPE_ORIENTATION = 3,
wippersnapper_i2c_v1_SensorType_SENSOR_TYPE_GYROSCOPE = 4,
```
**Describe the solution you'd like**
Add vector support to the protobuf
**Describe alternatives you've considered**
The current offering is to mash the data together to a single value with no direction.
**Additional context**
This affects a bunch of components that could otherwise be added, but to be fair within a matter of a few months v2 should be ready to support those components, and already includes vectors.
Maybe I should try adding the blocked components to v2, to ensure the protobuf suites our needs, as offline-mode is using it as a testbed.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing the v1 and v2 protobuf definitions, focusing on how Adafruit Sensor vector event types are represented. Confirm what changes are required for v1 to support the listed accelerometer, magnetic-field, orientation, and gyroscope types while preserving the existing offering; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- arduino, cpp
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100