Re-enabling options on an Agilent DSO81204A?

[nexus]

So when I enter a random key, or no key at all (completely blank), and press "Install License", I get the same exact message:

"License installation failed. Please contact Agilent technical support".

I have not seen any other messages, no matter what I type in the license key box.

Is this normal for blank or invalid license keys?

[tv84]

Have you tried to reinsert the license.dat file, instead of inserting the licenses via menu?

[nexus]

Yup, I've tried putting the license.dat, license.dat.bak, and Licenseserver.dll files from the original scope/bin folder back into the right directory.

I put the same files in the attached zip.

[PA0PBZ]

I can't see why it would be upset by the expired licenses, it should just ignore them but who knows? Try this:

FEATURE LOWSPEEDDEMO AGILENT 1.0 permanent uncounted \
   HOSTID=VDH=304BMY46001306 SIGN=08505554EB22
FEATURE EBWDEMO AGILENT 1.0 permanent uncounted \
   HOSTID=VDH=304BMY46001306 SIGN=7A82F91A5CEA
FEATURE NOISEDEMO AGILENT 1.0 permanent uncounted \
   HOSTID=VDH=304BMY46001306 SIGN=3B997EA6FFD6
FEATURE SOFTTRIGHIGHDEMO AGILENT 1.0 permanent uncounted \
   HOSTID=VDH=304BMY46001306 SIGN=09922BB4F1EC
FEATURE SOFTTRIGHIGH AGILENT 1.0 permanent uncounted \
   HOSTID=VDH=304BMY46001306 SIGN=698FE0981830
FEATURE LOWSPEED AGILENT 1.0 permanent uncounted \
   HOSTID=VDH=304BMY46001306 SIGN=B3AB5F5A705C
FEATURE 54857_MEMORY AGILENT 1.0 permanent uncounted \
   HOSTID=VDH=304BMY46001306 SIGN=E56B8754C2AA
FEATURE ETHERNET AGILENT 1.0 permanent uncounted \
   HOSTID=VDH=304BMY46001306 SIGN=94BF5EDCB738

[nexus]

Reviving again. I ended up sending my DSO81304B to an expert in Infiniium scopes. I have been working with him for a while, and we are still tackling the display and option issues.

A few takeaways I have learned from working with these scopes so far (and Agilent/KS gear in general).

- Each product line (scopes, spectrum analyzers, signal generators, network analyzers) is made by totally different teams at Agilent/KS. This is why all the naming conventions are different, software suites are mixed, and things like licensing and service are also stratified.

- DSO80K units have two motherboard versions, Intel D915GUX and Adlink M880 Nitro. The D915GUX does not have on-board LVDS driver, so it uses an Adlink PCI-E card which communicates with the D915GUX chipset using intel ADD2 protocol. The PCI-E card converts ADD2 to LVDS for internal display and also controls the backlight inverter. M880 nitro is a custom board by Adlink which includes LVDS driver on board, so no card is needed.

I also bought a DSO80604B recently which has the D915GUX mobo and is fully working. To try and recover the 81304B display issues, I copied U4 EEPROM from the Adlink PCI-E display card in the working unit. To be determined if this fixes display issues.

See attached bin/hex files for U4 eeprom contents from working unit display card. Maybe this will help someone someday.

[nexus]

can't attach hex for whatever reason, website wont have it. see link: https://drive.google.com/file/d/1yxRsc8GLv_FGVaXrnnydf23zqcl6DoPA/view?usp=sharing