Experimental Physics and
Industrial Control System

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	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
<== Date ==>		<== Thread ==>

Subject:	Re: pmacAsynCoord in-position vs .MOVN
From:	"Knap, Giles \(DLSLtd,RAL,LSCI\) via Tech-talk" <tech-talk at aps.anl.gov>
To:	"Hidas, Dean" <dhidas at bnl.gov>, "J. Lewis Muir" <jlmuir at imca-cat.org>
Cc:	"tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date:	Thu, 18 Feb 2021 11:20:38 +0000

Hi Dean, Lewis,

First re EPICS support modules. https://github.com/dls-controls/pmac is the one that DLS currently supports and includes all the functionality from tpmac, plus supports the power pmac and trajectory scanning, among other things.

Regarding your MOVN issue:

The driver looks at a few axis flags to determine if it reports the axis is moving:

In Position Bit == 1 (bit 1 of status word 2) OR
Motor On Bit == 0 (bit 23 of status word 2) OR
Amplifier Enabled == 0 (bit 19 of status word 1)

You can see the value of these status bits directly with the terminal command (for axis 1)

#1?

The LSB of the number printed is In Position Bit, if this is set to 0 when you see your issue then its due to the configuration of that axis.

The pmac sets in position for an axis under the following circumstances

1. The motor must be in closed-loop control;

2. The desired velocity must be zero;

3. The magnitude of the following error must be less than In-position deadband Ixx28;

4. The move timer must not be active;

5. The above four conditions must all be true for (Ixx88+1) consecutive scans.

I have seen a situation where the tuning of the motor is such that it may stop outside of the in-position deadband so this would be something to look for.

I hope this helps,

giles.

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of J. Lewis Muir via Tech-talk <tech-talk at aps.anl.gov>
Sent: 16 February 2021 21:10
To: Hidas, Dean <dhidas at bnl.gov>
Cc: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: Re: pmacAsynCoord in-position vs .MOVN

On 02/16, Hidas, Dean via Tech-talk wrote:
> I'm using pmacAsynCoord with a pmac turbo2 brick controller. What I notice is that occasionally the pmac reports that a move is finished, that the coordinate system is not motion, but the .MOVN field of the motor record stays high despite reaching the desired position and not actually being in motion. At this point the pmac reports in position, but the motor record does not seem to have any additional control effect (nor should it I believe), ie the .MOVN field stays high but there is no further motion. Are there any motor record fields or other parameters you might advise having a look at that could have an effect on this?

Hi, Dean!

Haven't seen that before. I initially thought it might be an issue I
reported a while ago

https://github.com/epics-modules/tpmac/pull/4

but after reading your description of the problem more carefully, I
don't think it's the same thing.

Where did you get pmacAsynCoord? There seems to be at least three PMAC
drivers floating around that I know of:

1. https://www.gmca.aps.anl.gov/TPMAC2/
2. https://github.com/epics-modules/tpmac
3. https://github.com/dls-controls/pmac

#1 is the original, #2 seems to be a friendly fork of #1, and #3 is a
driver for which I don't know its lineage.

Also, what version of the driver are you using?

Regards,

Lewis

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

References:: pmacAsynCoord in-position vs .MOVN Hidas, Dean via Tech-talk; Re: pmacAsynCoord in-position vs .MOVN J. Lewis Muir via Tech-talk

Navigate by Date:: Prev: Re: Accessing waveform record values in C Andy Foster via Tech-talk; Next: Re: Identical Process Variable names on Multiple Servers 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: pmacAsynCoord in-position vs .MOVN J. Lewis Muir via Tech-talk; Next: interest in database applications working group Hartman, Steven 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

ANJ, 18 Feb 2021

· Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System