Matthias writes...
> If you use IP modules which directly handle analog and digutal signals like those used for
> the IRM you probably are better off using the direct access to the memory of the IP than
> using an indirect way through an intermediate system. This implies that a general solution
> has to take into account that there are different flavours of boards - some you directly
> access and some ( like serial communication boards) that are better handeled by a
> dedicated CPU to take care of all te asynchronous interrupts. In the latter field you are
> using packages like HIDEOS or CDI.
> An additional thought should be spent on the usage of drivers you provide for one ore the
> other package. You probably want to be able to run the same driver - and save development
> efford - regardless whether you run it on a dedicated CPU ( through HIDEOS or CDI) or on
> the same CPU. (which to the best of my knowledge is only possible with CDI)
> This design feature of CDI did help us a lot when we ported our CAN driver with the CAN IP
> to the PC hardware with the IP on a ISA /IP carrier board.
>
> We should get some more input on this from other users of IP modules.
Our plan is to host IP's that require lots of processing, interrupts,
etc. on a 162 running HIDEOS, and host less processor-hungry IP's on a
162 that runs both EPICS and HIDEOS. We will still be going through
HIDEOS to talk to the local IP's, which is perhaps less efficient than
dedicated support for these local modules could be, but we won't have
to support two IP-interface mechanisms, and we'll be able to move an IP
from one board to the other by changing one number in the ioc-startup
file.
We haven't run IP's on the EPICS processor yet.
Tim Mooney
- Navigate by Date:
- Prev:
R3.13 App Devl Guide Janet B. Anderson
- Next:
Re: rec/devSup advise needed Marty Kraimer
- 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: epics driver & device support for IP modules Jim B. Kowalkowski
- Next:
R3.13 App Devl Guide Janet B. Anderson
- 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
|