trace tool kit

[kabooom]

Hi

I'm facing some some performance problem with a custom device i've made. Inb order to find the origin of the problem, i'm trying to use the RT trace toolkit . So I set the system channels Detailed tracing Flag, Thread tracing flags and vi tracing flags to 1, and i set the trace enabled Flag to 1 in order to start the trace and to 0 to stop the trace. I opened the file from the Real Time Execfution Trace Toolkit. The problem is in the file i could only see the thread (not the vi view). The vi view is disabled and i cannot move the scrollbar. It seems the vi views is empty. Moreover the vi tracing flags seems to have no effect.

The article i found : http://digital.ni.com/public.nsf/allkb/375EEF2235D8B8F3862577CA0073FD6F is called debugging Threads in NI VeriStand. Does it means that in VeriStand it is not possible to see the vis ???

I also tryed to generate personnal flags using the function Trace Tool Log User event. But i can't see the user event in the trace ... ( i didn't forget to configure the flags in the flag configuration, they should be displayed...).

Any help is appreciated ...

[kabooom]

Just some more informations about what happend:

- As i said, i tried to use the trace toolkit to find the origin of my problem. When i open the file with the real time Execution Trace Toolkit, i can see the thread, but not the vi (the Vi View is disabled).

- I installed the VeriStand debuggable version , and as specified in the documentation i select the vi to be non reentrant. in this case i have access to the vi view. The problem is i can only have on instance of the custom device.

- With the debuggable version of VeriStand, i tried to select the vi to be reentrant in order to see how it works with several instances of the same custom device. Again, i can't access to the vi view.

- At the end, i tried to duplicate the code of the custom device, and to make one instance of each. In this case i can access to the vi view, but the time were only reported for one of the custom device.

The question is how can you use the trace tool kit with veristand if you have a custom device which is reentrant... Or how can you debugg a reentrant custom device ?

[StephenB]

This is a limitation of the trace toolkit. It can only show VI view if the trace starts before that VI comes into memory... which means you're turning on the trace too late unless you're following the instructions in "note 1" in the KB you linked. You must edit the text of the sysdef file to change those channel's default value

[kabooom]

Hi Stephen

Thanks for your answer.

I tried again what was described in the Note 1 of the KB i.e. I set the default value of the trace Enabled Flag to 1. Unfortunately when i open the log file with the trace tool kit, i still have no acess to the VI View (the menu is disabled).

[StephenB]

Did you make sure to set VI tracing default value to 1

[kabooom]

Hi Stephen...

Yep, the 3 system flags: Detailed Tracing flag, Thread Tracing Flag and Vi tracing Flag are set to 1 (default value). I modified the xml to change the default value of the Trace Enabled Flag. All these flags are set to 1 after deploying ( i put a control on each channel on the workspace to check the default values and to control the trace enabled flag).

I tried severeal times... I deploy the project, set the Trace enbaled flag to 0, open the file with the trace tool kit, undeploy the project...  After 5 attempts it worked one time ( unfortunately the trace didn't contain anything valuable). At first i tought it works only for the first times after deploying... but it seems not. I also tried to restart VeriStand without success...

I don't understand why but the vi view was only enabled one time.