Experimental Physics and Industrial Control System
Hi Kevin,
Thank you for the note! That is indeed a recent development. A few observations:
- Our driver does not use the EPICS motor record (this could be positive or negative, depending on your use case)
- From the README it appears David's driver does not support changing positioner type and use of rotary stages, which the PSI driver should
- I was not aware of the step size (nm -> pm) difference from the MCS - I will be changing the default 'slope' accordingly, thanks...
==> Though according to the MCS2 manual rotary stages typically use nano-degree steps
- And of course, the fact that David's driver seems to have been tested is certainly an advantage over ours :)
Of course, I am sure both modules will be improved over time. When we do eventually get a test unit, I will make sure to let the community know.
Best,
Scott
__________________________________________
Scott Stubbs
Controls Group
Paul Scherrer Institut
5232 Villigen PSI
Schweiz
Telefon: +41 56 310 21 65
E-Mail: [email protected]
-----Original Message-----
From: Peterson, Kevin M. <[email protected]>
Sent: Mittwoch, 17. Juli 2019 17:45
To: Stubbs Scott Allen (PSI) <[email protected]>; [email protected]
Subject: Re: SmarAct MCS2 ASCII-based IOC
David Vine recently wrote an asyn motor driver for the MCS2 that uses ASCII commands instead of the vendor's C++ library. The driver can be found in the motorSmarAct module:
https://github.com/epics-motor/motorSmarAct
The README for the MCS2 support is here:
https://github.com/epics-motor/motorSmarAct/blob/master/smarActApp/src/README.SmarActMCS2
Kevin
On 7/17/19 4:31 AM, Stubbs Scott Allen (PSI) via Tech-talk wrote:
> Dear Tech-talkers,
>
> As it seems there is no fully ASCII-'byte stream' based IOC for the
> SmarAct MCS2 (at least not available publicly) I am pleased to present
> our first attempt at one using StreamDevice. I began developing it
> based on our MCS IOC when we believed we would need to integrate the
> MCS2 for a particular project. As we purchased the MCS in the end, and
> we have no MCS2 units for testing, our development has also stopped
> for the time being.
>
> Comments, forks, additions and/or fixes welcome. Note that while we
> have put some effort in converting commands and EPICS records from the
> MCS (e.g. positioner types, amplifier voltage.) this is a completely
> untested IOC and still based around our internal PSI build system.
> However, the db/ and cfg/ files can be considered universal. If I get
> permission from SmarAct I will publish their full documentation here
> as well.
>
> Also, a special thank you to SLAC colleagues who gave me a starting
> point for the protocol file =)
>
> Link:
>
> https://github.com/paulscherrerinstitute/smaract_mcs2/
>
> Greetings from Switzerland,
>
> Scott
>
> __________________________________________
> Scott Stubbs
>
> Controls Group
>
> Paul Scherrer Institut
> 5232 Villigen PSI
> Schweiz
>
> Telefon: +41 56 310 21 65
> E-Mail: [email protected]
>
- References:
- SmarAct MCS2 ASCII-based IOC Stubbs Scott Allen (PSI) via Tech-talk
- Re: SmarAct MCS2 ASCII-based IOC Peterson, Kevin M. via Tech-talk
- Navigate by Date:
- Prev:
RE: USBTMC Device can not autoConnect Mark Rivers via Tech-talk
- Next:
RE: USBTMC Device can not autoConnect Mark Rivers via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: SmarAct MCS2 ASCII-based IOC Peterson, Kevin M. via Tech-talk
- Next:
USBTMC Device can not autoConnect Christopher Herrmann via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024