Products > Test Equipment
First picture on EEVblog of the new R&S MXO4 series oscilloscope :)
tooki:
I was at the automation expo today and ran into the R&S rep that sold us the MXO4 I have at work. We were discussing and playing with the zone trigger. He mentioned that it somewhat overlapped (in how it’s designed) with the mask test feature available on some other R&S scopes. That got us curious and we poked around all the menus of the demo MXO4 to see if mask testing has been added. Before you get your hopes up: it hasn’t.
But it sure looks like it may be coming, because we found an entire menu full of other features that don’t seem to be implemented yet. To get to it, you have to edit the toolbar, and then there are “mask test” and “add mask” buttons you can add. Once enabled, pressing one of them opens a toolbar with mask testing and a menu with a bunch of other things, including a spectrogram. But actually trying to do anything doesn’t work. Trying to draw a mask just gives an error. I cannot rule out that these only appear with a demo all-features license installed, but I can say that these buttons/menu do not appear on an MXO5 (with demo license installed) with the prior firmware version.
tooki:
--- Quote from: Neoname on August 27, 2024, 09:52:22 pm ---Having spent an evening playing with it now, and I honestly feel that this feature update really does deserve a lot more attention.
If you've ever tried to hunt down something that's being obnoxious to pin down, even from the spectrum analysis: this just gets you straight there within a minute spent setting it up. Minimal effort is required to isolate exactly what you need. It's crazy how useful this is. There are even zone complex logic settings to make and/not/or/xor zone combinations if you need to go all out, and the logic can apply to zones across all channels and the spectrum analysis channels all simultaneously.
I will note a UI flaw in the multiple zone logic. While editing in "Zone Trigger -> Logic Operator -> Trigger condition" it is too easy to delete the spaces between the Zones to create as example "Zone1 andZone2" and there is no way to reinsert a space back. There needs to be a spacebar under the Punctuation input to restore this, else the only thing that can be done is to "Clr" and start entering the Zone logic again.
@pdenisowski Thanks! I'll reply to your PM.
--- End quote ---
Can you use the on-screen keyboard (in the main menu) to type the space?
Neoname:
--- Quote from: tooki on August 28, 2024, 05:48:29 pm ---Can you use the on-screen keyboard (in the main menu) to type the space?
--- End quote ---
No, there's no such option. You can see what the Zone combination logic menu looks like at 26min30 in the review video of the MXO5 linked earlier here.
tooki:
--- Quote from: Neoname on August 28, 2024, 06:42:47 pm ---
--- Quote from: tooki on August 28, 2024, 05:48:29 pm ---Can you use the on-screen keyboard (in the main menu) to type the space?
--- End quote ---
No, there's no such option. You can see what the Zone combination logic menu looks like at 26min30 in the review video of the MXO5 linked earlier here.
--- End quote ---
I don’t mean the keypad in the dialog. I mean the actual on-screen keyboard found in the main menu, circled in red in the screenshot below.
tooki:
--- Quote from: Neoname on August 27, 2024, 09:52:22 pm ---I will note a UI flaw in the multiple zone logic. While editing in "Zone Trigger -> Logic Operator -> Trigger condition" it is too easy to delete the spaces between the Zones to create as example "Zone1 andZone2" and there is no way to reinsert a space back. There needs to be a spacebar under the Punctuation input to restore this, else the only thing that can be done is to "Clr" and start entering the Zone logic again.
--- End quote ---
Also:
Yeah, the Zone Trigger UI has some rough edges, like the lack of Back button mentioned in the video. (Also, in the MXO GUI, why is the Back button within the settings area of some dialogs, and in the left navigation column of other dialogs? The MXO software definitely could use some feature rearranging, many options are split up in annoying ways.)
As for the logic operators, R&S should definitely change the logical operators to be in all-caps, as is customary in electronics: AND, OR, XOR, NOT
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version