| 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 2025 | 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 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Seeking config advice for smarAct MCS controller |
| From: | Torsten Bögershausen via Tech-talk <tech-talk at aps.anl.gov> |
| To: | "Jemian, Pete R." <jemian at anl.gov>, EPICS Tech Talk <tech-talk at aps.anl.gov>, "Reinhardt, Juliane" <jreinhardt at lbl.gov> |
| Date: | Tue, 20 Oct 2020 14:01:29 +0200 |
On 20/10/20 01:15, Jemian, Pete R. via Tech-talk wrote:
Here's a question from Juliane Reinhardt, ALS:
> anyone having some advice for connecting motors to a smarAct MCS
controller? What does the channel number mean? Our .iocsh file looks
like this
### Motors
# Motors substitutions, customize this for your motor
dbLoadTemplate "motor.substitutions.smaractmcs_201"# Configure each
controller
#origvalues# drvAsynIPPortConfigure("MCS_ETH","192.168.1.17:2102",0,0,0)
drvAsynIPPortConfigure("MCS_ETH","192.168.168.201:5000",0,0,0)#
Controller port, asyn port, number of axis, moving poll period, idle
poll period
# smarActMCSCreateController(const char *motorPortName, const char
*ioPortName, int numAxes, double movingPollPeriod, double idlePollPeriod);
smarActMCSCreateController("MCS", "MCS_ETH", 1, 0.020, 1.0)# Controller
port, axis number, controller channel
# smarActMCSCreateAxis(const char *motorPortName, int axisNumber, int
channel)
smarActMCSCreateAxis("MCS", 0, 0);
This doesn't seem to be a good thing.
The axis number is the EPICS axis number - it must start with 1.
The channel is the axis number inside the controller - I don't
know if they start counting at 0 ?
Not having such a controller, I would speculate and try
smarActMCSCreateAxis("MCS", 1, 0);