06-25-2008 12:17 PM
06-26-2008 12:22 PM
Hi Zach,
I took a look at your code, and I believe I have the answer as to why you are
receiving this error. It appears that you created a constant for your Simple
Error Handler to specify the "type of dialog", but you accidentally
wired it into the top-most input terminal, which is the "error code"
input. Thus, since you selected "OK message + warnings" on that enum,
it is passing the value of 3 into the error code, and thus returning the error
you are seeing every time you run the VI.
In addition, based on your explanation of what you are trying to accomplish
overall, I am not sure that your code will do quite what you are expecting. You
are using the Export Signal VI to route the Counter Output Event to the RTSI_0
line, but this is not the same as routing the output of the counter. The
Counter Output Event is a signal that will pulse when the counter reaches its
terminal count during an input task. In your case, you would actually want to
connect the counter output line, specified as "Dev1/Ctr0Out" to your
RTSI line using the Connect Terminals VI. You will also then have to disconnect
these terminals at the end of your program before clearing the task. I went
ahead and made the above changes to your VI and have attached it below. Please
also note that DAQmx allows you to route signals over the RTSI bus without
having to manually connect the terminals to the RTSI line. Therefore, you could specify the source of your sample clock on one device to be the counter output of the other device, and as long as you have properly configured the boards in Measurement & Automation Explorer (MAX) to be used with the RTSI cable, it will automatically route the proper signal over the RTSI bus. Hope this helps with your application,