05-27-2013 04:06 AM
A very crude way to create subVIs is to simply select logical groups of code, then do "edit..create subVI" (Be aware that if your selection contains e.g. property nodes or local variables, the outcome might not be very pretty).
Otherwise you simply need to invest some time to learn LabVIEW basics (some subVI related information can be found here). It does not make sense to start a big project with so little knowledge.
I would still recommend that you show us your code. Maybe we can give some more specific advice.
05-27-2013 04:10 AM
Hi Ranjeet Singh,
I said now i'm comfortable in doing subVi, so going for that and hence my VI size will be reduced. Then why do you need my VI..?? Even after reducing the size if problem remains, then I will come back to you with my vi.
05-27-2013 04:20 AM
@sushmith_ks wrote:
I said now i'm comfortable in doing subVi, so going for that and hence my VI size will be reduced. Then why do you need my VI..?? Even after reducing the size if problem remains, then I will come back to you with my vi.
If you create an oversized program with little LabVIEW knowledge (you don't even know about subVIs!), chances are that there a many (many!!!) other problems. Unfortunately, if we cannot see the code, we cannot give more specific advice on how to improve it. Many veterans on this forum have "seen it all" and can probably give you very valuable feedback.
It is in your best interest to show us the code, but nobody forces you to do so. We simply cannot help you past very generic advice if we cannot see what you are actually doing. Your loss!
05-27-2013 04:21 AM
Hi altenbach sir,
Since it is a defence related project I have no rights to share my vi. So 1st let me try with the inputs you have given and I will come back to you with the result, either positive or negative.
05-27-2013 04:22 AM
Like you said in your previous comment -'So edit my vi in such a way that its size reduces.'
This means you are asking someone to edit.Looks like you want to say editing my vi.
Using subVI may reduce the problem but what everybody want to say is remove the redundant code, try to optimize code, do less computation and all that
05-27-2013 04:23 AM
Hi altenbach sir,
Since it is a defence related project I have no rights to share my vi. So 1st let me try with the inputs you have given and I will come back to you with the result, either positive or negative.
05-27-2013 04:30 AM - edited 05-27-2013 01:06 PM
It really scares me when programmers that don't even have basic LabVIEW certification work on defence projects.
Most likely your company has a few experienced programmers. Why don't you ask around?
05-27-2013 04:42 AM
Hello altenbach sir,
Unfortunately yes. There may be someother problems too. I agree. I have attached snapshot of my vi. If you dont know the system working I dont think you can understand the block diagram even if i give my vi, i mean to say you cant edit block diagram without knowing the task. There are so many tasks involved in my project.
05-27-2013 04:44 AM
Hi ranjeet,
I meant I will edit my vi, sorry for misunderstandings.
05-27-2013 05:58 AM
@sushmith_ks wrote:
Hi ranjeet,
I meant I will edit my vi, sorry for misunderstandings.
Friend,
What we want to say is if in your VI there are multilple task is there then why cant you divide each task into subVI and then try to post that problem in this forum. Afterall a good programmer always try to break the large code into small pieces as it is very simple to attack the problem if it is small.
One more thing your VI looks is really scary. If you are trying to optimize this code then this will take ages. Break your VI into subVI and make sure input and output of subVI is working fine. This will take less time. This is called modular programming.
Go to page 6 and 7 of attached ppt. That is what I mean to say