LabVIEW
There may be a problem installing LabVIEW 2017 "on top of" earlier versions
Solved!
Is this specific to installation via the "stick" you mentioned? I'm also using a Dell Laptop, running Windows 10 x64, and have installed (at present) LabVIEW 2016, 2017 and the NXG beta (although I haven't used it enough to say if its working as intended).
My MAX version is 17.0.0f0 and appears to be working - yesterday I used it to demonstrate how to create a DAQmx Task as a comparison with the NXG version and I was able to place it on a 2017 block diagram. I didn't run the task, because I didn't have hardware to hand, but it looked like it should have worked.
I have 24 services running that begin with NI, although at least 3 are related to OPC and my guess is some of the others might be related to other toolkits that perhaps aren't on the "stick" you mentioned.
My installation process was just to download the installer for 2017, then run the installation. I saved the files so that I could copy them to another computer later (although was disappointed that the choices I made weren't saved somehow - I accidentally picked slightly different options on the second computer and it then began downloading more things).
As I recall, I installed DAQmx 17.0.0 after LabVIEW, and since then the update service has updated to 17.1.0. I don't think I have installed any other 2017 toolkits/packages yet.
@cbutcher wrote:
Is this specific to installation via the "stick" you mentioned? I'm also using a Dell Laptop, running Windows 10 x64, and have installed (at present) LabVIEW 2016, 2017 and the NXG beta (although I haven't used it enough to say if its working as intended).
You raise a very good/interesting point. When I was discussing this issue with NI Support, I was careful to mention that I was working from a "known installation point", namely the USB Key that contained the 2017 Software Bundle. I assumed that the software on the stick was the same as the software downloadable on a module-by-module, toolkit-by-toolkit basis, would be the same. I also very carefully documented my Installation steps, including at which steps NI Services "disappeared".
One thing that seems to be (in my hands, anyway) critical is that both LabVIEW 2016 and LabVIEW 2017 run fine on my PC if they are the only version installed, but LabVIEW 2017 installed "on top of" LabVIEW 2016 causes MAX to fail. Indeed, even when I installed LabVIEW 2017 solo on this PC, MAX wasn't quite right, as shown below.
I can think of a few possibilities (and there are probably more) why I'm having a "2017 problem" and others are not.
- I'm installing from the Spring 2017 Software Bundle, which is subtly different from installations from the Web. This seems unlikely to me, but certainly something that NI Support could check out.
- I'm installing LabVIEW 32-bit + Vision Development Module (similar to installations from 2012 on). Maybe Vision is "clouding things up". Seems unlikely, but I've documented what I did so that NI can try to reproduce and diagnose what is going on.
- There's something really flakey with my hardware. Again, that seems unlikely, as it is a standard Dell machine, plus there have been other reports on the Forums about problems with MAX 2017 (which led to my trying this myself), so there must be something there ...
- Maybe this is a "Windows 10" thing. Microsoft keeps "improving" Windows 10. First, there was Windows 10, then there was Windows 10.1 (Anniversary), now there's Windows 10.2 (Creators). [Note -- I'm being facetious with the numbers, of course]. I just checked -- my Laptop is running Creators (I have no idea when it updated itself to this new edition).
I do have a "Day Job", and do have a project being developed in LabVIEW 2016 that needs LabVIEW, Vision, and MAX all working, so I'm going to be handing this back to NI, with fairly complete documentation of my findings, in hopes they can find and/or understand the issue, and possibly even fix it.
This, incidentally, is what MAX shows on my Laptop after installing LabVIEW 2017 alone (having done as complete an uninstall of LabVIEW as practical, including deleting all LabVIEW folders from Program Files, Program Files (x86), and Program Data). Note that it shows both a USB 6002, with its proper Driver, and my Laptop's Camera (I installed the Vision Acquisition drivers), but the pane on the right doesn't show anything. On the "Bad MAX" (seen on the 2016+2017 install), the pane on the right showed some information + an error message about a timeout, but the Devices didn't show the Cameras, and the USB 6002 driver never loaded, leaving it with a VISA designation.
Bob Schor
Bob_Schor wrote:I can think of a few possibilities (and there are probably more) why I'm having a "2017 problem" and others are not.
- I'm installing from the Spring 2017 Software Bundle, which is subtly different from installations from the Web. This seems unlikely to me, but certainly something that NI Support could check out.
- I'm installing LabVIEW 32-bit + Vision Development Module (similar to installations from 2012 on). Maybe Vision is "clouding things up". Seems unlikely, but I've documented what I did so that NI can try to reproduce and diagnose what is going on.
- There's something really flakey with my hardware. Again, that seems unlikely, as it is a standard Dell machine, plus there have been other reports on the Forums about problems with MAX 2017 (which led to my trying this myself), so there must be something there ...
- Maybe this is a "Windows 10" thing. Microsoft keeps "improving" Windows 10. First, there was Windows 10, then there was Windows 10.1 (Anniversary), now there's Windows 10.2 (Creators). [Note -- I'm being facetious with the numbers, of course]. I just checked -- my Laptop is running Creators (I have no idea when it updated itself to this new edition).
Following up on this with some additional information about my system:
- I don't believe I installed the Vision toolkit, although it does appear on the splash screen when LabVIEW loads. The Licence Manager lists the following as activated in 2017 LabVIEW:
- Development System
- Advanced Signal Processing Toolkit
- Application Builder
- Control Design and Simulation Module 2017*
- Database Connectivity Toolkit
- DataFinder Toolkit
- Datalogging and Supervisory Control Module
- Digital Filter Design Toolkit*
- Mathscript RT Module
- Real-Time Module*
- Report Generation Toolkit for Microsoft Office
- Robotics Module*
- Statechart Module*
- Unit Test Framework Toolkit
- VI Analyzer Toolkit
- The items with an asterisk have 73 days remaining at present. This appears to be because they are licensed with a beta key. I'll look into switching that for a real key but I don't seem to be able to unregister or register these items, so probably they're not currently installed.
- I'm also running what I believe to be the Creators Update on Windows 10 Pro. Version is 1703 and Build is 15063.413. I can't swear to it, but I think the update arrived on this computer before I installed LabVIEW 2017.
