Has anybody tested the zoom issue that Dave experienced on older firmware? Maybe it was something that was accidentally introduced after the firmware upgrade.
Whats your opinion over the cursor time function, is or not a bug ?
Exist a new update over the 01.00.05 ?
John
Second if I don't want that many I can select the End Frame (Can be anything from 1 to maximum)
For existing DS2000 owners this is found under Utility --> Record --> End Frame.
Frames can be captured by time interval , captured on trigger or captured an a "mask" test fail.
Frames can be time date stamped and zoomed.
You can also "Analyse" the captured waveforms for "Error" frames by , after capture , selecting , a template from a frame , selecting a % value for error and running analyse. Or you can create a "mask" .
Hi - I'm the "culprit" behind the firware given to Dave. I also work for Emona Instruments who are the Rigol Distributors in Australia.
I'm posting here to clarify the issues with the firmware given to Dave. This was (As per what Drieg wrote) actually an engineering release not a public release. As such it was not fully tested . It was a release specifically given to me to show corrected XY display to a University here and there was a very short timeframe so it may have been rushed.
At the time I was unaware of it being an engineering release so passed it on to Dave with the introduced bug of non functional zoom in record mode. I have a new engineering release that fixes this but am waiting on an answer from Rigol on when we expect a public release. I'll post this information here. This was my mistake - Public release firmware is more thoroughly tested. (And yes it could be posted better)
While I'm here a couple of answers to questions that came up on the record mode .
This segments the memory.
Yes you can select the number of segments you want. This is done in 2 ways.
First you can change record length.
For example if I change record length to 14k I can record up to 8128 frames 140k 508 etc.
For existing DS2000 users this is found under Acquire menu --> MemDepth
(Note : My unit has the extended memory depth option so the exact numbers might differ if it is not installed)
Second if I don't want that many I can select the End Frame (Can be anything from 1 to maximum)
For existing DS2000 owners this is found under Utility --> Record --> End Frame.
Frames can be captured by time interval , captured on trigger or captured an a "mask" test fail.
Frames can be time date stamped and zoomed.
You can also "Analyse" the captured waveforms for "Error" frames by , after capture , selecting , a template from a frame , selecting a % value for error and running analyse. Or you can create a "mask" .
If anyone has any questions on the DS2000's or other Rigol products please feel free to ask me. I will try to keep any sales stuff out of it.
...then the current firmware will work fine prior to an update being available .
...then the current firmware will work fine prior to an update being available .Hi John,
Any idea if the ability to save/recall recorded frames is something that Rigol is planning to implement in the future? Currently the option is greyed out ... <snip> Since you can do post-processing (measurements, bus decoding, etc) on running frames, it seems like it would be a wasted opportunity (instead of a great feature) on Rigol's part not to allow the possibility to reload a waveform you recorded last week and check further measurements, etc. on it.
Thanks, Mark
Hi Mark - I'll check with Rigol if they have future funtionality improvements for the record mode and let you know.
John
<snip>
I've just ordered my Rigol DS2072 and will be expecting to arrive next Monday.
Much obliged,
Tim
@tlu: I too just placed an order! I noted earlier that you're in the US, and I responded to your group-order poll. I was a bit on the fence then, and wasn't sure how the group purchase would work. Recently I found Tequipment.net would give me a 5% .edu discount, and so I purchased through them. It is possible for individuals to get a discount, if you qualify by some means, and I hope things worked out for you.
I'm very excited too! And, we are all looking forward to trying @marmad's software!
Hi Mark - At this stage there are no immediate plans to add this functionallity (Save/Recall recorded frames) .
This is not to say it won't be added in the future.
John
That certainly sounds like the best way Dave but don't you think the Pass/Fail could also work?
I imagine that on a low end DSO that's going to run into the same capture rate issue??
BTW Dave can you setup a standardized test on a video that anybody with a DSO and a arb generator could use to test their scope? It would give all of us great data to publish in the videos forum thread and since you have several dso we could see how our cheapies stack up in an apples to apples comparison of wfcr.
And yes, as you could guess, I'm pretty fond of the Agilent scopes just because of their high capture rates independent of the mode you're running the scope in, plus that you don't have to think about record length/memory depth.
And yes, as you could guess, I'm pretty fond of the Agilent scopes just because of their high capture rates independent of the mode you're running the scope in, plus that you don't have to think about record length/memory depth.
I'm not exactly sure what you're saying here, but if you're implying that the Agilent X series waveform capture rates don't vary greatly with the timebase scale setting and other parameters - like every other DSO - then that is incorrect.
It would be interesting if somebody could produce a table corresponding to the Rigol example above, with additional columns for number of channels, decoding and so on. I have the intention to produce such a table for a DSO3000-series scope later this week.
If you can't get the help button method to work the first time, keep trying, it is a bit tricky to get the timing of the button press right, just after the power up.
It would be interesting if somebody could produce a table corresponding to the Rigol example above, with additional columns for number of channels, decoding and so on. I have the intention to produce such a table for a DSO3000-series scope later this week.Since I produced the table you're referring to, I'd be happy to create another one with channels, decoding, etc. enabled - but I'm currently travelling so I can't do it for 3 weeks. I did do a little testing when I made the original table, and I remember that some additional settings DID affect the rate - and others did not.
I might point out that the Agilent document which lists the update rates for the 2000X, 3000X, etc. notes: