It is important to note that any parameters or options passed directly to the Initialize function via the OptionString parameter discussed below override any settings found in the IVI Configuration Store. The user calls the Get Next Coercion Record function to extract and delete the oldest coercion record from the list. Error is thrown. You can override the default values by assigning a value explicitly in a string you pass for this parameter. If you use logical names, driver session names, or virtual names in your program, you must make sure that the name you use matches the name in the IVI Configuration Store file exactly, without any variations in the case of the characters in the name. This is useful if you have multiple physical instances of the same type of instrument. It is critical to understand what options are available and how they impact driver operation.
|Date Added:||20 October 2005|
|File Size:||34.35 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
You changed your response to Not Helpful.
When you set this parameter to TRUE, the driver verifies that the instrument you initialize is a type that this driver supports. Here is a recap of the data flow: Specifies how often the driver should save trace data to the trace log file. It is critical to understand what options are available and how they impact driver initiallizing.
ClassPrefix Initialize With Options
Message 6 of Note The Initialize VI creates a new session each time you invoke it. Returns an instrument handle that you use to identify the instrument in all subsequent instrument driver VI calls.
Message 3 of This is used to specify settings that are supported by the driver but not defined by IVI. Message 7 of Use this ocm to decide if any functionality should be bypassed in the event of errors from other VIs.
ClassPrefix Initialize – IVI Driver Help – National Instruments
You can override the default values by assigning a value explicitly in a string you pass for this parameter. Specifies whether the IVI specific driver validates attribute values and function parameters. Have you disabled those to see if either of those are causing the timeout?
You can use the same session ibi multiple program threads. Message 9 of It is not necessary to include the. Cache, range check, query instrument status – both checked 3.
Message tye of Message 10 of Specifies the maximum size of the trace log file in bytes. For MAX options, I’ve tried: Any model supported by the driver Trace Output trace log of all driver calls to an XML file in the same directory as the application executable accessing the driver. August Part Number: Cache, range check – both checked 2.
When caching is enabled, the IVI specific driver keeps track of the current instrument settings so that it can avoid sending redundant commands to the instrument.
The driver session, in turn, identifies a specific driver and device and specifies the initial settings for the session. For output parameters that represent instrument data, the specific driver functions return simulated values.
You have the option to reset or query the instrument id. If this is enabled, the driver will perform a reset of the instrument.
I’ve used the MAX to create an IVI logical name and tied the name to the appropriate driver session following the instructions in: Numeric jnitializing in minutes. Although you can create more than one instrument driver handle for the same resource, it is best not to do so. Specifies whether the IVI specific driver queries the instrument status at the end of each user operation.
Message 4 of