A familiar scene
A lab runs a HIL regression for an ECU. LabVIEW drives the simulator. Vector CANoe records the CAN traffic. A Python script merges the outputs into a report. The engineer who wrote the Python script left six months ago.
The lab has three strong tools. It does not have a traceable handoff between any of them.
For public reference, Vector documents CANoe test reporting options in its CANoe test report FAQ, while NI documents TestStand XML and ATML reporting in TestStand XML Reports. Those references are useful for naming the artifacts. The workflow question is whether the right LabVIEW version, CANoe configuration, DBC version, script commit, and report all point back to the same run.
What gets lost at each boundary
LabVIEW → Vector CANoe
- The LabVIEW VI version is not recorded with the CAN trace.
- The timing alignment between VI steps and CAN frames is implicit.
- If the VI parameter set changes, nobody knows which CAN trace belongs to which VI configuration.
Vector CANoe → report
- The CANoe configuration file version (
.cfg) is not captured. - The DBC database version used to decode CAN messages is not logged.
- If the report looks suspicious, the reviewer cannot trace back to the source data without the original engineer.
LabVIEW → report
- The test sequence steps are not linked to the CAN trace segments.
- A pass/fail in the report does not reference which VI produced it.
Why buying another tool doesn’t fix this
A new tool would have its own configuration files, its own version assumptions, and its own output formats. The handoff gaps would move into the new toolchain – possibly with less institutional knowledge about how to work around them.
What to do instead
Pick one LabVIEW VI and one CANoe trace that belong to the same run. Ask:
- Can someone who did not run the test match the VI version to the CAN trace?
- Can they reproduce the report without calling the original engineer?
- Is the CANoe config file version recoverable from the evidence?
If the answer to any of these is no, the handoff is a gap worth mapping.
Use the diagnostic kit to document the toolchain handoff for one workflow. The template takes 30 minutes. It does not require replacing anything – only making the current handoff visible.
Understand why the handoff between LabVIEW and Vector CANoe loses test workflow context.