Experimental Physics and Industrial Control System
|
Hi, I've been dealing with a bug for several days. I used my own st.cmd with modbusApp. The ioc shell did appear but the welcome words of EPICS like: Starting iocInit ############################################################################ ## EPICS R3.16.2-DEV ## EPICS Base built Dec 27 2018 ############################################################################ iocRun: All initialization complete
are missing. The EPICS server does not boot and i can't approach pvs by caget and caput. Now I find the reason. There was no newline after the `iocInit` command in my st.cmd. When I add a newline at the ending of st.cmd, It works. So, is this a bug? Why is a new line needed at the ending of `st.cmd`?
- Replies:
- Re: EPICS server won't boot when there is no newline at the ending of st.cmd Johnson, Andrew N. via Tech-talk
- Navigate by Date:
- Prev:
Re: EPICS Codeathon 2020 Gabriel Fedel via Tech-talk
- Next:
RE: Uploading a file with SFTP from an EPICS driver - Issue fixed! 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
2023
2024
2025
- Navigate by Thread:
- Prev:
RE: [EXTERNAL] ai records with data covering many decades [SEC=UNOFFICIAL] STARRITT, Andrew via Tech-talk
- Next:
Re: EPICS server won't boot when there is no newline at the ending of st.cmd Johnson, Andrew N. 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
2023
2024
2025
|
ANJ, 19 Nov 2019 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
·
Download
·
Search
·
IRMIS
·
Talk
·
Documents
·
Links
·
Licensing
·
|