Experimental Physics and
Industrial Control System

"Kasemir, Kay" <[email protected]> · Tue, 29 May 2018 13:03:08 +0000

Hi:

The file path must be a workspace path, i.e. something valid within the Eclipse/CSS workspace.

Start  CSS.

Invoke the menu CS-Studio, Utilities, Install Samples, select both the BOY and Display Builder examples

Now this will open the start of the BOY examples in the previously started CSS instance:

    ./css --launcher.openFile '/BOY Examples/main.opi'

.. and this will open the start of the display builder examples:

   ./css --launcher.openFile '/Display Builder/01_main.bob'^C

The single quotes are required because of the space in the file names.

Note that in practice I've found this to be fragile. The open-from-command-line mechanism is technically based on a SWT locating the already running instance by looking for its main window.
In our control room, the command-line mechanism fails to find an already running instance of CS-Studio that has been running for a while.
I believe that's related to us having several operator interface computers all use the same generic "operator" login with the same NFS-mounted home directory,  and X11/GTK storing some information in the $HOME directory.
So going forward, for the 'phoebus' update project that aims to remove Eclipse from CS-Studio, we simply listen on a TCP port for files to open, which so far seems easier, faster, more reliable, and can also used by e.g. 'telnet' or 'nc' to open files.

-Kay

________________________________________
From: [email protected] <[email protected]> on behalf of J. Lewis Muir <[email protected]>
Sent: Friday, May 25, 2018 6:25 PM
To: EPICS Tech-Talk
Subject: Open .opi file from command line with CSS Display Builder?

Hello.

How do I open a .opi file from the command line with Display Builder?

The OS is macOS High Sierra 10.13.4.

I have a "Basic EPICS" nightly build from:

  https://ics-web.sns.ornl.gov/css/nightly

and I invoke it from the command line with a script named css.

I read:

  http://cs-studio.sourceforge.net/docbook/ch29.html

and:

  https://epics.anl.gov/tech-talk/2013/msg01791.php

and concluded I should run the following command:

===
$ css --launcher.openFile ./simDetector.opi
===

Unfortunately, that results in a segmentation fault.  I assume this is a
bug?

I then tried specifying an absolute path to the .opi file:

===
$ css --launcher.openFile /tmp/simDetector.opi
===

That succeeded in launching CS-Studio, but I don't see the
simDetector.opi screen anywhere.

What am I doing wrong?

Thanks!

Lewis

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System