What is you most reused VI you came up with?

[AeroSoul]

---

@paul_cardinale wrote:

---

Love the icon.

My recently most used is a sub-milisecond delay. 

When i need just a tiny bit of delay when sending single characters with VISA.

[Henrik_Volkers]

today I'm allowed to add something... so here my wfrm renamer ..  the false case just forward the wires

[Frozen]

---

@JÞB wrote:

---

@raphschru wrote:

---

@JÞB wrote:

---

@raphschru wrote:

 - A simple and compact error inserter:

---

You want to right-click that Merge Errors and select "Retain all errors" it changes the glyph so, I know you missed that additional option in 2020.

---

Indeed I never used that functionality, but I usually only care about the first occuring error, as subsequent errors may be a consequence of the first error.

I agree it may add useful infos, but then the default error dialog becomes unreadable and a more complex error management is required too.

---

Then you should:

• Remove the merge errors
• Slap an error case in there
• Slap yourself silly for that

You have written add error if error in is no error

---

Here is my implementation of inserting an error.

[Bob_Schor]

In agreement with @JÞB, my most reused VI is "TEMPLATE Basic VI.vit" (I think I created this more than a decade ago), which I invoke every time I create a new VI (and I tend to create a lot of them, possibly "more than are necessary", but it keeps the "messy details" from obscuring what a VI is "supposed to be doing").  When invoked (from the File, New ... menu option), it creates a new VI in the standard 4-2-2-4 Connector design, with Error In and Error Out (I prefer to use these names, with Proper Case naming) wired to the lower corners, and a blank Icon (to "force" me to create something before I drop an otherwise "invisible" VI on my evolving Block Diagram.  But I also use a lot of Channel Wires ...

Bob Schor

[santo_13]

---

@AeroSoul wrote:

---

@paul_cardinale wrote:

---

Love the icon.

My recently most used is a sub-milisecond delay. 

When i need just a tiny bit of delay when sending single characters with VISA.

---

Why not the high-resolution polling wait?

It is the same technique you've implemented but with better precision since it leverages some windows dll

[Basjong53]

It's a pet peeve of mine, but I always disliked how to add units to numbers on frontpanel indicators. It's either 3.14kHz (%.2pHz) or 3.14k Hz (%.2p Hz).

The standard notation is 3.14 kHz (with a space between the number and prefix), which isn't natively supported. So for frontpanel indicators needing a unit I almost always use this vi that formats it correctly.

 

 

[JÞB]

---

@Basjong53 wrote:

.

The standard notation is 3.14 kHz (with a space between the number and prefix), which isn't natively supported. So for frontpanel indicators needing a unit I almost always use this vi that formats it correctly.

 

 

---

Nope, Mathematically it is 3.14*1000*Cycles/Second or "3.14kHz" where "*" is implied the space breaks the math.

[crossrulz]

---

@Basjong53 wrote:

 

 

---

You might get a little better performance if you changed your lookup to be a map.  This would eliminate the FOR loop and it would use a binary search instead of a linear search.

[paul_cardinale]

"%.2{Hz}p" works, but has the drawback of only working for frequency.

[paul_cardinale]

---

@Basjong53 wrote:

It's a pet peeve of mine, but I always disliked how to add units to numbers on frontpanel indicators. It's either 3.14kHz (%.2pHz) or 3.14k Hz (%.2p Hz).

The standard notation is 3.14 kHz (with a space between the number and prefix), which isn't natively supported. So for frontpanel indicators needing a unit I almost always use this vi that formats it correctly.

 

 

---

Try this