Jump to content

A Scottish moose

Members
  • Posts

    52
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by A Scottish moose

  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 is there an unlisted storage location for these files? If you use ini/text based files: How do you keep things orderly? I'm running into all kinds of limitations with the format. If you use XML: Where did you find your schema? Did you write it? I know NI saves tasks as XML files, and so therefore the schema exists, but I haven't been able to figure out how to use it. I've created a task in my project and then dug through the XML of the project to find the attached image. I believe this would be the ideal solution, but a little bit of digging in around NI.com (I know...) and google (actually useful) has resulted in no answers. I know there is an elegant answer to this question, I've just not found it yet. Thanks in advance for your comments. Cheers, Tim M
  2. What functionality in LVOOP do you need that you can't get with regular LV? Answer to this question will probably help you know where to start. Personally I'd just recommend finding a low consequence project and just write it with classes. Tip: LVOOP is basically vanilla LabVIEW but cluster TypeDefs also have methods. There is A LOT of depth with LVOOP but you don't need to know all that to start. Just follow good programming practices and you'll figure it out. Cheers, Tim
×
×
  • Create New...

Important Information

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