Experimental Physics and
| |||||||||||||||||
|
yes, I will send you all I have in a separate mail. Jens > Hi Jens, Do you have a model 3 driver for the OMS MAXv that we can > try out at SLAC? > > Thanks Mark! > > Nia > ________________________________________ > From: Mark Rivers [[email protected]] > Sent: Tuesday, May 08, 2012 12:42 PM > To: Fong, Nia W.; '[email protected]'; [email protected] > Subject: RE: Motor model 3 support for OMS MAXv-8000? > > Hi Nia, > > The current EPICS driver version is model 1, not model 2. > > Jens Eden told me in Nov. 2010 that he had a model 3 driver for the > MAX family working. > > This is from his message: > > ######################################### > Yes, I have a (beta) asyn driver version for the MAX family (MAXv > and MAXnet so far), > which I recently sent to Austen and Ron. I didn't announce it on > tech-talk, since I didn't > had a chance to do some testing yet, but if anyone is interested, > tell me and I will send you > what I have. > > Using Mark Rivers ' asynMotorDriver base C++ class is very straight > forward and has > several advantages. > - os-independent (we use it with RTEMS) > - easy to have derived classes for the other MAX-family members > (they all use the same command set) > (writing a MAXp Linux driver using Michael's devLib2 is on my list) > - the asynOctet layer which Dirk requested comes for free > (use a stringout or waveform to send ASCII commands to the Controller) > > With this driver version you may use the auxiliary encoders or use > encoders independent from their > motor axis (which is actually the reason why I wrote this, because > we want to use 2 encoders for > a single axis). > If this functionality is too specific, I could possibly remove it > and put it into a ptb-specific derived class. > I didn't care for OMS58 yet. > ######################################### > > If Jens is willing I could take this driver and add the new > coordinated motion API to it, and put into the standard EPICS motor > distribution. Tim Mooney has already done EPICS support for coordinated > motion, but it is an SNL program (like the old XPS trajectory > scanning), not using the Model 3 API. So I would just port his code > to the model 3 driver. > > I was actually talking to Pro-Dex about this today, because they > have developed a product that is a 10-axis MAXNet controller that > plugs into the left-hand slot of an ACS Step-Pak. This allows > Step-Pak systems to be VME-independent, and with a new driver they > could also do coordinated motion. With the new Step-Paks they can > also drive servo motors. > > Mark > > > > -----Original Message----- > From: [email protected] [mailto:[email protected] > ] On Behalf Of Fong, Nia W. > Sent: Tuesday, May 08, 2012 1:29 PM > To: [email protected] > Subject: Motor model 3 support for OMS MAXv-8000? > > Hi, > > Has anyone written a model 3 based motor driver for the OMS MAXv > VME-based board? > We just ordered a MAXv-8000 Motion Controller VME board. > > Is the current driver in the motor-R6-7 model 2? > > Thanks in advance, > > Nia
| ||||||||||||||||
ANJ, 18 Nov 2013 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |