Trying to sense a "non-trigger" on a 53131 timer/counter and Labview 7.1

[dlong]

I am using Labview 7.1 to create an automated testset for some surface mount boards and need to know when a trigger is not generated as well as the timing (t1 to t2) when a trigger is sensed. I am using the ag5313xa.llb library for subvis to control the timer counter  and am having no problem when a trigger occurs both on channel 1 and channel 2. My problem arises when I am watching channel 1 trigger and I am NOT expecting a trigger on channel 2. Labview comes back after 20-30 seconds with a popup error window and I must click <continue> to resume my tests. I have tracked the vis down to the lowest levels (concatenated strings) and removed all "error out" blocks but I still get the popup. Does anyone know how I can sense this "non-trigger" and verify that channel 1 triggers and channel 2 does not?

[Robert M]

Hi dlong,

It looks like you need to find out where the code for the pop-up is.  It could be either in the LabVIEW code, or in the dll's that LabVIEW is calling.  If it is in the LabVIEW code, then we can modify it, but if it is in a dll call, then you will either have to call a different dll or find a different way of getting the same functionality.  I would be happy to take a quick look at your program if you want to post your code.

Kind regards,

Robert Mortensen
Applications Engineer
National Instruments

[dlong]

Thanks Robert,
I was able to delete the offensive popup caller, it was an error out, from a vi pretty far down the heirarchy but this created other problems, my 53131 would occasionally get locked and need power cycled. The good news is...I have since worked around the problem by using a pulse generator set to a very low frequency, 100mHz,  to give me a trigger after a 10 second "time out" period.

I really appreciate the response and offer to look at my code. I may yet take you up on it as I continue to debug this program.

Thanks,

Dave