CAN Triple Device Manager 1.1.6 — the Source column names what generates a channel (device firmware 1.0.1)
One fix since 1.1.5. Device firmware unchanged at 1.0.1.
A transmit message is not a channel's Source
The Channel Editor's Source column named CAN n · <transmit message> as where a channel comes from. It is where the channel goes: a transmit row reads the value and puts it on the wire. Naming it under "Source" inverted the direction of the column, and for a channel that is only transmitted it also disclosed which message carries it — which this column has no business reporting.
The fix was a deletion. The column had its own walk of the document, a second implementation of a rule the model already owns for Check Channels and the Config Summary — and that one had the direction right all along. The column is now a lookup, so the three views answer in the same words.
Four more disagreements came out with it, each naming as a source something the device never generates:
- a relay's leftover rows, from a section re-typed to Message Relay
- a compound identifier whose ID Mask is 0 — the mapper skips it, so its rows are never decoded
- the output of an inactive calculation
- Off sections, excluded by a second rule of the column's own
A Transmit CRC8's publish channel is still a source. The device computes the checksum and writes that channel on every compose — so "transmit" was never the test; "does the device write it" is.
"not generated" is a new answer, distinct from "unused". Unused means neither generated nor used, and it is exactly the set Check Channels offers to delete — so a channel a transmit message carries must not land in it.
Install: download CANTripleDeviceManager-1.1.6-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.