DPO3000 Hacks

[analogRF]

can options (not necessarily the BW) be enabled on DPO4000 using the SCPI commands?

[VooDust]

But w.r.t. calibration, did you check the bandwidth? is it in fact >=500MHz?

I probed a 433Mhz carrier signal earlier this week. It allowed me to build a clone of my garage door opener. Since I only own 200 MHz probes, I presume the signal was attenuated heavily.

However, at 100 MHz, or 150 MHz (which is the available low pass setting when running the 500 MHz model) the RF signal was virtually nonexistent! With 500 MHz however, I got 800mV peak-to-peak!

So yes the upgrade is the bomb! I'm not able to provide details like trigger sensitivity, rise time etc. since I lack the equipment (and knowledge).

Cheers.

[VooDust]

If only I could upgrade from 2 to 4 channels... I would trade the 500 Mhz for this 

[smaultre]

Sure i make some research. It works, but there in the 4054 has no much dac's and demux chips on the board physically 
Its the perfect way upgrade 4034 to 4054 !

[analogRF]

I upgraded my DPO3012 from 100MHz to 500Mhz. After my initial joy  I noticed something very odd:



The "zero line" (i.e. measuring ground) is out of alignment - it's always minus half-a-div for vertical divs >= 50mV. So:

• 10mV - OK
• 20mV - OK
• 50mV - minus 1/2 div, AVG is -25mV
• 100mV - minus 1/2 div, AVG is -50mV
• 200mV - minus 1/2 div, AVG is -100mV
• and so on...

I ran some checks and this happens for either 500MHz and 300MHz settings, with 300MHz being off minus 1 div instead. Kind of a deal breaker...

Does anyone have a clue what's going on? It happens regardless of input termination, AC/DC coupling (!), trigger settings, or probe attenuation and bandwith settings. I tried adjusting the "Offset" parameter of the probe, but that just shifts the phosphor line, the wrong voltage values remain.

Luckily I was able to downgrade back to 100MHz and everything is back to normal 

would you mind saying which of the commands/methods you used for BW upgrade? also was your S/N >C020xxxx or <C020xxxx?

[analogRF]

I cannot get these to work and my IDA skills are too bad to figure out what is happening.

As I said in the other thread, there should also be a debug console avalible that is accessible through TCPIP but I cannot figure out how to connect to it....

Just a guess, but maybe Telnet? I have an MSO3034 -  I'll give it a try later today and see what happens.

Jay

OK, so using telnet didn't work, but using my browser (Firefox) brings up a Tektronix menu.
I selected the tab "DATA" and I'm able to talk to the scope using GPIB commands.
I then sent the following per abyrvalg's post:

:SETMODELID 5
:HWAccountant:ACQBandwidth 500

Then power-cycled the unit. It did not make any changes.
So I used the back door password first:

:PASSWord "INTEKRITY"
:SETMODELID 5
:HWAccountant:ACQBandwidth 500

Then power-cycled the unit again. Still no change. I'm probably doing something wrong; I'm an idiot when it comes to stuff like this... 

Jay

OK, it's confirmed, I am an idiot.  Remove the quotes around the password:
:PASSWord INTEKRITY
:SETMODELID 5
:HWAccountant:ACQBandwidth 500

Voila, it reports that it is a MSO5054!

Thank you very much abyrvalg!  Now to do some bandwidth testing!

Jay

Was your serial number >C0200000 or less?
was the upgrade successful both in triggering, amplitude and also in doing measurements?

[KrzysztofB]

I know topic is a bit old, but does anyone know if anything changed?
I was trying to unleash some serial decoding features on our old C01xxx DPO3034 to see if it would be worth purchasing it, but somehow ":ARMDEMO" seems to not work what so ever?
Anyone something about the topic?

[analogRF]

Has anyone tried doing the factory adjustment on DPO3000? Is it possible to do it DIY without Fluke calibrator?

perhaps JWalling can comment on this 

[Jwalling]

Has anyone tried doing the factory adjustment on DPO3000? Is it possible to do it DIY without Fluke calibrator?

perhaps JWalling can comment on this 

I've never tried...

[OYAZI]

Hello,
DPO/MSO3000
I was success that change of a model name and B/W.
Does anyone know the way to change s/n?

[darkstar49]

That info is at the beginning of the thread…
What’s the point changing the serial ? Do you expect to fool Tek in case you’d use their servicing ?
I’d be careful doing that… the instrument Id, which is if I remember well, derived from the serial, and is used to compute option keys… and I’m’pretty sure the instrument Id is stored at several places, either in the NVRAM, on the file system (flash), or both… and I wouldn’t be too confident that the call to alter the serial will update everything as it should…

[ebastler]

Does anyone know the way to change s/n?

Did you steal your scope or do you plan to use it to commit a crime? 

[OYAZI]

There is DPO3000 which damaged physically and there is other DPO3000 to which the mainboard is failed.
Don't you think to replace a mainboard with other machines?

[ebastler]

No worries, I was just kidding.

If my scope needed repair via a new (used) mainboard, I would not mind if it ended up with a different serial number in firmware vs. the stricker on the enclosure. Same as with an engine swap on a car, I guess. And as others have said, it is probably not so easy to change the serial number.

[analogRF]

No worries, I was just kidding.

If my scope needed repair via a new (used) mainboard, I would not mind if it ended up with a different serial number in firmware vs. the stricker on the enclosure. Same as with an engine swap on a car, I guess. And as others have said, it is probably not so easy to change the serial number.

but it will be an issue if you decide to sell the scope (or the car)

Changing the SN is easy to do either with SCPI or through the UART. But I have a bigger problem at hand which I hope someone can shed some light on

I have had this DPO3054 for about 2 years with a cooked front end board (TEK calls it attenuator board). The FPGA on the attenuator board was literally cooked.
So I finally got my hands on a very broken DPO3034 with broken case, missing PSU, and devoured main board but with good attenuator board. So I replace it and the scope works perfecly albeit totally out of calibration but it even passes SPC. However, it fails the self test (even power on self test) and the only reason is Attenuator board serial number mismatch It shows up as "No Ser" and I have not been able to enter/program the SN of the new atten board into the scope.

Does anybody know what needs to be done?

[darkstar49]

There are two options to address the issue...

The first one would be to patch the firmware to ignore the mismatch, the second is to alter the serial on either side, assuming they're to be identical, and not somehow 'related' via some computation...
A detailed 'system config' dump of a genuinely 'normal' DPO3K could perhaps help clarify this, if someone has one at hand.
Do you know where the FE board's serial is stored ? Is it 'burned' into the FPGA or stored in some NVRAM on the FE board ?

[analogRF]

Do you know where the FE board's serial is stored ? Is it 'burned' into the FPGA or stored in some NVRAM on the FE board ?

How to alter the serial? That was my question. That's what I have been trying to do...

There are no eeprom on that board. Can they store it in a FPGA?


in a good scope, the SN of the atten board appears in the list on the config page. in this scope, it shows "No Ser"

[analogRF]

the thing is I can change SN of all the othe modules, PSU, FP board, Display, Main board...it is just the Attenuator board that cannot be changed 

[lern01]

Very sorry, restart the thread, DPO3000 module crack someone successful?

[lern01]

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

I successfully connected to the computer through the LAN, and the following situation appears when I entered the command. What is the cause?

[lern01]

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

[BillCRM]

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

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?