Any thoughts on this from others who know more would be welcomed though!
Here's is a screen capture, using the 1052e square wave gen on the front panel as the input, trigger voltage set to 0.00uV.
As you can see, the signal crosses 0V 150nS before the "T" indicator at the top of the screen is showing.
Or am I misunderstanding something basic here?
I should get around to adding a DS1152E upgrade firmware as well, just as an option for people. This would upgrade to the 150Mhz model.
Due to the fact the ADC chips are actually rated at 40Mhz (in all units), I'm not sure what issues you will get by overclocking them to such frequencies. As with all chip manufacture, they will be binned based on QC, but I don't know what the QC tests are for the ADC's at given frequencies.
You need a signal with faster edges to see wheather you have an issue with delayed trigger. Check also the situation at falling edge trigger. Both trigger delays should be approx the same. Also check in both sampling modes (equ- and real-time).
For all those downgrading, model changing and upgrading twice, you can just use the above custom firmware and do it in the one flash. Much less chance of bricking.
I developed the hack specifically because I don't like the idea of all the possible things which could cock up with the existing process (like losing hardware version as above).
Up to you though!
Incidentally the hardware version can be set using the :INFO:HARDVERSION command.
Hi,
I've used Gizmo's hacked v4 firmware to increase the bandwidth of a DS1052E. All appears okay except for the displayed signal being delayed 3.4ns after the trigger point (or probably more correctly, the trigger point being displayed 3.4ns too early). On my scope the trigger offset is the same in Real Time and Equivalent Time sampling modes.
If you wish to fix it, there is a SCPI command, but it's not working in latest version unfortunately (another bug).
After much hacking, here's a custom firmware which sets the DS1052E to be a DS1102E. You wont notice any difference in serial or model number, but you now have the functionality of the DS1102E scope (2ns minimum time scale / 100Mhz). I've tested it and my 32Mhz clock I was looking at definitely has more resolution, so it is working.
CRC32: E62BB61B
MD5: 01d2d46d6c565c492b6f49725404f18b
http://synfin.net/public/DS1000EUpdate.rar
For anyone who is sceptical, do a file compare between the official 00.04.00.00.01 firmware and this one, and you'll see only one byte has changed.
As ever use at your own risk, blah blah. Works for my hardware 58 version DS1052E scope.
Edit:
May as well add some instructions. Copy the DS1000EUpdate.RGL file from the rar onto a memory stick, put it in the scope, and select OK when it asks if you want to update. It's that simple.
For your peace of mind, check the file's MD5 against the above number when it's on your memory stick to ensure it's correct before flashing. The scope doesn't bother with any data integrity checking, which is a bit of a shame, so if the file is corrupted at all, you will most likely brick the scope.
Hi, one little remark, regarding the Trigger delay issue:
I own the original 2.06 HW58 on the DS1052E and I noticed on some low rising edges also that the Signal was triggered before it reaches the given Trigger-voltage in the center of the Screen.
I could reduce the delay, by lowering the value, found unter (TRIGGER)-MENU > SET UP >SENSITIVITY.
It goes from 1 DIV to 0.1 DIV. The lower the value, the lower the delay.
Does it reduce the delays on the hacked devices too?
I hope so - Need the "Upgrade", too.
>>The auto calibrate must save all the calibration variables including the trigger delay that is giving you trouble
I am at V 2.06 now, and just discovered, equtrigdelay is updated permantly to a new value... but not realtrigdelay. I thought maybe the realtrigdelay value is not written into nvram bacause the sampling mode is real, so I switched to equ. still no joy. how can I terminate the "rmt"-Session over the serial line? I cannot operate the Scope after I connected over the RS232, scope shows "rmt" and ignores any key presses. So to calibrate after updating realtrigdelay I need to take it "off line" or run the calibrate command through the terminal session. Syntax?
I think, I stay at 2.06 for now...
rgds
Michael