ShaunR

Yup. LAN is usually the issue. Also. Different LV versions work only with certain processors - Something to bear in mind if you are trying to leverage an old PC sitting around. Requirements for Desktop PCs as LabVIEW Real-Time Targets

Nice find It would be nice if the tolerance had a default value so for most use cases we didn't have to specify it.

Yup. +1 to Ton

I never claimed "everything should be public" either. I argued protected vs private.

How I wish this one was true. I'd have definitely had a go Virgin ‘Little Red’ gets glass bottom

He can use a variant for different datatypes (array of boolean or array of doubles) and therefore won't have a problem with overrides.

Variant tomatoes? The problem isn't so much with different data-types, it is more numbers of terminals where you run into trouble.

A file with tag names, expected values and/or limits . Different set-ups have different files. (sorry to be sparse, but can't help thinking I've described this to you before, somehow )

That may sufficient for the OP and it is a lot closer than nothing at all..

Right! So that must be documented somewhere (as it was for the Single Precision Functions in the FPGA example I gave). I doubt if the "rules" for the particular target are that esoteric that you can only load this single precision object on this FPGA target when it's Tuesday and you have your left trouser leg rolled up. It's more likely that it will be things like an FPU isn't present on that target (that will be documented internally at NI) and the manual will supply the features that are or are not applicable. The OP says that it may not load on the target because the VI may be broken due to wiring, missing dependencies etc. So he is looking to weed out incompatible features (like the DLL checker that is used to check Pharlap DLLs). This is presumably so they can write it "offline" and verify the developer hasn't used unsupported features, At the simplest level you are trying to end up with a compatibility matrix accross LV versions, targets and features. I would be very surprised if an engineer at NI hasn't got a spreadsheet with it somewhere (probably an applications engineer) Once you have that, you can add simple rules for "odd" anomalies. You don't have to start with all targets or LV versions. However, eventually you will have a complete picture. After all. Most people that use the targets "know" what does and doesn't work. It just needs to be formalised to be able to use it programmatically.

I think this is the only (reliable) way. The functions and features supported on each platform are documented (example) but not in a single list that I'm aware of so you would have to spend a bit of effort pulling it all together (property nodes have tables in the help that state quite a bit about where they will and won't work). Once done however, it can be put in a DB along with LV versions etc making examining a VI fairly straight forward with scripting. You would just need to keep the list updated with the latest LV version. You never know. Maybe NI have an internal doc that pulls it all together. Worth asking your local rep.

Rolf is the man you need to talk to. But here is my limited tuppence. Pharlap uses a stripped down windows API that implements many but not all Windows API calls (I'm pretty sure you cannot use normal windows kernel mode drivers AKA sys files-Rolf will confirm). There is a checker that you can run on DLLs to see if they are compliant and you need the version for which LV version you are using (I've linked to the 2009 one, but there are 2011, 2012 etc that you can find with a bit of Googling). If it is not compliant and you do not have the source, then you are up a creek without a paddle. If you have the source, then you will have to hide in a dark room for a couple of months to make it compliant. If you need a "sys" file then this is a hard-core kernel mode driver and fraught with rabbit holes not only in respect of the driver, but also it working within Pharlap. It is an "expertise" in its own right - I would highly recommend you sub-contract it out if you cannot get support from the supplier or choose a different card.

According to wikipedia The only major difference I can tell is the size of the FPGA and NI don't state that there even is one in their docs.

You get used to it

Well. I've been there. I wrote a library for changing UI elements "on-the-fly" (passa mak). I deliberately excluded unicode since it is platform dependent, but it could be modified for a particular use case.

Labview doesn't (officially) support Unicode. There is a "hack" to display Unicode chars in indicators, but all labview functions/primitives still only support ASCII. You need to use the library that Tim_S linked to to even have a chance of manipulating unicode chars, which you are obviously not using.

When people ask me how I spell my name. I say "like the sheep"

I have, sort of But only for the UI (not for things like charts etc, but I suppose I could have). I used the same code as I use for config dialogues (it just iterates over UI controls), and kept a history of changes in a DB. You then just query the DB. You can go back, forward and, if you put a little bit of additional info in (like a short description), you can list the last (say) 10 changes in a menu and jump straight to them unwinding the list. By linking the entries to the control label, it works transparently and is not application dependent. I also attached events to all controls that I was interested in so I didn't have to write specific queries to enter them into the DB.

Nope. Don't know you or what your real name is (a hoover is a vacuum cleaner over here and in everyday usage). It was, and always will be a typo (apologies). My handle, however, IS my real name. (I don't care how you spell it and even I get it wrong sometimes whilst typing. Luckily I rarely refer to myself in the third person )

Yup. What hooovahh said.

Yup. I checked my snippet after Hoover said (on another thread) and it was fine. I've now uploaded the same snippet to http://postimage.org/image/5p8stekp7/ and it works fine when downloaded. Definitely something going on with lavag.org. Maybe it's now being optimised/compressed?

You are expecting that "Whole Match" really means Whole Match except those bits I don't want? LV Help To match individual components you have to create capture groups. The ?: syntax means that you exclude that component from the list of capture groups (this isn't a LV peculiarity, it's how all regex parsers work). So whilst (The quick brown fox jumped over thes*)([a-zA-Z0-9]*)(s*dog) will give you three terminal outputs with 1. The quick brown fox jumped over the 2. lazy 3. dog (The quick brown fox jumped over thes*)(?:[a-zA-Z0-9]*)(s*dog) will give you only two terminals with 1. The quick brown fox jumped over the 2. dog Similarly. The quick brown fox jumped over thes*([a-zA-Z0-9]*)s*dog will give you only one terminal with 1. lazy In all cases the Whole Match will give you the whole string if all capture groups match and bugger all if it doesn't.

Here ya go.

The way I resolved a similar issue was to use the "Path to Command Line String.vi" (which isn't on the palettes) rather than path to string then hacking the string. It seems to work on all platforms. You can then just use all the path primitives (e.g. strip and build) to traverse the path without worrying about the underlying format.