AndrewH

OK - couple of good ideas - thanks for this guys. I've now got some alternative ideas to try Thanks again Andrew

Ohh - thanks Ravi. Seems like a serious short-coming of Labview. Any one else have any ideas????

Having an unusual problem - wonder if anyone is able to help I'm using the Get Image method on an invoke node to grab the front panel of an intensity graph, which I then store as a JPEG. Within the application the user can change the color table on this and other intensity charts to the colorscheme of their choice. However the image that is stored from Get Image only uses the color table that is defined as the default one for that chart, and not the one that is currently in use. E.g. if the intensity chart is currently displaying a color table that maps from red->white->blue (hot-cold) coloring, but has a default color table that is full color spectrum (ROYGBIV), then the exported image is full spectrum, not the currently dispayed hot-cold scheme. Does anyone have any suggestions of ways to ensure that the exported image uses the currently displayed color table rather than the default that is stored in the depths of Labview.? thanks in advance Andrew

No apologies needed - will check it out and see if it merits the investment thanks to all respondents Andrew

Cool - thanks Phillip - I'll check it out

That's fine for the numeric data but the headers are a whole mix of stuff including strings (which may contain spaces), booleans, enums etx. Dumping header as the first row would make automatically decoding it a nightmare and you also get the "order matters" problem that I discuss in the next para. Sure I could dump all as simple text lines but the issue comes 'n' months down the line when it is decided to add an additional item to a cluster. If we go for a simple text file then position within the file matters. e.g. unit serial number currently on line 7 of file now moves to line 8 because an additional entry has been placed above it. And before you ask ... its not sensible just to add new lines to the bottom of the header section as this means that related data become scattered all over the header. This is why some kind of sectioned approach (e.g. INI file or XML categories) have an appeal where I could simply add a new line within a section. Have tried checking out OpenG but at the moment I'm having issues with VIPM in that it complains I haven't set "localhost" as a permitted server within VI server: Exported VIs and Machine access sections. Even when I have :-( As to data type - everything outside the header is a single precision float mostly waveforms or spectra acquired from scopes or network analysers Thanks for your thoughts guys - please keep them coming Andrew

Apologies if this is a noobie question that has been well discussed elsewhere - however a quick search didn't appear to find any obvious hits. The problem is as follows: I'm writing an application that will need to be able to output a large number of data files that may then be subsequently read back in for post processing. For entirely non-technical reasons the data files will be text rather than binary. Each data file will have to contain a reasonable sized header including device ID, test conditions, user ID, test equipment ID etc etc. The info in this header will be derived from typedef clusters that contain all the relevant info within the app. My issue is - how to format the data file? Also worth mentioning that there will often be a number of items that are redundant in any one given file, although which ones will vary greatly depending on which device type we are measuring. Initially I'd looked at trying to canibalise some of the ideas from a config [ini] type file format, where one could define sections, keys and values, but I suspect that this is not sensible given the potentially large number of files that I'll need and the way that the config files use a registry. I'd also looked at using the flatten to XML options but this gives rise to a header that is many hundreds of lines long (not least of which because there a number of typedef enums and the XML schema lists all enum cases before listing the selection. So - how would you chaps approach the situation? I'm really after suggestions and trying to canvas opinion from the wisdom here before ploughing headlong into writing code thanks for looking Andrew