Good afternoon, all! Hope everyone is staying healthy in these difficult times.
My company is running a group of laboratory instruments, each controlled by a NI 9067, running Linux. Our LabVIEW version is 14.0. The app includes custom FPGA code, and a separate user interface (HMI) running on a network-connected PC.
I'm a very experienced software engineer, but only have a year or so with LabVIEW. The app in my experience has been extremely stable; that is, we've never seen it simply "fall over" for no reason.
Until this week, that is. On one of the instruments, the cRIO side of the app appears to stop running, as evidenced by the lack of a heartbeat message that it should be writing to an app-level disk file every minute. I'm pretty sure the network comms loops are also quitting, because the HMI gets disconnected -- but these loops would also write app-level log records when they terminate, and that's not happening.
Logging in to the linux command line of the cRIO, I find that the linux operating system appears to be intact. There are several processes with "NI" in their names running, but the CPU load is nearly negligible. Unfortunately, I can't easily tell if there are one or more processes missing, because I don't know what processes *should be* there.
Given the lack of log data, I'm getting the impression that one or more processes are getting killed somehow -- and I'm looking for information to help me troubleshoot this.
Where can I learn about the process architecture of the compiled LabVIEW app running in cRIO/Linux? Also, where can I learn about the procedures that start and stop the app, in case it's debuggable somehow?
Thanks,
-- Mark
