Trouble mixing DAQmx Events and User Events

[CoastalMaineBird]

you can bundle dynamic event reg refnums into a cluster, and wire that cluster into the event structure.

--- Thanks for that, I hadn't thought of trying that.

[JÞB]

you MUST do the registration BEFORE THE TASK IS STARTED

What version of DAQmx?

Damn Steve! this sounds like a fun one.

Greg doesn't know how to spell "Life"

[CoastalMaineBird]

NIDAQmx 9.7.5 - LV2013 - LVRT 2013

Another problem I found was because I had slipped onto the host PC.  I'm supposed to be running on the PXI (where I have hardware), but I discovered one of these test things was on the host PC.  Duh.

This JING still shows a LV Bug, though: <http://www.screencast.com/t/cNyxANoMH>

That REGISTER node is happy when I wire the cluster to it.   When I wire the other REG. REFNUM to it, though, it changes personality.  You cannot expand it, you cannot shrink it -- it just goes all "tharn".

And then if you hook up the output line, it breaks the input connection?  why is that?

[CoastalMaineBird]

SUCCESS!

I had to use the BUNDLE trick.

I originally had the DAQmx REGISTER function after the task config and before the START.  But in all the fumbling around, I had moved it to AFTER the start.

LESSONS LEARNED:

1... Cannot register events on a task that has been started.

2... Cannot combine a DAQmx Registration with a user registeration. (Still don't know why).

3... Pay attention to where the dang thing is running!

Thanks, everybody!

[GregFreeman]

Again, haven't watched the jings because I'm lazy , but my guess is it's somehow due to the strict typing of the wires. It is because of this strict typing that I always use bundle, with each dynamic event refnum representing only a single event, not multiple events with an expanded registration node, serialized registration nodes with the dynamic event reg refnum wired through them all, etc. Only PITA is that unregister doesn't accept the cluster even though dynamic event terminals do .

[GregFreeman]

Another trick, you can use coerce to type to give more meaningful names to your event wires so when you register them they aren't just called "event registration refnum.<event name>"