Experimental Physics and
Industrial Control System

[email protected] (Bill Brown) · Thu, 22 Aug 96 07:41:48 PDT

> Date: Thu, 22 Aug 1996 13:46:24 +0200 (MET-DST)
> From: Matthias Clausen DESY -MKV2/KRYK- <[email protected]>
> To: [email protected]
> Subject: Re: epics driver & device support for IRM

> The idea of standardisation is always good - but this only works if the IP-modules can 
> really be identified by their ID. This rule is already broken by the IP modules designed 
> for the IRM. You have to manually specify the type which in our case is done through 
> environment variables in the startup command file.

Hmmm - it sort of looked like all the necessary stuff was there.  I exchanged
email with the people at fnal and learned the following:

 > If you look at the IP PROM contents using '162bug, you see the "IPAC"
 > followed by mfg ID  (Fermilab's assigned Manufacturer ID is "$BB"), Model#,
 > Rev#, three bytes of zero, the # of Bytes used ($14), and the CRC.   In the
 > Module Specific space is "IRMIPDG6" for The digital IP.
 [  ...  ]
 > The Analog Interface IP is similar with the Module Space containing
 > "IRMIPAN1".

It all seems to be as advertised.  On the other hand, you've actually done the
work, so I'm probably overlooking something.  It's looks like vxWorks doesn't
properly map the addresses of the IP ports, but I think that's a different
problem.

> 
> Maybe we'll find some time during the next EPICS meeting to start the
> discussion over coffee!?

Sounds good to me!  I've grabbed the notes by Andrew Johnson <[email protected].
ac.uk> that he mentioned in his response yesterday.  At first glance it
looks like a very good start, but I haven't looked at any part of 3.13
yet, and since I'm not sure where we are it's hard for me to tell where
I'm going, so to speak.

-bill

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System