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

Subject: Re: mcaAIM and nmcDemo not finding AIM 556 on new linux install
From: Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>
To: Mark Rivers <rivers at cars.uchicago.edu>, Érico Nogueira Rolim <erico.rolim at lnls.br>
Cc: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>, Hank Ball <hank at wv7u.com>
Date: Fri, 15 Mar 2024 18:15:32 +0000
Are you running the IOC with root privileges on both machines? That is required for pcap to work.

Mark

Sent from my iPhone

On Mar 15, 2024, at 1:08 PM, Mark Rivers <rivers at cars.uchicago.edu> wrote:

 You can also run Wireshark. The IOC sends out broadcast messages periodically searching for AIM modules, and they send a reply, which the IOC uses to build a list of available devices. That does not seem to be working, and Wireshark will tell what is happening.

Mark

Sent from my iPhone

On Mar 15, 2024, at 12:31 PM, Érico Nogueira Rolim via Tech-talk <tech-talk at aps.anl.gov> wrote:

 On 15/03/2024 12:42, Hank Ball via Tech-talk wrote:

Hi Andrew,

I don't have any iptables or firewall rules on any of these computers. I can reach other computers, webistes, etc, just fine over the network.

I can control an Amptek DP5 mcaAmptekApp over the network on the Debian 12 computer. I can also run an IOC/mca on the Debian 9 computer which connects to the AIM 556, and retrieve the data from that via medm, caget, etc, running on the Debian 12 computer.

So it seems the ethernet interface is working, but I may have done something wrong when building one of the EPICS components, or I'm missing a library or something. But I'm not sure where to look since all the EPICS modules built without errors.


Can you run the IOC under strace on Debian 12 and on Debian 9? Something like "strace -fe %net ./st.cmd" should do the trick. Simply comparing the calls that are supposed to connect to the device ought to be enough. If the system calls are different, you can look at what changed; if they are the same, the issue is probably the computer's network setup.


Cheers,

Érico


Thanks

Hank

On 3/15/24 08:55, Johnson, Andrew N. wrote:

Hi Hank,

 

I'm not a Debian or mcaAIM user, but I'm just checking the obvious: Have you found out whether Debian 12 sets up a firewall by default, and if so configured that to allow communication over whatever network ports you need for these devices? It looks like you might not be getting any response over the network at all, and a firewall is the first thing I would look at in that case.

 

- Andrew

 

 

On 3/14/24, 10:31 PM, "Tech-talk" <tech-talk-bounces at aps.anl.gov> wrote:

 

I've been working on building EPICS on a Debian 12 system with the
latest releases of mca (7-10) and base (7.0.8).

I'm hoping someone can help me please with mca ethernet connection
problem I'm having.

When I try to connect to a Canberra AIM 556 with nmcDemo I get this
response:

root@debian:/home/hank/epics# nmcDemo enp2s0 0x205
Using AIM-Module 205
Calling nmc_initialize ...
(nmc_initialize): waiting returned 1
Calling nmc_build_enet_addr ...
Calling nmc_findmod_by_addr ...

I get a similar result when using mcaAIM:

......
AIMConfig("AIM1/1", 0x205, 2, 512, 1, 1, "enp2s0")
(nmc_initialize): waiting returned 1
AIMConfig ERROR: cannot find module on the network!
.......

It may be helpful to add that mcaAmptekApp does work correctly and
communicates fine with an Amptek DP5.

As evidence that the AIM 556 is working, I have an older system running
Debian 9 and built with base-3.14.12.4 and mcaR7-6 that has no problems
with either nmcDemo or mcaAIM.  (This computer has a different ethernet
interface name, enp3s0 vs enp2s0.)

root@lab1:/home/hank/epics# nmcDemo enp3s0 0x205
Using AIM-Module 205
Calling nmc_initialize ...
Calling nmc_build_enet_addr ...
Calling nmc_findmod_by_addr ...
Calling nmc_buymodule ...
Calling nmc_show_modules ...
Module     Type  HW rev.  FW rev.  Owner name      Owner ID Status     
Memory size Free address
NI00801c    1       2        7                 00:00:00:00:00:00
Reachable     262140      00000000
NI000205    1       0        6       lab1      90:2B:34:13:12:C0
Reachable     261116      00000000
Calling nmc_addeventsem ...
Calling nmc_acqu_setup ...
Calling nmc_acqu_setstate(0) ...
Calling nmc_acqu_erase ...
Calling nmc_acqu_setelapsed ...
Calling nmc_setstate(1) ...
Waiting for event flag or timeout.  Should complete in 10 seconds.
Calling nmc_statusupdate ...
Calling nmc_acqu_getmemory_cmp ...
Time for nmc_acqu_getmemory_cmp = 0.071970
Calling nmc_acqu_getmemory ...
Time for nmc_acqu_getmemory = 0.191984
Total counts were 0; Real time = 10.00, Live time=9.99
Calling nmc_freemodule ...
Calling nmc_show_modules ...
Module     Type  HW rev.  FW rev.  Owner name      Owner ID Status     
Memory size Free address
NI00801c    1       2        7                 00:00:00:00:00:00
Reachable     262140      00000000
NI000205    1       0        6                 00:00:00:00:00:00
Reachable     261116      00000000

Thanks for any suggestions,

Hank



Aviso Legal: Esta mensagem e seus anexos podem conter informações confidenciais e/ou de uso restrito. Observe atentamente seu conteúdo e considere eventual consulta ao remetente antes de copiá-la, divulgá-la ou distribuí-la. Se você recebeu esta mensagem por engano, por favor avise o remetente e apague-a imediatamente.

Disclaimer: This email and its attachments may contain confidential and/or privileged information. Observe its content carefully and consider possible querying to the sender before copying, disclosing or distributing it. If you have received this email by mistake, please notify the sender and delete it immediately.


References:
mcaAIM and nmcDemo not finding AIM 556 on new linux install Hank Ball via Tech-talk
Re: mcaAIM and nmcDemo not finding AIM 556 on new linux install Johnson, Andrew N. via Tech-talk
Re: mcaAIM and nmcDemo not finding AIM 556 on new linux install Hank Ball via Tech-talk
Re: mcaAIM and nmcDemo not finding AIM 556 on new linux install Érico Nogueira Rolim via Tech-talk
Re: mcaAIM and nmcDemo not finding AIM 556 on new linux install Mark Rivers via Tech-talk

Navigate by Date:
Prev: Re: IOC databank Tran, Phi Dung via Tech-talk
Next: [no subject] saleem khan 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
Navigate by Thread:
Prev: Re: mcaAIM and nmcDemo not finding AIM 556 on new linux install Mark Rivers via Tech-talk
Next: RE: mcaAIM and nmcDemo not finding AIM 556 on new linux install 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
ANJ, 20 Mar 2024 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·