Re: Prodex MAXv command responses (RA, QA, EA, RL) for different versions of firmware

[Ron Sluiter <sluiter@aps.anl.gov>]

Hello Austen,

Thanks for clarify this.  Dirk Zimoch (PSI) discovered this "bug" and sent
me a fix late last year.  I assumed at the time that it was a "bug", but 
based
on your communication with OMS, the problem was due to a change in
the communication protocol.

Dirk Zimoch's fix for this problem is in R6-4-2 and above of the motor
record distribution.

Since there is an initialization problems with MAXv ver:1.29 firmware and
a problem with ver:1.30 firmware reading DPRAM encoder position data
when using mixed motor types (i.e., PSE and PSO), I recommend (and the
latest version of the EPICS driver fully supports) MAXv firmware ver:1.31
and later.

Best regards,
Ron


Rose, AJ (Austen) wrote:
> All,
>
> Please note that the content of the attached e-mail.
>
> The effect of this (for firmware versions V1.30, and later) is that the
> HOME flag is 'lost' when in PSE or PSM mode when the QA and EA commands
> are executed as a pair (as done in the ALL_INFO message) in drvMAXv.cc,
> lines 101, 304. And the problem code is at lines 643...645, where the
> HOME flag gets over-written with a ','.
>
> Regards,
>
> Austen Rose
> Senior Software Engineer
> +44 (0)1235 77(8495)
>  
> Diamond Light Source Ltd
>
> Diamond House
>
> Harwell Science and Innovation Campus
>
> Didcot
>
> Oxfordshire OX11 0DE
>
> United Kingdom
>
>
> From: Reto RT. Toengi [mailto:Reto.Toengi@pro-dex.com] 
> Sent: 01 July 2009 02:07
> To: Rose, AJ (Austen)
> Cc: Pro-Dex Beaverton Support Group
> Subject: FW: re[2]: Home input on MAXv cards
>
>
> Austen,
>
> The investigation revealed that all our command responses terminate with
> a <LF> (0x0A). There is no tailing NULL.
>
>  
>
> In FW 1.29 and older a bug added a NULL after the <LF> for the commands
> RA, QA, EA and RL.
>
> In FW 1.30 and newer this NULL was removed for RA, QA and EA.
> Unfortunately the RL command has still that problem. We intend to fix
> this for the next firmware release.
>
>  
>
> I am not sure if this connects to your original problem of not seeing
> encoder at home. Have you hardwired the encoder signal and issued the
> query?
>
>  
>
> Reto Toengi
>
> Engineer
>
> Pro-Dex Oregon Micro Systems
>  
>  
>