Products > Test Equipment

New Rigol DS7000

<< < (62/72) > >>

drhex:
I created the patch from a diff based on the 01.01.02.00.06 version. The symbols to be patched are the same in 00.01.02.00.06.
bspatch didn't complain when applying the 01 patch to the 00 version (think it would only complain if the target file is too small). Bit of a pity that patchfinder.sh doesn't display the actual offsets in the file - may figure that out at some point, I just searched with a hex editor and patched accordingly.
My scope came with the 01 version, too - so your original patch was very handy! Don't think the last change is an issue as such as there are no hard addresses in there. Worked without any change for me (but I haven't really looked for side effects).

wat:
hi drhex,
I had the same problem of the persistance of the settings after reboot,
this solves it: https://www.eevblog.com/forum/testgear/new-rigol-ds7000/msg1863522/#msg1863522


--- Quote from: drhex on May 02, 2021, 12:53:23 am ---And managed to brick the scope. Somehow it didn't persist settings through reboot, so tried to install the latest from the website (v00.01.02.00.06), no change. The patched appEntry from v01.01.02.00.06 doesn't work with that, patching it with the same patch bricks the scope - ssh doesn't come up when it gets stuck at appEntry, at least for me. Now I can't reinstall from the bootloader after pressing "single" on power on, says the package is invalid? Doesn't seem to use the USB really, at least not for an extended time before complaining about the package. Does anybody have an idea?

--- End quote ---

drhex:
Thanks for mentioning, I did work that out in the end - I did expect this setting to influence scope channel setup but not basics like the IP configuration. Seems it resets EVERYTHING.

normi:

--- Quote from: drhex on May 09, 2021, 11:42:22 am ---Thanks for mentioning, I did work that out in the end - I did expect this setting to influence scope channel setup but not basics like the IP configuration. Seems it resets EVERYTHING.

--- End quote ---

The default setting looks like its there to ensure that all scopes will have a standard setting, so if you report an issue support can be sure that they are comparing a scope with a known configuration. The missing feature is to allow you to add your custom setup as an option to boot the scope. You can manually  store and load your settings though, sometimes it takes a while to get all the triggering correct for a decode so I have to store the config to prevent having to repeat process.

normi:

--- Quote from: drhex on May 03, 2021, 05:52:27 pm --- Worked without any change for me (but I haven't really looked for side effects).

--- End quote ---

Did you see jitter analysis enabled under measure > Analyze

Navigation

[0] Message Index

[#] Next page

[*] Previous page

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