Who can fix my VI to work in LV8? please help...

[Dennis_Knutson]

For someone who has said they don't have much LabVIEW experience, you seem to be be pretty arrogant about about what you know. The fact that the conversion to LabVIEW 8 created binary files and you obviously had to change the program and had to ask how to do it, means that something else in the program got modified in the conversion. All I asked was a chance to see the original to see exactly how it was being written before. If something really got mangled in the conversion, I and all others would like to know what we all have to face. If you don't want to share, that's fine but what I posted will create a binary file. Go back to your old computer and try it or look at the shipping examples.

[Vr6Fidelity]

Ok, here it is it should NOT have write to binary file anywhere in it.

[Dennis_Knutson]

Thank you. I run it in LabVIEW 7.1 and it produces a text header with data in binary format. This is when I view the file in a text editor such as Notepad. I get exactly the same thing when I run it in LabVIEW 8. The thing with Write File is that you don't tell it to write text or binary. It automatically writes data in whatever data format you wire to it. The old example called Write Character's to File has a string wired to the data input and that's what gets written. The example called Write to I16 has a I16 wired to data why it writes an I16 binary file. That's why the fix in the LabVIEW 8 program was to convert the 1D array to strings. I can't explain how it once worked though. Did you have to do anything special in Excel to read the file? That's the only thing I can think of. In any case, my curiousity about 7.1 to 8 is satisfied.

[shoneill]

By the way, it seems like a simple phone call could have prevented all the confusion flying around here.

You are nor "forced" to upgrade to LV 8.  If you have LV 7 CDs, and a valid LV 8 licence, NI will basically always let you install and use LV 7 with the 8 licence.  You still can't install multiple environments on a single licence key.

Although this won't solve the immediate problem, it may have prevented the trouble in the first place.

Regarding the problem at hand, it seems like you had a modified VI in your LV 7 installation saved under the original "non-modified" name.  This is guaranteed to confuse LV when upgrading since it can't know that the original version was modified in any way.  Just for clarity, the people who have already answered your questions are highly experienced professionaly who have already gone through multiple upgrades.  They know what they are talking about.  You should listen carefully to what they are saying.

Hope this helps.

Shane.

[Vr6Fidelity]

I dont think you guys really understand my knowledge of Labview, I have next to none. We used to have a guy who knew it but he got fired, so I defaulted into labview. Its terrible. Thats my problem once something dosen't work i really have no means to fix it. I also don't have a service contract. I often would like to use certain VI's (such as write to spreadsheet file) but i can't figure out how to make it accept my data type. I just look at oter VI's that exist here at my work and try to replicate the components used to make them work. I really do appreciate your help greatly. I specifically asked to purchase 7 and i was told i could not. I didn't know about the new licence old version trick, i surely would have done that! I have no need to re-learn the few scraps of information i have gleaned from my trial by fire.

I am quite proud of this VI, It is my first with outputs, stacked sequences, multiple while loops with different speeds, local variables, decision making, I have never done any of this before, it took me about 16 hours to make it work properly. You will notice there is also saftey features installed, such as the fact the vi cannot shout down unless the T5 is below the minimum setpoint and the correct number of iterations has been met. It also heat-soaks for a variable length of time at the maximum setpoint value. It also turns on cooling air to accelerate the cooling of the oven.

Do any books exist on labview that are good? I would like to learn more about it to have less problems in the future. It also kinda interests me.

[EdDickens]

LabVIEW's not terrible, at least no more than any other development environment when you first start with it. There's going to be a learning curve.

There actually are a few good resources for learning LabVIEW. The best one would be to attend some the NI training courses. They have course that go to a training center and others that you attend online. It's a good place to start. Of course these both cost to attend.

A couple free options to help are to run through the tutorials that come with LabVIEW. From the LabVIEW 8 splash screen, you'll see a link on the right under the heading, "New to LabVIEW?" titled "Getting started with LabVIEW". This opens the tutorial and is a good place to start.

There is also a free online tutorial available at http://cnx.rice.edu/content/col10241/latest/. This is pretty much the same as the LabVIEW Basics 1 course. Takes a little time, but it will get you going.

Message Edited by Ed Dickens on 11-22-2005 08:47 AM

[PJM_Labview]

Here is one more usefull ressource to add to the list: The LabVIEW FAQ

PJM