Re: 2 MAXv problems

[Jens.Eden@ptb.de]

Hello Ron,

> but the motor record has not issued negative
> encoder ratio commands for a long time.
here is an extract of the boot messages with 
drvMAXvdebug=10, while autosave writes 
-5.55123456e-06 to the ERES-field.

--
send_mess: sent card 0 message:'
AX  ER-180140,52359 UU-3.440496
--
This command (ER-180140,52359) does not work for
current firmware versions.

> Are you using a really old
> version of the motor record?
No, this is the 
motorR6-4-4
EpicsRelease 3.14.11

Jens
_______________________________
Jens Eden
Physikalisch-Technische Bundesanstalt
Albert-Einstein-Straße 15
12489 Berlin

Tel +49 30 6392-5086
Fax +49 30 6392-5082




Von:
Ron Sluiter <sluiter@aps.anl.gov>
An:
Jens.Eden@ptb.de
Kopie:
tech-talk@aps.anl.gov
Datum:
05.03.2010 21:12
Betreff:
Re: 2 MAXv problems



Hello Jens

There has been a recent (R6-4 and above) fix to prevent intermittent 
MAXv command
errors from occurring when User Units are turned off, but the motor 
record has not
issued negative encoder ratio commands for a long time.  Are you using a 
really old
version of the motor record?

Ron


Jens.Eden@ptb.de wrote:
> Hi all,
>
> I found, that in recent firmware versions (1.31) of the MAXv cards the 
> command to set
> negative encoder resolutions (e.g. "AX ER-2,3") as used by the MAXv 
driver 
> does not work any more.
> Instead a command error is returned and the encoder resolution will 
remain 
> unchanged.
> I couldn't find this "new feature" documented anywhere.
>