EPICS Controls Argonne National Laboratory

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: problem with MCA module (Struck 3820 board), ACQUIRING command
From: Jay Steele <[email protected]>
To: "[email protected]" <[email protected]>
Date: Fri, 29 Oct 2010 20:26:48 -0700
Hi Tech-talk,
    I'm using epics-3-14-11, mca-s55 to try to control a Struck (SIS) 3820 VME board. I'm using a PPC mother board running vxWorks.
 
    I run the following in my startup script using the examples in mca-s55/iocBoot/iocVxWorks for SIS3820.
 
mcaSIS3820Setup(0xA0000000, 224, 6)
mcaSIS3820Config("mcaSIS3820/1", 0, 2048, 32, 2, 0, 1000000)
dbLoadTemplate("SIS3820_32.substitutions")
 
I get the following error after pmacVmeInit:
 
drvMcaSIS3820Asyn::drvUserCreate, unknown command=ACQUIRING
21:D3:BNP:scalar1:ReadCallback devAsynInt32::initCommon drvUserCreate
 
    This error seems to come from the following in SIS3820_32.substitutions.
 
file "$(MCA)/SIS3820.db"
{
pattern
{P,         INP}
{21:D3:BNP:scalar1:,  "@asyn(mcaSIS3820/1 0)"}
}
 
and SIS3820.db:
 
record(ai,"$(P)ReadCallback") {
       field(SCAN,"I/O Intr")
       field(DTYP, "asynInt32")
       field(INP, "$(INP)ACQUIRING")
       field(FLNK, "$(P)ReadAll.PROC PP MS")
}
 
When I change "ACQUIRING" to "MCA_ACQUIRING" (based on a quick review of the source code), the script seems to work correctly. Is this the correct solution?
 
Also assuming that the correct command is "MCA_ACQUIRING" - when I run scaler32_full.adl to see the data from the SIS3820 board and have a signal generator generating a 3.3V pulse train at 25 Hz connected to input #9, I only see the counts from the internal clock at input #1. Anybody have any hints on how to activate input #9? Attached is the screen shot from the MEDM screen.
 
Thanks,
 
Jay Steele
XRadia Corporation


The information in this email, including any attachments, is confidential and intended only for the recipient(s) listed. Any use of this email for any other purpose is prohibited. If you have received this email in error, please notify me immediately by reply email, delete this email, and do not disclose its contents to anyone.

Attachment: MEDM screen.JPG
Description: MEDM screen.JPG


Replies:
RE: problem with MCA module (Struck 3820 board), ACQUIRING command Mark Rivers

Navigate by Date:
Prev: RE: cygin-x86-debug behavior Mark Rivers
Next: RE: problem with MCA module (Struck 3820 board), ACQUIRING command Mark Rivers
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: cygin-x86-debug behavior J. Lewis Muir
Next: RE: problem with MCA module (Struck 3820 board), ACQUIRING command Mark Rivers
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 
ANJ, 29 Oct 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·