Lecroy options -=recovery=-

[Momchilo]

This is trial and error. But most of those options should work without any problem. And most of those options that don't work don't cause the fatal error.

It is possible to add more function to a scope than you could bought. At least for the Wavesurfer series.  I don't own a Waverunner.
The memory options shouldn't cause the error. For the old 500 Wavesurfer series it was possible to increase the memory with the option from M to L. So the memory chip(s) was already populated.

I know it is annoying but to reprogram the EEPROM is not a big deal. It will take 1-2 hours, a soldering iron and an Arduino. The worst case is not that bad
 

[sprit]

Schenkenstein

Now you only have to swap the CPU, RAM and hard disk. It will be a huge different but one more complete disassembly
CPU: https://www.cpu-world.com/CPUs/Pentium-III/TYPE-Pentium%20III%20(Tualatin).html
RAM: 2x 1GB DDR1 333MHz
hard disk: https://www.amazon.de/Geh%C3%A4use-Adapter-m-2-NGFF-Festplatte-Klassische/dp/B0196PRXY0 + https://www.amazon.de/Green-interne-Festplatte-Lesegeschwindigkeit-Solid/dp/B078WYRR9S + https://www.amazon.de/EasyULT-Adapter-Erforderlich-Unterst%C3%BCtzt-Kompatibel/dp/B07T5D6J81 (to restore backup)

Hi  Schenkenstein

Sorry for degging this post but can you make a tutorial how to do that plz? Thank you very much

Sincerely

[Schtolz]

Hello, colleagues!
I wanted to tell you about the attempt to apply the instructions specified in the first post for the HDO4054A model. First of all, I would like to note the need for strict compliance with the instructions attached to the .py files. Namely:

1) installing Python version 2.7.9 from the site repository python.org (it is worth mentioning separately that the path must be written in the system variables for correct operation) to avoid problems with the pip utility earlier versions;
2) installing Visual C++ version 9.0 for Python from the Microsoft website,
3) installing PyCrypto using the utility pip ("pip install pycrypto" in the console).
One of the posts included an archive with the most detailed text of the instructions for use. Following them, i managed to get a list of available extensions, generate a key for the required extension, perform its validation and additional verification.

The only catch is that XStreamSDO version 8.6 was installed on my oscilloscope, which obviously did not allow the necessary extension to be activated. At the same time, the oscilloscope sees the entered key as a LegacyKey (which indirectly indicates its validity, since even the name of the extension is displayed). In one of the posts there was a link for the XStreamSDO program version 8.0.1. By installing it on the oscilloscope, it was possible to achieve the functioning of the necessary extension (previously. additional testing is needed).

In this regard, a number of questions arose:
1) Is it correct to use XStreamSDO 8.0.1 for the HDO5054A oscilloscope?
2) Can someone provide a 64-bit version of the XStreamSDO 8.6, or the most relevant for my model, since I can't download it due to a strange blocking of my account on the Lecroy website? I wanted to be able to return the XStream to its original position.

Thank you in advance for any help!

[tv84]

2) Can someone provide a 64-bit version of the XStreamSDO 8.6, or the most relevant for my model, since I can't download it due to a strange blocking of my account on the Lecroy website? I wanted to be able to return the XStream to its original position.

Here v8.9 for 24 hours.

[Schtolz]

2) Can someone provide a 64-bit version of the XStreamSDO 8.6, or the most relevant for my model, since I can't download it due to a strange blocking of my account on the Lecroy website? I wanted to be able to return the XStream to its original position.

Here v8.7 for 24 hours.

I'm sorry, sir! could you please send another link? didn't have enough time to download the file

[alm]

1) installing Python version 2.7.9 from the site repository python.org (it is worth mentioning separately that the path must be written in the system variables for correct operation) to avoid problems with the pip utility earlier versions;

Or instead of using a Python version from almost a decade ago, you can apply the patch I posted here to make it work with current Python versions and the current Pycryptodome library.

[alm]

has anyone tried to use the options within flag #08? Seems as they are wrongly generated - maybe to "new"....

Example:

Code: [Select]

08-00002000 I2C_TDME 
08-00004000 SPI_TDME 
08-00008000 UART_TDME


result after validation - the flag add the option is "0":

Code: [Select]

Flags: 08
Mask: 0000E000
Options:
00-00002000 USB
00-00004000 SPI_TDME
00-00008000 UART_TDME

in the scope, the key leads in totally different options...
Any ideas / guessing?

I observed the same with flags 80 options. Looking at the X-Stream 7.9.0.1 options.cfg, it has no 0x08 or 0x80 options listed, so I guess this was stored as two 3-bit digits (0-7) at some point, causing both 0x08 and 0x80 to be interpreted as 0. I noticed that the license generation swaps bytes in the scope ID if the mask is >= 0x40, and tried any other permutation of scope ID bytes with mask 0x8, but none of them was accepted by the scope. Since the 0x08 and 0x80 options started appearing around the same time as the change to a new key generation scheme, I'm guessing the scope won't accept these options with the old key format as is currently implemented in the key gen.

[tv84]

I observed the same with flags 80 options. Looking at the X-Stream 7.9.0.1 options.cfg, it has no 0x08 or 0x80 options listed, so I guess this was stored as two 3-bit digits (0-7) at some point, causing both 0x08 and 0x80 to be interpreted as 0. I noticed that the license generation swaps bytes in the scope ID if the mask is >= 0x40, and tried any other permutation of scope ID bytes with mask 0x8, but none of them was accepted by the scope. Since the 0x08 and 0x80 options started appearing around the same time as the change to a new key generation scheme, I'm guessing the scope won't accept these options with the old key format as is currently implemented in the key gen.

No need to reinvent the wheel. Look at the options list here and use those flags/bitmasks.

[alm]

No need to reinvent the wheel. Look at the options list here and use those flags/bitmasks.

This is on X-Stream version 8.4.1.4 (same on 8.1.2.0) on a Windows XP / 32-bit WP7300A, which as far as I know is the last that supports Windows XP, and 32-bit support ended shortly after. Generating a key with as flags 0x4201 gives "this key cannot be installed, appears to be invalid".

[tv84]

Generating a key with as flags 0x4201 gives "this key cannot be installed, appears to be invalid".

Flag is 0x42. The rest is part of the bitmask.

[alm]

Flag is 0x42. The rest is part of the bitmask.

I didn't get that, thanks! But it still doesn't work. For example I2C-TDME is 42-01002000 according to that file, but the scope also rejects a key for that with the same error about the key being invalid.

[Azusa]

Does anybody know how to generate key for wavesurfer 3000？
It‘s based on WinCE 7,different to normal x86.

[hpw]

This is on X-Stream version 8.4.1.4 (same on 8.1.2.0) on a Windows XP / 32-bit WP7300A, which as far as I know is the last that supports Windows XP, and 32-bit support ended shortly after.

Do you altered some releases to false as 6.4.1.4 for W2K SP4, while there is IMHO no 8.4.1.4  or I am wrong 

While there is no such 8.4.1.4 to download 
Hp

[Azusa]

https://1drv.ms/u/s!AkhYvp-r_jl5jUmbsT1Q8quH-qY9?e=nhKmp8
8.4.1.4 32bit here.
The last version for XP.
And the last version of 32bit is 8.6.2.10,you can download it on lecroy's website at model wavesurfer10.
but It's for win7 only.

[Azusa]

Old models are limited.Most of TDME is only allow decode and measurement.So they are the same with old options.
Qscape is unavailable.and all three phase power options are only for 8ch HDO or newer.

[Azusa]

When I install 32bit 8.4.1.4/8.6.2.10 version on WaveRunner 8404.It has new onetouch function.
It‘s a large improvement of human–computer interaction.It can do a lot of thing by slide makes use easily.
So,Does anyone tried to hack the configmgr.dll to make it possible on older models?

[hpw]

When I install 32bit 8.4.1.4/8.6.2.10 version on WaveRunner 8404.....
So,Does anyone tried to hack the configmgr.dll to make it possible on older models?

Does this means, 8.4.1.4 is not for the older models as WM8000, SDA6000 as DDA5000 series by default?

[Azusa]

When I install 32bit 8.4.1.4/8.6.2.10 version on WaveRunner 8404.....
So,Does anyone tried to hack the configmgr.dll to make it possible on older models?

Does this means, 8.4.1.4 is not for the older models as WM8000, SDA6000 as DDA5000 series by default?

The 32bit version higher than 8.1.2.0 is for wavesurfer10 but reserved support for old WM/WP/WR/WS.
and it supported other newer models like Zi,HDO,WR8000 even they are 64bit by default.
8.4.1.4 32bit can run on old WM/WP/WR/WS.but without onetouch fuction and most of new options are limited.

[hpw]

The 32bit version higher than 8.1.2.0 is for wavesurfer10 but reserved support for old WM/WP/WR/WS.
and it supported other newer models like Zi,HDO,WR8000 even they are 64bit by default.
8.4.1.4 32bit can run on old WM/WP/WR/WS.but without onetouch fuction and most of new options are limited.

OK,

as long the 8.4.1.4 deals with existing options and less bugs. Often have an automatic restart of the 8.1.2.0 as in addition touch panel working once than later on as dead or only partial..

Hp

[darkstar49]

OK,

as long the 8.4.1.4 deals with existing options and less bugs. Often have an automatic restart of the 8.1.2.0 as in addition touch panel working once than later on as dead or only partial..

Hp

better behaviour with 8.4 than 8.1 with the touchscreen ?? (I've had issues with 8.1 and W7 recently... very strange, had to launch LecTouchScreenCtrl.exe manually after the DSO software  )

[darkstar49]

I observed the same with flags 80 options. Looking at the X-Stream 7.9.0.1 options.cfg, it has no 0x08 or 0x80 options listed, so I guess this was stored as two 3-bit digits (0-7) at some point, causing both 0x08 and 0x80 to be interpreted as 0. I noticed that the license generation swaps bytes in the scope ID if the mask is >= 0x40, and tried any other permutation of scope ID bytes with mask 0x8, but none of them was accepted by the scope. Since the 0x08 and 0x80 options started appearing around the same time as the change to a new key generation scheme, I'm guessing the scope won't accept these options with the old key format as is currently implemented in the key gen.

No need to reinvent the wheel. Look at the options list here and use those flags/bitmasks.

0x80 support existed, but not public... My Mac had to be replaced 2 times within 6 months, and cherry on the cake, my multi-TB TimeMachine backups have become corrupt 
I'll check if I can find something back.

[sprit]

Hello everyone, have a nice day.


I have a WS424 scope that is giving me the error "No hardware Detected- Not authorized to run on this system - something like 5c16d-84884...."

This behavior occurs after I read data from DS2433. In the process I accidentally erased that chip. currently I have a backup copy of eeprom but don't know how to write back. i use arduino when doing it. I don't have a 1-wire ds9097 programming circuit. Can anyone help me, thanks for your help.
Sincerely,
JingFeng

[Nx-1997]

This worked for me on windows 10. I used an Arduino Nano.

https://github.com/meawoppl/eepromTool-ds2433

[mickab]

OK,

as long the 8.4.1.4 deals with existing options and less bugs. Often have an automatic restart of the 8.1.2.0 as in addition touch panel working once than later on as dead or only partial..

Hp

better behaviour with 8.4 than 8.1 with the touchscreen ?? (I've had issues with 8.1 and W7 recently... very strange, had to launch LecTouchScreenCtrl.exe manually after the DSO software  )

I have some stability issue with 8.4.1.4 (Hard reset after ~2min).

8.6.2.10 works fine for the Waverunner 64Xi-A-N but I'm not able to decode with list.py the option.cfg (no problem to decode options on 8.1.2.0)
Did you patch the existing code to decode the options available on 9.7.0.3 @darkstar49 & @tv84?

The error is :

Code: [Select]

C:\PythonScript>python list.py options.cfg
Traceback (most recent call last):
  File "list.py", line 8, in <module>
    db = lec.db.fromfile(argv[1])
  File "C:\PythonScript\lec\db.py", line 299, in fromfile
    return LicDB(LicReader(fname))
  File "C:\PythonScript\lec\db.py", line 35, in __init__
    DecryptFile(hfi, hfo)
  File "C:\PythonScript\lec\db.py", line 18, in DecryptFile
    hfo.write(decrypt(hfi.read(8)))
  File "C:\PythonScript\lec\crypto.py", line 20, in decrypt
    return revd(cipher.decrypt(revd(blk)))
  File "C:\PythonScript\lec\crypto.py", line 16, in revd
    return pack(">LL", *unpack("<LL", blk))
struct.error: unpack requires a string argument of length 8

[wysp2023]

OK,

as long the 8.4.1.4 deals with existing options and less bugs. Often have an automatic restart of the 8.1.2.0 as in addition touch panel working once than later on as dead or only partial..

Hp

better behaviour with 8.4 than 8.1 with the touchscreen ?? (I've had issues with 8.1 and W7 recently... very strange, had to launch LecTouchScreenCtrl.exe manually after the DSO software  )

I have some stability issue with 8.4.1.4 (Hard reset after ~2min).

8.6.2.10 works fine for the Waverunner 64Xi-A-N but I'm not able to decode with list.py the option.cfg (no problem to decode options on 8.1.2.0)
Did you patch the existing code to decode the options available on 9.7.0.3 @darkstar49 & @tv84?

The error is :

Code: [Select]

C:\PythonScript>python list.py options.cfg
Traceback (most recent call last):
  File "list.py", line 8, in <module>
    db = lec.db.fromfile(argv[1])
  File "C:\PythonScript\lec\db.py", line 299, in fromfile
    return LicDB(LicReader(fname))
  File "C:\PythonScript\lec\db.py", line 35, in __init__
    DecryptFile(hfi, hfo)
  File "C:\PythonScript\lec\db.py", line 18, in DecryptFile
    hfo.write(decrypt(hfi.read(8)))
  File "C:\PythonScript\lec\crypto.py", line 20, in decrypt
    return revd(cipher.decrypt(revd(blk)))
  File "C:\PythonScript\lec\crypto.py", line 16, in revd
    return pack(">LL", *unpack("<LL", blk))
struct.error: unpack requires a string argument of length 8

Changed key and data arrangement, requiring new key and data storage methods。