Intrepid Control Systems: neoVIΒΆ

Vendor information

Vendor

Web page

Product name

Version

Intrepid Control Systems Inc

https://www.intrepidcs.com/

Vehicle Network Adapters (CAN)

0.1

Categories

MDL πŸ›ˆ

APL πŸ›ˆ

BAN πŸ›ˆ

BMA πŸ›ˆ

SVC πŸ›ˆ

DGN πŸ›ˆ

FIU πŸ›ˆ

EES πŸ›ˆ

FCT πŸ›ˆ

DBG πŸ›ˆ

IMG πŸ›ˆ

AUDIO πŸ›ˆ

ENVSIM πŸ›ˆ

ENVCOM πŸ›ˆ

βœ“

βœ“

βœ“

βœ“

βœ“

Signal recordings πŸ›ˆ

File format

Comment

*.asc

*.mf4

BUSACCESS - CAN(-FD) ports support MDF4 bus logging only. XCP ports support signal-based MDF4 recording.

*.pcapng

BUSACCESS - CAN(-FD) ports will use linktype=227. The resulting files cannot be processed by trace analysis.

Platform

Operating system

Support

Windows

βœ“

Linux

PortsΒΆ

SpecificsΒΆ

This interface allows, by means of hardware, direct CAN and CAN-FD bus access. It supports the test steps read signal, read/write signal group as well as monitor and supports signal recording, Raw diagnostics with KWP2000 over ISO-TP, the Mini residual bus simulation and Additional functions of the close-to-hardware bus connections.

Info

The APPLICATION ports can only be used with the Add-on ecu.test calibration

Drivers

To use the driver in ecu.test, it is necessary that the file icsneo40.dll is located in the directory %windir%/System32/. If the Vector installer does not store it there, the icsneo40.dll must be copied manually.

If the tool adapter is used in combination with another Intrepid CS application (especially Vehicle Spy or neoVi Explorer), make sure that ecu.test will be initialized with the hardware first. Otherwise it might happen that the device is blocked and a connection setup is not possible.

Warning

The β€œEnable Server” function in the β€œSystem Settings” subcategory (found in the neoVI Explorer) must be disabled under all circumstances. Otherwise unexpected crashes may occur.

It is recommended to install version 3.9.22.16 of the neoVI API and to use the latest drivers that are compatible with that API version. The use of ecu.test with other API and driver versions is untested. Unexpected errors of all kinds can occur, or the tool adapter can fail to work at all.

Hardware selection

One can either choose the device to be used directly in the test bench configuration. For example: The controller number 2 in a CAN port will then correspond to the second CAN channel.

Hardware-Settings

It is currently not possible to control bus termination using ecu.test.

Tested hardware:

  • ValueCAN 4-2

Name

Available if

Default value

Valid values

Type

Description

Hardware

[β€˜<online query>’, β€˜<no toollib start>’]

string

Selection of the CAN interface

Timeout for tool call ❲in sec.❳

β€˜600’

string

Timeout after which a tool call is aborted.