Instead of collecting performance data with PI Profiler on the device and importing it to Carbide.c++, you can also collect performance data directly from Carbide. The PI Import Wizard offers the option of collecting profiler data remotely from a device via a TraceViewer connection.
To collect profiler data remotely, perform the following steps.
In Carbide.c++, select Carbide > Performance Investigator.
NOTE Use the From File System option if you want to import existing PI Profiler data files. For more information see Importing Profiler Data files.
The Wizard automatically tries to fetch information on supported plugins from the connected device. If you already have set up a working connection, the plugins are listed in the Select Plug-ins for Tracing field. Otherwise you will get the below notice:
Figure 2. Import wizard notice
In this case, or if you want to change the settings, follow the instructions below:
NOTE You can use a USB or a TCP/IP Musti connection, but for profiling several samplers Musti is recommended due the too high amount of data.
The selected connections is now shown below the Connections Settings button.
The Wizard fetches the information on supported plugins and updates them to the Select Plug-ins for Tracing list.
Figure 3. Select Profiler Data File
The wizard starts tracing. You can see the name of the created base64 encoded file (*.base64), the trace time (how long the trace has been running), as well as the size of the file in the Created Profiler Data File(s) list.
Tracing stops and the Wizard start converting the *.base64 file into a *.dat file. You can follow the progress of the conversion from the progress bar. When the conversion is done, you can see the name of the file in the Created Profiler Data File(s) list change to *.dat.
It is possible to import several Profiler data files, so after the tracing and file conversion, you can either
Related references