CORE-01Sheet 1 / 3 · Part 4
Setting comparison record
Change one value at a time. Write your prediction before you change it, then write what you actually saw.
| Item | Record |
|---|---|
| Robot file | ☐ Book-CORE-01-CONTROLS (Robot 1)☐ Book-CORE-01-SCRIPT_PART (Robot 2) |
| Script/Library version | ☐ v1.6.3Other: ________ |
| Controls Mapping checked | ☐ CheckedNote: ____________________ |
| Start position & heading | |
| Screen at start | ☐ Folded☐ Open |
| Parameter tested | ☐ RPM☐ ACCEL☐ BRAKE F☐ BRAKE T☐ Added item STAGGER/RETURN ____ |
| Key used | 2 / 3 / 4 / 0 |
| Current level | LV ___ / 10 |
| Baseline value | |
| Value before | |
| Value after | |
| Prediction | |
| What you observed | |
| Failure or odd behavior | |
| One thing to change next | |
| Baseline back after Reset All (0, or fold with 1) | ☐ Yes☐ No |
Motor baseline record Appendix I · Table C01-I01-B
| Run | RPM | ACCEL | BRAKE F | BRAKE T | TORQUE (fixed) | Note |
|---|---|---|---|---|---|---|
| Robot file values | SETUP Motor (robot file) · Motor (fixed) | |||||
| Values the script applied | SETUP Motor (script) · only when different |
Copy the numbers from the Console SETUP lines of that run. TORQUE is a fixed value the script never changes.
CORE-01Sheet 2 / 3 · Part 5
Mission check form
For each step, write the time you set next to the motion you actually saw. If a step fails, stop at that row and pick one cause.
| Step | Action/State | Set time (s) | Observed | Done/Failed | Note |
|---|---|---|---|---|---|
| 1 | |||||
| 2 | |||||
| 3 | |||||
| 4 | |||||
| 5 | |||||
| 6 | |||||
| GUIDE | Screen guide | ||||
| RETURN | Return |
Use rows 4–6 if the route has more than three steps.
| Guide message | |
|---|---|
| Gap between start and return positions |
Whole-mission check
| Check | Result |
|---|---|
| 1. Recorded the start position? | ☐ Yes ☐ No |
| 2. Did the route run without breaks? | ☐ Yes ☐ No |
| 3. Did the screen open at the guide point? | ☐ Yes ☐ No |
| 4. Was the guide message visible? | ☐ Yes ☐ No |
| 5. Did the screen fold after guiding? | ☐ Yes ☐ No |
| 6. Did RETURN run? | ☐ Yes ☐ No |
| 7. Recorded the gap between start and return? | ☐ Yes ☐ No |
| 8. Picked the single biggest cause of failure? | ☐ Yes ☐ No |
| 9. Changed only one condition? | ☐ Yes ☐ No |
| 10. Recorded the re-run result? | ☐ Yes ☐ No |
CORE-01Sheet 3 / 3 · Web only
Challenge mission record
For challenges 1–3 on the web companion page. No solution code is provided; the concepts are in the chapters indicated.
Challenge 1 · Guide to a different place CH22 · CH23
| Step | Action | Time (s) | Observed |
|---|---|---|---|
| 1 | |||
| 2 | |||
| 3 | |||
| 4 | |||
| 5 | |||
| 6 |
Rule: at least four steps, at least one pause · Actions: forward · backward · turn_left · turn_right · rotate_left · rotate_right · pause
Challenge 2 · Back to the same spot three times CH24 · CH25
| The one value changed | Before: | After: |
|---|
| Run | Before · return-position gap | After · return-position gap |
|---|---|---|
| 1 | ||
| 2 | ||
| 3 | ||
| Average |
Also look at how much the three gaps vary.
Challenge 3 · A guide message readable at a glance CH21
Text Screen draft — 9 cells × 4 lines. One character per cell.
| Why this wording |
|---|
| ☐ Checked with a real screen capture |