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  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  <20232024  2025  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  <20232024  2025 
<== Date ==> <== Thread ==>

Subject: Re: procServ comminication with phoebus problem
From: "Hu, Yong via Tech-talk" <tech-talk at aps.anl.gov>
To: wang Ewen <ewenwang2021 at gmail.com>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Fri, 2 Jun 2023 13:15:26 +0000

Hello Ewen,

You are messing up two different things: procServ’s telnet port and Channel Access (CA) port. They are independent, not related to each other at all.

Since you are using ‘org.phoebus.pv.ca/auto_addr_list=false’, you probably should use “org.phoebus.pv.ca/addr_list=your-network-broadcast-ip”. Of course, you need to find “your-network-broadcast-ip” by yourself ( it is probably 192.168.238.255). You may need to restart your Phoebus after you re-configure the network settings.

Yong

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of wang Ewen via Tech-talk <tech-talk at aps.anl.gov>
Date: Thursday, June 1, 2023 at 12:04 PM
To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: procServ comminication with phoebus problem

Hi,

   I have a problem when I use procServ .It can works:
[root@localhost iocmyexample]# procServ -n "my-ioc" -L my-ioc.log -P 8888 -i "^D^C" /usr/local/EPICS/iocs/iocBoot/iocmyexample/st.cmd

procServ: spawning daemon process: 18044

[root@localhost iocmyexample]# ps aux | grep procServ

root      18044  0.0  0.0  16928  1268 ?        Ss   22:47   0:00 procServ -n my-ioc -L my-ioc.log -P 8888 -i ^D^C /usr/local/EPICS/iocs/iocBoot/iocmyexample/st.cmd

root      18093  0.0  0.0 112816   972 pts/1    R+   22:47   0:00 grep --color=auto procServ

[root@localhost iocmyexample]# caget ewen:aiExample1

ewen:aiExample1                6

[root@localhost iocmyexample]# caget ewen:aiExample1

ewen:aiExample1                0

[root@localhost iocmyexample]# caget ewen:aiExample1

ewen:aiExample1                4

[root@localhost iocmyexample]#

My phoebus setting.ini is::

org.phoebus.pv.ca/addr_list=192.168.238.134:8888

org.phoebus.pv.ca/auto_addr_list=false

It cannot read the value ewen:aiExample1, but when I close the procServ  and change the addr_list to org.phoebus.pv.ca/addr_list=192.168.238.134:5064 ,it works well.

Here the log:

@@@ Restarting child "my-ioc"

@@@    (as /usr/local/EPICS/iocs/iocBoot/iocmyexample/st.cmd)

@@@ The PID of new child "my-ioc" is: 18051

@@@ @@@ @@@ @@@ @@@

#!../../bin/linux-x86_64/myexample

< envPaths

epicsEnvSet("IOC","iocmyexample")

epicsEnvSet("TOP","/usr/local/EPICS/iocs")

epicsEnvSet("EPICS_BASE","/usr/local/EPICS/base")

cd "/usr/local/EPICS/iocs"

## Register all support components

dbLoadDatabase "dbd/myexample.dbd"

myexample_registerRecordDeviceDriver pdbbase

## Load record instances

dbLoadTemplate "db/user.substitutions"

dbLoadRecords "db/myexampleVersion.db", "user=ewen"

dbLoadRecords "db/dbSubExample.db", "user=ewen"

#var mySubDebug 1

#traceIocInit

cd "/usr/local/EPICS/iocs/iocBoot/iocmyexample"

iocInit

Starting iocInit

############################################################################

## EPICS R7.0.3.1

## EPICS Base built Dec 16 2022

############################################################################

iocRun: All initialization complete

## Start any sequence programs

#seq sncExample, "user=ewen"

[?1034hepics>

 

Please help me how can I do .

 

Best Regards,

 

Ewen

 

 

 

 

Windows 邮件发送

 


References:
procServ comminication with phoebus problem wang Ewen via Tech-talk

Navigate by Date:
Prev: Re: [EXTERNAL] procServ comminication with phoebus problem Mark Rivers via Tech-talk
Next: Re: [EXTERNAL] procServ comminication with phoebus problem Mark Rivers via Tech-talk
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  <20232024  2025 
Navigate by Thread:
Prev: Re: [EXTERNAL] procServ comminication with phoebus problem Mark Rivers via Tech-talk
Next: Keysight oscilloscope DSOX1204a connection issue MuYuan Wang via Tech-talk
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  <20232024  2025 
ANJ, 02 Jun 2023 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions ·
· Download · Search · IRMIS · Talk · Documents · Links · Licensing ·