Need the following .vi9(s)

[billko]

---

smercurio_fc wrote:

---

F. Schubert wrote:

If I remember correctly, there is a FTP site of ni where you can download LV 6. I guess the link was once posted in this forum.

---

I have LabVIEW 6i on a virtual machine and I can't find those VIs.

---

I still have to side on you with the custom sub-VI theory.  Look at the names of the VIs:

• binRead.vi
• findMinMaxfromCenterRange.vi
• IndexToTimeConv.vi
• CalcDecimateFactor.vi

binRead.vi I could make a case for saying it's an included function.  But look at all the other names.  Don't they strongly suggest that they are "helper" sub-VIs to calculate values for use within the main VI itself?

I know it is only inference, and by itself wouldn't mean much, but "candlestick" doesn't mean anything either, until combined with "Colonel Mustard" and "Study."  😉

Bill

[Dennis_Knutson]

It's possible that they were part of a toolkit or some odd example but since the op seems incapable of supplying the path information, we may never know.

[Bebeto]

They are probably part of a toolkit as like mentioned before I was looking for the JtfaEngine.VI and it was part of the Signal Processing toolkit.

Now how do I get the "path" for these?

[Dennis_Knutson]

As already mentioned, it's displayed when searching for them and when you get the prompt to find them, the expected path is also shown.

[billko]

---

Dennis Knutson wrote:
As already mentioned, it's displayed when searching for them and when you get the prompt to find them, the expected path is also shown.

---

Actually, Dennis, I think this was the first time how to determine the path of the missing Sub-VIs was mentioned.  😉

[Bebeto]

Yes you are confusing me, never mind let me post it.

[billko]

It's actually pretty straighforward.  Open the software you are having trouble with.  Every time it can't a sub-VI you'll get a "searching" dialog box.  If it can't find the sub-VI, you'll be presented with a file dialog box asking you where it is.

Bill

[smercurio_fc]

---

billko wrote:

---

Dennis Knutson wrote:
As already mentioned, it's displayed when searching for them and when you get the prompt to find them, the expected path is also shown.

---

Actually, Dennis, I think this was the first time how to determine the path of the missing Sub-VIs was mentioned.  😉

---

---

smercurio wrote:

When your top-level VI loads it tries to load the subVI, indicating the path in the search dialog.

---

[billko]

---

smercurio_fc wrote:

---

billko wrote:

---

Dennis Knutson wrote:
As already mentioned, it's displayed when searching for them and when you get the prompt to find them, the expected path is also shown.

---

Actually, Dennis, I think this was the first time how to determine the path of the missing Sub-VIs was mentioned.  😉

---

---

smercurio wrote:

When your top-level VI loads it tries to load the subVI, indicating the path in the search dialog.

---

---

Wow!  I stand (or sit) corrected.  Hat-tip plus kudos warranted.

[Bebeto]

Hello,

First of all, this is the message I get when loading the VI:

An error ocurred loading VI"binRead.vi".

LabVIEW load error code 10: VI version (5.1.1) is to old to convert to the current LabVIEW version (8.6.1)

Now this is the path I get:

Loading:

C:\Documents and Settings\montoye\Desktop\HAWK GUIs\Strip Chart Source\HawkStripChart.vi\binRead.vi

 Searching:

 C:\Documents and Settings\montoye\Desktop\HAWK GUIs\Strip Chart Source