|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||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|
|<== Date ==>||<== Thread ==>|
|Subject:||Device Support for Nemic Lambda Power Supplies|
|From:||Anthony Andrews <firstname.lastname@example.org>|
|Date:||Mon, 23 May 2011 21:57:38 -0600|
My name is Tony and I’m a student at Idaho State University. I’ve been doing a senior project to help establish an EPICS control system for the Idaho Accelerator Center. I have been trying to create a control system specifically for a Nemic-Lambda ZUP (20 V 10A) magnet power supply.
So far, I have hooked the power supply into one of the ports of a MOXA 6650-8 terminal server using a RS485 (4wire) cable. Then I sent commands to the port with telnet 18.104.22.168 4002 to change the current, display the model name, and so forth. One example of a command that I use is:
which serves as both an initialization command and displays the make and model of the power supply which has address 01. Now, the next step is to figure out a way to turn those commands into process variables that I can monitor or change with MEDM.
So, I found a paper called “How to create EPICS device support for a simple serial or GPIB device” written by W. Eric Norum. Since the power supply is a kind of serial device I figured that it would be pretty close to what I need to do. However, I’m a little confused as to what to do in my situation on one part.
In the paper there’s a section called “Create a new device support module”, which shows how to create an EPICS application using the makeSupport.pl script. In the paper, after he creates a directory, he runs the command:
/home/EPICS/modules/soft/asyn/bin/linux-x86/makeSupport.pl –t devGpib AB300
So, my question is: since I’m not using a GPIB device can I still use this kind of command? Would I have to change the devGpib part of the above command to something else? I was thinking that since there is a file named devGpib.dbd that maybe that has something to do with the command above.
Hypothetically, if I were to replace the devGpib in the above command with another .dbd file called drvAsynIPPort would that create an EPICS application for telnet type devices? Then can I still just follow this paper for the rest of it? Or, if you think that this wouldn’t work, could you give me any other papers, sources, or example files to look through which would help me to create device support? Thank you.