Products > Test Equipment

New Rigol DS7000

<< < (40/72) > >>

EEVblog:

--- Quote from: seppeltronics on October 13, 2018, 07:31:05 pm ---I'm buying an Oscilloscope next week and think I get a Rigol MSO7014. What do you think about the unit? The discussion was that my colleague prefers scopes that have a dedicated knob-set for each channel, so I came up with the MSO7014. The other option would be the R&S RTB2K-104M.
Any comments/recommendations?

--- End quote ---

If the company is paying, and money isn't really an issue, get the R&S, it's a much nicer and more capable scope with the 10bit ADC. Little contest there really.

oliv3r:

--- Quote from: tv84 on August 21, 2018, 09:40:58 am ---The v00.01.01.07.01 .GEL file is a .TAR archive and can be opened with the 7-zip decompressor.

Inside there are the following files:
<snip>
fw4linux.sh and fw4uboot.sh are 2 AES-CBC encrypted shell scripts
<snip>

--- End quote ---

I'm curious, I'm looking at both shell scripts, but the first character seems to be off in both. In fw4linux.sh the first character seems to be an '=' but I'm quite guessing it should be a '#' to make the first line a comment. I can't seem to spot what caused the error, it's not a simple bit-flip ..
as for fw4uboot.sh, it seems to be missing the entire first character ...

Can you double check if this is indeed what went wrong?

Finally, I think the shebang went missing on purpose; they probably are calling the script as `sh fw4linux.sh` somewhere so the executability likely won't matter ...

tv84:

--- Quote from: oliv3r on December 23, 2018, 07:29:16 pm ---
--- Quote from: tv84 on August 21, 2018, 09:40:58 am ---The v00.01.01.07.01 .GEL file is a .TAR archive and can be opened with the 7-zip decompressor.

Inside there are the following files:
<snip>
fw4linux.sh and fw4uboot.sh are 2 AES-CBC encrypted shell scripts
<snip>

--- End quote ---

I'm curious, I'm looking at both shell scripts, but the first character seems to be off in both. In fw4linux.sh the first character seems to be an '=' but I'm quite guessing it should be a '#' to make the first line a comment. I can't seem to spot what caused the error, it's not a simple bit-flip ..
as for fw4uboot.sh, it seems to be missing the entire first character ...

Can you double check if this is indeed what went wrong?

Finally, I think the shebang went missing on purpose; they probably are calling the script as `sh fw4linux.sh` somewhere so the executability likely won't matter ...

--- End quote ---

The first 4 bytes are (what I think is) a CRC32, after decryption! I didn't bother to verify but I can if needed.

So, I cutted those 4 bytes. (i think all of them)

I assume that if that is important maybe they, when removing the CRC, replace it with the proper #.

I have the AES key in the 5000 thread, so you can do the decryption yourself to validate.

oliv3r:

--- Quote from: tv84 on December 23, 2018, 08:07:03 pm ---
--- Quote from: oliv3r on December 23, 2018, 07:29:16 pm ---
--- Quote from: tv84 on August 21, 2018, 09:40:58 am ---The v00.01.01.07.01 .GEL file is a .TAR archive and can be opened with the 7-zip decompressor.

Inside there are the following files:
<snip>
fw4linux.sh and fw4uboot.sh are 2 AES-CBC encrypted shell scripts
<snip>

--- End quote ---

I'm curious, I'm looking at both shell scripts, but the first character seems to be off in both. In fw4linux.sh the first character seems to be an '=' but I'm quite guessing it should be a '#' to make the first line a comment. I can't seem to spot what caused the error, it's not a simple bit-flip ..
as for fw4uboot.sh, it seems to be missing the entire first character ...

Can you double check if this is indeed what went wrong?

Finally, I think the shebang went missing on purpose; they probably are calling the script as `sh fw4linux.sh` somewhere so the executability likely won't matter ...

--- End quote ---

The first 4 bytes are (what I think is) a CRC32, after decryption! I didn't bother to verify but I can if needed.

So, I cutted those 4 bytes. (i think all of them)

I assume that if that is important maybe they, when removing the CRC, replace it with the proper #.

I have the AES key in the 5000 thread, so you can do the decryption yourself to validate.

--- End quote ---

I don't have a scope yet, so I'll see if I can run the binary in qemu (I have it from the fw update). But if you manually did some cutting, then that can explain things, or rather, maybe they muked up the en/decryption of the file and it's not exactly 32 bits (I would not be suprised there).

But thanks, that explains it!

rowifi:
I've recently tried this scope.
It's full of bugs, regularly locks up and hardly worthy as a serious instrument at this time.
1. Using the search button regularly causes a lock up
2. Memory waveform recall.. lucky if it does.. partial recall, sometimes none, sometimes a bit, occasionally most.
3. Cursors that have been moved offscreen loose their position when the other cursor is moved.
4. Cursors don't track the math trace properly
5. Trigger rearm time seemed to be 60ms,  no hope of storing fast segments into memory
6. Plugging in a probe generated a whole load of screen data/noise killing the current view.
7.. There were others.

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