Log Bus Traffic With NI-XNET Bus Monitor While Running NI-XNET Application

This is possible when the interface NI-XNET Bus Monitor is set to Subordinate mode. A subordinate session uses the cluster and interface configuration from other sessions, in this case the user application; for more details see NI-XNET Hardware and Software Manual. Moreover, this does not require any code to be added to the application.

Perform the following steps to configure and run Subordinate mode logging:

Start the XNET Bus Monitor.
Select the interface that you want to monitor.
In XNET Bus Monitor choose Settings>>Interface and Database Settings
Verify the correct NI-XNET interface is selected under Interface Name.
Set Run Mode to Subordinate.
Place checkmark to Log Transmitted Frames if you want to log the transmitted frame too.
Place checkmark to Bus Error Frames if you want to monitor any error frame generated during the communication.
If you want to use a database to decode signals from frames check Assign Database Alias (optional), select your database under Alias Name and select your cluster under Cluster Name.
Choose Settings>>Logging, check Enable logging to disk, and set your logging format and destination file name.
- Note: When running the application on an RT target, you will not see the "browse" option (the yellow folder icon). The log files will be stored on the RT target at the path: /home/lvuser. See Tools Available for File Transfer/Access on NI Linux Real-Time Targets .
Click the Start button in NI-XNET Bus Monitor. Note that at this point logging will not yet start as the NI-XNET Bus Monitor is waiting for the application to start the session.
Run your application. When the application starts communicating over NI-XNET the logging will start.
Click the Stop button in NI-XNET Bus Monitor to stop logging. Note that even if you stop your application the NI-XNET Bus Monitor will keep logging and you have to stop it manually.