Main idea was to use small adapter (like mouse receiver) and do not use ethernet cable at all..
Main idea was to use small adapter (like mouse receiver) and do not use ethernet cable at all..
Why? Use a short ethernet cable, mount the mini bridge on the back, and you don't have to look at it. Otherwise you're giving up some % of processing power to support WiFi, and then only with limited options for which dongle to use.
Personally, I prefer ethernet only to avoid extra RF interference.
Main idea was to use small adapter (like mouse receiver) and do not use ethernet cable at all..
Why? Use a short ethernet cable, mount the mini bridge on the back, and you don't have to look at it. Otherwise you're giving up some % of processing power to support WiFi, and then only with limited options for which dongle to use.
Personally, I prefer ethernet only to avoid extra RF interference.
And to save the USB ports for things they are probably meant for, like a mouse and a couple of power supply cables for differential probes.
I have no idea if USB WiFi dongle will use more CPU power than wired ethernet adapter (depends on many factors).
USB ports already have some linux drivers (for example, mouse), so why not add more drivers to a system?
This will not dedicate some USB port for WiFi, it will just add more flexibility for all ports.
Not everyone uses scope as stable not-movable device attached to concrete wall with anchors
For example, you have to move oscilloscope within your lab to different places and want to save screenshots to SMB share.
With WiFi support, you can just find a wall socket with 230v inside, not triyng to find ethernet or attaching wifi router to scope
I think, possibility to use WiFi USB dongle will just add flexibility not removing any existing features.
In theory a good idea, but I am not aware of a wifi adapter where you don't need to install some sort of driver. And without root access to the system I don't think it would work. And on my scope I don't want to troubleshoot at the OS level when the adapter is causing crashes.
In theory a good idea, but I am not aware of a wifi adapter where you don't need to install some sort of driver. And without root access to the system I don't think it would work. And on my scope I don't want to troubleshoot at the OS level when the adapter is causing crashes.
On Linux (which most of the scopes run on nowadays), things like Wifi adapters just work out of the box.
On Linux (which most of the scopes run on nowadays), things like Wifi adapters just work out of the box.
That's only true if the libraries are loaded. Most scopes, IIRC including this one, are usually on custom Linux installs.
Not everyone uses scope as stable not-movable device attached to concrete wall with anchors
Very true. IMO cabled networking rules, so my solution was to have RJ45 connections all over the place; but having done that I must admit that Wifi takes a lot less effort
And drivers for USB Wifi adapters could be a nice addition to the scope. Not used by me as I am already low on USB connections, but certainly handy for some.
On Linux (which most of the scopes run on nowadays), things like Wifi adapters just work out of the box.
That's only true if the libraries are loaded. Most scopes, IIRC including this one, are usually on custom Linux installs.
And even when a Linux OS is installed you'd still need to access it to enable any WiFi dongle drivers.
Otherwise the scope OS/App needs to access the WiFi dongle drivers
and provide a UI to setup the WiFi AP and PW.
On Linux (which most of the scopes run on nowadays), things like Wifi adapters just work out of the box.
That's only true if the libraries are loaded. Most scopes, IIRC including this one, are usually on custom Linux installs.
Sure. But nowadays it is more work to cut stuff like Wifi out compared to keeping it as-is. The days that every MB counted are long gone.
Sure. But nowadays it is more work to cut stuff like Wifi out compared to keeping it as-is. The days that every MB counted are long gone.
Including a library requires...including a library. As Rob said, that's just the first part. In any case, if you're not planning on including WiFi, then why would you bother doing anything that has
any negative impact on resources?
Who knows, maybe they will add it at some point.
Also, WiFi is security atack vector...
Sure. But nowadays it is more work to cut stuff like Wifi out compared to keeping it as-is. The days that every MB counted are long gone.
Including a library requires...including a library. As Rob said, that's just the first part. In any case, if you're not planning on including WiFi, then why would you bother doing anything that has any negative impact on resources?
The thing is that modern day embedded Linux distributions (typically based on Debian or Ubuntu) come loaded with everything. Removing stuff is typically more work than adding. The days of tinkering with openembedded / Yocto or buildroot are long gone (except for those who like to suffer and waste their time). Ofcourse I can't look inside the Magnova OS build but likely most of the Wifi software infrastructure is already there. Without negative impact.
Also, WiFi is security atack vector...
Who cares. LXI has no protection whatever and allows full access to a device without providing any credentials. Web interfaces typically don't even use https. You can't connect test equipment to a corporate LAN and expect it to be secure.
Also, WiFi is security atack vector...
Who cares. LXI has no protection whatever and allows full access to a device without providing any credentials. Web interfaces typically don't even use https. You can't connect test equipment to a corporate LAN and expect it to be secure.
You and I do not. But IT police takes no prisoners and do not negotiate.
In places where such thing is a thing, you need to be able to say "It is not supported at all".
This might be an interesting accessory:
https://www.amazon.com/dp/B0DY8K122V/The TL-WR3002X is WIFI6, and has built-in microSD and USB ports that can allegedly be used for SMB / other file sharing methods.
This might be an interesting accessory: https://www.amazon.com/dp/B0DY8K122V/
The TL-WR3002X is WIFI6, and has built-in microSD and USB ports that can allegedly be used for SMB / other file sharing methods.
I have that one. Works pretty good for what it is. Even has 3 power settings, with low outputting 10mW (if you want to keep RF polution relatively small).
I tried out the TL-WR3002X. It works fine (ethernet to scope, USB port for power).
I put a USB flash drive in it, and set it up as an SMB. That also worked fine. It uses SMB 2.1. Screenshot from SMB save attached.
I did a speed test- with my desktop wirelessly connected to the TL-WR3002X (wireless to source router), it did about 108Mbps. The desktop wired to the real router is about 548Mbps. Either should be good enough for an oscilloscope.
Besides that, it was nice to see the Magnova had no trouble switching between the routers with different subnets, and still had access to both SMBs either way.
Thanks,
Josh
Besides that, it was nice to see the Magnova had no trouble switching between the routers with different subnets, and still had access to both SMBs either way.
Did you keep the TL-WR3002X in router mode? Why not let your main router take care of that, so you don't have multiple subnets???
Besides that, it was nice to see the Magnova had no trouble switching between the routers with different subnets, and still had access to both SMBs either way.
Did you keep the TL-WR3002X in router mode? Why not let your main router take care of that, so you don't have multiple subnets???
I did not. I followed the screen prompts to add it as an access point. I honestly didn't put much thought or effort into it, which was important for proper evaluation.
I actually like how little thought I put into it, including that it asked me to update the firmware and all I had to do was click one button. I downloaded it ahead of time for now reason lol.
Thanks,
Josh
Ok. Yeah TP-Link has quite a few interesting products lately.
Yeah, I like them. I use a lot of their Kasa stuff too.
I’m very interested in the Magnova scope. I understand that Batronix has plans to make this available in the US for personal use- are there any updates on this? I know that with our “dear leader” handing out tariffs like candy, it’s hard for any company to make long term plans- US or international. But it would be nice to have a rough idea of a timeline.
As a side note, I sent an email to service@batronix.com with this question, but never got a reply. So a couple of weeks later I tried with a different email account, and still no answer.
Thank you for your interest in the Magnova scope.
We had planned to complete the required U.S. approvals by the middle of last year. However, due to a period of significant regulatory and economic uncertainty, we decided to pause the project rather than move forward under unclear conditions.
We recently restarted the process, and we’re cautiously optimistic that we can complete it within the next three to four months.
Not everything was put on hold during the pause. For example, we had already begun the US trademark registration for “Magnova” at that time, and that lengthy process has since been completed.
Regarding your emails, that’s definitely not our goal. All inquiries should be answered, and I’d like to look into what went wrong in this case.
If you're comfortable doing so, please send me a private message with the email address you used (or the name you included in the message), and I'll look into it internally.
Any update on US availability? I understand that corporate things often move slower than we hope/expect, at least that was generally my experience during my career! And of course, the US tariff policy is still about as chaotic and senseless as before. Still, an update would be appreciated.
On the communication subject, in mid January I signed up for the Batronix newsletter. I never received a response of any kind, and since then have never seen a newsletter. Is the newsletter still active? If so, then I think I still have the "email black hole" issue I mentioned previously. I did check a month ago, and tried to re-signup. But the Magnova said the email was already subscribed, so it is in the system.
Thanks!
Regarding the US approval process (CB procedure and cTUVus certification): Thanks for asking - I understand that an update is appreciated, especially since this has taken longer than we had hoped. I spoke with the responsible TÜV inspector this morning. The first part of the approval process has been completed. Unfortunately, the second part will only start at the beginning of July, as the TÜV test laboratory is currently very busy. TÜV expects this second part to take around 4 weeks. We hope that after that, the remaining steps will not take too much longer.
Regarding the Magnova newsletter: so far, we have informed existing Magnova customers directly by email about firmare updates, and we have not sent out messages through the Magnova newsletter. That said, I fully understand that people who are not yet customers and not following this EEVblog thread would also like to stay informed. For future updates, we will make sure to also send the firmware update information also through the Magnova newsletter.
Thanks again for your patience and for pointing this out.
No teardown? Why turn on the scope if you can take it apart?
