PJM_labview

QUOTE(jpdrolet @ Sep 13 2007, 03:48 PM) Oops, and I though I looked at the code carefully enough... You are correct, this is not an error cluster. PJM

Here is another one that would probably win in the "slowest" category. PJM

QUOTE(Aristos Queue @ Sep 13 2007, 11:29 AM) This is not quite correct. If the array is an array of error cluster and if one of the error is the constant used on the BD (as unlikely as it seem) this may return the wrong result. PJM

Ya, this (the Shift+Enter on string constant entry) is pretty usefull and I wish it would work on floating label. I constantly catch myself trying to shift+enter floating labels... PJM

This is quite odd (With debugging off, the text ends up beeing drawn on the top of the image). After further investigation, it appear that this *might* be happening inside the case strucutre were the I16 is coerced to a double (see image below). If you drop an indicator connected to the I16 inside the case structure, everything works fine again. It look like this might be an implaceness optimization bug. PJM

May be I miss it, but what LabVIEW version is the deployed application buidl with? PJM

David If you were to use OpenG Pakcage file (ogp) then you could defined different versions of your librarie(s) to be installed under different LabVIEW versions. If you were to do this, then the ogp version becomes THE unique version. You do not have to worry about where or how to document the different versions included in your zip file. Unfortunately, if you have never made an ogp, this will requires a little bit of work to get started. Just a though. PJM

QUOTE(tcplomp @ Sep 1 2007, 02:05 PM) Ton You can not register event on VI which are not running (this is a pitty really). Therefore the portable event driven approach VI you attached will not help in this situation. PJM

QUOTE(Aristos Queue @ Aug 29 2007, 03:24 PM) This might be true on the Mac, but this does not seem to be the case on PC. I just tried a few controls; and not even one is a multiple of 12 when created. See screenshot below with dimension (width x height) http://forums.lavag.org/index.php?act=attach&type=post&id=6807''>http://forums.lavag.org/index.php?act=attach&type=post&id=6807'>http://forums.lavag.org/index.php?act=attach&type=post&id=6807 PJM

Win XP, LV 8.21 Getting 0 here. PJM

Here, in the US, NI has been know to organize user group meeting at company site (if there is a large enough number of participant). If this is what you are asking about and you have local NI sales people, you might want to contact NI. PJM

QUOTE(Ben @ Aug 24 2007, 05:22 AM) Thanks, but I had nothing to do with it. Jim (Kring) wrote it. QUOTE(Ale914 @ Aug 24 2007, 06:26 AM) PJM is this package also "relink" all the project VI, after change the name? Yes, after you renamed your folder, everything in it has been relinked of course (it would not be very useful otherwise). PJM

Download VIPM and install this package ogrsc_rename_folder_of_vis. This install under your file menu a great utility to move rename ("instanciate for your case") folder of VIs. http://forums.lavag.org/index.php?act=attach&type=post&id=6747 PJM

QUOTE(Neville D @ Aug 23 2007, 03:36 PM) Another thing I am doing (when state logging is not required) is to used a modified version of Daren "String with history probe". This is pretty usefull too. http://forums.lavag.org/index.php?act=attach&type=post&id=6745 http://forums.lavag.org/index.php?act=attach&type=post&id=6746 PJM

One thing I forgot to mentioned in my previous post. Having the ability to log your state name to file (as they got fired) does wonder for debugging. PJM

I played with it, but I don't have a major project involving class. One of the reason is that the entire class is broken when one member VI is broken. AQ, while you tried to explain the reason for it in another LAVA post, this was a huge turn off for me (debugging nightmare--> spend an entire weekend wasting time around this. And yes I know about the red cross next to the culprit VI). This coupled with lvlib relinking "pain in the behind" lead me to conclude, at the time, that the LabVOOP was not useable (I have not revisit this since). Also, I have to say that after reading about all the issues that TOMI encountered, I was not too motivated to spend more time to get into it. Eventually I am sure I will end up using it since I am using other by ref GOOP flavor. PJM

Ben, I will have to disagree that 2-10 state is a max. I do have queue state machine with a lot of states (> 60 and < 100) and it is manageable. As an example, the first time I look a the state machine of the OpenG Builder (done by Kostya Shifershteyn), it was pretty easy for me to follow what was going on (see screenshot below). http://forums.lavag.org/index.php?act=attach&type=post&id=6717 One of the critical issue in my opinion is to organize your state by category that are clearly different one from another. Also using "separator state" (see screenshot again) are very usefull for more that one reason: Another issue is that you have to put some limitation from where you are "allowed" to enqueue more state. If every state can enqueue more state, it becomes very difficult to keep track of what is going on. Typically I limit most of the enqueing to one of the previously mentioned section and from the UI event (Event Structure). PJM

QUOTE(blueshrimp @ Aug 22 2007, 04:04 AM) I think this comment is going to generate a few responses... I have seen quite a few systems that ship to customer with embedded LabVIEW code. If the code is slow this is most likely due poor quality of the code. Nowdays with device such as CompactRio CompactFieldpoint this pretty "easy" to ship product with embedded LabVIEW code. Just my 2c. PJM

Be carfull using fake execution. I found out it tend to make LabVIEW crash every so often (more so LabVIEW 8.2 than LabVIEW 8.0x). But, yes toggling it back to 1 should work. PJM

Yes, some filtering is required. Among other things you probably want to ignore probes. Therefore typically I used the properties below: VI:VIType and VI:IsProbe to achieve this. http://forums.lavag.org/index.php?act=attach&type=post&id=6670 PJM

Use the VI Activation scripting event for this. Works great. http://forums.lavag.org/index.php?act=attach&type=post&id=6661 PJM

QUOTE(Dan Bookwalter @ Aug 15 2007, 09:27 AM) Dan, Answer then: LabVIEW, like any porgramming language, can do anything that you want to do; from application that control hardware to application that have no interaction with hardware. <Shameless plug> As an example of application with no hardware interaction, show them http://jkisoft.com/vipm/' target="_blank">VIPM. This should make them understand that anything can be done. </Shameless plug> PJM

QUOTE(dsaunders @ Aug 1 2007, 05:06 PM) Reading your post just jog my memory. Additionally the value change events fires twice (when only one is expected). http://forums.lavag.org/index.php?act=attach&type=post&id=6517''>http://forums.lavag.org/index.php?act=attach&type=post&id=6517'>http://forums.lavag.org/index.php?act=attach&type=post&id=6517 PJM

QUOTE(Aristos Queue @ Jul 9 2007, 07:20 AM) This is the first thing I looked for as well, and I could not find any either. I will stay away from it. PJM

QUOTE(Aristos Queue @ Jun 25 2007, 11:19 AM) Actually there is one I wrote in 2004. It is available on http://forums.ni.com/ni/board/message?board.id=170&message.id=79506&query.id=716773#M79506' target="_blank">NI forum (Eventhough I though I post it on LAVA too, I was unable to find it). Note: Since that time, a lot of new class of objects have been added to LabVIEW. Therefore it might not work as well on LV 8.x (for example finding wire in flat sequence, disable structure or the like will most likely fail). PJM