PJM_labview
-
Posts
784 -
Joined
-
Last visited
-
Days Won
10
Content Type
Profiles
Forums
Downloads
Gallery
Posts posted by PJM_labview
-
-
The credit goes to njkirchner that brought this setting to our attention here.
* Directs a spotlight on njkirchner's face* Where did your get that information!
A quick search for that string on my LV 7.x installation (w2k) shows that it is inside labview.exe
PJM
-
Congratulations Didier ! :thumbup:
-
What it mean is that if you copy the utility in LVROOT\Project\Tunnel_Wiring_Wizard.vi ; next time you restart labview it will shows up in under your tool menu (note: LVROOT is most of the time on windows machine C:\Program Files\National Instruments\LabVIEW x.x\)
PJM
-
Thanks for the info. I contacted NI Belgium and this is indeed an example of functionality that cannot be used in an executable since the new default values cannot be saved to the vi because it is embedded in the exe. I have to do it using a configuration file (an ini-file).
Don't you think the application builder should give a warning in such cases?
Greetings,
Manu.
Check the help window (or right click on the node and click on help for....)
For every method property the help will tell you if the method/property is available in the run time engine.
Example for the Make Current Values Default Method
"Make Current Values Default Method
Inherits from VI Methods.
Changes the defaults of all controls on the front panel to be the current values.
The following table lists the flags for this method.
Is settable when the VI is running No
Requires the block diagram to be loaded No
Is available on local LabVIEW only No
Requires the front panel to be loaded Yes
Must wait until user interface is idle Yes
Is available with control VIs No
Is available with global VIs Yes
Is available with strict type definitions No
Is available with polymorphic VIs No
:!: Available in Run-Time Engine No <------------- here
"
PJM
-
Hi guys,
I'm new to this forum, but already thrilled with what I saw. I was amazed by the scripting possibilities. My question : has anyone cursed at the "relink to subVI" feature when there were many instances of the subVI that changed? Especially in big projects this can be annoying. There doen't seem to be a "relink to all" option.
Maybe someone here can do this using scripting?
Thanks for the ideas,
Manu
Here you go
PJM
-
Suppose you want to list all files of a number of types, e.g. only image files of the types bmp, jpg and png. I would like to do it like this :
But this does not work, you have to do it for each type seperately and then combine the different lists. I wish you could separate patterns to match with commas for example.
Manu.
Manu
Check out OpenG.org and more specifically the OpenG Toolkit.
You will find the following enhanced list directory SubVI.
PJM
-
Alex
This is true, in edit mode you can not get as small as you want, but programmatically you can get very small. I had VI getting as small as 4x4 (this is 4 pixel by 4 pixel). I had not done this in 6.02, but I dont see why it should not work.
PJM
-
There are exposed properties nodes that allow copy and pasting anything (LV objects) to the clipboard. I have used them in the past and it work fairly well.
The attached image show where they are located or how to "recreate them"
.What I mean by recreate them, is that when you know there is a method Pnl:Select All, it does not take much guessing that there will be one call BDiag:Select All or Diag:Select All
. Getting at it can be as simple as wiring the appropriate classe specifier to the porperty/method (and the property/method "morp" to the class and stay valid) or as complicated as regenerating the whole specifier constante class + property/method node, wire them together and set the property/method class name (all by scripting of course).:!: When you use these, watch out as it seem that there is no exposed scripting property for emptying the clipboard (which can be a pain).
PJM
-
About the clock: Post #21: this Thread
About the pic: Art of Greg Martin
More image in that style: Google for Digitalblasphemy
-
Nice desktop, where did you get that clock? :thumbup:I see your one of the few here using Internet Explorer
... We have to get you to switch to Firefox. :thumbup:So true
Also, Mozilla Thunderbird (Firefox email client "companion") is worth checking out as well.
PJM
-
Here is my work desktop (only 3 labview version in here)
And here is the bare naked version of it
PJM
-
Michael, I am astonished
otherwise I am starting a topic in this section Is this a picture of Toronto?
My desktop background changes often, sometimes from day to day
Edit: On this pc I don't have LV installed. For LV I have an other pc with special cards inside (arinc, synchro). And the other pc don't have network access :headbang: (I love my usb stick :worship: )
That's one hell of a SCARY desktop picture that you got !
I can't imagine staring at this all day...
PJM
-
Well I've heard rumors of such things before... My request then would be to add support for this feature so we can have it on the palette and don't have to cut/paste it from some other VI. Obviously without message boards I would never be able to use this feature in my native LabVIEW environment. How come I find myself cut/pasting the features I want in LabVIEW instead of NI just giving them to us... rrrrr.....
The official reason is that it is not yet ready (buggy ?) for release on LV7.x [other than PDA] (there was a thread about this a while back on info labview).
Regarding how to make it accessible in your palette, this is quite easy. Customize your palette, add the VI with the comment structure then make sure to set merge VI (RMB).
PJM
-
Didier
I did notice this well. As far as I know there is no way around it (except define one button per size .... ). These ptc file don't seem to have any known header.
PJM
-
NI "patched" all these exposed properties in labview 7.1 installation. So you can re install labview 7.0... or download the attached file (original LV 7.0 NI MAX\Assistants\LVCGen\ folder).
-
Ok I think I got it
The way I understand it, it does the following:
In any "case", whether the control boolean is true or false, an array is build and wired to the shift register.
So, initially, my guess is that the boolean control is set to true, and the array is build independantly form the subvi. Also my other guess is that once the boolean control become set to false, it will be reset to true quickly after.
Then when the boolean control is false and if previous value from the shift register is not equal to the one generated when the boolean control was true, then call the subvi with 2048 as input then again (and here lies another problem) if the boolean control is still false collect all the values from the subvi and display then to the following locals (Barrier A, Barrier B, Dipper, Spare A, Spare B and Relay) then rebuild the array with this value and wire it to the shift register.
This seem indeed to be legit code...
It a nightmare to understand that what's wrong with it!
PJM
Note: Now that I am re reading this, I am not so sure that I understand what's going on ...
-
Well, the file work fine for me (and is in LV7.0). I just redownload it from the forum.
Just in case I attached a 6.1 version (should not make any difference but who know).
I any case, you have the screenshot to get you going
PJM
-
Odd, there no call to anything in that file (only labview primitive).
What version are you running ?
Meanwhile here is a screenshot of the block diagram.
PJM
-
Hi Michael
Use the "system exe.vi" in the communnication palette.
PJM
-
I have a very specific need for an Express VI, basically to use my own dialog message box code instead of NI's so I can move the mouse onto the buttons, set the title, change the appearance, etc. I can currently use my own code but that doesn't allow me to move the constants off the block diagram that are required to set the title, message and button captions (which I find very very helpful when coding to reduce clutter). At times I resort to using the Build Text Express VI but that has obvious disadvantages (mainly making the VI hierarchy window unreadable)
NI charges $500 for their Express VI toolkit which there is no way I'll be able to get. Does anyone out there have it that might be willing to work with me to create one? Or is there anyone with a service for this, ie a flat fee to work with end customer (me) to give me something useful in relatively little time, for relatively little $$$ compared to the whole blooming toolkit?
I'm guessing not but can't hurt to ask... Thanks...
Hi
It is indeed possible to build express VI without NI toolkit.
Check this post: http://forums.lavausergroup.org/index.php?showtopic=376
Read especially post #5 and #6 by Jim Kring. Also NI has a doc explaining some stuff about how express VI work. I will try to dig it up again if you need it.
If you need more help, let me know.
PJM
-
Check the attached example (LV7.0)
PJM
-
-
Jean Pierre,
Lately I was playing around with the OpenGoop Framework and I realised it would be usefull if we could dynamically update Strictly type VI ref num in each class (being able to keep typedef is important in this case).
Attached is a llb that does that.
Also, check out the following VI "Variant to Flatten String {preserve typedef}.vi", I think it could be used as a possible replacement/enhancement to the native Variant to Flatten String primitive.
Cheer
Philippe
-
...
Yes but as commented in Remove Typdef From Variant there was a bug in LabVIEW 6.1 such that Variant to Flattened String did return an invalid type descriptor when used with typedefs. The VI was introduced as a workaround. Typedef information in type descriptors was introduced in LabVIEW 6.1 and this bug was a big disapointment since it did make LabVIEW Data Tools useless on typedef variant.
...
Ah, I did not know that LV6.1 Variant to Flattened String was returning invalid type desciptor with typedef information.
...I did not dig in documentation recently but I think that this typedef information is not yet documented for type descriptors (LV7 is shipped with the same old Application note 154). LabVIEW Data Tools have never been implemented to use that typedef information in variants. The returned type descriptor was invalid anyway.
Now that you have made me look more closely, it seems that the typedef feature was removed in LV7 (type descriptors from Flatten to String and Variant to Flattened String don't include typedef information anymore...). That makes me wonder if that was a feature in LV6.1 or a simply a plain bug. It is from LV6.1 that typdefs are displayed in variants, wire help and that typedef conversion is indicated with a coercion dot. Internally this information is carried in data type and maybe it was just a bug in LV6.1 that made it leaked in type descriptors....
Jean-Pierre
I did not realized until quite recently that Variant to Flattened String was not working (read was automatically stripping typedef) with typedef in LV 7.x. I think I figure out a way to get the typedef in the type descriptor using flatten to string with expose type def turned on and doing some stripping and "padding". This is not documented anywhere as far as I know, but it seem to work well in LV7x (a quick test under 6.1 seem OK). See attached VI.
Also, I noticed that the only way to get typedef info from controls on VIs is to used Get All Control Values {variant} methods. Every other way return type descriptors with no typedef info.
PJM
Tiff without IMAQ vision?
in Machine Vision and Imaging
Posted
Koji Ohashi has a tiff library
It supports on files in 8bit RGB or 8bit B&W Motorola byte order.
You can download it from below.
http://www.asahi-net.or.jp/~WR9K-OOHS/Pages/english.html
File name is Red27(lv6).zip(528k).
PJM