[Useless Code Corner] Wires Length

[PiDi]

Sooo, fellow LV Programmers, have you ever encountered textual language programmer, who measures "hard work" he's doing by number of lines of code? From now on, you can answer this by telling him how many wires you've laid!

https://decibel.ni.com/content/docs/DOC-28317

With this code you can easily calculate, how much your clients pay per meter of wire! I think this will be revolution in evaluating applications value 😄

Fun fact: to calculate length of wires in this project, I had to use 2.68 meters of wires. One of my commercial projects have about 260 m.

[tst]

Yep - http://lavag.org/topic/8001-wireometer/

I actually do remember writing the code to do this at some point. I think I still have it, although I can't say it's needed now that you posted yours.

Actually, I probably couldn't say it was needed before either. 😉

Also -

http://lavag.org/topic/6448-measuring-diagrams-in-acres-hectares-and-unit-icons/

http://lavag.org/topic/6308-calculate-vi-modularity-index/

[ejkaiser]

Can it also calculate inductance and capacitive cross talk between the wires?

Cheers

Edgar

[Norbert_B]

---

@ejkaiser wrote:

Can it also calculate inductance and capacitive cross talk between the wires?

Cheers

Edgar

---

Or loss of signal strength? Synchronization of signals by equal wire length? What is the speed of signals on a wire (which might create synchronization issues)?

Norbert

[johnsold]

Those are in the add-on toolkit. When released it will cost 100 times as much as the original VIs.

Lynn

[PiDi]

Yeah, I'll also add electromagnetic compatibility testing in future versions 😄

I like to think that errors in my codes are actually signals induced from other wires, not just my faults 😄

[Wire_Warrior]

I shudder to think what would happen if some Software QA or Program Manager whose never actually used LabVIEW should get a hold of this thread. Integration testing would have to start having a bit leakage paramenter,.....and the temperature testing to make sure the wires don't shrink over temp becoming disconnected. What about workmanship? Did we have the wire connections inspected? LOL

[crossrulz]

---

@Wire_Warrior wrote:
I shudder to think what would happen if some Software QA or Program Manager whose never actually used LabVIEW should get a hold of this thread. Integration testing would have to start having a bit leakage paramenter,.....and the temperature testing to make sure the wires don't shrink over temp becoming disconnected. What about workmanship? Did we have the wire connections inspected? LOL

---

That reminds me of an email I have floating around about a QA asking a bunch of questions of a vacuum chamber.  The best part is "how do you know pockets of the vacuum aren't leaking into the room".  Now I have to find it.

[billko]

---

@PiDi wrote:

Yeah, I'll also add electromagnetic compatibility testing in future versions 😄

I like to think that errors in my codes are actually signals induced from other wires, not just my faults 😄

---

Maybe twisted pair wires will help to reduce the errors.  😉

[GregFreeman]

---

@billko wrote:

---

@PiDi wrote:

Yeah, I'll also add electromagnetic compatibility testing in future versions 😄

I like to think that errors in my codes are actually signals induced from other wires, not just my faults 😄

---

Maybe twisted pair wires will help to reduce the errors.  😉

---

I always make sure mine are differential, not single ended.