LabVIEW stops suddenly and in aleatory way after some days

[frferrelb]

Hello everybody,

We create in my laboratory a LabVIEW program controlling pumps, flow meters, pH, and oxygen dissolved probes for microalgae cultures in a photobioreactor. After 4-5 days of working well, we observed that the LabVIEW program stops without showing an error (it still possible to browse in the program), and the only way to close or restart the program is by forcing it. We reviewed the code and everything look ok but we still have the same problem. Do you know what could generate a problem like this (I'm surprised that LabVIEW doesn't show me an error and however it crashes)? Could the problem come from the RAM capacity or from the processor of the PC?

Thank you in advance for your help!

[GerdW · Accepted solution]

Hi frferrelb,

---

@frferrelb wrote:

Could the problem come from the RAM capacity or from the processor of the PC?

---

Maybe. Probably. Perhaps.

How should we know when we don't know your VI(s) nor your hardware setup?

---

@frferrelb wrote:

After 4-5 days of working well, we observed that the LabVIEW program stops without showing an error

---

In an executable there will be no automatic error handling. And maybe you even switched that off for your IDE. Maybe you implemented a basic error handling, but forgot to handle/log all errors.

Who knows…

[RavensFan]

What word is "aleatory" supposed to be?

[NIquist]

---

@RavensFan wrote:

What word is "aleatory" supposed to be?

---

🤔 I have a pretty good vocab but have never even heard that word so had to look it up.  It means randomly.

[NIquist]

The most likely cause is a memory leak so you might want to look into the VI Profiler:

https://zone.ni.com/reference/en-XX/help/371361R-01/lvconcepts/using_profile_window/

Or try the VI Analyzer to see if it reveals some poor programming choices:

https://www.ni.com/en-us/support/downloads/software-products/download.labview-vi-analyzer-toolkit.ht...

However, as Gerd said, we really can't do much but guess unless you provide more info.

Is this an EXE or Dev system?  What version of LabVIEW?  Are you processing a lot of data?  Did you program proper error handling?

If you can, post your code so we can look for possible issues.

[Yamaeda]

Are you using timing with the ms-counter and it rolls over? It happens about every 3-4 days.

[RavensFan]

---

@NIquist wrote:

---

@RavensFan wrote:

What word is "aleatory" supposed to be?

---

🤔 I have a pretty good vocab but have never even heard that word so had to look it up.  It means randomly.

---

I have never heard of it either.  Why would someone think to use a word like that rather than the common word "random".

[Kyle97330]

---

@Yamaeda wrote:

Are you using timing with the ms-counter and it rolls over? It happens about every 3-4 days.

---

The ms counter rolls over every 49.7 days with a U32 or half that with an I32.  

While it might be a counter overflow of some kind, it's not the main ms-counter...

[pincpanter]

---

@RavensFan  ha scritto:

---

@NIquist wrote:

---

@RavensFan wrote:

What word is "aleatory" supposed to be?

---

🤔 I have a pretty good vocab but have never even heard that word so had to look it up.  It means randomly.

---

I have never heard of it either.  Why would someone think to use a word like that rather than the common word "random".

---

Probably because his mother tongue is a Romance language.

Alea is a Latin word meaning die (dice), hazard, risk or similar concepts.

Remember Julius Caesar's "Alea iacta est", that is "The die is cast".

Italian, Spanish: aleatorio. French: aléatoire. Portuguese: aleatório. Romenian: aleator