Products > Test Equipment

DPO3000 Hacks

<< < (15/15)

lern01:
My oscilloscope DPO3014,Version:2.38 Serial Number:C02xxxx.

BillCRM:

--- Quote from: abyrvalg on April 22, 2015, 10:53:40 pm ---Looks like some things (including BW upgrade) can be done over GPIB, but I don't have a scope to verify. Somebody willing to try?

Some interesting commands:
:PASSWord "password"- enable special modes
  Valid passwords:
  "XYZZY" - "user's password"
  "INTEKRITY" - "backdoor password" (this is the right one for other "backdoor" mode commands)
  "PUBLIC" - "public password"
  "TRESPASS" - "developer password"
  "MKTDEMO" - ???

:SETMODELID id - set model
  Valid IDs:
  0 - MSO/DPO3012 (MSO/DPO is selected by digital channels presense)
  1 - MSO/DPO3014
  2 - MSO/DPO3032
  3 - MSO/DPO3034
  4 - MSO/DPO3052
  5 - MSO/DPO3054

:HWAccountant:SERIAL - get/set serial number

:HWAccountant:INSTRumentid - get instrument id (no set here, it is generated from model+serial)

:HWAccountant:ACQBandwidth bw - bandwidth upgrade
  valid values:
  300
  500

:ARMDEMO pass, num_days - activate demo mode
   pass: "DontMakeTheWookieMad"
   num_days 1-30

--- End quote ---
The command for change serial number seems doesn't work, I tried on dpo2014 and dpo3054 and failed, the hack for model and bandwidth worked well. Maybe I didn't use it correctly?
Could you provide a command example?

phenol:
i updated a dpo3034 with a serial C01… to dpo3054 with :SETMODELID 6. While the -3db point went above 500MHz, the pulse response didn’t look quite right-too much overshoot, jittery rise time readings and unstable triggering. The pulse source was tested on a higher bandwidth scope and was reasonably flat. I wasn’t content with the result so i bumped it back down to 3034 with SETMODELID 4. After rebooting it was back to stock 300MHz.
However, the self test started to return a cpu error (see attached image) erratically. looks like a voltage somewhere is too low. I doubt it’s related to my attempt at hacking it, but who knows, maybe a coincidence? Anyway, i reseated some connectors on the cpu board and it now passes the self test every time.
Does anyone know where and what U0801 is? Ill go back in and measure the voltage on that pin 7 if it craps out again

analogRF:

--- Quote from: phenol on December 18, 2024, 11:03:42 pm ---i updated a dpo3034 with a serial C01… to dpo3054 with :SETMODELID 6. While the -3db point went above 500MHz, the pulse response didn’t look quite right-too much overshoot, jittery rise time readings and unstable triggering. The pulse source was tested on a higher bandwidth scope and was reasonably flat. I wasn’t content with the result so i bumped it back down to 3034 with SETMODELID 4. After rebooting it was back to stock 300MHz.
However, the self test started to return a cpu error (see attached image) erratically. looks like a voltage somewhere is too low. I doubt it’s related to my attempt at hacking it, but who knows, maybe a coincidence? Anyway, i reseated some connectors on the cpu board and it now passes the self test every time.
Does anyone know where and what U0801 is? Ill go back in and measure the voltage on that pin 7 if it craps out again

--- End quote ---

u0801 is a temperature and fan controller and pin 7 is the tacho pin of one of the fans that it can control. so probably the fan is failing.

these scopes never had an official BW upgrade and I have had bad experience trying to upgrade the BW by SETMODELID.
the board is not really calibrated up to 500MHz and then just limited by software to 300MHz like in MDO3000 or ol TDS3000
it will need a full adjustment

phenol:
thanks for the input. to my knowledge this thing only has one fan. I'll look into it.
as for the "upgrade ", im actually happy i could downgrade it back to its stock settings.
years ago i did that to a TDS3034 (3064 now) with greater success- good step response, stable triggering

Navigation

[0] Message Index

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod