didierj

...tss, tss, tss... how foolish :laugh:

Every question on this forum is important... Please consider these sites: Guidelines and here If your question isn't answered in 24 hours it's not because we don't like you. Everyone here has a real life. Maybe we have to test a workaround on your question needing more than 5 minutes of investigations, Maybe there is no solution, Maybe nobody knows about it and has an answer. ...To your question: I don't know the Matlab script node, but will the .m-files be readable form the script node? Otherwise you could try to break your matlab code in a way that the script node can be put into a loop, and a possibly existing iteration is performed in LV instead inside the matlab script. Didier

I think it won't work even for LV. Your LV package is not only dependant on the hardware platform, but also on the operating system. A MAC-LV (even an Intel-MAC-LV) has different interfaces (eg. display-, event-, keyboard-interface) to the OS than a Win-LV.

You forget the XNodes. They have the ability to run in the block diagram. ...ok, you need a vi that begins with ";...". But it can be hidden in a fairly complicated example (like the rmb-menu example). :thumbdown: EDIT: The combination of XNodes and self-reproducing code makes a powerful "copyright watermark" or an extremely dangerous virus: a vi that runs from the moment you open the block diagram and copies itself to all the vi's (if it doesn't exist there already) of the project or found on HD. You end opening vis, removing the code and when you open the next block diagram it is back there on the "cleaned" vis.

It is normal that the poly-vi is turned into a static vi. LV is datatype bound and so your "outer vi" supplies a value of a known datatype. LV recognizes it an on a double-click on the "innner vi" opens the correct "static" vi. That's the reason why you make poly-vi's. They are just a container for a collection of similar vi's (same operations, same connector panes, but different datatypes as input/output). While plopping a poly-vi onto the block diagram, it recognizes the needed datatype and places the correct collection member on the block diagram.

Sorry, my fingers were too fast, means "rmb (right mouse button) on led, select from the pull down-menu "create/local variable". ...voil

Regarding the "poymorphic", check the ini-file functions in your palette. You don't have to use the full complexity, but it gives the idea. Have separate vi's for opening and closing the port, and a set of vi's (grouped into a polymorphic vi) that do the transmission for a specific datatype. This way you can add a new vi with a new datatype when need rises. If you prefer the variant datatype, check OpenG. There you'll get (by installing OpenG commander and downloading the packages) a whole set of vi's to work with variants. Didier

Good example mross, at the first glance it looks rather complicated but includes everything, just worth of a "two-houres-LV-basic-course" :thumbup: Jaw, your next step would have been to tell your computer to switch off the leds, means wirting a false to a local variable of the led (rmd on led, select "crate/local variable"). Seems you missed two things: - how to create local variables in LV - the computer doesn't do anything unless you tell him exactly what to do, even with 3+GHz processors they are still dumb Didier

Then show us what you did so far. Good resources on how to program in LV are: - the thousands of examples: Menu "Help/Find Examples..." - The LabVIEW FAQ of this site - Most probably you'll find few books in your campus library.

How to use the LAVA Website ... we are not your "Homework Hustlers", thanks :thumbdown: EDIT: Could any admin remove the duplicate in Forum Feedback & Support?

After you uninstalled your LV7.1.1 copy, was the folder <program files\National Instruments\LabVIEW 7.1> gone or stilll there? If it stayes then delete it and only afterwards reinstall your LV7.1. I've already seen (on other programs) that some installer do not overwrite files but keep the copy that is already on disk. ...On the same occasion, after uninstalling LV7.1 try to build a LV8 app (with installer). If it also fails, then it would mean that the LV8 is looking for some files at the wrong location (in LV7.1 directory instead of LV8 directory) and you either got a bug in the LV8 installer or were a bit careless while programming (e.g. opened a vi from LV8 from the wrong directory).

If you can manage a good algorithm I'm also interested in it. It just happened that last night I had to stand up several times and chase away my neighbor cats. My neighbor has 4 or 5 female cats and so often all the males (of the village) are lurking around meowing the whole night. :thumbdown:

You are fortunate, I got last digest before weekend (April 28).

If I read your mail correct, the "increasing loop" is inside the start event case. If so you have two possiblities: Either move your "increasing loop" outside the event-loop and communicate with notifiers or queues. Or, set the timeout of your event-structure to -1, Start-case sets it to e.g. 1000ms and pause/stop-case sets it back to -1. In the timeout-case increase your value by +1. (see example) Didier Download File:post-253-1146231692.vi

Never was in Australia, but from what I heard, there it applies to men and also to women (throughout Europe beer is more a "men's-world").

I'm still alive... but the "dull course of live" cought me up . The whole forum is unusually quiet.

Usually a project folder is divided first into - Documents: as it says, descriptions of the code - Work: The place where I put the vi's - Build: The place where the app builder puts the exe and installer - Archive: list of zip-archives containing "Work" for the different revisions In the project folder itself is also - bld-file - app-icon - revision-history (usually a simple text file). the "Work" directory is the further divided into module-folders as crelf described (since I use openGoop the subdivision is done automaticly). In "Work" is also - top-vi - vi-list vi (containing top-vi and all dynamically called vi's) - ini-file - maybe a few more vi's that I can't assign to a specific module - dll's. Didier

Just checked the picture wire by "un-typecasting" it (see picture): Run the vi and theck the typecast output. It shows that the value "5" is written correctly to the picture-wire. Now change the line type from "solid" to e.g. "dot": ...strange "antenna" that is written on top of the line. To me it looks like the drawing algorithm of the picture control has really a bug... maybe the algorithm that produces the rounded end of the line.

The radio just reminds me: Sunday is "Tag des Deutschen Bieres" (transl: "day of german beer"). The German purity law was issued on April, 23 1516 by Wilhelm IV. :beer: Cheers :beer:

Or alternatively select the code portion you want and copy it to clipboard with <CTRL>+<C>. Cheers :beer:

I know of this Domino-Day and never miss to watch it on TV (even that I don't owe a TV, fortunately my mother-in-law owes one). Someone built up this "Incredible Machine" and was (hopefully) paid for that... Where do I have to apply for this job??

If your installer works, depends on what your privileges (of your user-account) are and what you want to install. - "Installing" an app (with user privileges) by just copying some files to a repository will work most probably. - Installing the runtime engine won't work, since the installer has to write some registry keys into a section you don't have write access (HKLM) as simple user. Skipping privileges that are system-wide from inside an app is not possible. Newer Installer allow to check privileges and on install time pop up a box allowing to select a different account, but this would mean that you have to build your installer by yourself (with e.g. InstallShield). The only workaround I see, is to log in as administrator (if you work in a "big" company you'll most probably have to ask your computer-admin to do the job). Didier

All those fitness-clubs going bankrupt, how bad... ...but on the other hand, doctors would let patients learn LV instead of sending them to the mountains for cure. :laugh: Hillarious, reminds me those "domino-days" (endless raining days in my childhood), working on room wide (sometimes even homewide) domino constructions together with Lego, Playmobil,... :thumbup:

It must be 7.1, since it's the version I used to make the test.

Let's move to the holo-deck... :laugh: Translation: Hans-Juergen waters his virtual cactus once a week