Slashdot Mirror


.Net On Lego Mindstorm

troop23 writes "A blog posting by Benjamin J. J. Voigt says this "The University of Potsdam has a project to develop a .NET VM for the Lego Mindstorms system. Lego Mindstorms just got a higher priority on my shopping list!" While the thought of using .Net to program Lego Mindstorms may not be palatable, having a mainstream dev environment sure is." Perhaps Mono would work just as well.

6 of 132 comments (clear)

  1. Java VM by Anonymous Coward · · Score: 5, Informative

    A Java VM exists already. It's called leJOS.

  2. NQC? by MrFlannel · · Score: 5, Informative

    There already is a C compiler (well, its very close to real C) its called NQC (Not Quite C). You can buy a book about it. Google yields this as its site. http://bricxcc.sourceforge.net/nqc/

    --
    Clones are people two.
  3. Developing for the Mindstorms brick by mollymoo · · Score: 5, Informative
    I've been playing with Mindstorms for a few years. There are basically two approaches used for programming the brick: Using the Lego firmware and replacing it. The graphical Lego programming language provided with the kit compiles to bytecodes which run on the Lego firmware. It's not very fast or flexible. The brick is a Hitachi H8 at heart, so writing code for it is preferable if you know how.

    NQC (Not Quite C) is compiled to Lego bytecodes. BrickOS programs are compiled to H8 with gcc. There are also Forth and Java environments.

    Given the range of options available (for *nixen, Windows, Mac...) I'd have to say in this case "mainstream" must mean "Microsoft".

    --
    Chernobyl 'not a wildlife haven' - BBC News
  4. Re:IDL Libraries? by omicronish · · Score: 5, Informative

    Great now you'll have to include 60 MB of IDL code to run any program. Where do these ideas come from? Who would think to port a bloated server app development API to a portable device. .NET is loved by managers who think they can dumb down their server side code so any H1-B can do it, that's about it. Nobody even uses .NET for desktop apps, so where'd the idiotic idea that it would take off in a portable environment come from. The main reason I refuse to use .NET for desktop apps is the 60 MB IDL needs to be included, better to VB 6 or anything else for that matter. M

    I would imagine most of that 60 MB is the .NET framework library, only a fraction of which you'd really need to port to portable devices. Stuff like ASP.NET, Winforms, the entire System.Drawing namespace probably wouldn't be needed. At the very core you'd only need an execution engine, which is basically an IL interpretor, and perhaps a partial implementation of the System namespace. Yes, there's bloat, but certainly nothing like 60 MB, and for something non-critical like Lego Mindstorms, the bloat would be acceptable to me.

  5. Re:Is Lego back on firm financial ground? by mark-t · · Score: 5, Informative
    They are not pulling the plug on Mindstorms.

    See here (January 2004) and here (March 2004)

    There was quite a kafuffle shortly after Christmas of last year when LEGO announced their shift in direction. Quite a large number of people were very concerned that LEGO would be dropping Mindstorms. Flurries of posts on LEGO discussion lists and even letters directly to LEGO were filled with remarks much to the effect of "What?!?!? Why is LEGO doing this?" LEGO issued the January press release above to abate those concerns. Also mentioned above is a March release in which they restate the Mindstorms is one of their core products and they will *NOT* be dropping it.

    First Lego League is also very dependant on Mindstorms, and I don't think they're going away anytime soon.

  6. Re:Why? by xenocide2 · · Score: 5, Informative

    Funny story about Java. Originally it was designed as a language for embedded systems, back when it was called Oak. There, the idea of a VM to provide various system tasks is actually quite tenable. The idea being, they write the VM once for a platform, and you're free to start prototyping the code before you finalize your choice of board.

    Reality sunk in, and the embedded systems market just didn't like the idea. Training people in the new language was going to be expensive (compared to the status quo), and most were skeptical about the utility of a VM. The concern being that you typically need or want access to specific available resources that an abstract interface can't provide.

    Seems marketing shifted gears and started pushing applets and the web. Went okay for them in the end, I guess.

    --
    I Browse at +4 Flamebait

    Open Source Sysadmin