Where it appears they've chosen to use an Ext trig for CS, right ?
If so, it's a feature that can be added in FW for any DSO with a Ext trig in.
If it decodes whatever's in memory then no FW update is needed. Trigger using CS and decode the captured CLOCK and MOSI data.
Most SPI data is bidirectional though. Normally you want to get data back from your slaves. Very few things will be purely master->slave with no reply. SPI with two channels isn't very useful.
Anyone noticed the DVM option is free on registration of the scope? The FFT has phase as well as magnitude? (and can we have that on the 2000X series as well, please Mr Keysight?) The bode plot function on the wavegen equipped models? And the ADC is 2Gsps on the 100MHz versions, not 1GHz split 4 ways like on the hacked Rigols?
Really, it all depends on the price...
Oops.
Ok, an announcement finally came a little earlier
Nice, cut down 2000X series. Too bad no MSO capabilities.
If it's $650 as per the Rupee document then I don't think this will in any way dissuade those to buy the 1054Z. Memory depth looks low compared to the Rigol to me...
And that would be $650 for the educational model (limited to 50 MHz without upgrade option, and probably limited to customers in the educational market). I would assume around $1000 for the 70 MHz "regular" model.
You will be pleasantly surprised
You will be pleasantly surprised
Russian retailer's pricelist hints for possible US retail price of ~$800 for DSOX1102G (and ~$1750 from that retailer in Russia).
If it's $650 as per the Rupee document then I don't think this will in any way dissuade those to buy the 1054Z. Memory depth looks low compared to the Rigol to me...
And that would be $650 for the educational model (limited to 50 MHz without upgrade option, and probably limited to customers in the educational market). I would assume around $1000 for the 70 MHz "regular" model.
You will be pleasantly surprised
But even then there are better options out there. Buying a crippled Keysight is just paying for the badge but it gets you nowhere:
What was that about '
Scrap the toys?'
I was under the impression that all you have to do is to hit the Stop button on the InfiniiVision.
But the whole memory thing is not so important to me so I'm maybe the wrong person to discuss this.
Rather than stop, which leaves the last acquisition (with its memory halved from the ping-pong buffer) on the screen you press single and then it captures the next trigger with the full memory depth.
I was under the impression that all you have to do is to hit the Stop button on the InfiniiVision.
But the whole memory thing is not so important to me so I'm maybe the wrong person to discuss this.
Rather than stop, which leaves the last acquisition (with its memory halved from the ping-pong buffer) on the screen you press single and then it captures the next trigger with the full memory depth.
Yep, I actually did a quick video about this:
http://bit.ly/2bx0Jrr
I was under the impression that all you have to do is to hit the Stop button on the InfiniiVision.
But the whole memory thing is not so important to me so I'm maybe the wrong person to discuss this.
Rather than stop, which leaves the last acquisition (with its memory halved from the ping-pong buffer) on the screen you press single and then it captures the next trigger with the full memory depth.
Are you serious? The 'trace of interest' is gone if you do that!
That is the whole problem: You keep switching between single and continuous mode with this half baked memory solution. It is just too tedious and time consuming.
I was under the impression that all you have to do is to hit the Stop button on the InfiniiVision.
But the whole memory thing is not so important to me so I'm maybe the wrong person to discuss this.
Rather than stop, which leaves the last acquisition (with its memory halved from the ping-pong buffer) on the screen you press single and then it captures the next trigger with the full memory depth.
Yep, I actually did a quick video about this:
http://bit.ly/2bx0Jrr
What would be useful, especially for less frequent trigger events, is a "repeated single" mode, which would be the equivalent of pressing "single" after each trigger. Maybe press and hold the single button to activate this mode?
All that new scope and still multplexed cursor, zoom and vertical controls. Why does every new scope have to be run like a damn video game?
Why not spend a few extra dollars and give me individual controls?
I was under the impression that all you have to do is to hit the Stop button on the InfiniiVision.
But the whole memory thing is not so important to me so I'm maybe the wrong person to discuss this.
Rather than stop, which leaves the last acquisition (with its memory halved from the ping-pong buffer) on the screen you press single and then it captures the next trigger with the full memory depth.
Are you serious? The 'trace of interest' is gone if you do that!
That is the whole problem: You keep switching between single and continuous mode with this half baked memory solution. It is just too tedious and time consuming.
I'd rather have the faster update and processing in the background whilst it's taking another capture. Losing half my memory isn't such a big deal when I know that if I want the full memory I can just hit the single button or deliberately set up a single shot event.
Granted, in modern terms, the 4MS memory in the Megazoom IV is long in the tooth. But I've hardly ever wanted/needed more memory than the Keysight offers anyway, but I appreciate the responsiveness every time I used it.
And the ADC is 2Gsps on the 100MHz versions, not 1GHz split 4 ways like on the hacked Rigols?
2Gsps on both channel, It does not half when the 2nd channel is switched on.
They must be using the full 4Gsps capability of the ASIC. Nice.
Is there an estimated schedule, so we can expect a review/teardown video?
I was under the impression that all you have to do is to hit the Stop button on the InfiniiVision.
But the whole memory thing is not so important to me so I'm maybe the wrong person to discuss this.
Rather than stop, which leaves the last acquisition (with its memory halved from the ping-pong buffer) on the screen you press single and then it captures the next trigger with the full memory depth.
Are you serious? The 'trace of interest' is gone if you do that!
That is the whole problem: You keep switching between single and continuous mode with this half baked memory solution. It is just too tedious and time consuming.
I'd rather have the faster update and processing in the background whilst it's taking another capture. Losing half my memory isn't such a big deal when I know that if I want the full memory I can just hit the single button or deliberately set up a single shot event.
Granted, in modern terms, the 4MS memory in the Megazoom IV is long in the tooth. But I've hardly ever wanted/needed more memory than the Keysight offers anyway, but I appreciate the responsiveness every time I used it.
I own an Agilent DSO7104A and it is sitting on a shelve. Double buffering isn't a Keysight specific feature because most (all?) DSOs use double buffering but simply fit doube the memory it says on the badge (which sometimes doubles the number of segments in segmented recording). Granted I don't need deep memory all the time but if you need to jump through hoops and start pushing buttons before capturing each trace in order to use all the memory then something is wrong.
Is there an estimated schedule, so we can expect a review/teardown video?
I think the clue is in the title of this thread
I own an Agilent DSO7104A and it is sitting on a shelve. Double buffering isn't a Keysight specific feature because most (all?) DSOs use double buffering but simply fit doube the memory it says on the badge. Granted I don't need deep memory all the time but if you need to jump through hoops and start pushing buttons before capturing each trace in order to use all the memory then something is wrong.
Jumping through hoops like pushing the Single button instead of Stop?
If you are using the stop button then you are generally looking at a triggered repetitive signal, so it makes virtually no difference between pushing the Single button instead of the Stop button.
Is there an estimated schedule, so we can expect a review/teardown video?
I think the clue is in the title of this thread
A teaser will come sooner...
No. For many measurements you'll want to capture just one event. Like a UART message or certain signal. Usually this means pressing buttons on a generator, closing a switch, clicking a button in a GUI, etc. Having to also press a button on the oscilloscope to arm it just wastes time and adds extra room for error (or annoyance when putting the probe onto the test point also produces a trigger and you need to re-arm the scope once more). If you can let the oscilloscope stay in continuous trigger mode instead of single the scope does what it should do without needing manual arming and thus save time and work more comfortably.
Because your lightning-fast reaction time beats the Keysight's trigger system every time?
We've been here before. If its something happening frequently the realtime is nice and you press single to get a longer record, if its something rare but you still want the longer record press single. Some people get really worked up over their workflow and specific methods (the auto trigger timeout differences etc). I like using all sorts of scopes and appreciate the idea of providing as much memory as possible given the current configuration rather than synthetically limiting it to the worst case in all cases, it keeps marketing happy with a big headline specification but you're not missing out on anything.
No. For many measurements you'll want to capture just one event. Like a UART message or certain signal. Usually this means pressing buttons on a generator, closing a switch, clicking a button in a GUI, etc. Having to also press a button on the oscilloscope to arm it just wastes time and adds extra room for error (or annoyance when putting the probe onto the test point also produces a trigger and you need to re-arm the scope once more). If you can let the oscilloscope stay in continuous trigger mode instead of single the scope does what it should do without needing manual arming and thus save time and work more comfortably.
But in that case you STILL have to reach up to the scope and press the STOP button!
What's the difference between pressing the STOP button and the SINGLE button
when your signal is re-triggering all the time? Your argument seems to be almost entirely without merit.