Tektronix Technical Forums are maintained by community involvement. Feel free to post questions or respond to questions by other members. Should you require a time-sensitive answer, please contact your local Tektronix support center here.

3706A Connection Timeout

Post Reply
Bart Plovie
Posts: 1
Joined: May 9th, 2017, 7:44 am
Country: Belgium

3706A Connection Timeout

Post by Bart Plovie » May 9th, 2017, 8:19 am

I'm currently attempting to establish a connection with a 3706A (running firmware 1.51b - and not allowed to upgrade) from TSB, however I'm running into some significant issues. First I tried the web interface, which worked perfectly fine other than a few Java related bugs. Next I installed TSB and tried to add the 3706A as a LXI instrument on a computer running Windows 8.1. In the Keithley Configuration Panel wizard this resulted in a "VISA Read Error" with no additional information provided. When clicking next anyway I select the 3706A in the instrument list, sadly the software seems to disagree and it said I was using the wrong driver. Though given the fact that the device currently standing next to me says 3706A on the front panel this seems highly unlikely. Thinking it was a Windows 8.1 issue I used an older computer which comes with Windows XP and tried again with no success and the same error. In the meanwhile I verified that all network ports are open and everything seems to be working.

So next I went to grab the 3706A and put it on my desk and connected it to my desktop through USB, while the wizard is now willing to add it the other software seems to fail to recognise it automatically. Manually entering USB0::0x05E6::0x3706::01390768::INSTR as instrument in Keithley Communicator does seem to establish communication at this point, but not very successful as some *IDN? requests seem to result in timeouts. When doing this the device gives me -285 and -420 as error codes if I remember correctly. And the :SYST:ERR? requests Keithley Communicator automatically makes receive the same response. Running the "Test" option in the Configuration Panel Wizard returns an error stating the driver is wrong recommending me to change it, however this has no effect since I do in fact need to use the 3706A driver I suppose? (It's the unit with DMM and front panel with display.) I repeat this test on the Windows XP computer and everything progresses in the same fashion. Next I remove everything from Keithley and National Instruments and uninstall the hardware and disconnect it from the computer.

Based on the advice of a colleague I then first install KIOL, NI VISA 5.2 second, and finally TSB. The device now shows up in VISA Interactive Control with the address USB0::0x05E6::0x3706::01390768::INSTR. And I can open a session to the device and it'll happily read the USB and I/O settings. Doing a query with *IDN? here seems to work fine and returns "KEITHLEY INSTRUMENTS INC.,MODEL 3706A,01390768,01.51b\n". The same problem with Keithley Communicator (time outs seems to persist). So I try to open TSB again, this time I get an error stating:
Failed to retrieve list of available resources.
Unable to load Keithley Configuration Panel.
Install Keithley I/O Layer and try again.

Details: Failed to retrieve list of available resources.

Unable to load Keithley Configuration Panel.
Install Keithley I/O Layer and try again.
com.keithley.KeithleyTSPLib.KeithleyTSPException: KeithleyTSPLib.KeithleyTSPException: Unable to load Keithley Configuration Panel.
Install Keithley I/O Layer and try again. ---> System.Runtime.InteropServices.COMException: Retrieving the COM class factory for component with CLSID {07818C4A-A5E2-11D4-8C0F-00A0C9050948} failed due to the following error: 800702e4 The requested operation requires elevation. (Exception from HRESULT: 0x800702E4).
at KeithleyTSPLib.IviConfigurationStore..ctor()
--- End of inner exception stack trace ---
at KeithleyTSPLib.IviConfigurationStore..ctor()
at KeithleyTSPLib.TspClassDriver.GetResourceList()
at com.keithley.internal.dotnet.ProxyIKeithleyTspConfiguration.Java_com_keithley_internal_dotnet_ProxyIKeithleyTspConfiguration_GetResourceList(IntPtr pEnv, IntPtr pObj1)
KeTSP Driver version: 4.0.5850.18624
KIOL-850C07 is installed so this seems a weird error, but I press ok and I get the Select Instrument window, where I can select USB0::0x05E6::0x3706::01390768::INSTR. Clicking Ok it attempts to connect but quickly fails doing the following:
Failed to open instrument.

VISA reports:
Command `reset()' timed out waiting for instrument response.

KeithleyRemoteIO.VISAException: Command `reset()' timed out waiting for instrument response.
at KeithleyRemoteIO.InstrumentIO.SendCommand(String command)
at KeithleyRemoteIO.InstrumentIO.SendCommandReadResponse(String command)
at KeithleyRemoteIO.TspVisa.Initialize(String resourceName, Boolean idQuery, Boolean reset, StringDictionary optionStrings)
at KeithleyTSPLib.TspClassDriver.Initialize(String ResourceName, Boolean IdQuery, Boolean Reset, String OptionString)
at KeithleyTSPLib.KeithleyTSP.Initialize(String ResourceName, Boolean IdQuery, Boolean Reset, String OptionString)
at com.keithley.KeithleyTSPLib.KeithleyTSP.Java_com_keithley_KeithleyTSPLib_KeithleyTSP_Initialize(IntPtr pEnv, IntPtr pObj1, IntPtr pStr2, Boolean arg3, Boolean arg4, IntPtr pStr5)
This is the output I get from NI I/O Trace being on at the same time as TSB (first two lines are me doing an IDN request in the VISA Interactive Control (capture file attached):
1. viWrite (USB0::0x05E6::0x3706::01... (0x08634E48), "*IDN?.", 6, 6)
Process ID: 0x00000864 Thread ID: 0x00001A58
Start Time: 17:11:39.293 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

2. viRead (USB0::0x05E6::0x3706::01... (0x08634E48), "KEITHLEY INSTRUMENTS ...", 1024, 54)
Process ID: 0x00000864 Thread ID: 0x00001A58
Start Time: 17:11:39.337 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

3. viOpenDefaultRM (0x358E1520)
Process ID: 0x00000D1C Thread ID: 0x00001424
Start Time: 17:11:50.548 Call Duration 00:00:00.003
Status: 0 (VI_SUCCESS)

4. viOpen (0x358E1520, "USB0::0x05E6::0...01390768::INSTR", 4, 2000, 0x358DECD8)
Process ID: 0x00000D1C Thread ID: 0x00001424
Start Time: 17:11:50.551 Call Duration 00:00:00.002
Status: 0 (VI_SUCCESS)

5. viGetAttribute (USB0::0x05E6::0x3706::01... (0x358DECD8), INTF_TYPE, 7)
Process ID: 0x00000D1C Thread ID: 0x00001424
Start Time: 17:11:50.553 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

6. viGetAttribute (USB0::0x05E6::0x3706::01... (0x358DECD8), INTF_NUM, 0)
Process ID: 0x00000D1C Thread ID: 0x00001424
Start Time: 17:11:50.554 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

7. viWrite (USB0::0x05E6::0x3706::01... (0x358DECD8), "ABORT.", 6, 6)
Process ID: 0x00000D1C Thread ID: 0x00001424
Start Time: 17:11:50.554 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

8. viWrite (USB0::0x05E6::0x3706::01... (0x358DECD8), "ABORT.", 6, 6)
Process ID: 0x00000D1C Thread ID: 0x00001424
Start Time: 17:11:51.055 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

9. viWrite (USB0::0x05E6::0x3706::01... (0x358DECD8), "errorqueue.clear(); s...", 465, 465)
Process ID: 0x00000D1C Thread ID: 0x00001424
Start Time: 17:11:51.555 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

10. viRead (USB0::0x05E6::0x3706::01... (0x358DECD8), "97e2f7c7-5292-4709-b5...", 1024, 37)
Process ID: 0x00000D1C Thread ID: 0x00001424
Start Time: 17:11:51.555 Call Duration 00:00:00.002
Status: 0 (VI_SUCCESS)

11. viRead (USB0::0x05E6::0x3706::01... (0x358DECD8), "localnode.prompts=0.", 1024, 20)
Process ID: 0x00000D1C Thread ID: 0x00001424
Start Time: 17:11:51.557 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

12. viRead (USB0::0x05E6::0x3706::01... (0x358DECD8), "localnode.showerrors=0.", 1024, 23)
Process ID: 0x00000D1C Thread ID: 0x00001424
Start Time: 17:11:51.557 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

13. viRead (USB0::0x05E6::0x3706::01... (0x358DECD8), "--hasDebuggingSupport...", 1024, 36)
Process ID: 0x00000D1C Thread ID: 0x00001424
Start Time: 17:11:51.557 Call Duration 00:00:00.001
Status: 0 (VI_SUCCESS)

14. viRead (USB0::0x05E6::0x3706::01... (0x358DECD8), "--hasLocalnodeAccessP...", 1024, 35)
Process ID: 0x00000D1C Thread ID: 0x00001424
Start Time: 17:11:51.558 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

15. viRead (USB0::0x05E6::0x3706::01... (0x358DECD8), "TSP>.", 1024, 5)
Process ID: 0x00000D1C Thread ID: 0x00001424
Start Time: 17:11:51.558 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

16. viWrite (USB0::0x05E6::0x3706::01... (0x358DECD8), "reset()..", 9, 9)
Process ID: 0x00000D1C Thread ID: 0x00001048
Start Time: 17:11:51.759 Call Duration 00:00:00.001
Status: 0 (VI_SUCCESS)

17. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:51.760 Call Duration 00:00:00.003
Status: 0 (VI_SUCCESS)

18. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:51.964 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

19. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:52.165 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

20. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:52.366 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

21. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:52.567 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

22. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:52.768 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

23. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:52.969 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

24. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:53.171 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

25. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:53.371 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

26. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:53.573 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

27. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:53.774 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

28. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:53.974 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

29. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:54.176 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

30. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:54.377 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

31. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:54.578 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

32. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:54.779 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

33. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:54.979 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

34. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:55.180 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

35. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:55.381 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

36. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:55.583 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

37. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:55.783 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

38. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:55.984 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

39. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:56.185 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

40. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:56.386 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

41. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:56.587 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

42. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:56.787 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

43. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:56.988 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

44. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:57.189 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

45. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:57.389 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

46. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:57.590 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

47. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:57.791 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

48. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:57.992 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

49. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:58.192 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

50. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:58.393 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

51. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:58.594 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

52. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:58.795 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

53. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:58.995 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

54. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:59.196 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

55. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:59.397 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

56. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:59.598 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

57. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:59.798 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

58. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:11:59.999 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

59. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:12:00.200 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

60. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:12:00.401 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

61. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:12:00.601 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

62. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:12:00.803 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

63. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:12:01.003 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

64. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:12:01.204 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

65. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:12:01.405 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

66. viReadSTB (USB0::0x05E6::0x3706::01... (0x358DECD8), 0)
Process ID: 0x00000D1C Thread ID: 0x00001B10
Start Time: 17:12:01.606 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

67. viWrite (USB0::0x05E6::0x3706::01... (0x358DECD8), ".localnode.prompts=0....", 115, 115)
Process ID: 0x00000D1C Thread ID: 0x00001424
Start Time: 17:12:01.807 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

68. viClose (USB0::0x05E6::0x3706::01... (0x358DECD8))
Process ID: 0x00000D1C Thread ID: 0x00001424
Start Time: 17:12:01.807 Call Duration 00:00:00.026
Status: 0 (VI_SUCCESS)

69. viClose (0x358E1520)
Process ID: 0x00000D1C Thread ID: 0x00001424
Start Time: 17:12:01.833 Call Duration 00:00:00.002
Status: 0 (VI_SUCCESS)
So my question is quite simple, what the hell am I doing wrong at this point?
Attachments
Capture.zip
NI I/O Trace output
(2.22 KiB) Downloaded 1409 times

Post Reply

Return to “Series 3700 Switch System/Multimeter and Plug-In Cards”

Who is online

Users browsing this forum: No registered users and 2 guests