Anybody knows how to program in the codes to the real robot and if I need to change anything to my codes because I was doing it in the simulation.
Thanks.
You need more than just an iRobot Create to run the Sumo code. The Create doesn't have an onboard processor that can be used to run user code to allow the robot to be autonomous. For the Sumo competition that we sponsored at MEDC, we built sumo robots that used the iRobot Create as a base along with a webcam and an ICOP eBox 2300 processor. You can find complete instructions for assembly a similar sumobot here:
http://msdn2.microsoft.com/en-us/robotics/bb403184.aspx
-Kyle
A few things to check
1. That you can ping the ebox
2. Run ConmanClient and CMAccept on the ebox
Let us know if this solves your problem.
Ioana
Hi,
When you are trying to deploy are there any MSRS nodes running on the device you are trying to deploy to It looks like you have a process running that is using cf.webcamservice.y2006.m05.proxy.dll. One thing you could try is to restart the device, reconnect it to VS and then deploy again.
Let me know if this helps.
Ioana
Hi,
What might happen is that a MSRS node is started automatically when you reboot the device ( MSRSAutostart does that) which would be the reason why you cannot copy the file because it in use. What you want to do is restart the device and then hit cancel when MSRSAutostart tries to start a node.
Then you can deploy to the device.
Let me know if this helps.
Ioana
The \Windows\StartUp folder contains a link to \bin\msrsautostart.exe. This exe calls \bin\startdsshost.cmd. The cf.dsshost.exe is started with the following parameters.
/p:50000 /t:50001 /mumoPlayer.Hardware.Manifest.xml
Hi,
You are missing the manifest file for your service. The manifest is the file that tells the node what services it needs to start and what initial configuration they should have.
If you created SittingDuck project using DssNewService it should have created a manifest for you. You need to modify that manifest to start the service that you want. You can do that directly or using the DssManifestEditor that is part of Microsoft Robotics Studio.
When you deploy you need to mark the manifest file as Copy Always as well as the SuttungDuck.hardware.config. Make sure you copy the manifest file in the MSRS bin directory on the Ebox.
Then you can start your service in 2 ways.
1. Manually from the bin folder >cf.dsshost.exe /p:50000 /t:50001 /m:<your manifest file>
2. By modifying the startdsshost.cmd commnad and replacing the name of the manifest with your manifest. Doing this will ensure each time you reboot the device that your service gets started.
Let me know if this helps,
Ioana
Hi,
Looking at you version number it looks like you are running on the May CTP. Could you please install Microsoft Robotics Studio 1.5 from here: http://msdn2.microsoft.com/en-us/robotics/aa731520.aspx. You also neeed to install the Sumo Package. After you've done follow again the instructions and copy the right runtime and files to the EBox.
Did you replace the manifest in the autostart. Also in your manifest for SittingDuck can you check that you have the correct service uri.
Let me know if you run into any other issues.
Ioana
Hi,
When you installed the new version of MSRS 1.5 and the Sumo package did you replace the files in the bin folder on the ebox Looks like you might have the wrong version on the ebox.
In 1.5 when you create a sumo service following the instructions it renames the manifest to sumoplayer. You can name it whatever you want. However make sure the MSRSautostart starts the right manifest. Also the manifest file should be placed in the same folder on the Ebox as the services and cf.dsshost.exe.
Let me know if you this helps.
Ioana
hi newbie_sg,
I've been following along with this thread and I am in about the same place as you.
This is what I have found out so far:
When I created the link by copying MsrsAutoStart.exe and selecting "paste link" in the \Windows\Startup folder, the link appears with a size of about 55 bytes. When I look in the properties window of that link, I see two tabs. The shortcut tab has a target containing:
"\Program Files\msrs\bin\cf\MsrsAutoStart.exe"
which is correct for my machine. When I edit this field and put all the parameters in it, similar to your example, I notice that the byte count goes to zero. If I then look at the properties, I see that the shortcut tab is missing.
Through trial and error, I discovered, at least on my machine, that there is a limit of 117 bytes that you can put in that field. Any more and the link goes into that wierd state and is unrecoverable. I must delete it and create a new one.
To get around this limitiation, I had to put the arguments into a text file that I called "DssArgs.txt", the contents of which look like this:
-p:50000
-t:50001
"-m:\Program Files\msrs\bin\cf\SumoPlayer.hardware.manifest.xml"
I had to put this in the root directory because there doesn't seem to be anything like a Path variable in CE. The resulting value of the target field in the shortcut tab of the link property looks like this:
"\Program Files\msrs\bin\cf\MsrsAutoStart.exe" "@DssArgs.txt"
This seems to have gotten me past this hurtle, and I'm stuck at the next. I don't know if this helps you or even if it is the right approach, because I've found no documentation on the subject. Anyway I thought I'd share my little adventure.
Good luck,
Dogulas