Experimental Physics and
| |||||||||||||||
|
I'm converting an existing BESSY gpib device support from R3.13.9 to R3.14.6, and I have a conversion routine within the device support that does an additional write and then a read in order to proceed with the conversion itself. Does anyone know how is this now done with the new asyn software? This is how the eariler version handled the details... if (drvGpib.writeIb(pdpvt->head.pibLink, pdpvt->head.device, msg, strlen(msg), pdpvt->timeout) == ERROR) goto fail; if (drvGpib.readIb(pdpvt->head.pibLink, pdpvt->head.device, resp, 50, pdpvt->timeout) == ERROR) goto fail; There are local read and write functions within the devSupportGpib() that may be accessible within some function table fouind within one of the structure, but it is unclear to me which can be used within device support. I would appreciate any help someone could offer. - Regards, Kristi Luchini
| ||||||||||||||
ANJ, 10 Aug 2010 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |