tv84 - great work!
How did you do it!?!
Here are fully decrypted release notes.
So the used 'key' doesn't seem to be any password/passphrase or other readable string, but rather a cryptographic nonce (except it has been used at least twice!)
I superficially looked update.
Result:
- No new functions, only bugfixed
- function, that determines the version of the board, is complete rewritten.
- No any changes on resoures (help, menu, images, etc)
I'm guessing that encryption was done by a manager, not an engineer.
Nothing major fixed or changed, probably not worth installing.
But ... somebody said "Pluses" was changed to "Pulses".
The release notes for v00.04.04.03.02 have vanished from the file, I wonder why?
I also wonder why anybody would use such a weird/rubbish encryption? A zip file with password would be much easier/universal/uncrackable.
Something else has been improved. My unit had a slight offset between channels and channel one was ever so slightly noisy when engaging the 20 MHz filter. After the update, even prior to recalibration that has improved a lot.
QuoteI'm guessing that encryption was done by a manager, not an engineer.I'm guessing that all Rigol encryption always was done by a manager, not an engineer.QuoteNothing major fixed or changed, probably not worth installing.And, in addition, release note does not fully correspond to the real changes.
I will further analyze the firmware, but I will not use it to my device yet. I will wait revoked from other enthusiasts.QuoteBut ... somebody said "Pluses" was changed to "Pulses".
1) String Pluses/Pulses - not in resources.
2) i see in firmware:
P4_rw:401FA8C4 aDuty_0 DCB "+Duty",0
P4_rw:401FA8CA DCB 0
P4_rw:401FA8CB DCB 0
P4_rw:401FA8CC aDuty DCB "-Duty",0
P4_rw:401FA8D2 DCB 0
P4_rw:401FA8D3 DCB 0
P4_rw:401FA8D4 aPluses DCB "+Pluses",0
P4_rw:401FA8DC aPluses_0 DCB "-Pluses",0
P4_rw:401FA8E4 aEdges DCB "+Edges",0
P4_rw:401FA8EB DCB 0
P4_rw:401FA8EC aEdges_0 DCB "-Edges",0
I also wonder why anybody would use such a weird/rubbish encryption? A zip file with password would be much easier/universal/uncrackable.
When it was brand new, out of the box, all the traces were on the same zero ground level.
After the first recalibration, I remember being somehow disappointed about the traces not being on the same zero line. Since then, I never seen that factory default zero line, with all traces on top on each other, and perfectly aligned.
Are you sure it is not just a lucky recalibration? If you recalibrate the scope again, would you still obtain the same result? How long did you let the scope to heat up before recalibration, please?
When it was brand new, out of the box, all the traces were on the same zero ground level.
After the first recalibration, I remember being somehow disappointed about the traces not being on the same zero line. Since then, I never seen that factory default zero line, with all traces on top on each other, and perfectly aligned.
Are you sure it is not just a lucky recalibration? If you recalibrate the scope again, would you still obtain the same result? How long did you let the scope to heat up before recalibration, please?
I can confirm that after the update (and an auto calibration -- needed three attempts until it passed), the traces are exactly centered on the trace markers. Have never seen that before on my DS1000Z since I purchased it some four years ago. They were always riding slightly above the markers. Seems like Rigol finally took care of one of the "minor annoyances" that could still make a difference...
Like others have indicated, I think I'll wait on updating mine. From what little information there is in the release notes, I don't see anything worth updating for and risking it somehow interfering with the community firmware efforts.
$ grep -i footer SparrowAPP.4435.matches.txt
f sign.bytes.sym.processFooter_0 500 @ 0x400644a0
f sign.bytes.sym.loadFooter_0 192 @ 0x40064770
f sign.bytes.sym.footer_magic_0 448 @ 0x400abfbc
@tv84: OK, I'll buy your 50 cents. I do like the possibility of fixing the zero offsets. Thanks for your input, especially regarding the GEL and bootloader.
@tv84: OK, I'll buy your 50 cents. I do like the possibility of fixing the zero offsets. Thanks for your input, especially regarding the GEL and bootloader.
While you all wait for konnor to update his new plugin version with the "pluses" corrected, I'll ask janekivi to correct them in the official 00.04.04.03.05 version if that's really important.
@tv84: OK, I'll buy your 50 cents. I do like the possibility of fixing the zero offsets. Thanks for your input, especially regarding the GEL and bootloader.
While you all wait for konnor to update his new plugin version with the "pluses" corrected, I'll ask janekivi to correct them in the official 00.04.04.03.05 version if that's really important.
The misspelling is really pissing me off. I guess we all appreciate if you guys make a fixed firmware.
@tv84: OK, I'll buy your 50 cents. I do like the possibility of fixing the zero offsets. Thanks for your input, especially regarding the GEL and bootloader.
While you all wait for konnor to update his new plugin version with the "pluses" corrected, I'll ask janekivi to correct them in the official 00.04.04.03.05 version if that's really important.
I can make this happen.
Did only Pluses.
DS1000Z_00_04_04_03_05.zip