Labview 7.1 executable on win7 64 bits

[seedbarrett]

Hi everyone

I'm currently working on a project using LabView and a PIC 18F2550. I'm not the initiator of the project, I just continue the work previously done. I got a problem, when i connect my device using the PIC on my new 64bits PC it seem that the .exe file don't recognize my device, but windows do. The drivers are from microchip so i guess they must be fine ! 

I have no idea where is the problem, in addition it work on my old windows XP 32 bits perfectly. Maybe because it's labview 7.1 ? On a 64 bits OS ? If i upgrade to a newest version it will be good ? If not, do you thing is a problem from my program ? The VID and PID seems good and it work on another computer..

Thanks for your help ! 

[nyc_(is_out_of_here)]

---

@seedbarrett wrote:

Hi everyone

I'm currently working on a project using LabView and a PIC 18F2550. I'm not the initiator of the project, I just continue the work previously done. I got a problem, when i connect my device using the PIC on my new 64bits PC it seem that the .exe file don't recognize my device, but windows do. The drivers are from microchip so i guess they must be fine ! 

I have no idea where is the problem, in addition it work on my old windows XP 32 bits perfectly. Maybe because it's labview 7.1 ? On a 64 bits OS ? If i upgrade to a newest version it will be good ? If not, do you thing is a problem from my program ? The VID and PID seems good and it work on another computer..

Thanks for your help ! 

---

Your guess is as good as ours as to what may be the problem.

Try debugging with the source VI.

[seedbarrett]

But the same exe is working on XP and not on 7, so i think the source VI is fine ?

[nyc_(is_out_of_here)]

---

@seedbarrett wrote:

But the same exe is working on XP and not on 7, so i think the source VI is fine ?

---

You think?

[Bob_Schor]

LabVIEW 7.1 is not supported under Windows 7 (either 32 or 64-bit).  LabVIEW 2009 is the earliest version supported by Windows 7.

I had some code that ran on a Windows XP machine and was developed in LabVIEW 7.0.  To continue development, I created a Windows XP VM (VMWare) that had LabVIEW 7.0 installed, and my executable ran fine on the Windows XP machine connected to my hardware.  I've recently moved my code (with a lot of rewriting -- the original LabVIEW 7 code was pretty disorganized) to LabVIEW 2012 and Windows 7, and it is much easier to maintain, runs at least 5 times faster, much smoother process.

BS

[nyc_(is_out_of_here)]

I was able to get LabVIEW 6.1 source code to run in Windows 8.1 Professional.

It depends on what is in the original source code.

[seedbarrett]

Ok so the problem come from the guy before me and there surely have mistakes in the code, or at least i must rewrite a part. Thanks for the advice, and yes i think a new LabView could be pretty nice, but i'm not the leader of the compagny 🙂

[Bob_Schor]

---

@nyc_(is_out_of_here) wrote:

I was able to get LabVIEW 6.1 source code to run in Windows 8.1 Professional.

It depends on what is in the original source code.

---

I'll wager that your "LabVIEW 6.1 source code" running on Windows 8.1 was being executed by a more recent version of LabVIEW than 6.1!  The problem here isn't really the "source code", but the development environment, namely LabVIEW 7.1 development tools on a Windows 7 computer.

Much of the code should "upgrade" with little change, and those functions that have become superceded will (usually) reveal themselves.  However, there is a lot that is "new and improved" (can you say LabVIEW Project?) that will handsomely pay off the effort to at least partly, if not fully, "refactor" for LabVIEW 20xx.

BS

P.S. -- I'm the Last of the Big-Time Gamblers -- the bet is $0.10, my usual ...

[nyc_(is_out_of_here)]

---

@Bob_Schor wrote:

---

@nyc_(is_out_of_here) wrote:

I was able to get LabVIEW 6.1 source code to run in Windows 8.1 Professional.

It depends on what is in the original source code.

---

I'll wager that your "LabVIEW 6.1 source code" running on Windows 8.1 was being executed by a more recent version of LabVIEW than 6.1!  The problem here isn't really the "source code", but the development environment, namely LabVIEW 7.1 development tools on a Windows 7 computer.

Much of the code should "upgrade" with little change, and those functions that have become superceded will (usually) reveal themselves.  However, there is a lot that is "new and improved" (can you say LabVIEW Project?) that will handsomely pay off the effort to at least partly, if not fully, "refactor" for LabVIEW 20xx.

BS

P.S. -- I'm the Last of the Big-Time Gamblers -- the bet is $0.10, my usual ...

---

All I installed was LabVIEW 6.1, NI-488.2, and NI-VISA.

No other versions of LabVIEW on that laptop. It was clean of all NI software when I started that job.

Many people spout the mantra about which versions of LabVIEW will work or not work without actually having the experience.

I was fully prepared to ask management to buy a newer version of LabVIEW if needed. It wasn't.

[Bob_Schor]

LabVIEW 7.1 came out in 2004, which means that there has been a decade's worth of improvements made, many of which have made LabVIEW (a) significantly faster in execution speed (due to better code and better code optimization), (b) a significantly easier development environment, (c) provide many more functions and toolboxes to ease development tasks, and (d) provide better Documentation, Help, and Examples.  If you haven't upgraded since then, and you really want to keep your 10-year-old product working (with modern PCs and Operating Systems) and up-to-date, I think a strong case can be made for acquiring LabVIEW 2014!

Bob Schor