Configure the runtime system in PAtools PCU Configuration so that the test station settings can use the runtime system.

PAtools real-time systems can start a maximum of 10 runtime systems in parallel. The following factors influence the maximum number of possible runtime systems:
  • Hardware equipment of the PXI
  • Complexity of your tests
The following runtime system subnodes are available for configuration.
Table 9. Available Runtime Systems
Subnode Description
Watchdog Configure the watchdog signal of the runtime system.
TestLogFile Configure the file size of the test log.
ResultLogFile Configure the file size of the result log.
PAclusterMember Determine the role of the runtime system in a PAcluster.

Complete the following steps to configure a runtime system:

  1. Open PCU configuration settings » Runtimesystems.
  2. Add a runtime system using one of the following options.
    • Copy an existing runtime system.
    • Create a runtime system by adding a new node. New runtime systems have default values.
  3. Enter the sequential Id of the runtime system as an integer.
  4. For Pabsize, enter the size of the memory for the process image in bytes.
    The following tasks share the available memory:
    • Operating system tasks
    • Runtime system tasks
    • PAB tasks
    When you use a single runtime system, a maximum of 3.9 GB can be reserved for the PAB. You can perform a case-specific diagnosis by querying the following channels:
    • SYSINFO_MEM: General free-working memory in bytes.
    • SYSINFO_PAB: Available PAB memory in bytes.
  5. For Processor, enter the CPU core on which the runtime system calculates.
    Each runtime system can occupy one processor core. The Processor parameter is only evaluated if you specify a multicore boot image.
  6. Select the Type of the runtime system.
    OptionDescription
    normal The fastest option that does not provide a storage context history.
    • Only has simple, stateless error messages.
    • Function-related SYSINFO channels are not supported.
    instrumented The standard setting that is useful for required performance and diagnostic functions.
    • Based on the normal option.
    • Has storage context history and complete logs for detailed analysis.
    • Function-related SYSINFO channels are not supported.
    trace Special setting for detailed analysis.
    • Based on the instrumented option.
    • Trace messages are written to the hard disk.
    • Different trace configurations are possible.
    • Not suitable for productive operation due to limited real-time behavior.
  7. Optional: For AutostartTest, enter the name of the test that appears when the runtime system starts.
    The test must be located in the vspN directory on the PXI controller.
  8. For TraceHistorySize, enter the number of entries in the history table.
    The TraceHistorySize parameter is useful when the default buffer depth is not sufficient for a cycle loss analysis.
  9. For DspMessageQueueSize, enter the number of entries the data storage can buffer.
    The DspMessageQueueSize parameter is useful when the buffer of the data storage is temporarily insufficient.
  10. For Encoding, select the definition of the code page and character set that the RTS uses.
    The RTS uses Encoding to read the test description.
  11. Optional: For HostIp0Interface, enter the name of the network interface written to the system variable hostIp0.
    If HostIp0Interface is empty, the activated network interfaces with the configured IP address respective to the activated DHCP.