Keithley DMM7510 Hidden & Undocumented Features

[Mickle T.]

The Keithley DMM7510, like its little brother, the DMM6500, is a very nice multimeter in every way. Particularly impressive is the flexible programming capabilities of the LUE and the wide range of built-in functions. Those who have delved a little deeper than the Reference Manual know that even more possibilities arise from the numerous undocumented programming interfaces and other hidden features of these devices.
One such hidden feature is the built-in classic game "Breakout," which lets you discover the names of the device's developers (as well as how much the company values ​​them .
To launch the game, go to Menu->Settings->Password and enter the game name "breakout" as a password. Good luck!

[Martin72]

Now I need to know the other hidden features...

[thm_w]

I don't see where it says how much they value anyone, maybe a dev snuck this in. Cool easter egg though.
If you win the game blocks will reset.

[Mickle T.]

Now I need to know the other hidden features...

Attached is a far-from-complete list of TSP interface functions and constants—including debugging and system-level ones hidden behind Lua metatables.
Examples:
1. Entering calibration mode using the admin password if the user password has been forgotten:
cal.unlocknorecall("ADMCAL75MM")
2. Dumping calibration constants:
print(ki.cal.getdata())
3. Remotely disconnecting/connecting multimeter inputs:
ki.dmm.connect = 0
ki.dmm.connect = 1
4. Dumping NVRAM:
print(ki.sysinfo.nvmemdump())
5. Changing the interface language without rebooting:
ki.sysinfo.lang = "SCPI"
TSP$ki.sysinfo.lang = "TSP"
The TSP$ prefix allows the following command string to be executed in TSP mode, regardless of the currently selected system interface language.
6. Executing SCPI commands in TSP mode:
TSP$scpi.execute('TRIGger:CONTinuous REST')
7. Determining fan speed:
print(ki.fan.getfantach())
8. Setting a specific fan speed (0–100%):
ki.fan.dutycycle = 40
9. Forcing the device into local mode:
ki.tsplink.golocal()
10. Rebooting the device:
TSP$ki.reboot()
11. Retrieving the error description for a specific code (example: 0x1642):
print(ki.eventlog.geteventinfo( 0x1642 ))

[Richard W.]

Thanks  I wonder, if some of them work on my 2601A as well...

display.OFF/display.ON would be nice if they work (for lengthy runs, where nobody watches the display. A simple 34401A has this feature...)

also the "fan" functions could be interesting, "gettemp" to see if its already stabilized and the ability to override the speedsettings.
In some cases its switching between two levels in a 5sec interval. Thats quite annoying if you sit right next to it.
Also for times when less accuracy but more power is necessary, one could set the fan to 100% continuously to keep the device cooler.

I already found out some of the math functions, like "math.mod()" for modulo operations and math.ceil(), math.floor() for rounding up and down work.

[Hydron]

I'm going to test some of this out on the dmm6500 too, hopefully the similar UI and firmware means the same commands work. Thanks for the work on this!