recommend a USB> ethernet device server for fluke scope meter et. al.

[strantor]

I have a fluke scopemeter 190-104 and I want to be able to connect with it remotely over the internet. I see several usb device servers for sale but reading comments on most of them leads me to believe that if you stray too far from the beaten path (external hdds, printers) you're out of luck. The scope meter uses FTDI drivers so know I'm dealing with glorified serial data and it shows in how slow it takes to suck a recorded waveform out of it. I can't imagine this would be too demanding for most of the USB> ethernet device servers out there, but I'd like to hear some personal experience from someone whose done it (successfully or unsuccessfully) with the scopemeter (or at least any other FTDI device) prior to making a purchase.


...AND if that weren't enough,  I'm considering purchasing a USB logic analyzer, most likely zeroplus,  and I predict that will be asking a whole lot more from the usb device server. So has anybody got an idea what USB server would work with a device like THAT?

[Rasz]

dont know about brand new plug&play black boxes, but if its FTDI you can just re-purpose any Openwrt router with USB port/rasppee.

[strantor]

Checking back in here to let you all know what I found. I bought this fancy black box for $100 USD: (Industrial USB 2.0 Over IP Network 4-Port Hub). It worked great for the Fluke 190 series II Scope, and also my el-cheapo Hantek 108 8-channel "scope." It also worked for Arduino, my camera, my Samsung Tablet, external HDDs, etc. The software is very intuitive and easy to use. I recommend you try this device first if you're looking for something similar, as you won't find anything more functional for less money.

The bad: It wouldn't connect to Omron PLC or Yaskawa VFD, which is a big deal for me. I am still looking for a product that meets ALL my needs. And when it doesn't like a device, it doesn't complain with a nice popup, it throws a wrench into your processor (BSOD).  The other negative is minor for me, may be major for you; your PC's IP address must be in the same IP subnet as the USBNET device. If they aren't in the same subnet, the USBNET software will still recognize the device, but won't let you connect to it and use the attached USB devices.

[David Hess]

... The other negative is minor for me, may be major for you; your PC's IP address must be in the same IP subnet as the USBNET device. If they aren't in the same subnet, the USBNET software will still recognize the device, but won't let you connect to it and use the attached USB devices.

That is weird.  I would expect it to take deliberate effort to create a restriction like this.

Maybe it relies on IP multicast for device discovery or configuration.