BreakPoint

cancel
Showing results for 
Search instead for 
Did you mean: 

Ever dig up your old code?

This may be somewhat similar to the rube thread. But, I was going through and looking at old code I wrote and posted to the forum when I first started using LabVIEW. here are three links from when I was first learning. Anyone else want to post some things that aren't necessarily rube, but just show how far they may have come. I think it will be interesting to see those knights, or people with bright orange blocks next to their name, and some questions they may have originally had when they just didn't quite "get it" yet.
0 Kudos
Message 1 of 16
(12,294 Views)
I was just showing this to a colleague this morning.  It's the first program I wrote when I came to this company two years ago.  I've gotten better...

Digital Pot_BD.jpg
Message Edited by jcarmody on 05-14-2010 12:49 PM
Jim
You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice
For he does not know what will happen; So who can tell him when it will occur? Eccl. 8:7

0 Kudos
Message 2 of 16
(12,284 Views)

I don't have access to my first few programs, but I know it was terrible.  I started with the stacked sequence structure because that is what I saw others do.  Yuck. 

 

Then I went to one loooonnngggg block diagram that you had to scroll horizonatlly for a mile.  It pretty much was the same as the stacked sequence just stretched out with code in each frame being put out end to end.  Yuck again.

 

Then I learned about state machinces, other architectures, proper use of subvi's, and WORM Globals.  Yaaayyy, I've gotten on the right track.

 

- tbob

Inventor of the WORM Global
0 Kudos
Message 3 of 16
(12,276 Views)

I wrote this about ten years ago after discovering all of my disk space disapeared after my son was done using the PC.

 

It was featured as part of the first presentation by Greg McKaskle in his presentation entitled "The Good, The Bad, and The Ugly" as one of "the Bad" ones.

 

The zip is attached.

 

It is a tool analyzes the storage on your hard drive or in a sub-folder and will present the storage as a pie chart where you can click on one of the regions in the Pie-chart to drill down into that folder. At the time there was no other way possible for totaling up the storage on a folder level.

 

So I used this self-assigned homework to learn how to use the Picture Control.

 

The part of this code that had Greg McKaskle stumped was I had written my owm bubble sort since he would have just used the "cluster sort".

 

It was a rough experience hearing my code get ripped apart.

 

I'd post a screen shot but it fills two monitors and only shows half of the code.

 

So have fun and I hope this is helpful to someone (at the very least in laughing at how I used to code).

 

Ben

 

 

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 4 of 16
(12,271 Views)

Re: the code i posted above:

 

THat code was done at home for my own learning only.

 

No customer was ever hurt in the making or running of that code.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 5 of 16
(12,263 Views)

Ben wrote:

Re: the code i posted above:

 

THat code was done at home for my own learning only.

 

No customer was ever hurt in the making or running of that code.

 

Ben


LOL ben has to add a disclaimer to his code!

0 Kudos
Message 6 of 16
(12,262 Views)

Colorful, to say the least! I like the amplifier stuff in the upper right corner. Who knows when that will actually execute? Well, besides the compute at runtime.

 


jcarmody wrote:

Digital Pot_BD.jpg

 

Message Edited by for(imstuck) on 05-14-2010 12:52 PM
0 Kudos
Message 7 of 16
(12,263 Views)

for(imstuck) wrote:

Colorful, to say the least! I like the amplifier stuff in the upper right corner. Who knows when that will actually execute? Well, besides the compute at runtime.



I knew it would start running before I needed it to;  the State Machine has a few init steps and requires operator interaction before ever needing that function.  The sub-VI reads a lock-in amplifier and updates a control on the front panel of the main VI, which then reads the value using Local Variables.  It stops when the main VI stops.

This equipment is still in production and hasn't given me a lick of trouble (once I put circuit protection in front of my Aardvark I2C adapter).  The only worry I have is if I ever need to add functionality; it's not very flexible.  I'd rewrite it if I had to add anything.
Message Edited by jcarmody on 05-14-2010 02:04 PM
Jim
You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice
For he does not know what will happen; So who can tell him when it will occur? Eccl. 8:7

0 Kudos
Message 8 of 16
(12,252 Views)

Does this count as old code?  Originally posted here.  I may have tried to blame HP, but I think this was my own handywork.  Upon reflection, I was an undergrad at the time, so I believe that the 8:36 AM timestamp could only mean that I was up all night in lab.

 

Notebook002.png

Message 9 of 16
(12,235 Views)

jcarmody wrote:

and hasn't given me a lick of trouble (once I put circuit protection in front of my Aardvark I2C adapter). 
Message Edited by jcarmody on 05-14-2010 02:04 PM

Jim-

Can you expand a bit on THAT little nugget-

 

I've got a system that I'm integrating an aardvark I2C adapter into.  Sounds like I could benefit from your experience.


"Should be" isn't "Is" -Jay
0 Kudos
Message 10 of 16
(12,156 Views)