You can apparently read out the operation time with a SCPI command.
:SYST:INFO? BTIME
Result: "May 26 2015 08:38:06 | 0 0:4 / 9 0:49"
Firmware build time: "May 26 2015 08:38:06"
Current operating time 'day hour:minute': "0 0:4"
Total operating time 'day hour:minute': "9 0:49"
Is just a guess.
Peter
Yes, I think that's right. But it still doesn't give the number of power cycles. The total "on" time is nice to know though, and is probably just as important as the number of power cycles.
Memory Depth set to "Auto" ? This appears to be one of the conditions for freezing.
What do you get in the file when you ask the scope to save a "Param" file?
Storage>Storage>Param and Save to USB stick
The file should contain more information about the software, firmware and board numbers.
Model:DS1xxxZ
SN:DS1ZA170xxxxxx
Manufacturer:RIGOL TECHNOLOGIES
Board Ver:0.1.1
Firmware Ver:0.2.3.11
BOOT Ver:0.0.1.2
CPLD Ver:1.1
SoftWare Ver:00.04.03.SP1
For my information please, why is the number of power cycles important?
For my information please, why is the number of power cycles important?
Not so important in this case aside from determining how much use it's had or the potential for data corruption, but it's a metric in failure analysis.
If you sold an oscilloscope that had a days use on it and a thousand boots it would look very suspicious. Manufacturers love to know this as users often say "I used it now and again now it's broken (sad face)" when they actually drove it into the ground 10hrs a day every day for 5 years straight.
Thank you for the answers. I understand that the total runtime is important, but not the number of boots.
When I buy a car, I want to know the total km or miles, but not how many times the car has been started.
Thank you for the answers. I understand that the total runtime is important, but not the number of boots.
When I buy a car, I want to know the total km or miles, but not how many times the car has been started.
I understand your point, but it's still important information despite your analogy, the hobbyist or the "average car buyer" might not care, at least until their new oscilloscope/car engine freezes.
Memory Depth set to "Auto" ? This appears to be one of the conditions for freezing.
What do you get in the file when you ask the scope to save a "Param" file?
Storage>Storage>Param and Save to USB stick
The file should contain more information about the software, firmware and board numbers.
Model:DS1xxxZ
SN:DS1ZA170xxxxxx
Manufacturer:RIGOL TECHNOLOGIES
Board Ver:0.1.1
Firmware Ver:0.2.3.11
BOOT Ver:0.0.1.2
CPLD Ver:1.1
SoftWare Ver:00.04.03.SP1
Memory Depth is set to "Auto" by default on bootup on mine. I did also toggle it at least once while testing and could not reproduce it. I suggest setting your scope to full defaults and trying, as well as doing this next time you complete a firmware update.
Model:DS1xxxZ
SN:DS1ZA17140xxxx
Manufacturer:RIGOL TECHNOLOGIES
Board Ver:0.1.1
Firmware Ver:0.2.3.11
BOOT Ver:0.0.1.3
CPLD Ver:1.1
SoftWare Ver:00.04.03
Boot code is different, does it get updated at all by a firmware update?
Well, when I do that I get exactly the same screen.
No, my scope was delivered with 00.04.02 "firmware" (what the scope calls "SoftWare"), and I have since updated it several times.
What is this supposed to prove?
Has anyone tested firmware 00.04.03.01.05 ?
https://www.dropbox.com/sh/ph4ff16d9s85tkt/AAA3UeuWQsdGbA_OfDkqiBlVa?dl=0
Glad I read around, I was about to buy a 1054Z. It seems to be a complete firmware fuckup, though. Random freezes are not a sign of good code quality
But now he does.