Jump to content

Search the Community

Showing results for tags 'task'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Software & Hardware Discussions
    • LabVIEW Community Edition
    • LabVIEW General
    • LabVIEW (By Category)
    • Hardware
  • Resources
    • LabVIEW Getting Started
    • GCentral
    • Code Repository (Certified)
    • LAVA Code on LabVIEW Tools Network
    • Code In-Development
    • OpenG
  • Community
    • LAVA Lounge
    • LabVIEW Feedback for NI
    • LabVIEW Ecosystem
  • LAVA Site Related
    • Site Feedback & Support
    • Wiki Help

Categories

  • *Uncertified*
  • LabVIEW Tools Network Certified
  • LabVIEW API
    • VI Scripting
    • JKI Right-Click Framework Plugins
    • Quick Drop Plugins
    • XNodes
  • General
  • User Interface
    • X-Controls
  • LabVIEW IDE
    • Custom Probes
  • LabVIEW OOP
  • Database & File IO
  • Machine Vision & Imaging
  • Remote Control, Monitoring and the Internet
  • Hardware

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Personal Website


Company Website


Twitter Name


LinkedIn Profile


Facebook Page


Location


Interests

Found 3 results

  1. Hello all, My question is: what is your preferred non-volatile way of storing daqmx task configurations? Backstory: For a long time I've used ini files to maintain task configurations between executions of a program. This has worked for primarily static DAQmx configurations but I'm looking at creating a test executive with some degree of flexibility, which means daqmx task configurations start to get more complicated. If you use MAX for storing your tasks: Do you run into problems accessing and maintaining these tasks even though you don't have direct access to the file? Or i
  2. I have a problem I was hoping you might be able to help me figure out. I need to be able to create 6 analog output channels that will have separate data files loaded into them. These channels will be started individually in a timed sequence. I am having trouble getting the analog DAQ tasks created. LabVIEW is complaining when I try to set them up as individual tasks in the same routine. I used a for loop on an array of data files and an array of channel names. The error code is suggesting that I set the channels up under one task. But the problem with that is that I don’t know how
  3. When trying out a new program most error messages that LabVIEW gives me are not very helpful because they refer to "unnamed task" such and such. And so I would like to give names to my tasks. It ought to be simple but still it illudes me. So now I ask... How do I give a name to a task so that error messages then will be helpful?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.