Hi Christian,
Here are the possible causes I can think of:
Does the scan progress even though it's not moving the positioners? If so, the sscan record must be writing to something, because it's getting callbacks from that thing.
Are the two iocs on the same subnet? If not, you should set the EPICS_CA_ADDR_LIST environment variable for the scanning ioc so it includes the IP address of the positioner ioc.
Are you running access control on the positioner ioc ? If so, you should arrange for the scanning ioc to have read/write access.
Is there by chance another ioc hosting PVs with the same names as those the sscan record is writing to? If so, the sscan record may have connected to the wrong PVs.
Can other records in the scanning ioc write to the positioners? If so, there may have been a problem in the sscan module's build.
Has the sscan record ever successfully written to those PVs? If so, it could be stuck waiting for a callback. If you clear and retype the PV name that problem should go away.
If none of this helps, please send the output of
dbpr("name of sscan record","1")
Tim Mooney
________________________________________
From: [email protected] [[email protected]] on behalf of Christian Pauly [[email protected]]
Sent: Tuesday, July 01, 2014 6:56 PM
To: EPICS Tech Talk
Subject: sscan records
Dear folks,
i have two questions regarding sscan record, maybe someone can help:
1) Is there anythig wrong with running a sscan record on one ioc on one
computer, reading data values from a sensor connected to this ioc, but
using positioners controlled by a second ioc on a second pc via
channelaccess ?
Or the other way round: does the sscan recond has to run on the same ioc
as the positioner controls ?
Somehow my positioners (controlled by second ioc) dont move at all if i
start the scan. Manual control of the positioners via caput works fine.
2) I can not dont find good documentation on how to save scan data (from
a 2-dim scan) to a file. Can anyone give me a simple receipe on how to
do this ? Do i need an extra module for this ?
Thanks a lot for any help !
Chrstian
- Replies:
- Re: sscan records Christian Pauly
- References:
- sscan records Christian Pauly
- Navigate by Date:
- Prev:
Re: Problems using devSnmp from NSCL John A. Priller
- Next:
Re: Problems using devSnmp from NSCL Florian Feldbauer
- 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: sscan records Mi Qingru
- Next:
Re: sscan records Christian Pauly
- 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
|