| Products > Test Equipment |
| Rigol MSO 5000 hardware/software revisions |
| << < (53/84) > >> |
| skander36:
v00.01.02.00.03 2020/02/27 - It solves the error of SCPI instruction reading La channel memory data, and solves the error of SCPI instruction reading La channel memory data v00.01.02.00.02 2020/02/25 - Optimized the connection HDMI start problem optimized the connection HDMI start problem - Optimize the vertical gear, channel zero elimination error - Optimization of the inconsistency between SPI CLK and SDA names - Zoom mode square wave display in optimized 2S time base - Added command to get pass / fail times - Delete the default email account and password - Problems in remote instructions are optimized - Optimized 1K storage depth, waveform recording - The problem of too many stuck events in optimized decoding |
| Cerebus:
--- Quote from: skander36 on March 15, 2020, 10:47:35 am ---v00.01.02.00.03 2020/02/27 - It solves the error of SCPI instruction reading La channel memory data, and solves the error of SCPI instruction reading La channel memory data v00.01.02.00.02 2020/02/25 - Optimized the connection HDMI start problem optimized the connection HDMI start problem - Optimize the vertical gear, channel zero elimination error - Optimization of the inconsistency between SPI CLK and SDA names - Zoom mode square wave display in optimized 2S time base - Added command to get pass / fail times - Delete the default email account and password - Problems in remote instructions are optimized - Optimized 1K storage depth, waveform recording - The problem of too many stuck events in optimized decoding --- End quote --- If we read the Chinglish "Optimize the vertical gear, channel zero elimination error" as something like "Optimised channel gain and offset calibration/compensation" we perhaps have an explanation for the issue with channel 3 coming on in 'auto' from residual noise/offset alone. If they muffed something up in automated gain/offset compensation it would explain this as a regression (in the sense of a bug appearing/re-appearing). Lordy, I do wish the Chinese would spend a few shekels on translation. Do we have any native Chinese speakers who can confirm my interpretation of the release notes from the original Chinese release notes? |
| sb42:
As noted earlier, I'm on firmware 00.01.02.00.02 and cannot reproduce the auto problem. Because NoisyBoy says it's a random event, I wrote a little script to test this repeatedly: --- Code: ---#!/bin/bash addr="192.168.8.32" check="2 3 4" wait="3" repeat=5000 for ((i = 0; i < repeat; i++)); do lxi scpi -a $addr ":autoscale" sleep $wait for c in $check; do res=$(lxi scpi -a $addr ":channel${c}:display?") if [[ "$res" == "1" ]]; then echo "failed at iteration $i: channel $c is on" >&2 exit 1 fi done done --- End code --- So, activate AUTO, wait 3s, check if channels 2-4 are active. With the scope rebooted and set to defaults, the script has been running for an hour with no spurious channel activations so far. Looking at the screen however, I notice that activating AUTO will occasionally (say 5-10% of the time) display a (flat) waveform for channel 2 for just a moment, which then disappears when the display settles. All channels other than CH1 stay off and their buttons are not lit. If I toggle channel 3 on and off before running the script, then it's that channel's waveform that flickers on and off instead; likewise for channel 4. TL;DR - I still can't reproduce the problem but there's now some other thing that I don't know what to make of :-// |
| mabl:
--- Quote from: skander36 on March 15, 2020, 10:47:35 am ---v00.01.02.00.03 2020/02/27 - It solves the error of SCPI instruction reading La channel memory data, and solves the error of SCPI instruction reading La channel memory data --- End quote --- Just as an additional data point: Compared to the larger changes of 00.01.02.00.02, the .03 release really only touches appEntry and the FPGA. --- Code: --- modified: firmware/fw4linux.sh modified: firmware/fw4uboot.sh modified: firmware/rootfs/rigol/K160M_TOP.bit modified: firmware/rootfs/rigol/appEntry --- End code --- |
| NoisyBoy:
What is your hardware version? I tried calibration last night, but skander36 is right, it made no difference. Channel 3 came on with nothing attached. I wonder if Rigol lowered the turn-on threshold with Auto across 5000/7000/8000, and the noisier front end on some 5000 triggers this problem. Regardless, the channel should not come on when there’s nothing attached. --- Quote from: sb42 on March 15, 2020, 03:38:25 pm ---As noted earlier, I'm on firmware 00.01.02.00.02 and cannot reproduce the auto problem. Because NoisyBoy says it's a random event, I wrote a little script to test this repeatedly: --- Code: ---#!/bin/bash addr="192.168.8.32" check="2 3 4" wait="3" repeat=5000 for ((i = 0; i < repeat; i++)); do lxi scpi -a $addr ":autoscale" sleep $wait for c in $check; do res=$(lxi scpi -a $addr ":channel${c}:display?") if [[ "$res" == "1" ]]; then echo "failed at iteration $i: channel $c is on" >&2 exit 1 fi done done --- End code --- So, activate AUTO, wait 3s, check if channels 2-4 are active. With the scope rebooted and set to defaults, the script has been running for an hour with no spurious channel activations so far. Looking at the screen however, I notice that activating AUTO will occasionally (say 5-10% of the time) display a (flat) waveform for channel 2 for just a moment, which then disappears when the display settles. All channels other than CH1 stay off and their buttons are not lit. If I toggle channel 3 on and off before running the script, then it's that channel's waveform that flickers on and off instead; likewise for channel 4. TL;DR - I still can't reproduce the problem but there's now some other thing that I don't know what to make of :-// --- End quote --- |
| Navigation |
| Message Index |
| Next page |
| Previous page |