Configuration Store. For more information, refer to the Using the Driver Effectively > The .NET API > help topic. Instantiating the Driver Direct I/O IVI instrument drivers for message-based instruments include and Read, ReadBytes, Write, WriteBytes methods, as well as a reference to the underlying I/O, which enable you to perform I/O directly DirectIO, with the instrument. For more information on using these methods and properties, refer to the Driver API help topic. Reference > Driver Hierarchy > I<ComponentID> > System Instrument Command Coverage IVI instrument drivers for instruments typically implement the full functionality of the instrument available via the commands and queries with a few exceptions. The help reference topics for each method and property list the instrument command(s) that the driver implements for each function and parameter. Some commands and queries are not suitable for an instrument driver. The following commands are NOT implemented in this driver: All commands in the subsystem <DIAGnostic> All commands in the subsystem <CALibrate> All commands in the subsystem <FORMat> All commands in the subsystem <DISPlay> All commands in the <SYSTem:COMMunicate>subsystem Undocumented SCPI commands Specific commands: HARDCopy CURSor> Driver users can send any commands to a message-based instrument using the driver’s Direct I/O functions. Known Issues The readme.txt file can be found in the <Program Files>\IVI Foundation\IVI\Microsoft.NET\Framework64\v2.0.50727\<DriverDirName> directory. It contains information about known issues. Contact Support If you have feedback or need help using this driver, contact <appropriate support contact information>. Trademarks <Optionally add trademark statements here> Help Documentation Help documentation be installed with the driver. Help documentation may contain additional information beyond what is specified in this section. For each IVIC driver function and IVICOM or IVI.NET driver method, an IVI driver shall provide help documentation for the following:
Configuration Store. For more information, refer to the Using the Driver Effectively > The .NET API > Instantiating the Driver help topic. Direct I/O IVI instrument drivers for message-based instruments include Read, ReadBytes, Write, and WriteBytes methods, as well as a reference to the underlying I/O, DirectIO, which enable you to perform I/O directly with the instrument. For more information on using these methods and properties, refer to the Driver API Reference > Driver Hierarchy > I<ComponentID> > System help topic. Instrument Command Coverage IVI instrument drivers for instruments typically implement the full functionality of the instrument available via the commands and queries with a few exceptions. The help reference topics for each method and property list the instrument command(s) that the driver implements for each function and parameter. Some commands and queries are not suitable for an instrument driver. The following commands are NOT implemented in this driver: All commands in the <DIAGnostic> subsystem All commands in the <CALibrate> subsystem All commands in the <FORMat> subsystem All commands in the <DISPlay> subsystem All commands in the <SYSTem:COMMunicate>subsystem Undocumented SCPI commands Specific commands: HARDCopy CURSor> Driver users can send any commands to a message-based instrument using the driver’s Direct I/O functions. Known Issues The readme.txt file can be found in the <Program Files>\IVI Foundation\IVI\Microsoft.NET\Framework64\v2.0.50727\<DriverDirName> directory. It contains information about known issues. Contact Support If you have feedback or need help using this driver, contact <appropriate support contact information>. Trademarks <Optionally add trademark statements here> Help Documentation Help documentation be installed with the driver. Help documentation may contain additional information beyond what is specified in this section. For each IVIC driver function and IVICOM or IVI.NET driver method, an IVI driver shall provide help documentation for the following:
IVI-3.1_Architecture_2017-05-08.docx