Skip to content

Application and tool settings ​

Open Settings in the main window. The following sections apply to beta testers. Control names match the application interface.

SectionPurpose
AccountSign-in, activation, license expiry and autonomous use
Application → ProfileSelect a profile and module
Application → StartupAutomatic connection and active serial port scanning
Application → PersonalizationTheme and accent color
Connections → TransportCommunication source and connection parameters
Connections → Driver Bridge32-bit J2534 driver bridge, when the component is installed
TracerImport folder and quick-label shortcut
MonitorData change highlighting
PackagesInstall, repair and update components
MCP ServerAgent permissions and McpBridge control
LoggingTechnical log file and recent events

Without a valid license, some settings are hidden; account, appearance and logging remain available. A group containing only one page may display that page without an intermediate group node.

Startup ​

Automatic connection on start-up allows connecting at startup with saved parameters. Check the selected module, port and speed before enabling it.

Active adapter detection ​

Active serial port scanning in Settings → Application → Startup enables automatic identification of CANable, WeAct and UCCB adapters through serial ports. It makes available adapters easier to find at startup and when you click Rescan in transport settings.

Possible unwanted traffic

Active detection opens ports and sends data to connected devices. Depending on the device, this data may reach the bus and generate unwanted traffic. This can happen as soon as the application starts, before you connect to the line in the application, and when you click Rescan.

If additional traffic is unacceptable, disable Active serial port scanning before starting the application with an adapter attached to the working bus. If necessary, disconnect the adapter from the bus first, start the application, and change the setting. Disabling it stops automatic identification of CANable, WeAct and UCCB adapters. The setting applies to the next scan; disabling it does not turn off automatic connection or other operations that send data.

Appearance ​

Theme selects Auto, Dark or Light. Auto follows the Windows theme. Use system accent color follows the system accent; disable it to select a custom color.

Tracer ​

  • Remember last import folder remembers the folder used for loading traces.
  • Capture → Quick label shortcut selects a quick-label key with the required Ctrl modifier. The default is Ctrl+L.

The details panel position, size and pin state, CAN column widths and filter expressions are saved while using Tracer. These are display preferences, not adapter settings.

Monitor ​

Dynamic highlight controls how data changes are displayed:

SettingEffect
EnabledEnables dynamic highlighting
Stale after, sTime since the last value change until its highlight fully fades, from 5 to 60 seconds
Stale data opacityOpacity of an unchanged value, from 0 to 1
Outdated after, sTime since the last data observation until the row fully fades, from 5 to 60 seconds
Outdated data opacityOpacity of an outdated row, from 0 to 1

Stale means a value has not changed recently: repeated identical data remains current. Outdated means no new data has been observed within the selected interval. It indicates age, not a data error. Observing data again restores the row's opacity, but an identical value does not restart the change highlight.

Highlighting is enabled by default, with both intervals set to 5 seconds. The intervals are independent and fading is gradual. Settings apply immediately to CAN and Modbus, are saved, and do not change the communication rate or device polling period. When loading older settings, the previous shared interval is used for both effects with a minimum of 5 seconds; a previous zero value keeps highlighting disabled.

For logs and issue reports, see diagnostics and support.

Protohaund is independent software and is not affiliated with, endorsed by, sponsored by, or certified by any third-party organization referenced in the application.Third-party names, trademarks, product names, device names, protocol names, and standards are referenced solely to identify vehicle applicability, supported products, technologies, protocols, formats, or compatibility.All third-party trademarks and other marks are the property of their respective owners. Their use does not imply any affiliation with, endorsement of, certification of, or approval of Protohaund by their respective owners.Compatibility is limited to the features, devices, protocols, standards, and versions explicitly documented by Protohaund.