Packages and updates
Install protocol and adapter components in Settings → Packages. The relationship between installed components and entitlements is described under license and access.
Required components
| Task | Components |
|---|---|
| Modbus RTU | Modbus; the serial transport is included in the core application |
| CANopen | CANopen and the selected CAN adapter package |
| Automotive VAG | VAG, its Automotive tools dependency and a CAN adapter package |
| CANable | CANable |
| WeAct | WeAct |
| J2534 adapter | J2534, including DriverBridge; install the manufacturer's driver separately |
| Lawicel or HEX-USB+CAN adapter | FTDI adapters |
| UCCB | UCCB |
| MCP client | McpBridge is included in the core application |
Installation and maintenance
- Find the component and click
Install. - If dependencies are required, review the proposed list and confirm their installation.
- Wait for completion and restart Protohaund when prompted.
Installed components show their versions. Package update status and the core application version are separate: package versions may differ from each other.
The Management menu offers Check updates, Repair all and Uninstall all. Individual packages also offer Uninstall. Removing a component may make its module or transport unavailable. A restart indicator means file changes have not yet been applied to the running instance.
Startup updates
After startup, Protohaund checks for application and module updates and presents a combined Update available dialog. It lists components and versions; when the installed version is known, it shows the transition to the new version.
Updateinstalls the proposed updates.Not nowdefers the proposed versions; manual checking remains available inPackages.
Module-only updates prompt for a restart after installation. A core application update launches the installer and closes Protohaund. Save important traces before updating.