LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

TCP Memory Leak?

Solved!
Go to solution

German version with cage clamps, since wire nuts didn't pass the VDE   (german UL) 

 

 

 

 and it's hard to get them in fancy colors.....    yellow/green (PE) for the error cluster might fit 😄

 

Message Edited by Henrik Volkers on 04-03-2009 01:05 PM
Greetings from Germany
Henrik

LV since v3.1

“ground” is a convenient fantasy

'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'


Message 11 of 21
(5,947 Views)
I have not tried the German cage clamps yet, but I have heard that they are prone to picking up data on AM frequencies.  I have a friend who was developing an application and he choose to use the cage clamps instead of the wire nuts, he was easily able to erradicate memory leaks but his data was very noisy.  After transforming the data he discovered that the data contained bits and pieces of transcripts from local AM radio shows.  We talked about it and concluded that it must be the lack of use of the AM frequencies in Germany that allowed the LabVIEW cage clamp technologies to be used there.  Has anyone else seen this?
0 Kudos
Message 12 of 21
(5,921 Views)
0 Kudos
Message 13 of 21
(5,923 Views)

Baji wrote:

I too tried the same wire nuts.I am also wondering about the statement  "Make sure to use the correct gauge or you may not fully resolve the leak" Smiley Very Happy

The VI has only a variant and it is supposed to resolve all the memory leaks as said the above statement.(I am wondering there is some magic inside the block diagram Smiley Wink


Baji, when talking about a JKI toolkit you can take it as fact that there is magic inside the block diagram.

0 Kudos
Message 14 of 21
(5,917 Views)

Hi Dennis,

 

I checked out the link you sent it dint speak about any of these topics memory leak - wire nuts - JKI softwareSmiley Happy. i am slightly skeptic whether you gave a wrong link Smiley Happy

 

You mentioned april fool and am sure who ever saw this toolkit fall under the same categorySmiley Very Happy

 

This forum is a collection of LabVIEW professionals and when i posted this message i expected a healthy discussion and good blazing answers on wire-nuts.  But dint expect such a treatmentSmiley Sad

With regards,
JK
(Certified LabVIEW Developer)
Give Kudos for Good Answers, and Mark it a solution if your problem is solved.
Message 15 of 21
(5,819 Views)

 


Baji, when talking about a JKI toolkit you can take it as fact that there is magic inside the block diagram.

 


All these days LabVIEW was working with Logic and dataflow programming.  When was 'Magic' introduced and why there was no information on that.  None of the LabVIEW training materials speak abt magic.Smiley Very Happy

 

With regards,
JK
(Certified LabVIEW Developer)
Give Kudos for Good Answers, and Mark it a solution if your problem is solved.
Message 16 of 21
(5,818 Views)

Hi Jmcbee


Baji, when talking about a JKI toolkit you can take it as fact that there is magic inside the block diagram.

 I am very glad, When i heard that LabVIEW Introduced MOP(Magic Oriented Programming) as said above Smiley Very Happy. What are the other highlighting features MOPSmiley Wink 

Balaji PK (CLA)
Ever tried. Ever failed. No matter. Try again. Fail again. Fail better

Don't forget Kudos for Good Answers, and Mark a solution if your problem is solved.
Message 17 of 21
(5,814 Views)

Hi,

 

If you tried the wire nuts, how you validate the wire nuts reduces the memory leakage?

 

I saw the code. LabVIEW code gives result only if there is any operation inside the block diagram. 

 

Wire Nut VI's only have a variant control. The memory size of the VI is approximately 8kb. So it doesn't have any operations inside the block diagram.

 

Suppose if the block diagarm functions are hidden, definitly the size is more then 8kb. Smiley Very Happy

 

Regards.

Rathnam.M

 

Regards,
Rathnam.M(CLAD),
Nokia Siemens Network
Message 18 of 21
(5,790 Views)
Hi Dennis, 

Really pissed off Smiley Madof your word April fool. Is this the way that we are treating LabVIEW professions of this forumSmiley Surprised. And I don’t see any logic which avoids the memory leakage problem that expected to be solved from the block diagram that delivered from JK1 toolkitSmiley Wink.

 

Hi Jmcbee,

 

Could you please explain different kind of magic involved in the JK1 toolkit?Smiley Wink I don’t think that a block diagram without a single wire connection will make any magic or logicSmiley Happy.

 

MRK (CLAD)

Message 19 of 21
(5,787 Views)

Well, first of all, get your facts straight. It was jmcbee who posted the April's fool post, Dennis just later pointed out the obvious for those wo did not "get" it after two days. 🙂

 

Look at the full thread. The memory leak problem was solved on fools day after 26 minutes by my post (the first reply!), and it is marked a solution. On a regular day, that would have setteled it. 😄

 

There is nothing wrong with an aprils fools joke once a year and personally I thought it was hilarious. We are aware that not all cultures have this tradition, so Dennis was nice enough to post a link to the relevant wikipedia article. I hope you had as much fun as we did.

 

Looking forward to next years fools day. Keep it up! 😄

Message 20 of 21
(5,731 Views)