Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020 
<== Date ==> <== Thread ==>

Subject: Re: Problems using Epics R3.14.3 with mvme5110 PowerPc
From: "Kiman Ha" <hkm@slac.stanford.edu>
To: <dba@ing.iac.es>
Cc: <tech-talk@aps.anl.gov>
Date: Thu, 18 Sep 2003 09:58:45 +0900
Hi, 
Dennis Armstrong

I had a same experience at the MVME5110 with Tornado 2.2 .
That time jeff helped for fixing that problem.
What kind tornado version used?
When the making the vxworks Kernel, If you added (remote route protocol? component) that component with epics CA making problem.

at the your task list you can not found "CAS-UDP" tasks. "CAS-UDP" task for CA client.
I'm sorry I'm visiting at SLAC ESD group, my problem note leave at PLS in KOREA.

This problem was same as last year when the starting Tornado2.2 with MVME51xx SBC.



NAME          ENTRY         TID   PRI   total % (ticks)  delta % (ticks)
--------     --------      -----  ---   ---------------  ---------------
tExcTask     excTask    1efe5290    0     0% (       0)    0% (       0)
tLogTask     logTask    1efe26f0    0     0% (       0)    0% (       0)
tShell       shell      1eee7460    1     0% (       0)    0% (       0)
tRlogind     rlogind    1eef7b50    2     0% (       0)    0% (       0)
tWdbTask     wdbTask    1eeefe30    3     0% (       0)    0% (       0)
tAioIoTask1  aioIoTask  1eff43b0   50     0% (       0)    0% (       0)
tAioIoTask0  aioIoTask  1efed130   50     0% (       0)    0% (       0)
tNetTask     netTask    1efa41a0   50     0% (       1)    0% (       1)
tAioWait     aioWaitTas 1effb630   51     0% (       0)    0% (       0)
tPortmapd    portmapd   1eefaf40   54     0% (       0)    0% (       0)
tTelnetd     telnetd    1eef57a0   55     0% (       0)    0% (       0)
tRipTimerTas ripTimer   1eee86a0  100     0% (       0)    0% (       0)
tRipTask     ripTask    1eef21f0  101    97% (    1551)   97% (    1551)
syncNTP                 1eb41ed0  109     0% (       0)    0% (       0)
cbHigh                  1eb23c90  128     0% (       0)    0% (       0)
timerQueue              1ef019e0  129     0% (       0)    0% (       0)
scanOnce                1eb18c70  129     0% (       0)    0% (       0)
scan0.1                 1eaf2400  133     0% (       0)    0% (       0)
scan0.2                 1eaf7c10  134     0% (       0)    0% (       0)
cbMedium                1eb294a0  135     0% (       0)    0% (       0)
scan0.5                 1eafd420  135     0% (       0)    0% (       0)
scan1                   1eb02c30  136     0% (       0)    0% (       0)
scan2                   1eb08440  137     0% (       0)    0% (       0)
scan5                   1eb0dc50  138     0% (       0)    0% (       0)
scan10                  1eb13460  139     0% (       0)    0% (       0)
cbLow                   1eb3d3b0  140     0% (       0)    0% (       0)
dbCaLink                1eb1e480  149     0% (       0)    0% (       0)
CAS-TCP                 1eaecbf0  181     0% (       0)    0% (       0)
---------------------------------------------------------------------------**** CAS-UDP   task need for extension CA client----------------------------------------------------------------------------errlog                  1ee40aa0  189     0% (       0)    0% (       0)
errlog                  1eea5c10  189     0% (       0)    0% (       0)
errlog                  1ea1d2b0  189     0% (       0)    0% (       0)
taskwd                  1fffef50  189     0% (       0)    0% (       0)
KERNEL                                    2% (      35)    2% (      35)
INTERRUPT                                 0% (       0)    0% (       0)
IDLE                                      0% (       0)    0% (       0)
TOTAL                                    99% (    1587)   99% (    1587)

Thanks,

Kiman Ha,
PLS Control Group.
##################################


Hi all

I am having trouble connecting to our new PowerPc card using EPICS r3.14.3.

I have built EPICS base and some of the extensions.

I can boot the ioc with an epics database (the demo.db one fron the sequencer extension)
I can access the datebase when logged into the ioc from a console ie dbpf, dbgf and dbl commands all work
and I can access the various pv fields.

I cannot access the database from outside the ioc using caget or medm. caget returns an "Invalid channel name" when
accessing any of the PowerPC PV's although it is quite happy to access the other iocs running EPICS R3.13.1

I tried to telnet to port 5064 on the ioc but it reports connection refused. It looks like the ioc isn't listening on this port.
The only tcp ports it recognises are 23, 111 and 513
Any suggestions as to whats missing in the ioc?

regards

Dennis Armstrong











Navigate by Date:
Prev: Re: aps cvs access Andrew Johnson
Next: Re: Problems using Epics R3.14.3 with mvme5110 PowerPc Dennis Armstrong
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020 
Navigate by Thread:
Prev: Re: Problems using Epics R3.14.3 with mvme5110 PowerPc Dennis Armstrong
Next: Re: Problems using Epics R3.14.3 with mvme5110 PowerPc Dennis Armstrong
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·