We have released RumiCar-lib v0.7.0. The release notes below are also available on GitHub.
PR #8 はマージ済みです。main の最新コミットは 54c2ff3 で、library.properties は 0.7.0、main でも CI はすべて成功しています。v0.7.0 のタグと Release は、下の内容で作れます。書式は過去の Release(英語、v0.5.0 と同じ見出しの構成)に合わせました。
タグ名: v0.7.0
対象ブランチ: main(コミット 54c2ff3)
Release のタイトル:
v0.7.0 — RC_read returns 0–2000 mm again; new RC_setReadLimit()
Release の説明文:
## What's new
- **`RC_read()` no longer cuts readings at 200 mm.** By default it returns 0 .. 2000 mm again, as up to v0.5.0. Readings above 2000 mm, "no target" (about 8190) and low signal quality return `-3`; `-1` (timeout, or no rear sensor for `REAR`) and `-2` (invalid argument) are unchanged.
- **New `RC_setReadLimit()`** — your program decides how far to trust the readings. Call it once in `setup()`, right after `RC_setup()`:
- `RC_setReadLimit(limitMm)` — the same limit for LEFT, CENTER, RIGHT and REAR.
- `RC_setReadLimit(direc, limitMm)` — one sensor only.
- `limitMm` is 1 .. 2000 mm, `0` means no limit, and values outside 0 .. 2000 are clamped. Readings above the limit return `-3` (far). It returns `1`, or `0` for an invalid `direc`.
- Raw readings with `sensorN.readRangeSingleMillimeters()` are not affected.
- `Exercise-3.3` and `Exercise-4.2-Answer` call `RC_setReadLimit(200)` in `setup()` and get exactly the same readings as in v0.6.1, so they drive the same way. Their comments now refer to "the limit set with `RC_setReadLimit()`".
- `AGENTS.md` (Exercise-4.1 / 4.2): `RC_setReadLimit` is added to the API table. New thresholds must be at or below the limit in `setup()`; if the line is missing, the agent adds it and asks the user for the value.
- README: reference for `RC_setReadLimit()` and a new "Choosing the limit" section (recommended example 200 mm — the hands-on text states that the RumiCar model 32 picks up the floor at about 30 cm, so 200 mm leaves a margin — and how to check it on your own car).
- `keywords.txt`: `RC_setReadLimit` is highlighted in the IDE.
## Compatibility
- **If your own sketch uses `RC_read()` and relied on the 200 mm limit of v0.5.1 .. v0.6.1, add `RC_setReadLimit(200);` after `RC_setup()` in `setup()`** to keep the same behavior. Without it, readings up to 2000 mm (including the floor) are returned.
- Sketches that use `sensorN.readRangeSingleMillimeters()` (Exercise-1.1 … 3.2, 4.1, 4.1-Answer, 4.2, `Basic`, `Exercise`) are unchanged.
## Notes
- Background: [RumiCar-Zero2Cam#32](https://github.com/RumiCar-group/RumiCar-Zero2Cam/issues/32) — with the fixed 200 mm limit, all three sensors went out of range and the car could not drive well.
- The same API (same name, same meaning) is coming to the Raspberry Pi `RumiCar.py` 0.7.0, RumiCar-Zero2Cam 0.7.0 and the RumiCar Simulator v12.0.0. Their current versions still limit `RC_read()` to 200 mm.
- Please report problems, and limit values that work on your car, as [Issues](https://github.com/RumiCar-group/RumiCar-lib/issues).
## Dependencies
- VL53L0X (Pololu) — installed automatically by Library Manager.
## Supported platforms
- Arduino AVR, ESP32, Spresense, Raspberry Pi Pico WRelease を作ると、この説明文が rumicar.com の記事として自動で公開されます。そのつもりで、外部の方の Issue #32 へのリンクも含め、公開してよい内容だけにしてあります。日本語の説明文がよければ用意します。
あわせて計画書の第5版(作ったばかりの版)を直しました。7章と、10章(段階2の依頼文)の「決まり」に、「タグや Release を作る段階では、タグ名・対象ブランチ・タイトル・説明文を表示し、次の段階の依頼文にも引き継ぐ」を足しています。表紙の版の欄にもこの変更を書きました。
