Ty McKinney

Hello,
The DMM4040 is an obsolete and unsupported DMM so the amount of support I am able to give is very limited. I did manage to find the programmers manual found below here, start on page 31 for all accepted SCPI commands.
DMM4040 and DMM4050 | Tektronix

Hello,
As listed in the error message, error code 1135 is a syntax error meaning there is a typo or invalid character somewhere within your program. I would recommend stepping through your script to find the exact command that is throwing this error.
Hope this helps!

Hello,
This script is only for 2636/2635 model to adjust offset current after upgrading 1.4.2 from 1.3.x. The model 2636 has more current ranges in the lower side than 2602. This script is only for the lower range adjustment. So, the script cannot be applicable for 2602 model. If you upgrade 2636, then the script is installed in the instrument but no script for 2602. I think your unit- with 35% offset uncertainty, needs to go to the service team to perform calibration. The Model 2602 is a very old unit, and we are not supporting it in service. But it is confirmed from our service team that we have calibration service only for the 2602.
See link below to help you start this process (US ONLY link attached, see Calibration & Services section on tek.com if out of US).
Service Quote | Tektronix

Hello,
Can you open a ticket with our Tek support team? This looks like it requires individual attention by one of our application engineers. See link below.
Support | Tektronix

Hello,
Can you supply a copy of your code?
This will help diagnose where the issue may lie.
 

Hello,
Apologies for the late response, I noticed this had been sitting here unanswered for a few weeks.
This is a bug that is known and we are working on a solution.
Can you tell me what firmware version you used previously where there was no issue? I would recommend downgrading to that version to fit your applications until a fix is presented.
If you can not find the firmware version that you need, where there was no pause in data entry, please open a case with our technical support center and we can work with you individually. If you make a case with us, please reference your TekTalk forum post so we can sort it out to the correct team.

Hello,
I would recommend updating to the latest firmware version found at the link below and see if that fixes this bug, as we may have patched it in a previous release.

Model 2450 Firmware Revision 1.7.12 and Release Notes | Tektronix

Let us know if this works!

Hello,
There are a few ways to get to an acquisition rate around 10kHz, by setting your NPLC to a set number such as somewhere around .006 to be around that ballpark. However, there is also a few other factors that you will need to consider such as firmware overhead, auto range, any filters you may be using, switching relay (open and closing of the relays IF using a switching card), and settling time for example- all of which will alter your sample rate. It may take some trial and error to find the sweet spot for stable 10kHz acquisitions. This is the most brute force method to fit your needs, aside from what you had mentioned previously about setting a fixed readings per second rate. But, again, this may change some settings. Hopefully this provides some insight and a good starting point!
For other measurements, for future notice, you can utilize the built-in digitizer. However, this does not work with resistance measurements of any kind. Only current and voltage (AC and DC signals).

Hello,
My first guess to combat this issue you're encountering is ensuring you are running your instrument on the latest firmware version. See Menu>System>Info-Management and the firmware will be displayed at the top left of your screen. The latest firmware can be found at the link below, version 1.7.12. The instructions on upgrading can be found at that same link under the release notes.
Model DMM6500 Firmware Revision 1.7.12 and Release Notes | Tektronix

Please let us know if that fixes your anomaly!

Hello,
I do not believe the driver supports scanning with the DMM6500. The example you're referencing states it's a DAQ6510 example, which would explain why the error is saying that the command is not supported by the DMM6500. See attached picture for DAQ ONLY capable commands.