Re: CAN questions

[Bernd Schoeneburg <Bernd.Schoeneburg@desy.de>]

At DESY we use commercial I/O modules with CanOpen communication connected
to a TIP810 CAN-IP. Our EPICS driver/device support can work with CanOpen
and Can (Layer2) devices as well. The driver works with the Ipac-Api. It
supports only basic functions of CanOpen but for simple I/O it's ok.
We had some bad experience with a analogue input module running in i/o-event
mode. But this wasn't a CAN-problem. The bus is very secure. A disadvantage
is that because of bitwise arbitration the speed must be reduced drastically
if the length of the bus becomes longer.

Bernd

John Maclean wrote:

> At the APS we are considering adopting CAN for one of our applications
> requiring some remote I/O.
>
> This particular project needs ~32 binary I/O channels and ~6 low res. (8
> to 12 bit) analog inputs per node.
>
> Is any one already using a similar off-the-shelf solution, or do people
> generally build their own custom CAN board? Is anyone interfacing
> CANopen or DEVICEnet products to EPICS?
>
> Someone, (management), also asked me if I knew of anyone who's had a bad
> experience with CAN. I didn't, but as a matter of interest I'd be
> interested to hear of any experiences with CAN, either bad or good.
>
> Thanks,
>
> John.