Products > Test Equipment

First picture on EEVblog of the new R&S MXO4 series oscilloscope :)

<< < (54/60) > >>

tooki:
I think the market is a bit slow now in general, which is why everyone is extending their promos. So if you need something now, jump on it, but if you have something to use at the moment, I wouldn’t rush. There WILL be another special. And remember that the end of the year is when the sales reps have targets they want to reach, so that’s when you can negotiate a bit more. ;)

radar_macgyver:
i convinced my boss to spring for the MXO4-BNDL to replace an aging Tek MSO 4054. Only had it for a month, and I find the MXO4 to be leaps and bounds ahead of the Tek, though it's not a fair comparision to a much older instrument. The spectrum analyzer is really nice, very fast update rates. I have it mounted on a VESA monitor arm (with a quick disconnect), frees up some bench space. Can't add much that hasn't been covered by, say, @shabaz and others. The included probes are 700 MHz, and feel very nice in the hand. Compared to the Tek P6139A, they are lighter and thinner, the cables are equally stiff. The spring-loaded tips are nice, but take a bit getting used to.

I also ordered a single active RT-ZS20 1.5 GHz probe (I had a TAP1500 to work with the Tek). Again, haven't had much quality time with it yet, but it seems well made and feels nice in the hand. Unlike the TAP1500s, the probe body doesn't get uncomfortably warm.

The MXO4's drawbacks I've come across so far:

* UI is a bit sluggish - using the vertical position dials to move the traces has a noticeable lag. Similar to the MSO 4054, but a lot worse than Keysight 3 or 4000 series. Really hoping R&S can improve this.
* Though I'm running the latest firmware, I've seen a few bugs pop up now and then. For example, if I leave the scope running for many days, it can get into a mode where the reference level indicator for the traces disappears, and the left and right borders of the screen start flashing, as if the traces are being overdrawn on top of the edges of the graticule. The only fix for this is to reboot the scope. Next time it happens, I'll take a video.
* When the scope is in the mode described above, the I2C decode seems to randomly not decode frames. May be related, but after the reboot it worked flawlessly
* After running any of the apps, for example the frequency response app, the scope effectively does a factory preset, rather than returning to the previous settings.
My place of work is such that it's hard for me to use the 'order the instrument today and pay for the options later' model since it's hard to justify a several kilodollar purchase that's 'just software' (I've had inventory management asking me where they can place the asset tags for a Fieldfox option I bought, for instance). The BNDL offer makes all this go away, and it was fortunate that we had the budget for it.

tv84:

--- Quote from: radar_macgyver on February 26, 2024, 12:55:46 am ---For example, if I leave the scope running for many days, it can get into a mode where the reference level indicator for the traces disappears, and the left and right borders of the screen start flashing, as if the traces are being overdrawn on top of the edges of the graticule. The only fix for this is to reboot the scope.


--- End quote ---

 :palm: Unacceptable on a R&S device.

pdenisowski:

--- Quote from: radar_macgyver on February 26, 2024, 12:55:46 am ---The MXO4's drawbacks I've come across so far:

* UI is a bit sluggish - using the vertical position dials to move the traces has a noticeable lag. Similar to the MSO 4054, but a lot worse than Keysight 3 or 4000 series. Really hoping R&S can improve this.
* Though I'm running the latest firmware, I've seen a few bugs pop up now and then. For example, if I leave the scope running for many days, it can get into a mode where the reference level indicator for the traces disappears, and the left and right borders of the screen start flashing, as if the traces are being overdrawn on top of the edges of the graticule. The only fix for this is to reboot the scope. Next time it happens, I'll take a video.
* When the scope is in the mode described above, the I2C decode seems to randomly not decode frames. May be related, but after the reboot it worked flawlessly
* After running any of the apps, for example the frequency response app, the scope effectively does a factory preset, rather than returning to the previous settings.
--- End quote ---

Thanks for letting us know.  If you haven't already, could you contact our North American Support Center about these issues?  I'll try to reproduce them on my MXO4, but it would be helpful if you could open a case so that we can investigate and fix these issues. 

USA: Phone: 1-888-837-8772 (1-888-Test-RSA), email: customer.support@rsa.rohde-schwarz.com

Incidentally, we do have a new FW release coming out very soon (checking on exact date right now) and that might address some of the things you're reporting.

Thanks again!


radar_macgyver:
Will do. I was going to try and capture a video of this, though the second time it happened I was in the middle of debugging a board and rebooted the scope to get things working (that's when I noticed the I2C decode issue).
Also, just for completeness, the reference indicator of all traces except the currently selected one disappear when the scope gets into that funny mode.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod