RE: spec Channel Access calls timeout

[Pete R Jemian <jemian@uiuc.edu>]

Subject: spec timeout observed

Ok, folks.  Here is one example of a timeout message just received.
I was moving a motor (lax:m58:c1:m6) some distance.
The move took more than a few seconds (maybe 30 s or so).
Only one motor was being moved when the timeout happened.
Nothing else scanning at the time.

Near the end of the move, but before the end of the move,
I received one of these timeout messages.  Here 'tis:
%------------------ clip here --------------------------%
1619.SPEC_USAXS> umv ax -75

         ax
Error reading 'lax:m58:c1:m6.RRBV':  User specified timeout on IO operation 
expired.
   -75.0000

1620.SPEC_USAXS> comment

Wed Nov 20 18:13:48 2002.  0.

1621.SPEC_USAXS>
%------------------ clip here --------------------------%

The comment was added to time stamp the spec command line.
Thinking to check the VxWorks log, there is no entry
synchronous with the motor motion.  Yes, the clocks
are in sync with a time server.
No VxWorks output was given.
Unfortunately, I did not yet turn on spec debugging
as Gerry outline this morning.

Here's the VxWorks console log:
%------------------ clip here --------------------------%
[usaxs@tex,32,~/2002-11]$ tail ~vme/console_logs/lax_vxworks.log
2002-11-04,15:08:16,LAX_VxWorks: sendto failed: S_errno_EHOSTDOWN
2002-11-04,15:12:07,LAX_VxWorks: sendto failed: S_errno_EHOSTDOWN
2002-11-04,15:12:17,LAX_VxWorks: sendto failed: S_errno_EHOSTDOWN
2002-11-04,15:14:06,LAX_VxWorks: sendto failed: S_errno_EHOSTDOWN
2002-11-04,15:14:16,LAX_VxWorks: sendto failed: S_errno_EHOSTDOWN
2002-11-04,15:16:07,LAX_VxWorks: sendto failed: S_errno_EHOSTDOWN
2002-11-04,15:16:17,LAX_VxWorks: sendto failed: S_errno_EHOSTDOWN
2002-11-17,11:02:35,LAX_VxWorks: lax:mvp:c0:m1:tdir = 1
2002-11-19,15:02:13,LAX_VxWorks: interrupt: command error detected by 
motorISR() on card 1
2002-11-20,17:59:32,LAX_VxWorks: lax:m58:c1:m7:tdir = 0
%------------------ clip here --------------------------%


Pete Jemian
UNICAT