Datalog file type

Hi,
I have an application written in Labview 4. This application is running
since 1996 and produces datalog files with collected datas.
I now have to rewrite it with Labview 5.1 (or 6) but the datalog file
type of Labview 4 and 5 are not compatible. I can convert them file by
file but I have approx 2000 files to convert. Does anyone have a
solution for converting a large number of files in one time ?
Thanks in advance for your help and best regards
A. Jacot
Developement engineer
University of applied sciences, Le Locle, Switzerland

There is a setting you can put in the labview.ini file to prevent conversion
dialogs:
SilentDatalogConvert=True
Jean-Pierre Drolet
"Antoine Jacot" a ecrit dans le message news:
[email protected]..
> Hi,
>
> I have an application written in Labview 4. This application is running
> since 1996 and produces datalog files with collected datas.
>
> I now have to rewrite it with Labview 5.1 (or 6) but the datalog file
> type of Labview 4 and 5 are not compatible. I can convert them file by
> file but I have approx 2000 files to convert. Does anyone have a
> solution for converting a large number of files in one time ?
>
> Thanks in advance for your help and best regards
>
>
> A. Jacot
> Developement engineer
> University of ap
plied sciences, Le Locle, Switzerland
>
LabVIEW, C'est LabVIEW

Similar Messages

  • Get a specific cluster out of a datalog file

    HI!
    I'm saving a cluster with controls (boolean, dbl, u32...) into a datalog file. For several different settings of the controls I'm saving the clusters consecutively in to the file. Is there a way to directly access a certain position at the file, in order to instantly read this position without going thru the hole file with a while loop? If I want to replace a certain position with a changed cluster is there a way to do it directly?

    Random access for reading is very easy to do, simply wire up the position terminal on the Read VI. Random access for writing is unfortunately not so simple. LabVIEW won't do it for you, and while you might be able to figure it out with a lot of file manipulation (using binary access to the file rather than datalog) it would be a really big pain. If you are looking to do these types of things then you might be better off using a more robust file storage method such as the Storage VIs (7.1 only).
    Regards,
    Ryan K.

  • How Do I Convert LV7.1 Datalog Files to LV8 Format?

    I have several LabVIEW 7.1 datalog files that generate Error 71 (File data type conflict) when I try to open them in LabVIEW 8 using the new Open/Create/Replace Datalog vi with my original typedef constants wired to the record type terminal.  Likewise, my original LV7.1 code recompiled in LV8 often generates error 116 (unflatten or byte stream read operation failed due to corrupt, unexpected, or truncated data) or error 4 (end of file encountered) when randomly accessing records in the LV7 datalog files, presumably due to changes made to the datalog file structure in LV8.  I recall one time when a dialog box popped up asking if I would like to convert the file to LV8 format.  Since this was a file currently in use on the server by LV7.1 clients, I had to reply no.  With copies of the datalog files now on my hard drive ready for conversion, I haven't seen the conversion dialog box pop up again.
    How do I convert the LV7.1 datalog files to LV8 format?
    Thanks,
    Larry

    Good afternoon Larry,
    Thanks for posting! 
    The Datalog file support in LabVIEW has changed, but the underlying
    principles of the technology remains the same. 
    Converting to the new format should just involve converting a few VIs to the new Datalog-specific versions.  As you can see, the new Datalog VIs appear in
    their own sub palette in 8 which will help keep things simple.
    Before we address the concerns with the errors, let’s first
    make sure that the code has been properly converted. 
    To convert your VI to the new format:
    1)      Replace
    the Open File VI from LabVIEW 7 with an “Open/Create/Replace Datalog” VI in LabVIEW
    8.  Keep your type constant or control
    wired to the “Datalog Type” input.
    2)      Replace
    any “Write File” VIs in LabVIEW 7 with “Write
    Datalog” and triple check that your data matches the datatype wired into the
    open exactly.
    3)      Replace
    any “Seek” VIs with “Set Datalog Position”.  The input to this VI is the number of records
    to advance (check the mode set by the “from” parameter).
    4)      Replace
    any Reading VIs with the corresponding “Read Datalog” VI.
    I suspect that if you are receiving errors saying that the
    end of file has been encountered it is a result of a bad input to the “set Datalog
    position” VI.  I attached a basic example
    of writing a Datalog file in LabVIEW 8, and reading the results.  The rest of the functions in the new Datalog palette
    should be pretty straightforward. 
    Does this help?  I
    would be more than happy to answer any other questions on this if you need any
    additional clarification, or if this response does not address your question.
    Travis M
    LabVIEW R&D
    National Instruments
    Attachments:
    Datalog8.zip ‏30 KB

  • How can I deny write access to datalog files for all but one process in LV8?

    In LabVIEW 7.1, wiring the deny mode terminal of Open File.vi with a Deny Write Only enum constant was an effective means for ensuring that only one process could write to a datalog file at a time.  In LabVIEW 8.0, Open File.vi is no longer available and the new Open/Create/Replace Datalog vi does not provide a deny mode terminal.  Also, the new Deny Access vi does not support datalog files.  Furthermore, the Set Permissions vi is an unsatisfactory solution because under the Windows operating system, it simply sets the Read Only file attribute.  This is inadequate because I have demonstrated that it is still possible for two processes to open a datalog file with read/write access before either one has had a chance to set the Read Only file attribute in order to lock out the file.  If a process sets the Read Only file attribute first, then it can't open the file with read/write access for itself.
    Does anyone understand the file mechanism by which deny mode used to work with the old Open File.vi?  I wish to restore the functionality I had in LV 7.1 in my LV 8 programs.
    Thanks!
    Larry

    Larry Stanos wrote:
    I appreciate the
    empathy from Rolf, but I'm hoping that someone may have written one or
    more vi's containing CINs that call Windows 2000/XP file access control
    library routines.  At least I'm assuming that is how the deny mode
    input to Open File.vi used to work in LV7.1.  The Microsoft
    Developers Network on-line documentation on Access Control http://msdn.microsoft.com/library/default.asp?url=/library/en-us/secauthz/security/access_control.as... is
    daunting to put it mildly.  But even if a set of CINs has not
    already been coded, perhaps someone could point me to the specific set
    of calls I need to make to absolutely guarantee that no two
    clients can simultaneously open the same file with write privileges.   Unfortunately
    the elimination of deny mode functionality for datalog files in
    LV8 has sabotaged my commitment to a March 1 release date because it
    would also be impractical to convert everything back to LV7.1 at
    this point.   Sincere thanks to anyone who can help me out here!
    Unfortunately
    the functionality you mention does not work in the way the deny mode in
    the LabVIEW nodes works. Basically that deny mode is converted to an
    according FILE_SHARE_READ/FILE_SHARE_WRITE value and passed to the
    Win32 API CreateFile function. This is more or less the only place
    where you can define a global share (or deny) access to a file. That is
    also why the Deny Access node online help is talking about that the
    file is reopened.
    But I just retried what you had tried to do, and low and behold it
    works with wiring a datalog refnum to Deny Access. What is important
    here however is that you do need to wire a datatype to the record type
    input of the Open/Create/Replace Datalog node. Otherwise you can't
    connect the resulting datalog refnum to any other file function, since
    it is an incomplete datatype.
    Rolf Kalbermatter
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Writing Datalog Files with record length

    How do I write a Datalog File with a record length of 128 int16s?

    Each I16 number in LabVIEW that you write uses 2 bytes because 8 bits equals 1 byte. If you write 128 numbers, the file will be 256 bytes long. You can modify the VI to write I32 (4 bytes) or I8 (1 byte) just by changing the representation of the number. You also need to change the subVI that does the actual writing (Write File+ [I16].vi). Be sure to rename the VIs that you change. I would think that your Fortran program would work as long as the data types match.

  • Same data wire (source and sink are listed as "datalog file reference of") will not connect

    I am trying to write a short program that will convert a string spreadsheet file into a datalog file with the numbers turned back into numbers.  I have a case structure for each type of spreadsheet (different types per columns and different number of columns).  I use a 'for loop' to process all records (rows).  And I use a 'sequence structure' to individually process each column item into its original format (string or number), then group together into a bundle and then write the results to the datalog file format.
    The first two (case structures) worked but the second pair of case structures would not allow me to connect the datalog file reference number from the 'write to datalog file' to the 'close datalog file' through the 'for loop' wall.
    I am using 8.2
    I am sure it is an stupid issue, but the error message just did not point me towards a solution.
    con-fUsed, DogFace.
    Attachments:
    PROCESS SH TO DLOG.vi ‏84 KB

    The problem is that you are creating a different type of datalog file in cases 2 and 3 than you are in cases 0 and 1.
    The structure of a datalog file is the same as an array of clusters. All of the clusters must be of the same structure. Only the values of the individual cluster elements can vary.
    You are trying to write three different cluster structures to a single datalog file. You just can't this.
    You'll either need to write to three different files, or come up with a structure that everything will fit into.
    One other quick hint. NEVER use a variable to pass data when you can wire the terminal directly to the function.
    Ed
    Message Edited by Ed Dickens on 03-19-2007 11:39 AM
    Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
    Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

  • How can you read datalog files in LabVIEW?

    I have a VI that records time and waveform data and writes them as a cluster to a datalog file. I have been unable to read these files in any way, however. I have been working with the datalog examples in LabVIEW, but I have not been able to figure out how to use the Read Datalog File example effectively. Does anyone have any suggestions on how I can either use this example to read waveforms, or how I can design a VI to read datalog files in another way? Thanks.

    Hi,
    when you read from a datalog file you have to wire to the datalog type input of the Open File function a cluster of the same type as the clusters when you created the file; each cluster is a record.
    In the example Write Datalog File Example.vi you see that each record consists of a cluster containing a string and 1D array of DBL; in the Read Datalog File Example.vi a cluster of exactly the same type is wired to the datalog type inputs.
    You can use this example to read your datalog files but you must wire to the datalog type input a cluster containing the time data and a waveform data; pratically you have to tell how the data are saved in your file.
    I hope I have been clear enough, eventually if you tell me how you save the time data (string, numeric) I
    can modify the example to read your datalog files.
    Good luck,
    Alberto

  • Opening my datalog file errors out with error 42 generic error

    I'm using the datalog API to store video images flattened to string (the record type is string).  This works great most of the time, and gives me easy access the whichever frame I currently want.  My files are between 15 and 125 MB.  Occassionally when I try to open a file, the Open/Create/Replace Datalog primitive returns error 42, which is a generic LabVIEW error.  The file appears to be the right size and looks as correct as I can tell in a hex editor.  I'm guessing it's some sort of parsing error, but I don't know the datalog API binary format.  I'd really like to recover these files that are throwing the errors.  Any ideas?
    Robert C. Mortensen
    Certified LabVIEW Architect
    Certified LabVIEW Embedded Systems Developer
    Endigit

    Greetings FlamingYawn!
    I apologize for the trouble you're having opening some of your saved datalog files.  Unfortunately, as you have already mentioned, Error 42 is a general error and as such, provides us with little information that we can use in troubleshooting the issue.  From all the research I have done, it seems that the two most common causes of this type of problem are from a logic error in the writing section of the code or from the files being corrupted by some other means during the write (i.e., from bad sectors on a hard disk).  Unfortunately, the file type is a proprietary binary format and the structure is not publicly known.  We currently do not have any tools for use in reading these files outside of LabVIEW.  This is not necessarily to prevent the files from being read by other software but simply because it is a file type that was designed specifically for LabVIEW. The best information I can provide you with is related to the file header.  This can be found in the following KnowledgeBase article:
    LabVIEW Data Logger: Binary Header File Format
    http://digital.ni.com/public.nsf/allkb/747B83B6C8E4A6218625669100563B61
    If it is at all possible, please try to see if the same set of data produces the same error each time following the write/read sequence.  If this is in fact the case, I can work with you further to file a Corrective Action Request so that the developers can address the issue. 
    I hope this helps some.
    Best Regards,
    Michael G
    Michael G.
    Applications Engineer
    National Instruments
    Self-realization: I was thinking of the immortal words of Socrates, who said, "... I drank what?"

  • Datalog files LV v6.0 & 6.0.2

    I saw a few other posts recently about datalog file conversions
    between versions, but they didn't mention quite the same problem that I
    just saw.
    I have an application under 6.0.2 that creates datalog files. I
    copied part of the application (a file reader program) to another
    computer that has v 6.0. I also copied a file that had been created
    under 6.0.2. When I ran the file reader under 6.0, using the datalog
    type input to the file dialog function, the file would not appear in the
    dialog, as if it was not recognized as a datalog file of the proper
    type. The file reader program worked on both computers with that same
    file once I had upgraded the 2nd computer to 6.0.2.
    Is there a known compatibility issue with datalog files going
    bac
    kwards from such minor version upgrades? If so, is there a way to
    successfully convert them?
    Regards,
    Dave Thomson
    David Thomson 303-499-1973 (voice and fax)
    Original Code Consulting [email protected]
    www.originalcode.com
    National Instruments Alliance Program Member
    Research Scientist 303-497-3470 (voice)
    NOAA Aeronomy Laboratory 303-497-5373 (fax)
    Boulder, Colorado [email protected]

    Dave,
    Thought the upgrade from 6.0 to 6.0.2 is not a large one, it was large enough to require that all VI's need to be recompiled, and also apparently, how the different data types are handled by LabVIEW has changed subtly. This would fit the criteria for why those datalog files aren't showing up, they do not filter as the "correct" data type.
    I have verifed your issue and haven't been able to find a workaround, except that all copies of LabVIEW should be upgraded to 6.0.2 as a good general rule of thumb.
    Joshua H.
    Applications Engineer
    National Instruments

  • Retrieving datalog files

    I have a log file created with an old version of a VI. I do not have a backup of the VI before the front panel was modified, so I cannot access the log file. There are a lot of fields on the front panel, so it is not something that can easily be re-created (I don't even know exactly which ones were on this version). Is there any way to easily retrieve this old data?

    greg@sontek wrote:
    > This sounds like exactly my problem. Is there any way that I can
    > submit this as a feature request? This does not seem like an
    > unreasonable/uncommon thing to have happen and basically makes a lot
    > of data trash. It seems to me that there should be some way to easily
    > exactly front panel information from the file. Is there a format
    > definition of the datalog file published anywhere, or is this held
    > internally at NI?
    I don't think it was ever published and there are modifications to the
    format with most major LabVIEW versions. However I'm pretty sure that
    part of the header in a datalog file corresponds with the "type string"
    returned from the "Flatten to String" function from a cluster with the
    same control typ
    es and their order as the controls on the front panel.
    The contents of this "type string" is documented in an Application Note
    on the NI site so it shouldn't be to difficult to get the original
    format back with the help of a Hex Editor.
    Rolf Kalbermatter
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Set file type associations in Adobe Bridge for Photoshop CS6

    Is there a way I can edit the registry so that in Adobe Bridge, under edit, preferences, file type associations, the jpg extension is forced to use the 32-bit version of Photoshop?  I can do it manually, but is there a registry key i can export to apply it to multiple computers?

    Yes, in theory, but it is generally not recommended. But that location would depend on what OS you are on. This video give the locations for the Photoshop files, Bridge would just be in a neighboring folder: http://tv.adobe.com/watch/the-complete-picture-with-julieanne-kost/how-to-reset-photoshop- cs6s-preferences-file/

  • Data Recover From Formatted Drive? What is the best program to use to get back Logic Projects and any other file type?

    I was in the process of reorganising my hard drives so I could RAID them however I managed to corrupt one drive and had to format it which meant I lost all my Logic Files and some other files. I managed to save a lot of files (mainly video files) before I had to format the drive but I need a Data Recovery service that will not alter anything on the hard drive and will put all the formatted files (regardless of the type) back for me so I can get the rest of the ones I need.
    Thanks in advance.

    What about folders and such?
    No. FS doesn't reconstruct folders. However, Data Rescue does, depending on how you use it. About the only thing in Data Rescue a Quick Scan ever seems to show you are files that are already live.
    So that leaves you with a Deep Scan, or a Deleted Files scan. The first pass of a Deep Scan will attempt to retrieve folders and files, along with their original names. The second pass only looks for file patterns. Like recognizing a Photoshop .psd file. It will recover it, but give it a nonsense name. A Deleted Files scan only results in nonsense names of recognized file types; no folders.
    What were you using File Salvage on? A hard drive?
    Yes, though you can use it on a flash drive, or any other mounted drive.
    At the moment it is estimating 289 hours remaining on a 1TB drive. Can it not go faster?
    No, both of the software mentioned are slower than molasses in January. When you delete anything in Windows, its file table entry simply tagged as deleted. So to unerase them, the tag is removed. That's why it works to quickly and easily (assuming you haven't already overwritten the data to be recovered).
    In OS X though, the whole idea of the underlying UNIX structure is all about security. It's not supposed to be easy to retrieve deleted items. When you delete items, their file table entries are erased. So the only way to find deleted items is to scour the entire drive for BOF (Beginning Of File) markers that don't have a matching starting block to anything that is in the file table.
    Another question, half the drive was empty. Will it fly over that empty space or will it sieve through it incase there was some files stored on it?
    If you use the Expert mode is FS, you can choose to do that:

  • File type in GUI_download

    Hi Experts,
    Whatis the coresponding file type for 'WK1 for WS_DOWNLOAD in GUI_DOWNLOAD?

    Hi ravi,
    1. Its the same WK1.
    2. U can check for yourself in the documentation of this parameter in se37.
    regards,
    amit m.

  • Removing obsolete file type associations from "Open With" menu

    Ever since I removed VMWare Fusion 3.x from my system, I've been unable to remove the Bootcamp file type associations that it created. For example, if I right-click on a PDF and choose Open With, this is a partial list of what I see:
    Adobe Acrobat Pro (default)
    Adobe Distiller (Mac) - Boot Camp partition (VMWare Fusion 3.0.0)
    Adobe Fireworks CS4
    Adobe Fireworks CS4 (Mac) - Boot Camp partition (VMWare Fusion 3.0.0)
    Adobe Illustrator CS4
    Adobe Illustrator (Mac) - Boot Camp partition (VMWare Fusion 3.0.0)
    Adobe Photoshop CS4
    Adobe Photoshop CS4 (Mac) - Boot Camp partition (VMWare Fusion 3.0.0)
    ...and on and on and on. 17 additional entries for Fusion for PDS's alone. This junk is driving me crazy.
    I've tried rebuilding the Launch Services database with MacPilot and Onyx (the recommended fix that I've found on the web), but the entries still are there even after restarting Finder and rebooting my iMac. I'm at a loss to figure out how to get rid of these.
    Can anyone help me?
    Thanks!

    They are stored in the LaunchServices database. You can give this a try, but no guarantees. If you no longer use VM Fusion then I suggest following the information below on uninstalling software.
    Rebuild LaunchServices Database
    Open the Terminal application in your Utilities folder. At the prompt paste in the following command in its entirety:
    find /System/Library/Frameworks -type f -name "lsregister" -exec {} -kill -seed -r \;
    Press RETURN.
    Wait for the Terminal prompt to return after which you can quit the Terminal.
    Uninstalling Software: The Basics
    Most OS X applications are completely self-contained "packages" that can be uninstalled by simply dragging the application to the Trash. Applications may create preference files that are stored in the /Home/Library/Preferences/ folder. Although they do nothing once you delete the associated application, they do take up some disk space. If you want you can look for them in the above location and delete them, too.
    Some applications may install an uninstaller program that can be used to remove the application. In some cases the uninstaller may be part of the application's installer, and is invoked by clicking on a Customize button that will appear during the install process.
    Some applications may install components in the /Home/Library/Applications Support/ folder. You can also check there to see if the application has created a folder. You can also delete the folder that's in the Applications Support folder. Again, they don't do anything but take up disk space once the application is trashed.
    Some applications may install a startupitem or a Log In item. Startupitems are usually installed in the /Library/StartupItems/ folder and less often in the /Home/Library/StartupItems/ folder. Log In Items are set in the Accounts preferences. Open System Preferences, click on the Accounts icon, then click on the LogIn Items tab. Locate the item in the list for the application you want to remove and click on the "-" button to delete it from the list.
    Some software use startup daemons or agents that are a new feature of the OS. Look for them in /Library/LaunchAgents/ and /Library/LaunchDaemons/ or in /Home/Library/LaunchAgents/.
    If an application installs any other files the best way to track them down is to do a Finder search using the application name or the developer name as the search term. Unfortunately Spotlight will not look in certain folders by default. You can modify Spotlight's behavior or use a third-party search utility, Easy Find, instead. Download Easy Find at VersionTracker or MacUpdate.
    Some applications install a receipt in the /Library/Receipts/ folder. Usually with the same name as the program or the developer. The item generally has a ".pkg" extension. Be sure you also delete this item as some programs use it to determine if it's already installed.
    There are also several shareware utilities that can uninstall applications:
    AppZapper
    Automaton
    Hazel
    CleanApp
    Yank
    SuperPop
    Uninstaller
    Spring Cleaning
    Look for them at VersionTracker or MacUpdate.
    For more information visit The XLab FAQs and read the FAQ on removing software.

  • File Type Associations

    Recently re-installed Adobe Photoshop CS6, Dreamweaver CS4 and Illustrator CS4 because I had considered not renewing my Adobe CC subscription. I decided to stay on CC one more year, but the previous version installs totally messed up my default file associations. I do not want to uninstall those previous apps.
    So of course I went to Bridge preferences and painfully changed them to the CC programs. The problem is if I want to open an .ai in Photoshop CC I used to be able to from one of the options in the flyout. Now I can only pick the default and all the other options are like Photoshop CS6 and Illustrator CS4. How can I change those other options populating the flyout without uninstalling the old apps?
    I can go to Photoshop CC and manually open it there, but that defeats the whole purpose of Bridge.
    I tried to change file type associations through Windows 8 file type associations but it won't let me do it there either.
    Thanks.

    Find a file you want to have associated to a different application in the Finder.
    Control-mouse click (or right click if you have a two button mouse) the file and select Open With's submenu Other...
    Find the application you want to open it with, and make sure in the Open With... file dialog box, you check "Always Open With" before selecting the application. Documents of that type will now always open with that specific application you chose.

Maybe you are looking for