EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
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: MAXv issue
From: Dirk Zimoch <[email protected]>
To: [email protected]
Cc: [email protected]
Date: Tue, 23 Nov 2010 12:09:32 +0100
Hi Austen,

What I actually see is that at a normal move the motor runs in the wrong direction. The retry then corrects this provided the limit switch is not hit.

The IOC sends: "AT VB1250 VL5000 AC7500 AF MR-162 GD ID"

Then when polling the status with "AT QA EA", the MAXV replies "PNNN,DDNNN", clearly announcing that is runs in POSITIVE direction even though it has been commanded to run -162 steps..

We use the sscan record to do the scan. The MAX is used with internal encoder feedback.

Dirk


[email protected] wrote:
Hi Dirk,

I have seen a similar problem, although not quite the same.

To get a higher update rate into the archiver I did the following
(MVME5500 processor running vxWorks):
1/ sysClkRateSet(1000)
2/ MAXvSetup(1, 16, 0xF000, IVEC, 5, 60)
In the cmd file, and this gives me 60 Hz data.

However, when running in this configuration I get an unrequested move
following a successful move that has a retry. This unrequested move then
takes it off to "infinity".




Are you seeing the problem following (and only following) a retry?


Regards,

Austen Rose.



-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Dirk Zimoch
Sent: 23 November 2010 10:10
To: EPICS
Subject: MAXv issue

Hi MAXv users,

We see a problem here with our MAXv cards and I want to ask if anyone has seen the same effect. This could help us to understand what's
happening.

During a long series of scans that drives a motors in negative direction

in pretty small steps, it happens in rare cases that the motor instead runs forward a quite large amount, possibly hitting the limit switch.

We have observed this behavior a few times in intervals of some three hours. Then again nothing went wrong for days. The problem happened with

two different axes and on several different MAXv cards (including cards with and without the latest bug fix -> see Ron Sluiter's mail "OMS MAXv announces fix" from October 27)

Pro-Dex is informed but they would like to have more input on the specific circumstances. Thus my question: Has anyone seen a similar effect? Under which circumstances did it happen?

Dirk


Replies:
RE: MAXv issue austen.rose
References:
MAXv issue Dirk Zimoch
RE: MAXv issue austen.rose
Navigate by Date:
Prev: RE: MAXv issue austen.rose
Next: RE: MAXv issue austen.rose
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: MAXv issue austen.rose
Next: RE: MAXv issue austen.rose
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, 23 Nov 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·