Yair

will be scanned by future researchers looking for help on LabVIEW programming or other strange keywords. Once it's out there baby, it's permanent. For the world to see.

Hopefully, those who are already clever enough to do the searching instead of asking straight away will also manage to get through my occasional badly phrased answers or have the common sense to read some more answers.

Anyway, if I really minded, I would either seriously proof read each and every post or not post them at all.

Incindentally, my last post has a perfect example of a typical error which happens when writing fast - it's missing the word "it" near the end, for whatever reason.

so my text is not always as fluent and clear as I'd like to be

"F y cnt rd ths yv gt rcks n yr hd!"

I can't read that. I think I might have rocks in my head. :headbang:

Regarding writing style on the web - at least for me, writing in forums such as these is often done as a break from other things and in some cases even in the middle of doing other things, so my text is not always as fluent and clear as I'd like to be and I don't always get to reread it before posting.

I'm also one of those without a built in spell checker, so spelling mistakes do creep in sometimes (usually brought on by typing fast and not paying attention). This is less an indication of disrespect and more an indication of the nature of the beast - a text which is written fast and will often only be read once, so it's not always perfect.

Of course, the distance from there to using "pls", "gr8" and their various friends is gr8.

:laugh: In the words of Sting: "I'm an alien, I'm a legal alien, I'm a legal alien in [Detroit]"

In keeping with the "it's spelled LabVIEW" spirit, the last part should probably be "I'm an Australian in Detroit".

I know, I can be really intolerable sometimes.

An interesting thing about the square of the Arc de Triomphe (something which can be seen in the image posted by Michael) is that it has about 5 lanes and that they're all unmarked.

When traffic is light, this is not a big deal, but if you were to go in there at rush hour and make the mistake of getting into one of the inner lanes, you could be circling in there for hours trying to find your way out.

BTW, did you ever notice how a square is actually circular? Funny language, English.

Welcome to the LAVA forums.

I suggest that you also check out the forums at NI's site.

One reason is that they also have a CVI board.

another is that there are a lot more people there, so if you're asking a simple question, you're more likely to get a quick answer.

Another suggestion is to try searching for the information you're looking for before posting any questions. You should also look for some tutorials, as there are a few of those around.

I fail to see how your second post has anything to do with the first, pther than that you have the two arrays there (and they're numeric arrays, not string).

If you still want to save and load to a file, then you just need to add a couple of states to your functional global which will go along the lines of what I previously suggested.

Incidentally, this type of global is quite common and has many names - "USR global", "LV2-style global", "Action engine", "Functional global (FGV)", etc. Hopefully, it's known by all LAVA members who have been using LV for any length of time.

Maybe you can use a .vit (VI template) and open a new VI based on the VIT and use this as the reentrant VI

As I already said, you can use a VIT, but you won't be able to connect to it, because the HTML file needed for the remote connection (assuming a browser is used) needs to point to an actual VI on the hard drive, so the code needs to create a fake VIT by copying the VI and renaming it and then running the copy and modifying the HTML to point at this copy.

I think that it was LV 8.2 which introduced seperate FPs for reentrant VIs, which means that the only way is probably to upgrade.

To workaround in 8, you could probably write a wrapper which would not be reentrant and connect to that wrapper.

If you need more than one VI, then I think that you will have to write some code which will copy the VIs and run them, because VI templates only create copies in RAM and RFPs require that you have the VI on disk so you can point to it.

I don't know if you can do this with an installer, but since you already have the RTE installed, you can write a small LV application which would do what you want and then launch your installer. If the INI file is the same name as the EXE, then you would also need it to rename the INI file and the section inside it.

Additionally, even if you don't have the RTE installed, you can run an LV application without installing the RTE if it's a simple application and you have the RT DLLs in the same folder as your EXE (Just get the files from NI\Shared\LabVIEW Run-Time).

There are functions in the String palette to convert an array to a string and vice-versa, so that should take care of the array part.

To find the actual array when you read from the file you need to find the last semicolon and read what's after it. You can do this by searching the string in a loop (or reversing it and searching for the first occurence) or perhaps by converting the entire file to an array with a semicolon as the delimiter.

If I'm not mistaken, the property Application>>User Name should give you what you want.

Another option might be to go to the MSDN and look for a Windows API function which returns this (or .Net) or maybe try the registry.

I haven't tried it, but you should be able to replace the Windows shell application with your own app. That way, your app will load instead of the windows shell. Try searching the NI forums, since I remember seeing something about this there.

That depends on how you pronounce "LV" Is it "el vee" or does your brain automatically insert "LabVIEW"? (PS: I agree, it should be "an")

I have trouble pronouncing "LabVIEW" (the "bv" part is tricky), so I think of it as "El Vee". Doesn't everybody?

I do to admit, though, that I don't think I ever actually pronounced that way out loud, so maybe I should think that everybody does.

And don't forget that when using an acronym which you begin pronouncing with a vowel, you need to use "an" when refering to it even when writing it, e.g "I want an LV icon under my name" and not "a LV icon" (nudge, nudge, Michael).

Wow! It even comes in a Student Edition.

But the student edition is "Labview 2" and it sells for $1,300.

Maybe they're throwing in one of those old Macs with it so you can run it.

Although, it also seems to have a door.

I've never seen a copy of LV with a door, so maybe it's worth it?

Addition - OK, I am near a computer with LV now and I can see that the method is a VI class method. It seems that the main obstacle in getting it to work is wiring in the TargetName which is a string. Anyway, it's not very interesting, as it's not coding and it's not G.

create code that converts a VI to a text representation and back?

Well, I'm not near a computer with LV at the moment, but I believe LV does have an "exposed" scripting Application class method for doing this (something along the lines of GenerateCCode).

I haven't actually tried it, but it's probably what the PDA module (and LV embedded?) uses and I don't know how good its C is. Also, it doesn't generate a VI back from the C code.

Well, you already wrote the code, but the answer is File>>VI Properties>>General>>Current Changes.

As I understand, every one of those little squares between frames results in a new data instance (i.e., a new memory alocation)

I can't see the code, but I would like to point out that tunnels do not automatically cause data copies. LV optimizes the usage of memory and only makes a copy if the data is needed in more than one place.

Using dataflow instead of a sequence is better, just not for that specific reason.

You need to be prepared to change your mindset - LV PDA is not LV!

Well, it is LV in the sense that you use the same editor and can use a lot of the same code, but it's not LV in the sense that a lot of the functionality is missing, that there are *a lot* of bugs and that you might need to do code differently in order to get your program to run.

First off, the device - get a Windows device. NI removed support for PalmOS in 8.2, so I wouldn't get Palm (although I don't have any experience with it). There are many varieties, but depending on your LV version, CE.Net 4.2 and above or WM2003 and above should work for you.

Second, LV. The PDA module only started with version 7.0, so every version has seen some important additions. You should consider getting a newer version of LV for this (7.1, for instance, does not have the ability to display arrays). Also, be aware that there is no RTE for the PDA module - instead, LV translates the code into C and then compiles it. This is an opening for a lot of bugs, which do exist in the PDA module - working around them can make your development time a lot longer.

PDAs are significantly slower than PCs - be aware that there will be limits to how fast your program will run. You might need to do some optimizations contrary to normal LV style (like having less subVIs). PDAs also use batteries, especially when dealing with wireless communication. Be careful if you get an industrial PDA, because I have seen that the special power optimizations used by these can mess up your program.

You should also consider licensing issues, because if you want to distribute more than one copy of your program, it will cost you. NI should be able to give you the details.

After all this, I would suggest that you consider another alternative, like a thin Linux client which will run an LV application or a wireless connection to a Windows server which will be the one actually running your program. A solution of this sort will get you around all of the problems of the PDA module and might be a much better solution for a system where you have a computer anyway.

Hey fellas, check this out --- I added it to the code repository a while ago:

XNode Wrapper

Nice... :thumbup:

I should definitely check that out.

If I recall correctly will closing the FP terminate the executable if it is the main VI.

Ton

Yes, you recall correctly. The RTE continuously polls to see if there are any open FPs and when there are none it terminates.

I use a toolkit from Karsten van Zwol, LabVIEW_Tray_Icon.lbb. Got it from here: http://forums.ni.com/ni/board/message?boar...essage.id=95141

This library is useful (I've used it in the past myself), but you should note that you need to install that library in order for it to work, because the ActiveX component needs to be registered.

Hmmm, maybe it is just my computer...

It's not. Happens here as well.

That is a nice commercial. Reminds me of the one for Carlton beer (scope wise).

Michael, the very idea of promoting this video is un-american. You should probably be deported.

I was surprised to find George Lucas in the middle of the clip.

Oh, and that "Good night, Michelle" - that's just wrong.