Difference between revisions of "Eiffel NXT"

(Initial Entry)
 
 
Line 1: Line 1:
 
[[Category:Projects]]
 
[[Category:Projects]]
  
 +
{{NoProjectMembers}}
 
== Overview ==
 
== Overview ==
 
There are a number of libraries springing up to support communication with [http://mindstorms.lego.com LEGO NXT Mindstorms] "bricks" remotely. Popular ones include a transport layer for communicating with the brick. Communication general is channeled through bluetooth or a hardwired USB connection.  
 
There are a number of libraries springing up to support communication with [http://mindstorms.lego.com LEGO NXT Mindstorms] "bricks" remotely. Popular ones include a transport layer for communicating with the brick. Communication general is channeled through bluetooth or a hardwired USB connection.  

Latest revision as of 13:21, 8 August 2007


Warning: To adhere to the standards for the Projects category, this project page should include a "Project members" section listing contributors and means to contact them. Please add this information, then remove the present notice.


Overview

There are a number of libraries springing up to support communication with LEGO NXT Mindstorms "bricks" remotely. Popular ones include a transport layer for communicating with the brick. Communication general is channeled through bluetooth or a hardwired USB connection.

Using an API the developer can query information on attached sensors, both LEGO sensors and third party sensors, like those developed by HiTechnic, or activate any connected servos. The remote APIs unbind developers from the confines of using the packaged limiting graphical builder (NXG), a micro amount of disk space (128KB) and volatile memory (32K). The APIs also permit access to external data stores, use of processor intensive computations/AI as well as many other things.

Existing APIs

A number of popular APIs are written in C#, Java, Perl and another written in Python. Microsoft even have integrated support in the Robotics Studio.

The Project

A project for a group at ETH would no only include writing such an API but also building a cross-platform library for communicating using Bluetooth and USB. EiffelStudio could then be extended to deploy a compiled project to the NXT brick, after a successful compilation. EiffelStudio could also be extended to support running and aborting programs on the brick, via the Run and Stop EiffelStudio commands.