Hello all. We have a Yokogawa WT1600 Power Analyzer and we are using the Labview program for it from NI. We integrated the NI Labview program into our own Labview program so we can show the values we desire. We have run into one major issue however. Our program pulls the values we want from the WT1600, but for some reason, the WP value is not correct. Between the instrument and Labview, the values are way off. Our program pulls 10 values from the WT1600, and the program shows the exact same numbers that are displayed on the Wt1600 screen -- except for the WP value. These are so far apart it doesn't make sense.
We spoke with Yokogawa, and the tech there said the NI Labview program might be doing some initialization changes that are causing the program and instrument to show the strange values. However, they could not help me with troubleshooting the program, so I am coming here. I've dived into the program, and I THINK I've found the offending area, but the problem is that I don't know what to change here. Can anyone offer any ideas as to what to do?
Attached is the program with some pictures. The Wt1600 pic shows the screen of the WT1600 taking a measurement for 1 minute 10 seconds. The labiew-wt1600 pic shows our program. The program ran for 1 minutes 12 seconds. We tried to get them to stop at the same time, but as you can see we were a little off. The issue is WP Sigma A. You can see that the WT1600 and Labview program values are vastly different. This is what we don't understand. The program ran for (roughly) the same amount of time, with the DUT in the same state, so why would the values be so different? We could not run the WT1600 and labview program together, as the program takes control of the instrument. So we had to run them in sequence: WT1600 first, then clear everything, then run the program next.
The picture labeled "screen change" shows what happens when we run the Labview program. As you can see, the screen totally changed from the WT1600 pic. Now we can't see what the WP value is on the instrument. The problem with this is that we can't compare values to see if Labview is reading correctly. We trust the instrument, so the issue is why is Labview not showing a corresponding value. There is a big difference between 829.7 mWh and 0.004568 mWh when the DUT is in the same state and the instrument and program ran for (roughly) the same amount of time.
Ok, so now for the possibly "offending" code. If you open the program and look at the "Config Voltage" or "Config Current" subVIs, keep going down into them and about three levels. You should come to a TCPIP Write. I think it is here that the issue occurs. Somewhere here, the program makes the WT1600 screen change over to the "screen-change" pic. What is causing it? I can't pinpoint it. If I use Highlight Execution at about this point, errors occur and the program doesn't run right.
There is also the possibility that the initialization isn't the issue at all. The Yokogawa tech just believed this is a possibility, so we'll start here.
Whew! I've said a bunch and probably missed giving you something important, so please question away. Thanks for any and all help.
