BrentonLang

Hey Crelf, this Toolkit is great! Far more easier than the standard build in XML toolkit. Not 100% sure about the price, but thanks for the heads up anyway. Just my personal opinion, I hate creating tasks in MAX. I either have the tasks built in the project explorer or manually create them in code. Sorry, just my opinion.

Yeah, thanks for that crelf. I wasn't sure if there would be any issues with distributing those logos, considering you can just Google-Image search them. But I can understand where NI are coming from.

WOW, this is a hot topic. I may as well add my two cents worth. I much prefer small terminals, not icons. Mainly because you can position them much closer, and it keeps the block diagram much neater. I think NI use Icon terminals by default, for beginners or amateurs of LabVIEW. ie. People who may not know the data types too well.

Hi All, Does anyone out there have hi-resolution logo images for the following Logos. - Certified LabVIEW Architect - Certified LabVIEW Developer - Certified LabVIEW Associate Developer - Certified NI TestStand Developer They need to be the most recent logos, for example, the current CLA logo looks like this: They don't need to be insane hi-res, but maybe 500 width pixel minimum. Vector images would also be fine. Thanks for your help.

I have to say...that is a fantastic idea!!! Thanks asbo.

Didn't know that...very nice! Thanks for sharing.

I agree with everyone's statements. Pretty much how I understand it is if you only require the most recent information, then Master/Slave. If you want to process every piece of collected data or information, then go with Producer/Consumer.

What I would do is create a config file using the standard XML format. This would be originally created from a TypeDef cluster containing all variables (this is also a good idea because it is expandable if required). LabVIEW contains XML subVis which can be used for this config.xml file. Make sure you specify labels for each element in the TypeDef cluster, as they are required in the XML file. I would start by creating a VI, which won't be used in your main program, to manually write a cluster (as mentioned previously) to a new XML file. Then in the initialization stage of your main program, read the xml file and convert it to usable data by providing the cluster TypeDef as the data type. The good thing about XML files is that it's just text, so it is manually customizable outside of LabVIEW if required.

I agree with JamesMc86. If I understand your question correctly, I don't believe it is possible due to the fact that LV-RT has a target of a cRIO, which contains a completely different processor than an Intel or AMD. The main problem will be allowing the cRIO real-time operating system to run on a different CPU. I'm pretty sure that .iso image generator is purely for LV-RT devices.