Magnova oscilloscope

[kaspich]

Btw, 1:10 probes still are not recognized correctly.
The bug was reported more than a month ago.
But, again - it's just a feature request

[Sorama]

Only a month

[kaspich]

Only a month

Two releases (1.7.2 and 1.8.1) were published. And this is basic functionality/a few lines of code.

[Sorama]

Yeah…but waiting a year for a so called standard feature at Keysight is much better, isn’t it?

[Darkover]

Btw, 1:10 probes still are not recognized correctly.

I don't have an Magnova, but in this case I like to say it is important that you can overwrite the 1:10 detection!
Old Hameg scopes (HMO2024) can not do this. This is a pain if you use a 1:10 probe with an external
circuit for current measurement and like to see "mA" on the screen. (scotch tape rulez)

Olaf

[2N3055]

First of all I see some are confused.

It NOT UNETHICAL for manufacturer to be on the forum.
They are welcomed here and it serves as GREAT resource for users.
They are open about who they are. They are here with full "blessing" of forum owner.

Whoever think it is better how Keysight, Tektronix, R&S are hiding behind support wall has scrambled brain.

Second, to @kaspich : create new forum topic, and go there and write your monologues there. So we can continue discussing here the actual oscilloscope. Hint: I personally think most of what you write is confused nonsense. But I have no problem with your right to free speech. Just do it somewhere else, not here. This topic is not for rants. It is for actual users exchanging useful info and converse with manufacturer. I agree with @rf-messkopf 100%.

And no, it is not Karate John. Be respectful to others. People always return in kind, bad and good.
You will either respect the will and rights of majority of people here or majority will start asking for you to be banned from forum. It is as simple as that.

Dear user,

Why are you thinking that your monologues deserve to be in this topic, by mine - no. Why do you think that you are different?
Simple question, I would receive a simple answer.

Simple and truthful and direct ?
No false politeness ?

Because I try for what I write not to be stupid and unreasonable (to the best of my ability and limited knowledge) and what you write mostly is. Arrogantly so.

Please do not be insulted by my honest statement. A person can have only limited patience.. And you asked for it.

[2N3055]

We don't own a Magnova, so no skin in the game, but have been impressed by Batronix. Especially so with Andre77 comments/information/support, keep it up

Best

Same here, I do not own Magnova, but have immense respect for both management of Batronix that made the brave decision to embark on this journey, and excellent engineers that created very good product, and from the scratch. Kudos.

what? You don't own Magnova, but posting crap like this?
I own Magnova, but my aposts about bugs are not welcome?
You are a real clown, sorry

 

[mikeselectricstuff]

This post is dedicated to the people who are still making their descision to purchase Magnova or not.

First, you should keep in mind – Batronix uses this forum as a free-of-charge advertisement platform.

If that means a manufacturer actively engaging with (potential) users, then bring that on all day long. This is the sort of thing that can be a major buying factor, and benefits both the manufacturer and users.  Yes, it is cheap and effective advertising, but so what? It benefits everyone.

[john74]

And this is basic functionality/a few lines of code.

if you already know the effort, why not share the patch with us
or sell it to Batronix?

sorry, but I get this claims a lot at work...'the device worked until yesterday....can't be a big issue'

[hotze]

[..]
 1:10 probes still are not recognized correctly.
The bug was reported more than a month ago.
[..]

I don't think automatic detection of arbitrary active 1:10 probes is ever going to be implemented.

[KungFuJosh]

[..]
 1:10 probes still are not recognized correctly.
The bug was reported more than a month ago.
[..]

I don't think automatic detection of arbitrary active 1:10 probes is ever going to be implemented.

I don't know whether they plan to add that support or not. Either way, it's a feature request and not a bug, but don't try explaining that to him lol.

[Sorama]

It is not about active probes, is it?

[Andre77]

Btw, 1:10 probes still are not recognized correctly.

Just a quick clarification: are you referring to the following post?

...Probes are not correctly identified at startup. If a 50 Ohm termination was set previously, then a 1:10 probe was connected while the scope was off, the probe was identified (1:10 attenuation is set properly), but the 50 Ohm setting remains active;

In that post, you mentioned that when connecting a 1:10 probe to the powered-off Magnova oscilloscope, the attenuation factor is correctly detected and set on startup, but a previously manually enabled 50-ohm termination on the channel is not automatically disabled.

This behavior is indeed easy to improve, and we’ve just implemented it for the upcoming update: when a 10:1 probe with a readout pin is connected while the Magnova is powered off, the scope will now not only set the 10:1 attenuation on startup, but also automatically disable the 50-ohm termination.

For (active) 10:1 probes with a 50-ohm output, the 50-ohm termination can still be enabled as needed and will continue to persist across restarts.

I don't have an Magnova, but in this case I like to say it is important that you can overwrite the 1:10 detection!

Yes, the settings can be overwritten and will then remain in effect.

[KungFuJosh]

Is he talking about 10:1 or 1:10?

[Andre77]

Is he talking about 10:1 or 1:10?

He wrote 1:10, but I assume he actually meant standard 10:1 probes.

-> Automatically disabling the 50-ohm termination when a probe is detected, so the user doesn’t have to keep an eye on that setting.
This already worked when the probe was connected while the oscilloscope was running, and with the next update, it will also work when the probe is connected while the Magnova is powered off.
As mentioned, all of these automatic settings can still be overridden at any time if needed.

[KungFuJosh]

-> Automatically disabling the 50-ohm termination when a probe is detected, so the user doesn’t have to keep an eye on that setting.
This already worked when the probe was connected while the oscilloscope was running, and with the next update, it will also work when the probe is connected while the Magnova is powered off.
As mentioned, all of these automatic settings can still be overridden at any time if needed.

...and that is awesome.

Just another example of how you actually listen to your users. It's refreshing!

Thanks,
Josh

[Andre77]

ok, now I think there is actually a real bug, in the new version :-)
when you change the y-offset of one of the analog channels (when the measurement is stopped)
sometimes the analog channels are not visible anymore.
happens with mouse and touch....the knob works fine for me.

Dear John,

we’ve built version 1.8.2 this morning. After a few hours of in-house testing here at Batronix, we’re already making it available as a preview.

It includes a fix for the issue you reported above, as well as automatic deactivation of the 50 Ω termination when a probe is connected while the Magnova is powered off.

We’re planning to release it officially next week, but with a long 4-day holiday weekend coming up here, we didn’t want to keep you waiting.

If you prefer, you can of course also wait for the official release.

To install it, you can go to Settings → Update and simply replace latest.updt with preview.updt for the network update. This will download and install the update directly on your Magnova.

Alternatively, you can download it from the link below, copy it to a USB stick, and install it locally:
https://batronix.com/magnova/dist/stable/preview.updt

[kaspich]

[..]
 1:10 probes still are not recognized correctly.
The bug was reported more than a month ago.
[..]

I don't think automatic detection of arbitrary active 1:10 probes is ever going to be implemented.

I don't know whether they plan to add that support or not. Either way, it's a feature request and not a bug, but don't try explaining that to him lol.

Dear professionals.
Dear modern digital oscilloscope users.

Recognition of these probes is already implemented. But one of the settings (50 Ohm impedance) is not correctly modified at startup.

Keep going on!

[KungFuJosh]

Dear professionals.
Dear modern digital oscilloscope users.

Recognition of these probes is already implemented. But one of the settings (50 Ohm impedance) is not correctly modified at startup.

Keep going on!

Learn how to read the thread before continuing to waste people's time with your bad attitude. If you can't recognize that this is amazing customer service, then you don't deserve it. Go enjoy Keysight's customer support. You'll love that. 

we’ve built version 1.8.2 this morning. After a few hours of in-house testing here at Batronix, we’re already making it available as a preview.

It includes a fix for the issue you reported above, as well as automatic deactivation of the 50 Ω termination when a probe is connected while the Magnova is powered off.

We’re planning to release it officially next week, but with a long 4-day holiday weekend coming up here, we didn’t want to keep you waiting.

[john74]

Dear John,
we’ve built version 1.8.2 this morning. After a few hours of in-house testing here at Batronix, we’re already making it available as a preview.

damn, this was quick....of course I downloaded the pre-release version....what should go wrong 

at a first glance, the bug of the vanishing analog signals is fixxed with version 1.8.2 
I will spend some time of the weekend to try and find another one.

Have a nice weekend and keep up the good work

And a question, just for curiosity:
is it always possible to roll back to an older version?
(e.g. the very first v1.0.6 stored on a USB stick)

[KungFuJosh]

is it always possible to roll back to an older version?
(e.g. the very first v1.0.6 stored on a USB stick)

Yes, you can roll back. There might be a limitation to what the filename is, I don't remember if they changed that yet.

Thanks,
Josh

[john74]

Has anybody tried the new counter functionality yet?

I am not sure about the current behavior of the trend chart.

In my opinion the trend chart should be updated automatically after some amount of time
(lets say every second)
if there was no new event, the counter value should stay at the same height and generate
a flat line over time.

In the current implementation you see no update at all of the trend chart
until a counter trigger event appears...

if you are counting a periodical event, that is not a problem,
but with sporadic events the display looks a bit "weird"

or what is your opinion?

[KungFuJosh]

I've used the counter a lot, and have been very happy to finally have a hw counter. That was a feature I looked forward to the most.

I have not tried the trend chart with it yet tho. I'll try it out and see how it behaves. Do you have any screenshots of what you're not liking?

[john74]

Do you have any screenshots of what you're not liking?

of course...see these 3 pictures,
-total counter for digital channel D1 (CAN-Signals)
-voltmeter measurement from CH1 (noise)
-VPP measurement of CH4 (1Khz with noise)
-Period measurement with counter of CH4 (1Khz with modulation)
(just to check the new functions)

screen1, captured after 55s runtime with 565 counter events from CAN-D1
screen2, captured after 220s runtime, with no new counter event...so the timeline of CAN-D1 shows still 55s
screen3, captured after 230s runtime, with new counter events (591)...timeline jumps from 55s to 220s

the data of the D1 total counter is correct, but the presentation is a bit odd in my opinion

[john74]

and here a feature request for the trend charts:
(not sure if it is feasable)

all the traces (curr,min,max,avrg) in the trend chart have the same color.
if the data gets crowded, it's hard to distinguish between them.

One solution to this would be, if you could 'hide' and 'show' them, after the measurement is stopped.
(to check only one of them at a time)

but in the current version, if you disable one of them, the trace is lost and can't be enabled again.


and also a nice feature would be, to be able to place the cursors inside these windows too
(I think there was already some request for that)