LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Yokogawa Data Collection

I've been working on this code to collect data from our yokogawa WT1800 power analyzer. It all used to work really well and then has since stopped working and I'm not sure why. From what I can tell the first VISA that calls to the yokogawa is returning with and error code -1073807346 that says "VISA Open in Yokogawa WT1800E Series.lvlib:Initialize.vi". It used to have no problem calling it up and I don't recall changing anything to do with this part of the code anytime recently. Any help would be appreciated, still somewhat new to Labview as a whole. I'm using 2019 Labview if that makes any difference.

0 Kudos
Message 1 of 11
(1,710 Views)

Sounds more like a hardware issue. Is the device connected correctly?

 

I don't have any of your drivers, but what is the output of the "find yoko" VI? Can you probe that?

 

(What's the point of the initialize state? does not do anything? Why is there s a wait in the lower outer loop? The mechanical action of "stop and save" seems unusual. I recommend to use the boolean text to label the button functions)

0 Kudos
Message 2 of 11
(1,694 Views)

We would need your Yokogawa subVIs to troubleshoot, but this is a standard VISA error indicating that the instrument is simply not connected.  Do you know how to use NI-MAX to check it?  Your first step is to get the instrument to respond to the *IDN? command.  If it can't do that in NI-MAX you need to figure out why.

 

Is there some other program or utility that might be communicating with your instrument? 

Have you confirmed all your wiring is tightly connected?

Could you have accidently changed a GPIB address or Serial port parameter on the instrument?

 

LabVIEW Pro Dev & Measurement Studio Pro (VS Pro) 2019
0 Kudos
Message 3 of 11
(1,691 Views)

I'm leaning towards it being a hardware issue as well. We've had connection issues in the past but replaced the Ethernet cable and it seemed to fix it until now. The find yoko VI normally would output the reference to the Yokogawa but currently doesn't output anything other than the error code. I appreciate the advice, I'm still getting into Labview and just trying to learn as much as possible.

0 Kudos
Message 4 of 11
(1,688 Views)

We recently bundled our yokogawa into a testing cabinet. The people who designed and made it could have messed with some internal settings to get it to talk to the screen and rpm tester they connected. I'll start checking out the yokogawa's settings to determine if anything regarding ethernet connection has been changed.

0 Kudos
Message 5 of 11
(1,687 Views)

Can you open up NI-MAX on that PC and look under the "My System → Devices and Interfaces → Network devices" section and see if there is something there that looks like a connection to the Yokogawa?

 

In theory it would look something like:

WT1800 "TCPIP0:192.168.12.34::inst0::INSTR"

 

If you do see something like that, do you see a red X on it?

 

If there's an entry with an X on it that means that it was formerly findable at that address but is no longer there and you will likely need to resolve it by either changing the device IP or resolving whatever other issue is stopping that connection from being usable.

 

If there is no entry you may need to add one.  You can see if you can find the IP address in the menus on your device, or try right-clicking the "Network devices" section heading to add a new one and hopefully it will autodetect it.

 

If none of that seems to apply, then knowing the contents of the "find yoko" VI is quite important, and what it outputs when it runs.

0 Kudos
Message 6 of 11
(1,643 Views)

I have seen times that using NI-Max, customer provided software, or even an unexpected exit from your LabVIEW program could leave the original open to your instrument hanging.  My suggestion is to exit out of NI-Max and any other software that controls or monitors your Yokogowa instrument including LabVIEW.  Now, open LabVIEW and run the close.vi on that connection.  It should be fine and NOT present an error.  Now your program should work when you run it again.

Help the Community (and future reviewers) by marking posts as follows:
If it helped - KUDOS
If it answers the issue - SOLUTION
0 Kudos
Message 7 of 11
(1,636 Views)

I actually have a lot of experience with this exact power analyzer but all of your sub-vi's are missing so I can't really help you. 

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 8 of 11
(1,605 Views)

one place to start is the Find Yoko.vi that produces the VISA resource

CY (expired CLAD)
0 Kudos
Message 9 of 11
(1,550 Views)

It is possible that your hard drive may be having issues and either corrupted the lvlib or has bad sectors.

 

  1. Are you able to open the Find Yoko.vi (Finds any available Yokogowa scopes and returns the VISA Address for that Instrument)?
  2. Can you run that VI as a stand alone?

 

Your answer would have been shown to you as the blank boxes in your Block Diagram if that was the solution and would have been revealed during Altenbach's initial post.

Help the Community (and future reviewers) by marking posts as follows:
If it helped - KUDOS
If it answers the issue - SOLUTION
0 Kudos
Message 10 of 11
(1,541 Views)