×

Our Future . . .

When I initially created this site in 2014, it was to serve two primary purposes.

  1. To document the tips, tricks, and other higher level development practices that make programming for FRC in LabVIEW easier.
  2. Provide a common place for LabVIEW teams to find resources.

At first, this meant documenting the architectural and similar tools that I had learned on my way to becoming a Certified LabVIEW Developer, that had been put to use by the team I was currently mentoring (#3937, Breakaway). (This had the added bonus of helping the senior programmer that had been soaking all this up document it for his successor.)

Since then, this site has had a few additions and updates (mostly by me).

While I have often invited other teams (I am no longer in the AR area and have pretty much lost contact with Breakaway) on CD and at the regionals I've been at to write tutorials for specific topics that they had solved, I was rarely met with a response (specifically once - shout out to the Huskie Robotics 3061 for actually following through, but they were the only ones).

 

In recent years, I have found myself going through some family changes and needing to dial back my commitment to other activities.

This leaves this site both:

  1. Looking for a new champion/curator, that is willing to:
    • maintain the back end,
    • make sure material that becomes obsolete is either updated, or moved to the archives section of the menu,
    • and either write content or get other teams to write content to help this site remain relevant.
  2. Looking for a new source of funding/hosting. (I have been personall providing the $36/yr that it costs to maintain it using Google Domains for the domain name - and email - and Hosting24 for the hosting; I have thought about using some sort of a Donate button, but have not been able to find a platform that allows for *only* raising the target amount).

 

If you have any interest in seeing the continuation of this site, please let me know.

FRC LabVIEW Tutorials - Documentation

Table of Contents

Purpose

The purpose of documentation is twofold:

  1. Others can look at your code and know what you are doing (ranging from mentors, to the next primary programmer, to someone your trying to help)
  2. You can remember what that piece does (or which loop was the ___ in?)

Documentation is very important, and with a few built in tools, your LabVIEW code can be much easier to read.

Simplest - comments

These allow you to put text anywhere in the code to explain what is going on. They can be used to label which motor is which, etc., but it is better to use labels for that.

Adding a comment

Hidden, but useful - labels

Labels are on everything in LabVIEW and (with a few exceptions) you can change them to say what you want. Use them to name your controls and indicators to what they actually represent.

Using labels to document controls and indicators

You can also use them to help keep track of which wire is which.

Using labels to document wires

Harder to find, but extremely useful - Subdiagram labels

Some items in LabVIEW have subdiagram labels (case structures, loops, etc.) - allowing you to put a nice looking comment inside them.

Adding a sublabel to a while loop

If uncertain how or when to use one of these, or would like to suggest another option, please fill out this form.

Google Form