VI's bogging down?

[chuggins143]

---

@Britoa wrote:

---

@Ray.R wrote:

It's always a good idea to backup development software on a regular basis (ie once a day) 😉

---

True, but it's an even better idea to use Source Code Control to handle your backups.  (For a single developer, even setting up a local SVN with tortoise does wonders)

---

Ok, I"m not familar with these terms...  I'll have to go do some reading.    What is Tortoise?  SVN?

THX

C

[Britoa]

Short answer:  Tortoise:  http://tortoisesvn.tigris.org/

Long answer:  SVN is Subversion, it's a source code control server/scheme that generally tracks changes (when you submit them to the source code repository that you set up).  Tortoise is a client, that happens to be able to impliment it's own local SVN repository to work with.  To make a 'backup' it's as simple as a few mouse clicks (to commit your changes to the repository).  And to restore, it's again, in a right click menu.

Neat stuff (it works better with text based files, but still does a good job with Labview)

[chuggins143]

Looks pretty slick... I'll see about digging into it tonight.  Thanks for the tip!

C

[Yamaeda]

---

@chuggins143 wrote:

Ok guys/gals, quick question.... when creating a subVI... When I highlight a section of code that I want to create the sub from, if there are shift registers going in and coming out will those be pulled into the subVI or will they create inputs & outputs on my icon?

THX

C

---

If you select the loop with shift registers they'll end up inside the subvi, the wires get turned into controls/indicators to make a direct replacement in your code.

Sometimes i've managed to get some extra stuff or too little stuff into my subvi, which can have strange effects. Most of the time a simple ctrl+z works and reselect. As mentioned, backup alot, it's always good.

As for SVN, we've rather recently started to use it, and it's simply lovely. One nice thing is the saving of space, as a submit only updates updated vi's even if you submit a full project (it keeps tracks of it), and the data is compressed for nice storage.

/Y

[chuggins143]

---

@Yamaeda wrote:

If you select the loop with shift registers they'll end up inside the subvi, the wires get turned into controls/indicators to make a direct replacement in your code.

Sometimes i've managed to get some extra stuff or too little stuff into my subvi, which can have strange effects. Most of the time a simple ctrl+z works and reselect. As mentioned, backup alot, it's always good.

/Y

---

Yep, when I tried it the first time I ended up with a subVI with about 20 inputs/outputs.... way too many to keep track of.   So I'm reworking it.  Thanks for the insite.

C

[Ben]

---

@chuggins143 wrote:

---

@Yamaeda wrote:

If you select the loop with shift registers they'll end up inside the subvi, the wires get turned into controls/indicators to make a direct replacement in your code.

Sometimes i've managed to get some extra stuff or too little stuff into my subvi, which can have strange effects. Most of the time a simple ctrl+z works and reselect. As mentioned, backup alot, it's always good.

/Y

---

Yep, when I tried it the first time I ended up with a subVI with about 20 inputs/outputs.... way too many to keep track of.   So I'm reworking it.  Thanks for the insite.

C

---

"STOP right there!" (Paradise by the Dashboard Lights Meatloaf, Bat out of Hell album)

You can pass more than one value using a cluster, but if you want to add something latter, you will have to redefine the cluster over again (oh bother).

So please review this Nugget I wrote on "type definitions" before you start using clusters.

Now I feel better.

Ben

[chuggins143]

Ok guys/gals... I've done some serious rewriting and have had it running today to verify that I didn't screw anything up... everything seems to be working fine.  Last iteration ran for about 2.5 hrs before locking up.  All of this time I was running the Profile Performance and Memory feature.... so I've got it saved, I can look and see what's used Max Bytes and such,  but I have nothing to reference it against.  ...what am I looking for?

Thanks!

Chad

[Ben]

You should be looking for VI's that have an ever increasing memory usage.

A large but stable memory footprint is usually not the issue, look for the ever increasing.

Once you have identified the offending VI you can start using

Tools >>> Profile >>> Show Buffer Allocations

to play "wack a mole" and start reducing the buffers.

This thread has some links and suggestions.

These tags are related to LV memory and performance.

If you know the offending VI but still can't figure out to fix it, post it up and let the team here advise.

Ben

[chuggins143]

Sounds good.  Thank you for the direction and insite!

C

[chuggins143]

Ok.. I figured out what was going wrong...  didn't have a issue with an array or anything like that, or anything Labview related as a matter of fact. 

I'm an idiot... my harddrive was full.  DOH!  Went and pulled most of my extraneous crap (music and pics), defragged it and it runs like new. 

Thanks for the help guys, at least I did learn a few new things about diagnosing LabView related issues! 

C