Triggered Analog Out and Digital Out on DAQmx

[declandineen]

Hi,

I'm having trouble with a triggered Analog Out and triggered Digital Out to a digital edge. This is code that is working with Labview 8.5 and I'm moving to Labview 2020 (I know, a big jump) where it does not work. The code is to trigger a change in an Analog Out voltage (AO3) and start a Digital clock on a digital output (from CTR1 routed to PFI10) with a falling edge on a counter (CTR2/PFI14).

Am I missing some instruction in the newer version of Labview compared to v8.5 which maybe is causing it to behave differently?

I don't get any errors during execution.

I've attached the code to setup the triggered Analog AO channel (separate VI) and setup of other channels.

I've also attached scope shots of what the triggered outputs look like with v8.5 and what I'm currently getting with Labview 2020. (Trigger CTR2 - Yellow; Triggered Dig Out - Pink; Triggered AO - Blue; DUT Output - Green)

Any help would be much appreciated.

[Kevin_Price]

I don't think there's an underlying change in DAQmx or device behavior that would explain what you describe.  Are you really *absolutely* sure you're running the same code under the same configurations in both cases?

Here are some "missing pieces" that make me ask:

- You didn't include the config for the Measurement task or the subvi "Take Triggered Measurement.vi"

- The VI's you *did* include have many of their front panel config items showing with blank default values.  That makes me not trust the other default values that aren't blank.

   A fair test would require *ALL* the config items to be the same when you run under 8.5 and when you run under 2020.

Let me suggest that you revert to your 8.5 code, set up all the config items the way you want them, run a test to confirm proper behavior, then go to the menus to choose "Make Current Values Default" on all your vi's.

Only then copy all your code into a different place, open and run it under 2020.

One other thought: are you sure your scope was set for single triggering prior to your runs?  You generate 2 pulses with Ctr2.  Your DAQmx tasks will respond to the 1st, your scope *could* respond to both depending on what mode you're in.  If the scope display for 2020 is from the 2nd pulse, that could also explain the apparent lack of sync between signals.

-Kevin P