Search the Community

Showing results for tags 'export'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • Add-on Boards
    • Scopes & Instruments
    • LabVIEW
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 5 results

  1. Here's an OpenScope and OpenLogger log file utility that can export to CSV (TODO: JSON). It's written in Python, but the important part (the log file parsing) is portable across about a dozen other languages. https://github.com/bdlow/dlog-utils-portable I've used a combination of the data structure definitions in the Digilent dlog-utils project, some information posted in this forum on the OpenScope data format, and the application of educated guesswork. IMHO this is an improvement over the current version of dlog-utils, which has various log file parameters hard-coded within even though these parameters are specified within the log file header. It's also more portable (Python 3), smaller and of course handles both log types. This work was made possible through the use of the awesome Kaitai Struct project to define the log file structure and automatically generate a Python parsing library from that. Kaitai handles all the details of the log formatting including endianness and data types, and presents the log via a very easy to use Python class. The web IDE makes it very easy to poke around the binary log file. Want to use something other than Python? All you need's the `.ksy` file and you're almost there for any of the languages that Kaitai supports: C++/STL, C#, Go, Java, JavaScript, Lua, Perl, PHP, Python and Ruby. I've a JSON exporting version almost ready, though I probably ought to add some tests first. @Digilent: can you expand on what the channel map is meant to represent? I had presumed it was the channel number to sample index mapping, e.g. if I recorded channels 2, 3 and 7 in the OpenLogger then I'd have expected the data to have three channels in each sample; and the channel map to look like [2, 3, 7, 0, ...]. However my OpenLogger generates log files with a channel map [1, 2, 3]. Bug?
  2. Hi, I use WaveForm 3.11.5 and I would like to be able to import a previously exported Scope FFT, Impedance Analyzer and Network Analyzer data. The exports work fine, and it's pretty good for working with other tools that can handle .csv. On the other hand, it would be great to have the ability to import these values later to compare them with the ones we are measuring. I could imagine it as a new reference type, so we could import even multiple files, name them and choose colors for them. What do you think, @attila? Regards, Andras
  3. Hello everyone, I have problem with impedance data exporting from AD2 and can't find-out the solution. I wasn't lucky to find people who had the same problem. Problem: exporting Impedance measurement data to CSV I got empty rows. Graph looks correct. All data point refer to only one number, so results only horizontal line. I had the same problem with older version WaveForms and from first was thinking that update solved my problem, but it still occurring. I had idea that I save to much reference lines in Workspace, but problem accures with 6 reference lines too. System: MacOS High Sierra. WaveForms 3.10.9 64-bit Qt5.6.3 macOS 10.13 If anyone has any ideas please let me know the solution.
  4. Waveforms metadata has improved in the past year, but I'd like to see still more. Here are 4 suggestions: Metadata from other tools in the instrument: For example, when saving oscilloscope results, I would like to have the power-supply and waveform settings reported as meta-data. I'm often characterizing circuits, and it would be good to have those important parameters saved automatically, instead of having to manually add them each time. Save measurements with traces: Also, exporting from the oscilloscope currently allows saving either the measurements or the waveforms, but the "Acquisition" option should save both, with the measurements included as comments in the file. Column headers as comments in tab-separated format: It would also be nice if in tab-separated format, the headers of the columns were done as a comment (at least as a selectable option), rather than uncommented. The plotting program I use does not like non-numeric values in the fields, but ignores comments. (There are various workarounds for the non-numeric values of the headers, but the easiest one is to modify the data file, which is not a practice I really want to encourage in engineering students—it is safest for data integrity to regard data files as untouchable.) Sticky notes: Finally, I find myself having to retype notes over and over, as I do experiments with one external parameter changes—it would be good if added notes were remembered from one export to the next, so that experimenter-added metadata could be edited easily, without needing to be retyped (or cut-and-pasted from an external file) each time.
  5. I'm trying to find a way to include the Analog Discovery's serial number when exporting images of the oscilloscope in Waveforms. My lab instructor requires us to include the SN in each of our 'scope captures, but i can't find an option to include it (online or in the reference manual). Right now I'm resorting to hitting printscreen and editing in mspaint Does anyone know of a better way to get oscilloscope captures from Waveforms with the serial number showing?