EPICS Home

Experimental Physics and Industrial Control System


 
1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  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  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: 答复: AutoSaveRestore of the motor position
From: 张招红 <[email protected]>
To: "'Mark Rivers'" <[email protected]>, <[email protected]>
Cc: "'Zheng Lifang'" <[email protected]>
Date: Wed, 12 May 2010 10:25:00 +0800
Yes,Ron Sluiter has told me the message!We are trying to do the things he
suggested.
Thank you very much for your help.

Zhang


-----邮件原件-----
发件人: Mark Rivers [mailto:[email protected]] 
发送时间: Wednesday, May 12, 2010 9:32 AM
收件人: ???; [email protected]
主题: RE: AutoSaveRestore of the motor position

I think Ron Sluiter has already told you this, but for the benefit of others
on tech-talk: 
this appears to be a known problem with the MAXv, and you should return it
for new firmware.
 
Mark
 

________________________________

From: ??? [mailto:[email protected]]
Sent: Tue 5/11/2010 8:06 PM
To: Mark Rivers; [email protected]
Subject: ??: AutoSaveRestore of the motor position



The version of the motor is MotorR6-2-2,the epics is base-3.14.8.2.
Sorry,the scanning is just the step by step mode.

Zhang

-----????-----
???: Mark Rivers [mailto:[email protected]]
????: Tuesday, May 11, 2010 7:36 PM
???: ???; [email protected]
??: RE: AutoSaveRestore of the motor position

What version of the motor software?  When you say on-the-fly scanning, are
you just telling the motor to go to the end of travel and then reading the
motor positions along the way?

Mark


________________________________

From: ??? [mailto:[email protected]]
Sent: Mon 5/10/2010 11:52 PM
To: Mark Rivers; [email protected]
Subject: ??: AutoSaveRestore of the motor position



It seems that we should pay more attendion to the MAXv board.
In XAFS beamline EPICS is used for DCM control and LAbVIew8.6 for user
experiments. The interface between LabVIew and EPICSThe is DSC module
developed by NI.
The boot process of the VME/IOC with all MAXv-8000s is normal.
When the user is doing the on-the-fly energy scanning(Bragg), the
corresponding MAXv crashes and has no any response to the input command. The
GREEN LED(D6) on the MAXv board flashes with GREEN LED(D4) on.(Normally D6
is off and D4 is on).

Till now it's still difficult for us to diagnose the problem, the DSC
interface, the network transport, the driver or even the MAXv controller
itself?

Zhang Zhaohong

-----????-----
???: Mark Rivers [mailto:[email protected]]
????: Monday, May 10, 2010 8:58 PM
???: ???; [email protected]
??: RE: AutoSaveRestore of the motor position

I think the first thing you need to do is to figure out what is wrong with
the MAXv.  There has been a recent discovery of problems with MAXv modules
occasionally not being available when the system boots, but I believe that
will hang the boot process, so should not lead to the problem you are
seeing.  What do you mean by "crashes"?  Was it working at all during that
boot of the IOC?

The problem with save/restore is harder to solve.  One way to do it is to
note when the MAXv crashes, and just manually edit the auto_positions.sav
file before rebooting again to put in the last known good values from a
periodic backup or the last good boot.  But if the MAXv worked for a while
before crashing during the current boot, that may not be possible.

Mark


________________________________

From: [email protected] on behalf of ???
Sent: Sun 5/9/2010 11:12 PM
To: [email protected]
Subject: AutoSaveRestore of the motor position



Hi,everybody,



In SSRF beamline control we use the autosave module to save the 'DVAL' field
and restore the value of a motor position when rebooting.

Recently we encountered  a  problem.



Sometimes one of the controllers(MAXv-8000) in a VME crate crashes while the
IOC(mvme5500) still runs. Because the motor channel is still connected, the
system looks OK. In this case if changing the 'DVAL' field to drive the
motor, the controller doesn't response and  the 'DRBV' of the motor keeps
unchanged. So the saved value 'DVAL' isn't no long the motor real position.



When hard rebooting the VME crate, the  'DRBV' set by the recovered 'DVAL'
doesn't match the motor real position.



Are there some problems in our saving and restoring method? How to deal with
this kind of problem?



Any suggestion will be greatly appreciated!



===================================================
Zhang Zhaohong(???)
No.239 Zhangheng Road
PuDong District
Shanghai Institute of Applied Physics CAS
Shanghai, China
Tel: +86-21-33933238










References:
RE: AutoSaveRestore of the motor position Mark Rivers

Navigate by Date:
Prev: RE: AutoSaveRestore of the motor position Mark Rivers
Next: Re: MAXv vs XPS liuping
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: AutoSaveRestore of the motor position Mark Rivers
Next: Re: AutoSaveRestore of the motor position Ron Sluiter
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024