RE: Motor Record - OMS58 Driver

["Gillingham, IJ \(Ian\)" <ian.gillingham@diamond.ac.uk>]

This is the very same issue I experienced when migrating my application
from R3.13.9 to R3.14. I concur with Ron about the undocumented change
in parameters. On dropping the 'Number of axes' parameter, it all sprang
into life! It took me a couple of days to track it down.

Regards,
Ian


-----Original Message-----
From: Ronald L. Sluiter [mailto:sluiter@aps.anl.gov] 
Sent: 13 April 2007 15:40
To: Ralph Lange
Cc: EPICS Tech Talk
Subject: Re: Motor Record - OMS58 Driver


Ralph,

If you look at the "Known Problems" from R5-4 to R5-9 on the motor
record web page;

http://www.aps.anl.gov/upd/people/sluiter/epics/motor/index.html

you will find the following;

>    1. An undocumented change was made in R5-4 to two OMS setup
>       functions. Namely, the unused 2nd argument ("axes per card") was
>       eliminated from omsSetup() and oms58Setup().
>
In other words, the 2nd argument was eliminated.  That is probably your 
problem.

Ron


Ralph Lange wrote:

> Hi -
>
> I'm moving a stepper motor application using an OMS VME58 card:
>   from EPICS 3.13.9 / motor 4.9.3   to   EPICS 3.14.8.2 / motor 6.1
>
> In the old setup everything works fine, in the new setup the driver 
> claims that it doesn't find the VME58 motor card. Hardware settings 
> are unchanged, the setup call in the st.cmd is the same.
>
> Searching the release notes of the motor record I did not find 
> anything that I found applicable to my problem.
>
> Before I dig into the code: Is there anything obvious that I didn't 
> see? Similar effects somewhere?
> HW: vxWorks 5.4.2, mv2100, OMS VME58, test stand with no other VME
cards.
>
> Thanks a lot!
> Ralph
>