DAQmx Task not propagated through FGV/AE

[JÞB]

---

@rolfk wrote:

---

@nikvl wrote:

---

Following the comments, I would probably not use AE for data acquisition but it might still be useful for DIO functions. For example, I'd have 14 valves (fixed number hence fixed number of resources) and trying to figure out the state each individual state at any given time is going to be a challenge so I was wondering if it might be easier to manage that in an AE.

---

With time and experience you will find out that if someone tells you that there is a fixed number of resources to be handled, that is only a valid statement for that moment. Tomorrow they may decide that they need to have a 15th valve because they can't control the process properly otherwise!

---

Not a valid concern! In fact, a VERY GOOD argument for using an AE.  Need another Channel or line?  Recalibrate a Scale? Change Sample rate or size? Change it in the DAQmx definition and not in the LabVIEW code.  Even after building to exe LabVIEW exports DAQmx config data to an ini file.  Create the Task and Task resource definitions once.  Way before writing code.

[nikvl]

---

@JÞB wrote:

---

---

Change it in the DAQmx definition and not in the LabVIEW code.  Even after building to exe LabVIEW exports DAQmx config data to an ini file.  Create the Task and Task resource definitions once. 

---

Hi, what do you mean by changing in the DAQmx definition? Do you mean as in defining the tasks in NI MAX instead of the standard LabVIEW VIs for creating, reading and writing to task?

[JÞB]

---

@nikvl wrote:

---

@JÞB wrote:

---

---

Change it in the DAQmx definition and not in the LabVIEW code.  Even after building to exe LabVIEW exports DAQmx config data to an ini file.  Create the Task and Task resource definitions once. 

---

Hi, what do you mean by changing in the DAQmx definition? Do you mean as in defining the tasks in NI MAX instead of the standard LabVIEW VIs for creating, reading and writing to task?

---

Actually,  those DAQmx wizards do a great job of providing configuration settings!  They save them in xml format within lvproj files and the NI MAX database and export them as ini files during a exe build.