Error Code

[Dazed_And_Confused]

I used Labview 2011 to program and control a Measurement Computing USB1208FS.

The program was written to operate a valve, igniter, and pressure transducer. The purpose is to operate the valve, a short time later (milliseconds) the igniter would fire, and then the pressure would be monitor for the following three seconds, and the system would then stop.

The problem has been, that I am getting an error code that makes no sense and the Labview System locks up.
The computer ASUS laptop, with the Labview 2011 running on Windows 7 OS. There is nothing else operating on the system.

The error code is

 – Error – 10133 occurred at ULX –create Channel ( Do - digital output . )    VI : I

Any suggestions or solutions

[mikeporter]

Sounds like it's time to call Measurement Computing... This is clearly an error that is bubbling up from them. You might also want to characterize better what causes the problem exactly. Is it a particular number of channels? A particular combination of channels?

It would also be helpful to see the code, and to know exactly where in it the error occurred.

Mike...

[crossrulz]

Is there a better error description in the error cluster?  That is coming from a third party, so you should ask the manufacturer about the meaning of the error code.

[Dazed_And_Confused]

Thanks for the reply Mike

I have one big problem with providing more details and that is I am getting the information second hand. I did this design and programming for someone else. The system was sent half way across the country and I am getting the information via the telephone.

As far as the channels, as I mentioned in my first post (or maybe I didn't) I have three digital out, with two of those outputs being a mirrored function, and one analog input. The outputs trigger fast acting SSR's local to the DAQ so I know the wiring is not the cause. The input is a 0-10v pressure transducer. also local to the DAQ.

I did not include the code itself because I do not suspect that to be the issue. The program will run through successfully several times (in the order of 20 times) without issue. This tells me right off that the code is correct and not the primary cause of the error. There is a logging function as part of the code, and that too will record the data successfully through each iteration. I actually suspect that the issue is related to the windows operating system since the program is running from a laptop and the fault is intermittent.

The error appears to be an issue with VI from Measurement Computing, and a time issue with the OS. I was hoping (just a blind chance) that someone from this site had experience working with MC and may be able to point me the proper direction.