Experimental Physics and
Industrial Control System

Benjamin Franksen <[email protected]> · Tue, 18 Sep 2007 15:32:02 +0200

Hi,

we have trouble trying to control a scope (Tektronix DPO7254) via VXI-11. It 
started after the scope's firmware was upgraded to fix some (unrelated) 
bug. However, the side-effect is that our IOC (linux) now crashes:

#!../../bin/linux-x86/SIOC3CP
# Change to top directory
cd ../..
########################################################### Set up 
Environment
epicsEnvSet IOC SIOC3CP
epicsEnvSet LOG_DIR /opt/IOC/log
epicsEnvSet EPICS_CA_PUT_LOG_INET 192.168.48.97
epicsEnvSet STREAM_PROTOCOL_PATH db
############################################## Register all support 
components
dbLoadDatabase dbd/SIOC3CP.dbd 0 0
SIOC3CP_registerRecordDeviceDriver pdbbase
############################################################ Configure 
drivers
# Configure asyn vxi-11 driver for DPO7254 device
vxi11Configure L1 SCOPE1ZCP.mlscs.bessy.de 0 1 inst0 0 0
asynSetTraceMask L1 -1 0x001f
2007/09/18 11:46:36.129 L1 -1 exception 3 occurred calling exceptionUser
asynSetTraceIOMask L1 -1 0x0003
2007/09/18 11:46:36.129 L1 addr -1 queueRequest priority 3 not lockHolder
2007/09/18 11:46:36.129 L1 -1 exception 4 occurred calling exceptionUser
asynSetOption L1 -1 rpctimeout 10
2007/09/18 11:46:36.129 L1 addr -1 queueRequest priority 3 not lockHolder
2007/09/18 11:46:36.129 L1 addr -1 queueRequest priority 0 not lockHolder
2007/09/18 11:46:36.129 asynManager connect queueCallback port:L1
2007/09/18 11:46:36.129 L1 addr -1 vxiConnect
2007/09/18 11:46:36.129 L1 vxiConnectPort
2007/09/18 11:46:37.078 L1SRQ read error: Connection reset by peer
2007/09/18 11:46:37.078 L1SRQ vxiSrqThread terminating
2007/09/18 11:46:37.078 L1 vxiCreateIrqChannel VXI: channel not established 
(create_intr_chan)
2007/09/18 11:46:37.078 L1 Warning -- SRQ not operational.
2007/09/18 11:46:37.078 L1 -1 exception 0 occurred calling exceptionUser
[1]    19274 segmentation fault  (; cd 
SIOC3CP/iocBoot/iocSIOC3CP; ./st.cmd; )

Most probably the scope's new firmware is at fault for sending strange 
responses or something. Anyway, asyn should not crash, even if the device 
sends protocol errors.

We have tried several versions of asyn (4-5, 4-6, 4-8) and several versions 
of stream (all versions from 1.1 to the latest snapshot) but they all 
display teh same or similar behavior. The base release is 3.14.8.2.

Our main problem is that the scope should be operational at the start of 
next week when out shutdown ends. So, our next step will be to try 
communication via a GPIB gateway.

Still, any advice on how to search for and maybe fix the error that lets 
asyn crash would be appreciated.

Cheers
Ben
-- 
"Programming = Mathematics + Murphy's Law" (E.W.Dijkstra)

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System