Shop OBEX P1 Docs P2 Docs Learn Events
Difficulty using Boe-bot and Microsoft Robotics Studio, error message please he — Parallax Forums

Difficulty using Boe-bot and Microsoft Robotics Studio, error message please he

rashoperashope Posts: 4
edited 2007-05-21 17:03 in Robotics
Hi,

I've been trying to get my boe-bot to work with Microsoft Robotics Studio.· After speaking to customer support, I found out there was the issue with version 1.5 so I uninstalled it and installed 1.0 instead.· I have centered and tested the servos and followed all of the instructions for putting the boe-bot together.· Everything has worked perfectly until I tried to connect to it using·bluetooth.· I followed all of the instructions in the BluetoothControlledRobot.pdf and when I press the debug button, it begins to work correctly, opens the prompt,·bot beeps·and flashes and the bluetooth light comes on, but then the prompt starts displaying error messages.··I went ahead and tried to run the simple dashboard, but when I enter localhost and port 50001, I don't get any available services in the window like I'm supposed to (I did when I was trying version 1.5, but now I don't.)· All the while every few minutes while connected to bluetooth the robot beeps (I added debugging to get it to beep when it got new drive command input) and drives one wheel forward an inch or so.

Does anyone have any ideas?· Do I need a specific kind of bluetooth device?· I'm using a cheap Bluetake dongle.·

Thanks for any help you can give.· Here is the whole contents of the prompt including error messages:


*·· Service uri:· [noparse][[/noparse]http://beckysdell:50000/directory]
*·· Service uri:· [noparse][[/noparse]http://beckysdell:50000/constructor/fd8b4760-fb39-4502-85d4-b
623fd9a2706]
*·· Starting manifest load: [url=][/url]
ples/config/Parallax.BoeBot.manifest.xml [noparse][[/noparse]http://beckysdell:50000/manifestloader
client]
*·· Service uri:· [noparse][[/noparse]http://beckysdell:50000/basicstamp2]
*** Manifest Loader: Creating service failed: http://schemas.microsoft.com/robot
ics/2006/06/bsmotor.html.
Reason: Exception has been thrown by the target of an invocation.
InnerException: Could not load file or assembly 'BASICStamp2.Y2006.M06.Proxy, Ve
rsion=1.0.313.2, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its
·dependencies. The located assembly's manifest definition does not match the ***
embly reference. (Exception from HRESULT: 0x80131040) [noparse][[/noparse]http://beckysdell:50000/m
anifestloader/50523410-a48d-4bf4-a8d9-9f956eca7c3e]
*** Manifest Loader: Creating service failed: http://schemas.microsoft.com/robot
ics/2006/06/bsmotor.html.
Reason: Exception has been thrown by the target of an invocation.
InnerException: Could not load file or assembly 'BASICStamp2.Y2006.M06.Proxy, Ve
rsion=1.0.313.2, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its
·dependencies. The located assembly's manifest definition does not match the ***
embly reference. (Exception from HRESULT: 0x80131040) [noparse][[/noparse]http://beckysdell:50000/m
anifestloader/50523410-a48d-4bf4-a8d9-9f956eca7c3e]
*** ManifestLoaderClient: Initial manifest failed: http://www.w3.org/2003/05/soa
p-envelope:Receiver -> Fault [noparse][[/noparse]http://beckysdell:50000/manifestloaderclient]
*** IssuePartnerSubscribe: Timeout waiting for notification on partner: http://w
ww.w3.org/2003/05/soap-envelope:Receiver -> http://schemas.microsoft.com/xw/2004
/10/dssp.html:ResponseTimeout [noparse][[/noparse]http://beckysdell:50000/drivedifferentialtwowheel
]
*** IssuePartnerSubscribe: Timeout waiting for notification on partner: http://w
ww.w3.org/2003/05/soap-envelope:Receiver -> http://schemas.microsoft.com/xw/2004
/10/dssp.html:ResponseTimeout [noparse][[/noparse]http://beckysdell:50000/drivedifferentialtwowheel
]
*** Partner enumeration during service startup failed. Service will not start: h
ttp://schemas.microsoft.com/robotics/2006/05/drive.html
··· Partners specified statically in service implementation class:
······· PartnerAttribute Name:SubMgr,Contract[noparse]:http:[/noparse]//schemas.microsoft.com/xw/20
05/01/subscriptionmanager.html,CreationPolicy:CreateAlways
······· PartnerAttribute Name:LeftMotor,Contract[noparse]:http:[/noparse]//schemas.microsoft.com/ro
botics/2006/05/motor.html,CreationPolicy:UsePartnerListEntry
······· PartnerAttribute Name:RightMotor,Contract[noparse]:http:[/noparse]//schemas.microsoft.com/r
obotics/2006/05/motor.html,CreationPolicy:UsePartnerListEntry
······· PartnerAttribute Name:LeftEncoder,Contract[noparse]:http:[/noparse]//schemas.microsoft.com/
robotics/2006/05/encoder.html,CreationPolicy:UsePartnerListEntry
······· PartnerAttribute Name:RightEncoder,Contract[noparse]:http:[/noparse]//schemas.microsoft.com
/robotics/2006/05/encoder.html,CreationPolicy:UsePartnerListEntry
··· Partners specified at runtime, in CreateRequest:
······· Name: http://schemas.microsoft.com/xw/2004/10/dssp.html:StateService, Co
ntract: , Service: /mountpoint/samples/config/Parallax.BoeBot.Drive.Config.xml
······· Name: http://schemas.microsoft.com/robotics/2006/05/drive.html:LeftMotor
, Contract: , Service:
······· Name: http://schemas.microsoft.com/robotics/2006/05/drive.html:RightMoto
r, Contract: , Service:
······· Name: http://schemas.microsoft.com/xw/2004/10/dssp.html:ConstructorServi
ce, Contract: http://schemas.microsoft.com/xw/2004/10/constructor.html, Service:
·dssp.tcp://beckysdell:50001/constructor/fd8b4760-fb39-4502-85d4-b623fd9a2706
······· Name: http://schemas.microsoft.com/xw/2004/10/dssp.html:PartnerListServi
ce, Contract: http://schemas.microsoft.com/xw/2004/10/partnerlist.html, Service:
·dssp.tcp://beckysdell:50001/drivedifferentialtwowheel/PartnerManager
······· Name: http://schemas.microsoft.com/robotics/2006/05/drive.html:SubMgr, C
ontract: http://schemas.microsoft.com/xw/2005/01/subscriptionmanager.html, Servi
ce: dssp.tcp://beckysdell:50001/subscriptionmanager/e56ec9e1-a913-4fbf-a2b5-87fd
b3a4b1ee
·[noparse][[/noparse]http://beckysdell:50000/drivedifferentialtwowheel]

Comments

  • edited 2007-05-18 04:14
    This doesn't look like it has anything to do with your Bluetooth; it's somethig in the MSRS software or settings. I would recommend posting the same explanation and error messages in the MSRS forum.

    A few quick things to check: Make sure to open BASICStamp2.csproj using the MSRS command prompt. Also, make sure you have both BASICStamp2 and BSServices C# projects in the same solution file and that BASICStamp2 is the startup project.

    If the connection still doesn't work after the manifests correctly load, then we'll take a closer look at your Bluetooth module.

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Andy Lindsay

    Education Department
    Parallax, Inc.
  • rashoperashope Posts: 4
    edited 2007-05-19 17:50
    Hi Andy,

    I've just double-checked the things you suggested.· Everything seems to be in order and I'm still getting the errors.·

    I want to post the question to the MSRS forum, but I don't see it in the forum list... Can you point the way, please?· Thanks [noparse]:)[/noparse]

    Becky
  • PARPAR Posts: 285
    edited 2007-05-19 18:26
    rashope said...I want to post the question to the MSRS forum, but I don't see it in the forum list... Can you point the way, please?· Thanks [noparse]:)[/noparse]
    Start at http://forums.microsoft.com/MSDN/default.aspx?ForumGroupID=383&SiteID=1
    and browse around the several fora to see which one(s) might apply to your question(s).

    PAR
  • rashoperashope Posts: 4
    edited 2007-05-20 02:14
    Thanks Par [noparse]:)[/noparse]
  • rashoperashope Posts: 4
    edited 2007-05-21 17:03
    Andy,

    I'm pleased to report that the problem has been fixed! I got help from the MSRS forum. A rebuild did the trick: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1622741&SiteID=1

    Thanks for pointing me there.

    Becky
Sign In or Register to comment.