ARXplorer

轻量级 AUTOSAR ARXML 浏览器 —— 在 VS Code 里直接浏览 ECU 配置，无需为读一个文件去打开 DaVinci Configurator。 A lightweight AUTOSAR ARXML browser — explore ECU configuration directly inside VS Code, without opening DaVinci Configurator just to read a file.

它能做什么 What It Does

• 语义树 —— 以 AUTOSAR 对象模型（包、SWC、端口、ECUC 模块/容器/参数）浏览 ARXML，而不是看原始 XML。结构的包装层自动折叠，树与对象图一致，读起来直观。 Semantic tree — Browse ARXML by the AUTOSAR object model (packages, SWCs, ports, ECUC modules/containers/parameters) instead of raw XML. Wrapper layers of the structure fold away automatically, so the tree matches the object graph and reads intuitively.
• 原始 XML 视图 —— 需要时切换到字面标签层级。 Raw XML view — Switch to the literal tag hierarchy when needed.
• 跳转源码 —— 点击任意节点，跳到它在编辑器里 SHORT-NAME 所在的位置。 Jump to source — Click any node to jump to its SHORT-NAME location in the editor.
• 项目索引 —— 加载 DaVinci .dpa，索引整个工程，回答跨文件的问题。 Project index — Load a DaVinci .dpa, index the whole project, and answer cross-file questions.
• 反向引用 —— 选中任意元素，查看整个项目里都有谁指向它。这是单文件树回答不了的查询。 Reverse references — Select any element and see everything in the project that points to it. This is a query a single-file tree cannot answer.
• ECUC 模块配置页 —— 加载项目后，以配置页形式打开任意 BSW 模块（CanIf、Com、Os……）：它的容器、实例，以及每个实例的参数和引用。当前只读，是未来编辑器的雏形。树按层加载，几万节点的模块也能立即打开、不卡顿。 ECUC module configuration page — After loading a project, open any BSW module (CanIf, Com, Os…) as a configuration page: its containers, instances, and each instance's parameters and references. Read-only for now, a precursor to a future editor. The tree loads per level, so even modules with tens of thousands of nodes open instantly without stalling.
• 宽组的表格视图 —— 实例数量很多的组会提供 Table 按钮，把所有实例按参数铺成行列，方便横向对比；多值参数会在单元格里保留全部取值。 Table view for wide groups — Groups with many instances offer a Table button that lays every instance out in rows and columns for side-by-side comparison; multi-valued parameters keep all their values in a cell.
• 展平列表 —— 顶部工具栏可一键把所有容器展平为一个列表，快速扫完整个模块有哪些容器。 Flat list — The top toolbar can flatten every container into a single list, letting you quickly scan which containers a module has.
• 配置搜索 —— 按名称、容器名、参数值搜索；点结果即可进入详情。 Configuration search — Search by name, container, or parameter value; click a result to enter its detail.

快速开始 Quick Start

1. 命令面板运行 ARXplorer: Load Project Index (.dpa)，选择工程描述文件，索引整个工程。 Run ARXplorer: Load Project Index (.dpa) from the command palette, pick the project description file, and index the whole project.
2. 在侧边栏模块列表里选一个 BSW 模块，打开其配置页。 Select a BSW module from the sidebar module list and open its configuration page.
3. 在树里逐层展开容器与实例；点实例查看它的全部参数与嵌套容器。 Expand containers and instances layer by layer in the tree; click an instance to see all its parameters and nested containers.
4. 用顶部搜索框按名称/值搜索，点结果进入对应配置详情。 Use the search box to search by name/value, then click a result to open the corresponding configuration detail.
5. 要横向对比多行数据时，点组标题旁的 Table 用表格查看。 To compare many rows side by side, click Table next to a group title.

命令 Commands

设置 Settings

版本对比 Basic vs Pro

ARXplorer 分 基础版（Basic，缺省、无需授权）与 高级版（Pro，需 License Key 激活）。基础版覆盖日常浏览；达到上限的功能会提示升级，激活后自动放开。

ARXplorer is available in two editions: Basic (default, free to use) and Pro (requires a License Key). Basic covers day-to-day browsing; features that hit a cap prompt you to upgrade, and a Pro license lifts those caps automatically.

节点上限 对应 arxplorer.parser.maxNodes（单文件）与 arxplorer.index.maxNodes（整个工程）。文件/工程超过基础版上限时，会显示提示并保留一个可持续可见的「已截断」标记；激活 Pro 并重新加载后即可索引完整内容。

Node caps map to arxplorer.parser.maxNodes (single file) and arxplorer.index.maxNodes (whole project). When a file/project exceeds the Basic cap, ARXplorer shows a prompt and keeps a persistent "truncated" marker; activating Pro and reloading indexes the full content.

提示：上限提示由实际生效的配置变量驱动。你在设置里调低 arxplorer.index.maxNodes，提示中的数字会随之变化。 Note: the cap shown in prompts is driven by the effective configuration variable. Lower arxplorer.index.maxNodes in settings and the number in the prompt follows.

提示：上限提示由实际生效的配置变量驱动。你在设置里调低 arxplorer.index.maxNodes，提示中的数字会随之变化。 Note: the cap shown in prompts is driven by the effective configuration variable. Lower arxplorer.index.maxNodes in settings and the number in the prompt follows.

License 使用方式 How to Activate Pro

License 绑定到「机器指纹」（Windows 使用注册表 MachineGuid，macOS 使用 IOPlatformUUID，Linux 使用 /etc/machine-id），因此一个 Key 只能用于一台机器；把 Key 复制到别的机器会失效。

The Pro license is bound to a machine fingerprint (Windows registry MachineGuid, macOS IOPlatformUUID, Linux /etc/machine-id), so a Key works on one machine only; copying it to another machine won't validate.

激活步骤 Activation steps

1. 命令面板运行 ARXplorer: Show Activation Code。 Run ARXplorer: Show Activation Code from the command palette.
2. 插件把你的激活码（Activation Code）与机器码（Machine ID）复制到剪贴板，并弹出 License 获取页面入口。 The extension copies your Activation Code and Machine ID to the clipboard and offers the license page.
3. 将激活码与机器码发送给授权方，换取该机器的 License Key（形如 ARXP-XXXXXXXX）。 Send the Activation Code and Machine ID to your license provider to get a License Key for that machine (of the form ARXP-XXXXXXXX).
4. 命令面板运行 ARXplorer: Enter License Key，粘贴 Key 完成激活。 Run ARXplorer: Enter License Key and paste the Key to finish activation.
5. 激活成功后，License 保存在 ~/.ARXplorer/license.json，下次启动自动校验，无需重复输入。 On success the license is stored at ~/.ARXplorer/license.json and validated automatically on next launch.

在受限制的功能（如导出表格、超大文件/工程）触发时，插件也会弹出提示，可直接从提示进入「获取激活码 / 输 Key」流程。

When a restricted feature (e.g. export table, oversized file/project) is triggered, the extension also shows a prompt that leads straight into the "Get Activation Code / Enter License Key" flow.

激活「工程索引」后需重新加载工程（再次运行 ARXplorer: Load Project Index），上限才会按高级版放开。 After activating, reload the project (run ARXplorer: Load Project Index again) for the Pro cap to take effect on the project index.

用法提示 Usage Tips

• 界面语言自动适配 —— 界面文案（按键、提示、空态等）会跟随 VSCode 界面语言自动在中文和英文间切换；把鼠标悬停在展开箭头等关键控件上可看到功能说明。 Interface language adapts automatically — The UI text (buttons, tooltips, empty states, etc.) switches between Chinese and English automatically to follow the VS Code interface language; hover over key controls such as the expand arrow to see a tooltip explaining what they do.
• 搜索是入口，不是终点 —— 搜到结果后点进去，即可在搜索流程内看到该容器/实例的完整配置与兄弟参数，无需回到树里手动找。 Search is an entry point, not the destination — After finding a result, click into it to see that container/instance's full configuration and sibling parameters within the search flow, without going back to the tree to find them manually.
• 宽组用表格、整模块用展平列表 —— 实例很少的组用树浏览最自然；实例很多的组用 Table 对比最省事；想扫全模块的容器名用顶部 Flat list。 Tables for wide groups, flat lists for whole modules — Groups with few instances are most natural to browse as a tree; groups with many instances are best compared with Table; to scan a module's container names, use the Flat list at the top.
• 跳源码 —— 配置上的跳转按钮（↗）直接把对应行定位到源文件。 Jump to source — The jump button (↗) on a configuration row locates the corresponding line directly in the source file.

关于 ARXML 解析 About ARXML Parsing

• AR-PATH 由 SHORT-NAME 链构建，而非 XML 标签链。 AR-PATHs are built from the SHORT-NAME chain, not the XML tag chain.
• 引用在全部文件索引完成后统一解析，因为 ARXML 文件之间会双向引用；目标按多种写法匹配，最具体的路径胜出。 References are resolved only after the whole set of files is indexed, because ARXML files reference each other in both directions; targets are matched against several spelling variants and the most specific path wins.
• ECUC 参数节点以其 DEFINITION-REF 的叶节点为键，因为参数本身没有 SHORT-NAME。 ECUC parameter nodes are keyed by the leaf of their DEFINITION-REF, because a parameter has no SHORT-NAME of its own.