LAVA 1.0 Content

QUOTE (cheekychops @ Oct 9 2008, 10:56 AM) You need to give us a little more information about the project requirements/guidelines, what type of program/major are you in, where you are located, what access you have to specific I/O hardware, possible budget to purchase additional, HW, etc. My suggestion is that you build a sprinkler system controller with remote web interface.

Is that LV 8.5 or LV 8.6? The messages in LV 8.5 seemed to be lacking in the manner you described but a small test using LV 8.6 (just transfering to LV 8.6 today) looked like we were getting better messages. Ben

QUOTE (Pollux @ Oct 8 2008, 04:45 AM) I see nothing bad with event driven architrectures. I use them for almost all of my GUI's and with user events i have extended their use to more than just the GUI. The "old way" used polling which almost shapes out the same but puts additional load on the CPU to do the polling and introduces a delay if you throttle the polling. Ben

Is there a way to change the default icon mask (pen and glasses) when using the VI for Data member Access Wizard? In the same way, is it possible to remove the automatic numbering for new VI's icon? Especially for classes where it mess up my icon mask. Thanks.

QUOTE (Pollux @ Oct 7 2008, 09:31 AM) Yes it is, using VI server. Look this http://forums.lavag.org/SHAREcompute-factorial-using-recursion-t1543.html' target="_blank">thread For faster performance, you should consider doing recursion on the data only. Goog luck!

QUOTE (Xtian Andres @ Oct 7 2008, 01:24 PM) What is the representation of your array constant? Ton

QUOTE (manojba @ Oct 7 2008, 12:19 PM) It can be a 'Do While' or a 'Do Until', it can auto-index at outputs and inputs (for each). Ton PS and it is patented by NI

QUOTE (sahara agrasen @ Oct 6 2008, 11:03 AM) :ninja: Ben

QUOTE (webbguy @ Oct 3 2008, 08:09 AM) You can only have one RT Startup EXE, which is called when the cRIO system boots up. But you can call additional VIs from the EXE dynamically when it is running. So you can have two or more VIs running on a cRIO at the same time. Once a second VI is started, the main VI or RT EXE can stop running and the second VI will continue to run on its own. The second VI of course can start additional VIs dynamically as well. To do this, become familiar with how to call VIs dynamically using the VI server functions. When building the RT EXE you will need to explicitly include any VIs that you call dynamically in the Build Specification for the RT EXE.

QUOTE (p.gabor @ Oct 3 2008, 10:03 AM) You can make your task a VI and then set it as dialog (VI Poroperties, Windows Appearance, and click Dialog). Then you VI will be shown until execution ended.

QUOTE (sahara agrasen @ Oct 3 2008, 05:28 AM) usually there is a way to download such files...

QUOTE (sahara agrasen @ Oct 2 2008, 10:28 PM) Maybe you can share why you are looking for these? Specifically what types of applications are you interested in? Are you considering using PXI to develop a specific type of application? Providing more infromation about your request will be a lot more useful to those trying to help you. Create Hardware-in-the-Loop Testing Systems for BMW with LabVIEW and PXI Retrofitting Rack-Mount-Based ATEs Using PXI Modules as Virtual Instrumentation RF Summit - Spectrum Monitoring and Signals Intelligence with the NI PXI-5660

This is a cross-post, please mention the other post. Ton

QUOTE (neB @ Oct 2 2008, 07:54 PM) Not that I know of, it was a rail-grinder and I was there for reviewing a system. I think these loco's are custom built. I recently was visiting some upgrading of Class66 loc's where I met some GE folks from Canada. Ton

QUOTE (Ton @ Oct 2 2008, 01:29 PM) That wasn't by any chance a GE built Locomotive was it? Ben

I was recently at a customer and looking up in the cabin of a maintenance train I saw a PXI device with custom cards. No idea what it was doing there but it was there. PXI is just a platform for semi-ruggidized computers. (however I have other experiences with certain SCXI devices). Out of my head: Testing Xbox 360 controllers LHC Ton

QUOTE (crelf @ Oct 2 2008, 04:27 PM) That's someone's personal setting (the by default part), you can enable this on posts. My proposal, the person who reported it to the NI buglist is responsible for the feedback to LAVA. This can easily be done by getting the RSS feed for a specific bug thread and keeping it in a separate group in your aggregator. Then you will be notified if a new response is to that thread. So I would make a new normal NI thread simply stating the bug (might be crosspost) and refer to that NI thread in the NI bug thread so you only get updates for that specific bug. Ton PS Crelf, how long have you changed your avator? (must be RSS-reading to long)

QUOTE (Louis Manfredi @ Oct 1 2008, 11:22 AM) The right-click on Label option sound a good idea. Another argument against the auto-copy of all free-label would be for VI with state machine, events structure or some similar design pattern. This could generate a lot of free-label base on the number of state. Another idea. Using a tag may be interesting to decide which part of the free-label you want to display http://lavag.org/old_files/monthly_10_2008/post-6703-1222957706.gif' target="_blank">

I'll try to condense this to the basics. The LabVIEW Champion have worked with NI and have received their commitment to look into and follow-up on bugs reported here on LAVA with the following limitations/guidelines. 1) The should be reported by posting the NI Bug Thread. (see example here) 2) NI will evaluate those reports and take appropriate action. 3) If the bug is confirmed, NI will confirm this with an update. If the thread is on the NI forum, they will relpy in that thread. If it is on LAVA, they will reply in the Bug Thread (see example here) So for LV this is great news but we still have a loose end that LAVA to deal with. How do we close the loop and get the original thread here on LAVA to reflect the NI follow-up? In the case I above I updated the LAVA thread with a link to the NI response. But I can't be counted on to keep these threads sync'd up. So how would LAVA like to handle this last step? Ben

Roy (Head of LV R&D) posted in the NI Bug Thread found here the following; " I've confirmed the issue discussed in the LAVA thread was previously reported to R&D (CAR # 113018) and subsequently fixed in 8.6. Roy " Ben

QUOTE (AndyDm @ Oct 1 2008, 10:41 AM) The same can be done with MS Paint, by creating the bitmap there and copy/pasting it to LV. http://lavag.org/old_files/monthly_10_2008/post-3370-1222884326.png' target="_blank">

QUOTE (normandinf @ Oct 1 2008, 12:08 PM) Buy another screen for you FP

QUOTE (Louis Manfredi @ Oct 1 2008, 11:22 AM) I should add to my previous... I am not stuck on any of those ideas and methods. I just want to make the documentaion work easier and if Y'all have better/different ideas, please share them. Ben

Very often I find myself copying the documentation I put on the root of the BD (the white background, not inside structures) and pasting it as VI documentaion. It seems that I could save a lot of time if these comments automatically appered in the VI documentation. Thoughts; If there is already text in the VI documentation, then the new free-label text would be added to the end of what is already there, possibly with a header saying "Comments for Block Diagram follow:" If the there is more than one free label they would be seperated by two CRs to make them easier to read. If you don't want it to do this automatically, then how about a button on the VI dialog screen that when clicked copies the text? Another variation would be to add a right-click option to free-lables that woudl copy THAT text to the VI docuemtation? For LVOOP accessor VIs I'd like to it to add documentaion that reads "Get Y where Z" such that Y= the data element being accessed and Z= documentaion for that value as defined in the class data definition. Your thoughts and opinions on this idea are welcome. If y'all think this will save you time, chime in and I'll submit the product suggestion. Take care, Ben

QUOTE (ancle @ Oct 1 2008, 11:02 AM) I think they are in your LabVIEW.ini Ton