Hi LAVAs!

I've a monitor program for some motors. Basically, it stops the motors when there's an error, and logs the status of the motor every 1 sec.

When I ran it overnight, and checked the logfile next morning (while it was still running), I found that there is a 13 hour interval with no data recorded. Apparently, the data logging resumes after I come back.
I've checked the hibernation/standby setting in Windows and it was set to be Always On.

I've attached the screenshots of the simplified version of my programs here.

Thanks in advance for any comments!

Raymond

Is the (network) drive available during the night?
You could try the same approach to log data on the FP (once every 15 minutes or so)
Maybe your computer is set to hibernation by some group policy?
Do you log the user off? (or does this happen automatically?)

Ton

Thanks for your reply!

1. this is the local drive.
2. what is FP?
3. i've checked the settings on the screensaver page. i guess that's the only place i can set hibernation policy, right?
4. no. when i came back to the computer, the user is still logged in.

FP=Front Panel

OK. Thanks, JiMM!

I will try to write the log to a text field on the front panel. (i suppose this is what you suggest, Ton?)

What about some power saving settings
(e.g. switch off the hard disks) in the BIOS?
Do you get any error message from LV?

G

Let me check the BIOS.

I got a "Generic File IO error" from LV.

I obviously spend waaaaay too much time using RT as I read this as compact Field Point, but front panel makes much more sense.

It seems like a very interesting problem.

Just a thought, but you stated that you checked the hibernation settings on the power options page accessed through the display properties page. did you also check that "system standby" and "turn off hard disks" on the "power schemes" tab were both set to never?

As to the group policys concern that a fellow member has raised, is your computer part of a domain?

Is you disk set to power down after a timeout? (ie: powersave) Can you post the code? Or at least a screenshot of the general area where the error is generated?

Thank you all for your comments!

1. I've checked that all the stuff hibernation/powersave/hdd turnoff/... are set to never.

2. My computer is not in a domain.

3. i didn't try to write to FP, but if i disable file io at all, it runs smoothly.

In fact, I have just successfully run the vi overnight (20+ hours). But the computer has become very irresponsive.
I checked the task manager to see that labview is using >110MB of RAM. Does it look like a memory leak or sth like that?

Are there any memory leak checkers (like Valgrind) for LabVIEW?

Ray

This post has been edited by Raymond Tsang: Aug 21 2008, 09:48 PM

I think the problem i have is memory leak.

I turned off (using a case structure wired with a FALSE) each component of the vi one by one and look at the "Profile performance and memory" found that, the leak comes from a "Cluster to Array".

Now the problem is how to convert a cluster to an array without using "Cluster to Array"???

Puzzled Ray

This post has been edited by Raymond Tsang: Aug 22 2008, 12:48 AM

What is the history length of your "Load Cell2" waveform graph? Could that be the reason your vi is becoming sluggish as you add more points?

I would be surprised to discover a memory leak in Cluster to Array.

Even if I unwire the graph, the leak is still there.

In fact I found whenever I convert the cluster into a string for writing to file in "datalogger", i have a memory leak in the "main program" as seen in "profile performance and memory". I tried the following things:
1. Unbundle cluster, cluster to array, array to spreadsheet string
2. Unbundle cluster, format string
3. Cluster to array, array to spreadsheet string, concatenate strings
4. Number to fractional string, concatenate strings,
and other permutations.

All leaking...

Is the passing of a cluster to the datalogger from the main program causing it?

Ray the Leaker

This post has been edited by Raymond Tsang: Aug 22 2008, 10:03 PM

Could you post your VIs? (Not just screenshots)
Maybe we can find an explanation if we try it first hand...