new killer scope in town - a true game changer from R&S - RTB2002 & RTB2004

[Hydron]

Thanks Rich, sounds like it was worth the wait!
I look forward to having a play when it shows up on the R&S site.

[hwj-d]

Many thanks from me too.

By the way, a completely different question:
is it possible to upgrade from 100Mhz to 200Mhz and later from 200Mhz to 300Mhz, and how much does it cost?

[maginnovision]

Nice long list, thanks Rich!

Surprisingly loooooong list. 

Are you suggesting the upgrades and bug fixes are a bad thing or just surprised some companies try to do more than one bug fix every 6 months?

[tautech]

Nice long list, thanks Rich!

Surprisingly loooooong list. 

Are you suggesting the upgrades and bug fixes are a bad thing or just surprised some companies try to do more than one bug fix every 6 months?

Neither.

A certain member whom I quoted takes care to post in anything here about Siglent, I was just returning the favor.
We can all happily carry on along on EEVblog without the shite he has in his signature.

[Rich@RohdeScopesUSA]

By the way, a completely different question:
is it possible to upgrade from 100Mhz to 200Mhz and later from 200Mhz to 300Mhz, and how much does it cost?

It is. While the part numbers only exist to go from 70MHz to each of the higher steps, we’ll discount out the difference - you should just need to ping the place you purchased it from.

-Rich

[EEVblog]

Are you suggesting the upgrades and bug fixes are a bad thing or just surprised some companies try to do more than one bug fix every 6 months?
[/quote]
Neither.
A certain member whom I quoted takes care to post in anything here about Siglent, I was just returning the favor.
We can all happily carry on along on EEVblog without the shite he has in his signature.
[/quote]

And if your intention is to post in here just to be provocative then you will not be welcome here.

[kcbrown]

That's an impressive list.  Certainly justifies the amount of time it took. 


Sent from my iPhone using Tapatalk

[borjam]

That's an impressive list.  Certainly justifies the amount of time it took. 

That's something the new kids on the block (ie, Chinese manufacturers) still need to learn: transparency. A detailed list of changes can be of critical importance.

It's not only a matter of detailing "fixes in measurements" but _what_ you have fixed.

[hwj-d]

It's not only a matter of detailing "fixes in measurements" but _what_ you have fixed.

... if they know it

[hwj-d]

By the way, a completely different question:
is it possible to upgrade from 100Mhz to 200Mhz and later from 200Mhz to 300Mhz, and how much does it cost?

It is. While the part numbers only exist to go from 70MHz to each of the higher steps, we’ll discount out the difference - you should just need to ping the place you purchased it from.

-Rich

Yes, that's my opinion too, but not from this nice lady on the phone R&S-Germany. 
I think something like that should be settled in this sense.

[nctnico]

I'm wondering about two things:
- Does the latest firmware fix all the outstanding issues or are there more issues to be fixed?
- What is the price including the current special offers? IIRC originally the 300MHz model + MSO + decoding would set you back about 8000 euro.

[0xfede]

I'm wondering about two things:
- Does the latest firmware fix all the outstanding issues or are there more issues to be fixed?
- What is the price including the current special offers? IIRC originally the 300MHz model + MSO + decoding would set you back about 8000 euro.

I don't have an answer for the first question but I have ordered it last Friday (It should arrive today) from Farnell. Final price ~4150 + VAT for a full optional scope (MSO 300MHZ + PK1) thanks to black Friday (15%) and launch offer on PK1.

Best,
0xfede

[0xfede]

And here it is my new baby 

[nctnico]

I'm wondering about two things:
- Does the latest firmware fix all the outstanding issues or are there more issues to be fixed?
- What is the price including the current special offers? IIRC originally the 300MHz model + MSO + decoding would set you back about 8000 euro.

I don't have an answer for the first question but I have ordered it last Friday (It should arrive today) from Farnell. Final price ~4150 + VAT for a full optional scope (MSO 300MHZ + PK1) thanks to black Friday (15%) and launch offer on PK1.

Thanks. That price level seems way more sane to me. Looking forward to what others have to say about the new firmware.

[dr.diesel]

Doesn't show on the R&S website, but:

https://cdn.rohde-schwarz.com/pws/dl_downloads/dl_firmware/zip_1/RTB200x_Firmware_V02.000.zip

YMMV - You know the risks - etc.      

[Octane]

It’s on the website now:
https://www.rohde-schwarz.com/hu/firmware/rtb2004/

Michael

[Hydron]

It's online (officially) now, and I just did the update. Scope is still alive!

[Robaroni]

Thanks R&S.

[Octane]

A few graphics issues have made it into this release as well, as the attached screenshot shows.
Square-wave on channel 1.
Measurement added (peak-peak).
Zoom enabled (exact settings are visible in the screenshot).
Hit the Run/Stop button (history navigation appeared).
Added second measurement (rise -time).
Scrambled overplayed graphics appeared.

BR,
Michael

[mikeselectricstuff]

Unfortunately they've not killed all the sliding effects that make the UI feel more sluggish than it needs to be

[mikeselectricstuff]

-MOSI/MISO functionality for SPI bus with option RTB-K1
-Rx/Tx functionality for UART bus with option RTB-K2

These are cosmetic changes only - if you enable MISO and MOSI this uses both decode channels ( second channel gets disabled) .
Similarly if you have UART TX and RX, that also uses both channels, so you can't for example do SPI with MISO and MOSI and any other decode at the same time.

It's a slight improvement for SPI ( Though not equivalent to scopes that have two full decode channels), but for UART I can't really see much advantage over using the channels seperately.

At least UART framing works correctly now.

[mikeselectricstuff]

One previously reported bug not fixed :
Aux out setting not preserved over a power cycle

[Hydron]

It's definitely disappointing to discover that one full-duplex decode is still all that you get despite the change in configuration method. Even having the second decoder limited to simpler options (i.e. non-RX/TX or MOSI/MISO) when the first decoder is doing full duplex would be a big improvement.

Rich - are you able to comment on the reason for the limitation continuing despite the configuration change? Is it due to hardware capability, or commercial reasons? The fact that multiple addressed buses (e.g. I2C, CAN) are supported simultaneously argues to me against it being the latter.

The other changes/improvement/bug-fixes are certainly welcome - looks like they got to most (though not all) of the bugs I submitted. I'll be using the scope in anger this weekend, so will provide feedback on what I find. What is the "Fast Segmentation" option btw?

Edit: "Fast Segmentation" seems to have an effect in "Nx Single" capture mode - I'm seeing as little as 3.2us between segments, i.e. 300k+ segments/s.

[Rich@RohdeScopesUSA]

One previously reported bug not fixed :
Aux out setting not preserved over a power cycle

Hi Mike - this is actually the intended behavior.  Because the output can be used as a generator, 10MHz out, pass/fail, etc we try to protect users who may not realize that the output was set as a generator (e.g. in schools) and end up destroying a sensitive device.  We realize this is frustrating to a more experienced user, but we feel like we chose the lesser of two evils.  Definitely open to other suggestions if you have them. 

-Rich

[Rich@RohdeScopesUSA]

It's definitely disappointing to discover that one full-duplex decode is still all that you get despite the change in configuration method. Even having the second decoder limited to simpler options (i.e. non-RX/TX or MOSI/MISO) when the first decoder is doing full duplex would be a big improvement.

Rich - are you able to comment on the reason for the limitation continuing despite the configuration change? Is it due to hardware capability, or commercial reasons? The fact that multiple addressed buses (e.g. I2C, CAN) are supported simultaneously argues to me against it being the latter.

The other changes/improvement/bug-fixes are certainly welcome - looks like they got to most (though not all) of the bugs I submitted. I'll be using the scope in anger this weekend, so will provide feedback on what I find. What is the "Fast Segmentation" option btw?

Edit: "Fast Segmentation" seems to have an effect in "Nx Single" capture mode - I'm seeing as little as 3.2us between segments, i.e. 300k+ segments/s.

Hi Hydron - first, you are correct on "Fast Segmentation".  It's a feature that had been there, but was not obvious and/or easy to use, so based on feedback from a number of users we tried to simplify it.

With respect to your question on the duplex buses, I have a guess, but I'll also confirm with our R&D team.  I believe it is due to our hardware implementation of bus decoding in a FPGA.  We tried to simplify the setting up of a duplex bus (which I believe we did), but we weren't able to completely reconfigure the FPGA to handle a duplex bus on a single decode at this time.  Having said that, we know that several people would like the ability to decode a full duplex bus and another bus simultaneously and we'll continue to keep that on the potential enhancement list for future updates.

-Rich