petercat

Thanks, Jeffrey. I confirmed that remoting remains the likely culprit, even after switching to a Win10 laptop. TracerDAQ Pro seems long in the tooth. It could use an update to make it more user-friendly, add features, and eliminate this remoting incompatibility. At a minimum, the Help file should be updated, for example, to warn against remoting in, or at least add an error troubleshooting section to translate each error like you did.

I am using TracerDAQ Pro with an 8 channel USB thermocouple DAQ. Late last night, at 9:15 pm, TracerDAQ Pro crashed, and logged a “DAQ Stopped” annotation. Here is a screenshot. I lost about 4 hours of data until I remotely rebooted the program. It had been running flawlessly for several days on a Windows 7 machine. How do I avoid this in the future? Is there a more bulletproof software package avaialble?

Late last night, at 9:15 pm, TracerDAQ Pro crashed, and logged a “DAQ Stopped” annotation. Here is a screenshot. I lost about 4 hours of data until I remotely rebooted the program. It had been running flawlessly for several days on a Windows 7 machine. This happened again a few hours later. How do I avoid this in the future? This appears to be a software problem. Is there another software package that is more bulletproof?