The 2.3 degree FoV published for the TFMINI/TFMINI-S dates back to
#24700 without a documented source and does not match the Benewake
datasheet, which specifies 2 degrees. Publish the datasheet value so
collision prevention and MAVLink consumers see an honest envelope.
Add the TFMINI Plus as variant 4. It speaks the same protocol but has
a 3.6 degree FoV and 0.1 m minimum range per the datasheet. Selecting
the TFMINI variant for a Plus made PX4 discard all readings below
0.4 m (signal_quality forced to 0), starving EKF2 of range aiding in
close-range use.
Update the PX4 docs so the model table, reported ranges and
out-of-range behaviour distinguish the two models.
Bench-verified on px4_fmu-v6x with a TFMINI Plus: variant 1 reports
h_fov 0.0349 rad and stamps quality 0 below 0.4 m; variant 4 reports
h_fov 0.0628 rad, keeps quality -1 from 0.11 to 0.30 m and stamps
quality 0 at 0.05 m.
Fixes#29460
Assisted-by: GLM:glm-5.3-flash
Signed-off-by: jiakun <53556221+ddwolf87@users.noreply.github.com>
The page predated the rangefinder page template: it had no specifications,
pinout, firmware support or testing sections, and claimed TFmini-i support,
although the TFmini-i only has RS-485 and CAN interfaces that the tfmini
driver can't read. The page now covers the TFmini-S and TFmini Plus, sourced
from Benewake's current datasheets and manuals and the driver, and the
rangefinder index lists each model.
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Hamish Willee <hamishwillee@gmail.com>
* Add vitepress tree
* Update existing workflows so they dont trigger on changes in the docs path
* Add nojekyll, package.json, LICENCE etc
* Add crowdin docs upload/download scripts
* Add docs flaw checker workflows
* Used docs prefix for docs workflows
* Crowdin obvious fixes
* ci: docs move to self hosted runner
runs on a beefy server for faster builds
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
* ci: don't run build action for docs or ci changes
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
* ci: update runners
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
* Add docs/en
* Add docs assets and scripts
* Fix up editlinks to point to PX4 sources
* Download just the translations that are supported
* Add translation sources for zh, uk, ko
* Update latest tranlsation and uorb graphs
* update vitepress to latest
---------
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
Co-authored-by: Ramon Roche <mrpollo@gmail.com>