Top products from r/LabVIEW

We found 12 product mentions on r/LabVIEW. We ranked the 7 resulting products by number of redditors who mentioned them. Here are the top 20.

Next page

Top comments that mention products on r/LabVIEW:

u/ultralame · 2 pointsr/LabVIEW

You have a lot of choices.

Ultimately it looks like you want to use physical relays (most allow signals up to 250V). You could either use a dedicated multiplexing board (The board is wired such that only one path is connected at a time), or you could use a bank of relays and wire them so that all their common outputs are tied together, and then you just write code that only allows for one connection at a time.

What's most important to you, Cost or Hardware quality?

_

If cost is important, go for an arduino + relay board, like this...

https://www.amazon.com/LANDZO-8-Channel-Relay-Module-Arduino/dp/B01NBUDHPB/ref=sr_1_1?ie=UTF8&qid=1500396954&sr=8-1-spons&keywords=arduino+relay&psc=1

The cheapest thing to control it would be something like an arduino microcontroller:

https://www.amazon.com/Arduino-Uno-R3-Microcontroller-A000066/dp/B008GRTSV6/ref=sr_1_3?ie=UTF8&qid=1500397057&sr=8-3&keywords=arduino+uno

You would write you code in LV, which would use a serial message to control the arduino. The arduino has digital outputs that would drive the relay board.

The code on this is not terribly complicated, but you would not be using DAQ drivers, but the VISA serial messaging and you would have to deal with a USB com port on the PC. This adds a little complexity and possible failure mode. This is what I would use in my own home for an inexpensive, non-critical application. You can even get cheaper controllers and relays, but we're talking $40 here.

Another advantage of the arduino is that you could put a fairly simple protection circuit into the controller code, so that if something goes wrong at the PC level or you generate a bug that the relays can shut down or be more sure that they won't short circuit two paths.

_


To go the other route, where money is no object (or you need a very robust, mission critical system) and want overly simple programming, you could go with an NI relay board on a PXI chassis. That's going to run in the thousands of bucks, but if I was shipping this off to China on a test rig that I never wanted to have to fix, that's what I would use.



In a local environment where I could easily support a problem (and a problem wouldn't cost us $50K a day), for an employer that would want a compromise between cost and my time, I would probably use an NI-USB 9174 chassis + 2 9482 relay modules. This will run about $1200, but is reasonably robust and very simple to program and is practically plug-and-play in terms of hardware. Remember that to a reasonably sized employer, you cost about $100/hr considering benefits and such. So if you can save 4-8 hours of learning/programming/debugging/wiring/soldering, it's a wash.

____

Lastly, I recently saw an Industrial Arduino, which is a relatively inexpensive way to get the cost down but beef up the hardware, for about $200. With one of those, I would not use that cheap relay board, but probably find a set of DIN mount discreet, industrial relays, about $20-50 each.

If this was the solution, I would spend some time to figure out how to talk to the arduino over some other method of communication, other than USB. It's been my experience that USB can be a source of pain in the ass-ness. Driver updates can break things, plugging something else in can break things, hubs can cause headaches, even certain brands of PC come with shit USB controllers that refuse to play nice once in a while.

IF you do use PC + USB in a production environment (which I have done, many times), I suggest buying a dedicated PCI/PCIe USB controller (and get a couple replacements), so that you are not at the mercy of shitty motherboard design or having to deal with driver changes if IT tells you you have to change out the PC.

(OK, I'm getting ahead of myself here)



Note: For all of these solutions, even the serial programming is simple, so it's really about how stable/robust the hardware is. With the arduino, you are relying on relatively inexpensive non-industrial boards that have a relatively high failure rate, along with a bit of your own wiring and a separate code base on the controller. That's not necessarily bad, but I wouldn't send that up on a satellite- and I have actually programmed QA for satellite parts- that's when you spend $10K to get a bank of relays that you don't have to worry about.

u/ElectricWraith · 1 pointr/LabVIEW

Find a project! LabVIEW's WAY too much to dive into without a specific goal to guide your efforts. I'd recommend (as I always do in these threads) picking up a copy of LabVIEW for Everyone ( https://www.amazon.com/LabVIEW-Everyone-Graphical-Programming-Made/dp/0131856723 ) for a readily accessible reference.

Do yourself a favor and avoid posting on the NI forums (they can be a bit on the snarky side), but definitely use the site as a reference.

u/quantum0058d · 2 pointsr/LabVIEW

> My supervisor wants to have an option in the main VI to choose one of the circuits. How can I go about doing this?

An event loop which takes an input and then conditionally runs the code.

Best to start at basics:

https://www.amazon.com/LabVIEW-Everyone-Graphical-Programming-Made/dp/0131856723

u/trigger5365 · 1 pointr/LabVIEW

Honestly, unless you are trying to do this as a project to learn, you are going to save an incredible amount of time (and maybe money) by buying an off the shelf usb barcode scanner for $20. These scanners work as input devices, like a keyboard, and require no programming to get started. You may want to add a little code to restrict where it can input data in your program, but otherwise it is a very simple application.

u/rofex · 1 pointr/LabVIEW

Look no further. This book here is all you need. Comes with a CD and everything. I found it very useful.

u/wolfcry0 · 3 pointsr/LabVIEW

These units have an ESP8266 inside that can be programmed using the Arduino libraries for it, you could pull data from that over HTTP or UDP or something.

u/steelpickled · 6 pointsr/LabVIEW

Here is a student version of labview plus an Arduino for $50.

https://www.sparkfun.com/products/11225

You can use the arduino for real data acquisition and output. You can also learn labview and the arduino idk, which is C or something similar.

I have also found that this is a good reference book even though it is for version 8.

http://www.amazon.com/LabVIEW-Everyone-Graphical-Programming-Edition/dp/0131856723/ref=sr_1_2?ie=UTF8&qid=1405129568&sr=8-2&keywords=jim+kring

Let me know if you need any ideas for projects!

u/infinitenothing · 1 pointr/LabVIEW

USB is the worst protocol if you need that distance. You might want to put a cheap headless computer at the other end and retransmit over ethernet, wifi, etc.

Another option for USB is to use an active repeater chain:
https://www.amazon.com/Geplink-Extension-Amplifier-microphone-bluetooth/dp/B00XPBRSPG