Is "1easyIO.llb" a National instuments LLB?

[Vr6Fidelity]

Is "1easyIO.llb" a National instuments LLB? It seems as if all the VI's in my company look for VI's in this LLB. The VI's it looks for are AIaquireWaveforms.vi and CreateDataString.vi

LV8 is impossible for me to use. I literally cannot firgure out how to read signals off my hardware, i have no clue how to create calibrations for signals into real values, make graphs, write files, etc. Thanks for Re-inventing the wheel NI and providing zero free support. I hate you NI.

[Bob_Y.]

Easy, easy.  What exactly is the problem you seem to be having?  LabVIEW 8.0 is not really that different from LabVIEW 7.1 and unless you need to be compiling for another platform (RT or FPGA, or PDA, etc) you can totally ignore the project.  That leaves it JUST LIKE 7.1. 

As for 1easyIO.llb, yes it is part of the daq drivers.  I think it is installed as a device driver.  If you did not install the device drivers when you installed LabVIEW 8.0 you may be missing this llb.  It is in this directory on my PC  \LabVIEW 8.0\vi.lib\Daq\1easyio.llb

Perhaps you can better explain your other problems.

Hope that this helps,
Bob Young

[Vr6Fidelity]

Right, whatever you say. Where is traditional DAQ? Where is "write to file.vi"? I have never used MX before and now i am FORCED to. I have no clue.

[Dennis_Knutson]

You are not forced to do anything. DAQmx was introduced with LabVIEW 7.0 and could have (and probably should have) been used with your old programs. If you still want to use the old DAQ functions, all you have to do is install it. It's not installed by default because NI wants to encourage users to switch but you can do whatever you want. I don't knwo which version ships with 8.0 but the latest version can be downloaded at http://digital.ni.com/softlib.nsf/websearch/3DBF3D343476A28F8625709E006A4937. 

I do agree with you though, when you say you "have no clue".

[Vr6Fidelity]

Ok, where would i find the "AI Waveform Scan.VI"?, "AI Waveform Scan(waveform).VI", and "AI Waveform Scan(scaled array).VI"

Ill assume they are in some LLB?

Why arent theres LLB's installed automatically?

Why is there no way for LV to know where to look, or to have it look in a folder of llb's?

[tbob]

Why don't you start learning what you don't know before blasting NI.  You can start with examples that NI includes with Labview.  There are help screens that can give you a clue.  That's the way the rest of us learn new things.

Once your start learning, if you have problems or questions, post the specific problem you are having and we will try to help.  That's what we are here for as volunteers, to help our fellow Labview programmer solve his problems.

[Bob_Y.]

Vr6Fidelity,

Try not to take any offense, but is English your native language?  Some times you come across as upset and when you are asking a large community of users for help, the best way is usually by asking, not by compalining.  If you truely hate the stuff that we all love, ask for help.   The reason I ask about English is that sometimes the tone can change during translation and you might not mean to be insulting to these beloved products.

Now on to your question at hand.  The VIs that you are looking for are all part of the traditional daq VIs.  If you do not have them, you did not install them.  They are available on the Device Drivers CD that came with the LabVIEW 8.0 disk.  You need to insert the first Device Driver CD (1 of 2) and select to install Traditional DAQ. 

Yes, traditional daq is being phased out in favor of DAQmx.  DAQmx is necessary for the newest series of DAQ card from NI where as Traditional DAQ is used by the older (usually depricated) DAQ card.  The rest can use either DAQmx or Traditional DAQ.  I would recommend learning to use DAQmx as it is more powerful and flexable than Traditional DAQ.  Do not use it if you have older cards and already have a large install base of Traditional DAQ VIs.

Thanks for the interesting questions.

Hope that this helps,
Bob Young

P.S.  I forgot to mention that LabVIEW automatically searches what you tell it to search in the Tools -> Options -> Paths -> VI Search Paths.  This usually includes all of the subdirectories of LabVIEW's installation directory.  In other words, it does usually find what it is trying to find.

Message Edited by Bob Y. on 02-21-2006 01:26 PM

Message Edited by Bob Y. on 02-21-2006 01:27 PM

[Vr6Fidelity]

Yes, English is my first language. Yes the anger is present. The anger sprouts from the fact that it is nearly impossible for me to take a VI that i spent days writing in 7.1, and not be able to install it on a newer 8.0 machine. Is that really too much to ask? I really dont think so. I should not have to replace sub VI's because NI feels like changing them. All they need to do is ADD more VI's, do not remove them.

Writing code is NOT my job. I am a mechanical engineer, I have almost no software background. I know the people who answer kindly to my rants are software programmers. Im sure the problems seem plebian to you. But for someone who just fubles his way thru they are almost insurmountable. The function of most of my VI's are quite simple (read inputs, write data to file, Analyze data logically, write output) But what they control is usually dangerous and expensive (jet engines, 2000 degree ovens, etc.) Sometimes one needs to be comfortable with just installing an older version of a VI onto a newer machine. With NI this seems to never be the case. There is seemingly always some minor change that I as the casual user am not quite aware the ramifications of. I would prefer my upgrade to LV8 not literally kill me.

So when NI changes seemingly minor things like removing the "write to file" VI, and having LV automatically replace it with "write to binary file" angers me to no end. This literally cost me a test sample, the VI ran fine but resulted in a useless binary file instead of tab delimited text suitable for analysis.

So now, i will apparently re-install this support for traditional Ni-Daq and see what happens. Thanks for your time and support. I have already realized the discussion forum help is better than what NI gives over the phone.

[tbob]

If you wrote your vi in 7.1 and it works, then why do you want to upgrade to version 8?  Perhaps you are installing it on an additional computer and you can't get 7.1 anymore?  If so, you could go back to your 7.1 system and build the program into an exe application.  Then on any new systems you could just install the 7.1 Run Time library (its free) and just run the program as an exe.  You don't really need to upgrade to 8 in that case.

[AnalogKid2DigitalMan]

tbob:

Governmant 'rules' see reply 9 of this thrant.

http://forums.ni.com/ni/board/message?board.id=170&message.id=159068#M159068