Michael Aivaliotis

QUOTE (vugie @ Mar 19 2009, 04:06 AM)

The "only" thing required for that would be a development environment running on server...

LAVA runs on a linux server. If you have a plan for how we can accomplish this, I'm all ears.

QUOTE (crelf @ Mar 12 2009, 08:27 AM)

It would be great if there was a board plug-in that could show a web-preview of the diagram of uploaded VIs...

Ya that would be great. Now back to reality...

QUOTE (gmart @ Mar 18 2009, 03:13 PM)

A clarification. A project ,by itself, does not load VIs into memory when it is loaded. It is able to determine what dependencies are needed/used without loading VIs into memory. The project does load project items such as libraries or classes which may load VIs.

This is important to note. Thank you gmart for reminding everyone. If some of you see the "loading VIs" dialog popup when you are opening a project, this is because you either use LV classes or lvlibs. Only VIs called by the classes or contained in the lvlibs are loaded into memory, other VIs are not. Watch out for this.

QUOTE (Aristos Queue @ Mar 18 2009, 03:07 PM)

Is that more or less dirty? Can it be made acceptable somehow?

It depends. Can the VI that is being aborted tell if it is? If so then it can exit gracefully. Otherwise, it's a no-no in my books. I would only abort a VI if it's a runaway process, a very very simple VI or I've exhausted all other forms of communication. Like a divorce is to marriage.

I also use a similar stop functional global concept to trap aborts from parallel processes. Mine also has a reset input so you can clear the abort after you've acted upon it.

I'd like to address the use of cases to "case-out" code after an abort. Depending on the granularity of your state machine, you may be able to get away with handling the abort up front and avoiding the need to place the abort checking too deeply in your code. here's how I handle it using the JKI state machine.

I try to avoid putting looping code inside subVIs where I have to later abort them. Instead I use the natural looping of the state machine to repeat test tasks.

I remember watching this back in the 70s as a kid. However, I can't remember the context. Was it before a movie or what? Maybe I saw it on SNL. Not sure. I remember thinking at the time: "That's brilliantly funny".

No idea, I just hopped in to comment that I think your post title is awesome!

I always try to post screenshots. That was the LAVA policy way back at the beginning. Now it seems people are not bothering. Now that the tools have caught up, I think screenshots should always be included.

I think we should all make an effort to post screenshots. Nowadays I prefer video. It's so easy with Screencast.com and Jing (is screencast.com blocked Cat?).

LabVIEW uses Ctrl+G and Ctrl+shift+G to jump to the next or previous item in the Search results list dialog.

I want a similar key combination to navigate to the next error in the Error list.

Currently my process is:

• Click broken run arrow (or ctrl+L)
  
• Scroll the Items with errors list to the top item in the list.
  
• Highlight the first VI in the Items with errors list
  
• Doubleclick the first item in the Block Diagram Errors list.
  
• Fix the error in my code
  
• press ctrl+L to bring the list frontmost
  
• Doubleclick the next item in the Block Diagram Errors list.
  
• Fix the error in my code
  
• press ctrl+L to bring the list frontmost
  
• Repeat process until errors are fixed in the first VI in the list
  
• Continue doubleclicking in the errors and warning list until I'm done.
  

I would like to see a shortcut key that would iterate through the errors in the errors list.

Edit: I'd like to add that LabVIEW needs to be smart so that it wouldn't jump to the next error if it doesn't exist anymore due to a previous fix. However, I don't see this as a big problem since the Error list dialog already performs that checking in real-time anyway.

I can attach an 8.6 VI with that property but it won't help you much since you can't generate the sub-properties from it. You need to do all your work in 7.1. I think there is a wind of change which may see scripting come out of the shadows. Hopefully sooner than later. If you feel strongly about it post your support here.

QUOTE (scott45acp @ Mar 4 2009, 07:00 AM)

I have been mentoring The Hartford Wisconsin team 1091 Oriole Assault. We just got back from the Chicago regional. It was more fun that I ever could have thought it would be.

http://vimeo.com/3430342

Congrats on giving back to the engineers of tomorrow! We need more like you.

Anyone who has a link to the LAVA Forums on their website (like Hooovahh) is cool in my books.

QUOTE (sachsm @ Mar 1 2009, 09:54 AM)

Take a closer look at my example and notice that it is able to differentiate, on a single numeric control, between a double click and two fast successive value changes.

If it works then what's the problem?

Good Job Tomi! Any customer would be very lucky to work with you.

I think a coding challenge involving LVOOP would be nice to see. Also, how about having an NI Forums vs. LAVA Forums competition?

QUOTE (Kubo @ Feb 20 2009, 02:12 PM)

Thank you.

I put a picture of my front panel to better discribe what my program's functionality was supposed to be... I personally work better with drawing stuff out then actually discribing it. However others may obviously disagree.

I agree, that's why you should post an image of your block diagram, not your front panel. There are two parts to a VI. A block diagram and a front panel. We can't see the block diagram.

I've added it.

Sorry, I misunderstood. Actually, the software running on this site is composed of a number of paid software components. One of them being the forums module. More information can be found here.

That guy should have known better. Kids have a better success rate if they're pushed off a cliff.

Thanks for reporting that.

BTW, these aren't "Free" forums.

If you're new at LabVIEW, things can be a little overwhelming. It sounds like your application is working so I wouldn't change anything right now. Look at my attached image for a suggestion to do what you want. Some of the string primitives in LabVIEW require a bit of extra code to get them to do what you want. For example, in the image attached, I had to add a >=0 function to find out if my string actually matched.

PS. I added a linefeed character to your string building. That might make your Terminal output a little more readable.

Hey Alessandro, nice creative use of LIDAR. I was at a robotics show and took a video of a LIDAR that was setup in the middle of the show floor. Check out the video on my blog here: http://michael.aivaliotis.com/2008/11/20/lidar/

An easier fix is just to make sure there is a blank line between each instance of the template.

I've added a feature to the LabVIEW Wiki. Now you can embed flash videos from external sites like youtube, screencast.com, blip.tv etc, etc. All you need to do is switch to the plain text editor and paste the embed code from the site of your choice. Make sure to strip out any <object> code. All you need is the text between the <embed></embed> tags.

I haven't tried it with all video sites. If you need one that doesn't seem to work please let me know in the main support forum and I'll fix it.

I figured the most useful embed would be screencast.com. You can create a screencast to enhance the existing content of a wiki page.

I'm still looking at how to embed video that's uploaded to the wiki directly and not sourced externally. I'll keep you posted.

QUOTE (zmarcoz @ Feb 6 2009, 05:54 AM)

Could you please teach me how to label the wires? I cannot find this function in LabVIEW; and I always do the system label only. Thanks

I suggest you read through the http://wiki.lavag.org/Tips_and_tricks' rel='nofollow' style="background: url(http://wiki.lavag.org/skins/monobook/external.png) center right no-repeat; padding-right: 13px; style="border-bottom: 1px dotted rgb(51, 102, 187); cursor:pointer; text-decoration:none;" class="wiki" alt="Link to LabVIEW Wiki Article: Tips_and_tricks" title="Link to LabVIEW Wiki Article: Tips_and_tricks">Tips_and_tricks Wiki page. This was mentioned in there.