Upconvert VI Requests

[DonRon1972]

---

@Ray.R wrote:

Guys....

Don,

This thread is intended for upconverting vi's not to discuss fixing code.

---

This is code that worked very well. I was up-converting but your definition of up-converting and fixing code must be difference than mine. What happens here? Do you run the code through NI software to convert? If so then you are correct I'm in the wrong place. I did convert to 2010 and fix most of my code but for the DIO access code. I expect professional behavior from myself and the people I deal with, I did lose my cool for that I'm sorry; I was acting like a child. I have a hard time not reacting to rude comments from online forms. I try to stay away from discussion forms because some people hide behind the shroud the web provides to trash people and there work.

---

@Ray.R wrote:

Guys....

 I checked one of the 3 vi's that you posted and it was already at LV2010.

The problem is that it is missing the .lsb (CIN) file.  That file is probably with the Legacy DAQ stuff.  Unfortunately, I do not have any Legacy DAQ drivers installed.  Nevertheless, I do not know if LV2010 will support it, but it is worth a try.  I have many things that are not supported but they work 😉

---

 

The images below show where the problem is..  I do not know the name of the file that it is looking for, so I can't even search for it.

---

Ray.R you were the only one to give me information that I could use. In this post you did deserver the kudos I gave you but when you agree that I'm an idiot in your next post you lost it.

[Dennis_Knutson]

You've been told already that those old DAQ functions cannot be converted. You must throw them away and use the latest version of the driver - which you have already been told where to get. All before you had your little tantrum -for no reason.

[saharvey]

If anyone has the time to convert (alot) of files from LabVIEW 5 to something that will open in LabVIEW 10 it would be of great help.  There's no rush, but I need to recover the files if at all possible for continued windtunnel operation.  I have attached them in two posts because of file size.  If you have the time, thanks in advance for your help. 

[saharvey]

Second batch of files if you can.  Trying to open in version 10.

[Butz]

---

@smercurio_fc wrote:

---

@Butz wrote:

Hi,

i would appreciate if someone could converts some drivers for me...

The drivers can be found here:

http://www.oinst-software.com/OIRI/docs/LV5drv/lv5drv.htm

I need the drivers for the ITC503, ILS and the IPS (first three in the list).

The drivers are for Labview 5 and I'm using Labview 2010.

(I'm new to labview so i don't really know which of the 10 llb files one need to convert..)

---

I don't know which ones you needed either, so since you pointed to the first three files on that page, that's what was converted. Given the size of the file I used 7-zip to get a smaller archive. You can download 7-Zip for free at 7-zip.org.

---

Thanks so much!

You converted just the right ones. And by now, it works just fine!

Thanks!

[Ray.R]

-- deleted --

[Ben]

---

@DonRon1972 wrote:

...

1) You still bring a bad name to NI because I see their logo all over this form and you represent then, period.

2) Start you own form and get away from this one.

3)By the way you were NO help to me at all. Called a real NI engineer to help me not a want-a-be.

---

1) If atruistic service to the LabVIEW Community brings a bad name to anything, I would have to agree. This whole thread is Saverio's idea in the first place. Before him the public offer to upgrade code simply did not exist. It had to be asked for on a one-off basis.

I call that a plus to the community. Again if service to the community bring shame, then I am in full agreement with your comments.

2) "start your own forum" NI made that offer to us and we took them up on it. We are just a group of scientist and engineers that share our interest in LV and science with similarly mind people. See the various posts in the Breakpoint to get a better idea of the people that support this form.

3)If you do not like the answers from the ""want-a-be"s then don't read any of the posts from people with yellowish bars under their avatars. Just read what the blue-bars say.

An now that the adrenelin (sp?) as disapaited a bit...

Not all of us are up ther on the social skills as you may find in other venues (my wife tells me not to bring up God and politics and those discusions of buffer re-use fall flat at most parties).

I can not speak for others but for myself I can say that to get the most out of this forum it is important to read the responses you recieve (free of charge from experts if you read the yellow bars) and follow their suggestions. Few of us have spare time to repeat ourselves and we hope that our readers will learn from our efforts and do the work.

Now to the concrete situation at hand.

The old DAQ drivers are not something that gets upgraded like a Word doc from an old version to a new version. It is more like replacing WordStar with Word. It requires a specific set of software be loaded.

Just trying to help!

Ben

[smercurio_fc]

---

@saharvey wrote:

If anyone has the time to convert (alot) of files from LabVIEW 5 to something that will open in LabVIEW 10 it would be of great help.  There's no rush, but I need to recover the files if at all possible for continued windtunnel operation.  I have attached them in two posts because of file size.  If you have the time, thanks in advance for your help. 

---

Attached is the code in 10.0. You should read the mass compile reports that I included to see what the issues were.

The code uses Traditional DAQ. You will need to either download and install Traditional DAQ 7.4.4 or rewrite that part of the code to use DAQmx. It also uses the DapDaq library, and I'm not sure if there's a version that will work under LV 10.

[nsr128]

---

@Ray.R wrote:

Extracting from the library might make our lives easier.. 

Are you sure that you are using LabVIEW 7.4.4?  I'm quite sure 7.1 was the last version of that vintage.

---

I'm not sure, I'm just going by what the engineer told me. Maybe I heard him wrong?

Regardless, I was able to extract the files I needed from the library. These need to be converted to Labview 2009 (9.0f3, according to the error message). There are a decent number of files (9 .vi files). This isn't terribly urgent, so there's no reason to rush to them.

Thanks in advance, I really appreciate this!

[smercurio_fc]

---

@nsr128 wrote:

---

@Ray.R wrote:

Extracting from the library might make our lives easier.. 

Are you sure that you are using LabVIEW 7.4.4?  I'm quite sure 7.1 was the last version of that vintage.

---

I'm not sure, I'm just going by what the engineer told me. Maybe I heard him wrong?

Regardless, I was able to extract the files I needed from the library. These need to be converted to Labview 2009 (9.0f3, according to the error message). There are a decent number of files (9 .vi files). This isn't terribly urgent, so there's no reason to rush to them.

Thanks in advance, I really appreciate this!

---

I believe your confusion stems from the fact that the engineer was referring to Traditional DAQ 7.4.4. Traditional DAQ is a hardware drivers, and those VIs you have are part of that driver. These VIs should not be upconverted. See my previous response to your latest post to saharvey regarding Traditional DAQ.

(Hmmm... is it just me, or has this come up several times in the past few days?)