CAN Triple Device Manager 1.1.8 — DBC names read like names (device firmware 1.0.1)
Two changes since 1.1.6. Device firmware unchanged at 1.0.1.
DBC signal names import with underscores as spaces
A DBC signal name has to be a C identifier, so an author who means "Engine Speed" is obliged to write Engine_Speed. The underscore is the file format's limitation, not part of the name — and every hand-made channel in this application is spelled with spaces. Imported ones now match: Engine_Speed arrives as Engine Speed.
Runs collapse and the ends are trimmed, so Engine__Speed imports as "Engine Speed" and _Rpm as "Rpm". It is a default, not a rule — the name column in the import dialog is editable, so type the underscore back if you want it. Message names are untouched.
Under the hood, for anyone reading the source: the substitution deliberately does not happen in the parser. A .dbc file refers to its own signals by the underscored name, and a SIG_VALTYPE_ line — which is what marks a signal as a float — is matched against it. Renaming in the parser would leave that line matching nothing, and every float in the file would quietly decode as raw integer bits. So the parser keeps the file's spelling and the substitution sits at the one point where a signal becomes a channel.
The title bar names the version
CAN Triple Device Manager 1.1.8 - Untitled. The version was readable only through Help → About, and "which build is that on?" is the first question about any behaviour worth reporting — so it belongs where it can be read without opening anything, and where a screenshot of a problem carries it for free. The document name, the unsaved marker and the [protected] suffix still follow it.
Install: download CANTripleDeviceManager-1.1.8-Setup_Windows_x64.exe below and run it. Windows x64; the installer carries the Qt runtime, the device firmware image and the ST-Link drivers.