RRS-II Client Setup

This section details customization options for the RRS servers file.

Before using RRS-II, it must be configured on the machine that it is running on.

Note: For setup instructions for the machine that the VRC module is running on (also referred to as the RRS-II server), refer to separate documentation provided by the VRC module vendor.

When you click RRS Connect and select an RRS-II server, 3DEXPERIENCE verifies that the RRS-II product is authorized. If it is not, the RRS-II connection attempt is ended and an error message appears.

If there are no restrictions specific to the VRC module, both RRS-II and the VRC module can run on the same machine.

RRS-II client setup involves the following topics that are discussed in more detail below:

This page discusses:

RRS Servers File Customization

The RRS servers file is read by 3DEXPERIENCE at run-time to generate the RRS-II servers list and may need to be customized before attempting an RRS connection to an RRS-II server.

Note: This file lists both RRS-I and RRS-II servers. To see the RRS servers file that is being used, select Me > Preferences > Robotics > RRS > RRS Servers File.

In this file, lines that start with a "#" are assumed to be comments. Otherwise, each line represents a Server record and, for an RRS-II server, must have the following fields (in the order indicated) separated by spaces or tabs:

<RRS-II_Server> <RRS-II_Interface_Type> SOCKET <Host> <RPC_Program_Number >

Where:

  • <RRS-II_Server> is the RRS-II Server name that is displayed in the RRS Servers list during "RRS-II Connect".
  • <RRS-II_Interface_Type> identifies the 3DEXPERIENCE RRS-II interface module used to establish the RRS-II connection between 3DEXPERIENCE and the VRC module.
    Note:

    RRS-II uses this field to create the name of the RRS-II interface shared library (and executable) file as:

    DNBRRS<RRS-II_Interface_Type>.{so | dll}
DNBRRS<RRS-II_Interface_Type>{.exe}
  • <Host> is either the host name or the IP address of the machine that the VRC module is running on. This entry can correspond to either the local machine that 3DEXPERIENCE is running on or can be a remote host on the TCP/IP network. Make sure that when a host name is specified, there is a corresponding entry in the /etc/hosts file on the machine that 3DEXPERIENCE is running on (<Windows_Install_Directory>/system32/drivers/etc/hosts on Windows machines).
  • <RPC_Program_Number> is the Remote Procedure Call (RPC) program number through which the VRC module is servicing the VRC manager service requests coming from 3DEXPERIENCE. This number is expressed in hexadecimal notation.

Example:

##############################################################
# DELMIA DNL Virtual Time VRC Managers
# 

DELMIA_DNL_VRC_Manager1              VRC_IF SOCKET             Lynxdeu 200c0000
DELMIA_DNL_VRC_Manager1_Using_VTM_IF VRC_IF_SIM_RPC_VTM SOCKET Lynxdeu 200c0000

#
# DELMIA DNL Real Time VRC Managers
#

DELMIA_DNL_Real_Time_VRC_Manager1    VRC_IF_SIM_RPC_RTM SOCKET Lynxdeu 200d0000

By default, RRS-II interface shared libraries are read from the 3DEXPERIENCE installation's <architecture>/code/bin directory (for example, win_b64/code/bin on Windows machines). However, you can specify a different directory by setting the Me > Preferences > Robotics > RRS > RRS$LIB Directory option.

ONC RPC Setup

If not provided as part of a local VRC module installation, 32-bit ONC RPC run-time components must be installed on 3DEXPERIENCE (32 and 64 bit) Windows machines. A 32-bit Windows port of ONC RPC can be downloaded from the following location:

https://sourceforge.net/projects/oncrpc-windows/ (see the oncrpc.zip link on this page)

Unzip oncrpc.zip, and perform the following steps to install it:

  • Copy oncrpc\win32\librpc\lib\Debug\oncrpc.dll to the C:\WINDOWS folder.
  • Create a new folder named PortMapperService and copy oncrpc.dll,oncrpc\win32\bin\inst_pm.exe, and portmap.exe files into it.
  • If the portmap service has not been previously installed, perform the following steps to install it:
    • Open a Command Prompt window as Administrator, cd /d into this new folder, and type .\inst_pm.exe <full path of PortMapperService folder> (for example, \inst_pm.exe C:\PortMapperService\portmap.exe) to install the portmap service.
    • Run the Windows Services app (search for Services), right-click the Portmap service in the list, select Properties and change Startup Type to Automatic so this service runs automatically when the machine is rebooted. Click Start to start it immediately.
    • Open Windows Task Manager and ensure that a process named portmap.exe is running. This process must always be running when an RRS connection to an RRS-II Server (VRC Manager) is attempted.
    • The Portmap service can be uninstalled at any time by running .\inst_pm.exe remove from a Command Prompt window run as Administrator.