Experimental Physics and
Industrial Control System

"Isenegger Andreas" <[email protected]> · Fri, 8 Aug 2008 19:26:43 +0200

Hello Joe,

Your directions showed me where to look for the substitution files. That
helped me to get the communication working, but the stage didn't move.
Then, after fiddling for hours with the parameters and reading the
source code, I got it moving flawlessly. Hence I can state that the
EPICS driver for the C-862 also works for the C-863 PI Mercury
controller.

Thanks for your help.
Regards,
Andy

-----Original Message-----
From: Joe Sullivan [mailto:[email protected]] 
Sent: Wednesday, August 06, 2008 17:16
To: Isenegger Andreas
Cc: Epics Questions
Subject: Re: EPICS support for PI C-862 Mercury motor controller

Hi Isenegger,

There are example setup files in <top>/iocBoot/iocWithAsyn of
the motorRecord distribution. st.cmd.Vx has examples of the
configuration calls for the C-862
  	PIC862Setup() and PIC862Config()
That is where the connection to the asyn port is made.

I would recommend looking at the motor.substitutions file
(also in that directory) for a nice template for loading
motor records.

Your asyn port setup looks right to me.

Joe

Isenegger Andreas wrote:
> Hello All,
> 
>  
> 
> According to the 'motor record' manual V6.1, the motor record has 
> support built in for the PI C-862 Mercury motor controller from Physik

> Instrumente GmbH. It is connected via RS-232 to the IOC.
> 
>  
> 
> I am supposed to control this device via EPICS. It seems obvious to
use 
> the motor record. However, I don't have the faintest clue what to put 
> into the 'OUT' field of the record to make it connect to the dedicated

> serial channel. Can anybody help me here (example, documentation, 
> instructions, ...)?
> 
>  
> 
> What I found out by doing a
> 
>   #> grep device /work/iocBoot/R3.14.8/dbd/motor-test.dbd
> 
> is that I should write 'PIC862' into the DTYP field.
> 
> Furthermore, I think I know how to configure the asyn driver in the 
> startup script to open a serial port:
> 
>   drvAsynSerialPortConfigure ("BusC863Ctrl", "/dev/ttyS0")
> 
>   asynSetOption ("BusC863Ctrl",   0, "baud",    "9600")
> 
>   asynSetOption ("BusC863Ctrl",   0, "bits",    "8")
> 
>   asynSetOption ("BusC863Ctrl",   0, "parity",  "none")
> 
>   asynSetOption ("BusC863Ctrl",   0, "stop",    "1")
> 
>   asynSetOption ("BusC863Ctrl",   0, "clocal",  "Y")  # Y = ignore
DTR/DSR
> 
>   asynSetOption ("BusC863Ctrl",   0, "crtscts", "N")  # N = ignore
RTS/CTS
> 
>  
> 
> Any help appreciated.
> 
>  
> 
> Thanks and regards,
> 
> Andy
> 
>  
> 
>  
> 
> ----------------------------------
> 
> Andreas Isenegger
> 
> Section 'Control Systems'
> 
> Swiss Light Source
> 
> Paul Scherrer Institute, WBGB/003
> 
> CH-5232 Villigen PSI, Switzerland
> 
> Tel/Fax: ++41 (56) 310 5125/4413
> 
> ----------------------------------
> 
>  
> 

-- 
Joseph Sullivan
[email protected] <> 630-252-8657
Advanced Photon Source
APS Engineering Services Division
Beamline Controls & Data Acquisition Group

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System