Basic voltage measurement, with Meter, Relay, and Load. How do I make it work?

[Ben_7128]

Hello,

I have LV2010, and I am controlling a Meter, Relay, and Load.

Here is what I need.  Please give me any crazy idea that you can think of to explain why this will work all day and then after shift change it hangs, and locks repeatedly.

I have looked at our LAN, and Server usage.  The second shift operator likes to wear nitrile gloves so we asked that he take them off and that seamed to help but didn't solve it.  I have stood and watched both operators and their methods seam to be the same.  I can operate the test for a dozen cycles and it is perfect, then he takes over and it locks on the second cycle.

The program is very simple with a loop that calls the subvi for the equipment and then records the data for a service to push to the server.

So after you laugh at what a poor post this is, please give me any off the wall idea you have because it isn't making any sense to me.

Thanks,

Ben P.

[ABCPrograms]

it doesn't seem to have something to do with the code?  But still, are you able to post the VI in here so we can have a look at it and check some possible dependencies or what ever?

Kick the second operator out and hire a new one? 😄

[Ben_7128]

Hello again,

Here is the code.

OCV-CCV Test is the main program

OCVF is the Fluke control subvi

CCV is the BK Load control subvi

4x4 Relay Control is well the relay control

A xml configuration file is read for what subvi's to call and what limits to set.

The relay is the most trouble.  It will send the command to set 1 thru 4 and the relays respond but never turn on. If you see a better way to talk to them please let me know.

Other times it just seams to lock even with the "Status" window updating at every turn I can't see why it would lock during a instrument read one time and not the next.

Again thank you for the help.

[tbob]

Sorry I don't have time to look in great detail at your code.  But I would like to throw out one suggestion.  You have a lot of blank space in your block diagram.  You have to scroll across the screen a whole lot.  This makes it hard to look at the code and to understand what it does.  Make it easier for others to read by eliminating the blank space and moving objects closer together.  I have two monitors side by side and I still can't see all the code without scrolling.

[RavensFan]

---

@tbob wrote:

But I would like to throw out one suggestion.  You have a lot of blank space in your block diagram.  You have to scroll across the screen a whole lot.  This makes it hard to look at the code and to understand what it does.  Make it easier for others to read by eliminating the blank space and moving objects closer together.  I have two monitors side by side and I still can't see all the code without scrolling.

---

Something is wrong with that block diagram (looking at OCV-CCV.vi).  I ran the block diagram cleanup on it, and it stretches out a lot of structures very wide even when they hardly have any code in them.

It would be good if someone from NI can look at that VI and see if they get the same results and figure out why the cleanup tool is failing on this one.

Ben P, you are missing alot of subVI's and typedefs.  You may want to create a source distribution and upload a zip file of that so we can see all the files.

Look at the event structure in your Wait Case.  You have a Run:Value change event and Change Info:Value change event.  Both of those have their event properties set to lock front panel until event completes, but yet the event may not complete right away since the event structure is inside your state machine in a case that may not be up for execution right away.

[Ben_7128]

I have wondered about the BD Cleanup and why it spread it out so much, but thought it was just the way it was.

Can you recommend a better way to keep from spreading accross like it does?  I would like all the pointers I can get.

Here are the rest of the files.  I don't understand what you mean about the Event cases.  Please point it out and help me make it better.

[RavensFan]

I have no idea why BD cleanup does that to your VI.  I had not seen it to that until I saw it do it to some of your VI's.

Here is the part about the event structure.  Try unchecking that.  There were at least a couple event cases that were set that way.

[Ben_7128]

Ok, I see them now.  I really do need to learn Event Structuring because I don't understand it at all.

That said, I don't use this part of code at all.  None of my .ctl's point to that "Wait" case.

Can this affect my program given that it isn't used?  I don't want to seam like I know more because I don't.  I would just remove the whole case seeing that I don't use it.

Thank you,

Ben P.