jgcode

QUOTE (zmarcoz @ Jan 13 2009, 05:33 AM) This is terminology on design patterns from NI: Simple VI - block diagram is usually a component/function - typically a subVI General VI - block diagram contains parts e.g. initialise routine >> main (loop) >> shutdown routine. Therefore use the above terminology IMHO: "add 2 numbers" = simple VI "DAQ vi inside a while loop" = general VI

QUOTE (Jim Kring @ Jan 13 2009, 10:37 AM) I think that is the point - MS were suprised at XP's extended lifescycle/the fact that Vista was a dud. Therefore MS are planning to market Windows 7 at all the people still clinging onto XP and won't upgrade to VISTA. Essentially bypassing Vista completely. I think the Vista interface is great, but issues with UAC, driver support, overhead etc.. XP still has its place, it is lightweight and a great candidate for EEE PC's and smaller devices. Windows 7 feels very much like Vista from the GUI perspective. Under the hood tho it is going to need to be good to swing a lot of unhappy people.

QUOTE (hooovahh @ Jan 9 2009, 11:23 PM) Of course it is just for sh :beer: ts and giggles, but it would have been cool if it worked!

My LabVIEW 8.6 installer does not work with Windows 7 Beta

ttt

I have an application whereby I am able to crash the LabVIEW Run Time Engine (8.5). 1. My application consists of a Template VI (which is always in memory) that dynamically loads VIs into a subpanel. 2. These dynamically loaded VIs contain LVOOP classes. 3. In my Build Script in LV AppBuild I rename my LVOOP class VIs with a prefix (I have no inheritance) in order to try and neaten the build. 4. I build the application (success) and run the executable. Randomly the LV RTE will crash when switching between screens (i.e. unloading then loading a dynamic vi into the subpanel). Sometimes on the first switch, other times the 50th switch. Fixes I have found: 1. In the template VI I host an object of each LVOOP Class as a constant of the block diagram. This must keep the class in memory the whole time? As switching between screens in the subpanel is way faster. Seems to be alot of overhead in loading the different classes. 2. Do not rename the LVOOP Class VIs (resulting build structure is more complex) in the build script. Either solution seems (thus far) to make the Application way more robust. Of course with inheritance I would be forced to use Fix 2 as with Fix 1 I would have to use the same prefix (which would still cause a name collision etc..). Question: Is there a known issue with the LV RTE dynamically loading/unloading VIs containing classes that have a prefixed name? If so is this fixed in 8.6 (I dabble in 8.6 at home from time to time but 99.9% of work is 8.5 or 8.5.1 so) I haven't tried with this app. There are some great reads on LAVA about related topics here and here [Cross Post]

QUOTE (zmarcoz @ Jan 3 2009, 10:51 PM) 1. I am in a different country but at the time it was ~ US$200 (discount for NI Alliance member may have applied) 2. No, your objective is constructing a working VI from a given spec [E.g. Traffic Light, Security System, Carwash] and being marked on Functionality, Documentation and Style. It is software development, not hardware so there is no NI-DAQ, Serial and there is no ActiveX. 3. Contact NI Training 4. The manuals are great. You really only need Intermediate I as Intermediate II is about connectivity (VI server, TCP/IP, ActiveX) and whilst great stuff is not critical IMHO. LabVIEW For Everyone is still a great resource for CLD IMHO 5. No, I am under the impression that a certain group of people at NI mark the exams for consistency so there is a turn around cost associated with this (they said 2 weeks in my country, but it was more like 4-5 weeks - but it was around NI Week time so I cut them some slack) 6. [E-Kit] Yes read the course manuals, do the examples, the prep course, read lots (LAVA is great) and practice as time is tight for some (if not all) of the specs

QUOTE (zmarcoz @ Jan 3 2009, 01:57 PM) Hi Zmarcoz. Sitting the NI courses (which I am assuming your are talking about by mentioning $5500) is not a prerequisite to taking the NI exams. However, the course material does lend it self well to the exam content, as the exam assumes you have the knowledge presented in the courses. If you have the time and enjoy self study you can purchase the course manuals at a substantial price difference to taking the courses. Although I am a big fan of the NI courses and certification, there are however other good non-NI references out there. For example, IMHO, LabVIEW For Everyone contains all the relevant information to pass the CLAD and is about 60 bucks. If you search LAVA you will be able to find other topics on good references as well like this one

Happy New Year... A little SNL flavor to ring in the new year...

QUOTE (Ton @ Dec 29 2008, 03:45 PM) You can do it manually as Ton suggested or there is an Open G install by Jim Kring called Rename Folder of VIs that will install into your LabVIEW runtime menu.

QUOTE (crelf @ Dec 25 2008, 05:10 AM) Hi crelf, its an invoke node of a pane. http://lavag.org/old_files/monthly_12_2008/post-10325-1230169711.png' target="_blank">

QUOTE (sachsm @ Dec 20 2008, 07:47 AM) Hi Sachsm Perhaps you could still cache the references as suggested above but run them through a proxy on each call. I.e. if the reference is good (no error) use cache (fast); In that case that the reference is bad (error) then [run state machine] to open a new reference (slow), update cache, then use cache. Therefore you avoid the time penalty associated with opening a reference each time, but you have the proxy ready to kick in when needed to avoid an error that can be handled from a dead reference e.g. when the PC restarts. And all this can be relatively transparent.

QUOTE (LV_FPGA_SE @ Dec 9 2008, 03:50 AM) Well I have used it - and I say damn good job. I actually integrated it into a license manager (client specification) for a third party device and am looking forward to using the NI Hardware component in an upcoming project. The application note was really helpgul and easy to follow. :beer:

God would not need to wear a glove.

QUOTE (mike_nrao @ Dec 9 2008, 06:51 AM) Hi Mike Are you able to elaborate on your test suite - did you get this to run automated? I see NI is beta testing unit tests for VIs, looks really good.

QUOTE (P. Rosegger @ Dec 8 2008, 10:00 PM) Hi P See here for an example that may help Regards JG

QUOTE (Bulletman @ Nov 25 2008, 09:48 PM) Here's a http://www.ni.com/serial/' target="_blank">start for NI serial hardware Which ever hardware platform you choose, from your current spec you will need at least serial 17 ports. Cheers JG

QUOTE (dblk22vball @ Nov 22 2008, 12:15 AM) I'm with Andrey on this one - I don't like use the tab control as a type def. I use the plugin architecture for most GUIs I create, as it is a flexible, scalable design. But I don't think it hard at all to pass data. I dynamically register all universal controls (hosted by the Main UI - e.g. tree control) to an interface that the plugin vis can access Each plugin should handle its own data and have its own UI (no need to pass data to the Main UI) Each screen's data is an object(s). Each other screen can access another screens data through an interface if needed

QUOTE (GraemeJ @ Nov 21 2008, 02:08 PM) If you are using the Mechanical Property "latch" the you can not use a local variable or the write to it's value property. Using an event structure with the boolean placed in the loop is used to refresh the button when a value change occurs. But some more info would help...

Yer, you will definitely need to look at the Database Toolkit, as it is needed. I have used it to talk between LV and MS Access, and it works great.

QUOTE (crelf @ Nov 12 2008, 02:23 PM) Godamn Queenslanders!

QUOTE (Maca @ Nov 12 2008, 10:57 AM) Damn, XXXX? Around here you get beat up for drinking that s@#t!

QUOTE (Thang Nguyen @ Nov 11 2008, 04:49 AM) A knob does not have a needle, (wrt to controls) a dial has a needle. I would have thought a knob would work, i just tried it as a steering wheel and it kinda reminds me of a 2D virtual suicide spinner knob http://lavag.org/old_files/monthly_11_2008/post-10325-1226380346.png' target="_blank">

QUOTE (crelf @ Nov 11 2008, 09:34 AM) Yes I was quite surprised when I found out that you can write VI plugins for SignalExpress. So it does have a place in application development.

QUOTE (crelf @ Nov 11 2008, 09:25 AM) Ahh.. now i understand the reason behind the question!. I will withdraw my previous lame attempt