With a web based interface OTOH you only need a standard web browser and it should even be possible to use a smartphone or tablet to do screen captures.
Hi,
The web interface lets you capture screenshots and transfer data easily.
Michael
Note: new User Manual v06 posted.
https://www.rohde-schwarz.com/us/manual/rtb2000/
Minor changes from what I can tell. I found the following:
* Quick Access
* Auto scale in probe menu
* Zoom icon
* Features in segment table (average, envelop, overlay)
* FFT screen seems to have a slightly differen tlayout at the bottm (they changed the pic)
I found another bug, when i was working with UART (RTB configured for 9 data bits and Terminal configured for 8 data bits + parity odd). The display sometimes doesnt clear correctly, resulting in showing the current AND the last waveform. I love the scope, but things like this are annoying, thinking of the price i paid. I use the current firmware V02.101. To reproduce the error hold down a key in the Terminal (e.g. Putty) resulting in continuous triggering, then press a second key on the keyboard. Maybe this error can be reproduced with other settings, but that was what i was working on:
Hi robotrovsky - I tried to PM you back, but it says your inbox is full.
I found another bug, when i was working with UART (RTB configured for 9 data bits and Terminal configured for 8 data bits + parity odd). The display sometimes doesnt clear correctly, resulting in showing the current AND the last waveform. I love the scope, but things like this are annoying, thinking of the price i paid. I use the current firmware V02.101. To reproduce the error hold down a key in the Terminal (e.g. Putty) resulting in continuous triggering, then press a second key on the keyboard. Maybe this error can be reproduced with other settings, but that was what i was working on:Hi robotrovsky - I tried to PM you back, but it says your inbox is full. This doesn't appear to be a bug as the signal has different pulse widths and with an edge trigger you could see both of those appear on the display at the same time (our update rate is fast enough that we have to plot lots of waveforms at one time). Do you still see this issue if you use an advanced trigger like?
• trigger on start frame of uart
• trigger on pulse width
• use trigger hold off time
-Rich
I found another bug, when i was working with UART (RTB configured for 9 data bits and Terminal configured for 8 data bits + parity odd). The display sometimes doesnt clear correctly, resulting in showing the current AND the last waveform. I love the scope, but things like this are annoying, thinking of the price i paid. I use the current firmware V02.101. To reproduce the error hold down a key in the Terminal (e.g. Putty) resulting in continuous triggering, then press a second key on the keyboard. Maybe this error can be reproduced with other settings, but that was what i was working on:Hi robotrovsky - I tried to PM you back, but it says your inbox is full. This doesn't appear to be a bug as the signal has different pulse widths and with an edge trigger you could see both of those appear on the display at the same time (our update rate is fast enough that we have to plot lots of waveforms at one time). Do you still see this issue if you use an advanced trigger like?
• trigger on start frame of uart
• trigger on pulse width
• use trigger hold off time
-Rich
LOL. It's a feature.. You should use complicated trigger that will ensure retrigger slowdown, so our poor display engine will have time only to paint waveforms once..
With do all respect, how is that not a bug? You cannot show ANYTHING except last trigger event. Display persistence have no place here.
What is this, an artsy fartsy graphic tablet or a scope. From a premium manufacturer. For a premium price.
No wait, but you can paint on screen with your fingers... That's important.
Rigol can do it, Siglent can do it. For price that is less than one software option on R/S.
It's year and a half now since RTB2000 was released..
Get a grip. And that buggy, hipstery platform is used for 3000 and 4000. That cost a lots of money. Lots of money.
Bug fixes would really need to me a bit more aggressive (faster) at least until you weed out basic platform functions.
R&S was one of the legendary companies for many years. Good solid stuff. Expensive, but professional and worth every penny. Now, not so much, at least at this scope range.
Shame really...
I really hope you keep up with the reputation.
When big guys do it, it's not a bug, or not their fault...
I think that is exactly what the scope should do. If there are multiple triggers within one frame-time of the screen it should show all the events within this time, no? I thought that is what intensity grading is based on. So if you have two qualified trigger events within 16ms (assuming 60Hz LCD refresh rate; I know this is simplified ) then I would like to see both, no? Or should one just be thrown away? Do i miss something?