Experimental Physics and
Industrial Control System

I know the resolution is available to the Newport XPS driver, because it uses it for profile moves.

I forget how I did that, and don’t have good search tools available from my phone. I seem to recall functions at some layer that send that motor record information to the drivers. Search for motorResolution in MotorSrc and NewportSrc.

Mark


Sent from my iPhone

> On Feb 7, 2020, at 10:33 AM, Koennecke Mark (PSI) via Tech-talk <tech-talk at aps.anl.gov> wrote:
>
> Hi,
>
> I am writing a motor driver for an old piece of french equipment called EuroMove.
> This is going well. But the thing does not implement homing in the controller. I try
> to implement this in the asynAxis driver. To that purpose, I need the motor resolution.
> It is in principle there, in the MRES field of the motor record.  I tried:
>
> pC_->getDoubleParm(axisNo_, pC_->motorResolution_, &resolution);
>
> but this gave me a 0 instead of the .01 to which the MRES field had been configured in the
> motor substitutions file. I know the record sees this because the conversion for physical
> units to motor steps is working.
>
> I also tried motorEncoderRatio_ which returned infinity.
>
> My question now is how I can get at that information in an asynMotorAxis driver?
>
> Or is my only option to write a configuration command or axis creation command which
> passes the resolution value in?
>
> This is against base3.14.12 and motor6.9 on RHEL7 linux.
>
> Best Regards,
>
>     Mark Koennecke
>
>
>
>