LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Can LV2016 32 bit run on Win 10 64 bit?


@Cryotester wrote:

Altenbach- Are you implying that the traditional DAQ won't even function with a 64 bit OS?

Yes. (I had an old NI card (AT-MIO-16E-1, ISA bus!) that is not DAQmx compatible and to just and to just being able to load the code for a side-by side updating to a new card and DAQmx required 32bit windows. (Ultimately, I did not go that way and went with a sbRIO instead, freeing up the computer from any DAQ hardware.It is so much nicer if all daq and drivers can be isolated to standalone hardware. Now the PC program requires just ethernet to communicate)

 

Quote from this page: "Traditional NI-DAQ (Legacy) for PC Compatibles, version 7.5 for Windows Vista/7/8 32-bit. 64-bit versions of Windows are not supported."

0 Kudos
Message 11 of 19
(1,249 Views)

It looks like you can't install traditional DAQ drivers in a 64 bit OS.

 

http://digital.ni.com/public.nsf/allkb/8EC9E81C3DE4E619862573930083BD7A

 

Altenbach beat me.  But really Windows 7 was the first time I think 64 bit OSs started to be more common, and that wasn't released until 2009, and the last update to traditional DAQ was a few years later.

0 Kudos
Message 12 of 19
(1,240 Views)

So can you even get Traditional DAQ for LabVIEW 2016? 

0 Kudos
Message 13 of 19
(1,230 Views)

@dkfire wrote:

So can you even get Traditional DAQ for LabVIEW 2016? 


Yes

 

 
But it also specifically says it must be a 32 bit OS.
0 Kudos
Message 14 of 19
(1,228 Views)

@Hooovahh wrote:

It looks like you can't install traditional DAQ drivers in a 64 bit OS.

 

http://digital.ni.com/public.nsf/allkb/8EC9E81C3DE4E619862573930083BD7A

 

Altenbach beat me.  But really Windows 7 was the first time I think 64 bit OSs started to be more common, and that wasn't released until 2009, and the last update to traditional DAQ was a few years later.


Alright then. I HAVE to do a CLEAN install of WIN 10 32-bit, then reinstall NI2016, 32-bit, then reinstall my other software, which I'm still waiting on whether it'll run on 32-bit or not.

What a cluster, just because we're running a system last built in 2013 with multiplexer boards!

0 Kudos
Message 15 of 19
(1,223 Views)

You might have built your system in 2013, but it looks like those AMUX boards first existed in 1999.

 

http://www.ni.com/pdf/manuals/320253c.pdf

 

That is a long time ago.

0 Kudos
Message 16 of 19
(1,215 Views)

@Cryotester wrote:

@Hooovahh wrote:

It looks like you can't install traditional DAQ drivers in a 64 bit OS.

 

http://digital.ni.com/public.nsf/allkb/8EC9E81C3DE4E619862573930083BD7A

 

Altenbach beat me.  But really Windows 7 was the first time I think 64 bit OSs started to be more common, and that wasn't released until 2009, and the last update to traditional DAQ was a few years later.


Alright then. I HAVE to do a CLEAN install of WIN 10 32-bit, then reinstall NI2016, 32-bit, then reinstall my other software, which I'm still waiting on whether it'll run on 32-bit or not.

What a cluster, just because we're running a system last built in 2013 with multiplexer boards!


Well, if you had planned correctly for device obsolescence you would have updated the test system years ago.  Now, instead of hiring a person to update the system you need to hire several people to: troll E-Bay to find obsolete equipment,  use obsolete knowledge to integrate obsolete software into obsolete environments and operate obsolete systems.  On the bright side, with so much time between updates the operating instructions and installation procedures should be fairly well documented.  


"Should be" isn't "Is" -Jay
0 Kudos
Message 17 of 19
(1,205 Views)

Alright Jeff getting a little harsh there aren't we?  Let's not kick a man when he's down.  

 

It does suck when these types of things happen and I've been on both ends of this as someone who's system crashed and the only path forward was to upgrade, and someone who was brought into fix a broken system only to have to deliver the bad news.  Moving forward I'd say the takeaway is to design new systems with relatively new hardware, and use relatively new APIs, on relatively new operating systems.  I'd expect a system from 2013 to probably be running Windows 7 64 bit which would have forced modern hardware and modern software selection.  If you do need more help than the forums can offer NI has several Alliance Partners that are experts in this kind of thing.

0 Kudos
Message 18 of 19
(1,199 Views)

@Hooovahh wrote:

Alright Jeff getting a little harsh there aren't we?  Let's not kick a man when he's down.  

.


Possibly, it came across harsher than I intended.  I wish I had a regularly updated  interface to make my points in the most effective means 😄  (You know, like the LabVIEW IDE, Computing systems, and test hardware have regular updates)  

 

<Darn, that went back to sounding harsh again didn't it?>

 

You know, I find it beneficial at times that some companies forget to plan for the long term.  More than a few of my client's pay me for the exact advice I intended to pointedly point out to the OP.  

 

I agree that NI Certified Consultants and NI Alliance Partners, can help bring focus to developing sustainable systems that are capable of reducing costs over time with proper design.  

 

You missed a great chance to link to one NI Alliance Partner that manages to keep soup between sternum and spine by keeping that exact business case out front.

 

<Yeah 8-Ball Consulting can help with that>


"Should be" isn't "Is" -Jay
0 Kudos
Message 19 of 19
(1,187 Views)