could not perform this operation

[tavwtby]

I have a vi(attached) that I improved upon from the previous version I did, which worked fine. The only improvements were two new inputs for torque, and displaying them on a graph and indicator. The executable runs great and only uses about 2-8% of CPU usage, and thats with task manager open and an excel file also. After a few hours I get an Out of memory error, could not perform this operation. I read through the other related threads and I'm not seeing any thing in those threds that apply to my situation. At least I dont think so. Could someone please browse through my VI and tell me where this is coming from and why now is it happening. I tried adding the flush queue and creating sub vi to optimize but to no avail.

[Taki1999]

I think you may be getting hit with a problem with too many controls or too large of a block diagram.

Have you been through the LabVIEW Tutorials?

There are a lot of potential problems with your VI.

[tavwtby]

I took core one and this vi was working fine prior to me adding the torque input. I am starting to think I need to clear the plots every hour or so. Would I be correct in this thinking?

[Taki1999]

---

@tavwtby wrote:

I took core one and this vi was working fine prior to me adding the torque input. I am starting to think I need to clear the plots every hour or so. Would I be correct in this thinking?

---

Are you talking about the torque slope and intercept inputs for Rig 1 and Rig 2?

I would seriously consider using clusters on your UI.

[Taki1999]

You're running sample compression on a single scalar.  Why?

[tavwtby]

It was code I had copied from another program that used it to calculate the cycles per minute, it seemed to work,  would like to do it better, but couldn't figure out a way of converting the analog signal from th prox switch into a single cycle count.

[Taki1999]

I don't think your problem is with your Chart.

I'd focus some attention inside your Record Loop and see if you're leaving something open or growing an array to extremely large sizes.

This VI is a good candidate to refactor and make manageable.  While it may work now, there's a lot that needs to be done to make it maintainable.

[Taki1999]

Your Shift Register Arrays in your top loop grows uncontrollably if the Reset button is not pressed.  This will also cause you to crash out if your number of points grows too large.

[tavwtby]

I have to keep the values of the cycles and the displacement current, other wise it would reset my position and cycle count, which would defeat the purpose of my test, I a very open to suggestions. I am a test emgineer that was thrust into the programming role, so I am learning as I go here. I do appreciate the help and suggestions. So tell me more.

[tavwtby]

Also I am not recording unless the button is pressed to do so, and I've used this record loop in the past and never had a problem, in fact this program was running great until like I said, added two torque analog inputs and changed the load inputs from the strain daq to the analog in daq