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: Newport XPS and Motor record |
From: | John Dobbins <[email protected]> |
To: | [email protected] |
Date: | Mon, 27 Jun 2011 14:29:00 -0400 |
All, Thanks for the various replies.If I look in the XPS web interface I don't see any errors reported there. Should I expect to see them there?
The stages actually move normally. And report statuses that would be expected, "Ready from Homing", "Reading from Moving", ...
Also I have two different stage types connected and both types produce this error.
The XPS configuration was generated by the XPS using that option as available in the web interface. Limits, velocities, ... appear to be set correctly. So I can't tell what the XPS is complaining about.
John On 6/27/2011 11:57 AM, John Hammonds wrote:
I once had a problem that the configured velocity (in the motor record) was not allowed by the XPS. It returned the same error code. This was a manually configured motor. We had to play around a bit to get the XPS configuration correct. John On 6/27/2011 10:52 AM, Pete Jemian wrote:John: What is your configuration in the XPS controller? Can that have some influence? Pete On 06/27/2011 09:51 AM, [email protected] wrote:Hi, It could also be that the XPS axis is in the wrong 'state'. I think it needs to be in 'ready state' (states 10 to 13) to receive move commands. I updated the XPS driver recently. So in the next release of the motor support module the driver should indicate if there is a problem (via the motor record MSTA field). So if the axis is in a state which means you can't move it then you will be notified by the record going into alarm state. Cheers, Matthew-----Original Message----- From: [email protected] [mailto:tech-talk- [email protected]] On Behalf Of Mark Rivers Sent: 27 June 2011 15:17 To: John Dobbins; EPICS Tech-Talk Subject: RE: Newport XPS and Motor record Hi John, If you translate that error code, -22, using ErrorStringGet in the XPS Web terminal interface you will get: 0,Error -22 : Not allowed action So there is something illegal about the request you are making. Is it possible that you are exceeding a soft limit, etc.? Mark -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of John Dobbins Sent: Monday, June 27, 2011 8:38 AM To: EPICS Tech-Talk Subject: Newport XPS and Motor record All, I am using Motor Record R6-4-4 , EPICS R3.14.9, ASYN 4-9 with a Newport XPS controller. When I send a new position to an actuator I get a messages in the IOC like this: epics> 2011/06/24 12:35:35.552 SendAndReceive unexpected response =-22,GroupMoveAbsolute (GROUP2.POSITIONER,12.00003072008),EndOfAPI otherwise everything seems to be working, i.e. motor responds properly. Does someone know what this means? The XPS set-up portion of my st.cmd script is below. Regards and Thanks, John Dobbins Cornell University The XPS set-up portion of my st.cmd script: # cards (total controllers) XPSSetup(1) # card, IP, PORT, number of axes, active poll period (ms), idle poll period (ms) XPSConfig(0, "erpxps01", 5001, 3, 10, 500) # asyn port, driver name, controller index, max. axes) drvAsynMotorConfigure("XPS1", "motorXPS", 0, 3) # card, axis, groupName.positionerName, stepsPerUserUnit # PR50CC rotational stage XPSConfigAxis(0,0,"GROUP1.POSITIONER",100) # CMA-12CCCL linear stage XPSConfigAxis(0,1,"GROUP2.POSITIONER",20480) # CMA-12CCCL linear stage XPSConfigAxis(0,2,"GROUP3.POSITIONER",20480)