3091LD AC LOAD from California Instruments Initialization.vi error

[ewtotem]

Symptoms

When initialize vi is executed durectly after AC Laod is power cycled the follwing error occurs:

Error -1073807339 Timeout expired before operation completed. 

Error -1074135039.  Paramter not allowed. This was followed by a device error desplaced on the instrument display "error 108" p164 of the users manual states: "108: A parameter was sent with the command, but none was expected"

All programs and drivers reinstalled

I installed the latest drivers as you will see below. Eventually, I tried removing all the SW and reinstalling it.

I reinstalled the following order:

1. ni488225.exe  GPIB core  SW, reboot
   1. [link removed]
2. Labview 7.1 Express, Developer Edition - Complete, with all functions and drivers I could stuff it with, reboot.
   1. From CD
3. VISA 4.2 drivers, reboot
   1. [link removed]
4. IVI Compliance 3.1
1. https://www.ni.com/en/support/downloads/drivers/download.ivi-compliance-package.html#307076

Labview device VIs

They havn't changed from original, but downloaded anyway.  Installed folder in same place in instr.lib, were all other instrument VIs are located.  these can only be found on the California Instruments website.

AC LOAD Drivers 1.0.0.0

http://www.californiainstruments.com/component/option,com_docman/task,doc_download/gid,61/Itemid,170...

The README file within the ACLOAD package had the following statement:

=====================================================================
CALIFORNIA INSTRUMENTS LAB VIEW 7.0 Driver LD Series
=====================================================================

This instruments driver supports the California Instruments LD Series
of AC Loads.

This driver requires LabView version 7 or higher. 

This driver uses a run time version of the LabWindows/CVI driver for
the LD Series.  As such, the cicld30.dll and the LabWindows/CVI Run
time engine are required to operate.  The RTE is included in the
driver archive file.  You may also have to add the instrsup.dll to
your Windows\System directory if it is not present on your PC.

This statement, combined with Coworkers earlier issue with the Initialation problem, created the following additional steps (including reinstalling all SW and drivers)

http://forums.ni.com/ni/board/message?board.id=170&message.id=146138&query.id=476131#M146138

BTW - it looks like the io.dll file is a necessary part of the Binaer code, rather than VI functionality.

1. Verified the LabWindows/CVI Run Time Engine is installed. It is installed with the VISA 4.2 package.
2. Copied the instrsup.dll, found in the \System32 foldr ot the Windows\System folder.
3. Copied the cicld30.dll to the \system and \system32 folder. although it was also in the same instr.lib, as it has always has been, tried placing it next to .vi being executed.

This AND making sure that the ID Query input is always false seemed to solve the issue.  Setting the ID Query input is always false is not required for a similar VI for my California Instruments 3001ix AC Source Initialize.vi

[BrianInTheForest]

I am not sure of your question.  

I have found that many times that "canned" instrument drivers do not always work the way you expect them to work.

The drivers might have been written for similar instrument model but not your specific model.

[ewtotem]

Thank you, Iach, I will clarify:

The question is "Why does the Initialize.vi for this particular instrument fail when the "ID inquiry" is declared "true".

I am listing the particular errors I found for this specific canned driver for this specific instrument to simply place the issue out into the communinity to see if anyone else has had the same issue.  It is a Instrument specific driver.

In the mean time, I am interacting with CA to see if we can resolve the issue. I will post a solution.  If someone ran into the same situation and has already resolved the issue, that would be even better!

[Can_W]

Hey ewtotem,
I wasn't able to download the driver from the third party company, so I'm not to sure what's causing the errors you're seeing. I looked into the errors, and the most common problem that will cause this is timing issues. If the function is using VISA commands, you may have to change the default times to be longer as it may not have enough time to send it all the data your device has to send.
As for the second error you mentioned, it seems that it is a driver specific item, unless you are using calibration vis. You may need to look over the code and verify that all the information being sent to them are valid, try running it under highlight execution so that you can see specificallly what's happening.