Skip to content

Safety & Best Practices

Data injection directly influences ECU behavior. Treat it as a controlled test activity, not a casual feature. This guide explains how to plan, execute, and document injection in the current UI so results are safe, repeatable, and defensible.

Why Injection Requires Extra Care

Injected signals can override real inputs or recorded data. That means the system can behave differently than expected, especially if an ECU interprets a signal as a fault or a critical state. Even in a bench setup, unexpected behavior can damage hardware, corrupt test results, or hide real issues. The goal is to inject with intent, observe carefully, and stop quickly if results look wrong.

General Safety Rules

  1. Test environment only: Run injection on bench setups or controlled environments unless you have explicit approval for vehicle testing.
  2. Physical safeguards: Keep a hardware disconnect or emergency stop within reach. Know how to cut power fast.
  3. Clear intent: Write down which signals you plan to override and why before you start.
  4. Communicate: Notify anyone else on the bus that injection will be active.
  5. Monitor continuously: Keep Network Traffic, Signal Chart, and ECU Console visible while you inject.

Pre-Test Checklist

Before you press Start, confirm the basics:

  • Activation and permissions: Make sure your license and user role allow injection.
  • Hardware readiness: Verify CAN interface cables, termination, and power to ECUs.
  • DBC alignment: Confirm the correct DBC is loaded so physical values map correctly to raw data.
  • Signal selection: Only enable injection for signals you intend to override.
  • Length settings: Use Frames or Duration for temporary overrides when possible.

A small setup mistake (like a wrong DBC or a mis-typed physical value) can quickly snowball into confusing results.

Safe Operating Flow

Use this basic runbook for every injection session:

  1. Start the system from the main toolbar.
  2. Open Signal Player & Injection and locate the target signals.
  3. Open the signal injection options and set override value, encoding, and length.
  4. Decide if Start with playback is required, then click Save.
  5. Begin injection with Start all (or start one signal manually if needed).
  6. Watch live feedback in Network Traffic and Signal Chart.
  7. Stop injection immediately if results are unexpected or unsafe.

Monitoring During Injection

Injection should never run unattended. Keep these panels visible:

  • Network Traffic confirms frames are actually being transmitted on the expected bus.
  • Signal Chart shows whether decoded values match the override values you configured.
  • ECU Console provides early warnings if an ECU detects faults or rejects messages.

If you see errors or no traffic, stop injection first, then investigate.

Post-Test Actions

After the run, clean up and document:

  • Stop injection and confirm the system returns to normal behavior.
  • Save system changes if any configuration was updated.
  • Export relevant evidence such as Network Traffic captures, chart images, or console logs.
  • Record the injection settings (signals, values, length, and whether Start with playback was used).

The goal is to leave a clear trail for anyone who needs to reproduce your test.

Handling Failures

Scenario Recommended Response
ECU enters bus-off or resets Stop injection, reset the CAN interface, and check bus load.
Unexpected behavior or unstable system Stop injection immediately and document what you observed.
No injected frames appear Verify the selected network and DBC; check that injection is started.
Values look incorrect Confirm encoding type and ensure the DBC matches the ECU firmware.

Traceability & Documentation

Injection is most useful when the results are easy to explain. Keep a short test record that answers:

  • Which signals were injected?
  • What override values and lengths were used?
  • Did injection start with playback or manually?
  • What did the ECU do as a result?
  • Where are the exported logs or charts saved?

This can be as simple as a markdown file stored alongside the system or a ticket comment with links to exported artifacts.

Team Practices

  • Standardize naming for test runs and exports so multiple engineers can compare results.
  • Share a short template for injection notes so everyone documents consistently.
  • Review injection outcomes during regular team check-ins to prevent repeated mistakes.
  • Do not inject on live customer vehicles or production hardware without explicit authorization.
  • Follow regional regulations on CAN manipulation and data handling.
  • Keep credentials and tokens secured if your environment uses authenticated interfaces.

Next Steps

  • Review Schedules & Profiles to understand signal-level injection options and length settings.
  • Use Controls & Panels for a full walkthrough of monitoring panels.
  • Refer to Exports & Reports to package evidence from injection tests.