Ping360 example uses auto messages without checking protocol support
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- api, embedded-iot
Research direction
Start in test/test-device-ping360.cpp at the linked example and review the Ping-protocol v1.1 auto-transmission documentation. Add a protocol-capability check so unsupported devices use only manual messages, then verify the example's behavior for devices that do and do not support the relevant messages.
Written by the indexing model from the issue text.
Description
Ping-protocol v1.1 introduced support for auto transmission for the ping360 message set, which our example uses without checking that the device is capable of handling and sending the relevant messages.
Ideally it should check the protocol version and fall back to only manual messages if relevant.
Raised/discussed here.
- Dominant language
- C++
- Stars
- 19
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bluerobotics/ping-cpp
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bluerobotics/ping-cpp#66 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
bluerobotics/ping-cpp#69 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
bluerobotics/ping-cpp#68 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 55/100
bluerobotics/ping-cpp#57 ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
bluerobotics/ping-cpp#54 ·
All issues in bluerobotics/ping-cpp
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
duckdb/duckdb-wasm#2258 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
objectionary/eo-graphs#75 ·
-
Coarray integration tests carry no LABELS, so run_tests.py silently skips them under every backend Opencoarray
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FISCO-BCOS/FISCO-BCOS#5642 ·