-
If the DMM will be left idle between runs, then yes, using the event log is not helpful. There's no other way to tell if the warm up period is directly complete. You can monitor the internal temperature separate from your measurements though. The DMM has a built in internal temperature sensor and command to return the value of the internal temperature. Please see attached screenshot from the manual.
-
The event for warm up time is event number 2822. The message is "Warm up period complete." The eventlog.next() command returns the oldest event in the log, so you could return the event code:
eventNumber, message, severity, nodeID, timeSeconds, timeNanoSeconds = eventlog.next()
And check if the eventNumber is equal to 2822 before proceeding. Once you've read the event remotely, it cannot be read again remotely as it's cleared from the queue, but it does still appear on the front panel. If you restart the DMM, the warmup timer would be restarted and a new warm up event would be generated then.
-
Hi,
The default value should be display.STATE_LCD_50. What firmware version are you running on? This does not appear to be the case on firmware version 1.7.12b.
-
Hi,
There is no direct command to read the warm up time. However according to the manual, an information event should be posted to the event log when the warm up time has completed. Therefore, you could read the event log to confirm the event was posted before proceeding. The event log is cleared on power off, so if the DMM were to lose power, you wouldn't read a previously existing event.
-
Hi,
We do not currently have any plans to add this feature. Thank you for the feedback.