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  <20212022  2023  2024  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  <20212022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: EPICS 7 base on WSL2
From: "Leblanc, Gregory via Tech-talk" <tech-talk at aps.anl.gov>
To: Freddie Akeroyd - STFC UKRI <freddie.akeroyd at stfc.ac.uk>
Cc: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Thu, 6 May 2021 15:44:32 +0000

Re-adding tech-talk to the CC list, since this might help someone else in the future.

 

Manually setting the EPICS_CAS_INTF_ADDR_LIST on both the softIoc and the caget seems to do the trick.  I do have a virtual wired network connection configured.   Running:

sudo firewall-cmd --zone=public --permanent --add-port=5064-5065/tcp

 

will do the trick, I think. I ended up using the cockpit web console, which seemed to be OK.

 

I’ll keep playing around, and see what else I can break.  Thanks for all the help,

     Greg

 

 

From: Freddie Akeroyd - STFC UKRI <freddie.akeroyd at stfc.ac.uk>
Sent: Wednesday, May 5, 2021 6:20 PM
To: Leblanc, Gregory <leblanc at ohio.edu>
Subject: RE: EPICS 7 base on WSL2

 

Hi Greg,

 

core.autocrlf should be “input” on linux and “auto” on windows. If wsl has picked up a .gitconfig from windows that sets this to “auto” then that is why you have CRLF endings on checkout.

 

I have two guesses to the caget issue. One is the firewall is blocking it, the other is did you assign any network adapters to your VM or does it just have loopback? I think EPICS does not automatically add loopback to the IOC address broadcast list – I have a feeling it does this to avoid duplicate replies to queries, so if you have not assigned any real network adapters to the VM then you may not see anything.

 

Try in one window:

 

env EPICS_CAS_INTF_ADDR_LIST=127.0.0.1 softIoc –d test.db

 

And then see if caget works as is in the other. If it doesn’t, then try:

 

env EPICS_CA_ADDR_LIST=127.0.0.1 caget temperature:water

 

Regards,

 

Freddie

 

From: Leblanc, Gregory <leblanc at ohio.edu>
Sent: 05 May 2021 22:44
To: Akeroyd, Freddie (STFC,RAL,ISIS) <freddie.akeroyd at stfc.ac.uk>
Subject: RE: EPICS 7 base on WSL2

 

Not sure what it means, but:

 

leblanc@DESKTOP-43GPJQ9:~$ which git

/usr/bin/git

leblanc@DESKTOP-43GPJQ9:~$ git config --get core.autocrlf

true

leblanc@DESKTOP-43GPJQ9:~$ git config --get core.eol

leblanc@DESKTOP-43GPJQ9:~$

 

 

caget issue screenshot at:

https://photos.app.goo.gl/85o2dhwLbdVZdErV9

 

     Greg

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Freddie Akeroyd - STFC UKRI via Tech-talk
Sent: Wednesday, May 5, 2021 5:16 PM
To: tech-talk at aps.anl.gov
Subject: RE: EPICS 7 base on WSL2

 

Hi,

 

if you type

 

    which git

 

in WSL is it picking up Ubuntu git correctly? Do

 

    git config --get core.autocrlf

    git config --get core.eol

 

show anything amiss?

 

Re: caget issue, yes you type the caget in a new linux terminal. Do you still have the softIoc running in another linux terminal and did you get the expected output from the dbl command in the softIoc window?

 

Regards,

 

Freddie

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Leblanc, Gregory via Tech-talk
Sent: 05 May 2021 21:30
To: tech-talk at aps.anl.gov
Subject: RE: EPICS 7 base on WSL2

 

There’s clearly something up with my git checkout. 

/EPICS/epics-base$ file README

README: ASCII text, with CRLF line terminators

 

I ran the checkout from within ubuntu by doing:

$ git clone --recursive https://github.com/epics-base/epics-base.git

 

Since there’s no CentOS package for WSL, for the short term, at least, I ditched WSL and installed CentOS-8-Stream in a VMware virtual machine.  That seems to have gotten me a couple of steps further, but I’m pretty sure I’m missing something pretty straightforward.

 

At https://docs.epics-controls.org/projects/how-tos/en/latest/getting-started/installation.html#test-epics

 

I see a segment that shows:

Open a new terminal (we call it nr. 2) and try the command line tools caget and caput. You will see something like

 

your prompt> caget temperature:water

 

Is that a new linux terminal?  If so, I get the following:

 

$ caget temperature:water

Channel connect timed out: 'temperature:water' not found.

 

However, the > implies that this is an epics prompt, but there is no caget in the list of commands for softIoc.  I’m sure it’s staring me in the face, but I can’t see it.

     Greg

 

From: Freddie Akeroyd - STFC UKRI <freddie.akeroyd at stfc.ac.uk>
Sent: Friday, April 30, 2021 8:30 PM
To: Leblanc, Gregory <leblanc at ohio.edu>; tech-talk at aps.anl.gov
Subject: RE: EPICS 7 base on WSL2

 

Hi Greg,

 

I tried it just now and it all built and ran OK with no changes. My dbd file also looks to be with the correct line endings

 

/mnt/c/devel/wsl-epics-base$ file dbd/softIoc.dbd

dbd/softIoc.dbd: ASCII text

 

So I think you are right that the issue is line endings. If you run file on the top epics base README what does it give? For me that is also:

 

/mnt/c/devel/wsl-epics-base$ file README

README: ASCII text

 

If yours mentions CRLF etc. did you do the checkout using git from WSL or with windows git? Is a git config file getting picked up from somewhere that sets the line endings incorrectly?

 

I think the dbd files get generated from a .pod file using perl. If the above README is the correct line endings, then I would assume the .pod files are too. Another possibility is then that the wrong perl program is being picked up – Windows strawberry perl would add CRLF. If you type    which perl    in WSL does it look right?

 

Regards,

 

Freddie  

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Leblanc, Gregory via Tech-talk
Sent: 30 April 2021 22:21
To: tech-talk at aps.anl.gov
Subject: EPICS 7 base on WSL2

 

Anybody tried running EPICS under WSL?  I was just playing around, trying to decide if heading down the EPICS path makes sense for our lab. 

 

I followed the docs at: https://docs.epics-controls.org/projects/how-tos/en/latest/getting-started/installation.html

I had to edit the EpicsHostArch script to change the line endings from CRLF to LF (or was it vice-versa?).  After that, the build went well.  I tried to run softIoc to do a test, and got the following:

 

$ softIoc

Error: Invalid character 'c'

at or before "c" in file "/home/leblanc/EPICS/epics-base/bin/linux-x86_64/../../dbd/softIoc.dbd" line 1

Error: Invalid character 'a'

Error: Invalid character 'l'

Error: Invalid character 'c'

Error: Invalid character 'o'

Error: Invalid character 'u'

Error: Invalid character 't'

Error: Invalid character 'D'

Error: Invalid character 'O'

Error: Invalid character 'P'

Error: Invalid character 'T'

Error: syntax error

Error: Failed to load DBD file: /home/leblanc/EPICS/epics-base/bin/linux-x86_64/../../dbd/softIoc.dbd

 

At which point   I decided that was enough for a Friday night.  I wonder if it might also be line endings, since file reports:

 

$ file EPICS/epics-base/dbd/softIoc.dbd

EPICS/epics-base/dbd/softIoc.dbd: ASCII text, with CRLF, LF line terminators

 

Am I out to lunch, or is it worth a try next week?

     Greg

 

--

Gregory Leblanc

Accelerator Engineer

Edwards Accelerator Lab - Ohio University

123 University Terrace

Athens, OH 45701

leblanc at ohio.edu

M: (401) 52-OUAL1 or (401) 526-8251

 

This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses. Opinions, conclusions or other information in this message and attachments that are not related directly to UKRI business are solely those of the author and do not represent the views of UKRI.


References:
EPICS 7 base on WSL2 Leblanc, Gregory via Tech-talk
RE: EPICS 7 base on WSL2 Freddie Akeroyd - STFC UKRI via Tech-talk
RE: EPICS 7 base on WSL2 Leblanc, Gregory via Tech-talk
RE: EPICS 7 base on WSL2 Freddie Akeroyd - STFC UKRI via Tech-talk

Navigate by Date:
Prev: Job Opportunity at APS/APS-U- Software Engineer Shen, Guobao via Tech-talk
Next: calcout record processing Randall Cayford 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  <20212022  2023  2024 
Navigate by Thread:
Prev: RE: EPICS 7 base on WSL2 Freddie Akeroyd - STFC UKRI via Tech-talk
Next: Re: EPICS 7 base on WSL2 Maren Purves 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  <20212022  2023  2024 
ANJ, 06 May 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·