> >From the magazine article:
> "Yes, the studio is Windows based, but Trower said
> the runtime code it
> produces can run and work with virtually any
> platform. In fact, all that's
> necessary, according to Trower, is that the robot
> have some form of
> communication-essentially hooks that the run-time
> can tie into. As long as
> that exists, robotics developers can use the
> Studio's "services" layer to
> create the communication protocol."
>
> I read this to mean there is a "services layer" that
> is a software
> adapter/interposer for any given platform. That
> technique has been popular
> with teleprocessing controllers. If the "service
> layer" is open source, it
> would truly be platform independent.
>
> New packages always look good to me at first glance!
>
> John Ferrell W8CCW
> "My Competition is not my enemy"
>
http://DixieNC.US
>
> ----- Original Message -----
> From: "James Newton, Host" <
jamesnewton
spam_OUTpiclist.com>
> To: "'Microcontroller discussion list - Public.'"
> <
@spam@piclistKILLspammit.edu>
> Sent: Thursday, June 22, 2006 8:27 PM
> Subject: RE: [EE] Microsoft robotics development kit
>
>
> > Has anyone looked at what embedded processors this
> thing supports? They
> > say
> > in the intro that it manages several 8 and 16 bit
> CPU's but they don't
> > list
> > which ones.
> >
> > ---
> > James Newton: PICList webmaster/Admin
> >
KILLspamjamesnewtonKILLspampiclist.com 1-619-652-0593
> phone
> >
http://www.piclist.com/member/JMN-EFP-786
> > PIC/PICList FAQ:
http://www.piclist.com
> >
> >
> >
> >
