Closed chrschroeder closed 4 years ago
It looks ok to me. Are there databases and user-interface screens that are associated with these new parameters?
We use customized templates and our own edl (edm) files for motor applications. The records following the style of the db files in the motor support would look like this:
record(bo, "$(P)$(M)cmdCal") {
field(DESC,"cmd calibration")
field(DTYP,"asynInt32")
field(OUT, "@asyn($(PORT),$(ADDR),$(TIMEOUT))CAL")
}
record(longout, "$(P)$(M)setMclFreq") {
field(DESC,"MCL Frequency")
field(DTYP,"asynInt32")
field(OUT, "@asyn($(PORT),$(ADDR),$(TIMEOUT))MCLF")
field(VAL, "5000")
field(HOPR,"20000")
field(LOPR,"50")
field(EGU, "Hz")
field(PINI,"YES")
}
Hello,
my user needs additional parameters / commands for the MCS2 controller (MCLF and CALx), which are not supported by the motor record. Unfortunately you removed the methods necessary for extension from Mark River's ACR driver, which your work is based on. I basically readded the writeInt32 method from the ACR driver together with the parameters I need. Please have a look.
Thanks, Christoph