Search code examples
labviewrobotics-studio

Comparing LabView and Microsoft Robotics Studio


On the surface LabView and Microsoft Robotics Studio appear to me to have a very similar programming paradigm and environment.

Is it fair to compare these two products, or are they in different leagues?

I am hoping someone who has used both products will help compare and contrast them so that I can understand when it is appropriate to use one or the other.


Solution

  • Disclaimer. I have not worked with Microsoft Robotics Studio. I only looked at the fact sheet and some of the documentation. However I have a great deal of knowledge of LabVIEW. So this answer might be (and probably is) biased.

    History wise LabVIEW has been around for 20 years and has the following features which MSRS doesn't have (from the first glance).

    • Platform independent (LV compiles on Windows, Linux, Mac and various embedded platforms), however hardware support varies
    • A compiler, directly into machine code
    • LabVIEW is a programming language not targetted at robotics but originated in Test and Measurement
    • Extensive DAQ and data analysis support

    The VPL (MSRS) looks very clumsy compared to LabVIEW code, it looks like MS doesn't really makes the switch to visual programming (or is not allowed by patents from third parties).

    Price wise, MSRS is much friendlier with a free 'hobbyist' version, while a LabVIEW base begins around $1300.

    Additional MSRS does not run on the robot, it only controls the robot via the robot API (bluetooth or wired), while LabVIEW (and more specific NXT-G) run on the processer inside the robot stand-alone.

    What might be important is the LabVIEW is the main software product of NI while MSRS is one of many products of MS, so support and development should have a higher priority.

    Ton