Search the Community

I need to use 5 Bytes Hex string as a key, Hex string as a Value. Normally data stored in INI as ASCII. What can be the possibilities to store HEX String?

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

Hi, When an Exe is built using application builder, an ini file is created in the same location as that of the Exe with the same name. This ini file contains some settings to be used by the Exe and is read by the Exe whenever it is run. There is an option to specify the ini file using the command promt using the command line argument 'pref'. A shortcut may also be used for the same purpose (as explained in the Labview wiki). The settings are read from the specified ini file by the Exe. Everything is fine until "Pass all command line arguments to application" option in the 'Advanced' catagory is enabled while building the Exe. If this option is enabled, the command line arguments (in this case the ini file) are not interpreted by the Exe and hence it uses the settings in the default ini file (LabVIEW.ini). Is there any way by which the ini file, to be used for the settings, can be mentioned programmatically? Thank you, Ganesh Kumar