I've been away from these fights...
Has anyone tried the "EJ" and "SENT" options on the SDS2000X+?
Software has it like this:
EJ - SDS-5000X-EJ - SDS_2000XP_EJ - SDS6000Pro-EJ
Also looks like a new file options_ej_times.txt showed up in the 1.3.9R4 firmware:
$ ls -la options_*
------xr-x 1 user users 2 april 10 2021 options_1553b_times.txt
---------x 1 user users 2 april 10 2021 options_awg_times.txt
------x--x 1 user users 2 april 10 2021 options_canfd_times.txt
-rw------- 1 user users 2 sep. 11 13:14 options_ej_times.txt
------x--x 1 user users 2 april 10 2021 options_flx_times.txt
------xr-x 1 user users 2 april 10 2021 options_i2s_times.txt
---x------ 1 user users 2 april 10 2021 options_manc_times.txt
-------r-x 1 user users 2 april 10 2021 options_mso_times.txt
---------x 1 user users 2 april 10 2021 options_pa_times.txt
---x------ 1 user users 2 april 10 2021 options_sent_times.txt
-------r-x 1 user users 2 april 10 2021 options_wifi_times.txt
I already have SENT enabled, but never had reason to use it.
(I believe) I've generated the code for EJ using the Python script, but there is no option to install it (1.3.9R6)
No joy.
Tried the format below, and rebooted afterwards. No extra option shown enabled, and nothing extra menu under Analysis.
LCISL EJ,wwww-xxxx-yyyy-zzzz
Also tried variations of case, spacing and no dashes.
LCISL EJ,wwww-xxxx-yyyy-zzzz
Why the dashes? It should be no dashes but others may confirm.
The script produces the codes with dashes.
I can’t recall when I did the others originally, but I think I typed them onto the screen, so dashes are not used anyway, but I have tried without dashes via command too.
The script produces the codes with dashes.
I can’t recall when I did the others originally, but I think I typed them onto the screen, so dashes are not used anyway, but I have tried without dashes via command too.
And what is your FW version, at this moment?
1.3.9R6
In your NSP_system_info.xml is there any reference to a "Dynamic Key"?
(I believe) I've generated the code for EJ using the Python script, but there is no option to install it (1.3.9R6)
Because there is no eyediagram/jitter analyzis option for the 2000XP in real, this isn´t a hidden easteregg feature..
EJ - SDS-5000X-EJ - SDS_2000XP_EJ - SDS6000Pro-EJ
I think, it´s only "there" because all the three scopetypes are using more or less the same software.
A few months before, we got the same problem on a lecroy if I remember it right.
Installing all "theoretical possible" licenses but won´t work correctly.
I think it was on a WS3000 scope.
That worked a lot better :-)
/usr/bin/siglent/firmdata0 # cat NSP_system_info.xml
<?xml version="1.0" encoding="UTF-8"?>
<nsp_system_info_root>
<device>
<system_information>
<serial_number>
<chip>XXXXXXXXXXXXXXXXX</chip> (S/N removed)
</serial_number>
</system_information>
</device>
<Device><Mac>74:5b:c5:20:7b:e2</Mac></Device></nsp_system_info_root>
I think, it´s only "there" because all the three scopetypes are using more or less the same software.
Martin, understand but this isn't the same "only there".
There is the explicit license designation "SDS_2000XP_EJ" in there and this only happens when there is a real reason. It's not only "EJ".
Of course, can be in beta, may need a flag to activate, not yet releasable, etc. But it's explicitly inside.
It's not like a "1000M" reference that we are trying to make it work in a SDS2k+.
The eye diagram feature seems to be guarded by a lot of checks everywhere for product type, so enabling the license might not have any effect.
Not sure if this is just because they want us to buy the most expensive model, or if this feature requires some hardware or fpga logic not in the SDS2000X+. Could also be that it's unfinished like tv84 says.
Well, trying the key did something, though permissions are different to others:
---x------ 1 root root 20 Nov 15 2020 options_canfd_cfg.bin
---x------ 1 root root 20 Nov 15 2020 options_canfd_license.txt
-rw------- 1 root root 20 Feb 20 11:59 options_ej_cfg.bin
-rw------- 1 root root 20 Feb 20 11:59 options_ej_license.txt
---x------ 1 root root 20 Nov 15 2020 options_flx_cfg.bin
---x------ 1 root root 20 Nov 15 2020 options_flx_license.txt
---x------ 1 root root 20 Nov 15 2020 options_i2s_cfg.bin
Well, trying the key did something, though permissions are different to others:
No problem with the permissions. Well, that somewhat confirms that my suspicion was right. Let's all try to better understand the environment...
OK,I can confirm the SCPI command+key is accepted on SDS5k. No additional menus appear. However at the risk of misleading you I noticed the trigger setting on "pattern" after the reboot. Which I didn't use before.
FW; 095R3