Vector Toolchain: CANoe, Hardware & Licensing

Advanced12 min read

Assumes: 3.1 Signal-Based Communication, 9.4 UDS & DoIP

TL;DR

Vector CANoe is the industry-standard tool for automotive network analysis, simulation, and testing. It works with CAN, CAN FD, Automotive Ethernet, SOME/IP, and UDS/DoIP — the protocols from Modules 3 and 9. Before using CANoe you need three things: the software installed, a VN hardware interface connected and configured via Vector Hardware Manager, and a valid license activated via Vector License Client. This page covers all three — tool setup, daily workflows, and where CANoe fits in your bench alongside ADB, UART, and QXDM. Memorize the setup chain: D-L-H-C = Driver Setup, License Client, Hardware Manager, CANoe.

You already know the protocols — CAN signals (Page 3.1), SOME/IP services (Page 3.3), UDS/DoIP diagnostics (Page 9.4). This page gives you the tool that ties them together on your bench. Love them or complain about them, they’re the IDE and debugger of automotive rolled into one (expensive) subscription.

What CANoe Does

CANoe is a multi-bus development environment that covers the full workflow from early simulation through integration testing to production diagnostics:

flowchart TB
    subgraph canoe ["CANoe Software"]
        TRACE["Trace Window\nraw packet decode"]
        GRAPHICS["Graphics Window\nsignal plots over time"]
        SIM["Simulation Setup\nnodes, databases, interaction layers"]
        DIAG["Diagnostic Console\nUDS sessions, DTCs"]
        CAPL_IDE["CAPL Browser\nscript editor + debugger"]
        TEST["Test Setup\nvTESTstudio / CAPL test modules"]
    end

    subgraph hw ["Vector Hardware"]
        VN1610["VN1610\n2x CAN/CAN FD"]
        VN5620["VN5620A\n4x Automotive ETH + 2x CAN FD"]
    end

    subgraph vehicle ["Vehicle / Bench"]
        CAN_BUS["CAN Bus"]
        ETH_BUS["Automotive Ethernet"]
        ECU["ECU under test"]
    end

    VN1610 <-->|"D-SUB9"| CAN_BUS
    VN5620 <-->|"ix Industrial\n100/1000BASE-T1"| ETH_BUS
    CAN_BUS <--> ECU
    ETH_BUS <--> ECU
    canoe <-->|"USB / Ethernet"| hw

CANoe Options and Use Cases

CANoe is modular — you purchase the base tool plus options for each bus system and protocol:

Option	Protocols Covered	Typical Use Case	Module Link
CAN (included)	CAN, CAN FD, J1939, CANopen	Bus analysis, DBC signal decode, frame logging	Page 3.1
Ethernet	SOME/IP, SOME/IP-SD, DoIP, AVB, PTP, TCP/UDP, VLAN	SOME/IP service testing, Ethernet packet analysis	Page 3.3
Diagnostics	UDS, KWP2000, OBD-II, ODX/CDD import	Diagnostic session testing, DTC reading, flashing	Page 9.4
DiVa	Automated diagnostic validation	Generate + execute UDS test cases from ODX/CANdela	Page 9.4
LIN	LIN 2.x	Body domain signal testing (seats, mirrors, lights)	Page 3.1
CAPL scripting	All buses	Restbus simulation, fault injection, automated tests	This page

CANoe vs CANalyzer: CANalyzer is analysis-only — no simulation, no restbus, no CAPL test modules, lower cost. CANoe adds simulation, virtual ECU nodes, test automation, and scripted fault injection. Most integration and validation programs use CANoe. CANalyzer is sufficient when you only need passive bus monitoring.

Where CANoe sits in the toolchain ecosystem

Vector’s automotive toolchain is broader than CANoe alone:

Tool	Purpose	Relation to CANoe
CANoe	Network development, simulation, test	The hub — uses all databases and interfaces
CANalyzer	Passive bus analysis	CANoe subset, analysis only
CANape	ECU calibration and measurement (XCP/CCP)	Parallel tool, shares VN hardware
vTESTstudio	Test case authoring (integrates with CANoe)	Creates test sequences CANoe executes
DaVinci Configurator	AUTOSAR BSW configuration	Generates ARXML databases CANoe imports
MICROSAR	AUTOSAR Classic BSW implementation	Runs on ECUs that CANoe tests

On your bench, CANoe runs alongside ADB (AAOS debug), UART (boot logs), QXDM (modem debug), and lb (OTA campaigns). Each tool covers a different domain — CANoe owns the network bus layer.

Vector Hardware Interfaces

VN interfaces bridge your PC to the vehicle bus. The interface you need depends on which buses you work with:

Interface	Bus Support	Connectors	Host Connection	Power	Use Case
VN1610	2x CAN high-speed (CAN FD capable)	1x D-SUB9 (use CANcable 2Y for split channels)	USB 2.0	USB-powered	Daily CAN bus tap — compact, portable
VN1630A	2x CAN/CAN FD + 2x LIN (with piggybacks)	2x D-SUB9	USB 2.0	USB-powered	CAN + LIN mixed-bus setups
VN5620A	4x Automotive Ethernet (100/1000BASE-T1), 2x standard Ethernet (RJ45), 2x CAN FD	2x ix Industrial, 2x RJ45, D-SUB9	USB 3.0 or Ethernet	USB-C or 12V external	Automotive Ethernet / SOME/IP bench
VN8900	Configurable: CAN, LIN, FlexRay, Ethernet (module slots)	Multiple (module-dependent)	Ethernet	External 12V	HIL rigs, standalone logging

Physical Connections

CAN (VN1610): The D-SUB9 connector carries two CAN channels. Pin 2 = CAN_L, pin 7 = CAN_H, pin 3 = GND (for Channel 1). Use the CANcable 2Y splitter to get separate D-SUB9 connectors per channel. Always ensure the CAN bus is properly terminated (120 ohm at each end).

Automotive Ethernet (VN5620A): The ix Industrial connectors carry 100BASE-T1 or 1000BASE-T1 signals — the automotive physical layer, not standard Ethernet. The RJ45 ports are standard 10/100/1000BASE-T for connecting to your PC or infrastructure switches. The VN5620A acts as a media converter between automotive and standard Ethernet, transparently and bidirectionally.

Power considerations: The VN5620A can run on USB-C power for basic setups but needs the external 12V supply for full Automotive Ethernet port power. If your Ethernet LEDs don’t light up, check power supply first.

Vector Hardware Manager

Vector Hardware Manager (VHM) is the unified configuration tool for all VN interfaces. It replaces the legacy “Vector Hardware Config” and “Vector Network Manager” tools — if you see those names in old documentation, they map to VHM now.

Setup Workflow

sequenceDiagram
    participant You
    participant VDS as Vector Driver Setup
    participant VHM as Vector Hardware Manager
    participant VN as VN Interface
    participant CANoe

    You->>VDS: Install (includes VHM + drivers)
    You->>VN: Connect via USB
    VN-->>VHM: Auto-detected
    You->>VHM: Open, enter Edit mode
    You->>VHM: Configure ports (link speed, role)
    You->>VHM: Click Deploy
    VHM->>VN: Apply configuration
    VN-->>VHM: Status LED green
    You->>CANoe: Open configuration
    You->>CANoe: Hardware ribbon > Channel Mapping
    CANoe->>VN: Measurement started

Step-by-Step: Ethernet Setup (VN5620A)

1. Install Vector Driver Setup — download from vector.com/drivers. Run with administrator rights. This installs the VN5620A driver and Vector Hardware Manager automatically.
2. Connect VN5620A — USB-C to your PC (or Ethernet for remote setups). Attach 12V external supply if using Automotive Ethernet ports.
3. Open Vector Hardware Manager — the interface appears in the device list. Power LED should be solid green.
4. Enter Edit mode — click the edit (pencil) icon at the top.
5. Configure Ethernet — navigate to the Ethernet tab. Drag the port your ECU is connected to into the center configuration area. Double-click the port to set:
   • Link speed: match the ECU (100BASE-T1 or 1000BASE-T1)
   • Role: if the ECU is master, set VN port to slave (and vice versa)
   • Network name: note this name exactly — CANoe must use the same string
6. Deploy — click Deploy (top-right). The VN5620A applies the config. Network LED lights up if the Ethernet link is established.
7. In CANoe — open your Ethernet configuration. Verify the network name matches VHM exactly. Go to Hardware ribbon > activate the physical hardware ports via Channel Mapping.

Step-by-Step: CAN Setup (VN1610)

1. Install Vector Driver Setup — same installer covers VN1610.
2. Connect VN1610 — USB to your PC. No external power needed.
3. Open VHM — VN1610 appears with 2 CAN channels auto-detected.
4. Verify baud rate — in Channel view, confirm CAN baud rate matches your bus (typically 500 kbit/s for vehicle CAN, 2 Mbit/s data phase for CAN FD).
5. In CANoe — open a CAN configuration. Hardware ribbon > Channel Mapping > select VN1610 channels.

Common Gotcha

If the Ethernet network name in Vector Hardware Manager doesn’t exactly match CANoe’s config, you get zero packets and no error message — just silence. The #1 CANoe setup failure is a name mismatch: Ethernet 1 vs Ethernet1 (no space). Always verify the name matches character-for-character before debugging anything else. If you renamed the network in VHM, update CANoe’s Simulation Setup to match.

Vector License Client

No license, no CANoe. The Vector License Client (VLC) manages activation, renewal, and troubleshooting for all Vector software.

License Types

License Type	Where It Lives	Portable?	Use Case
Dongle / hardware	On VN interface (or USB dongle)	Yes — plug into any PC	Shared equipment, lab benches
PC-local	Locked to one machine (hardware ID)	No — that PC only	Dedicated workstations
Floating / network	License server on network	Yes — any PC with VLC pointing to server	Teams with shared license pool

Activation Workflow

Online activation (most common):

1. Open Vector License Client (search “Vector License Client” in Start menu)
2. Click Activate
3. Paste the Activation Key from your Delivery Note (format: XXXXX-XXXXX-XXXXX-XXXXX)
4. Click Load — VLC contacts Vector’s server and retrieves available licenses
5. Select the License Carrier: your PC, a connected VN interface, or a USB dongle
6. Select the license(s) to activate
7. Click Activate — license is written to the carrier
8. Start CANoe — it should find the license automatically

Offline activation (behind corporate proxy / air-gapped):

1. In VLC, click Activate, paste the key, select the carrier
2. Click Create Context File — save the .VLC file
3. On a machine with internet access, go to https://portal.vector.com/vector-offline-licensing/
4. Upload the .VLC file, select licenses, click Activate
5. Download the Update File (.VLU)
6. Back in VLC on the original machine, click Apply Update File, select the .VLU
7. VLC writes the license. Save the Receipt File (.VLR)
8. Upload the .VLR to the Vector portal to complete the transaction

Common License Problems

Symptom	Likely Cause	Fix
“No license found”	Wrong License Carrier selected in VLC	Open VLC, check which carrier has the license. If dongle: is it plugged in?
CANoe starts but option grayed out	License doesn’t include that option (e.g., Ethernet)	Check VLC > Licenses tab for active options vs. what you need
“License expired”	Maintenance/subscription lapsed	Contact your Vector account manager for renewal
Online activation fails	Corporate proxy blocking VLC	VLC > Settings > Test Proxy Settings. Configure proxy. If still failing, use offline flow.
Dongle not detected	USB driver issue	Reinstall Vector Driver Setup with admin rights. Try different USB port.

Mental Model

CANoe is a flight simulator for vehicle networks. Just as pilots practice in simulators before flying real aircraft, you use CANoe to simulate, test, and analyze vehicle bus communication before and after connecting to real ECUs. VN interfaces are the cockpit instruments — they connect your simulator to the real world. The License Client is your pilot’s license — without it, the simulator refuses to start.

CANoe = the Swiss Army knife. VN1610 = the USB CAN interface. Together = your window into every bus.

Think About It

You need to debug a SOME/IP service discovery failure. Which Vector tool do you reach for?

Reveal Answer

CANoe with the Ethernet option and SOME/IP interaction layer — connect a VN5620A to automotive Ethernet and filter SOME/IP-SD traffic (OfferService/FindService multicast) in the Trace window. Use CAPL or Simulation Setup to verify the expected Service ID and Instance ID are offered, and confirm Vector Hardware Manager link speed, role, and network name match the ECU. CANalyzer works for passive sniffing only; CANoe adds injection, restbus simulation, and timed assertions when you need to simulate a missing ECU.

CANoe for Your Stack

Here is how CANoe maps to the specific technologies you work with daily:

SOME/IP Testing (Pages 3.3, 8.6)

Connect VN5620A to the vehicle Automotive Ethernet port. Open a CANoe Ethernet configuration with the SOME/IP interaction layer enabled.

What you can do:

• Observe SOME/IP-SD multicast: see which ECUs offer which services (FindService / OfferService)
• Filter by Service ID to find the OTA UpdateManagement service from Page 8.6
• Subscribe to events and watch field notifications in the Trace window
• Inject SOME/IP method calls to trigger ECU behavior without waiting for the real caller
• Simulate missing ECUs with restbus: CANoe acts as the zone controller offering services your cockpit SoC expects

Practical filter: In CANoe Trace window, filter by SOME/IP Service ID = 0x1234 (your program’s update service ID). This shows exactly the discovery and method calls your lb tool uses.

CAN Signal Verification (Pages 3.1, 6.3)

Connect VN1610 to the CAN bus on your bench. Import the program’s DBC file into CANoe.

What you can do:

• Decode raw CAN frames into named signals with engineering units (e.g., VehicleSpeed_kph = 42.5)
• Plot signals over time in the Graphics window — verify VHAL property changes from Page 6.3 appear on the bus
• Check signal timing — is the 10 ms periodic signal actually arriving every 10 ms?
• Detect missing messages or DTC-triggering conditions (signal timeout = “ECU lost communication”)

DoIP Diagnostics (Page 9.4)

Configure a DoIP tester node in CANoe’s Simulation Setup:

• Set the tester’s IP address, logical address, and target ECU logical address
• DoIP connects on TCP port 13400 with routing activation
• Open the Diagnostic Console, import an ODX/CDD file for the ECU
• Send UDS requests: ReadDataByIdentifier (0x22), RoutineControl (0x31), ReadDTCInformation (0x19)
• The Diagnostic Console decodes responses using the ODX database — no manual hex parsing

Restbus Simulation

When your bench has only the cockpit SoC but the real vehicle has 20+ ECUs on the network, CANoe fills the gap:

1. Import the network ARXML or DBC database describing all ECUs and signals
2. CANoe generates interaction layer nodes for each missing ECU
3. These virtual ECUs send periodic CAN frames and respond to SOME/IP service requests
4. Your cockpit SoC sees a “complete” network — no DTC storms from missing ECUs, no timeout errors

flowchart LR
    subgraph real ["Real Hardware"]
        SoC["Cockpit SoC\nSA8155P"]
    end

    subgraph canoe_sim ["CANoe Restbus Simulation"]
        VGWN["Virtual Gateway"]
        VZONE["Virtual Zone Controller"]
        VBODY["Virtual Body ECU"]
        VADAS["Virtual ADAS ECU"]
    end

    SoC <-->|"CAN bus\n(VN1610)"| canoe_sim
    SoC <-->|"Automotive Ethernet\n(VN5620A)"| canoe_sim

CAPL Quick Reference

CAPL (Communication Access Programming Language) is Vector’s C-like scripting language embedded in CANoe. It reacts to bus events, timers, and diagnostic responses.

Example 1: Log a CAN Signal Value

/* Triggered every time the VehicleSpeed message arrives on CAN */
on message VehicleSpeed
{
  float speed_kph;
  speed_kph = this.VehicleSpeed_kph;  /* DBC signal name */

  if (speed_kph > 0)
  {
    write("Vehicle moving at %.1f km/h", speed_kph);
  }
}

Example 2: Periodic SOME/IP Service Check

/* Timer fires every 2 seconds to check if UpdateManagement service is offered */
on timer checkUpdateService
{
  /* Log current SOME/IP-SD state for the update service */
  write("UpdateManagement service state: %d",
        SomeIpGetServiceState(0x1234, 0x01));  /* serviceId, instanceId */
  setTimer(checkUpdateService, 2000);
}

on start
{
  setTimer(checkUpdateService, 2000);
}

Example 3: UDS Read DTC Information

/* Send ReadDTCInformation (0x19, sub-function 0x02 = by status mask) */
on key 'd'
{
  diagRequest ReadDTCInformation_reportDTCByStatusMask req;
  req.DTCStatusMask = 0x09;  /* testFailed | confirmedDTC */
  diagSendRequest(req);
}

on diagResponse ReadDTCInformation_reportDTCByStatusMask
{
  long numDTCs;
  numDTCs = diagGetRespPrimCount(this);
  write("Found %d active DTCs", numDTCs);
}

CAPL scripts live inside CANoe’s Simulation Setup as node programs. They compile and run when you start the measurement. For more complex test automation, use vTESTstudio test cases that call into CAPL functions.

CANoe bench setup checklist

Before every measurement session:

1. Open Vector Hardware Manager — verify your VN interface is detected (power LED solid green)
2. Check channel config — CAN baud rate matches bus (500 kbit/s typical), Ethernet link speed and role correct
3. Deploy — apply config to VN interface. Ethernet link LED should light up.
4. Open CANoe config — verify channel mapping in Hardware ribbon matches VHM
5. Start measurement — Trace window should show packets

If no packets appear:

• CAN: check termination (120 ohm), cable connection, baud rate mismatch
• Ethernet: check network name match (VHM vs CANoe), link speed/role, cable, power supply on VN5620A
• General: check VN firmware version (update via VHM if outdated), try USB re-plug

The setup chain troubleshooting mnemonic: D-L-H-C = Driver Setup installed? License active? Hardware Manager configured and deployed? CANoe channel mapping correct? Trace backward from C to D until you find the broken link.

The D-L-H-C Setup Chain

When setting up Vector tools on a new machine, follow this exact order:

flowchart LR
    D["1. Driver Setup\nInstall VN drivers + VHM"]
    L["2. License Client\nActivate CANoe license"]
    H["3. Hardware Manager\nConfigure VN interface"]
    C["4. CANoe\nOpen config, map channels"]

    D --> L --> H --> C

Step	What to Verify	Failure Symptom If Skipped
D — Driver Setup	VHM opens, VN device appears in Device Manager	“No hardware found” in CANoe
L — License Client	VLC shows active license with correct options	CANoe won’t start or options grayed out
H — Hardware Manager	VN status LED green, config deployed	CANoe connects to VN but no bus activity
C — CANoe	Channel mapping set, measurement starts with packets	Silent Trace window

If CANoe isn’t working, trace backward through D-L-H-C. Most issues are at step L (license) or H (hardware config not deployed).

Connect the Dots

Module 3.1 (Signal-Based Communication) taught CAN frame structure and DBC files — CANoe decodes those signals live. Module 3.3 (SOME/IP) covered service discovery and methods — CANoe’s Ethernet option tests those services with its SOME/IP interaction layer. Module 3.4 (gRPC) is the one protocol CANoe doesn’t cover — use Wireshark or grpcurl for gRPC streams. Page 9.4 (UDS/DoIP) explained diagnostic services — CANoe is the industry-standard tester for executing those sessions. Page 10.1 (Debug Bench) showed your bench layout — VN interfaces sit alongside the UART adapter, JTAG probe, and USB cables. Page 10.5 (Debug Decision Tree) maps bus-level symptoms (missing signals, DTC storms, SOME/IP discovery failures) to CANoe as the first-reach tool for network-layer debug.

Quick Reference

1. CANoe = analysis + simulation + testing for CAN, Ethernet, SOME/IP, UDS/DoIP. CANalyzer = analysis only.
2. VN1610 = daily CAN tap (USB, compact). VN5620A = Automotive Ethernet + CAN bench (external power for full ETH).
3. Vector Hardware Manager configures VN interfaces. Always Deploy after changing config. Network name must match CANoe exactly.
4. Vector License Client activates licenses. Dongle = portable, PC-local = fixed, floating = shared. Offline flow uses .VLC / .VLU / .VLR files.
5. D-L-H-C = Driver Setup, License Client, Hardware Manager, CANoe. Install in order, troubleshoot in reverse.

Check Your Understanding

1. What is the key difference between CANoe and CANalyzer?

Recall

A. CANalyzer requires a VN5620A interface; CANoe works without any Vector HWB. CANoe is free and open-source; CANalyzer requires a paid dongle license keyC. CANoe adds simulation, restbus, CAPL scripting, fault injection; CANalyzer is RXD. CANalyzer supports DoIP diagnostic routing; CANoe does not support Ethernet

2. Which Vector hardware interface provides Automotive Ethernet (100BASE-T1 / 1000BASE-T1) access for SOME/IP testing alongside CAN FD channels?

Recall

A. Any VN interface can do Ethernet with a firmware updateB. VN1610 — it supports all bus types via piggyback modulesC. VN5620A — it has 4 Automotive Ethernet ports and 2 CAN FD channelsD. VN8900 — it is the only interface that supports Ethernet

3. CANoe shows zero Ethernet packets even though the VN5620A link LED is green. What is the most likely configuration issue?

Applied

A. Ethernet network name in HW Manager doesn't match the CANoe config nameB. The active CAPL script has a filter that drops all inbound Ethernet packetsC. CANoe requires a full restart after any hardware or driver change on the PCD. The VN5620A firmware needs updating

4. You are setting up Vector tools on a new PC. In the D-L-H-C setup chain, which step must succeed before CANoe can launch?

Applied

A. Only Driver Setup (D) — the rest can be configured after CANoe opensB. License Client (L) only — Vector drivers install automatically with CANoeC. All four steps must complete successfully before CANoe can open a configD. Driver Setup (D) and License Client (L) — CANoe needs license + HW drivers

5. Your bench has only the cockpit SoC but the real vehicle has 20+ ECUs. CANoe generates virtual nodes sending periodic frames. What is this technique called?

Applied

A. DoIP routing activationB. SecurityAccess seed-key provisioningC. A/B OTA rollback of the zone controller firmware to the previous build slotD. Restbus simulation — CANoe fills missing ECUs so DUT sees complete network

6. A factory issue report cites DTC U0140 and RoutineControl 0x0203 failure during a DoIP session. Which Vector workflow helps reproduce and decode this?

Synthesis

Connects to: Module 10 — Debug Engineering

A. DaVinci Configurator BSW code generation and AUTOSAR module parameterizationB. vFlash production line flashing with automated MES traceability integrationC. CANoe DoIP tester with ODX/CDD — sends UDS 0x19/0x31, decodes responsesD. CANape XCP calibration measurement for real-time parameter tuning on bench

Further Reading

• Vector CANoe — Official product page for bus analysis, simulation, SOME/IP testing, and UDS/DoIP diagnostic sessions on the bench.
• Vector CANalyzer — Analysis-focused sibling tool for passive bus monitoring when you don’t need full simulation or test automation.
• Vector DaVinci Developer — AUTOSAR authoring tool for SWC design, service interfaces, and diagnostic service definitions that feed CANoe test databases.
• Vector DaVinci Configurator Pro — BSW and ECU configuration tool for Classic AUTOSAR stacks integrated with Vector MICROSAR.
• Vector Hardware — VN Interface Family — VN1610, VN5620A, and related interface hardware configured through Vector Hardware Manager.
• Vector Support & Downloads — Driver packages, License Client, Hardware Manager, and release notes for the D-L-H-C setup chain.