Error -89125 occurred at DAQ Assistant

[nicomm]

I use a setup with seven (7) PXIe-4330 and one PXIe-4353 simulated modules.
This is going to be a 'real' system, all modules will be installed in a PXIe-1078 Chassis (9 slots).
Chassis configuration will be:

slot1    : controller
slot2-8 : PXIe-4330
slot9    : PXIe-4353

I have created one task in NI MAX that I use to read all 56 AI channels from all 4330 modules.

When I run the task I get the following error "Error -89125 occurred at DAQ Assistant".

Please see also attached error reported from NI MAX.

I am using LabVIEW 20.0.1 and NI MAX 20.0.0f0.

Thank you for for reading

[santo_13]

1. Simulated instruments do not have all features of actual instruments, especially triggers - your error states that Channel-expansion uses triggers that are not available on your "Simulated" instrument. This means you can implement software and test it only up to an extent using Simulated instruments but not completely without actual HW.
2. Given such a large DAQ system, I would recommend learning DAQmx driver-based automation and completely moving away from DAQassistant at any cost. This is analogous to using some kind of training wheels on an aeroplane instead of a bicycle.
   https://www.ni.com/en-us/support/documentation/supplemental/06/learn-10-functions-in-ni-daqmx-and-ha...
   (please skip the DAQassistant part alone)

[nicomm]

Thank you santo_13 for your quick reply!

My fault, there is something I should have added in my original post:

I am accessing the PXIe modules programmatically, from my application, using DAQms start task and DAQmx read analog and, I get the same error in my application (Error -89125).

I just posted the error (which is the same) reported when I run the same task from NI MAX for easier explanation and simulation on other systems.

So if I understand correctly, you are suggesting that if I run the same task on my real HW the error will not be there?

Thanks again

[santo_13]

---

@nicomm wrote:

So if I understand correctly, you are suggesting that if I run the same task on my real HW the error will not be there?

---

Not guaranteed, but at least that will be a real problem you will have to sort out. The simulated instrument was never a replacement for actual HW to test the developed software, it can simulate only a limited amount of features within the instrument and cannot function across instruments in the chassis.

[nicomm]

Thank you Santhosh.

I will let you know how that works, when I'll get a chance to try it on the real HW.