08-10-2007 01:43 PM
08-13-2007 01:42 PM
Hi there,
Check out this KnowledgeBase entry. You can write the result to an array or some other type of storage and then write that to a file using the Write to Spreadsheet File.vi amongst others (see the File I/O Palette under Functions on the Block Diagram). Let me know if you have any questions!
Stephanie
08-13-2007 02:53 PM
08-14-2007 10:10 AM
12-07-2020 01:09 AM
I'm looking for this exact features of profiling set of VIs programmatically while the application runs. I got some hindsight that VI Analyzer toolkit and Log VI Data can help with this. Anyone successful in this?
12-07-2020 06:41 AM - edited 12-07-2020 07:07 AM
I'd start searching in C:\Program Files\National Instruments\LabVIEW 20xx\project\_ProfileBufferAllocations.llb
Now a lot of this is PW protected (EDIT: actually, a lot isn't but the interesting parts are), the main VI is completely obfuscated (no diagram, not a normal VI).
Turn On LV Profiling.vi and Turn Off LV Profiling.vi are pretty autonomic though.
What I get from other VIs (Read PBA Bin File API.vi, etc.) it seems that enabling profiling creates a file somewhere that can be read... EDIT: Turn On LV Profiling.v takes a path to a BAP file. That could be the PBA file?
12-07-2020 07:27 AM
This gives me results.
But it's tricky! It only gives results for (sub) VIs that executed. Also execution of those VIs is somehow blocked by the profiler. My test.vi (that should be a path of course) didn't execute until I continued from that 1st brakepoint. It's probably designed to run in another context...
The results are somewhat cryptic as well. But that's what you get once you go low level...
12-07-2020 07:31 AM - edited 12-07-2020 07:37 AM
I think this works mostly as expected, and does everything asked for?
Except "Also, how can I save the results into a spreadsheet?". I hope that's clear now we can get data? It's really a completely different topic.