There is certainly a learning curve. Finally, watching YouTube videos on using the instrument got me over the hump, as well as a sit down session with one of the oscilloscope experts. 

The Rohde & Schwarz user interface is very oriented towards drop and drag functions on the screen. Some of those are just not obvious how to use. You have to have somebody get you over the hump. My understanding is they have a newer user interface, but I haven't gotten around to upgrading the firmware on my scope in some time, so I'm not familiar with it yet. In comparison, I love the LeCroy interface.

Recently, I've learned that there are ways to adapt these instruments to become a Vector Network Analyzer (VNA), which is of interest to me. If I can use probes that are not in the 50 ohm domain, which is what you would have with a normal Vector Network Analyzer, then doing power applications for me, this would be a lot safer. Using a traditional communications type Vector Network Analyzer in the 50 ohm domain and having these high DC potentials (adding the DC blocks is adding air to the test method), then having an oscilloscope type front-end which is lot more tolerant of overload, it is a lot safer. The vector network analysis that I need to do is well under a gigahertz, and the other instruments that I have sort of stop at 40 megahertz. Trying to get past 40 megahertz into the mid-hundreds of megahertz and have high impedance probes that will tolerate DC, that is really of interest to me.

It would be good if they would try to automate most things because it has more pressing buttons and repetitive work. If there were automation scripts that they could provide, that would improve things.

It would be good if they could go up to higher gigahertz bandwidths. Right now, the analyzer that we have is able to go to 10 GHz, and there's a lot of stuff going on at higher frequencies. I'm not sure if they have this product available in the market.

In terms of the user interface, the program is great but the front panel is a little bit tough to get through.

In the next release, I would like to see report generation. It would make it a lot easier to refer back to and, when doing final testing, seeing what went on during the pre-test would help.

The GUI could be improved since the hierarchy is a little complicated for the new users. It would be good if the frequently used configurations in the calibration setup such as the signal power, phsical bandwidth etc. could be moved to one editable table. And users can access to the table by clicking a quick link button in the desk top of the GUI.

The user interface could be improved, e.g., the documentation on the menus. I have to open a separate document to figure out the functionality sometimes. Some primaries are unclear and the limitations are sometimes unclear, then you have to go ask customer support. So, it would be better if the documentation was more easily accessible (not lacking).

There was a learning curve. Their use interface and the way that their products work are not intuitive to somebody who switches from other vendors, like Keysight or LeCroy. At first, I had to be walked through every step because every time I guessed where to find a function, I would guess wrong.

Once you learn the user interface, it's very nice. However, when you face it for the first time, it's tricky. You have to spend time with the product before you feel comfortable with it.

I would like to increase the range of our signal processing functions in our real-time oscilloscopes. Since they have been marketing their oscilloscope as universal or as a multi-purpose scope, it does very well for the supplying those measurements, but it is lacking in jitter measurements.

User interface is okay. I would probably rate it a seven out of ten. The software is sometimes not intuitive, even though we want it to be. It could be a bit better.

I'm against the Windows-based tools. Now everybody is running scopes, VNAs, and all their tools based on Windows. I don't want to see that in the future.

We would like to have autotracking and auto error tracking for regression testing. We would like to know what error happened, when it happened, and during what scenario (such as setup), because right now we have to manually look at when it happened. Sometimes, this takes a long time. We want when something happens, to capture it, then have it give out the full timestamp. We also want it user-friendly and sent to the cellphone, so that's the Internet of Things.

The test equipment has configured the capability to ease the tester's routine job. Going forward, the product should be able to forward the tester's debugging and test information to the their cellphone and enable them to check the results on-time. 

There is a small learning curve. It probably took a month or two to get used to the instrument because of the user interface, which could be cleaned up more. Sometimes, it's difficult to find menus.

The user interface of this solution is not that intuitive. When you're used to a different product, there's a learning curve.

Also, the size of the unit is too big, too heavy. It has to be made more portable and smaller.

They could use an RDA interface.