Starting the Kuka RRS Server

You can choose from multiple methods to start the Kuka RRS server.

This task shows you how to:

Before you begin: You must have already installed the Kuka KRC 1.XX RRS Server and Windows Services for UNIX.

Start the server from a Korn shell

Use Windows SFU Korn shell (ksh) to start the Kuka RRS Server as follows.

  1. Open a Windows SFU Korn shell.
  2. Change to the \KUKA_KRC1__1.XX\bin folder.
    Example: cd /dev/fs/C/krc/rrs1/KUKA_KRC1__1.XX/bin
  3. If pid.log exists, remove it first.
    Example: rm pid.log
  4. Set the library path to the current folder.
    Example: export LD_LIBRARY_PATH=/dev/fs/C/krc/rrs1/KUKA_KRC1__1.XX/bin
  5. The following three flags are required for the RCS Server (rcssrv_KUKA_KRC1__1.XX):
    • -tcp: defines the TCP port to communicate with V6
    • -log: specifies name and location of the logfile
    • -pid: specifies the file for the process ID
    Syntax: ./rcssrv_KUKA_KRC1__1.XX -tcp 2800 -log ./rcs.log -pid ./pid.log
  6. Execute the krc1test.exe utility provided in ..\KUKA_KRC1__1.XX\bin and choose either the license server or the license file provided by Kuka to have the license registered properly.

    In the case of a node locked license, this will result in the creation of a My Computer/HKEY_LOCAL_MACHINE/SOFTWARE/FLEXlm License Manager/KUKAROB_LICENSE_FILE Windows registry key that points to the RCS license file. See the file ..\KUKA_KRC1__1.XX\bin\enduser.pdf for any RCS FLEXlm licensing questions.

    Note: This step needs to be done only once.
    Note: You can alternatively configure a server-based floating RCS license environment. See Configuring and Using a Server-based License.

Start the server using a batch file

You can also start the server from a batch file.

Instead of typing in the commands described above each time, you can instead create a kuka_rrs_server_start.ksh batch file to start the server.

  1. Create a batch file with the following content (as an example). 
    cd /dev/fs/C/krc/rrs1/KUKA_KRC1__1.XX/bin
rm ./rcs.log
rm ./pid.log
export LD_LIBRARY_PATH=/dev/fs/C/krc/rrs1/KUKA_KRC1__1.XX/bin
./rcssrv_KUKA_KRC1__1.XX -tcp 2800 -log ./rcs.log -pid ./pid.log
echo Kuka RRS Server started
pause
  2. Double-click the saved file to start the server.

Start the server using SFU Korn shell aliases

You can also use Korn shell aliases to start the server.

Instead of typing in the commands described above each time, you can instead define aliases similar to the following in the user's .profile file and simply invoke these aliases (kuka_rrs_server_start/stop) in a SFU Korn shell to start/stop the Kuka RRS Server.

  1. Add aliases similar to the following in your .profile file. 
    alias kuka_rrs_server_clean='rm -f /dev/fs/C/krc/rrs1/KUKA_KRC1__1.XX/bin/*.log'
alias kuka_rrs_server_start=' kuka_rrs_server_clean; 
    export LD_LIBRARY_PATH=/dev/fs/C/krc/rrs1/KUKA_KRC1__1.XX/bin;  
    ./rcssrv_KUKA_KRC1__1.XX -tcp 2800 -log ./rcs.log -pid ./pid.log'
alias kuka_rrs_server_stop='kill `cat /dev/fs/C/krc/rrs1/KUKA_KRC1__1.XX/bin/pid.log`'
  2. In a SFU Korn shell, use kuka_rrs_server_start and kuka_rrs_server_stop to start and stop the server.

Run multiple servers and RCS versions from the same machine

You can also run multiple Kuka RRS Servers (each running a different RCS version) on the same RCS server machine.

This is accomplished by installing each RCS module version in a different root folder and starting each RCS server by specifying a different TCP port number, PID and LOG file.

Note: The default KUKA_KRC1__1.XX\bin and data folders must not be renamed.

Before you begin:

To start more than two RCS servers, the .profile file must be modified. The example that follows assumes the following directory structure.



All steps required for a typical single RCS server are still required, as well as the following modifications to the .profile file.

  1. Declare the proper variables for each server. 
    export KRC1_52_RCS_BIN_DIR=/${DNB_RCS_DRV}/RRS/Kuka-5.2/KUKA_KRC1__1.XX/bin
export KRC1_56_RCS_BIN_DIR=/${DNB_RCS_DRV}/RRS/Kuka-5.6/KUKA_KRC1__1.XX/bin
export LD_LIBRARY_PATH_52=/${DNB_RCS_DRV}/RRS/Kuka-5.2/KUKA_KRC1__1.XX/bin
export LD_LIBRARY_PATH_56=/${DNB_RCS_DRV}/RRS/Kuka-5.6/KUKA_KRC1__1.XX/bin
export LD_LIBRARY_PATH="${LD_LIBRARY_PATH_52}:${LD_LIBRARY_PATH_56}"
  2. Declare specific aliases for each server. 
    # KRC1 specific aliases
alias krc1_52_start="cd ${KRC1_52_RCS_BIN_DIR}; ./rcssrv_KUKA_KRC1__1_5.2.XX 
    -tcp 28052 -log ${LOG_DIR}/rcssrv_KUKA_KRC1__1_5.2.XX.log -pid 
    ${LOG_DIR}/rcssrv_KUKA_KRC1__1_5.2.XX.pid;“
alias krc1_56_start="cd ${KRC1_56_RCS_BIN_DIR}; ./rcssrv_KUKA_KRC1__1_5.6.XX 
    -tcp 28056 -log ${LOG_DIR}/rcssrv_KUKA_KRC1__1_5.6.XX.log -pid 
    {LOG_DIR}/rcssrv_KUKA_KRC1__1_5.6.XX.pid;“
alias krc1_stop='kill `cat //${LOG_DIR}/rcssrv_KUKA_KRC1__1_5.2.XX.pid`'
alias krc1_stop='kill `cat //${LOG_DIR}/rcssrv_KUKA_KRC1__1_5.6.XX.pid`'
  3. Create a conditional RCS start. 
    # Check and if necessary start RCS server daemon
krc1_52_rcs_running=`ps -o comm -e | grep rcssrv_KUKA_KRC1__1_5.2.XX`
krc1_56_rcs_running=`ps -o comm -e | grep rcssrv_KUKA_KRC1__1_5.6.XX`
if [ -z "${krc1_52_rcs_running}" ]
  then
    echo
    echo STARTING UP RCS SERVER 5.2 ON `hostname` AT `date`:
    # write loggin into tmp
    rm -f ${LOG_DIR}/rcssrv_KUKA_KRC1__1_5.2.XX.log
    rm -f ${LOG_DIR}/rcssrv_KUKA_KRC1__1_5.2.XX.pid
    krc1_52_start
fi

if [ -z "${krc1_56_rcs_running}" ]
  then
    echo
    echo STARTING UP RCS SERVER 5.6 ON `hostname` AT `date`:
    # write loggin into tmp
    rm -f ${LOG_DIR}/rcssrv_KUKA_KRC1__1_5.6.XX.log
    rm -f ${LOG_DIR}/rcssrv_KUKA_KRC1__1_5.6.XX.pid
    krc1_56_start
fi
  4. After making the changes above to the .profile file, reboot the machine and open the Windows Task Manager to verify that the following processes are running.
    • rcssrv_KUKA_KRC1__1_5.2.XX
    • rcssrv_KUKA_KRC1__1_5.6.XX

Verify that the server is running

The following steps describe how to ensure that the server is running.

  1. Open the Task Manager.
  2. Display all running processes via Processes tab and sort them by name.
  3. Verify that rcssrv_KRC1__1.XX is running: