Trouble communicating with Serializer using a ZigBee Modem
Navigates to RoboticsConnection.com Home RoboticsConnection.com HomePage
RoboticsConnection User Forum
Home       Members    Calendar    Who's On
Welcome Guest ( Login | Register )
        



Trouble communicating with Serializer using a... Expand / Collapse
Author
Message
Posted Tuesday, July 22, 2008 7:49 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: Tuesday, July 22, 2008 10:27 AM
Posts: 2, Visits: 9
I have set up Visual Studio 2005 to run the TraxsterDriveService.sln.
 
I have extracted the RoboticsConnection_Services_MSRS_1.5.zip file under the samples directory.
 
I now have the following directories, with appropriate sub-directories:
 
Microsoft Robotics Studio (1.5)\samples\Platforms\RoboticsConnection\SerializerServices
Microsoft Robotics Studio (1.5\samples\Platforms\RoboticsConnection\TraxsterDriveService
 
I have followed the instructions in the document (InstallingSerializerServices.txt) incuding the setting the "Specific Version" to false for SerializerServices.Y2006.M08.Proxy and setting TraxsterDriveService as the start up project and setting the proper com port in the SerializerServices.config.xml file.
 
The solution builds fine however, when the command window opens and after it finishes loading all of the services I get the following repeating line for as long as the program runs:
 
Unable to open serial port
Initializing SerialIO, Port:3, BaudRate:115200
Unable to open serial port
Initializing SerialIO, Port:3, BaudRate:115200
Unable to open serial port
Initializing SerialIO, Port:3, BaudRate:115200
Unable to open serial port
Initializing SerialIO, Port:3, BaudRate:115200
 
I have tried other baud rates (9600, 19,200) but get the same repeating line but with the different baud rate.
 
I am using an XBee RF modem to communicate with the Serializer in the Traxter robot. The drivers for this device emulates a simple serial port that should make it look like a serial com port to the TraxsterDriveService program.
 
The XBee modem I am using is listed here:
 
The drivers for the device were downloaded here:
 
 
by clicking under the comment column where it reads "Microsoft WHQL certified.

Also available as a setup executable for default VID and PID values."

 

I have installed and configured the drivers for the XBee modem and I have verified that the modem is working using a program called (Device Monitoring Studio) to verify the communications to the device. When the program runs it shows LOTS of activity on USB device. I can capture the activity to a log file if necessary and post it here if that will help.
 
I get a power on USB LED light when I plug in the modem and when I run the TraxsterDriveService I can see the Rx LED light periodically as if it is receiving a signal from the computer but I never see the Tx LED light even though the activity recorded by the monitoring program seems to indicate it is trasmitting. (THE Tx LED is working since I can see it light when I plug in the modem to the USB port).
 
If I step through the code I am seeing more detail about the com port. It says the com port is already open.
 
I have the Serializer board installed in the Traxster robot with a XBee communication module installed and a brand new fully charged battery (it is a 9.6 volt 2200 mAH N-MH battery - tested at 9.99 volts when fully charged).
 
Bottom line is the Traxster is not responding to commands so any help you can give me to resolve this is appreciated.
 
Best regards,
Blake Mann
Continuum Software Consulting, Inc.
Mobile: (215) 584-6652
Post #590
Posted Wednesday, July 23, 2008 12:40 PM


Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Administrators
Last Login: Today @ 7:20 AM
Posts: 285, Visits: 414
Hi Blake,

Sorry it's taken so long to respond...I've been slammed this week.

Did you change the baud rate of the XBee module, that you plugged into the Serializer, to match the baud rate set in the Serializer firmware?  Typically, people have troubles w/ XBee because the baud rate of the module doesn't match that of the Serializer (e.g. XBee is talking at 115200, but the Serializer is talking at 19200).

Best Regards!

Jason Summerour
President,
Summerour Robotics Corporation
Microsoft MVP
www.roboticsconnection.com

Post #595
« Prev Topic | Next Topic »


Reading This Topic Expand / Collapse
Active Users: 1 (1 guest, 0 members, 0 anonymous members)
No members currently viewing this topic.
Forum Moderators: jsummerour, ringo

Permissions Expand / Collapse

All times are GMT -8:00, Time now is 8:28pm

Powered By InstantForum.NET v4.1.4 © 2008
Execution: 0.062. 13 queries. Compression Disabled.