jgcode

Hi Dave, as per the Readme, only 2009 is currently supported at the moment. One of the next things I will be doing is testing it in 2010, to make sure its all good. Are you moving up to 2010?

This was a question at NI Week 2010 Coding Challenge. You should have entered!

Shortcut to download latest version here Changelist: 0.15-1 2010 09 26 - Added (): Name of Method VI being cloned is displayed on Clone Dialog - Fixed (): Order of Virtual Folders in GUI did not match script - Fixed (): Creating Constructor from Template did not replace Class Input Control (caused by refactoring for Clone method support)

Ha! I never mentioned the size of that connection... Yes, you are right, to use DAQmx as an example: whilst the size has not increased dramatically in the last few releases - like it was doing previously (it may be ever so slightly shrinking as well) - I would love to be able to have the ability to be able to scope support to single devices so I can limit the size of my installers. (~150MB for the LRTE and) ~150MB for DAQmx Core drivers is cumbersome, we obviously can work with it, but I would like to know if anything could be done for it - maybe I should post this on the Idea Exchange?

OMG! I think you have set a new standard on LAVA (and it was only 12 mths ago Mods pulled my Saturday Night Live video).

I have never understood those people who always go for the cheapest DAQ just because its the cheapest. IMHO, the most powerful thing about NI is not their hardware and not LabVIEW (don't get me wrong these are both fantastic), its their Drivers - the connection between the IDE and the hardware. Again, IMHO, for the extra cost upfront of going with more expensive hardware, you are going to save a bucket load of time (and therefore money) by having a reliable Driver set e.g. standardization/familiarity, support, flexibility, upgrades etc... So a lot of the time (for what we do) it makes sense to choose NI. (However, we are also an Alliance partner, so we are bias)

I think that man prefers open-source stuff.

Obviously the Class is getting loaded or is loaded in other application instance? But that would suggest there is dependencies between the two projects - but the dependencies tree is has no elements in it (no expand button). ?

Hi Farid, here is some code to do it: Image copyright David Vignoni, www.icon-king.com Symbol.vi

By looking at it, it doesn't seem to be Locked under Properties >> Protection >>Locked/Password-Protected as the private-scoped folder is shown. Might be a loading issue?

Well, if you end up writing one, be sure to post it.

No probs, glad you found it handy.

Hi Martin See here for some additional system controls - cluster and array, don't know about mixed signal graph. Note: This package should automatically be available in VIPM (through the LabVIEW Tools Network Repository).

[Duplicate Thread] Hi Karasi As you are new to LabVIEW and will be using NI-DAQ Hardware (e.g. USB-6008) I would suggest checking out Getting Started with DAQmx as well as any general LabVIEW topics. I don't think anyone will do your homework for you (who knows? maybe you will get lucky) but if you post specific questions of the problems you are having, along with example code as to what you have tried and where you are stuck, you will be more likely to get a response. Cheers -JG

Of course you can, otherwise the Task-based API would be pretty useless. As long as you don't run two tasks at the same time that share the same physical resources you are fine.

It is slightly disproportional, but that works .

Hi Martin A few ideas tossed around if you can't get the Tab to go: Why not just use one graph that is set to fit to pane and if the user selects a different graph (view) then just write this data to this graph. This is assuming you have your own buffers and are not using the graph's, and the graphs are the same types. Otherwise, if not, use multiple graphs (with fit to pane set) and just stack the graphs on each other and just make the active graph visible. Cheers -JG

Great list. Well, I am pretty sure all Customers want their software to work. But I agree, we are mostly likely talking a different project scope as I definitely don't have access to such a system/IP as you described. So if it makes sense for the project I do go with MAX.

I have tried both approaches, I particular like integrating with MAX in certain situations: Here is a brief list of my FORs: MAX is usually installed (or its not a hassle to) just install the Full Driver (which the client gets on disk with the hardware anyways). MAX already has an interface, no need to create one (save budget) And having a GUI is normally easier for a customer to navigate than a config file API (depending on the Client of course). MAX includes the ability to handle Scales of different types (linear, non-linear etc...) - again, I don't have to account for this my code. Communicating with MAX is really easy using the Task-based API (through PNs etc...) (So far) Clients seem to like using MAX Especially if they have used it before, then you can maintain a consistent interface for hardware configuration. Its easy to back up your configuration and port it over to another PC etc.. Some of my AGAINSTs: It separates your (custom) application Your application has a dependency on MAX

I used to be that posse, but it was due to narrow-mindedness. I now think they have a valid use case as per my posts above and link to D's article. Yes, as I mentioned above, I was referring to RT. The OP wasn't focussed on a particular target. Well, thats ok, your allowed to NI's PSP protocol seems pretty nice, and it sure is a fast way to share data/messages between a Target and a Host application. I haven't tried the Network 'this is the way SV were meant to be used" Streaming feature of LV2010, but that looks very cool. Also for tying into a Database or Alarms, is pretty straight forward, so I have found you could save a lot of work using them. <edit> I did not know this! Cool tip - I will try it out. How much jitter are you talking? And what is acceptable for your TCL? (what is it doing?) </edit>

lol I thought you might mention that But in this case its seems best as you mentioned. Ok - you are ready for this... You can create Tasks , Scales etc... in your LabVIEW Project! [... the crowd goes wild...] I love this, now I can associated hardware configuration with the Project, meaning its easy for anyone (or me in the future) to quick get access to the configuration and is the first thing I do for development. When it comes time to test/build etc... I use the Import/Export features integrated into the Project. The only downside with this is that is I want to include DAQmx configuration for an installer it has to be as an .nce file. The Project exports as an .ini only. So it means importing the .ini to MAX then exporting it back out as .nce so I can point the installer to it. Don't know if this has changed in LV2010, or if there is an easier way. [License] I have seen this license but never been affected by it. What was the result of actually trying to create a Scale? I mean if the customer buys NI-DAQ hardware which ships with the DAQ-mx drivers then they are going to need to create Scales etc... so this should not be an issue. I normally get the prompts but I just acknowledge them and it all (seems to) works.

That is not true, due to the error wiring to sequence dataflow they can be a much better choice. Also, you are never going to use a NPSV in a time critical loop (or any serious loop), you are going to use a SPSV.