Author Topic: 4 channel Keysight 1000x series scope  (Read 18838 times)

0 Members and 1 Guest are viewing this topic.

Offline martinot

  • Regular Contributor
  • *
  • Posts: 81
  • Country: se
Re: 4 channel Keysight 1000x series scope
« Reply #125 on: July 10, 2020, 10:54:07 pm »
You are missing one very important point, the idea is not to capture all 50000 packets with a scope to do an analysis.  A logic analyzer is better suited for such capture and analysis.  The point I was trying to make is that by triggering 50000 times, it can capture a specific event and the Siglent will probably miss it.  That is the whole point of using the protocol analyzer on the scopes.  My SPI test setup has a user button enabled that sends a specific packet 0x3F when pressed, and 0x37 when not pressed.  The KS gets it almost on every click, but the siglent misses a lot of them, the SDS1104X-E that I tested missed like 80-90% of them.  Even the GDS-1054B can trigger on 90-100% of the time, the siglent is very slow handling serial decoding and triggering.

When scope is armed and waiting for trigger (in Normal not Auto mode), it will trigger instantaneously. It is literally waiting to pull the trigger. It is retriggering that is questionable, once it triggers and finishes the sweep, it will take time to rearm. That rearm time is very fast on Keysight, also very fast on new Rigols , and a bit slower on Siglent. And because of it, Keysight might trigger on every packet and Siglent might not be ready for next one and miss it...

Yes, that looks like a reasonable explanation.

Offline Bud

  • Super Contributor
  • ***
  • Posts: 4461
  • Country: ca
Re: 4 channel Keysight 1000x series scope
« Reply #126 on: November 11, 2020, 06:41:12 am »
Firmware for the DSOX1204x series is now posted on the Keysight website. As this scope runs linux it should be interesting to take a peak at.

Shouldn't be mission impossible to devise workarounds... ;)

The .ksx is a initrnamfs file which can be easily opened with 7zip decompressor.
There is a 128 byte sw-description.sig file.  Anyone knows how it is generated?  It is different on each install package (.ksx)

Sounds like a 1024-bit RSA signature to me. Must be generated using a private key at the factory and verified with the public key residing inside the scope during software setup.
Facebook-free life and Rigol-free shack.

Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo