Wt1600 - Labview changes instrument screen

[Dhouston]

Hey, I'm still working on this.  The PC I've been using is being used for other projects, so I've been sidelined a bit.  I'm incorporating the additional subVIs you have shown and getting them configured with the desired values I wish to see.  I hope to be able to test this soon and see how it works.

On the Config Numeric Normal, where you have the array constant with the 16 values listed horizontally, since there are only 10 values I am wanting to see, will I just use those 10 values, or do I have to put all of them in?  I believe you answered this, but I am wanting to be sure I am understanding it correctly.

I will be setting up a 8x2 array for displaying the data, so instead of the 64 items you had in the Read Numeric Normal, I think I will be using 30.  Am I thinking of things correctly?

[RTSLVU]

---

@Dhouston wrote:

Hey, I'm still working on this.  The PC I've been using is being used for other projects, so I've been sidelined a bit.  I'm incorporating the additional subVIs you have shown and getting them configured with the desired values I wish to see.  I hope to be able to test this soon and see how it works.

On the Config Numeric Normal, where you have the array constant with the 16 values listed horizontally, since there are only 10 values I am wanting to see, will I just use those 10 values, or do I have to put all of them in?  I believe you answered this, but I am wanting to be sure I am understanding it correctly.

I will be setting up a 8x2 array for displaying the data, so instead of the 64 items you had in the Read Numeric Normal, I think I will be using 30.  Am I thinking of things correctly?

---

Yes, put just the measurements you need in the array Constant.

Number of Items is the total number of measurements you want to retrieve.

So if you configure 10 measurements on 3 elements then Number of Items=30 would be correct.  

[Dhouston]

Hello again all.  I've finally got a chance to briefly get on this again.  Ok, so I've incorporated the additional subVIs and made a debugging array named "output array" to test how things go.  

Hmm, it seems either I still didn't configure something correctly, or I'm not pulling in exactly what I need.  "Output Array" does appear to get the 6 values for each element as I listed them in the array constant in the Initialize state, but I don't think the Sigma A value is being shown.  Did I still configure Configu Numeric Normal incorrectly?  I still have the 146 element array available for reference (although I am only taking 30 values from it), and I don't see anything in there which seems to be a Sigma value for WP.  

The attached picture in the zip file shows an Integration screenshot.  As of now the Power Analyzer Cluster is irrelevant, as I'll have to rearrange what is shown to my liking, so "Output Array" is all we need be concerned with right now.

[RTSLVU]

I don't think you understand how Arrays work...

This is what you have configured

Element 1	Element 2	Element 3	Sigma A
Urms	Urms	Urms	Urms
Irms	Irms	Irms	Irms
P	P	P	P
Wp	Wp	Wp	Wp
I-Time	I-Time	I-Time	I-Time
Freq U	Freq U	Freq U	Freq U

The Array returned by "Read Measurement Normal"  will be a single dimension array containing the measurements you configured in this order.

Urms 1

Irms 1

P 1

Wp 1

I-Time 1

FreqU 1

Urms 2

Irms 2

P 2

Wp 2

I-Time 2

FreqU 2

FreqU 2

Urms 3

Irms 3

P 3

Wp 3

I-Time 3

FreqU 3

Urms A

Irms A

P A

Wp A

I-Time A

FreqU A

But you then reshape this into a 2x8 array that will only contain the first 16 measurements out of the 24 you configured

Urms 1	P 2
Irms 1	Wp 2
P 1	I-Time 2
Wp 1	Freq U 2
I-Time 1	Urms 3
Freq U	Irms 3
Urms 2	P 3
Irms 2	Wp 3

[Dhouston]

Wow, I greatly appreciate how you broke that all out.  Whew!  Yeah, I did not at all think through how the embedded For Loop was putting out data.  You did some great simplification for me by showing me all I was getting.

I broke out my arrays to be the same format as what you showed.  So Output Array should show the 6x4 array that is the 24 element configuration you gave.

I added a 1-D array in Application Example2 that shows the configured data just as you showed.  I do see that you show two FreqU 2s in the 1-D array.  Is one of them a typo, or is this correct?  The data doesn't show two frequencies when I run the program.

All this definitely lets me see what I am getting.  Fabulous work you did here!

However, I have seen that the WPA value I am getting is the same as WP1.  I can not understand this.  There should be no way that the Sigma of the elements is the same as the 1st element since WP2 and WP3 do not cancel out.  Why are WP1 and WPA the same number?

[Dhouston]

Added the project

[RTSLVU]

---

@Dhouston wrote:

However, I have seen that the WPA value I am getting is the same as WP1.  I can not understand this.  There should be no way that the Sigma of the elements is the same as the 1st element since WP2 and WP3 do not cancel out.  Why are WP1 and WPA the same number?

---

Hmm... I really don't know the answer to that but. What I would to in this case is check the display and compare the display WPA to the WPA you are reading through LabVIEW. If they are the same then it's a configuration issue, it the displayed is correct and the LabVIEW is wrong then it's a program issue.

There's a couple thigs that can effect the Sigma channel and how it is calculated internally. 

1. Section 5.1 Selecting the Wiring System
2. Section 6.5 Setting the Delta Computation

Also check your setup and make sure your voltages and current measurements are phased properly.

[Dhouston]

Thank you.  Ah, you mention one point that is my biggest problem with trying to correlate the Labview program with the WT1600:

"What I would to in this case is check the display and compare the display WPA to the WPA you are reading through LabVIEW. If they are the same then it's a configuration issue, it the displayed is correct and the LabVIEW is wrong then it's a program issue."

This is my biggest hurdle from the start of working with this thing.  Since the program takes control of the instrument I could not get the instrument to show the WPA at the same time the program ran.  Thus, I could never compare the two.  Is there a function that allows me to change the instrument screen to show what I want?  I looked at the Config Display Numeric vi, which seems to have the same inputs as the Display Format vi,  but I'm not sure this vi is what I should use.   If it is, I think an embedded For Loop should solve it, like how it works in the example you showed me.

What you showed in that 2x8 table is roughly how I need the instrument screen to appear.  It would be as simple as saying "Transfer this labview screen to the instrument screen", but I'm not sure how to actually code that.

[RTSLVU]

---

@Dhouston wrote:

Thank you.  Ah, you mention one point that is my biggest problem with trying to correlate the Labview program with the WT1600:

"What I would to in this case is check the display and compare the display WPA to the WPA you are reading through LabVIEW. If they are the same then it's a configuration issue, it the displayed is correct and the LabVIEW is wrong then it's a program issue."

This is my biggest hurdle from the start of working with this thing.  Since the program takes control of the instrument I could not get the instrument to show the WPA at the same time the program ran.  Thus, I could never compare the two.  Is there a function that allows me to change the instrument screen to show what I want?  I looked at the Config Display Numeric vi, which seems to have the same inputs as the Display Format vi,  but I'm not sure this vi is what I should use.   If it is, I think an embedded For Loop should solve it, like how it works in the example you showed me.

What you showed in that 2x8 table is roughly how I need the instrument screen to appear.  It would be as simple as saying "Transfer this labview screen to the instrument screen", but I'm not sure how to actually code that.

---

Well what you can do is:

1. Pause your program at a steady state.
2. Press the "Local" button on the WT1600 to regain manual control.
3. Scroll through the measurements on the WT1600 and compare them to the last measurements taken.  

[Dhouston]

Magnificent.  Just magnificent.  I had no idea I could actually regain control of the instrument while the program was running.  I can work with this.  Oh RTSLVU, where were you those 6 years ago when I still had hair left before dealing with this? 🙂

Ok, I think at this point things are more on the instrument side than the Labview side, so I will close this topic and work with things there.  I thank everyone for their help, especially RTSLVU for sticking it out with me.

If something comes up long after this I'll open another topic to ask for more assistance, but I think I'll be hibernating with the solutions presented here for quite a while.

Thanks again.