Search the Community

Showing results for tags 'export'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • DAQFactory
    • Alarming
    • Channels, Conversions and general data acquisition
    • Graphing
    • Logging
    • Modbus
    • Networking: web, email, FTP etc.
    • PID
    • Screen Components and User Interface
    • Sequences and scripting
    • Serial Communications
    • General DAQFactory
    • DAQFactory and the LabJack
    • DAQFactory Express
    • DAQConnect
    • DAQFactory New Feature Requests
    • The DAQFactory Guru's Articles
    • DAQFactory Newletters

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 6 results

  1. We recently ran a test for the last 7 days and had issues logging data for one of the tests. DAQFactory is still active and has all the history data. I tried using export to save the data to a file by removing the indexes from each channel (channel_1[0] -> channel_1). When I run the export function, DAQFactory 'freezes' for a couple of hours appearing to be doing something, but no file is actually created. Is it possible to use the export functionality in DAQFactory to save our data to non-volatile storage?
  2. BallardHill

    Verifying Export Success

    What is the simplest method to verify that a beginexport command succeeded - that the file was written and closed successfully? From what I've read in the Forum here it seems beginexport runs in its own thread and does not provide a method to detect success or failure upon completion or report same to other sequences.
  3. Hi Guru, When I run RB_Export by right clicking this export set in the Workspace and selecting "begin export set" it works just fine. But when I try to do the same thing in the sequence below it produces a .csv file with no data, just a header. Please what am I doing wrong? if (component.EditBox_Export_FileName.strContents == "") system.MessageBox("Pleae enter a FileName to Export to in the box just above. You may use the <DIR> button to select the last saved filename, then press <+Copy> to use that name incremented by one. ") else if (system.MessageBox("Export Graph data set to .csv file? Note: To export a subset of data points select the starting point with MarkerA [and optionally the ending point with MarkerB]." ,"OKCancel") == "OK") Export.RB_Export.strFileName = strExportPath + strExportFileName Try Export.RB_Export.Start() Export.RB_Export.Stop() Catch() System.ErrorMessage(strLastError) ?StrLastError endcatch strExportLastFileName = StrExportFileName component.EditBox_Export_Last_FileName.strContents = strExportFileName StrExportFileName = "" component.EditBox_Export_FileName.strContents = "" endif endif
  4. orlee

    Export Of Alarms To Csv File

    Exporting Alarms to CSV do not export the EVENTS contained in the alarms So I need to rewrite them all?
  5. I've run into a problem related to export sets and DLLs. Basically, if I export a certain way after opening a project, then try to call a DLL which writes to a (different) file, the DLL write doesn't work. In fact, lots of other problems arise in DLLs because of this, not just the file writes, but that's the easiest thing to verify. If, however, I simply call the DLL function, it runs and creates the file fine. Only if I export BEFORE calling the function does the problem arise. Again, the files are unrelated. The DLL is not writing to the same file that the export set is writing to. I've attached a very small project which shows this, including a tiny DLL with one function that just writes some text to a file. The project automatically loads the DLL. To see the problem, manually type the following two commands into the Command / Alert window: beginexport(DebugExportSet) fnSimpleDLL() [/CODE] This has to be done RIGHT AFTER OPENING THE CTL. If fnSimpleDLL() was run successfully already, the export doesn't seem to cause a problem for subsequent calls. I included a sequence that shows this, but don't run it directly because somehow the timing of it means it doesn't always show the behavior. To test that fnSimpleDLL() actually does something, [b]close and reopen[/b] the project and just type: [CODE] fnSimpleDLL() [/CODE] You should see "simpledll.txt" show up in the project directory (assuming you double clicked it from explorer. Side note: It's weird that DAQFactory's working directory is different depending on how you open a file. Tough to work around). By the way the DebugExportSet exports to C:\debug.csv, and the specific settings of the export set MAY MATTER. I hope the procedure to reproduce the bug makes sense. I've verified this with two projects, different DLLs, different export sets, and different PCs. It's also holding me up on a much larger project so I'm hoping to get some feedback ASAP. In the meantime I'm trying to work around it by making sure I never export before running my DLL functions. Here's the code for the DLL's function: [CODE] extern "C" SIMPLEDLL_API int fnSimpleDLL(void) { FILE * outfile = fopen("simpledll.txt", "a"); fprintf(outfile, "Hello\n"); fclose(outfile); return 42; } [/CODE]
  6. Hello! How can one export the data from some channels that weren't included in a logging set during the run of an experiment? With the help of the manual I got to the stage of creating an export set with each channel I forgot to log initially in one row of the Main tab. Into the Expression column, I put one channel name each (Line_9 to _16 in this case). In the Details tab, I adjusted all possible settings to the same state or values as the Details tab of the successful logging set. However, I'm unsure how to restrict the data set to the time frame of my expirement (10 days in this case)? I am sure that the persistent data reaches much further back and I don't want/need to export more than necessary. Can you please let me know the precise instructions? In particular, what has to be entered into the Expression column of the 8 channels? I'm sorry, but the functions and variables lists from the manual was too technical for me. Thanks and greetings! Katrin