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.

Search found 4 matches

by brayday01
January 22nd, 2013, 10:25 am
Forum: Instrument Accessories & GPIB
Topic: KUSB-488B & 2182 NANOVOLTMETER
Replies: 10
Views: 37467

Re: KUSB-488B & 2182 NANOVOLTMETER

Dale, As discussed, I tried to use a different Keithley meter with the KUSB-488B. I used a Keithley 2400 SourceMeter and the problem persisted. I then took the SourceMeter and the KUSB-488B to a different computer. Still 8=timeout when sending *IDN?. I am currently trying to get a hold of another KU...
by brayday01
January 17th, 2013, 9:20 am
Forum: Instrument Accessories & GPIB
Topic: KUSB-488B & 2182 NANOVOLTMETER
Replies: 10
Views: 37467

Re: KUSB-488B & 2182 NANOVOLTMETER

Dale, I am still getting 8=timeout with Lang: SCPI. To ensure all went well with the driver, I disconnected the KUSB-488B from the PC, set the 2182 to SCPI, uninstalled the driver, rebooted the machine, installed the driver, rebooted the machine, plugged in the KUSB-488B, went through the found new ...
by brayday01
January 16th, 2013, 10:45 am
Forum: Instrument Accessories & GPIB
Topic: KUSB-488B & 2182 NANOVOLTMETER
Replies: 10
Views: 37467

Re: KUSB-488B & 2182 NANOVOLTMETER

Dale, Sorry for the delay in getting back to this. I have been out of pocket for a bit. Here are the answers to your questions: 1. Are you using the Model 182 language mode of the SPCI mode of the Model 2182? In your Labview VI do you send commands like T1X or :TRIG:SOURCE EXT? T1X is for Model 182 ...
by brayday01
December 5th, 2012, 4:56 pm
Forum: Instrument Accessories & GPIB
Topic: KUSB-488B & 2182 NANOVOLTMETER
Replies: 10
Views: 37467

KUSB-488B & 2182 NANOVOLTMETER

We recently lost connection to our 2182 via the KUSB-488B. We have been using LabVIEW to record data on the change in voltage with increasing temperature. The system was working perfectly until we disconnected the 488B and reconnected it. Immediately thereafter, we started getting the following erro...

Go to advanced search