I want to thank everyone here on the forum and elsewhere, but especially this forum, for the reviews, discussion, and information provided about the RTB2000 (and the other test equipment I have researched and bought over the years).
I can truthfully say that the launch promotion (as read about via the forum) significantly impacted my hobby by saving me time in tracking down very intermittent protocol faults and ruling out various causes (it turned out to be a corner case in my code), that would have been near impossible to find with my significantly older scopes and PC controlled logic analyzer as I left the scope on for a week with a carefully setup trigger condition. Prior to this experience, I never would have thought that it was worth having any MSO capability or protocol decodes in a scope and thus would not have purchased those capabilities at the future date I would have eventually purchased a modern scope.
To the general goal of a new product promotion being to get the product into the hands of evangelists, I will admit to not having influencing power over a large school or company lab, or a following on social media, but I now own an FPC1500 as well (as sadly for my wallet my interests take me to the 2.4GHz band ruling out most of the cheaper options), and with work being interested in upgrading our scope (a TDS2000B) to a newer scope, I have been advocating for a RTM3004, budget permitting, as we are familiar with my RTB2K from the few times I have brought it in to troubleshoot something our 60MHz scope doesn't do well (and of course all my personal use).
I'd also like to thank Rich for being a helpful company representative on the forum, R&S for retroactively including the Bode plot option in the bundle (and the promotion in the first place, if that wasn't clear above), and R&S support for very promptly activating the option for me.
And finally,today I somehow found a bug new to version 2.202. I managed to get the displayed trigger level to not actually line up with the waveform shown on the screen. I am not sure what I did to cause this, other than I was using the position offset, and I tried shifting the waveform on the screen later in the day and could not reproduce the issue. See the attached screen shot, it should be fairly clear that the trigger line does not line up with where the wave crosses 0 time and that the trigger voltage matches the point that the screen is displaying but clearly not where the hardware is.