1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Asyn/StreamDevice for HP3458A through Agilent E5810 LAN/GPIB Gateway |
From: | "Hu, Yong via Tech-talk" <tech-talk at aps.anl.gov> |
To: | Michael Davidsaver <mdavidsaver at gmail.com> |
Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Fri, 17 Jul 2020 14:12:24 +0000 |
Michael, Thank you. Yes, there are two GPIB devices connected to that E5810. The other GPIB device, a DC calibrator, and its IOC are supposed to be offline during machine operation, but they were turned on during maintenance days and left on. There is one record scanned at "2 second" in the DC calibrator IOC. I stopped the DC calibrator IOC. Now, the DMM HP3458A system is back to its previous "normal" state: it scans at "5 second" to read a floating point number without any
problem (again, I have never made this system work faster although I tried all kinds of commands/settings). Indeed, it only takes a few milli-second to get a reply for the command “ID?”. See below.
So, the problem seems related to the DMM itself (specifically related to the data acquisition & readout) rather than the E5810 & the network. 2020/07/17 09:11:25.614
L0 addr 6 queueRequest priority 0 not lockHolder …… 2020/07/17 09:11:25.614 L0 6 vxiWrite numchars 4 2020/07/17 09:11:25.616 L0 6 vxiWrite ID? ID?\n 49 44 3f 0a 2020/07/17 09:11:25.616 L0 addr 6 queueRequest priority 0 from lockHolder 2020/07/17 09:11:25.616 L0 schedule queueRequest timeout 2020/07/17 09:11:25.616 asynManager::portThread port=L0 callback 2020/07/17 09:11:25.616 L0 vxiSetEos 1 \n 0a 2020/07/17 09:11:25.618 L0 6 vxiRead HP3458A HP3458A\r\n 48 50 33 34 35 38 41 0d 0a
2020/07/17 09:11:25.618
L0 vxiSetEos 0 On 7/14/20, 10:42 AM, "Michael Davidsaver" <mdavidsaver at gmail.com> wrote: Yong, As a test, have you tried sending commands through the embedded web server in the E5810? When timing reply latency, it would be interesting to compare with a command which should be quick, like "ID?". If I recall correctly, it is also possible to send vxi11 commands to the E5810 itself. I believe it responds to "*IDN?". This removes the DMM completely from the loop. Unless this is also slow, I wouldn't suspect the network. Also, since I should have asked previously. Is the DMM the only GPIB device connected to this E5810? |