Desktop Trace Execution Toolkit: Access details programmatically

[Sebastian.Weber]

Hi!

I have a vast project and trying to track down a performance issue. Therefore, I would like to know which SubVI was called when by which VI, how long it run, and so on.

The DETT is (almost) the perfect tool to collect this data. The table shows clearly when a SubVI was called and when it returns. "Almost" because I still have to calculate the time it took. In the lower region, there's the "details" field showing for example the call chain when a VI is called.

Now, here's the point: I want to dig down this data, which is not possible in DETT itself, so I need access to the data. However, DETT allows to save the data as *.det file, which is an unknown binary format, or as *.txt file. But that is missing the details.

So, any idea how I can access the full data including details? Either from e.g. the *.det file or any other means?

[cordm]

I don't think there is any public documentation about the det format, it seems to be onyl for use with DETT.

James Powell had a presentation at GDevCon how to access the DETT API from LabVIEW.

Watch Memory in LabVIEW by James Powell: https://labviewwiki.org/wiki/GDevCon-6/Memory_in_LabVIEW

Here is the custom Trace Tool that has some of the features you want: https://bitbucket.org/drjdpowell/trace-tools/src/Main/

IIRC it saves trace data to an sqlite database.

[Sebastian.Weber]

Hi!

Wow, this tool looks like what I'm looking for. I can't test it right now, but the code is quite easy, and I can adjust it to my needs.