Announcing the New JKI Wire-Nut Toolkit for LabVIEW

by Jim Kring on April 1, 2009 in Company News | 11 comments

JKI is pleased to announce the release of the new Wire-Nut Toolkit for LabVIEW,  a revolutionary new addition to the LabVIEW dataflow programming language, available now!

A Tool You Never Knew You Needed

The JKI Wire-Nut Toolkit for LabVIEW is a collection of dataflow Wire-Nuts that you can use to terminate wires in many different ways.

With the JKI Wire-Nut Toolkit, you never have to leave another output terminal unwired!

Wire Nut Example

The JKI Wire-Nut Toolkit Will Improve Your Code

Here are just a few of the innovative features of the JKI Wire-Nut:

  • Eliminates memory leaks caused by data flowing out of exposed wire ends!
  • Helps keep abstractions from leaking out of LVOOP wires!
  • Protects your coworkers from the shock of finding unwired terminals in your application!
  • Works with all LabVIEW wire gauges, from the tiniest booleans to the largest super-clusters!
  • Never wears out!  Disconnect and reconnect hundreds of trillions of times!
  • Unit tested with VI Tester!
  • Works with your existing LabVIEW wiring tools, like Connect Wire, Probe Data, and Set/Clear Breakpoint!
  • Multiple colors for easy identification!
  • Supersedes JKI Electrical Tape!
  • Safe for use by children and pets!

Act Now!  Download and Install the JKI Wire-Nut Toolkit!

The JKI Wire-Nut Toolkit is available as a VI Package.  If you already have VI Package Manager, just download the JKI Wire-Nut Toolkit here:

Download: jki_lib_wire_nut-1.0.0-1.vip

After you’ve downloaded the package, double-click the .vip file and VI Package Manager will guide you through the installation process.

How To Get VI Package Manager

If you’re not already a VI Package Manager user, what are you waiting for?  VI Package Manager lets you take control of your reusable VIs, and is also the best way to put all the great tools from JKI Labs, OpenG.org, and the whole VI Package Network into your palettes!

Join The Discussion

What will you do with the JKI Wire-Nut Toolkit?  Will it save your project?  Your job?  Your life? Tell us in the comments below! (Also, there’s a lively discussion at LAVA, too.)

Wire-Nut is a registered trademark of Ideal Industries.  LabVIEW is a registered trademark of National Instruments.

  2. jcarmody on April 1, 2009 at 6:12 am

    I installed this package as soon as I got into the office today. I’ve been loosing test data for the longest time and had been thinking that the problem involved a race condition between multiple process stations updating a single data file. Now I’m thinking that the data may be leaking from unterminated wires. We were careful to keep these wires from touching but perhaps that was not enough. Now I can securely terminate these wires and finally put this issue to bed.

    Thank you JKI!

  3. Bruce on April 1, 2009 at 7:05 am

    I installed it and it works like a charm! Don’t know how I ever got by without it. Thanks JKI!

  4. crelf on April 1, 2009 at 7:31 am

    The toolkit is great – thanks so much for that! It gives me a convient place to probe my wires without have to wire them to something else :) Are variant-based wire-nuts on your roadmap, so I don’t get coersion dots on them?

  5. Justin Goeres on April 1, 2009 at 9:23 am

    “We were careful to keep these wires from touching but perhaps that was not enough.”

    That’s a good point. Also, be aware that long, parallel runs of wires can lead to crosstalk problems due to the capacitance between the conductors. This is especially true if the memory registers used to hold the data are too close together in the host computer’s memory. On our internal projects, we frequently use the special “twisted pair” wiring techniques that we’ve developed.

  6. Tomi on April 1, 2009 at 10:31 am

    I placed to blue wire-nut at the open end of my LV Class wire. On first run everything worked like a charm but on the second run, the initial value of my subVI input terminal was interchanged with the previous value of the nut. Can you please investigate this problem. I guess that a sort of worm hole has formed between the terminals.

  10. Jim Kring on April 3, 2009 at 8:52 am

    I’m excited to see that people are already using the JKI Wire-Nut Toolkit to solve some real-world problems. For example, here’s a case where a TCP Memory Leak was fixed using Wire-Nuts. Good work, people!

  11. Jim Kring on April 3, 2009 at 8:56 am

    Tomi: how large was your LV Class object’s data and how long was the wire to the input terminal? There are a few known cases where, due to harmonic resonance, you may need to add another Wire Nut in parallel in order to match the impedance of your subVI’s inputs.