LabVIEW not recognizing ELVIS II+

[eytan321]

Greetings.

In our lab, we have a Prior Proscan II, for our measurements.

In my engineering project - I wrote an automation code in Labview, to connect all our hardware components (stage, spectrometer & other polarizing motors) for better and more accurate measurements.

Most of the time - the code works and I don't get any problem, but in some case (in longer measurements usually) - I get an "error" message from one of the VI's of the stage.

I will appreciate your help please.

see attached the error messages i got (i know my code isn't elegant... sorry in advance)

Thank you!

E. Ackermann

Hebrew University of Jerusalem

[Kyle97330]

I believe your attachments didn't get attached... I don't see any errors to look at...

[eytan321]

sorry.

the files are here now.

thank you!

[Kyle97330]

Any chance you can post the actual VIs that are causing the problem?  It's kind of hard to see a lot from pictures and video.

Best I can tell it looks like you're trying to open an ActiveX reference and failing.  Any chance there's a 3rd party program open that might be using it?  Or maybe you open a reference to it so many times it causes a problem and you're not closing the reference later?

Also, at one point in your video I thought I saw two event structures in one loop.  If so, that's generally but not always a bad idea...

[eytan321]

Hi.

See attached the function that i have problems with. it's the IStageGetPosition.vi .

I tried to contact PRIOR, but they told me they do not support and can't help me... 😞

In addition, I attached also my code, but i'm sorry in advance - i started it when i was completely new on Labview, so it has many bugs. If it doesn't open properly, I'll try to see if i have a newer version of the code on the computer in the lab.

Thank you very much! Appreciate it 🙂

Ethan

[Kyle97330]

In the VI where you open the reference, can you change it to be like this:

(The False case just sends the wire straight through)

The reason is that each time you open it, it actually makes a different copy of the reference.  So after a long time, you have a gajillion copies of the reference and it can't handle it any more.  Here's a quick illustration of opening 5 in a row:

You can see that each time it runs, it is actually a different reference under the hood, even if to LabVIEW they all act the same.

You could also open the reference one time outside of all of the loops and pass it in to the loops one time each, so it's not created over and over.  That's a bit more work and requires more wiring spaghetti, so it's your call.

[eytan321]

Thank you very much!!!

I won't be in the lab until Tuesday (because others are using it for their own measurements... we are a group of students in the same lab), but as soon as I'll be back in there i'll let you know.

Thanks again 🙂

Appreciate a lot.

[eytan321]

hi. i'm truly sorry for the late answer.

due to personal issues i didn't work at all in the lab the past three weeks...

i tried what you said, and it didn't work - not because it wasn't good, but because now it makes an error in the next VI (IStageGetPosition.vi).

i receive a 'ERROR 97' - see pictures attached. it's the same error i was receiving after a while in the previous configuration of the code...

is there anything to do to fix this problem?

i tried also an idea i got - also a form of a feedback loop, but this idea was even worse - i got a broken arrow 😞

thank you