What did YOU learn today? Get your Daily Micro-Nuggets here.

[Wayne.C]

Be very carefull when dealing with a .llb archive a former   coworker created that contains all the vi's and custom controls from a LV7.1 project.  Including those normally found in vi.lib folder.  I pulled everything out of the .llb and put it in a folder.  All of a sudden my beloved Code Capture Tool quit working.

[Broken_Arrow]

I learned that I can use Wait For Front Panel Activity inside a non-modal SubVI to monitor a click on the calling VI.

I also learned if you create a VI from a selection that contains Wait For Front Panel Activity, LabVIEW will place a Property Node on the calling VI so you can get the pane reference in a jiffy. Neat!

[Broken_Arrow]

I learned that the new undocumented Coerce to Type indeed should be supported, and I learned a good use for it as shown. I built a cluster and typed the wire to my Type Def, which you might otherwise do with a TypeCast...

... see Jack's idea and follow some discussions..

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Officially-Support-quot-Coerce-to-Type-quot/idi-p/1213...

[GregFreeman]

repost from here

Readers digest version-

For loop sampling going slow as hell on FPGA. WTF thought it should be fast! Is my DMA FIFO overflowing? NO!, Are my indicators just not updating quick enough to reflect the FPGA indicator values changing? Maybe...but NO!

What ever could it be???

"Found the problem. The RTDs I am using default to "accuracy" mode. These RTDs also do not have simultaneous sampling (NI 9217). In accuracy mode, the conversion time is set to 200 ms. That explains why when I bench marked it was taking 800 ms to execute one for loop iteration (200 ms/channel * 4 channels).

To fix this go to your project, right click any given RTD, choose properties, change conversion time to 2.5 ms."

Can I get a few hours of the contract back now please??????

[JackDunaway]

---

@broken Arrow wrote:

I learned that the new undocumented Coerce to Type indeed should be supported, and I learned a good use for it as shown. I built a cluster and typed the wire to my Type Def, which you might otherwise do with a TypeCast...

... see Jack's idea and follow some discussions..

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Officially-Support-quot-Coerce-to-Type-quot/idi-p/1213...

---

Thanks for the plug! I've got to ask... why not go simpler:

But to keep with the spirit of this thread, I've got to introduce a micro-nugget, so, let's see....

Not explicitly code related, but I have found some great LabVIEW articles and resources in some of the most unlikely places using Google Alerts. Using "LabVIEW" as a search term is a bad idea: I have slowly been refining my query over the past few weeks such that it currently looks like "LabVIEW -torrent -crack -rapidshare -hotfile -megaupload -warez" for reasons you can probably imagine.

This also solved the mystery as to why one of my old Ideas out-of-the-blue caught the glint of a few people's eyes. 😉

[Broken_Arrow]

---

JackDunaway wrote:

Thanks for the plug! I've got to ask... why not go simpler:

---

My quick edit to my code in order to post a screenshot ended up missing a wire which would have gotten across the point that I typed dissimilar sub-cluster names.

Edit: Oh wait! I can't reply without a Micro-Nugget, but it's Sunday... well today I learned that normal high quality brushes are always a better bet than cheap foam brushes even when applying stain.

[JackDunaway]

---

Broken Arrow wrote:

My quick edit to my code in order to post a screenshot ended up missing a wire which would have gotten across the point that I typed dissimilar sub-cluster names.

---

In both your snippet and mine, the output wire will assume the names of the cluster constant (regardless of the names of the wires coming into the Bundle), so I still hold the Coerce to Type is unnecessary.

And in the spirit of introducing one nugget per post...

Typedefs are bad. Don't create them.* "Fustercluck" traditionally refers to what invariably will happen if you do not typedef a cluster, but a new strain of fustercluck has emerged that attacks those who do typedef data structures.

*Overstatement, not meant to be taken literally, read link for details.

[F._Schubert]

Today, I found that 'New Vi' is available via 'Open Application Reference', but many scripting properties are not.

Anyone interested in a competition for a StuxNetLabVIEW?

Felix

[Broken_Arrow]

---

JackDunaway wrote:

In both your snippet and mine, the output wire will assume the names of the cluster constant (regardless of the names of the wires coming into the Bundle), so I still hold the Coerce to Type is unnecessary.

---

I meant like this.... Is there another obvious way to do this??...

 

[JackDunaway]

An added benefit of the method below is it shows explicitly that "Apples" is being wired into "Coffee".

Micronugget: PNG screenshots compress to a smaller filesize than JPG for code screenshots, and the compression mechanism is lossless instead of lossy. Win-win! 😉