01-04-2018 03:20 AM - edited 01-04-2018 03:22 AM
Hi All,
is there any possibility to register for VI events (call, return, etc..) from LabVIEW IDE? Im sure, it is possible, because Destop Execution Trace Toolkit can do that, there are some LabVIEW API, which can do that implicitly (see picture - option "VI Execution High Level"). So the real question, is there any _public_ interface for these purpose? Of course, I could use it, but I cant use it at the same time with DETT, and I get not readable and not deterministic results via this interface.
DETT
Thanks for any help,
Balint
01-04-2018 10:02 AM
What exactly are you attempting to do? What is your goal?
01-05-2018 03:12 AM
I'd like to write a custom monitor for our application, but at this moment I can't do that (DETT and "performance and memory" tools are not completely suitable in our case).
01-05-2018 09:32 PM
The events you mentioned are not available. Just because LabVIEW has access to something, doesn't mean it is necessarily exposed for G programming. For example, you can color the bezels on old classic controls using the brush tool, but you cannot change the bezel colors programmatically.
01-08-2018 01:59 AM
I attached a picture, so you can see, the event is available 🙂 I understand your point, there is a lot of private LabVIEW API, but in this case it is not true, because it is used by DETT. As I mentioned, it is not "totally" public API, because it can be enabled only with a special flag, but as far as I know, it is not forbidden to use it. The question is still; does the code available behind Application.DTT.Setup, which is responsbile for subscribe to "VI Execution High or Low Level" events?
01-08-2018 07:45 AM
@ViltBalint wrote:
I attached a picture, so you can see, the event is available 🙂
You didn't attach a picture that shows the event is available. You attached a picture that has a control with "Event" in it's label, that's all.
The "event" might very well be captured by compiled LabVIEW, an not (as mentioned) by "G" code. So even if it's an event, it's probably not a "G" User Event that we can use.
You still haven't described what you want or require, only that you want to "monitor" your application.
In stead of catching events used by DETT, there might be stubs\API to actually programmatically use DETT from LabVIEW (not saying it's possible, I just don't know). That might help, depending on your exact needs.
Any solution based on undocumented features is risky. Sure there are plenty user solutions that will work (depending on the exact needs). Using undocumented\underwater solutions usually only get you 20-80% there, and the rest is usually impossible...
01-08-2018 09:53 AM
I agree with the previous responders that there may be other ways to achieve what you have in mind. So please give us an idea what your end-goal is so that we can help you.
Ben