Experimental Physics and
Industrial Control System

"Kasemir, Kay" <[email protected]> · Mon, 12 May 2014 16:47:11 +0000

Hi:

I think the recommendation would really be to have the IOC save the data.
The person who starts the scan, using CSS on the GUI PC, obviously needs to eventually see the collected data, so yes, that data must be accessible on that GUI PC, but that is usually done via a network mount to wherever the IOC saved the data.
That way, you may have 0, 1, 2, .. CSS GUIs to start/stop/monitor the scan, you can also use 'caput' on the command line or other means to control the experiment. The user interface (CSS, command line) is separated from the IOC which actually collects the data, no matter what UI.

Thanks,
Kay

On May 12, 2014, at 12:34 PM, Christian Pauly <[email protected]>
 wrote:
> Hi
> Again, i could use some advice how to proceed:
> 
> I have a working lab setup consisting out of a sensor and a stepper motor XY-table. Both are controlled via EPICS,
> i use a sscan record for doing XY scans.
> The sensor is connected via a remote pc (actually a RaspberryPi) running an epics IOC.
> 
> I have a CSS GUI to control everything. Now i want to make scans, and save the scan data (i.e. the sensor value for each X/Y-position) into a local (ASCII) file ON THE GUI PC running CSS. Not on the PC running the IOC client.
> 
> Any hint, how to implement this ?
> From the docs, i understand that the natural way is to store the data on the IOC-PC.
> 
> Thanks for any suggestion/comment
> 
> Christian Pauly

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System