Experimental Physics and
| |||||||||||||||||
|
We've been using VXI11 over Asyn 4-8, talking to a Agilent E5810A, for a while now. However, I never did get this to work on VxWorks. Using Linux is fine (RedHat Enterprise 4, 2.6.9-42.0.3.ELsmp). When I did try to use VXI11 on VxWorks I got a different error to what you saw, which I posted to tech-talk on 15th June 07. Cheers, Mathew Diamond Light Source On Thu, 2007-08-23 at 09:01 -0700, Robert Emery wrote: Mark, I made the changes to asynManager but that made no difference. I tried using the asynSetTraceMask but that did not give me any more information. When I tried using asynSetTraceMask with my ioc that was working using asyn 4.5, the ports that I set asynTraceMask for would no longer connect. I have attached the outputs from various ioc configurations. Thanks Rob Mark Rivers wrote: > Rob, > > We recently had a report from Dirk Zimich at PSI that VXI11 was not > working with asyn R4-8. But he was upgrading from EPICS R3.13, not an > earlier version of asyn. So your report is very useful, since you say > it worked in asyn R4-5. > > Can you send the complete output when your IOC starts? > > Can you set the asynTraceMask on that asyn port so that you get full > debugging information? > > Also, I suspect that the problem may be coming from the code that was > added in asyn R4-6 to automatically queue a connect request (call to > pasynCommon->connect) when a call to pasynManager->connectDevice is done > for a port with the attributes autoConnect=Yes and isConnected=No. > > Can you please try disabling this code with the following change that > comments out the call to pasynCommon->connect() and letting me know if > it fixes the problem? > > corvette> cvs diff -rR4-8 asynManager.c > Index: asynManager.c > =================================================================== > RCS file: > /net/phoebus/epicsmgr/cvsroot/epics/modules/soft/asyn/asyn/asynDriver/as > ynManager.c,v > retrieving revision 1.93 > diff -u -r1.93 asynManager.c > --- asynManager.c 28 Apr 2007 21:19:58 -0000 1.93 > +++ asynManager.c 22 Aug 2007 17:25:32 -0000 > @@ -1185,6 +1185,7 @@ > } > pasynCommon = (asynCommon *)pasynInterface->pinterface; > commonPvt = pasynInterface->drvPvt; > +/* > status = pasynCommon->connect(commonPvt, pasynUser); > if (status != asynSuccess) { > asynPrint(pasynUser, ASYN_TRACE_ERROR, > @@ -1192,6 +1193,7 @@ > portName, pasynUser->errorMessage); > goto cleanup; > } > +*/ > cleanup: > status = pasynManager->freeAsynUser(pasynUser); > if (status != asynSuccess) { > > Thanks, > Mark > > > >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Robert Emery >> Sent: Wednesday, August 22, 2007 11:25 AM >> To: [email protected] >> Subject: asyn 4.8 problem >> >> I have recently upgraded from asyn 4.5 to 4.8 and am seeing the >> following error messages whereas I didn't have them with 4.5: >> >> Starting iocInit >> ############################################################## >> ############## >> ### EPICS IOC CORE built on Oct 9 2006 >> ### EPICS R3.14.8.2 $R3-14-8-2$ $2006/01/06 15:55:13$ >> ############################################################## >> ############## >> 2007/08/22 09:01:13.319 gpib0,1 vxiCreateDeviceLink RPC error : RPC: >> Unable to receive; errno = Connection reset by peer >> >> 2007/08/22 09:01:13.319 CoilA vxiCreateDevLink failed for addr 1 >> 2007/08/22 09:01:13.319 asynManager::asynConnectCallback, port CoilA >> error calling asynCommon->connect >> 2007/08/22 09:01:13.319 gpib0,1 vxiCreateDeviceLink RPC error : RPC: >> Unable to send; errno = Broken pipe >> >> 2007/08/22 09:01:13.319 CoilA vxiCreateDevLink failed for addr 1 >> >> . >> . >> . >> >> I am using this to control equipment on GPIB via an Agilent E5810 >> Ethernet/GPIB bridge. >> >> Any ideas? >> >> Thanks >> >> Rob Emery >> UW Medical Center >> >> >> > > This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0D! E, United Kingdom
| ||||||||||||||||
ANJ, 10 Nov 2011 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |