Eddie - Robot Dashboard not coming up
Hi All,
I just finished building an Eddie Robot. I got the board programmed and Kinect SDK 1.7 installed. I also downloaded the new code to fix the Kinect issue from the Beta version of the code.
I am now able to run the .user version of the code without red (runtime) errors. But, the issue is that the Robot Dashboard isn't coming up...I can see the Ping sensors working (green LED blinks)...and no error messages on the DSS screen.
I do not have the Xbox Wireless controller. Could that be the issue?
Should I see sensor data displayed on the screen? All I see open is the DSS screen.
Any help would be appreciated.
Thanks,
Nick
I just finished building an Eddie Robot. I got the board programmed and Kinect SDK 1.7 installed. I also downloaded the new code to fix the Kinect issue from the Beta version of the code.
I am now able to run the .user version of the code without red (runtime) errors. But, the issue is that the Robot Dashboard isn't coming up...I can see the Ping sensors working (green LED blinks)...and no error messages on the DSS screen.
I do not have the Xbox Wireless controller. Could that be the issue?
Should I see sensor data displayed on the screen? All I see open is the DSS screen.
Any help would be appreciated.
Thanks,
Nick
Comments
I seem to be having the same or similar problem to you.
I have got to running the eddie command from the DSS and I get some errors. I have attached the output file from DSS.
If you or anyone else can help I would appeciate it.
Also, I'm in Melbourne Australia and would like to meet locals building Eddie's and using Microsoft Robotics.
Regards
Mike.
DSS Output is as follows:
C:\Users\Mike\Microsoft Robotics Dev Studio 4>REM Run an Eddie Robot with Obstacle Avoidance and the Robot Dashboard
C:\Users\Mike\Microsoft Robotics Dev Studio 4>"C:\Users\Mike\Microsoft Robotics Dev Studio 4\bin\\dsshost32" /p:50000 /t:50001 /m:"C:\Users\Mike\Microsoft Robotics Dev Studio 4\bin\..\Samples\Config\EddieObstacleAvoid.manifest.xml"
* Service started [08/19/2013 10:59:07][http://127.0.0.1:50000/directory]
* Service started [08/19/2013 10:59:07][http://127.0.0.1:50000/constructor]
* Service started [08/19/2013 10:59:07][http://127.0.0.1:50000/console/output]
** Common Create Handler ExceptionSystem.InvalidOperationException: Service not found: http://schemas.microsoft.com/robotics/2011/08/kinect.html
at Microsoft.Dss.Services.Serializer.DataCache.LoadServiceAssemblies(ServiceInfoType createRequest)
at Microsoft.Dss.Services.Constructor.ConstructorService.CommonCreateHandler(DsspOperation create) [08/19/2013 10:59:07][http://127.0.0.1:50000/constructor]
* Rebuilding contract directory cache. This will take a few moments ... [08/19/2013 10:59:07][]
* Service started [08/19/2013 10:59:08][http://127.0.0.1:50000/serialcomservice/9fb83413-f0e7-470c-bf11-09ab18bdecec]
* Contract directory cache refresh complete [08/19/2013 10:59:12][]
** Common Create Handler ExceptionSystem.InvalidOperationException: Service not found: http://schemas.microsoft.com/robotics/2011/08/kinect.html
at Microsoft.Dss.Services.Serializer.DataCache.LoadServiceAssemblies(ServiceInfoType createRequest)
at Microsoft.Dss.Services.Constructor.ConstructorService.CommonCreateHandler(DsspOperation create) [08/19/2013 10:59:12][http://127.0.0.1:50000/constructor]
*** Error creating service. Service type:http://schemas.microsoft.com/robotics/2011/08/kinect.html [08/19/2013 10:59:12][http://127.0.0.1:50000/constructor]
*** Service creation failure most common reasons:
- Service contract identifier in manifest or Create request does not match Contract.Identifier
- Service references a different version of runtime assemblies
Additional information can be found in the system debugger log.
[08/19/2013 10:59:12][http://127.0.0.1:50000/manifestloader/7b54573e-6557-48af-8b68-682a33d0f1bf]
* Service started [08/19/2013 10:59:12][http://127.0.0.1:50000/parallax2011referenceplatformiocontroller]
I did do a "rebuild" for all of the code within RDS. 0 errors and 0 warnings. So, it seemed to work but still no luck getting things running.
Nick
Here's what I did. After you change the COM port to allow the PC to talk to the Eddie Controller board, you need to recompile the Eddie controller software. There is a BAT file that does this. It is located within Eddie Reference section (I think - I'm not in front of the Robot right now).
Anyway, no more Assembly errors. Now, I need to figure out why the Kinect UI doesn't want to come up...I also tried to run it via DDS and the KinectUI command.
Hope this helps someone.
Nick