Hey @analogRF I don’t know if you’ve bought a 6500 yet, but I put together that Probe hold script for you and anyone else (@MikeP). Also see the end for news on firmware.
It uses the App interface of the DMM so it behaves a little differently from a normal script. I put together some info below.
INSTRUCTIONS:
1. Download the attached file and change the .txt ending to .tspa
2. Make sure your DMM’s command set is set to TSP in MENU > Settings
3. Put the script on a USB drive and insert into the DMM
4. Press the APPS key and go to the USB tab
5. You can either run the script here, or save it to local memory first (it will be added to local memory automatically)
6. Click Run
DESCRIPTION:
The app adds a swipe screen to the home screen that detects stable readings and displays them on screen. The big reading is still what the DMM is currently measuring. There is a delete button to remove the last reading and a settings button, described below. All readings ever displayed are stored in a separate buffer, called App_buffer, that can be exported just like any other buffer. defbuffer1 holds all the readings the DMM takes, like normal, so you can go back and review the exact measurements taken (though defbuffer1 clears when you change functions). Most functions are supported, the ones NOT supported are digitizing, temperature, continuity, or diode. You can swipe off the probe hold, but no measurements will take place while you’re away from it.
SETTINGS:
- Beeper: turns the beeper on and off
- Probe Hold Tolerance: The app requires that multiple readings (5 to be precise) must be within this percent change to be considered stable
- Low Threshold: Readings below this value are ignored, you may need to change this value depending on your needs or the measure function (like capacitance where you're probably measuring uF. This is really only a setting because I haven’t figured out a good way to discount readings near 0
- Repeat Tolerance: Immediately repeated readings are ignored. Readings are considered repeated if the percent change between the new reading and the last reading is less than this setting.
POWER USERS:
I wrote the app using the TSP language, which is pretty easy to follow as far as programming languages go. There are some Global Settings towards the bottom of the script that act as defaults (except for $mcount, which is not adjustable "in app", and sets the measure count). You’ll see some TODO statements of features I want to add in the future, or places where I know things need to be improved.
BUGS:
I made this in my spare time so I’m 100% sure it has bugs in it, there’s a few I’m even aware of but haven’t had time to fix yet. If you find one though, or have an idea for how you’d like the app to work differently,
you can comment over at this thread on the Tek forum (It’s not like I won’t read it if you post here though…) For one, it doesn’t quit gracefully, if you want to close this app I recommend restarting your DMM, there are lots of ways closing it will lead to blue screens or lock-ups. Most of those issues require a firmware change to fix, and there are things I’d like this app to do which also require a firmware change. That brings me to…
NEW FIRMWARE:
I’ve been told by the project manager that a new firmware will now not be coming until early next year. It’s involved a lot of backend work and it’s simply taken longer than thought to get it ready. I’ll let you all know a firm release date as soon as I get one.
*EDIT: I changed the attached file since the first one I had accidentally had the wrong firmware listed as a requirement.