John,
There was a change in the oms58Setup command some time ago. Here is a
diff of my st.cmd file from one I used previously
########################################################################
########
# Setup device/driver support addresses, interrupt vectors, etc.
-# OMS VME58 driver setup parameters:
-# (1)cards, (2)axis per card, (3)base address(short, 4k boundary),
-# (4)interrupt vector (0=disable or 64 - 255), (5)interrupt level
(1 - 6),
-# (6)motor task polling rate (min=1Hz,max=60Hz)
-oms58Setup(8, 8, 0x4000, 190, 5, 10)
+# OMS VME58 driver setup parameters:
+# (1)cards, (2)base address(short, 4k boundary),
+# (3)interrupt vector (0=disable or 64 - 255), (4)interrupt level
(1 - 6),
+# (5)motor task polling rate (min=1Hz,max=60Hz)
+oms58Setup(10, 0x4000, 190, 5, 10)
Note that the second argument used to be axis per card, but it is now
the base address. So perhaps you are simply using the wrong syntax?
Mark
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of John M. Skinner
Sent: Tuesday, June 24, 2008 1:00 PM
To: [email protected]
Subject: Re: latest motor record on RTEMS?
I get the following. I've tried an mvme2307 and mvme5500 with the same
results.
dbior drvOms58
Driver: drvOms58
Oms Vme58 motor card #0 not found.
Ron Sluiter wrote:
I can't address the RTEMS question, but I doubt that the error is
related to the OS.
This error message occurs when the motor driver fails to establish
communication
with the motor controller at boot-up (iocInit). I suggest querying
the EPICS shell with;
dbior "<driver_name>"
where <driver_name> is; e.g., drvOms58, drvMM4000. You may get message
like the following,
dbior "drvOms58"
Driver: drvOms58
No VME58 controllers configured.
value = 0 = 0x0
Hope this helps,
Ron
John M. Skinner wrote:
We're running several NSLS beamlines with 5.3 motor records under
RTEMS. I got the motor code from Bill Nolan, who might have gotten it
from Kate Feng. We'd like to upgrade our motor records, but I've
tried 6.1 and 6.3 and I get "motor_init_record_com(): card does not
exist!" errors. Is anyone using motor records beyond 5.3 under RTEMS?
