Where can I find old "write to digital port.vi"

[WaterCal]

I have an old (like 20 year old) LAbView project that I would like to get up and running. Unfortunately it uses one of the old LabView library vi's, Write to Digital Port. Is there anywhere that I can download that old vi?

Thanks 

WaterCal

[RavensFan]

That sounds like one that was a part of the traditional NI-DAQ drivers.

Replace that with DAQmx.

That means some partial rewriting of your VI's.

[WaterCal]

Yes, understood. I was trying to avoid the rewrite. Someone else wrote the old project and I'm not much of a developer , although could if I had to 🙂 . If I had the old vi (or library) I could just point to it and the project would run. So I was hoping there was an archive somewhere, or someone might have it.

[altenbach]

---

@WaterCal wrote:

If I had the old vi (or library) I could just point to it and the project would run. So I was hoping there was an archive somewhere, or someone might have it.

---

No, it won't be that easy. While traditional DAQ is still available, it won't run on any 64bit OS and also windows 10 is not supported.

[RavensFan]

---

@WaterCal wrote:

Yes, understood. I was trying to avoid the rewrite. Someone else wrote the old project and I'm not much of a developer , although could if I had to 🙂 . If I had the old vi (or library) I could just point to it and the project would run. So I was hoping there was an archive somewhere, or someone might have it.

---

I'm afraid you will have to do some rewriting!

It isn't that bad, mostly replacing old NI-DAQ subVI's with their DAQmx equivalents.

Read Transition from Traditional NI-DAQ (Legacy) to NI-DAQmx in LabVIEW for some guidance.

[WaterCal]

OK. Thanks very much for pointing me to the tutorial. I'll let you know how painful it was after I'm done.

Cheers!

[MrJackHamilton]

Going to second the advise here. There are no one-to-one replacement VI(s) for the old traditional DAQ suctions. DAQmx is the new functions to use. However, they are different in ways that would be 'complex' to a novice user.

Having coded in LabVIEW 1.1.0 to the current version, I would recommended you start with MAX and create a 'Virtual channel' or 'Virtual task' for the signal you are wanting to duplicate. This provides for you to select the physical DAQ device, channel and type of signal. Within MAX without LabVIEW coding, you can actually operate the DAQ hardware from MAX to actually test the control or acquisition of the signal.

Once you have that task saved in MAX, you then open LabVIEW and drop the MAX Task on the LabVIEW diagram and it can create the basic LabVIEW function to perform that task within LabVIEW.

If you have problems, contact me. I'm happy to help within limits to get you back on the road....My offer is free. Although we do consulting in LabVIEW based test systems.

As your working with old LabVIEW legacy code. Your issue is unique and we have experience using early LabVIEW...originally, LabVIEW was in B&W.

Regards

Jack Hamilton

[screen_fan]

Hi, If the traditional DAQ won't run any 64bit OS, is it then safe to assume if we run LabVIEW 2014 (for instance) with the traditional DAQ in a 32bit OS this would fix the problem? 

[billko]

---

@screen_fan wrote:

Hi, If the traditional DAQ won't run any 64bit OS, is it then safe to assume if we run LabVIEW 2014 (for instance) with the traditional DAQ in a 32bit OS this would fix the problem? 

---

It's not "safe to say" but I think it's more Windows version dependent.  https://www.ni.com/en-us/support/documentation/compatibility/22/traditional-ni-daq--legacy--windows-... 

[crossrulz]

---

@screen_fan wrote:

Hi, If the traditional DAQ won't run any 64bit OS, is it then safe to assume if we run LabVIEW 2014 (for instance) with the traditional DAQ in a 32bit OS this would fix the problem? 

---

At this point, I would do a rewrite of the application to use DAQmx.  Just make sure the version you use still supports the hardware you are using.  Go through the Readme files to verify.