Are both computers on the same subnet as the AIM? Do both have 1Gbit NICs, or is one 10Gbit?
Mark
Sent from my iPhone
> On Mar 14, 2024, at 10:31 PM, Hank Ball via Tech-talk <tech-talk 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
>
>
- Replies:
- Re: mcaAIM and nmcDemo not finding AIM 556 on new linux install Hank Ball via Tech-talk
- References:
- mcaAIM and nmcDemo not finding AIM 556 on new linux install Hank Ball via Tech-talk
- Navigate by Date:
- Prev:
mcaAIM and nmcDemo not finding AIM 556 on new linux install Hank Ball via Tech-talk
- Next:
Re: mcaAIM and nmcDemo not finding AIM 556 on new linux install Hank Ball 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:
mcaAIM and nmcDemo not finding AIM 556 on new linux install Hank Ball via Tech-talk
- Next:
Re: mcaAIM and nmcDemo not finding AIM 556 on new linux install Hank Ball 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>
|