Skip to content

Support mbmap spec 2.1.0, more vendor icons, Russian README - #208

Merged
nobrega8 merged 2 commits into
mainfrom
mbmap-2.1-support
Nov 10, 2026
Merged

nobrega8 merged 2 commits into
mainfrom
mbmap-2.1-support

Conversation

@nobrega8

Copy link
Copy Markdown
Owner

What

  • mbmap 2.1.0
    • identify (FC17/FC43) is read, validated (bad-identify), written back and used by Check device (app and CLI) to compare model and firmware. Registers with a role take priority.
    • read_alone / read_group are validated (bad-read) and honoured by the read planner (poller, Node-RED export).
    • The 2.1 samples in mbmap-library/tests give the errors listed in its expected.json.
  • Vendor icons: fall back to DuckDuckGo/Google favicon services when a vendor site refuses automated requests, as the mbmap site does. This sends the vendor domain to those services.
  • README: new compatible-.mbmap badge; Russian translation (docs/readme/README_RU.md) and language switcher entries.
  • vendor/mbmap-library updated to the latest main.
  • Simulator test: the map used as "no identity registers" now has one, so it uses abb/acs355.

Known limitation

FC17 answers whose run-indicator byte is not 0x00/0xFF are rejected by tokio-modbus, so the check is "unknown" for those devices (e.g. Lovato DMG610). FC43 is complete. Needs a small patch to tokio-modbus to fix.

Not done

The map builder UI has no fields for identify, read_alone or read_group yet (TS types only).

Tests

cargo test, cargo clippy --all-targets -- -D warnings, npm run check and npm test pass.

- identify block (FC17/FC43) read, validated and used by Check device
- read_alone / read_group honoured when planning reads
- favicon service fallback for vendor sites that refuse automated requests
- new compatible-.mbmap badge
- README in Russian
- update mbmap-library to the latest main
@nobrega8
nobrega8 merged commit 6d3321b into main Nov 10, 2026
7 checks passed
@nobrega8
nobrega8 deleted the mbmap-2.1-support branch November 10, 2026 16:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant