Skip navigation

Community

1 2 Previous Next

LabVIEW Tools Network Developer Center

22 Posts tagged with the partners tag
0

Cool Toys for Big Kids

Posted by penrenpo Dec 19, 2013

toys.jpg

Let’s face it, the holidays are for kids - sons, daughters, nieces, nephews, and grandkids, all wide-eyed and squealing with laughter on Christmas Eve or morning about the gifts that Santa delivered. But what about the big kid on our shopping list?  As a mom and marketer, I’m inundated with the flashy, full-colored print ads in the mailbox, and online ads in my inbox for every retailer on the planet. However being married to a gadget geek, I still struggle with finding that cool gift for my tech savvy husband and not ending up with the traditional shirt/tie box set, new video game, or favorite collegiate or pro football clothing or gear. We’re really all just big kids living vicariously through our younger generation and the evolution of technology they can access.  And who needs another pair of Darth Vader lounge pants?

 

Get the big kid on your list what they really want – new software “toys” from the LabVIEW Tools Network!  These cool tools will give you hours of LabVIEW playtime and hopefully an excuse to escape the “assembly-required” part of kid’s holiday gifts.  Grab some hot cocoa, sneak off to your computer hide-out, download from the list below, and get started.

 

 

Electronics Prototyping - LabVIEW Interface for Arduino Toolkit

Interface Your Microsoft Kinect with LabVIEW - Kinesthesia Toolkit for Microsoft Kinect

Control Your Synthesizers, Musical Instruments and other Multimedia Devices - Open Sound Control for LabVIEW

Build VIs for Drones - AR Drone Toolkit for LabVIEW

Create a Robot with Your Roomba Vacuum - iRobot Create for LabVIEW

 

 

LabVIEW Hacker, creators of the AR Drone Toolkit and iRobot Create, have some exciting software toys designed to interface with a variety of cool devices:

 

Use the Leap Motion Controller to Capture Gestures with LabVIEW - LabVIEW Leap Interface

Send and Receive Tweets Without Leaving LabVIEW - i3 Twitter Toolkit for LabVIEW

Utilize the Sensors of an Android Device Directly in LabVIEW - LabVIEW Android Interface

Pull Motion Data and Button Actions from a Nintendo Wiimote into LabVIEW - LabVIEW Wiimote Interface

 

 

Have fun and Happy Holidays!

 

 

Penny Wright

Marketing Communications Manager

LabVIEW Tools Network

0

Your website is an important vehicle to help generate leads for your business and to create awareness for your products and solutions. This section covers the following:

 

  1. Things to Consider When Creating Your Website
  2. Making Your Website Search Engine-Friendly
  3. Linking to ni.com from Your Website

 

 

1. Things to Consider When Creating Your Website

  • Clearly define the strategy for your site and decide on the primary goals and objectives.
    It is important to establish what you are trying to accomplish in each area of your site. Having clearly identified objectives (i.e.collecting leads, driving e-commerce, generating inbound calls, educating users) helps you prioritize which content to include on your pages. When adding content to an area of your web site, always ask yourself, "Does this content match my objective?"

  • Create compelling content and present it clearly on your site.
    When writing content for your website, keep your users in mind. Address their needs, pain points, and concerns and explain how your products and solutions alleviate those problems. They care about how your system benefits them. Having useful content is crucial, but it doesn’t help anyone if users cannot find it on your site. Think about how to most logically group your content and organize it on your site. Clearly label sections of information and pieces of content so that users can skim the page and find what they’re looking for. Based on your experience with your customers, highlight their most typical key points of interest.

  • Check to make sure you have a clear user experience and friendly interface.
    Make sure that your site is easy to use and to navigate for your users. If it’s hard for them to find what they’re looking for, they might give up and leave. It is tempting to try to cram a bunch of content and calls to action on one page, but that often clutters the experience and potentially confuses the user. If in doubt, keep things simple, and refer to your primary objectives to decide what to prioritize and present on the page. When you are working with customers, feel free to request their feedback on your website, and what they would like to add or change.

2. Make Your Website Search Engine-Friendly

Search engine optimization (SEO) helps increase traffic, and therefore leads, to your website. This section covers the following: understanding how search works, understanding the user, optimizing content on the page, and promoting content off the page. This is intended as a basic introduction. There is much more you can learn about SEO. It is recommended that you continue pursuing this topic as it can directly impact the performance of your website.

 

Understanding How Search Works

Search engines feature four main functions:

  1. Finding content: Search engines use software (bots) that move from page to page through links to find your content.
  2. Indexing content: This is the process of bots parsing through the HTML on a page and storing it in a file for the search engine to reference when a user searches for a term.
  3. Returning results to the user based on relevancy: The main way that search engines determine relevancy to a page is through something called anchor text or link text. Anchor text is the visible, clickable text in a hyperlink. You want this anchor text to match as closely as possible to the keyword you are trying to optimize.
  4. Ranking those results based on importance: Search engines determine importance based on popularity and the quality of your popularity (for example, who is deeming your content popular). Search engines are trying to reward good content, so it assumes that popular content is deemed good by users.

Understanding the User

The way the user interacts with a search engine is by inputting keywords. It’s important to understand the language users use to describe their applications and your products and services. That way, you can get the right people to your site. By using these keywords in your web site content, search engines will associate your web site with these keywords and direct users to it.

 

Brainstorming Keywords

  • Ask yourself/sales team
  • Search the keyword
  • Use your web analytics tool
  • Look it up on the Google keyword tool
  • Test it with Google AdWords

Selecting Keywords

  • Narrow your list of keywords down to 1-3 per page
  • Think about long tail SEO. That is the distribution of search terms from broad to niche. Which 20% of keywords gives you 80% of the correct traffic?
  • Broad terms: A very broad word such as “daq” is going to get a lot of search traffic, have a lot of competition, and have a lower probability of converting.
  • More niche terms: These phrases have less competition and less search volume, meaning you could potentially get less traffic to your site. But these terms also convert better, meaning the customers that get to your site are more likely to continue shopping and browsing because your site applies to them well.
  • When selecting a particular keyword for one page, think about your goals. Are you trying to build awareness that you are a DAQ vendor but are less concerned with converting people to leads or sales? Then a broad term might be a good decision.

 

Optimizing Content on the Page

Search engines view certain content on the page as more important based on where you place it. The items with a higher weight are page title, headings, and URL, so you want to make sure that your keywords are included at this level.

  • HTML tag: This is a code surrounded by brackets (<>) that denotes format, hyperlinks, or information for the bot.
  • Page title: The page title or title tag shows up in a few places. It is visible at the top of the browser. It is also the clickable link in the search engine results.
  • Meta tag: This is a type of HTML tag that gives information about the page. The bot can see this information in the HTML, but the user can’t see it on the page. Users can see it on the search engine results page below the clickable link. It is not a factor in determining your rankings, but it can help persuade users to click on your link versus another one on the first page.
  • Heading: This is recognized by the HTML tag “H” and then the number, such as H1 or H2 as the heading tag.
  • Keyword at the page level: Sprinkle the keyword throughout the body content, with a few variations to allow for user variations in the query and for natural writing in the content. At the page level, it’s really important to remember your users. If they type in a search term, get to a page, and find out it’s not about that keyword, they’re going to leave.

Promoting Content off the Page

Of all the things you can do to optimize your content for search, this is the most important. The search engine determines your popularity and relevence at the top of the results page largely based on which external sites link to yours.

  • Get links from trusted, relevant sites. Examples include:
    • Credible institutions: .edu, .gov
    • User-generated: blogs, forums
  • Focus more on external links than internal
  • Get links from multiple unique domains

 

Build links to your site by

  1. Creating exciting content: If people are really excited about what you do as a company, they are naturally going to talk about you and link back to your site.
  2. Building relationships: Build relationships with editors to get them to write articles for you; build relationships with bloggers in your industry to get them to write posts about you.
  3. Taking advantage of social media: Post comments on blogs and forums related to your industry. Social media is a great way to get links back to your site.
  4. Participating: Make sure you are participating in the forums, conferences, and communities that contain your target audience. This helps you spread the word, forge relationships, build credibility, and much more.

 

3. Linking to ni.com from Your Website

Cross-linking between relevant and content-rich sites is important for driving traffic. Your company can greatly benefit from linking to our site. For example, by linking between sites, you improve your ranking in web search engines, as we just discussed above. Higher rankings mean better chances that customers will come to both ni.com and your websites looking for your services and solutions.

 

As a contributor to the LabVIEW Tools Network, take advantage of the Related Links section of your model page to link back to important documentation and demos on your own website. Link back to your model page on ni.com and the LabVIEW Tools Network to strengthen the link connection.

 

As always, feel free to post your own ideas below.

 

Will Schoettler

LabVIEW Tools Network Product Manager

2

Design and Implementation

 

In Tools For Developing Tools, Part 1 we looked at a variety of tools that improve the process of creating detailed documentation that meets the Compatible with LabVIEW standard.  In order to utilize tools for documentation, you must have code worth documenting.  Fortunately, there are a wide array of different tools available on the LabVIEW Tools Network that assist in the the actual design and implementation of a large application.  Many of the tools on the LabVIEW Tools Network are extremely useful for specific applications, such as the set of VIs used to program KUKA Robots.  The focus of this post will be on more generic tools that are useful in a wider variety of applications.

 

 

General Purpose Toolkits

openg_libraries_l.jpg

 

OpenG Libraries

 

The OpenG community has built and shared hundreds of open-source VIs that cover a wide variety of different functions.  There are additional palettes with advanced functions for working with arrays, strings, application control, file handling, and more.  If you aren't already using OpenG, you probably should be.

 

 

GPower Toolsets

 

Another set of useful functions, the GPower Toolsets include functionality for advanced error handling, timing functions, overflow arithmetic, dynamic VIs, and more.  They also introduce the concept of VI Registers, which are extremely useful for global access throughout your application.

 

 

MGI Library - Moore Good Ideas

 

Moore Good Ideas employees consolidated a free set of VIs created by MGI over time.  This toolkit includes functions for most of the categories in the default LabVIEW Programming palette, expanding on built-in functionality with advanced re-usable VIs.

 

 

NI Labs: LabVIEW VI Scripting

 

VI scripting allows you to programmatically generate, run, inspect, and modify LabVIEW code.  These tools are indispensable when working with large sets of code, and can significantly decrease the amount of time needed to generate large libraries.

 

 

EasyGIO Tools

 

EasyGIO Tools is an add-on that addresses a wide variety of new functionality.  It includes VIs to create HTML help files automatically, set help options programmatically, modify VI descriptions, update front panel tip strips, and more.  In fact, this tool addresses much more than just documentation.  It includes functions that manipulate controls on your front panel, easily create FGVs, rename and save VIs without conflicts, and create a top-level VI with project.  The EasyGIO Tools are exceptionaly useful utility VIs that assist in many phases of development.

 

 

Third-Party Licensing and Activation Toolkit

 

Properly licensing code for distribution to customers presents a number of challenges, such as managing activations and preventing fraud.  Implementing custom licensing can be very time consuming, especially when maintaining a positive end-user experience.  The Third-Party Licensing and Activation Toolkit is an out-of-the-box solution that takes care of licensing, activation, evaluation, and more.  It supports development and deployment licensing and is highly recommended for use with any code that needs to be licensed.

 

 

Source Code Control


tsvntoolbar_l.jpgTSVN Toolkit

 

Source code control allows teams of developers to ensure easy access to shared code while mitigating conflicting changes, allowing check outs of code, merging versions, and more.  Tortoise SVN is a very popular free set of code that performs source code control from a file browser.  Viewpoint Systems' TSVN Toolkit integrates the functionality of source code control programs directly into LabVIEW, extending the native source code control of LabVIEW with an intuitive interface that overlays directly on a LabVIEW project.

 

 

TortoiseSVN Tool for LabVIEW

 

Similar to TSVN, this toolkit incorporates source code control into the LabVIEW Tools menu.  Created by JKI, this full-featured toolkit saves time for developers, accessing common TortoiseSVN operations without leaving LabVIEW, allowing them to focus on their work rather than source code control.

 

 

Clusters and OOP

 

Cluster_Toolkit_l.jpg

 

Cluster Toolkit

 

Clusters are an extremely powerful way to manage elements in LabVIEW.  This set of VIs simplifies a number of different operations related to working with clusters.  You can easily obtain individual or sets of elements, manipulate elements, split or index cluster subsets, convert clusters to other data structures, and sort clusters programmatically.  The Cluster Toolkit also works with clusters in the form of variant data, further increasing the flexibility of this powerful toolkit.

 

 

Cluster Tools

 

Cluster Tools by IMS builds on the native LabVIEW cluster functions by allowing programmatic indexing, register reference, recursive operations, and more.  Allowing direct access to cluster element references means you can perform manipulation of those elements without bundling values with references.  Overall, Cluster Tools is extremely useful when working with code that is heavily dependent on clusters as a data structure.

 

 

GOOP Development Suite

 

Object oriented programming in LabVIEW has grown by leaps and bounds in recent years.  Object data is stored in wires that are accessed via cluster tools.  There also exists a series of tools designed to extend LabVIEW's OOP feature set.  The GOOP Development Suite simplifies management of classes, allows automatic code generation, and incorporates Unified Modeling Language support into LabVIEW. 

 

 

G# Framework

 

This toolkit adds reference-based object oriented support, includes a debugger for tracing object instantiation, and adds automated garbage collection to remove the need to manually destroy objects.  The toolkit's object oriented support makes LabVIEW as powerful as any object oriented language.

 

 

UI Customization

 

ProgressBar_screenshot_l.jpg

 

WF ProgressBar

 

The WireFlow WF ProgressBar module is a simple, easy way to add progress bars into your application.  It allows full customization of the appearance, giving you control over the user interface and allowing the end user to potentially cancel longer operations.  For more progress bar functionality, check out the LabVIEW Taskbar Progress Bar API, which allows you to use the progress bar embedded in Windows 7 by leveraging very simple VIs.

 

 

VI Box XControls

 

One of my personal favorites, this XControl allows you to create a tab control on your LabVIEW front panel that performs similarly to a browser.  You can create additional tabs, manipulate their locations, pop them into separate windows, and more - all during run-time.  The ability to provide users an intuitive tabbed experience similar to what they are used to from internet browsers increases the usability of a wide variety of applications.

 

 

UI Control Suite

 

The UI Control Suite adds controls and indicators that differ aesthetically from the built-in LabVIEW UI objects.  Available in Metallic Theme, NI Theme, and System Controls, the UI Control Suites offer the ability to make engaging, coherently styled UIs for a variety of desired looks.

 

 

UI Tools

 

The UI Tools palette, created by LAVA, allows the LabVIEW front panel to fade in or out, smoothly move objects programmatically, override generic dialog boxes, and more.  This powerful toolset also incorporates functionality to improve the usability of front panels of LabVIEW OOP VIs.

 

 

 

 

There are many more tools available on the LabVIEW Tools Network that facilitate productivity, expand built-in functionality, and incorporate specific applications to save you and your developers time and effort during the Design and Implementation phase of your project.  In Part 3 of this series, we will take a look at a number of tools that simplify the Deployment process in a variety of different ways.

 

Patrick Simmons

LabVIEW Tools Network Engineer

0

Case studies document how our customers use our products and services to develop innovative solutions, optimize existing applications, or perform cutting-edge research. They are excellent tools for demonstrating the capabilities of your products and building credibility in industry. This post will cover how to write an effective case study. We will cover:

 

  1. Type of content you want to include
  2. How to structure your case study
  3. Important details

 

Type of Content you Want to Include

Case studies are inherently about projects that your customers have created. So typically you will work directly with your customers to obtain content and review the messaging that is used. When obtaining content for your case study, be sure to cover the following points:

 

  • Demonstrate how your application met the customer’s challenges better than any other company and include examples of other options the customer may have chosen.
  • Communicate the challenge clearly and include the “pain points” the customer was trying to alleviate.
  • Highlight all of the software, hardware, and services used to develop the solution.
  • Quantify the results. Include phrases such as, “We helped the customer increase efficiency by X percent, decrease costs by X dollars, and decrease test time by X minutes/hours.” The more specific you can be, the better.

 

How to Structure Your Case Study

Now that you have your content, how do you present it to the reader? You want to make it as easy as possible for your reader to get a snapshot of the solution. You should also have more detailed supporting content so they can learn more if they are interested.

 

  1. Provide a conside but descriptive Title. 60 characters maximum.

  2. Start by crediting the Author(s), including the company name that created the solution. This helps you gain credibility in the eyes of the reader. A recognized name that uses your products will have the most weight in the eyes of the reader.

  3. State your Products used in this case study. Simply state them - description will come later.

  4. Next, mention the Industry and Application Area that the solution pertains to. This allows readers to self-select by their interest area.

  5. Now it's time to describe the Challenge your customer needed to overcome. This is the reason they needed your product. Make this 25-50 words.

  6. Follow the Challege by the Solution. Describe how your customer solved the problem using your products. This should also be 25-50 words.

This completes your snapshot of the solution. You have given the reader enough information to decide if this fits their interests and if they want to learn more. The next step is to provide more details on the customer, the solution, and reasoning why your product was chosen for the solution. This is the main Body of the case study. It should be 800-1200 words.

 

  1. First paragraphs should be a Brief Description of the Customer. Specifically who they are, what they do, and who they serve. Elaborate on the engineering problem they were trying to solve and why it was important.

  2. The next few paragraphs should describe the Project itself that was used to solve the challenge. This is a high-level description of how the system works. Be sure to describe:
    • Other options besides your own, that could have solved the problem.
    • Why the customer chose your product over the other options.
    • The specific features of your product that were most utilitized and why they were important for the success of the solution.
    • Mention any additional services you provided that were helpful for the project.

  3. Now explain the Benefits of the Solution. Provide detail, and give quantifiable measures of the benefits. Specifically:
    • Practical benefits (Increased efficiency, ability to reuse or scale, etc)
    • Business benefits (Cost savings, time savings, meeting more customer needs)
    • Any benefits your or your customer did not expect

  4. The Final Paragraph should discuss how this solution and specifically your products met the customer's objective for their project.

  5. Follow the body with Contact Information to learn more about your products and the solution as well as any Additional Materials you may want to include like code or supplemental technical documents.

 

Once complete, your case study should have the following structure:

 

Case Study Title

 

Author(s):

 

Products Used:

 

Industry:

 

Application Area:

 

The Challenge (25-50 words)

 

The Solution (25-50 words)

 

Body (800-1200 words)

    • Brief Description of the Customer
    • Project Itself
    • Benefits of the Solution
    • Final Paragraph

 

Contact Information

 

Additional Information

 

Important Details

There are a few details that help to make a case study particularly engaging and effective. Always do the following:

 

  1. Include links or methods for readers to learn more about your product and get in contact with you. They should always have a next step.

  2. Choose a solution that is either attention grabbing or solves a very common problem in the industry you serve. This will help get people interested and give the case study more mileage.

  3. When possible, include pictures. Graphics and photographs immediately add a new element and sense of reality to your case study. People will be able to understand the case study more effectively. It also adds additional credibility.

  4. When possible, include video of the solution or concepts applied in the solution. Videos are one of the most effective methods to gain attention and get important messages across to the viewer.

 

Final Thoughts

Case studies can be a very effective addition to your overall marketing strategy. They give you the opportunity to demonstrate your technical aptitude while quickly showing others how people are effectively using your products. One of the best ways to gain exposure and increase sales is by demonstrating that respected organizations in your industry are happily using your product.

 

For example case studies, take a look at ni.com/casestudies. As always, free to post questions or your own examples below.

 

Have a great weekend!

 

Will Schoettler

LabVIEW Tools Network Product Manager

0

NIWeek 2013 has finally, but sadly come to an end.  Every year, it's a great experience for Alliance Partners and the LabVIEW Tools Network, but 2013 has been by far the best.  In case you weren't able to join us (or if you did join us and just want to relive the memories) here are a few of the highlights:

 

LabVIEW Tools Network Awards

 

This year the LabVIEW Tools Network Awards were bigger and more successful than all of the others.  Combined with the Alliance Partner Network awards, we completely filled the keynote room to showcase this year's top new LabVIEW Tools Network products.  Congratulations to the finalists and winners in all 5 categories:

 

Test Product of the Year

Winner:  Tool Qualification Kit for NI TestStand by CertTech, L.L.C.

Toolkit to Qualify NI TestStand as a Verification Tool

http://sine.ni.com/images/products/us/interface_handout_l.jpg

Runner Up: Digital Video Signal Generation Toolkits by MaxEye Technologies

Create Test Signals for DVB, DTMB, CMMB, DAB, ISDB, and ATSC Digital Video Standards

 

Embedded Product of the Year

Winner: Raima Database API for LabVIEW by Raima, Inc.

Database solution for NI CompactRIO, Single-Board RIO and Windows

http://sine.ni.com/images/products/us/raima_database_api_l.jpg

 

Runner Up: modeFRONTIER for LabVIEW by ESTECO

Integration platform for multi-objective and multi-disciplinary Hardware-in-the-loop optimization.

DAQ Product of the Year

Winner:  Chameleon for NI CompactDAQ by PVI Systems

Configurable DAQ Software for Structural Test and Monitoring

 

http://sine.ni.com/images/products/us/06190807_1217_l.jpg

Runner Up: iDaq by Tools for Smart Minds (T4SM)

Data Logger, Fully Programmable With LabVIEW

Community Product of the Year

Winner: TSVN Toolkit by Viewpoint Systems Inc.

Subversion Version Control for NI LabVIEW

 

http://sine.ni.com/images/products/us/tsvntoolbar_l.jpg

Runner Up: VI Box XControls by SAPHIR

Advanced front panel controls for a more dynamic user experience

LabVIEW Innovation Product of the Year

Winner: Wirebird Labs: Deploy by Wirebird Labs LLC

Setup Authoring and Application Distribution for NI LabVIEW

http://sine.ni.com/images/products/us/wirebirdlabs_l.jpg

Runner Up: BLT for LabVIEW by Studio Bods

Building, Licensing, and Tracking for LabVIEW Executables

Runner Up: VI Helpeks by Konstantin Shifershteyn

Provide Your VIs With Help That Looks Like LabVIEW Help

 

Double the Products, Double the Downloads, Double the Fun!

Since this time last year, the LabVIEW Tools Network has almost doubled the number of products available (Currently 177 and growing) and doubled the number of downloads (Over 2 Million downloads).  This only happened thanks to the time and effort from our great developers and their awesome products. 

 

LabVIEW Tools Network Products in the Day 1 Keynote

This year the LabVIEW Tools Network took over the Day 1 Keynote stage.  Not only were the 5 LabVIEW Tools Network awards winners congratulated on the big screen, but Jack Dunaway from Wirebird Labs demoed Deploy, Raima Database API for LabVIEW and RTI DDS Toolkit for LabVIEW were showcased in a case study from LocalGrid, and Viewpoint Systems TSVN Toolkit was mentioned as a key Software Engineering Tool for LabVIEW.  Kudos to everyone involved!

 

Alliance Day Session: Selling Tools on the LabVIEW Tools Network

LabVIEW Tools Network Program Manager, Matthew Friedman, and LabVIEW Tools Network Engineer, Robert Des Rosier gave a very well received session on the process of selling a product on the LabVIEW Tools Network.  Slides from this session are attached below.

 

LabVIEW 2013 Release

LabVIEW 2013 was released and is better and more stable than ever.  The most notable new feature is that the LabVIEW Tools Network and VI Package Manager is actually installed by default when you install LabVIEW 2013.  This means that customers have an even easier opportunity to download and try out third party tools from directly within the LabVIEW environment without any additional steps needed.  A more detailed review of notable features of LabVIEW 2013 to come soon..

 

Much more

This is just a small bit of the excitement that we had for NIWeek this year.  For more information check out the NI News Blog.  Hopefully we'll see everyone out here next year!

0

After spending all the time and effort to create a top-notch product in LabVIEW, it's extremely important to accompany that product with high-quality marketing material. Although a high quality product can speak for itself once it is in a user's hands, the marketing material will put it there and show off the best parts to the user. One key part of your marketing material is your Model Page on the LabVIEW Tools Network.

 

Step 1: Identify Your Target Audience

You designed your product to satisfy a need in industry. That need was created by a specific user base that you are familiar with. The features you implemented keep that user base in mind so that it is intuitive and effective for them to use. By keeping this user base, or target audience, in mind when you create your model page you can simultaneously demonstrate your industry expertise and relate to your potential customers. This is done by using technical language understood by your target audience and by highlighting the features that fulfill their needs most effectively. If you have correctly interpreted their needs and speak to them in their industry language you will build credibility and interest in your product.

 

Avoid This Pitfall:

Many developers encounter this issue: "My product has many great features that fulfill the needs of many different target audiences. I should market to all of these audiences."  Unfortunately, in reality, this approach typically results in marketing material that is confusing due to mixed industry terminology and does not effectively engage the customer's interest. It makes it difficult to speak to the product's strengths and can result in a loss of company focus as there is no clear definition of which type of customer should be prioritized.

 

For example, assume your product, T1D, is a table with a drawer.  It has good features like strength, stability, a high-quality smooth hard surface, and the drawer can be used to keep commonly-used items on hand. The T1D can also be used as a chair. Its features of strength and stability to support objects makes it an effective solution. However, key features you developed like the smooth hard surface and convenient drawer are not good selling points for a comfortable chair. In addition, a chair has a backrest which immediately makes it better suited for longterm sitting. Therefore, although the T1D has the functionality that could allow it to be marketed and sold to the Chair Buyer audience, you would find much more success by targeting the Table Buyer audience.

 

By selecting one primary target audience you can focus your energy and resources to reach your customers most effectively. Once you have established success with one audience you can consider reaching out to additional audiences. With your target audience in mind, you can begin crafting the model page content.

 

Step 2: Product Subtitle

Your product subtitle is the 1-sentence description all customers will see. It shows up on the product tile when browsing the LabVIEW Tools Network, and appears directly beneath the product name on the Model Page. The product subtitle is used to grab attention and describe your product at the same time. A good subtitle brings in potential customers. A poor one can cause them to pass your product by. Click the images below for examples.

 

Chameleon Tile.jpgChameleon Model page.jpg

 

The example above include three main components:

  1. Key Differentiating Product Feature ("Configurable")
  2. Primary Product Function ("DAQ Software")
  3. Target Audience ("Structural Test and Monitoring")

 

By including these three components in the Product Subtitle, you can make your initial pitch to your potential customers. You tell the potential customer if they are the right type of user, what the product does, and what makes it stand out.

 

Step 3: Product Feature Bullets

When a potential customer clicks through to your model page, the first thing they will see is the Feature Bullets at the top of the page. Click the image below for an example.

CertTech Bullets.jpg

 

In general, feature bullets should provide the following:

  1. Brief description of what the product will do for the user
  2. Key differentiating features that make it stand out over other similar products
  3. Benefits of those features

 

When selecting your bullets, always keep your target audience in mind. Choose features and benefits that best apply to them.

 

Step 4: Product Overview

The product overview section is where you can provide an in-depth description of your product. Click the image below for an exmaple.

 

SCCT Overview Small.jpg

 

A good product overview will describe the functionality of the product using terminology and features that are pertinent to the target audience. It will also include key decision information such as supported hardware and system requirements, if applicable.  Additional features and a description of package contents can also provide helpful insight into what your product offers.

 

Step 5: Related Links

Often overlooked, the Related Links section is the perfect location to send your customer to additional information like case studies, video demos, documentation, and more. All of this supporting marketing material can be used to gain credibility with customers and help them make the decision to evaluate your product. Click the image below for an example of Related Links.

 

NeuralID Related Links.jpg

 

At a minimum, you should provide a pathway for your customers to learn more about the product. It is highly recommended to include demos and case studies. If you do, create them such that they cover topics applicable to your target audience.

 

Step 6: Ratings & Reviews

Ratings & Reviews are a highly beneficial mechanism for both gaining credibility in the eyes of potential customers and for gathering feedback from your existing users. Click the image below for an example of Ratings & Reviews.

 

ltk reviews.jpgBy encouraging your user-base to return to the model page and contribute ratings and reviews you can find some invaluable feedback. Potential customers are also typically more likely to evaluate or purchase a product that they can verify others have had success with.

 

Step 7: Spread the Word

A model page is a great first step to getting your product into the market. However, it is just a small part of the entire marketing effort. The most success comes from a combination of marketing efforts including case studies, press wires, participation in interest groups, and any other sort of communication you can have with your target audience. Always include a call to action to evaluate or purchase the product. Use your model page as the link point. By reaching out to your target audience and establishing yourself as a credible source of expertise in their industry you can develop a reputation for quality products that could translate in good sales.

 

Best of luck with your marketing efforts and feel free to comment below.

 

Will Schoettler

LabVIEW Tools Network Product Manager

5

Another NI Week has come and gone, and it was another great success.  We set a high bar at NIWeek 2011 but the LabVIEW Tools Network team was quite busy this year and made it even better!  Here are the highlighs in case you missed out:

 

LabVIEW Tools Network Ships with LabVIEW 2012

 

Last year we were excited to announce that you could easily access the LabVIEW Tools Network directly from the LabVIEW Getting Started window.  This year, we have done one better and actually ship VI Package Manager 2012 with LabVIEW 2012.  This means without any additional downloads, you can access all your favorite LabVIEW Tools Network add-ons from right within the LabVIEW development environment!

 

Introducing the Jitter Benchmarking Framework for LabVIEW Real-Time

This year we have introduced our newest tool to help LabVIEW Tools Network developers, the Jitter Benchmarking Framework for LabVIEW Real-Time.  The Jitter Benchmarking Framework (JBF) for LabVIEW Real-Time provides users with an initial reference containing basic definitions of key concepts related to execution jitter on RT systems, explanations of common execution jitter sources, practical examples of execution jitter sources, and a testing framework complete with code templates for common execution jitter measurements on LabVIEW Real-Time systems.

 

If you are interested in learning more about this new tool, check out the JBF community for more information.

 

LabVIEW Tools Network Awards 2012

 

This year we had so many great new products released on the LabVIEW Tools Network.  However, 8 products stood out as the best of the best this year.  A run-down of this year's winners is available on our blog.

 

LabVIEW Champions vs LabVIEW Marketing Trivia Challenge

 

This year I was asked to join a few others in the LabVIEW Marketing team to take on 4 LabVIEW Champions in a LabVIEW trivia challenge.  Sadly, the LabVIEW Champions beat us again, but we were much closer this year only losing by 90 points!  Some more details and a picture can be found on the NIWeek 2012 blog.

 

5 LabVIEW Tools Network-Oriented Sessions

 

This year the LabVIEW Tools Network team gave 5 technical and marketing sessions   Many asked us for our session content after it was over, so here it is for you to use and share.

 

Build a LabVIEW Add-on with VI Package Manager (Hands-on) - by Stephen Roso

The LabVIEW Tools Network Awards Winners (Tech Theater) - by Will Schoettler

Explore Tools to Customize LabVIEW - by David Ladolcetta

Introduction to LabVIEW Scripting - by David Ladolcetta

Do Real-Time Right With the NI Jitter Benchmarking Framework - by Robert Des Rosier

 

I hope everyone had a great NI Week, and we hope to see you again next year!

 

Over 100 Certified Products and 1 Million Downloads

This year we also announced that the LabVIEW Tools Network has reached over 100 certified products and 1 million downloads!  Thanks to @vishots for the picture of our 2 story tall announcement at the Day 3 Keynote!

 

Az3GIAcCIAAPGqZ.jpg

0

niweek2012.png

NIWeek is just around the corner! It'll be another week of great sessions and opportunities. Here are some sessions you don't want to miss:

 

TS8166 - Do Real-Time Right with the NI Jitter Benchmarking Framework

Robert Des Rosier, Partner Program Engineer, National Instruments

Troy Troshynski, Vice-President, Avionics Interface Technologies

One of the most important -- and often challenging -- aspects of any real-time system is the characterization of jitter.  In this session, learn how you can improve and document the performance of your real time system with the NI Jitter Benchmarking Framework for LabVIEW Real-Time. Using Avionics Interface Technologies as a case study, we will explore how this benchmarking helped them get an edge on their competition.

 

TS8526 - Introduction to LabVIEW Scripting

David Ladolcetta, Partner Program Engineer, National Instruments

Gain an introduction to programmatically creating, modifying, and inspecting G code. Familiarity with VI Server is recommended but not required.

 

TS8527: Hands-On: Build a VI Package with VI Package Manager

Stephen Roso, Partner Program Engineer, National Instruments

 

TS8528: Explore Tools to Customize LabVIEW

David Ladolcetta, Partner Program Engineer, National Instruments

 

LabVIEW Tools Network Awards


0

VIPM 2012 Released

Posted by Will_S. May 15, 2012

VIPM 2012 Released

VIPM Logo

 

 

We are proud to announce the release of VI Package Manager 2012! Click here to get it. VIPM 2012 brings great new features for LabVIEW teams and add-on creators. Through direct collaboration, one-on-one interviews and public forums such as the VIPM Idea Exchange NI and JKI have learned a lot about how people use VIPM and more importantly how people want to use VIPM. Some major changes in VIPM 2012:

 

New Low Price, Easy Trial Activation

There are now only two versions of VI Package Manager: VIPM Free and VIPM Pro. VIPM 2012 Pro is now $499, and if you’ve ever bought a previous version of VIPM Pro or Enterprise upgrades are just $199. It's also easy to evaluate VIPM Pro for 30 days: just activate VIPM with the special trial code VIPM-PRO-EVAL-NI.

Unleashing VI Package Repositories

With VIPM 2012, VIPM Pro users can create as many VI Package Repositories as they want. This means that if you’re building LabVIEW add-ons or reusable libraries for your coworkers, customers, or the community, you can create one or more central VI Package Repositories to easily distribute your add-ons. Other features:

  • VIPM 2012 Pro can connect to any number of repositories. Repository client limits are a thing of the past.
  • VI Package Repositories can be hosted in public Dropbox folders. You no longer have to run your own web server or ftp site to host a repository (although you still can if you want).
  • VIPM 2012 Pro users can now manage multiple shared repositories. Previously, VIPM could only a manage a single repository.
  • VIPM 2012 Pro can create private repositories for package sharing within your organization or with your customers.
  • Every VI Package Repository has a unique RSS feed so repository users can subscribe to receive package release notifications in their favorite RSS reader.


Automate Tasks With VIPM’s New VI-based API

VIPM VI-based API

Do you want to automate installation of packages or perform maintenance tasks on your reuse library easily? Now you can, with VIPM 2012 Pro’s new public API. Learn more here.

Here are some examples of automations you can create:

  • Automated package builds: Create a one-click build for your LabVIEW add-on. Write LabVIEW code to automatically apply a VIPC file, build your package, install the built package & test it, then publish the package to your repository, all automatically.
  • Unattended system updates: Script your development systems to automatically find and install add-on updates.
  • Group package publishing: Create a “package release dropbox” for members of your team to put built packages into; automatically publish packages from that folder to your repository.
  • New development system setup: Create a “system setup” script to automatically install “core” packages on multiple LabVIEW versions with a single command.
  • System inventory and maintenance: Validate system installations, perform cleanup and maintenance on deployed systems.

VI Package Configuration (VIPC) Improvements

Our users tell us that once they start using VI Package Configuration files they can’t stop. They’ve also given us some great ideas to improve how VIPC files work. We’ve listened, and VIPM 2012 Pro adds the following enhancements:

  • Apply VIPC to any LabVIEW Version: VIPM 2012 allows you to apply a VIPC in any version of LabVIEW.
  • LabVIEW Project (.lvproj) Dependency Scanning Support: VIPM 2012 Pro supports LabVIEW project files as a source for finding project VI package dependencies. Use this feature to create a VIPC file containing exactly the right libraries and add-ons for each project you work on.

New in VIPM Free

  • New Install\Uninstall Custom Action Parameters
  • "Generate VI" Buttons from templates for Custom Actions
  • Improved Network Connectivity for users behind corporate Proxies
  • Easier Removal of Unpublished Packages

Other Stuff

 

 

Much of this content has been taken from the JKI blog post here.

0

We are changing the re-certification process for the Compatible with LabVIEW program this year and I have a few deadlines for you to meet in order to be eligible for awards at NIWeek 2012!

 

As many of you know, the Compatible with LabVIEW program we rebuilt in 2009 requires a yearly review, or re-certification, by our engineers to ensure products are maintaining compatibility with the latest LabVIEW release.  We also use this yearly review to hit upon any tests or requirements we've added to the program during the course of the year -- in doing so, we hope to continue to add value by ensuring your products are up to date with new features and entry points in the LabVIEW platform.

 

Changes for Re-Certification

We are no longer expecting you to submit an application to trigger the re-certification process.  All products on the LabVIEW Tools Network will be re-certified by our engineers for each LabVIEW release and a report delivered to you for your Compatible with LabVIEW level.  If product updates are required, we expect you to submit an installer with updates identified in the re-certification report to maintain your status on the LabVIEW Tools Network.

 

*Note: If you intend to achieve a higher level in the Compatible with LabVIEW program, please fill out the Compatible with LabVIEW Application and include the customer references and CLD/CLA information required for the Silver and Gold levels.  Submitting an application will notify our team that you're requesting a product to be reviewed for a higher Compatible with LabVIEW level.  Please submit 2 customer references we can survey for the Silver level and a total of 5 customer references for the Gold level (if you're already certified for Silver, we need 3 additional customer references).

 

**Also Note: If you ever have an updated installer for the LabVIEW Tools Network, please send an email to labviewpartnerprogram@ni.com with details for obtaining your new VI Package or installer and we will ensure your Tools Network product page is updated as soon as possible!

 

Important Dates

  • Compatible with LabVIEW recognition at NIWeek
    Partners who achieve either the Silver or Gold level during the previous calendar year are recognized with a plaque during the LabVIEW Tools Network Awards at NIWeek.  If you have not achieved a higher level this year and are interested in moving to the Silver or Gold level, the following deadline applies for notifying our team to have your product reviewed in time for NIWeek 2012:

    • May 15, 2012 -- Notify the LabVIEW Partner Program Team by this date if you intend to re-certify for a higher Compatible with LabVIEW level so we can prioritize your re-certification in time for NIWeek.  Use this application to submit a notification to our team and be sure to include the customer references required for your desired Compatible with LabVIEW Level:
      http://zone.ni.com/devzone/cda/tut/p/id/12901  (2 references for Silver, 5 references for Gold.  If you are moving from Silver to Gold, we need 3 additional references)

    • May 15, 2012 -- If you have not already registered for the LabVIEW 2012 Beta Program, you will also need to register in order to test your products in the new version and apply updates required to be compatible with the new version.  The beta application process is simple; go to http://www.ni.com/beta to apply and enter 'robert.des.rosier@ni.com' as the email of the person who invited you.

    • June 30, 2012 -- Once you submit for re-certifying your product for Silver or Gold, the Compatible with LabVIEW process must then be completed by June 30 so the awards to be ordered in time for NIWeek.

  • LabVIEW Tools Network Awards
    The 2012 Tools Network Awards are now open for submission!

 

Contact Us

If you have questions or feedback, please contact the LabVIEW Partner Program team by sending us an email at labviewpartnerprogram@ni.com

0

LabVIEW 2012 Beta is OPEN!

Posted by RDR Feb 9, 2012

The LabVIEW 2012 platform beta program is open for enrollment and there are some exciting features for partners to check out!  I encourage you to follow-up on the invitation below:

 

You are invited to register for participation in the LabVIEW 2012 Platform beta program.

 

You can register by visiting http://www.ni.com/beta and selecting "LabVIEW 2012 Platform" from the list of beta programs.  Please be sure and enter your complete address information in Western characters.  All customers outside the United States will have to pass Export Compliance as defined here.

 

Please complete the profile questions to help us understand your experience and use cases with LabVIEW.  Make sure you agree to the T&C of the beta program so that you can complete your registration.

 

After you register, please be patient for the beta coordinators to process your application.  You will be notified once you have been approved. Registration does not necessarily guarantee you a position in the beta program.  Determination of acceptance into the program is up to the sole discretion of National Instruments.

 

We will have a private section of the Discussion Forums on NI Developer's Exchange set up for beta users to discuss the beta version of the LabVIEW 2012 Platform.

 

We eagerly await your registration.  Thank you for your invaluable help in assisting us design and test LabVIEW.

 

(http://forums.ni.com/t5/LabVIEW/Announcing-the-LabVIEW-2012-Platform-Beta-Progra m/td-p/1859557)

 

-bob

0

For this Part II blog post on Market Validation, I will lay out a spectrum of best practices and tools that can be used for market validation.  To get started, let's look at relative costs associated with each of these tools, because you will ultimately need to make trade-offs based on your time/budget.  The red boxes represent secondary market research, which while important, is generic market data that most people (including your competitors) will also have access to.  The blue boxes represent primary market research, which is proprietary domain knowledge that you will create as you better understand the target customer. 

 

https://decibel.ni.com/content/servlet/JiveServlet/download/38-39360/Costs%20of%20Market%20Validation.png

 

Before going further, let's recall once again why market validation is so important.  The relative costs of doing market validation, are dwarfed in comparison to the cost of NOT doing market validation and building a product that is destined to fail.  It's much cheaper to listen to customers before you build the product, especially if they are telling you that your product idea is not that great. 

 

https://decibel.ni.com/content/servlet/JiveServlet/download/38-39359/Cost%20of%20a%20Failed%20Product%20Launch.png

 

Now let's look at each of these tools in more detail.

 

Secondary Market Research (Generic information)

 

Secondary market research is a great place to start, and can quickly help you determine the market size and competitive landscape.  I use the following two types regularly:

 

Market Research Reports.  At NI, we purchases various market research reports in the industries that we operate, they usually cost a few thousand dollars a piece.  You can typically secure the abstract page free of charge, which contains high-level information.  Example companies that offer market research in the high-tech space include Forrester Research, Gartner, EETimes, Frost & Sullivan, VDC, Prime Data, Aberdeen, and many more. 

 

Publically Available Financials. All publically traded companies (and some privately held companies) have financial information available that you can use to do a "market build-up" and come up with your own projected market size.  What's great about this, is it can be done free of charge.  One of my favorite sites for financial information is ycharts.com, you can dive in by industry and sector. 

 

Primary Market Research (Proprietary Research for your Product)

 

The purpose of primary market research tools when doing market validation, is to go beyond the general market data and really understand the customer's needs.  The outcome of this step will help shape your product offering.  Here's a few of the tools I use for market validation, it's not an exhaustive list but I find these to offer a good variety.  Note that each of these have their own tradeoffs. 

 

Industry Conferences.  You need to get plugged into the market and the best way to do that is attend a conference that specialized in that area.   The primary goal is to make contacts and learn best practices to go deeper with your market validation.   A follow-up activity would be 1-1 interviews with key contacts you meet at the conferences. 

 

LinkedIn Groups.   This is an inexpensive time investment to get started, and it's free of charge.  Just like attending an industry conference, LinkedIn can help you find experts in your field, and you can use the Groups on LinkedIn to participate in conversations.  The downside is, it still takes work to get something out of this, and I find the face-to-face interactions to be more effective than online mediums. 

 

Surveys.  If you have a list of contacts that you can reach out to, online surveys can help you collect information efficiently and at a low cost.  I personally use jotform.com as my tool of choice, but there are plenty of options out there.  Be careful with surveys to not ask leading questions, and also keep in mind a survey is not nearly as powerful as a 1-1 conversation. 

 

Phone Interviews.  Phone interviews are more time consuming than surveys, but also much more powerful.   If someone is willing to spend 30-60 minutes on the phone, that is a pretty good indicator that they are feeling some pain with their current product -- and presumably your product could address that.  The rule of thumb from experts, is to talk to at least 100 people when doing your market validation.

 

Focus Groups.  Focus Groups are more challenging to pull off logistically, because you'll need a team to execute this.  This is something you can outsource, but they can be expensive.  The results can be very effective though, because you are bringing together a sample group of your target audience and getting in-depth discussions led by a moderator.

 

Customer Visits.  This is my favorite activity when doing market validation, because you gain tremendous insight by going on-site to a customer and learning about his or her challenges.  A popular book at NI that many of the product managers read, is called "Customer Visits: Building a Better Product Focus, by Edward McQuarrie".  It really offers a "recipe" for how to apply customer visits to gain market insight.  The downside is, if you are a new player in the market, you don't have any existing customers to go and visit. 

 

Expert Opinion.   My last recommendation is to speak with the experts.  This may also be the most challenging and cost prohibitive activity.  For example, a business tycoon such as T. Boone Pickens may require upwards of $25K for a discussion on energy.   However, in many cases you can get response from an expert without paying a speaking fee -- so don't be discouraged.  I've reached out to experts via email (or on their blog) and had some success with getting responses.   Also, if you aware of a speaking engagement that the expert is delivering, many times experts will stick around and answer questions after the session.

 

Conclusions

 

Consider using a range of tools for both secondary and primary research when doing your market validation. 

 

Secondary market research key points:

  • Includes:  Market Research Reports, Publically Available Financials
  • Can be easy to access
  • Contains general market information
  • Generic in nature (available to anyone)
  • Can be paid (Market Research Reports) or free (Publically Available Financials)

 

Primary market research key points: 

  • Includes: Customer Visits, Phone Interviews, Expert Opinions, Focus Groups, LinkedIn Group discussions, Survey, Industry Conferences
  • Represents your proprietary research
  • Can shape your product design
  • Requires significant time investment, but is well worth it
  • Rule of thumb: Experts recommend you talk to at least 100 customers when developing a new product

 

To wrap up, remember that perhaps the best return on your investment will be the times when market validation helps you realize that the product idea isn't that great.  It's 10 times cheaper to find out a product will fail, before you build it, then going through with the product launch and then have it flop in the market.

1

At NI Alliance Day earlier this year, the partner team at NI hosted a slew of both technical and business sessions for our partners.  One session for LabVIEW developers was called “The Addressable Market for LabVIEW Add-ons”, where we shared some adoption data for the LabVIEW Tools Network.  Due to the innovation from our partners who are using LabVIEW in some pretty interesting and exciting ways, this online marketplace continues to see more than 2X growth in both web traffic and downloads.  In addition to all the new partner products, there’s also been some great work by the LabVIEW R&D team to enable hooks into LabVIEW itself through APIs, which contributes to this growth in LabVIEW Add-ons by allowing more places for developers to extend the environment.

 

The question I get asked all the time, is "Should I build this product?"  And going back to Alliance Day, there was a critical topic that we didn’t get into during the sessions  – Market Validation. This topic is critical for every product company to understand, and it’s the motivation for this blogpost. If the market validation stage of product development is overlooked, the success of your product launch is left to chance.  I’m really interested to hear your personal experiences with market validation, so drop me a comment below or shoot me an email at jeff.meisel(at)ni.com with what has worked for you. During this post I’ll share some simple things that I've learned along the way when performing market validation. 

 

First, consider the analogy where you are captain of a ship planning a trip in unknown waters with treacherous conditions.  Wouldn’t it be nice to have a strong plan in place, and understand as much as possible about what lies ahead?   If you talk to the local fishermen and they aren’t going out to sea, that tells you an important piece of information.  Similarly, if you check the weather information, and realize a storm is coming – you may decide that leaving shore is not the right decision.  Now, it doesn’t mean that you have to cancel the trip entirely.  One possibility is to change the timing of departure or reroute your travel path.  Both options are better than going into the oncoming storm.  And if you lose some money by scrapping your original plan and creating a new one, well at least you didn’t lose your entire ship or put yourself in harm’s way.  The same goes for new product development.  Through market validation, a systemic approach can be used to evaluate market opportunities before investments are made.  If the product is a bad idea, it’s good to know that early. 

 

Basic Guidelines for Market Validation

Rob Adams, author of “If you Build it Will They Come?” provides some good insight into some basic guidelines.  His book is a quick read and Adams offers a blueprint for how to perform market validation.  For example, one rule of thumb is that you'll need to allocate 10 percent of development budget to Market Validation.   Why?  If the product isn't going to work,  it’s better know with a 10 percent investment versus 100 percent investment. 

 

Three critical questions to consider when applying market validation in evaluating a new product launch are:

  1. Is there a clearly defined need?
  2. Can you deliver the right product to meet that need?
  3. Are customers willing to pay?

 

The following diagram shows a basic view of market validation, which we can expand further in future discussions:


 

Market Validation

Talk to People, Rinse, Repeat

 

Wrapping it all together

 

If you’re not willing to invest the time in doing market validation, that’s a red flag and illustrates that it may not be a good idea to build the product in the first place.  In addition, if you don’t know if there is a market need for your product, what the right features are, or if customers will pay -- don’t build it.  Or at a minimum go back to the drawing board before proceeding. For example, the pricing model is something that you can tweak in order to see if customers would be willing to pay under different terms.   But the question “Is there a need?” is something you can’t get around – so always start there first. 

 

In a future Part II blog post, we’ll look at some best practices on how to perform Market Validation for your product.    As mentioned, feel free to email me some of your strategies for market validation – I’d love to learn about them.

 

More Resources:


LabVIEW Tools Network

NI Alliance Partner Network

 

References:

Book Reference - Rob Adams "If You Build it Will They Come?"

0

Can your add-on do this?

Posted by Sumedha Aug 15, 2011

There is a way to build add-ons that plug directly into the LabVIEW project window. Using LabVIEW Project Providers, your add-on can integrate into the project and add new menus, toolbars, right click menus and do much more:

 

1. Add new menu options

Add New Menu Items.png

 

2. Add new toolbar buttons to Project Explorer window

Add New Toolbar Items.png

 

3. Add right click pop-up menu options

Add pop-up menu options.png

 

4. Modify the icons in the project tree

Modify icons.png

5. Customize the double-click behavior of any item in the LabVIEW project

 

html_screencast.png


6. Add new items to the project tree

Add new items to project.png

html_screencast.png

 

 


To get a better idea of what YOUR add-on can do with project providers look at some existing project providers from National Instruments:


1. LabVIEW Source Control

2. LabVIEW VI Analyzer Toolkit

3. Build Specifications: Application Builder, Source Distribution, and Web Services

 

For more information on building provider based add-ons, please contact the LabVIEW Partner Program Team

0

NIWeek 2011 has come and gone and it was a great success.  The LabVIEW Partner Program and the LabVIEW Tools Network specifically had some great announcements, releases and events that made it one of our best NIWeeks ever!  Hopefully we'll be able to top it for NIWeek 2012.

 

LabVIEW Tools Network Directly in LabVIEW 2011!

In LabVIEW 2011, there is now a "Find LabVIEW Add-Ons" link directly on the Getting Started window.  Clicking this link will open the Tools Network View of VI Package manager which provides LabVIEW users with a direct entry point to download and install add-ons, toolkits and LabVIEW applications directly from within the product.  The new Tools Network View was a great hit at NIWeek and was mentioned in 2 keynote presentations and multiple technical sessions throughout the week.  Let's all work together to drive traffic of the LabVIEW Tools Network by trying each other's products from the new VIPM LabVIEW Tools Network View!

 

LVTN View.png

 

Third Party Licensing & Activation Toolkit 2011 and the Standard Licensing Mode

This week we also launched the newest version of the LabVIEW Third Party Licensing & Activation Toolkit 2011.  This was a major release with the introduction of the Standard Licensing Mode for a quick, easy and FREE way to license your LabVIEW Toolkit directly in LabVIEW.  More details can be found at ni.com/licensingtoolkit

 

LabVIEW Add-On of the Year Awards 2011

The Add-on of the Year Awards was a huge success this year.  With over 75 partners and NI employees in attendance including the Father of LabVIEW himself, we were able to celebrate our 6 award winners, 7 Gold Products, 14 Silver Products and 17 Standard third party products.  More details can be found here

 

8 Partner-oriented Technical Sessions

The LabVIEW Partner Team gave 8 technical sessions specifically tailored for our add-on developers including "Create a Software Evaluation for your Product in 10 Minutes", "The Addressable Market for LabVIEW Add-ons", "Professionalize Your Add-on or App Best Practices: Documentation and Icons" and "Hands-On - How to Build a LabVIEW Add-on with VI Package Manager".  Great work team!

 

Over 75 products now available on the LabVIEW Tools Network and Counting!

There's not really any explanation needed for this one!  We just keep growing and growing.

1 2 Previous Next