Has anyone used this product it is free from Microsoft it has the ntx from lego and the bs2 boe-bot as well. I am looking at it I have not really found out much yet but that will come.
I have the sumo Boe Bot kit and have added bluetooth to both of the Boe Bots.· Both of the Boe Bots work with MSRS 1.5.· I would like to use these Boe Bots with the final release of Microsoft Robotics Development Studio 2008 (MRDS 2.0).· The documentation and support for Boe Bots that used to ship with MSRS 1.5 is no longer included in MRDS 2.0.· When I went searching for MRDS 2.0 compatible samples and documentation on the Microsoft Robotics forum, the answers I read indicate MRDS 2.0 does not work with the Bot Bots anymore.· The·people who seemed most knowledgeable about Boe Bots within the Microsoft forum indicated that Parallax will be releasing the documentation and samples that would have been included in MRDS 2.0.
Where can I find the Boe Bot documentation and samples that will work MRDS 2.0?· If these are not yet downloadable from Parallax, is there an estimate for when they will be·available (either·the beta or the final release)?
The code that Parallax developed for the Boe-Bot robot that works in conjunction with Microsoft Robotics Studio (MSRS) 1.5 is fully functional. It is ready to be used with Microsoft Robotics Developer Studio (MRDS) 2.0 so long as MRDS 2.0 is backwards compatible with MSRS 1.5 services. If it's not, Parallax is not going to develop PC code for Microsoft to fix this problem. Either Microsoft of perhaps a member of their community will have to do that if they want MRDS 2.0 to work with the Boe-Bot robot.
"It is ready to be used with Microsoft Robotics Developer Studio (MRDS) 2.0 so long as MRDS 2.0 is backwards compatible with MSRS 1.5 services."
It isn't fully compatible with MRDS 2.0.· As with any major release on a product, there are new features as well as changes to the old version.· I'm fairly sure that Parallax has known this for at least a year so it shouldn't be "news" to you at this point in time.· Selling a product that claims to be compatible, but isn't, is ... unprofessional, to say the least.
"If it's not, ..."
It's not.
"...Parallax is not going to develop PC code for Microsoft to fix this problem."
You wouldn't be developing PC code "for Microsoft".· You would be writing documentation for your own product.
Comments
http://www.parallax.com/Store/Robots/RollingRobots/tabid/128/CategoryID/3/List/0/SortField/0/Level/a/ProductID/390/Default.aspx
Dave
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Dave Andreae
Parallax Tech Support·
Dave
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Dave Andreae
Parallax Tech Support·
http://msdn.microsoft.com/en-us/robotics/default.aspx
The download for the Express Edition of Visual Studio, check at:
http://www.microsoft.com/downloads/details.aspx?FamilyId=F3FBB04E-92C2-4701-B4BA-92E26E408569&displaylang=en
·
Where can I find the Boe Bot documentation and samples that will work MRDS 2.0?· If these are not yet downloadable from Parallax, is there an estimate for when they will be·available (either·the beta or the final release)?
The code that Parallax developed for the Boe-Bot robot that works in conjunction with Microsoft Robotics Studio (MSRS) 1.5 is fully functional. It is ready to be used with Microsoft Robotics Developer Studio (MRDS) 2.0 so long as MRDS 2.0 is backwards compatible with MSRS 1.5 services. If it's not, Parallax is not going to develop PC code for Microsoft to fix this problem. Either Microsoft of perhaps a member of their community will have to do that if they want MRDS 2.0 to work with the Boe-Bot robot.
Andy
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Andy Lindsay
Education Department
Parallax, Inc.
It isn't fully compatible with MRDS 2.0.· As with any major release on a product, there are new features as well as changes to the old version.· I'm fairly sure that Parallax has known this for at least a year so it shouldn't be "news" to you at this point in time.· Selling a product that claims to be compatible, but isn't, is ... unprofessional, to say the least.
"If it's not, ..."
It's not.
"...Parallax is not going to develop PC code for Microsoft to fix this problem."
You wouldn't be developing PC code "for Microsoft".· You would be writing documentation for your own product.