TG

QUOTE(crelf @ Mar 4 2008, 03:42 PM) I think Ben is (rightly) not using RSS feed because he wants to get content out to the widest possible audience. That includes professionals who are stuck behind secure firewalls and other such blockades.

QUOTE(dthomson @ Feb 16 2008, 05:50 PM) Sounds to me like the scheduler is not handling the refwerence correctly or the error is normal under your scenario. The ref goes invalid because it is in use by the long running VI perhaps? The other Vi sees a locked or busy reference and then assumes it is invalid after a timeout? I can feel ears perking up right now LOL! I may have run into stuff similar to this before but usually I go bezerk and just fall back on a crappy work around to keep things moving along. Like repeatedly testing the reference in a loop (ignoring 1026 error) until it becomes valid again (with a timeout of course). Just thinking out loud here... one thing I know is LV sometimes invalidates references with me but the rules are not so clear as to why. Its always a valid reason but still somewhat of a pain to track down. As an addendum to my senseless gabbing I think if you have not already digested this it might be helpful. At least there may be a clue there and an idea as to how to proceed. http://wiki.lavag.org/Lessons_learned_from_plugins

QUOTE(tcplomp @ Feb 8 2008, 05:22 PM) I appreciate the response Tcplomp. I just wish I could follow through on it. Ive read it a hundred times. please bear with me, this may be a dum Q but how is a mnu file created?

I have always struggled with LabViews palette folders, especially User.lib folder. I have 4 copies of LabVIEW 8.2.1 and I need to work on one program at a time in 4 different places for various reasons. What Id like to be able to do is have "exactly the same" user.lib palette display on the four machines so as to not get twisted around looking for user made VIs. I really would rather have a few meaningful tips as to how this and other nice things could be accomplished. Its easy enough to copy the folder but Q is how do u guys get the palette views to copy over? Also, since Ivs started this one how about a palette tips and tricks thread regarding user palette for future Thank You

Gosh Darnit. I used to get those really great videos u guys post. Now all I get is a blank page. I hope it on Lava';s end.

Id like to know whetre the state charts are in version 8.5? Perhaps I am missing something.

QUOTE(jfazekas @ Feb 6 2008, 05:04 PM) Thats not bad. I thought it would be much slower. Seems proper to make the tradeoff if data privacy and protection is high on the priority list.

QUOTE(JoeLabview @ Feb 3 2008, 07:39 PM) I agree, in my exp there is a lot of eye glazing at NI when a significant Q is asked. That does not happen here. Thats whay I joined in 2006 and never regret it.

QUOTE(Aristos Queue @ Jan 15 2008, 05:17 PM) Even though I found it initially confusing I appreciate that the 'world' is realizing the drawbacks to mouse clicking. I been clicking over 20 yrs now and believe me it actually hurts to click now. Id also like to see visual panning based on eye or head movement.

QUOTE(Michael_Aivaliotis @ Nov 11 2007, 04:05 AM) Thanks Mike. Not only for starting LAVA but for keeping it honest. I personally have learned much about advanced concepts here, simply by reading the posts and trying out the uploaded VI's.

QUOTE(crelf @ Jan 2 2008, 07:35 AM) A nice cold :beer: for -> Tomi (Jimi) for all the expert help you have given me.

QUOTE(PeterB @ Dec 12 2007, 12:33 AM) This is a joke right? Guess not. How about if I installed 8.5 full from the DVD. Do I have to remove these parts or can they be overwritten with a fixed device drivers CD set or DVD? Most likely not using the affected files (yet) (I guess Ill ask NI about this too) BTW Thanks Michael thanks for bringing this up here. Appreciated.

QUOTE(Stevio @ Dec 10 2007, 03:19 PM) There is a nice peak detector in the palletes somewhere. As long as you can find a good offset value as a trigger for the input it will work just fine

QUOTE(Michael_Aivaliotis @ Nov 17 2007, 12:07 AM) Heh Im one of those spagetti guys but can't helpit. Hard habits are hard to break.

quote name='Kevin P' date='Dec 6 2007, 02:37 PM' post='39375'] Could you post the LOGGER code? -Kevin P. Edit -> Arrrgggg!!! I think I found it! Man! Stupid got me again.! Kevin, Thanks for suggetesting I upload this to the forum. It forced me to look really hard and I am pretty sure I found my "issue". Turns out my hard coded path was sitting in a typedef, was defaulting to empty and my error trap was not set up to shut down the LOGGER state machine immediately. Ill let you know if it actually solves the problem when i get access to the rig again. Cold bear coming at ya

QUOTE(Kevin P @ Dec 5 2007, 01:45 PM) Intersting Kevin.. Thats the thing. None of my vis are running to completion. Also there is no way to reduce to an example this since many VIs are instruments and its all coupled. I can't get access to the rig for another week so I'll speculate here, maybe someone can remember some rule or similar occurance. The outter wrapper to the segment above is simply a queued state machine and it is dynamically launched (no wait until finished) from the MAIN processor state machine, which itself is static and runs continously. In other words MAIN is STATIC and launches PROCESSOR and LOGGER PROCESSOR then launches various PROCESS's (clones) the clones send data to LOGGER during their lifetime however the clones have no link to (or even awareness of) the file ref. Only LOGGER has the file ref in its memory shift register. None of the important stuff is shutting down. its just that they are seperate entities not tied to each other by data flow. The file ref seen above is opened by LOGGER The segment above is contained within the "log to disk" frame of LOGGER.. Its all pretty simple actually, despite my imperfect attempt to illustrate with words. The only complex part is that the clones send data packets at odd intervals to LOGGER. It is up to LOGGER to queue up the requests sent to it and execute each request when it can. I think that is generally where the issue is occuring, but I can't figure out how to isolate. If I go through the trouble to decouple the code for an example Im pretyu sure it will work just fine, thats whats driving me nuts. Only reasons I can imagine to see this 1) File Refs created in a dynamic vi (One that has no link to static MAIN); ex; LOGGER, can go invalid for unknown reasons <-ugly 2) Re-entrant VIs messaging to a dymamic vi, (such as LOGGER ) can somehow cause a file ref created within LOGGER to be dropped. <-ugly 3) A Memory cache issue? <ugly but perhaps the most feasible explanation. That beer is getting colder in the fridge...

QUOTE(orko @ Dec 4 2007, 07:19 PM) Thanks orko, I appreciate the thoughts anyway. Ill try to get more info about this. I have to wait until I can access the rig again for further development (troubleshooting) next week. Yeah I am using a number of reentrant clone VIs. They are the producer points for the command to go ahead and execute the diagram above which is a frame of a QSM very much like this one. http://expressionflow.com/2007/10/01/labvi...e-architecture/ The QSM wrapped around this (example) code segment above however is static. I probed the ref num and it is just a number so there is no way to tell if it is valid since sometimes it works and sometimes it shows an error when asking it for the current file position. I have seen this kind of thing before (and felt stupid before) where during a probe the ref appears to be valid but it actually is not, especially with Queue refs, DAQ refs etc..

A free beer to the best answer I have trouble with writing (appending) to text file in a QSM that is in an "occurence mode" of operation whereby the queue waits for outside engueue to go ahead and do a task. The task is simply to write to a file a line of text. (see above) This circuit is contained within a Queues state machine loop. The loop keeps the file reference between iterations. Only an outside event triggers the loop iteration. (not shown) Outside producers give the queue its go ahead and data is sent along etc... WHat I am seeing in the logging function shown here (this is a subVI ) are multiple errors (Error 1) Somehow Labview is not noticing that the reference is valid or it is invalidating the reference., hence the (silly) work around just to get something positive going. Ive seen this kind of thing before my calling VI (outter loop) is not idle this time. Q is Should I just let the outter QSM loop to keep it alive and would that work? What is the rule concerning a loop controlled by queue waiting for an event? Does the VI get flagged as idle and is that why the ref appears to be dropped or is it more likely a cache issue? All i know for sure is is the recycled ref is closing OR generating Error1 just for fun.. The example above works when wrapped in a simple loop but not in my QSM loop that is waiting on an occurence. Anyone know why? Thank You

QUOTE(eaolson @ Nov 21 2007, 04:23 PM) IM no architect but I had discovered this exact behaviour a few months ago when I was trying to learn how to use events beyond the simple UI stuff. Got feedback here that it was a crash on 8 and 8.2. Sorry I never tried to get at the bottom of it but Is this not an NI example? What what I can tell you that event structures can be dangerous creatures if not handled properly. I have learned the hard way and I will not use them (or notifiers) for anything fancy. As to NI thinking it is not a bug I kind of wonder if they might be a little overwhelmed at the moment.

QUOTE(eaolson @ Nov 21 2007, 04:23 PM) IM no architect but I had discovered this exact behaviour a few months ago when I was trying to learn how to use events beyond the simple UI stuff. Got feedback here that it was a crash on 8 and 8.2. Sorry I never tried to get at the bottom of it but Is this not an NI example? What what I can tell you that event structures can be dangerous creatures if not handled properly. I have learned the hard way and I will not use them (or notifiers) for anything fancy. As to NI thinking it is not a bug I kind of wonder if they might be a little overwhelmed at the moment.

QUOTE(torekp @ Nov 7 2007, 02:32 AM) Hey thanks Torekp I appreciate the quick response. This example looks detailed enough to be close to what I am looking for although Ill need a few leisurely hours to figure it out completly. It looks at first glance that you are using Labview default directory as the anchor for all other locations. I know there is a simple way to change path variable in INI file for Labview but have not yet attempted it. Still waiting on that wiki to get wikified;) Thank You

Hi guys I tried LAVA search and found some good stuff but would also like very much to find some (decent) examples of how to use relative paths properly so that the APP can resolve where things are in either Edit or Executable mode. Thank You.

QUOTE(Vladimir Drzik @ Oct 26 2007, 06:57 AM) I may be wrong about this but I have seen this work and then not work when editing strings and such. I think it works until you encounter a LF or until the label resizes. Again not sure but I have seen it not work sometimes. Never studied it further because it is just a minor annoyance.

Nice short story. Nothing like revenge on a rude cell phone user PS I noticed that filmmaker actually had a rolling track for the first scene.

QUOTE(Thang Nguyen @ Sep 12 2007, 06:31 PM) You are making a good point Nguyen. I am always amazed at how little I know (the holes in my knowledge) and I been reading LabVIEW user manuals for years. It would be really nice to see some of the little tricks of the trade explained here. Trust me they are not known by everyone. Might save someone a lot of grief.