Ilya Grudovik

I created.

Is it possible to add a command to read the Warm_up_end flag?

Temperature reading doesn't work in Digitize mode :(

Thank you for your attention to my problem.

I go to my computer and run my script. I don't see the device. I only have remote access. I don't know if the script was run before me. But I want to know if the device is warmed up. If I read the log, it may have been erased by a previous run of the script.

Is there any other way to find out if the warm-up is complete?

I was considering reading the internal temperature. In my opinion, I can only read the temperature from a warm-up device. But this is also not very convenient because I can only read the temperature when measurements are in progress. It turns out to be a very difficult path..... :(

Hello!  I checked version 12... the problem remained.  It still hasn't been fixed.

It is very uncomfortable.

In my opinion, I can not read the log again? Or I'm wrong?

Hi :)
Thank you!
I have to check it out. In the list of fixes, this was not announced and I did not update the firmware.

Are there any plans to add remote commands for managing dual measurements?

How can a remote program know that the device has warmed up enough? So that I can trust the measurements automatically. Maybe the device has frozen and someone restarted it 5 minutes ago and it has not warmed up yet.

Is there any command for this?

I can read the internal temperature. It becomes relevant after warm-up time. But it's very inconvenient.

The digitize 100V range behaves very strangely.
For example, I see a reaction from a change in input resistance.

Short input noise:
At 10 MΩ - 750 μV
At Auto - 65 μV

Input band:
At 10 MΩ - 17.5 kHz
At Auto - 7.5 kHz

Is there any difference between 10 MΩ and Auto?
If you select a range of 1000V there is no such effect.

print(display.lightstate) always returns display.STATE_LCD_OFF after power-up

At the same time, the device screen is turned on.
This variable starts to work normally only after writing any value to it.
Perhaps the variable does not have an initial initialization.