includes two methods for creating sessions: a LabVIEW project and the Create Session function. You typically use only one method to create all sessions for your application; each method is best suited to different situations.

Understand the differences between these methods of creating sessions to know how to best approach the design for your application:
OptionDescription
LabVIEW Project

Best suited for applications that are static, in that the network data does not change from one execution to the next. Does not allow end users to configure sessions interactively.

Example: If your application is used for a specific product (for example, an instrument panel for a specific make/model/year of vehicle), and the front panel must be simple (for example, a test button with a pass/fail LED), a LabVIEW project is the best method to use for sessions. Because the configuration does not change, a LabVIEW project provides the simplest programming model.

When you configure the session in a LabVIEW project, you select the interface, mode, and database objects with the user interface.

For protocols that support databases, any database objects (cluster, frames, and signals), must exist in a file. If you do not already have a database file, you can create one using the Database Editor , which you can launch from user interface.
Create Session

Creates sessions at run time. Allows the end user of your application to configure sessions from the application at the cost of more complex programming.

Example: If your application is used for many different products (for example, a test system for an engine in any make/model/year of vehicle), Create Session is the best method to use for sessions. On the front panel, the application end user can fine tune the configuration to suit a variety of test cases.

Create Session takes inputs for the interface, mode, and (if relevant to your protocol) database objects.