Comparing LabView and Microsoft Robotics Studio

Question

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.

Answer 1

ya, 불행히도 관련 항목 필드는 링크이기 때문에 연결할 수 없습니다.내가 항상 워크 플로가 워크 플로가 워크 플로가 생성하는 경우 새 태스크가 생성 될 때마다 워크 플로가 해당 열을 관련 콘텐츠 ID로 채우는 것입니다.이 방법으로 연결된 웹 파트 및 필터를 수행 할 수 있습니다.

Answer 2

I have programmed extensively with MSRDS and to a lesser extent with LabVIEW and here is my opinion. Earlier, most of our software used to developed using LabVIEW but the last few years we have been moving a major part of it to C# because it is much easier to do objected oriented programming using a language like C#. I personally feel MSRDS and in particular the Concurrency Coordination Runtime (CCR) is so underrated partly because of the not so detailed documentation. Although the MSDN forums are excellent, we are required to search through them to find out some of the things that I feel should have been part of the documentation. Another excellent source of information to refer is the book "Professional Microsoft Robotics Developer Studio" by Kyle Johns and Trevor Taylor.

Coming back to the comparison, I feel both LabVIEW and MSRDS (although I am not sure about LabVIEW Robotics) follow different programming methodologies. Although it has been targeted to Robotics, MSRDS is used to harness asynchronous behavior in any application. CCR has some excellent coordination primitives (such as Joins and Interleaves) and it makes asynchronous programming a lot easier. DSS is used to develop service oriented applications that are distributed across multiple nodes residing in the same machine or across different machines. We developed a framework for developing Laboratory Automation Systems using MSRDS. The framework is used to develop distributed component based software that is both thread-safe and responsive.

It is also worth mentioning that Task Parallel Library Data Flows in .NET 4.5 is based on the CCR concepts and also the concepts from .NET RX. I suggest you consider looking at them as well.

Thanks,

Venkat

Answer 3

I think Ton hit it on the nose, but there a couple key points I disagree on.

Independent of price LabView is a far superior system for automation and embedded programming. However, there is the catch that without a license LabView will break the bank a few times over. Depending on your targeted platform, you could easily spend several thousand dollars for a development environment.

Both systems do have a compiler. For a while LabView was restricted to only a few embedded environments, but with the addition of an ARM compiler there are now a huge number of supported hardware systems. LabView is compiled in real time as you program, MSDS is compiled on request (as far as I know).

LabView is absolutely targeted to robotics. NI has put forth a lot of tools for robotic applications and many of the ideas taken from automation can be dropped right into a robotics setting. As an interesting note, the FIRST Robotics Competition exclusively uses NI hardware (the cRIO) and LabView is a popular programming option.

RDS's visual programming and LabView's visual programing aren't really comparable. They don't operate by the same paradigms.

RDS does create machine code and the code can run on a robot without intervention.

If you are looking to buy a complete robotics system for development with LabView check out this page: http://www.ni.com/robotics/how_to_buy.htm

Just as a bit of background, I am a certified LabView developer and have used RDS with the lego NXT system as an instructor.