LAVA 1.0 Content

QUOTE (Doug Norman @ Sep 10 2008, 03:28 PM) Thank you Doug for the link, but I can't download the workaround.zip the link to the file is not working. Dany

QUOTE (Val Brown @ Sep 10 2008, 01:36 PM) Use this link: http://ni.com/beta

QUOTE (ExpoEra @ Sep 10 2008, 11:28 AM) What I/O modules and channels have you configured? Can you attach a screen shot of the project with the configuration or the project file. Make sure the VIs are assigned to the same FPGA target in the project.

QUOTE (crelf @ Sep 10 2008, 10:50 AM) Since I don't have a note from my mother either, can you tell us more about the LabVIEW Software Engineering Tools (if you can).

QUOTE (george seifert @ Sep 10 2008, 10:13 AM) At first look its seems that we can't add function to the Word toolkit because the NI_Word.lvclass (LabVIEW 8.6\vi.lib\Utility\NIReport.llb\Word) is locked. The class implementation lock the access to the Word ActiveX. That's a very bad news since I made some custom function in some of my old project and I would not be able upgrade it in 8.6 Dany

QUOTE (Antoine Châlons @ Sep 10 2008, 11:36 AM) Well that URL gives me a page that does indicate I need a note from my mother (Not a registered Beat user at the moment). Ben

QUOTE (crelf @ Sep 10 2008, 10:50 AM) That link does not work for me. Do I need a note from my mother to access it? Ben

How can i edit the font size of lable in a customised runtime menu?Please help me regarding this, regards, Naresh.N

QUOTE (ExpoEra @ Sep 9 2008, 12:42 PM) You should first create a new project and configure your FPGA target and all of the I/O for your target that you plan to use. Then add the two VIs to the FPGA target. Open up the Use 8 Channels and help it find the subVI if necessary. Then if you go to the diagram you should be able to click on the I/O references and select any of the channels you have configured in the project for your FPGA target.

QUOTE (Eugen Graf @ Sep 9 2008, 04:20 AM) Is there a reason that you need exactly 15 levels? In your list you break out the Bachelors into separate years, but you do not do the same for the high school student. Also across North America secondary school is somewhat synonymous with high school. Usually high school is grades 9-12/13, while secondary school is anything after primary school, i.e. grades 5-12/13. You may want to use Middle School which commonly is grades 5-8, and Elementary School (Grades 1-4). Are you trying to list the current process someone is in, or the highest level of degree they have achieved? For consistency Freshman, Sophomore, Junior, Senior should be combined into 'Undergraduate Student'. Graduate should be 'Graduate Student'. Which really combines Masters and PhD students.

QUOTE (ExpoEra @ Sep 8 2008, 07:23 PM) Just as an FYI, You could wrap 96 DIO values into three U32 integers and keep the interface very simple. On the FPGA you can convert each U32 into an array of Booleans to pass to the I/O node. The same works for inputs as well. Converting a U32 into an array of 32 Booleans on the FPGA takes no additional time or space as the U32 is really an array of 32 bits already. It is simply a different representation in LabVIEW, but not on the FPGA.

I was using a muticolumn listbox with 5 columns.In third column,i want to generate a ring control,generate in the sense,whenever user clicks on any cell of third column of multicolumn listbox,the ring control should pop up.The thing is that i need to use only one ring control and whenever user clicks on any cell of a third column,this ring control should pop up.How can i achieve this,anyone please help me, Regards, Naresh.N

QUOTE (BobHamburger @ Sep 9 2008, 12:23 AM) Agreed! We go a step further and use functions that check the error boolean and log the error to file when detected. The log file is the first place I check if things go badly AND It's the first place I check if the app runs fine. It also lets me "see" the error after the fact, like when the customer from two years ago sudenly runs into a problem. I can't count the number of times engineers have returned from delivering an app saying "I love that Event Logger!" Ben

QUOTE (Daklu @ Sep 8 2008, 04:59 PM) Yes, OpenG builder suffers from the same issue as NI builder. To counteract that I have placed every class in a separate folder. (something you most likely already have done) In OpenG builder I have setup source (and target) directory for each folder. (so every class in it's own llb) http://lavag.org/old_files/monthly_09_2008/post-2399-1220897435.png' target="_blank"> Ton

QUOTE (Val Brown @ Aug 29 2008, 03:50 AM) QUOTE (Jim Kring @ Aug 29 2008, 04:34 AM) When you say that you "need to stay with as much native LV as possible", does that mean that you don't use VIs and only primitive functions? Nearly all the OpenG VIs are written in "native LV" (a.k.a., "Pure G"), with the exception of the zip library that makes a call into a DLL. QUOTE (Val Brown @ Aug 29 2008, 09:55 AM) Perhaps I should clarify a bit more what I mean by "native LV". Yes, I use VIs but I use VIs -- as far as possible -- that either I have created or that come for NI directly in their official releases. .... Val has the 'http://www.joelonsoftware.com/articles/fog0000000007.html' rel='nofollow' target="_blank">Not Invented Here' syndrome (which is sometime good, sometimes bad). Ton

QUOTE (rolfk @ Sep 5 2008, 09:48 AM) I think it was "Goedel Escher Bach, The Eternal Golden Braid" that when addressing the nature of intelegence (for a clue as to what artifical intelegence is) that observed that the ability to recognize an endless loop (Old kids joke a index card has written on the front "How do you keep an idiot entertained? (flip over)" with the same text on the back) and break out same. I view the "God answer" as a break out of that endless philosophical loop. Ben

QUOTE (shoneill @ Sep 5 2008, 05:42 AM) Here's an example of how to get the path of a calling VI and automatically strip the EXE if necessary. VI and project are attached. http://lavag.org/old_files/monthly_09_2008/post-3370-1220628668.png' target="_blank">

On my computer (windows XP) I get on both version (George's and Neville's) the same result. To easily see the difference between the two actions connect the 'peak plot' output to an XY graph: In this screenshot you can see the peaks found and the data. I suggest you sent this data to NI so they can examin. Ton

QUOTE (martin@aerodynamics @ Nov 20 2007, 09:21 AM) Whoaw, that I missed this tool. The XControl Inheritance toolkit has a VI (listprops__XIE.vi) which has a property node of the type 'property node' which returns all possible strings under 'All props[]'. Here's the screen shot: Maybe this can help you. Ton

QUOTE (Daklu @ Sep 3 2008, 09:45 PM) Yes, you miss something. You should consider your own used classes as products. So you have a development source which is source code controlled. For usage in other projects you make source distributions. However you need to rename those to prevent cross linking between development code and production code. This can be done in various ways, if you use VIPM you should change the custom postfix to make use of hierarchies of classes (I have a serious doubt if VIPM can deal with hierarchies of classes). The only thing you have to do in your production project is build the class hierarchy. Now if you need a new version of your class you can build your class, install it and the next time you open up your production project the new version will be loaded. (Make sure the production class isn't loaded during this action). Here's your definition of relinking: QUOTE This process is much more cumbersome if I'm upgrading a lvlib instead of a class. Since the library vis don't have a dynamic input like class vis, I have to go through and replace every single control/typedef and library vi with the correlating item from the new library version. (I've uttered many curses for Labview not having a more customizable dev environment. Would it be that hard to enable more hotkey options? Replace With...?) If you had used the exact same name for the library and the VIs you would have no relinking issues. Ton PS Fixing classes inside OpenG builder would fix VIPM, so if you have time join us.

QUOTE (Daklu @ Sep 3 2008, 06:28 PM) I'm absolutely against putting versions into any filename. You should use the build in versioning capabilities of classes, xcontrols and libraries. If you put the version into the library name you have to relink upon upgrade. To beat cross-linking it is better to have a building process in which the source is named different from the code you use in other projects. There are several ways to do so. One of them is VIPM or OpenG builder. Ton

NO SLinG BacK?

QUOTE (alfa @ Sep 3 2008, 03:11 AM) IQ tests to qualify to vote were outlawed in the US. That would be like having an IQ test to participate in a mob (See Plato's Republic). I think the question that really matters is "Can they field dress a moose?" (Fred Thompson, 2-Sep-2008) Ben

QUOTE (Giseli Ramos @ Sep 2 2008, 12:28 PM) Do you have the right port and number? It looks like there is no-listening at that port. Could you post a screenshot? Ton

I assume that the fact you use unnamed cluster elements is a fact LabVIEW dislikes. It probably is some variant optimization bug. Ton (I get similar results)