![ni-daqmx driver support for labview 2017 is missing ni-daqmx driver support for labview 2017 is missing](https://s1.manualzz.com/store/data/048717592_1-c32b5e26d12992b6d836401c5e04b70e.png)
- #NI DAQMX DRIVER SUPPORT FOR LABVIEW 2017 IS MISSING HOW TO#
- #NI DAQMX DRIVER SUPPORT FOR LABVIEW 2017 IS MISSING CODE#
- #NI DAQMX DRIVER SUPPORT FOR LABVIEW 2017 IS MISSING LICENSE#
#NI DAQMX DRIVER SUPPORT FOR LABVIEW 2017 IS MISSING HOW TO#
My issue I think is that when I want to do something in LabVIEW, I can see in my mind exactly what I want to be done- but get stuck again and again when working out how to implement it, as the LabVIEW way of doing things seems completely unintuitive to me, and I can’t see the way to solving my problems, because I can’t see where to look. However, the only times I’ve managed to get them to do exactly what I want), is when I’ve programmed them in C (not real impressed with ni-daqmx c api either, but can work it out), or using COMEDI. We have a few ni-daq cards around too, with great looking features on them.
#NI DAQMX DRIVER SUPPORT FOR LABVIEW 2017 IS MISSING LICENSE#
I’ve tried many times to get into labview, as there are so many people around where I work who use it and swear by it, and in fact we have a site license so it’s free if I want it. Makes me wonder just how many people out there type “I HATE LABVIEW!” into Google searches!”Īctually, I typed “Labview sucks”, and this is what I found =) “I think this post is kind of hilarious, since it’s old and I keep getting comments on it. If I ever get offered a job where I have to work with LabVIEW I will turn it down immediately. If I have to work 3 times as hard to do my job so some non-programmer can understand my work by “looking at the pretty pictures”, then I want doctors to do dumb down their work so I can understand how they do their jobs. Most of all, it completely violates the philosophy of programming because it takes something that is simple and makes it ten times more inefficient.Īnd the reason my professor says people like it: its graphical and so non-computer engineers can understand it. Its frustrating to even get a case structure set up and even more so to get nested loops set up without the program freezing. Its messy and there are wires everywhere. I have no idea how to follow someone else’s program because I don’t know where the program “starts”. Its impossible to debug and figure out where problems lie. Now this semester I’ve been introduced to LabVIEW and I hate every minute of it. Last semester I had to program in C++ and I absolutely loved it. I am a student at Stevens and am required to take a Design Lab.
#NI DAQMX DRIVER SUPPORT FOR LABVIEW 2017 IS MISSING CODE#
I wouldn’t mind it if they changed arrays, changed navigation and zoom, and added scripting support…so you could make blocks of scripted code for those times when something graphical is just wayyyyy too needlessly complicated. And seriously…who was in charge of the mouse UI!? Each attempt to make a long wire or scroll the screen was one step closer to dumping Labview completely…which we did. Downside: Labview is graphical, so it’s impossible to add features in a timely manner when specifications change. My conclusion: Upside: Labview is interesting because it’s graphical. Things that took screens and screens in labview took a page of infinitely editable lines…with comments on every one if you want! With that and some run-ins with version compatibility problems…we’ve now moved to an easy to use text based language and never looked back. Towards the end, after I showed some higher ups what it took to maintain, I was pretty much told to screw neatness and get the feature added. We had to add features…it took HOURS UPON HOURS to move all the damn little wires around. We had some part screening programs that were made by some former engineers. MY LAB RUNS ON IT AAAAAAAAAAAAAAAAAAAAHHHHHHHH!!!!!.It handles arrays in an extraordinarily clunky manner–and when you’re taking data, the role LabView is best suited for, MOST OF THE TIME YOU CAN’T POSSIBLY AVOID USING ARRAYS!.Shift registers and sequence instances! The saddest excuses for variables on the planet–and they contribute to the messy wiring problem!!.The fact that it has to rebuild all its data acquisition sub-VIs every time I want to make a tiny change to the sampling mode!.Timing structures–THEY DO NO SUCH THING!.Mouse sensitivity! As in, my programming ability should not have to rely on my skill to accurately position the mouse over some of those frakking tiny terminals!.Sequence structures–the most cumbersome way possible for the LabView creators to have tried to rectify the problem that sometimes YOU JUST NEED TO EXECUTE COMMANDS IN ORDER JUST LIKE A CONVENTIONAL PROGRAM, DAMMIT!!!.Computer processors operate linearly anyway–LABVIEW IS LYING!!!.
![ni-daqmx driver support for labview 2017 is missing ni-daqmx driver support for labview 2017 is missing](http://artsdocbox.com/docs-images/93/112133475/images/229-0.jpg)
Extreme difficulty to insert new commands into an established program without ruining the organization structure!!.Messy, horribly hard-to-follow programs! Wires everywhere!.Nonlinear, graphical programming interface:.Inability to write descriptive comments!.