Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
general programming practice question (possibly re: clusters)
JJoe
Member
04-06-2007 06:06 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
I apologize for this probably being an old topic or something I should have found elsewhere, but I simply didn't know what to search for.
I am tackling my first labview program of significant scale, and quickly discovering that the difficulty of wiring scales exponentially with the number of things you're trying to do. I marvel at the short and sweet pieces of code people post on here, and try my hardest to replicate the style to no avail.
If I've missed a good guide for good organizational practices when programming, please point the way!
Essentially, I'm grabbing info from a video signal via a daq card, using this to compute the location of objects in the video, and sending instructions to a robot to control its movement-- this means I have the image wires, serial wires, integer wires for pixel values, real wires for coordinates coordinates, and error wires flying around. It's not an extraordinary amount of data but it seems to be an extraordinary amount of scooting things around to make things look pretty and/or readable, every time I make a change.
Clearly use of subVIs is the way to go for each of the tasks, but I still have several pieces of data that need to be communicated from each task to the next.
Is it common practice to cluster the data even if it's unrelated, just to simplify the wiring? Is there significant overhead if you're unclustering and re-clustering it in each subVI? (I tried to write a quick benchmark program but I couldn't quite figure out how to use the profiler)
Any general veteran tips would be much appreciated!
I am tackling my first labview program of significant scale, and quickly discovering that the difficulty of wiring scales exponentially with the number of things you're trying to do. I marvel at the short and sweet pieces of code people post on here, and try my hardest to replicate the style to no avail.
If I've missed a good guide for good organizational practices when programming, please point the way!
Essentially, I'm grabbing info from a video signal via a daq card, using this to compute the location of objects in the video, and sending instructions to a robot to control its movement-- this means I have the image wires, serial wires, integer wires for pixel values, real wires for coordinates coordinates, and error wires flying around. It's not an extraordinary amount of data but it seems to be an extraordinary amount of scooting things around to make things look pretty and/or readable, every time I make a change.
Clearly use of subVIs is the way to go for each of the tasks, but I still have several pieces of data that need to be communicated from each task to the next.
Is it common practice to cluster the data even if it's unrelated, just to simplify the wiring? Is there significant overhead if you're unclustering and re-clustering it in each subVI? (I tried to write a quick benchmark program but I couldn't quite figure out how to use the profiler)
Any general veteran tips would be much appreciated!
Conseils
Active Participant
04-07-2007 06:01 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Check out the following links: -
http://www.bloomy.com/resources/index.php#pres
Specifically here the Powerpoint presentations (five_techniques_for_better_labview_code.pps)
Some additional pointers/ resources below: -
http://forums.ni.com/ni/board/message?board.id=LVETF&message.id=1
http://zone.ni.com/devzone/cda/tut/p/id/4434
http://openg.org/tiki/tiki-index.php?page=Style%20Guide
There is a host of other information out there as well, try Google and use the term 'LabView style guide'.
Hope this helps put you on the right track.
http://www.bloomy.com/resources/index.php#pres
Specifically here the Powerpoint presentations (five_techniques_for_better_labview_code.pps)
Some additional pointers/ resources below: -
http://forums.ni.com/ni/board/message?board.id=LVETF&message.id=1
http://zone.ni.com/devzone/cda/tut/p/id/4434
http://openg.org/tiki/tiki-index.php?page=Style%20Guide
There is a host of other information out there as well, try Google and use the term 'LabView style guide'.
Hope this helps put you on the right track.
