Why Windriver?

[Greg McKaskle]

Wow. Where to start.

WindRiver is the supplied C++ tool because VxWorks is the realtime OS that has been used on the cRIO for the last ten years. Targeting a piece of HW is a bit harder than choosing how you type text and where the compile button is located. The libraries and drivers for supporting the hardware have been engineered by WindRiver to be far more realtime than what you will find on desktop OSes. This is a huge investment, and is why VxWorks is highly regarded as a realtime OS vendor. The landscape is constantly changing, but NI chose to use VxWorks because it made our customers happy and allowed the cRIO perform tasks it otherwise couldn't.

It is possible to use other code tools to target the VxWorks environment, and at NI, many of the developers subset the IDE, using only the command line or using the IDE for source, but not the debugger, etc. It is a matter of preference and efficiency. When your paycheck and your coworker's paycheck depend on getting the job done, you need to learn to evaluate what each element brings to the table. What are the good and bad aspects of different tools, etc. If something irks you, but works well, more than likely, you change your habits rather than the tool. Also, it is an ongoing evaluation. You always look around for the thing that will let you do more, do it better, or do it faster.

Is OpenSource an option? Absolutely. If you go to ni.com/linux, you will see a listing of products we offer. Also, some open source libs are amazing and are incorporated into NI products. LV extended and has shipped the Mesa OpenGL engine for twelve or so years, as an example. But again, choosing an OS is a bit more complicated, and isn't a static decision. Linux is evolving and it may be an option in the future. I used free and open SW before GPL and other licensing manifestos came about, and I have to say that I preferred it without the strings. I'm not sure I understand how they made things better.

As for using more HW, you have options. FIRST lets you use coprocessors and circuits to enhance your robot. FIRST is also trying to make things a bit easier and a great deal safer, so elements such as the battery, motors, and safety are top priority. If/when there is a way to do that with other products, I suspect you'll see it. In the meantime, this is just part of the game -- same for all.

As for open source, I'm curious why open source tools are any better for FIRST than proprietary ones? Does gimp sponsor your regional? Does Linus Torvalds sponsor your team? It'd be cool if they did, but do you see my point? FIRST is one of the most effective organizations I've ever seen at organizing volunteers and getting things done for free, and I suspect they do things this way for a reason. Meanwhile, if you look into the licensing agreements of the tools in the kit, you will see the influence of open source. It is a real factor in the market today, but not in the "I will isolate myself and only use open source" sort of way.

Finally, as for LV, my guess is that you still haven't even tried it. If you are interested in computer science, I'll once again encourage you to take full advantage of the kit. Learn how to use generics in C++, objects in Java, and wires in LV. Also, learn how to use a multimeter, put on a chain, prove an algorithm, model the forces on an arm. Learn how to lose an argument without going to forums to complain about your team and mentors. Learn how to teach and be taught. Keep asking why, but make sure that you do it in a nice way.

Greg McKaskle