NI: VISA¶
Vendor information
Vendor |
Web page |
Product name |
Version |
|---|---|---|---|
National Instruments |
Virtual Instrument Software Architecture |
Categories
MDL 🛈 |
APL 🛈 |
BAN 🛈 |
BMA 🛈 |
SVC 🛈 |
DGN 🛈 |
FIU 🛈 |
EES 🛈 |
FCT 🛈 |
DBG 🛈 |
IMG 🛈 |
AUDIO 🛈 |
ENVSIM 🛈 |
ENVCOM 🛈 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Platform
Operating system |
Support |
|---|---|
Windows |
✓ |
Linux |
Ports¶
Specifics¶
Info
An instruction is a string that either configures a device to which it is transferred or requests certain information (its status) from that device in order to be able to read that information. Concrete instructions can be taken from the documentation for the hardware concerned.
The VISA interface allows direct access to different kinds of hardware for configuration, programming or error treatment. For that purpose, the hardware can be connected via different interfaces, such as GPIB, USB, LAN or RS232.
Supported drivers
In order to access hardware by means of VISA it is necessary that a VISA driver is installed on the system. In addition, there must be an entry for the device in the respective VISA management tool (e.g. NI MAX) that ends with ::INSTR. That driver, as a rule, is included in the scope of hardware supply. In this case it is strongly recommended to use this driver, because only such drivers support the particular hardware-specific functions which extend the VISA standard.
If any problems occur using ecu.test with hardware drivers, it may help to install, alternatively, the VISA driver of NI. This driver supports the default functions of hardware to be used via VISA and has been tested in combination with ecu.test. The driver can be downloaded, after prior registration, at the following address:
Test bench options
For utilization in ecu.test the tool VISA must be selected in the test bench configuration and be activated in by means of a right click.
Hardware name: Alias or interface identifier of the hardware to be connected.
Time-out: Maximum duration (in ms) of an operation before abort.
Chunk size: Maximum size (in Bytes) of individual data packages to be transferred.
Note: The option to adjust the chunk size is relevant only in case of problems with the existing hardware. Normally you may keep the default setting, as most devices support message transfer distributed over several data packages.
Properties 🛈¶
Name |
Available if |
Default value |
Valid values |
Type |
Description |
|---|---|---|---|---|---|
Timeout for tool call ❲in sec.❳ |
‘600’ |
string |
Timeout after which a tool call is aborted. |