I have a project that will need to run 24/7 for weeks on end (power cycling parts) problem is it is dying at the 34-ish hour mark running under LV10, 79-ish hours running under LV9.
No Errors or warnings when compiled.
PC it is running on is running XP, 3GB ram. installed is an PCI-5402 for clock generation and a PCI-6353 A/D to capture data. It uses GPIB to setup several power supplies and get heat sink readings from a Agilent 34907a.
It uses a NI USB to RS232 to control and monitor a chiller. all data is being saved to a network based Access database.
so far I've tried isolating the some of the IO's as stand alone apps (GPIB reads, USB reads, PCI access) using as much of the actual VI as possible. initial try ran for 40 hrs without incident.
when I went from VL10 to LV9 the run time before failure increased, also after the run I got a warning about and insane object. I then recreated the object (large type def cluster used in an array in a functional global, size set at runtime) and re-ran the test under LV10, test ran for 65 hours before failing.
the failure mode is no error, complete freeze, I was able to run trace execution during a failure, nothing, no indicators as to why it died.
I do have a support session going with NI, they even have my code, but so far nothing solid and no real progress.
I'm hoping someone in the community has seen a similar issue or have some suggestions as to what to try in order to isolate the problem, any and all ideas are welcome.
Of courser this is a high profile project with a time constraint and customers screaming for data (is there any other kind?)
thanks,
-Doug