# RasRobot — TB6612FNG 4WD robot local authority asset

Purpose: prepare a clean, useful technical resource for a Robot Maker thread about a 4WD Linorobot2 robot using Raspberry Pi 4, Raspberry Pi Pico and TB6612FNG motor drivers, without forcing an opportunistic link.

## Verified targets — 2026-06-19

Live checks from this run:

- `https://rasrobot.com/controler-moteur-dc-raspberry-pi-l298n/` — HTTP 200
- `https://rasrobot.com/construire-premier-robot-diy/` — HTTP 200
- `https://rasrobot.com/gpio-i2c-spi-uart-raspberry-pi/` — HTTP 200
- `https://www.robot-maker.com/forum/topic/14861-avis-schema-robot-4wd-sous-linorobot2-pico-rpi-4-tb6612fng/` — HTTP 200
- `https://learn.sparkfun.com/tutorials/tb6612fng-hookup-guide/all` — HTTP 200

## Why this asset exists

The forum thread is about TB6612FNG, not L298N. The safe authority angle is therefore not “drop a RasRobot L298N link”. The useful first move is to provide a motor-debug checklist that stands on its own:

1. validate motor power separately from Raspberry Pi power;
2. enforce common ground between logic, driver and motor supply;
3. keep `STBY` controlled and not floating;
4. test one channel and one motor before a full 4WD chassis;
5. check stall current before assuming the issue is ROS, micro-ROS or code.

RasRobot L298N content is useful only as background on DC motor debugging principles; this repository is the TB6612FNG-specific checklist.

## Files in this local asset

- `README.md` — French overview and source list.
- `README.en.md` — English/bilingual repo-style overview for future GitHub/resource-list use.
- `schema-tb6612fng-4wd.md` — wiring logic and checklist.
- `test_moteurs_tb6612fng.py` — minimal `gpiozero` test snippet.
- `LICENSE` — MIT for code, CC BY 4.0 intent for docs/diagrams.
- `CONTRIBUTING.md` — local contribution/PR etiquette guardrails for a future public micro-repo.
- `PR-awesome-raspberry-pi-checklist.md` — local README-line and PR checklist for `thibmaek/awesome-raspberry-pi`; **NO-GO until a public English/bilingual asset exists and William validates the visible GitHub action**.
- `PR-awesome-raspberry-pi-draft.md` — final local PR title/body draft for `thibmaek/awesome-raspberry-pi`; **not submitted, no fork/branch/PR created**.
- `RELEASE-MANIFEST-2026-06-20.md` — local file-size/SHA-256 manifest and live-check evidence for review before any public exposure.
- `NINJA-LINKING-METHOD-2026-06-20.md` — concrete prospecting and no-link-first method requested by William; includes 2026-06-20 live checks and GO/NO-GO boundaries.
- `validate_robotmaker_reply_preflight.py` — read-only gate before any Robot Maker no-link-first reply; verifies the live thread, support URLs, approval status and local note markers.
- `ROBOTMAKER-REPLY-PREFLIGHT-RUNBOOK-2026-06-20.md` — mandatory command/output/GO-NO-GO runbook for the future forum reply validation.

## License

- Code snippets: MIT License.
- Documentation, diagrams and explanatory text: CC BY 4.0 attribution intent.
- Attribution suggestion: “RasRobot / DAVLYRS — TB6612FNG 4WD examples”.

## No-link-first draft answer

> I would validate the power and motor chain before debugging ROS or micro-ROS. On a 4WD robot the symptom can look like a software/control problem while the real issue is a motor current spike, missing common ground, or a standby pin left floating.
>
> My checklist would be:
>
> 1. Raspberry Pi / Pico logic ground, TB6612FNG ground and motor supply ground are common;
> 2. the Pi 4 is not powered from the same rail that absorbs motor startup spikes unless the buck converter and filtering are clearly sized for it;
> 3. `STBY` is tied to a known state;
> 4. one motor is tested on channel A at low PWM, forward and reverse;
> 5. one motor is tested on channel B the same way;
> 6. only then should two motors per side be connected, after checking stall current.
>
> This keeps the first answer useful even without any link. If a link is later approved, it should be positioned as background on DC motor debugging principles, not as a direct TB6612FNG replacement guide.

## Publication status

This repository is the public English-first version of the RasRobot TB6612FNG 4WD checklist. It is provided as a standalone technical reference; no forum reply or external PR is implied by this publication.