I have another gateway issue, this
time its legit J
My EPICS clients (caget, caput, camonitor and guis) can access my PVs behind my
gateway (R3.14.9). However, I have a MVME2304 running VxWorks 5.3.1 and
EPICS R3.13.10 and it’s having issues with the gateway, basically its not
connecting. Before I added the gateway, it was directly accessing the
channels in question via EPICS_CA_ADDR_LIST and it didn’t have any
issues.
When the vxworks user doesn’t
have write access in the gateway I get the following output for the channels
behind the gateway:
( I cleaned up the output by
removing the good channels and you can ignore the not connected ones).
########################################################################
no write access ‘dbcar‘
summary:
connected
k1laserserver:5064 no_read_access no_write_access k1:ao:ls:bpsd:lsshutCmd.OUT
k1:ao:ls:shutterCmd
connected
k1laserserver:5064 no_read_access no_write_access k1:ao:ls:bto:btoTrack.OUT
k1:ao:ls:ss:btoperm nNoWrite 605
connected
k1laserserver:5064 no_read_access no_write_access k1:ao:ls:bpsd:lightOnPsd.INPB
k1:ao:ls:ss:PsdSum nNoWrite 0
connected
k1laserserver:5064 no_read_access no_write_access k1:ao:ls:bpsd:lsPropSt.INPA
k1:ao:ls:ss:LaserOn nNoWrite 0
connected
k1laserserver:5064 no_read_access no_write_access k1:ao:ls:bpsd:lsPropSt.INPB
k1:ao:ls:ss:LShutOpen nNoWrite 0
connected
k1laserserver:5064 no_read_access no_write_access k1:ao:ls:bto:pntState.INPA
k1:ao:ls:ss:OnSky nNoWrite 0
connected
k1laserserver:5064 no_read_access no_write_access k1:ao:ls:tm5psd:lsPropSt.INPA
k1:ao:ls:ss:LaserOn nNoWrite 0
connected
k1laserserver:5064 no_read_access no_write_access k1:ao:ls:tm5psd:lsPropSt.INPB
k1:ao:ls:ss:LShutOpen nNoWrite 0
connected
k1laserserver:5064 no_read_access no_write_access k1:ao:ls:bpsd:threshSel.NVL
k1:ao:ls:ss:FdMirState nNoWrite 0
connected
k1laserserver:5064 no_read_access no_write_access k1:ao:ls:tm5psd:threshSel.NVL
k1:ao:ls:ss:FdMirState nNoWrite 0
ncalinks 137 not connected 7
no_read_access 10 no_write_access 10
nDisconnect 0 nNoWrite 605
########################################################################
When giving read/write access to the vxworks user, I get the
following errors and a different ‘dbcar’ output:
read/write access dbcar summary:
dbCa:exceptionCallback
stat "Network connection lost" channel "unknown" context
"k1laserserver:5064"
nativeType
DBR_invalid requestType DBR_invalid nativeCount 0 requestCount 0 noReadAccess
noWriteAccess
May 23,
2011 17:13:34.846100273
dbCa:exceptionCallback
stat "Network connection lost" channel "unknown" context
"k1laserserver:5064"
nativeType
DBR_invalid requestType DBR_invalid nativeCount 0 requestCount 0 noReadAccess
noWriteAccess
connected
k1laserserver:5064 k1:ao:ls:bpsd:lsshutCmd.OUT k1:ao:ls:shutterCmd nDisconnect
2
connected
k1laserserver:5064 k1:ao:ls:bto:btoTrack.OUT k1:ao:ls:ss:btoperm nDisconnect 2
nNoWrite 2668
connected
k1laserserver:5064 k1:ao:ls:bpsd:lightOnPsd.INPB k1:ao:ls:ss:PsdSum nDisconnect
2 nNoWrite 0
connected
k1laserserver:5064 k1:ao:ls:bpsd:lsPropSt.INPA k1:ao:ls:ss:LaserOn nDisconnect
2 nNoWrite 0
connected
k1laserserver:5064 k1:ao:ls:bpsd:lsPropSt.INPB k1:ao:ls:ss:LShutOpen
nDisconnect 2 nNoWrite 0
connected
k1laserserver:5064 k1:ao:ls:bto:pntState.INPA k1:ao:ls:ss:OnSky nDisconnect 2
nNoWrite 0
connected
k1laserserver:5064 k1:ao:ls:tm5psd:lsPropSt.INPA k1:ao:ls:ss:LaserOn
nDisconnect 2 nNoWrite 0
connected
k1laserserver:5064 k1:ao:ls:tm5psd:lsPropSt.INPB k1:ao:ls:ss:LShutOpen
nDisconnect 2 nNoWrite 0
connected
k1laserserver:5064 k1:ao:ls:bpsd:threshSel.NVL k1:ao:ls:ss:FdMirState
nDisconnect 2 nNoWrite 0
connected
k1laserserver:5064 k1:ao:ls:tm5psd:threshSel.NVL k1:ao:ls:ss:FdMirState
nDisconnect 2 nNoWrite 0
ncalinks 137 not connected 7
no_read_access 0 no_write_access 0
nDisconnect 20 nNoWrite 2668
########################################################################
This crate is on a separate network
but I have the EPICS_CA_ADDR_LIST set to find the gateway which is using the
default EPICS_CA_SERVER_PORT.
I’ve also logged into my unix
server as the vxworks user and it doesn’t have any problems accessing the
gateway channels.
Only from vxworks. Is it a
vxworks / r3.13.x issue?
Any thoughts on this would be
appreciated.
Mahalo!
Kevin Tsubota
WM
Keck Observatory