|
Hi Feng,
Can you send the link to that project on Github?
I see that it is using asyn, so you should be able to enable asynTrace on the low-level driver and see the communication between EPICS and the device. Right now it looks like EPICS is sending messages but getting no response.
The datasheet says the 6845 supports both RS-232 and GPIB. Which are you using? With RS-232 there are lots of things that can go wrong, from the cable to the parity, data bits, stop bits, etc.
Mark
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of LONG FENG via Tech-talk <tech-talk at aps.anl.gov>
Sent: Tuesday, March 11, 2025 6:13 AM
To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: Keithley device reading failure
Hi all,
I'm using the Keithley648x project from GitHub to read data from my Keithley 6485 device. However, I'm getting the following error messages:
2025/03/11 18:49:30.491 k648x:CA1:model devAsynOctet::readIt failed
2025/03/11 18:49:30.491 k648x:CA1:serial devAsynOctet::readIt failed
2025/03/11 18:49:30.491 k648x:CA1:digRev devAsynOctet::readIt failed
2025/03/11 18:49:30.491 k648x:CA1:dispRev devAsynOctet::readIt failed
2025/03/11 18:49:30.491 k648x:CA1:brdRev devAsynOctet::readIt failed
2025/03/11 18:49:30.491 k648x:CA1:read devAsynFloat64::processCallbackInput process read error
2025/03/11 18:49:30.491 k648x:CA1:rangeAuto devAsynInt32::processCallbackInput process read error
2025/03/11 18:49:30.491 k648x:CA1:zeroCheck devAsynInt32::processCallbackInput process read error
2025/03/11 18:49:30.491 k648x:CA1:zeroCorrect devAsynInt32::processCallbackInput process read error
2025/03/11 18:49:30.491 k648x:CA1:medianFilter devAsynInt32::processCallbackInput process read error
2025/03/11 18:49:30.491 k648x:CA1:digitalFilter devAsynInt32::processCallbackInput process read error
2025/03/11 18:49:30.491 k648x:CA1:digitalFilterControl devAsynInt32::processCallbackInput process read error
2025/03/11 18:49:30.491 k648x:CA1:medianFilterRank devAsynInt32::processCallbackInput process read error
2025/03/11 18:49:30.491 k648x:CA1:digitalFilterCount devAsynInt32::processCallbackInput process read error
2025/03/11 18:49:30.491 k648x:CA1:rate devAsynInt32::processCallbackInput process read error
2025/03/11 18:49:30.491 k648x:CA1:range devAsynInt32::processCallbackInput process read error
2025/03/11 18:49:30.491 k648x:CA1:rangeAutoUlimit devAsynInt32::processCallbackInput process read error
2025/03/11 18:49:30.491 k648x:CA1:rangeAutoLlimit devAsynInt32::processCallbackInput process read error
2025/03/11 18:49:30.491 k648x:CA1:readStatusOverflow devAsynInt32::processCallbackInput process read error
2025/03/11 18:49:30.491 k648x:CA1:readStatusFilter devAsynInt32::processCallbackInput process read error
2025/03/11 18:49:30.491 k648x:CA1:readStatusMath devAsynInt32::processCallbackInput process read error
2025/03/11 18:49:30.491 k648x:CA1:readStatusNull devAsynInt32::processCallbackInput process read error
2025/03/11 18:49:30.492 k648x:CA1:readStatusLimits devAsynInt32::processCallbackInput process read error
2025/03/11 18:49:30.492 k648x:CA1:readStatusOvervoltage devAsynInt32::processCallbackInput process read error
2025/03/11 18:49:30.492 k648x:CA1:readStatusZeroCheck devAsynInt32::processCallbackInput process read error
2025/03/11 18:49:30.492 k648x:CA1:readStatusZeroCorrect devAsynInt32::processCallbackInput process read error
2025/03/11 18:49:30.492 k648x:CA1:readStatusRaw devAsynInt32::processCallbackInput process read error
2025/03/11 18:49:30.492 k648x:CA1:readTimestamp devAsynInt32::processCallbackInput process read error
iocRun: All initialization complete
I've only modified the path definitions in configure/RELEASE. Are there any additional steps I should follow or configurations I might have missed?
Any suggestions would be greatly appreciated. Thanks!
Feng
|
