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 corrupt data on 2nd scan only (out of 100s of successive scans)

Post Reply
alexwaguespack
Posts: 1
Joined: October 19th, 2017, 1:45 pm
Country: United States

3706a corrupt data on 2nd scan only (out of 100s of successive scans)

Post by alexwaguespack » October 24th, 2017, 6:18 am

Hello, I'm running a C++ application that sends TSP commands over a raw TCP socket to the Keithley 3706a (with a 3724 dual 30ch mux installed) to read a bunch of K thermocouples. My program first sends a handful of commands to setup the device parameters then starts a periodic timer that sends a few commands to execute the scanlist at specific intervals (in the range of .25 - 1.0 seconds). I'm experiencing some odd behavior where the returned values from my 2nd scan gets corrupted. The 1st scan and the hundreds that follow work great, but the 2nd one is consistently garbage.

Since I'm displaying the readings on a temperature vs. time graph, the result is a weird spike near the beginning of every run. I've considered simply throwing away the first couple of scans, but I'd much rather address the root of the problem if possible. Any suggestions would be appreciated. the TSP commands I'm using are listed below. Thanks! -AW

Commands sent once at the beginning to set up parameters.
reset()
reading_buffer=dmm.makebuffer(60)
dmm.func = dmm.TEMPERATURE
dmm.autozero=dmm.OFF
dmm.autodelay = dmm.OFF
dmm.nplc=0.006
dmm.transducer=dmm.TEMP_THERMOCOUPLE
dmm.refjunction=dmm.REF_JUNCTION_INTERNAL
dmm.thermocouple=dmm.THERMOCOUPLE_K
dmm.units=dmm.UNITS_CELSIUS
dmm.configure.set(\"mytemp\")
dmm.setconfig(\"1001:1060\",\"mytemp\")
scan.mode=scan.MODE_FIXED_ABR
scan.create(\"1001:1060\")

Commands sent every 500ms
scan.execute(reading_buffer)
printbuffer(1,60,reading_buffer)

Dave W
Tektronix Applications
Tektronix Applications
Posts: 266
Joined: April 26th, 2010, 12:01 pm
Country: United States

Re: 3706a corrupt data on 2nd scan only (out of 100s of successive scans)

Post by Dave W » January 5th, 2018, 12:18 pm

I suspect it may be due to the dmm.autodelay setting being turned off. Having this turned off can cause the first reading to be "unsettled" as the measurement circuitry may not yet be settled. You get faster performance with it turned off, but you can run into measurement issues with it off.

Try turning it back on and see if your measurements look OK after.

Post Reply

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

Who is online

Users browsing this forum: No registered users and 3 guests