Does anyone know of a 1.01 hardware difference?
New scope seems to have a low noise fan and the display brightness is much better than previous one
The Keysight gets around 20-50% of the event, the Siglent SDS1104X-E none and the Rigol MSO5074 none.
Probably you should use a specific hardware which can only decoding for this special case.
It is not a specific use case that I have, it is just a scope decoding benchmark I created and was able to test it on Keysight, Siglent, GWInstek, Micsig and now Rigol scopes.
Serial protocol triggering and search seem to be implemented independent of the decoding (display). Even when the decoding is disabled, you can set trigger to SPI and do search on SPI as well.
It is not a specific use case that I have, it is just a scope decoding benchmark I created
Is there a separate forum thread where I can report bugs?
It is not a specific use case that I have, it is just a scope decoding benchmark I created and was able to test it on Keysight, Siglent, GWInstek, Micsig and now Rigol scopes.
It is a specific use case that most people would not encounter. We even get different results trying to measure the same thing.
Anyway, why are you using 1Mpt dept, why can't it be lower?
I've shown in your thread that 50,000 triggers per second with the Rigol is possible. It would also capture every unusual SPI event (about once per second).Serial protocol triggering and search seem to be implemented independent of the decoding (display). Even when the decoding is disabled, you can set trigger to SPI and do search on SPI as well.
Yes this seems to be the case that there is some processing done in HW and some in SW. So either Rigol has not had time to make use of the HW functionality yet, and it was easier to implement in SW, or there are limits to the HW (ie can trigger but can't store all the packets).
Ah, the second confirmation of my measurement, so it couldn´t be a coincidence anymore…
1st confirmation
.
.
.
After consulting with rigol, I´ll send my scope to them in mid of june for fixing the noisy fan issue (and probably the dim display issue too).
Hi~ sir.
Does anyone know of a 1.01 hardware difference?
My RIGOL is 1.00. and a different offset when self calibrated.
3ch At 10mv, dc gain is not within normal range.
When the same signal, the two channels are different.
Setting Auto Mem Depth (1Kpts in this case) I can get 50,000 triggers per second. I still cannot make Zone trigger to work with the random byte 0x3F
Hi~ sir.
Does anyone know of a 1.01 hardware difference?
My RIGOL is 1.00. and a different offset when self calibrated.
3ch At 10mv, dc gain is not within normal range.
When the same signal, the two channels are different.
Did you let it warm up ~15min+ before starting self calibration, and all channels are disconnected? Try doing it again.
I don't see any offset issue if I set all channels to 10mV, and 4x average I get: -255uV, -550uV, -420uV, and -300uV. I see a slight difference between channel 1, 2 and channel 3, 4 in terms of vertical amplitude but its not very much. 1.460V vs 1.413V for example.
Hardware difference is not confirmed yet.
--------------------------------------------------
Yes.
I tested it after 30 minutes and 1 hour.
I think calibration error is big.
Yes.
I tested it after 30 minutes and 1 hour.
I think calibration error is big.
DC Offset Accuracy <200 mV/div (±0.1 div ±2 mV ±1.5% of offset value)
DC Gain Accuracy[2] ± 3% of full scale
This is the 2nd MSO5074 I am testing and the UI is more responsive [...] than the previous unit. I tested both units with the same firmware 1.1.04.04
Does anyone know of a 1.01 hardware difference?
Vertical Resolution: 8 bits
Vertical Sensitivity Range[3]: 1 mV/div~10 V/div
Dynamic Range: ±5 div (8 bits)
Note[3]: 1 mV/div and 2 mV/div are a magnification of 4 mV/div setting. For vertical accuracy calculations, use full scale of 32 mV for 1 mV/div and 2 mV/div sensitivity setting
After consulting with rigol, I´ll send my scope to them in mid of june for fixing the noisy fan issue (and probably the dim display issue too).