Hi Dirk,
I have seen a similar problem, although not quite the same.
To get a higher update rate into the archiver I did the following
(MVME5500 processor running vxWorks):
1/ sysClkRateSet(1000)
2/ MAXvSetup(1, 16, 0xF000, IVEC, 5, 60)
In the cmd file, and this gives me 60 Hz data.
However, when running in this configuration I get an unrequested move
following a successful move that has a retry. This unrequested move then
takes it off to "infinity".
Are you seeing the problem following (and only following) a retry?
Regards,
Austen Rose.
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Dirk Zimoch
Sent: 23 November 2010 10:10
To: EPICS
Subject: MAXv issue
Hi MAXv users,
We see a problem here with our MAXv cards and I want to ask if anyone
has seen the same effect. This could help us to understand what's
happening.
During a long series of scans that drives a motors in negative direction
in pretty small steps, it happens in rare cases that the motor instead
runs forward a quite large amount, possibly hitting the limit switch.
We have observed this behavior a few times in intervals of some three
hours. Then again nothing went wrong for days. The problem happened with
two different axes and on several different MAXv cards (including cards
with and without the latest bug fix -> see Ron Sluiter's mail "OMS MAXv
announces fix" from October 27)
Pro-Dex is informed but they would like to have more input on the
specific circumstances. Thus my question: Has anyone seen a similar
effect? Under which circumstances did it happen?
Dirk
