I meant to say that your st.cmd contains these 2 lines:
epicsEnvSet "P" "$(P=testIPServer)"
dbLoadRecords "db/testIPServer.db", "P=$(P)"
The first line is the one with the error. My original reply had the wrong second line.
Mark
________________________________
From: Mark Rivers
Sent: Monday, July 06, 2015 5:22 PM
To: yann stephen; [email protected]
Subject: RE: EPICS TCP server
Hi Stephen,
The "cas warning" messages are normal.
It should not create an ipSNCServer executable. That is an SNL program which is part of your IOC application. That is working OK since you did not get an error from this command:
seq("ipSNCServer", "P=testIPServer:, PORT=P5002")
These errors:
> sevr=minor ipSNCServer[0](after 5 sec): assigned=3, connected=0, monitored=0, got monitor=0
are happening because your records don't have the same prefix as the SNL program is expecting. Your st.cmd file has these 2 lines:
epicsEnvSet "P" "$(P=testIPServer)"
dbLoadDatabase "dbd/myexample.dbd"
That does not look correct to me. I think the first line should be:
epicsEnvSet "P" "testIPServer:"
You can use the iocsh "dbl" command to see the names of the records that are loaded. This is what I get from the asyn/asynTestIPServerApp IOC:
epics> dbl
testIPServer:connected
testIPServer:stringInput
testIPServer:stringOutput
Mark
________________________________
From: [email protected] [[email protected]] on behalf of yann stephen [[email protected]]
Sent: Monday, July 06, 2015 1:27 PM
To: [email protected]
Subject: EPICS TCP server
Good day!
i am experimenting with epics tcp socket capabilities using asyn driver. having done some reading , install the asyn package and the epics sequencer as well. under the asyn directory there is an testIPServer directory with a read me file that tell to setup the SNCSEQ in the realese variable to use the sequencer capabilities. this folder provide a ipSNCServer.st and ipEchoServer.c files that i am trying to incorporate to my application to have a server listening at a specific port.
now, i build my application and under top/xxxApp/src i modified the Makefile as the one attached to this email.
i also modified the release file under configure to include the different variable path.
i modified my st.cmd file as well to include the ip port configuration as attached as well.
my problem is this, when a run make under this directory, xxxApp/src it create two file, the application executable and the sncExample executable but never an ipSNCServer executable. when i run the st.cmd i get this output.
cas warning: Configured TCP port was unavailable.
cas warning: Using dynamically assigned TCP port 53146,
cas warning: but now two or more servers share the same UDP port.
cas warning: Depending on your IP kernel this server may not be
cas warning: reachable with UDP unicast (a host's IP in EPICS_CA_ADDR_LIST)
iocRun: All initialization complete
## Start any sequence programs
#seq sncExample, "user=myHost"
#ipEchoServer("P5001")
seq("ipSNCServer", "P=testIPServer:, PORT=P5002")
Sequencer release 2.1.13, compiled Wed Apr 1 07:55:20 2015
Spawning sequencer program "ipSNCServer", thread 0x9f89330: "ipSNCServer"
epics> sevr=minor ipSNCServer[0](after 2 sec): assigned=3, connected=0, monitored=0, got monitor=0
sevr=minor ipSNCServer[0](after 5 sec): assigned=3, connected=0, monitored=0, got monitor=0
sevr=minor ipSNCServer[0](after 10 sec): assigned=3, connected=0, monitored=0, got monitor=0
sevr=minor ipSNCServer[0](after 18 sec): assigned=3, connected=0, monitored=0, got monitor=0
sevr=minor ipSNCServer[0](after 31 sec): assigned=3, connected=0, monitored=0, got monitor=0
the readme file provide this output,
iocInit: All initialization complete
ipEchoServer("P5001")
seq("ipSNCServer", "P=testIPServer:, PORT=P5002")
SEQ Version 2.0.10: Thu Jan 5 13:14:09 2006
Spawning state program "ipSNCServer", thread 0x809e720: "ipSNCServer"
epics>
i am running epics 3.14 on ubuntu 12.04
Thank for any assistance.
Yann
- Replies:
- Re: EPICS TCP server Andrew Johnson
- References:
- EPICS TCP server yann stephen
- RE: EPICS TCP server Mark Rivers
- Navigate by Date:
- Prev:
RE: EPICS TCP server Mark Rivers
- Next:
Re: EPICS TCP server Andrew Johnson
- 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: EPICS TCP server Mark Rivers
- Next:
Re: EPICS TCP server Andrew Johnson
- 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
|