io.github.mushitaro由 GitHub 帳號 mushitaro 發布v0.4.0更新於 Oct 30, 2026
BMW E46 M3 DME and SMG II: VE and rf_korr from Testo logs, decode SMG calibrations. Local.
讀取 BMW E46 M3 的 MSS54HP DME 映像、行駛日誌與 SMG II 變速箱映像，提供 VE/rf_korr 調校建議並解碼標定資料。
Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.github.mushitaro%2Fmatrix-tsunagi-mapping/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"tsunagi-matrix-mapping": {
"type": "http",
"url": "https://matrix-mcp.tsunagi.app/mcp/mapping"
}
}
}The calculations behind TSUNAGI's BMW E46 M3 tools, as a library, a command line and MCP servers. Read an MSS54HP DME image and a drive log, and get the VE map correction the drive supports. Read an SMG II gearbox image, and decode and compare its calibration. Read a DME backup or a cluster EEPROM backup, and check what it holds. On your own machine, with no car and no cable.
--sample runs on the practice files shipped in the package. Replace it with --bin <file.bin> --log <file.csv> for your own.
Installing it for an AI assistant (Claude, ChatGPT and others): see INSTALL.md. It is written so that you can hand this repository to the assistant and it installs what fits its client.
TSUNAGI///M is TSUNAGI's family of tools for the E46 M3 (S54 engine, MSS54HP DME, SMG II). Owners meet the tools on m3.tsunagi.app; AI assistants meet them here. TSUNAGI///Matrix is the family's gate for AI assistants: it computes nothing of its own, and carries each tool's own code to the assistant, one category at a time. This package carries two categories. MAPPING: MSS54HP CSL CONVERT /// TUNER and E46M3SMG2 /// MAPPING. MIGRATION: it reads the backups of MSS54HP CSL CONVERT /// BOOT and E46 M35080 /// MIGRATION, and only reads them.
How do I correct the VE (alpha-N) map of my CSL-converted MSS54HP from a Testo log?
Which cells change and by how much, which need more driving and how to drive them, and — with --out — the
tuned BIN with its checksums corrected. That file is byte-for-byte what TUNER's DOWNLOAD TUNED gives for the same two files.
What is in my MSS54HP bin? Are its checksums right? Which patches are on it?
Why did most of my log get thrown away?
Every reason a sample was left out (cold engine, transient, full load, overrun…), each with what to change on the next drive.
What rf_korr table does my drive support? (experimental)
The exhaust-temperature density correction (KF_RF_KORR_DRREL), cell by cell, with the evidence behind each.
What are my SMG II shift points? What is this SMG image?
smg2 image needs nothing else: it says whether the image is the 24 KiB calibration window or the full 512 KiB flash, and gives the ZB number and whether the CRC checksums hold.
smg2 read decodes every item the MS4X definition names, through E46M3SMG2 /// MAPPING's corrections to it. That includes shift speed thresholds per gear and program, gear ratios, and clutch and launch settings.
The definition (Siemens_SMG_II_510_24K.xdf or _512K.xdf) is the MS4X Dev Team's and is not shipped here, so pass your own.
The WORKS build of E46M3SMG2 /// MAPPING carries it.
What changed between two SMG II calibrations?
Which bootloader is in my DME backup, and what is left of the CSL conversion?
From BOOT's full 1 MiB backup: standard M3 or CSL bootloader on each processor, whether each bootloader CRC holds, the program number, and the stages left.
migration boot compare a.bin b.bin names where two backups differ.
What mileage does this cluster EEPROM hold? Is the dump even a real read?
From a 1 KB M35080 backup: whether it is a real chip read (a dead or shorted bus reads as one repeated byte), the mileage in the secure counter, the layout and checksums, and whether the VIN copies agree.
migration m35080 compare a.bin b.bin shows which area changed between two dumps.
MIGRATION only reads. The functions that would change an image are not in this package, and npm run verify checks the bundle for them.
The VIN and the DME's identity record are never printed, because what a command prints goes into the conversation with the assistant.
What can it do?
npx matrix-tsunagi describe once. Every command prints JSON on stdout, and errors come as JSON on stderr with exit code 1.summary to relay, result with the numbers, and source, which says which tool and version computed it and whether the calculation is experimental.apply appears only when the owner would have to write the result to the car. It names the app, says whether the app is free or WORKS, and says how. apply.how and source.note are in English and Japanese.--sample to show the command working on the practice BIN and drive.plugin/ is the Claude plugin, one package for both parts. The public part runs the MAPPING and MIGRATION servers on this computer (Claude Code), with the matrix-public Skill. The WORKS part is the TUNER WORKS connector (bridge/, sign-in on m3) with the tuner-drive Skill, so an owner can talk to TUNER WORKS while it logs the car, from the phone too. It can stage a calibration change, save the session and sync it with the owner's cloud, each after the owner says yes; connecting to the car and writing to it stay with the owner, on the screen. The Skills are only the way in: the procedures come from the servers (about_matrix's howToUse, tuner_guide), so they update with the tools without a new plugin, and the plugin runs the newest matrix-tsunagi on npm. How to install it is in INSTALL.md.
There are two servers, one per category.
The MAPPING server exposes the same calculations as tools. For TUNER: read_bin, read_log, propose_ve and propose_rfkorr. For SMG2: smg2_image, smg2_read and smg2_compare. And about_matrix. It runs locally over stdio.
The MIGRATION server (npx -y matrix-tsunagi mcp migration, or npx -y matrix-tsunagi-migration) exposes boot_backup, boot_compare, m35080_read, m35080_compare and about_matrix, all read-only.
Claude Code:
Claude Desktop (claude_desktop_config.json):
On Windows, if npx is not found, use "command": "cmd" with "args": ["/c", "npx", "-y", "matrix-tsunagi", "mcp", "mapping"].
For assistants that cannot run npm, the MAPPING server also runs remotely:
In ChatGPT, turn on Developer mode (Settings → Security and login), then add it as a plugin by that URL. Attach your BIN and log in the chat and ask. Files reach the server as ChatGPT file parameters: it downloads them from the temporary link ChatGPT issues, computes in memory, returns the result, and keeps nothing. It returns values only, so make the tuned BIN with the free TUNER, and it is MAPPING only, because MIGRATION's dumps carry a VIN and a mileage and stay on your machine. How it handles files is set out in section 11 of the privacy policy.
mapping.readBin, mapping.readLog and mapping.proposeRfKorr take the same inputs. For SMG2 there are mapping.smg2Image({ image }), mapping.smg2Read({ image, xdf, item }) and mapping.smg2Compare({ image, other, xdf }), where xdf is the definition's text.
The calculations are free. Writing a result to the car is done in the apps.
The WORKS builds are for people who have bought MILE on MESH, and for owners of cars TSUNAGI has worked on, on request. They are TUNER's experimental features, E46M3SMG2 /// MAPPING, E46M3 /// MONITORING, MSS54HP CSL CONVERT /// BOOT and E46 M35080 /// MIGRATION. MILE is a one-time payment, with no subscription and no renewal. A purchaser can allocate MILE to a MILESTONE to say what they would like it spent on. That is a wish on record, not a promise of any release or date.
Siemens_SMG_II_510_24K.xdf for a window or _512K.xdf for a full read. The other variant is refused rather than read at the wrong offset.This package does not re-implement anything. It bundles each tool's own code from its public repository, at the commit its submodule is pinned to:
mushitaro/mss54hp-csl-convert-tuner (vendor/tuner) and
mushitaro/e46m3smg2-mapping (vendor/smg2),
mushitaro/mss54hp-csl-convert-boot (vendor/boot) and
mushitaro/e46-m35080-migration (vendor/m35080).
Every result names the tool, version and commit in source.
npm run verify holds the tuned BIN to a SHA-256 measured from TUNER's own DOWNLOAD TUNED, read out of that same commit.
It holds SMG2's decoding to the app's own loadDefinition, item by item.
Each has a control that shows the comparison can fail.
The SMG2 check needs the MS4X definitions and a car's image, which are not public. Without them it reports SKIP, which is not a pass.
TSUNAGI///M（BMW E46 M3 のツール群）の計算を、ライブラリ・コマンド・MCP で使えるようにしたパッケージです。
TSUNAGI///Matrix は、M のツールを AI アシスタントにつなぐ門です。自分では計算せず、各ツールのコードをカテゴリごとに束ねて渡します。
MSS54HP の BIN と走行ログ（Testo の CSV）から、VE マップの補正案、ログのどこが使われなかったかとその直し方、rf_korr の表（試験中）を出します。
SMG II の画像からは、ZB 番号とチェックサム、較正の解読（変速点など）、2 本の比較を出します。解読には、お手持ちの MS4X の XDF が要ります。
MIGRATION は、DME のバックアップ（ブートローダの種類と CRC、CSL 化の残り）と、メーターの M35080 のバックアップ（走行距離、チェックサム、VIN の一致）を読むだけで、書き換えはしません。VIN と DME の識別情報は出力しません。
お手元の PC で計算し、どこにも送信しません。ファイルがなくても --sample で試せます。
VE マップは MSS54HP CSL CONVERT /// TUNER（無料・ブラウザで動作）で車に書き込めます。 rf_korr などの試験中の機能は、TUNER のワークス版でファイルにして書き込みます。 SMG II の車からの読み取り・編集・書き出しは、E46M3SMG2 /// MAPPING のワークス版で行えます。ワークス版には XDF も入っています。 ワークス版は、MESH で MILE をご購入いただいた方と、お申し出いただいた施工オーナーさんがお使いいただけます。 MILE は一回限りのお支払いで、自動更新はありません。 MILESTONE への割り当ては使い道のご希望の表示で、公開や時期を約束するものではありません。
MIT, © TSUNAGI. See THIRD-PARTY-NOTICES.md for what is bundled, including the practice BIN.
來源：README.md，提交 d4aab7f
About TSUNAGI///Matrix
What TSUNAGI///Matrix is (BMW E46 M3 / S54 / MSS54HP / SMG II tools), which commands exist, which app puts a result on the car, how the WORKS builds and MILE on MESH work, and how to go about these tools (howToUse, the current procedure). Call this first, and before recommending the apps.
無需輸入參數。
Read an MSS54HP DME image
BMW E46 M3 (S54) MSS54HP DME, CSL conversion: read a 64 KB calibration partial and report the checksums, the logic patches (MAP, TANK VENT, WOT TH, RF GATE), how far the VE (alpha-N) and warm-up tables are from stock, and the VE table.
bin_pathuse_sampleRead an MSS54HP drive log
BMW E46 M3 (S54) MSS54HP: read a drive log (Testo CSV, or TUNER's own CSV) and report its channels, how many rows the VE and rf_korr calculations can use, and why the rest were left out — each reason with what to change on the next drive. Pass the BIN it was driven on for the DME's own lambda thresholds.
bin_pathlog_pathuse_sampleVE map correction from a drive
BMW E46 M3 (S54) MSS54HP, CSL conversion tuning: from a DME image and a drive log, the VE (alpha-N) map the drive supports — which cells change and by how much, which need more driving and how. With out_path, also saves the tuned BIN (checksums corrected), byte-for-byte what MSS54HP CSL CONVERT /// TUNER's DOWNLOAD TUNED produces.
bin_pathlog_pathout_pathuse_samplerf_korr table from a drive (experimental)
BMW E46 M3 (S54) MSS54HP: from a DME image and a drive log with exhaust temperature, the rf_korr table (KF_RF_KORR_DRREL, exhaust-temperature density correction) the drive supports, with the evidence per cell. Experimental in the app; returns values only — the WORKS build of TUNER makes the file and writes it.
bin_pathlog_pathuse_sampleIdentify an SMG II image
BMW E46 M3 SMG II (Siemens SMG2 510, the sequential gearbox ECU): say what an image is — the 24 KiB calibration window or the full 512 KiB flash — its ZB number, and whether its CRC checksums hold. Needs no definition.
image_pathuse_sampleDecode an SMG II calibration
BMW E46 M3 SMG II (Siemens SMG2 510): decode the calibration — shift speed thresholds per gear and program (AUTO, SPORT/RACE, Drivelogic), gear ratios, clutch and launch settings — through the MS4X definition with E46M3SMG2 /// MAPPING's corrections. Pass item for one item's full table and axes.
itemxdf_path必填image_pathCompare two SMG II calibrations
BMW E46 M3 SMG II (Siemens SMG2 510): which calibration items differ between two images of the same scope, how many cells, and the largest difference in physical units.
xdf_path必填image_path必填other_path必填已滿足適用檢查項的 100%
該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。
npx matrix-tsunagi mapping ve --samplenpx matrix-tsunagi mapping ve --bin my.bin --log drive.csv --out tuned.binnpx matrix-tsunagi mapping bin my.binnpx matrix-tsunagi mapping log drive.csv --bin my.binnpx matrix-tsunagi mapping rfkorr --bin my.bin --log drive.csvnpx matrix-tsunagi mapping smg2 image smg.binnpx matrix-tsunagi mapping smg2 read smg.bin --xdf Siemens_SMG_II_510_512K.xdf --item "A1 Speed"npx matrix-tsunagi mapping smg2 compare before.bin after.bin --xdf Siemens_SMG_II_510_512K.xdfnpx matrix-tsunagi migration boot backup dme-backup.binnpx matrix-tsunagi migration m35080 read eeprom.binnpx matrix-tsunagi describeclaude mcp add matrix-tsunagi-mapping -- npx -y matrix-tsunagi mcp mapping{ "mcpServers": { "matrix-tsunagi-mapping": { "command": "npx", "args": ["-y", "matrix-tsunagi", "mcp", "mapping"] } }}https://matrix-mcp.tsunagi.app/mcp/mappingimport { mapping } from 'matrix-tsunagi';import fs from 'node:fs';
const ve = mapping.proposeVe({ bin: new Uint8Array(fs.readFileSync('my.bin')), csv: fs.readFileSync('drive.csv', 'utf8'),});console.log(ve.summary);fs.writeFileSync('tuned.bin', ve.tunedBin);git clone --recursive https://github.com/mushitaro/matrix-tsunagicd matrix-tsunagi && npm install && npm run verify