Can't communicate with Agilent 34401A Multimeters anymore

[Daron]

Hey!

Just go to file in you labview window when the program is opened then save in previsous version. You'll be asked to save it in 7.1 version or more prvisou if you wish (7.0, 6.1...)

You will just have save it in 7.1 and it will be done for you and our poor Dennis who has only the 7.1 version

[carolyne]

Sorry when I don't check stars you're not happy and when I do too.

It's very difficult to check an answer like this one... And when you tick you can't modify your choice afterwards...

[carolyne]

Sorry Daron,

I see what you mean but I have no choice to save the VI in another version I can just save it as All files, VIs or Template VIs...

[Dennis_Knutson]

I really don't care if you check stars and I have never asked anyone to do that or indicated that I'm unhappy when I don't get a rating. Personally, I tend to give either 5 stars or none at all though I occassionally find some posts and answers offensive. The little angry smiley was meant as a joke and if you noticed, I did answer on how to save for previous version. I also noticed that you haven't done this yet. I am really curious as to how it was working in one post and then stopped working again.

[Daron]

Hey buddies take it easy lol!!

Actually Dennis you wrote with such a small size we didn't see it

You were right, but as for me Carolyn in LabVIEW 8.0 to save in previous version, do : 

"file"  then  "save for previous version" and then the choice is up to the user...

I apologize I made you doing something wrong when saying "save as"... Now it is good, I hope so...

Daron

[carolyne]

Ok guys it's done !

Sorry Dennis I didn't see your answer ;).

So you will find the example from Agilent to read multiple measurements. I think the problem is in the initialize vi since the error is "Error -1073807339 occurred at VISA Read in Agilent 34401.lvlib:Error Query.vi->Agilent 34401.lvlib:Reset.vi->Agilent 34401.lvlib:Initialize.vi->Agilent 34401 Read Single Measurement.vi" (corresponding with a timeout error)...

Thanks

[Daron]

I have tested your VI with my multimeter same like yours (HP34401), and it works...

I just had the problem of getting all the sub-VI included in cause those weren't in the good folders.

So i have saved it again but with the files of my labview folders. If it doesn't work anymore for you, that might be cause some files have been moved from the folders where labview refers to other one and when opening your program labview don;t find them.

Then you have just to check your sub-VIs manually (labview is checking them by itself but if those aren't in the good folder iit doesn't find them. It givers you anyway the name of the missing file, then find it and replace it. When all the files are replaced, labview will say to you it didn't find the files in the right place. Thus,just save your program, then it will works again

Hoping this is what you needed.

Daron

[carolyne]

Daron,

I've opened your VI and tried to make it work but it doesn't...

The error is still : Error -1073807339 occurred at VISA Read in Agilent 34401.lvlib:Control Mode.vi->Agilent 34401.lvlib:Initialize.vi->Agilent%2034401%20Read%20Multiple%20Measurements[1].vi
 and my multimeter displays an error as well....

I don't know what to do anymore I can work without my multimeters...

[carolyne]

Daron,

I've find this in the error query.vi where the message indicated me the error the first time, maybe there is a link with my problem... Can you set me straight about this ?

"Device Clear must be called after a timeout to stop the current operation and flush the computer's input buffer.  This allows the results of the Read STB call to be read appropriately.  Read STB checks to see if the Event Status bit is set.  If set, there is an instrument error so proceed to sending error query command.  If the Event Status bit is not set (no instrument error), return the timeout error that was passed into this VI."

"Check if error is timeout.  If so, then check if instrument
reports an error.  If instrument reports an error, best to
report instrument error since probably a syntax error
in a query command sent to instrument.

If instrument doesn't report an error, then best to
report the timeout error since probably a true timeout. "