05-26-2015 08:26 AM
We have an issue that exists on one of two nearly identical systems that use NI USB-6225 OEM cards. We are reading 75 channels at 1 kHz once per second. On one of two systems the Error Code -88079 occurs intermittantly and when this happens the DAQ measurements stop though the code does not freeze. We do not write to the 6225 card, the only thing we are doing is reading the AI channels.
Our LabVIEW version is 2013 SP1 f2 and NI-DAQmx is version 14.1. NI MAX is v14.0.0f0.
The first system runs on a Windows 7 desktop workstation and has serial mass flow controller software with timers to change flow and concentrations based on a control file as well as a MODBUS TCP NDIR interface. This system is complex but works perfectly.
The second system runs on a Windows 8 laptop. The mass flow software, timers, and NDIR interface were removed from the code of the first system to simplify the software for the second system.
It is only the second system that produces the Error Code -88079. This can happen once a month or several times a day.
I've removed all the 'bloatware' from the Windows 8 laptop and ensured that nothing is set to hybernate or sleep and also turned off the Windows and other automatic updates because these systems must run 24/7 for a year.
So, what is the best resolution for the Error Code -88079 problem with the second system?
Any other suggestions?
Warm Regards,
Lloyd
05-27-2015 05:10 PM
Hi Saturn233207,
Could you give more detail about the error that you are getting? What are the steps to reproduce the error? Is there any descriptive text at all in the error dialog box - maybe post a screenshot of the error?
Also, as you mentioned I believe it would be a good idea to ensure that you are using a quality USB cable.
06-01-2015 08:24 AM
Yes of course.
The full text of the DAQ Error Message is:
Error Code-88709
DAQmx Read (Analog 2D DBL NChan NSamp).vi:4960002<append> <B>Task Name: </B>6225AI
06-01-2015 04:23 PM
Were you able to use a higher quality USB cable? If so, has the behavior changed at all?
06-05-2015 01:57 PM
Not yet. The apparatus is at another location. I'll test the new USB cable on Monday, 6/8/15.