Wt1600 - Labview changes instrument screen

[RTSLVU]

Here's the drivers Yokogawa ykwt1600 Meter LabVIEW Plug and Play Instrument Driver

Just download the one for your LabVIEW version...

BUT I do not think this is your problem, as I noted above you are reading the PRESETS but your are NOT setting the preset measurements anywhere in the program you uploaded.

So you are getting the defaults or the presets someone before you set.

[Dhouston]

Hey RTSLVU.

Thanks for your input.  I went to the link you gave.  However, I do not see a 2019 version of the driver.  I see 2018 and 2021.  How did you get a 2019 version?

The 2021 version has the Read Numeric Normal VI you mentioned.  Blast.  How can I get it?

[RTSLVU]

---

@Dhouston wrote:

Hey RTSLVU.

Thanks for your input.  I went to the link you gave.  However, I do not see a 2019 version of the driver.  I see 2018 and 2021.  How did you get a 2019 version?

The 2021 version has the Read Numeric Normal VI you mentioned.  Blast.  How can I get it?

---

Use the 2018 version

[Dhouston]

Ok, I changed the Read Preset Normal to Read Numeric Normal as you stated, but this gave a very weird operation.  The Integration did not do anything, and most of the other values were wrong.  See attached pics.

I used a case statement with a control so I could switch between the original Read Preset Normal and Read Numberic Normal VIs.  I had the subVI containing these two VIs open when I ran the program, so I was able to make sure the program was using the correct one.

[RTSLVU]

Well there are actually a couple steps you have to take to set up the instrument first.

1. Configure measurement ranges ect...
   1. Use the appropriate config VIs
2. Configure the Measurement List
   1. Use "Config Numeric Normal.vi"

Now when you want to take a measurement use "Read Numeric Normal" and it will return the measurements in the order you configured using Config Numeric Normal.vi

I have examples but they are rather complex as our ATE stations have WT-500, WT-1600 and WT-1800 power analyzers. So my programs have to support all of them 

[Dhouston]

Ok, putting the Config Numeric Normal VI in at least got all the values showing again, but the Integration is still wrong.  I believe I have the Config Numeric Normal vi set up correctly, except I don't know what "Item Number" is.  Can you tell me what this value is?  I left it at the default "1".

So I'm still getting a WP value of 0.004 when the instrument shows 800+mWH.  

I did have a thought.  The WT1600 pics I have shown you (the ones that show 16 items) is done through a setup program that was developed between former employees and Yokogawa.  I don't understand the specifics of that program, other than it allows for the displaying of the 10 items that we want out of Preset 4.  Could something here be also causing the drastic differences between what Labview shows and what the instrument displays.

Oh, I believe I know why we don't have the latest version of the driver.  The driver is normally setup for GPIB access, but we use Ethernet. At the time we downloaded this (which I believe was in 2017), the NI Application Engineer at the time actually took the driver and changed it to work for Ethernet.  I know NI doesn't do this kind of thing now (especially for a non-supported driver), but it was done then.  So the program works for our Ethernet uses.  All the driver versions on NI's website are set up for the GPIB access, and I don't know what changes that NI App Engineer made to make our version work.  So that's why we have the version we have.  If I download any version for the website, it will be the GPIB version, and I can tell you from two attempts that simply changing the input from GPIB to TCPIP didn't work.  That engineer must have done something deeper to make this thing work.

[RTSLVU]

---

@Dhouston wrote:

Oh, I believe I know why we don't have the latest version of the driver.  The driver is normally setup for GPIB access, but we use Ethernet. At the time we downloaded this (which I believe was in 2017), the NI Application Engineer at the time actually took the driver and changed it to work for Ethernet.  I know NI doesn't do this kind of thing now (especially for a non-supported driver), but it was done then.  So the program works for our Ethernet uses.  All the driver versions on NI's website are set up for the GPIB access, and I don't know what changes that NI App Engineer made to make our version work.  So that's why we have the version we have.  If I download any version for the website, it will be the GPIB version, and I can tell you from two attempts that simply changing the input from GPIB to TCPIP didn't work.  That engineer must have done something deeper to make this thing work.

---

Hmm... That really doesn't make much sense as their LabVIEW drivers use VISA so nothing should have to change as far as the driver for Ethernet or GPIB or even serial. As once you open a VISA session it's the same regardless if that VISA session is for GPIB or Ethernet.

But I digress...

---

@Dhouston wrote:

Ok, putting the Config Numeric Normal VI in at least got all the values showing again, but the Integration is still wrong.  I believe I have the Config Numeric Normal vi set up correctly, except I don't know what "Item Number" is.  Can you tell me what this value is?  I left it at the default "1".

So I'm still getting a WP value of 0.004 when the instrument shows 800+mWH.  

You are either not configuring the measurement list properly or requesting the wrong measurements.

I need to see all of your code and maybe I can figure out what you are doing wrong.

[RTSLVU · Accepted solution]

Here's a simple example I found from a program that monitored a 3 phase grid tie solar inverter, I was also measuring Watt hours using the integrator function to get daily "solar harvest" numbers...

First I configure the WT-1600 for the measurements I want to take

The main part I want you to see is I put Config Numeric Normal in a nested For Loop because you have to list every measurement for every phase in the order that you want to retrieve when you request later.

When I take a measurement I use just YKWT1600 Read Numeric Normal.vi

The "Number of Items" is 64 because my "measure list" was 16 individual measurements times 4 (3 phases plus Sigma A)

I also reshape the 1D 64 element array into a 2D 4x16 because it was easier to display that way...

Every night at midnight I would reset the integrator.

[Dhouston]

Wow!  That's some fantastic stuff you have there!  Thanks for that!

You said you would need to see my code to see what I am doing wrong.  I attached the project in the zip file.  Everything is in there, or so I thought.  Did something not appear when you looked at it?

Egads.  I see that perhaps I don't understand this driver as much as I thought.  So I have to put Config Numeric Normal in a loop?  I sure didn't know all the specifics of that vi.  Ok, I'll work on this and see what happens.

I had some questions on some things I see in your example:

1.  How did you form the"Element 1, Element 2, Element 3, Sigma A"  array.  When I clicked on the terminal I chose "Create constant" and got a list of measurements to choose.  I could only choose one.  How did you expand that to get more than one?

2.  Considering that I arrange the data to be displayed like I want, would I need the Config Display Format vi?

3.  This question is not example specific.  You mentioned that I was possibly not configuring the measurement values correctly, or not setting the measurements as the reasons my WP value is incorrect.  Can you tell me how is it that all the other values I getting are correct?  If I am setting something wrong, shouldn't it affect all the other values as well?  I am asking this to attempt to understand what the program is doing with the values I seek.  Is it changing something, or am I doing something wrong with what it is giving me?

I really appreciate your time and help here.  I've never been so close to finally solving this.  

[RTSLVU]

---

@Dhouston wrote:

Wow!  That's some fantastic stuff you have there!  Thanks for that!

You said you would need to see my code to see what I am doing wrong.  I attached the project in the zip file.  Everything is in there, or so I thought.  Did something not appear when you looked at it?

---

Sorry I didn't realize that you were modifying the examples and using similar names.

---

@Dhouston wrote:

Egads.  I see that perhaps I don't understand this driver as much as I thought.  So I have to put Config Numeric Normal in a loop?  I sure didn't know all the specifics of that vi.  Ok, I'll work on this and see what happens.

I had some questions on some things I see in your example:

1.  How did you form the"Element 1, Element 2, Element 3, Sigma A"  array.  When I clicked on the terminal I chose "Create constant" and got a list of measurements to choose.  I could only choose one.  How did you expand that to get more than one?

---

Egads is right! If you don't know how to create an Array Constant on the block diagram you might want to consider taking or revisiting some of the free LabVIEW tutorials.

---

@Dhouston wrote:

2.  Considering that I arrange the data to be displayed like I want, would I need the Config Display Format vi?

---

That depends on if you want to see certain things in certain places on the WT-1600 display.

---

@Dhouston wrote:

3.  This question is not example specific.  You mentioned that I was possibly not configuring the measurement values correctly, or not setting the measurements as the reasons my WP value is incorrect.  Can you tell me how is it that all the other values I getting are correct?  If I am setting something wrong, shouldn't it affect all the other values as well?  I am asking this to attempt to understand what the program is doing with the values I seek.  Is it changing something, or am I doing something wrong with what it is giving me?

---

There's so much going on here... But basically you are not retrieving the measurements in the order that you think you are... 

If you setup all your measurements in the order you want them like I do using Config Numeric Normal you will be able to keep things straight and you can avoid making a mess like you did here...