I’m not sure what this program is for (i read about it but it did’nt help to mush)
It sound cool and preti easy to use.
THX ALL FOR HELPING A BEGINER 
I can’t get it to do much of anything. I know it installed a whole lot of crap on my computer though and took forever doing it. So it must be good for something. 
I found that to. Hmm, maybe this is too much for me. 
YUP, me too… I downloaded it and all i got was about an hour worth of wasted bandwidth. It seems like all it is, is command prompts which are not very useful for a beginner and even if you fluent in a programming language you still use an editor like mplab or something.
IDK what it is or how to use it but if anyone finds out tell me.
Robotics Studio will require a robotic system with a PC running windows somewhere in it. If your robot has a PC on-board then you are set. If it’s something with a smaller processor then you will be running Robotics Studio on a remote PC communicating with your robot in some way.
Robotics Studio allows you to create a group of services that can be interconnected to form a system. If you take a look at the Robotics Studio support for the Lynxmotion arm that is available on this web site you’ll see a service that supports the SSC-32 board. This service is generic (it doesn’t know what the servos are connected to). There is also a service to control an arm that utilizes the SSC-32 service to actually control the servos. The arm service doesn’t know or care how to control servos and the SSC-32 service doesn’t know or care what the servos are being used for.
These services can be placed anywhere on a network of connected processors. You will probably have the SSC-32 service running locally on the PC connected to the SSC-32 board. The arm service could be running on another machine entirely. The concept of a “sea of services” is one of the features of Robotics Studio.
There are a group of HTML tutorials on how to get start with Robotics Studio on their website. There are also a group of video tutorials that are worth the time to view. If you look in the upper right corner there is a link to the HTML tutorials. These are a good introduction to how to use the system although there are a few mistakes in them.
This might be a little misleading to some, even though it’s not what you mean to do.
Robotics Studio does not require Windows to actually be running on the robot itself. It requires that a robot be controllable from a PC running Windows and Robotics Studio. Theoretically, any robot can be controlled by a PC running Windows and Robotics Studio. The communication between Robotics Studio and the robot can be through something as simple as a hardwired cable, or a wireless communications link such as Bluetooth, ZigBee, or WiFi.
Again, this is not necessarily going to be the case. Robotics Studio does not require that any part of the robot’s hardware be physically connected to it. The SSC-32 service does not have to be running on the PC that is connected direct to the SSC-32 itself. In fact, the SSC-32 service will be running on the PC that is running Robotics Studio (a Windows PC). The SSC-32 itself will be on the robot being controlled by Robotics Studio. If the robot is not tethered to the Windows PC by a cable and is not connected direct to the Windows PC, there will have to be a wireless link between the robot and the Windows PC running Robotics Studio.
Are these tutorials fixed now and can they actually be run through all the way? The last time I checked, with the November CTP, there were still problems with the tutorials and they were not clear and I could not complete them. I was being literal and trying to follow them literally to complete each step to see if a raw beginner would be able to complete them. I even sent feedback about the problems I found.
8-Dale
Yes, that is what I meant to say. You just made it clearer, thanks.
That is correct. If the SSC-32 is on a remote processor the SSC-32 service running locally on the PC will need to perform some form of communication to make the requests to the remote SSC-32. Effectively the remote microprocessor becomes the peripheral to the SSC-32 service on the PC.
Unfortunately, no. This is by far my biggest complaint with the whole system is the level of documentation. However if you can work beyond the couple of issues in the early tutorials most of them work fine.
Jon
True. Afterall, if the robot doesn’t have some intelligence (a microcontroller) of its own, then it becomes little more than an end effector for Robotics Studio, which is not a robot at all, even though it may be a robotic system. Very little feedback to Robotics Studio would be possible with this kind of setup unless it uses the raw analog and digital I/O features of the SSC-32, which is still very limited in number for the analog I/O. I’ve always held the opinion that if a machine does not have a microcontroller and ability to gather and process information about it’s environment and act on that information to interact with the environment, it is not a true robot at all. I believe true robots are autonomous, and these are the kind of robots I design and build.
This is what will also be the downfall of Robotics Studio if Microsoft does not get with it and do some proper documentation and get the tutorials fixed such that they can be gone through literally. Tutorials are supposed to be an aid to assist learning how to use a system, whether hardware based, software based, or both. Microsoft has dropped the ball in a major way with respect with Robotics Studio if they still haven’t fixed the tutorials. Personally, I still think Robotics Studio is way more complex than it should need to be for what it is supposed to do and Microsoft is just trying to leverage more existing code into a new market. I’m not it is wrong to do that, but the code they are leveraging isn’t necessarily meant for or designed for this purpose.
8-Dale