| Products > Test Equipment |
| Functional comparison of R&S RTB2000, Siglent SDS2000X and Keysight DSOX1000 |
| << < (5/39) > >> |
| RBBVNL9:
Concerning the probe sensing… It’s an area where the SDS certainly has a plus over the RTB and DSOX (as I mention in the video). In my video and document, I just relied on the User Manual of the SDS, and an old 10x Tek P6105A 10x probe I happened to have in the lab (and which is correctly identified as a 10x probe by the SDS). I now tried a couple of resistor values. As far as I can see, the SDS interprets any resistance between 0Ω and 56kΩ as “10x”, and resistance between 82k to infinity as “1x”. So, it seems that there is no recognition for other attenuation values, as it is. No idea whether the hardware allows other detections (via a firmware upgrade) or not. |
| nctnico:
IMHO probe sensing is pretty much useless if you can't configure it for vendor specific probes. As soon as you connect a probe with vendor specific probe sensing (like 20x for example), it only gets in the way because the scope still thinks a 10x probe is connected. The R&S RTM3004 has several, easely accessible presets for the probe attenuation factor; I assume the RTB2004 is the same. |
| RBBVNL9:
--- Quote ---The R&S RTM3004 has several, easely accessible presets for the probe attenuation factor; I assume the RTB2004 is the same. --- End quote --- Looking at the RTM300 manual, the RTB2000 has the same general probe settings: 4 general presents (1:1, 1:10, 1:100 and 1:1000) a user setting (fully variable between 100μ to 10M (equals 10-4 ~ 107) (since FW02.300), and a V/A setting (where the attenuation units change to current). Of course, the RTB does not have the more advanced probe options the RTM has, like support for probes with integrated data memory for ID (serial number, production data, electrical characteristics) and memory for individual probe correction, access to additional metering electronics in the probe itself ('ProbeMeter'), and the configurable button on the probe head ('microbutton'), degaussing for current probes, and so on. All of these goodies require the R&S probe interface (recognisable by the six round electric contacts next to the BNC), which you find on the RTM3000, the RTA4000, and 'above'. |
| hj:
Hi Rudi, thanks for putting this series together, I really appreciate your work. Getting through all those detailed infos must be very time consuming. This is a really valuable contribution. I only own the 2104x+ and actually find the overall button layout quite intuitive. Almost all sub menu items are "buttonized". However, in the beginning I had my issues with the five so called "Menu" buttons from which only three are actually corresponding to a real "Menu..." entry (which should rather be renamed into "Settings" or "Setup" to be aligned with the Trigger "Setup" button). Why didn't they order the three top level "Menu..." buttons in the order of their appearance on the screen (Utility, Display, Aquire). I understand that they want to indicate AWG on/off state with an illuminated button but I really wished they made the "save/recall" button user assignable. And what's better than one user definable button? Right: two ;) In regards to the online documentation: I know that developing and maintaining a good and well integrated documentation is as much a challenging and expensive task as writing good software. If Siglent chose to cut corners here, we might have to accept that. In the end we buy this thing for its very good price/performance ratio. But Siglent could really improve on their online docs and make use of the touch screen by heavily hyperlinking the content. Why can't I jump from chapter 9 into the dedicated sections and back. And why do I actually have to go to chapter 9 and navigate from there? Even my car's online help allows me to touch a virtual dashboard bringing me to the corresponding content. I also miss a free search and a cross reference (index/glossary). I think, rendering HTML from a Word file just doesn't cut it anymore these days as there are better options available especially when this device has a builtin http server... BTW: Did you notice that there is no chapter 20 and that the 'Developer Options' are still called 'Debug' in the online docs;) (FW 1.3.9R6) Again thanks for putting this series up and for giving it such a clear and in depth structure. Let's hope your family grants you the time to produce all planed episodes;) That's going to become epic. Could it be that the white balance in your camera is a little on the warm side? Joachim |
| RBBVNL9:
@Joachim (and others), Thanks for the reactions and the various compliments. --- Quote ---Could it be that the white balance in your camera is a little on the warm side? --- End quote --- Ah yes, that is a good point ;-) I shot with a Nikon Z7 plus Atamos Ninja V and edited in Final Cut Pro, and normally speaking, that should leave one with quite some room for colour grading afterwards. But surprisingly, both colour temperature settings and colour grading wheels result in quite ugly results :-[ So, for the time being, I left it kinda reddish/warm. There are a couple of possible solutions: (1) get the paid upgrade of the Z7 to get RAW output (have to send it in to the Nikon distributor for that) and get the Ninja upgraded dor ProRes RAW. Should give me much more leeway for colour grading. Takes time and money. (2) Get studio lights so I am less dependent on natural / room light. Probably the better option. Already bought those but my son confiscated them and and took them to his house ;-) At some point in time, I will try to improve the video (colour) but now I will first give priority to the videos themselves ;-) |
| Navigation |
| Message Index |
| Next page |
| Previous page |