Magnova oscilloscope

[Andre77]

how large is the memory for arbitrary in the generator module (option)?

The memory for the arbitrary signals will probably be 32 kBytes. We have not yet finalised how much memory the generator ‘gets’ in the FPGA - therefore the final value may still differ slightly.

Best regards
Andre

[Andre77]

Can you answer a few questions:
1. When you planning to add histogram functionality into Magnova?
2. Same question about web interface?
3. Same question about desktop software? I can turn its support in Magnova's interface, but does such software exists?
4. Do you have some development roadmap that you can share with your customers?

1. The histogram function is already planned, but we have not started implementation yet. At the moment, I cannot provide a specific timeline for its availability, as other tasks need to be prioritized first – particularly item 2 and the firmware for new hardware options (logic probes and generator).
2. The web interface is one of our top priorities for Q1/2025. We will begin development in January and expect the web interface to be available by March or April. In parallel, we will continue to release regular updates with minor enhancements, improvements and functions for the logic probes and the generator option. And should bugs occur, these will of course also be fixed with priority.
3. The software already exists, but we need to finalize some things before we can release it.
4. We have not yet set a fixed roadmap, as we aim to remain flexible to accommodate customer requests.

Best regards
Andre

[Tomki]

Hi Andre
Talking about the development timeline: The Magnova brochure also mentioned the development of a frequency counter. Can you say when this will be available and what bandwidth it will have (if it differs from that of the Magnova)?
Also, have you got any idea when the improved math functions including measurement feature will be available?
Thanks
Thomas

[Andre77]

Hi Andre
Talking about the development timeline: The Magnova brochure also mentioned the development of a frequency counter. Can you say when this will be available and what bandwidth it will have (if it differs from that of the Magnova)?

Hi Thomas,

The frequency counter function will become available after the web server and the other extensions mentioned above. As a rough time estimate, I would put this in the second quarter of 2025.

Also, have you got any idea when the improved math functions including measurement feature will be available?

I'm sorry, but I can't estimate the time frame for this yet.

[ralphrmartin]

Is there an SCPI command for switching to X-Y mode? I could not see it in the SCPI manual...

[nctnico]

Hi Andre
Talking about the development timeline: The Magnova brochure also mentioned the development of a frequency counter. Can you say when this will be available and what bandwidth it will have (if it differs from that of the Magnova)?

Hi Thomas,

The frequency counter function will become available after the web server and the other extensions mentioned above. As a rough time estimate, I would put this in the second quarter of 2025.

What kind of features can be expected from the frequency counter function? Is this equivalent to a fully featured frequency / time interval counter?

[Andre77]

Is there an SCPI command for switching to X-Y mode? I could not see it in the SCPI manual...

Thank you for your feedback! Currently, X/Y display cannot be activated via SCPI, and selecting the X/Y channels is not yet possible via SCPI. We will include these in the next update.

What kind of features can be expected from the frequency counter function? Is this equivalent to a fully featured frequency / time interval counter?

We still need to define the exact functionality of the frequency counter feature.

Here’s an initial list of potential functionalities:
- Measurement of frequency, period, and duty cycle.
- All channels can be selected (not just the trigger channel).
- Switching threshold selection: Automatic (Vmid), trigger level, or manually adjustable level
- Data acquisition and processing performed in the FPGA (in the background, independent of "normal" acquisition).
- High resolution and accuracy (adjustable averaging time).

If you have specific requirements or suggestions, we’re happy to consider them.

[mk_]

We still need to define the exact functionality of the frequency counter feature.

Here’s an initial list of potential functionalities:
- Measurement of frequency, period, and duty cycle.
- All channels can be selected (not just the trigger channel).
- Switching threshold selection: Automatic (Vmid), trigger level, or manually adjustable level
- Data acquisition and processing performed in the FPGA (in the background, independent of "normal" acquisition).
- High resolution and accuracy (adjustable averaging time).

If you have specific requirements or suggestions, we’re happy to consider them.

Would be nice if there is also something like:

- A/B Relation
- Counter with either rising or falling edge as trigger
- A trigger / B counting by trigger A without aliasing, specialy when time/div is slow so that aliasing could be a visible problem

[nctnico]

What kind of features can be expected from the frequency counter function? Is this equivalent to a fully featured frequency / time interval counter?

We still need to define the exact functionality of the frequency counter feature.

Here’s an initial list of potential functionalities:
- Measurement of frequency, period, and duty cycle.
- All channels can be selected (not just the trigger channel).
- Switching threshold selection: Automatic (Vmid), trigger level, or manually adjustable level
- Data acquisition and processing performed in the FPGA (in the background, independent of "normal" acquisition).
- High resolution and accuracy (adjustable averaging time).

If you have specific requirements or suggestions, we’re happy to consider them.

I'm wary of claiming 'must have specs' as these will vary between use cases. Let me outline the use case I'm most familiar with and the problems I encounter using existing equipment:

One of the fields I'm involved in is time & frequency distribution down to the picosecond level over large distances (tens to hundreds of kilometers). In order to measure the stability long term (which is affected mostly is due to temperature effects) the tool of choice is to use a time interval counter like the Keysight 53230A (20ps resolution) or Tektronix FCA3100 (50ps) resolution to compare 1PPS (1 pulse per second) outputs between two (or more) pieces of time & freququency distribution equipment. The only problem is that the equipment we are using has a much higher stability compared to the time interval counters. For some measurements we are just looking at the noise from the time interval counters, not the equipment itself.

And there are other problems as well: for both counters the skew between channels is rather large so we have to calibrate the skew before making a measurement. A Keysight 53230A specific problem is that it can't deal with large time intervals accurately. Measuring an edge which is almost 1 second later compared to the first edge gives a large error (using an external reference clock doesn't help). It also can't determine the sign automatically beyond 1 nanosecond or so. If the second edge is 1 second later, it is convenient the counter produces a negative interval. The Tektronix FCA3100 can determine the sign automatically and it does correct measurements for long intervals but the 50ps resolution is severely limiting its usefulness. Both counter models need to average for quite a while (the FCA3100 more than the 53230A) before the average gives a decent number for the actual time offset. When I want to make a quick measurement, I'm using a Lecroy DSO to make the time interval measurements using edge to edge measurements but I have to make the vertical sensitivity high in order to get accurate measurements. Like 20mV/div for a 1.7Vpp input signal. Otherwise the edge contains too much noise from the front-end to make accurate measurements. I would want to use even lower V/div settings but that overdrives the front-end. My previous Agilent DSO was more forgiving in that respect.

The measurements for /on the time distributions systems are typically made using remote control where a measurement is queried from the counter over SCPI so there is a new data point every second. However, having things like a trend chart and statistics on the timer interval counter itself is handy every now and then to have a quick insight to what is happening.

[king2]

1. Got deeper into filter section of channel, so I would like to make a feature request - what about possibility to set filter frequency manually?
Sometimes it needed to set filter to something about 30-100kHz - in very noisy environment. It is always compomise between chances to see signal without noise - and chances to see signal that still not filtered out

2. From time to time I met a noise signals from hardware, and I have to guess where noise is coming from. I see clearly noise signal, I can measure it with cursor (something about 45kHz), but if I set trigger and make a measurement panel - I geting values like a 48Mhz. Can I measure frequency of noise signal spikes?

3. I made a connection to smd server on Linux. Tried to make quicksave to such share - and scope was turned off. How to make SMB shares work (or how to debug?)

4. Scope can access network via RJ45 cable. What about idea to use WiFi USB adapter?

[KungFuJosh]

+1 for manual frequency range selection. Filtering BP/HP/LP manually, and/or setting a specific range of frequencies to include or ignore (Max and Min) can be helpful when isolating signals.

[egonotto]

Hello,

there is a German-speaking Youtuber who has already published several good videos about the Magnova:

https://youtu.be/GVWIh5sl-o4?si=L6KZgBbHrWvqE0gO


Best regards
egonotto

[jusaca]

Does the magnova somehow support filters (highpass, lowpass, bandpass) of the math channels? I could not find any filtering functionality in the math section of the manual. Currently I'm working with a Keysight which does at least allow a lowpass filter on the math channel, but no other filtering. I would love to have a scope that allows both low- and highpass filters at the same time on a math channel.

[FloBX]

Does the magnova somehow support filters (highpass, lowpass, bandpass) of the math channels? I could not find any filtering functionality in the math section of the manual. Currently I'm working with a Keysight which does at least allow a lowpass filter on the math channel, but no other filtering. I would love to have a scope that allows both low- and highpass filters at the same time on a math channel.

Hi jusaca,

the Magnova does currently not provide a filter functionality for math channels. While we are working on improvements related to math channels and have planned further changes on the long term, we currently do not want to make any promises regarding implementation of a math filter feature.

Best regards,
Florian

[FloBX]

And since I was just preparing a general post, here it is:

Hi,
we hope that we have met expectations with our SCPI-"Christmas update" and that you had a successful start to the new year. While development of further Magnova firmware improvements and new features is on track, yesterday was the last day of our introductory discount period (about four months now since shipping of the first Magnova devices).
 
Starting today (16^th January) pricing of Magnova oscilloscopes follows a new retail pricing scheme:

Bandwidth	Standard	Non-Commercial (NC)
100 MHz	2999 €	2599 €
200 MHz	3749 €	2999 €
350 MHz	4499 €	3749 €

(retail prices excl. VAT)
 
We have decided to facilitate access for private customers, educational institutions and non-profit organizations by introducing separate retail prices for non-commercial purposes. The principle is straightforward: Non-commercial customers get the next higher bandwidth level for the same price, without any limitation in functionality.
We also reduced the retail prices for 200 MHz and 350 MHz models in general.
 
Do not hesitate to contact Batronix service in case of any related questions.
 
Best regards,
Florian
Batronix Team

[Tomki]

Hello and Happy New Year to everyone !
I have got a suggestion on the subject of triggers:
The, let's say "very thin" Magnova manual does not give any explanation for the use of triggers - just a list. So I looked at the manuals of other oscilloscope manufacturers and also at Dave's videos on the EEVblog and came across video #685 (https://youtu.be/y5aAjd9YPok).
Not that I have often missed these trigger options so far, but if they are standard elsewhere (even on cheaper devices), I wonder whether it would not be useful or desirable for the Magnova as well.
1. Triggers can usually be coupled AC or DC, although AC coupling is the usual option. This is apparently not possible with the Magnova. The trigger coupling is always "DC", i.e. a selected voltage value. This means that the trigger is lost if I switch between signals with different DC offsets.
2. There is no "alternate" or "OR" trigger (the latter only via pattern trigger). This means that you cannot trigger signals with a runtime difference that would allow the signals to be compared at the same trigger position.
3. Would an alternate timebase be desirable?
Does anyone have an opinion on this?
Regards Thomas

[Tomki]

And since I was just preparing a general post, here it is:

Hi,
we hope that we have met expectations with our SCPI-"Christmas update" and that you had a successful start to the new year. While development of further Magnova firmware improvements and new features is on track, yesterday was the last day of our introductory discount period (about four months now since shipping of the first Magnova devices).
 
Starting today (16^th January) pricing of Magnova oscilloscopes follows a new retail pricing scheme:

Bandwidth	Standard	Non-Commercial (NC)
100 MHz	2999 €	2599 €
200 MHz	3749 €	2999 €
350 MHz	4499 €	3749 €

(retail prices excl. VAT)
 
We have decided to facilitate access for private customers, educational institutions and non-profit organizations by introducing separate retail prices for non-commercial purposes. The principle is straightforward: Non-commercial customers get the next higher bandwidth level for the same price, without any limitation in functionality.
We also reduced the retail prices for 200 MHz and 350 MHz models in general.
 
Do not hesitate to contact Batronix service in case of any related questions.
 
Best regards,
Florian
Batronix Team

Hello Florian
General question about the new pricing options: I assume that the "NC" versions are technically no different from the "normal" devices. How does Batronix ensure that not everyone purchases an "NC" version? Will Batronix require any proof (e.g. proof of enrollment at a university) or declaration of private use?
I'm asking because, for some other reason I can't figure out, the "NC" version of the BMO350 is in stock, while the "normal" / commercial version will only be available in 11-21 days?
Regards Thomas

[Sorama]

I don’t like this new price setting.

I did my very best to be an early adopter to have this so called 30% reduction but now anyone can buy the same scope for only 200€ more than the “early adopter price”.
That is NOT 30% reduction.

Will companies with a VAT number be able to buy the NC version? (With a proper invoice)

[FloBX]

General question about the new pricing options: I assume that the "NC" versions are technically no different from the "normal" devices. How does Batronix ensure that not everyone purchases an "NC" version? Will Batronix require any proof (e.g. proof of enrollment at a university) or declaration of private use?

Will companies with a VAT number be able to buy the NC version? (With a proper invoice)

There is no technical difference between "normal" and NC devices. NC products will not be sold to company customers, meaning that company invoice addresses will not be accepted for these devices. This is the proof we intend to rely upon.

I did my very best to be an early adopter to have this so called 30% reduction but now anyone can buy the same scope for only 200€ more than the “early adopter price”.
That is NOT 30% reduction.

After the introductory phase, we decided to adjust the retail prices based on extensive feedback to make the Magnova more accessible to private customers in the long term. This was not an easy decision, but we believe it is the right step to ensure the product's appeal to as many users as possible.
All early adopter prices were set below the now specified values, even if me must admit, that the initially stated percentages do not apply to the now changed pricing scheme.

I'm asking because, for some other reason I can't figure out, the "NC" version of the BMO350 is in stock, while the "normal" / commercial version will only be available in 11-21 days?

Thanks for the hint: We fixed the incorrect the availability note.

[woody]

I don’t like this new price setting.

I did my very best to be an early adopter to have this so called 30% reduction but now anyone can buy the same scope for only 200€ more than the “early adopter price”.
That is NOT 30% reduction.

You never know, maybe we early adopters get an extra discount on the LA and AWG 😉

[Sorama]

Both for free is something I could live with 

[Martin72]

That is NOT 30% reduction.

At that time, yes.
As an “early adopter”, you always run the risk of either paying more than others or getting less for the same money.
I know this from my Siglent Scopes, with the 2000X HD it was really bitter afterwards, because it later cost just €1000 less than I had paid.
Or when the devices are available with bundles, but only for new buyers...
I was always “too early” to buy.
The fairest thing for early buyers is actually an introductory discount, as offered by Batronix.
You still have something out of it, even after the price adjustments, you had paid less.
I would also like to see something like that from other manufacturers (cough, cough)...

[Sorama]

The  so called 30% reduction is now something like 7%. Just a few months after introduction.

For that price, I could easily have bought a Siglent 3000HD with is on another level.

You didn’t buy the 2000hd with a so called introduction price with an end date.
Thats different from Batronix who explicitely announced an exclusive, onetime offer.

[woody]

All in all, I am still pretty chuffed with the device. The fact that my discount is smaller than initially thought does not influence this. This happens a lot when you are an early adopter. I remember shelling out 63k for a Tesla 5 years ago that now sells for 52k.

More important to me is Batronix meeting the promise of support and addition of new features. Because that is also a real risk when adopting early: sometimes products don't make it and are abandoned (DCC, DAB).

So far I have no complaints about that with the Magnova.

[Sorama]

But again, Tesla did not promise nor advertised an early adopter price reduction for a limited time.

Batronix did and put a deadline on it.