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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: EPICS and large CAN systems |
From: | Rod Nussbaumer <[email protected]> |
To: | Elliott Wolin <[email protected]> |
Cc: | [email protected] |
Date: | Wed, 16 Mar 2011 07:19:29 -0700 |
Elliot:We use CANbus extensively to control beam optics power supplies. These are controlled mostly from VME CPUs using the Tews vxWorks and more recently Tews Linux driver, with EPICS device support from Andrew Johnson's package. Most recently we have deployed CANbus from low-cost ARM CPUs running EPICS on Linux and using the open-source CANbus driver. Andrew's device support package was locally re-worked to use the open-source Linux driver (lincan). We have numerous CANbus branches with 100 or more satellite nodes (all custom built at TRIUMF). These have been used successfully for over ten years. I would be interested in having a CANbus port driver for asyn, so our custom controller nodes could be used in some more novel ways, such as exploiting their RS-232 interfaces.
TRIUMF's use of CANbus has been reported in at least one ICALEPCS. Rod Nussbaumer ISAC Controls, TRIUMF Vancouver, Canada. Elliott Wolin wrote:
To all EPICS CAN experts, We are about to construct a 3000 channel CAN system. Please contact me if you have any experience controlling CAN buses from EPICS. Our current thought is to use about 8 Anagate Ethernet-to-CAN controllers, four channels per controller, to talk to the CAN devices, about 100 devices per CAN bus. We'd use the ASYN framework to implement the driver that talks to the Anagate devices (they communicate via TCP/IP). I am open to suggestions and alternative solutions. I am especially interested in existing drivers for any type of Ethernet-based CAN controller so that we can avoid writing a new driver. Also, is the ASYN framework the best choice if we have to develop a new driver? Finally, to Marty Kraimer et al: is the Java IOC and port driver framework ready? Might we use this instead? Thanks,