Nothing on this page is built. It is listed so you know where you still need the vendor tool, and what has to happen before a capability can be relied on. Nothing here is a commitment to a date. Many items wait on a vendor document, a vendor tool on a lab machine, or files from a customer.
Verification
- Run the Vector, PEAK and Kvaser CAN and LIN interfaces against the vendors' own libraries through the verification kits, per hardware family, and on real adapters (Vector, PEAK, Kvaser and slcan) with bench ECUs.
- Run the CANoe4SW Server Edition, DaVinci Configurator, D-PDU API and OEM seed-key kits against the real tools and libraries.
- Run the module on Windows, where most engineers will use it (the vendor libraries driven natively, receive events, registry discovery, 32-bit Windows), and on macOS.
- Check an offline install, a managed machine without administrator rights, a licence server failure and a packaged, code-signed build.
- Open what the module writes in the vendor tools: an edited DBC in CANdb++, ASC and BLF recordings in CANalyzer and CANoe, MF4, DCM and CDF files in CANape and INCA, TRC files in PCAN-View and PCAN-Explorer.
- Try customer projects at realistic size: production DBC files with CAN FD, a system description as delivered, a real ECU's A2L with its HEX or S19, its ODX, PDX or CDD, and traces written by the customer's own tools.
- Reprogramming against a real ECU and flash bootloader, and DoIP against a real vehicle gateway.
Agents
- Agent tools called from the chat: the Editor's default chat participant has to pass the request's tools to the model and run the calls it returns through the tools service. Today the tools are reached through the tools service only (see Approvals and audit).
- Agent tools for SOME/IP, the Ethernet side of the rest-bus simulation and panels.
Networks and simulation
- OEM interaction layers and send types beyond Ford's FixedPeriodic, EventPeriodic and Event, which are shown as notes today and sent cyclically only when you ask.
- OSEK/VDX network management and OEM network management variants.
- The collection of PDUs updated since the last frame (trigger, timeout, queued or last-is-best) for container PDUs in the simulation.
- FlexRay: FIBEX files, a live FlexRay channel through vendor FlexRay interfaces, FlexRay rest-bus simulation, FlexRay in the CAN Bus panel, the signal plot and the agent tools, and editing a FlexRay cluster.
- J1939: a tester that claims its own address, a simulated node that looks for another address after losing one, the extended transport protocol sent and answered, groups the transport protocol carries in the trace editor's plot and message filter, and J1939 on CAN FD from ARXML.
- ISOBUS virtual terminal and task controller.
- E2E profiles 4m, 7m and 8, the E2E state machine and profile behaviour settings; SecOC freshness timestamps, OEM freshness value managers, authenticators in a separate PDU and algorithms other than CMAC/AES-128; E2E on SOME/IP methods.
- Automotive Ethernet: payloads of Classic Platform PDUs, serialisation with tags (TLV) and C++ implementation data types; vendor logger encapsulations (TECMP, ASAM CMP); Ethernet frames in BLF; service discovery over IPv6 and the description's SD timing for the SOME/IP node; secured SOME/IP.
- DLT: a live connection to a log daemon, DLT over serial and the version 2 header.
- PCAN-View transmit lists (
.xmt), PEAK symbol files (.sym) and PCAN-Explorer projects.
Diagnostics and flashing
- OEM flash templates, vFlash packs (
.vflashpack), flashing over XCP or CCP, and INCA's ProF flashing. - Authoring CANdelaStudio files and exporting ODX from them.
- OEM security manager plug-ins for seed-key and SecOC keys.
- Generated diagnostic tests for more services: InputOutputControl, CommunicationControl, ControlDTCSetting, memory reads, the transfer services, and ReadDTCInformation sub-functions other than 0x02.
Calibration
- CCP, XCP on FlexRay and SxI, and several devices in one session.
- CANape projects (
.cna), INCA's database and workspaces, and ETAS ETK and ES measurement hardware.
CANoe and test
- Desktop CANoe through its COM interface, and with it CANoe configurations (
.cfg), the Write window of a running measurement, the test modules of a desktop configuration, a CAPL debugger, and runtime values of system and environment variables. - vTESTstudio projects and their parameter files.
- Trace item files (
.vti-tso) and requirement references in CANoe reports, ReqIF tool extensions, and links written back into the requirements tool. - Panels: import of CANoe Panel Designer, CANalyzer, CANape and PCAN-Explorer panels; controls bound to CANoe system variables, DBC environment variables, LIN and SOME/IP signals and diagnostic requests; pictures, tabs and pages, colours by threshold, curves, maps and plots on a panel, and key bindings.
- CANoe's Scope option, which needs Vector's scope hardware.
AUTOSAR configuration
- ISOLAR-B's own validation and generation, and DaVinci Configurator 5's command line.
- Findings of
dvcfg-bplaced at their element rather than on the project file. - Software components: mapping-based port compatibility, writing pass-through connectors, and the mapping of components to ECUs.
- Adaptive manifests: user-defined deployments, the content of persistency, DLT, platform health management, identity and access, crypto and update elements, editing DDS instances, and signal-based service deployments.
Migration and change management
- CANoe and CANalyzer key assignments as a preset, CANape and INCA keymaps, and a layout preset like CANoe's desktop.
- Import of settings from CANoe configurations, CANape projects, INCA workspaces, PCAN-View, PCAN-Explorer and CanKing projects, and of ECU definitions from a CANoe diagnostic configuration or a vFlash project.
- The vendor's change management: which systems teams deliver these files through (candidates include PREEvision, DaVinci's text projects, PTC Integrity and IBM ELM) is still to be researched. Today the module offers Git and the semantic DBC compare.
Out of scope
- Running CAPL without CANoe: CAPL runs in your CANoe.
- OEM engineering testers (ODIS, DTS.monaco) and their back ends.
- INCA automation (INCA-FLOW, INCA-MIP); the module's agent tools automate natively.
- HIL hardware (dSPACE SCALEXIO, ControlDesk) and Simulink model-based flows.
- Compliance evidence such as ASPICE or ISO 26262 work products, and bundling any vendor driver, schema or specification.