Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017 
<== Date ==> <== Thread ==>

Subject: Re: CA problem w EPICS 3.14.11 & VxWorks 6.7
From: Kazuro FURUKAWA <kazuro.furukawa@kek.jp>
To: "GOURNAY Jean-Francois" <jean-francois.gournay@cea.fr>
Cc: tech-talk@aps.anl.gov
Date: Wed, 25 Nov 2009 21:13:08 +0900
Hello Jean-Francois, 

>>> On Wed, 25 Nov 2009 11:28:00 ,  "GOURNAY Jean-Francois" <jean-francois.gournay@cea.fr> wrote;
> Hello Jeff, hello Kazuro
> 
> Thanks for your replies.
> 
> Jeff,
> 
> I have included the trace of the 2 following commands  :
> 
> Dbcar "VMETST-CA-O", "2"
> 
> Casr "1"
> 
> Before these commands, I did a dbtr "VMETST-CA-O", surprisingly UDF 
> becomes 0 but the value (supposed to be retrieved through a CA link to 
> VMETST) is 0 (it should be "223").
> 
> Both VxWorks IOCs are on the same network (132.166.33.10 and 
> 132.166.33.11)

I'm not sure whether I explained the situation well or not.  If 
you build EPICS without BSD=44, the default EPICS_CA_ADDR_LIST 
(or the address list on memory) will not include your broadcast 
address, and your IOCs will never communicate each other unless 
you specify your broadcast address or host addresses explicitly 
into EPICS_CA_ADDR_LIST. 

> Kazuro,
> 
> I will pass the information to my colleague in charge of the VxWorks 
> support. He had already a lot of trouble with the IP stack of the new 
> release of VxWorks (2nd Ethernet port of our MVME5500 not working, 
> problem of connection with rlogin, problem with connect function of 
> socket.h). Recompiling with gnu instead of diab helps for some point 
> (wancomEnd.c) but there are still pending problems.

Our colleagues Tomohiro Okazaki and Takuya Nakamura tested the 
2nd Ethernet.  Their memo says followings;

1. Apply patches Diab5700_WIND00166270.zip and 
 WIND00165238-wancom.zip.
2. #define INCLUDE_WANCOM_END in config.h
3. build bootrom, driver, and kernel
 make clean bootrom.bin
 make CPU=PPC32 TOOL=diab
 vxprj build
4. configure the interface 
 ipAttach 0,"wancom"
 ifconfig "wancom0 inet 192.168.1.3 netmask 255.255.255.0 up"

We don't use vxWorks-6.7 yet for production systems, but only 
5.3 and 5.5.  

> J.F. Gournay
> 
> CEA Saclay
> 
> IRFU/SIS

We'll purchase VME CPU soon.  Are there anyone using MVME4100?  
Are there good reasons to switch from MVME5500 to MVME4100? 

Cheers, Kazuro. 

-----
Kazuro FURUKAWA <kazuro.furukawa@kek.jp>
 Linac&KEKB,  High Energy Accelerator Research Organization (KEK), Japan
 Telephone: +81-29-864-5200 x4316,  Facsimile: +81-29-864-0321


References:
RE: CA problem w EPICS 3.14.11 & VxWorks 6.7 GOURNAY Jean-Francois

Navigate by Date:
Prev: RE: CA problem w EPICS 3.14.11 & VxWorks 6.7 GOURNAY Jean-Francois
Next: Addition of command primitives to Asyn motor matthew.pearson
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017 
Navigate by Thread:
Prev: RE: CA problem w EPICS 3.14.11 & VxWorks 6.7 GOURNAY Jean-Francois
Next: RE: CA problem w EPICS 3.14.11 & VxWorks 6.7 Jeff Hill
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017 
ANJ, 31 Jan 2014 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·