So for example, here is a 440 MHz sine wave as displayed on my DS1054Z (100 MHz hacked). Is the amplitude correct? No, but still, you can clearly use the scope to follow it through a circuit. Even going higher in freq. it still displays the signal but it starts to look a little squirrelly.
Thank you very much for your help! For frequency meter of the scope, I assume that it shows wrong frequency. Right?
... I assume that it shows wrong frequency. Right?
The built-in hardware frequency counter - oh hell it's way wrong. But, the frequency measurement you can choose from the left menu, derived from the sample data, it's actually pretty damn close, flickering a bit, but pretty close.
I think I would rather rely on the cursors. Anyway, does the hack actually affect the signal trace of higher frequencies? You mentioned the 3dB point, so is this artificially induced on non-hacked scopes? Or what is the effect of this one hack?
Although the hardware frequency counter can be wrong under certain circumstances, when I compared mine using the output of a calibrated function generator that I borrowed, it was spot on to the last decimal place.
So, don't just blindly assume that the number is correct. Verify that it makes sense either by looking at the wavelength and estimating the expected frequency, turn on the software frequency measurement from the menu on the left of the screen, or use the cursors.
Anyway, does the hack actually affect the signal trace of higher frequencies? You mentioned the 3dB point, so is this artificially induced on non-hacked scopes? Or what is the effect of this one hack?
There is an actual analog low-pass filter in the scope's input. It is switchable to three different configurations under firmware control, and that is what distinguishes the different models in the DS1000Z series. A hacked DS1054Z will have the same input configuration as a DS1104Z.
Dave has done a video where he reverse-engineers the input section of the DS1000Z scopes and draws a schematic, if you are curious.
Although the hardware frequency counter can be wrong under certain circumstances, when I compared mine using the output of a calibrated function generator that I borrowed, it was spot on to the last decimal place.
Hi bitseeker, what I was referring to in that post was the high frequency of 440 MHz, which cannot be measured by the hardware freq. counter.
I just did an experiment, which I hadn't tried ever before, to see how high the hardware and "software" freq. counters could be usable.
I found that the hardware counter basically stopped being usable at 103 MHz, so it's in some way still tied to the "official" or hacked BW. After 103 MHz, the readouts it gave were non-sensical. I was feeding the scope about 440 mV RMS from my generator. Maybe someone else can confirm this.
But the software freq. calculation was working (roughly) up to 440 MHz. It ain't a very accurate readout (+/- 5 MHz) at that high a frequency, but it was hanging in there.
I think I would rather rely on the cursors. Anyway, does the hack actually affect the signal trace of higher frequencies? You mentioned the 3dB point, so is this artificially induced on non-hacked scopes? Or what is the effect of this one hack?
@
MetrologistSo you can better understand BW control see:
https://www.eevblog.com/forum/testgear/sniffing-the-rigol's-internal-i2c-bus/msg353571/#msg353571To see how it is the hardware that sets the bandwidth . But the Bandwidth is selectable in the firmware.
We found out that the DS 70mhz was the same as 100mhz. That chip was the Lmh6518. A similar chip is used in the DS1054Z.
Hi bitseeker, what I was referring to in that post was the high frequency of 440 MHz, which cannot be measured by the hardware freq. counter.
Oh, I see. Is the amplitude just too small to trigger the hardware counter properly at that frequency? I don't know how steep the low-pass filter is on the input, but at some point the signal will be too small to count even though it's visible on the screen.
Oh, I see. Is the amplitude just too small to trigger the hardware counter properly at that frequency?
As xrunner stated in his post that the hardware counter already stops working at 103 MHz, it can't be due to the amplitude drop. There must be some other, timing-related limitation in the counter's implementation.
You mentioned the 3dB point, so is this artificially induced on non-hacked scopes?
Yes.
The hack just turns off the artificial inducement.
You mentioned the 3dB point, so is this artificially induced on non-hacked scopes?
Yes.
The hack just turns off the artificial inducement.
Guys I haven't hacked mine. Do you lose features by hacking it?
Do you lose features by hacking it?
Yes, the 50MHz bandwidth limiter is disabled.
Do you lose features by hacking it?
Yes, the 50MHz bandwidth limiter is disabled.
Ohh Shit..
This is a serious loss. I will not upgrade.
Ohh Shit.. This is a serious loss. I will not upgrade.
I think this is a misunderstanding.
In order to become a 50 MHz oscilloscope, the 1054Z has a 50 MHz bandwidth limiter. Conversely, the 1074Z has a bandwidth limit of 70 MHz.
But this does not affect the optional 20 MHz limit in the analog channels, which I think you understood
borjam, thanks for your response but I was joking back to Fungus joke. You are definitely my friend now. Hopefully Fungus will not joke with me again and become my friend too !!!
Do you lose features by hacking it?
Yes, the 50MHz bandwidth limiter is disabled.
Ohh Shit.. This is a serious loss. I will not upgrade.
You also lose the length properties of the trigger menu and internal RAM.
You also lose the length properties of the trigger menu and internal RAM.
Man I thought you were bullshitting. Tell me seriously. Why should I believe you?
Oh, I see. Is the amplitude just too small to trigger the hardware counter properly at that frequency? I don't know how steep the low-pass filter is on the input, but at some point the signal will be too small to count even though it's visible on the screen.
You're possibly correct, but I do not know. I looked in the manual but I didn't find a specific specification for the hardware frequency counter
As xrunner stated in his post that the hardware counter already stops working at 103 MHz, it can't be due to the amplitude drop. There must be some other, timing-related limitation in the counter's implementation.
I may play around with it some more today. I'd like to know from somebody with an unhacked DS1054Z, what the frequency limit is on that hardware counter.
You also lose the length properties of the trigger menu and internal RAM.
Man I thought you were bullshitting. Tell me seriously. Why should I believe you?
It's true! Both those items get bigger after the hack, ask anyone...
It's easy enough to remove the "hack" and restore the original 1054z configuration, so you can test your own scope in both "hacked" and "virgin" mode.
Send the SCPI commands to the scope using your favorite method (I like telnet over LAN):
Use ":SYSTem:OPTion:UNINSTall" to go back to virgin DS1054Z (without the quotes)
Use ":SYSTem:OPTion:INSTall XXXXXXXXXXXXXXXXXXXXXXXXXXXX" to enter a key, where XXX is your 28 character key (without hyphens or quotes...)
I may play around with it some more today. I'd like to know from somebody with an unhacked DS1054Z, what the frequency limit is on that hardware counter.
Nobody's ever tested this as far as I know. Is there a difference before/after?
It's easy enough to remove the "hack" and restore the original 1054z configuration, so you can test your own scope
Use ":SYSTem:OPTion:UNINSTall" to go back to virgin DS1054Z (without the quotes)
Use ":SYSTem:OPTion:INSTall XXXXXXXXXXXXXXXXXXXXXXXXXXXX" to enter a key, where XXX is your 28
I have file/ email with all the different option keys commands for my scope, I just cut and paste when switching options to test
I just bought myself a DS1054z and it will arrive in a few days.
Expect from the 100MHz hack, what do you reccomend to do? Should I update it to the latest firmware, or leave it as it is?
Thank you