3091LD will not communicate with Labview

[ewtotem]

California Instruments 3091LD AC Load.

Problem:

When test vi ACload_test_single.vi or ACload_test_double.vi is executed, Labview will stall on cicid30_IVI_error_converter.vi (CI). Encounter with this subvi occurs in several places within the main test vi mentioned above. The main test vi will stall on cicid30_IVI_error_converter.vi at what seem to be random point within the main vi.  Once the main test vi is stalled, it does not seem possible to correct the situation.  VI windows can be closed. Labview immediately displays the recovery window(see attached). See attached code and spy result.

The display window on the instrument showed no error.

Labview cannot reset the vi.  The only way to exit is to Ctrl-Alt-Delete, and force a shutdown of Labview.

Instrument is power cycled after each failure.

Configuration:

Error occurs on two independent hardware clusters. 2nd hardware cluster has additional AC Load.

 WindowsXP, service pack3

  Labview 8.5.1

GPIB, 5 instruments in star pattern according to specification, all instruments on during testing, no other instrument has issues. 

Reload the following drivers (provided by NI):

IVI Compliance Package – ICP320.exe

  FULL VISA driver – visa430full.exe

 488.2 driver – ni48825.exe

California instrument drivers for LD series – LV82_cicld30_v1001.exe (provided by California Instruments “CI” – see attached cahnge .zip to exe).

First instrument cluster: firmware 1.2/3.0 Second instrument cluster: firmware 1.2/2.0 and 1.2/3.1 on 2nd AC Load

[Aashish_M]

Hey Ewtotm,

I found some information that explains the possible reasons for the Resetting VI error code in What Does the "Resetting VI: (VI name)" Message Mean in LabVIEW?

I tried running the VIs and it seemed to run fine except for an error for an unconfigured device. That happens because I don't have the hardware.

Is there a specific location in which the "cicid30_IVI_error_converter.vi " produces this error?

To find this out, you can remove the Simple Error Handler.vi and enable automatic error handling.

Hopefully this helps!!

[ewtotem]

Thank you, Aashish,

Unfortuneately, the cicid30_IVI_error_converter.vi lockup occurs in several places at what seem to be random point within the main vi

Here's small sample of were the system locked up:

System tested	Load that errored	Loop Iteration were failed	Position interation were error occured
sys. with 2 loads	1st	5	enable
sys. with 2 loads	2nd	5	recall 0
sys. with 2 loads	2nd	2	close
sys. with 2 loads	1st	1	enable
sys. with 2 loads	2nd	4	enable
sys. with 1 load	n/a	1	recall 1
sys. with 1 load	n/a	2	store 1

[ewtotem]

It turn's out that California Instruments was able to find and fix a bug in the store\recall function. Note that it was also advised not to exercise the flash memory function unecessarily on a regular basis (1000 of cycles, in a loop) in order to perserve it's longevity - shouldn't be an issue for standard usage.  It is advised to use driver version LV71_cicld30_v1002 or later (available from their website).

Also attached are revised versions of the test code with tuned timing between VIs provided by CI.  Works like a charm!