Unfortenately, till now nothing has hapened with MXO4, and i think nothing will be to expected with MXO5 either.
Oh, I wouldn't say that: we just had a major firmware release a few weeks ago that added a number of features, and we are running at full steam to bring out additional features and options. If you look at the release notes of any of our other oscilloscopes (like the RTO6) you can see that we regularly and aggressively introduce new features.
[I also say this based on the fact that I have our internal roadmap open in another window and beta FW on my MXO right now
![Smiley :)](https://www.eevblog.com/forum/Smileys/default/xsmiley.gif.pagespeed.ic.R8GFI-pF6f.png)
]
If you look at company hierarchy, real signal analysis starts only with RTO6 platform.
That depends on the kind of analysis you are doing: the RTO6 is a higher series scope (RTO
6 > MXO
5 > MXO
4), so naturally it supports some features not found on lower tier scopes. I absolutely love the RTB2000 ("2"), but I don't expect it to have eye diagrams, jitter analysis, Ethernet conformance testing, etc. We don't try to put every feature in every scope because (a) some scopes are simply unable to perform certain functions and (b) some customers don't want to pay for features and capabilities they don't need. This is true of all scope manufacturers (and indeed, for all companies that manufacture different tiers of products: look at cars, phones, etc.)
Probably, bouth MXO platform are capable for that, but company policy don`t wont that.
Honestly, I would have to look to see if there are any existing features on our higher end scopes (like RTO6 and RTP) that couldn't - theoretically - be ported to the MXO series.* But in a general way, our policy is always to give customers a range of price and performance (and thus cost) choices when it comes to test instruments.
(*Now I'm going to go waste half of my day being unproductively curious about something I can't publicly share anyway
![Laughing :-DD](https://www.eevblog.com/forum/Smileys/default/smiley_laughing.gif.pagespeed.ce._hfWAz_QHO.gif)
)