Go to Post We may not have a robot yet, but we have Robot Potential! - Blue_Mist [more]
Home
Go Back   Chief Delphi > Technical > Electrical
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #1   Spotlight this post!  
Unread 03-15-2011, 10:05 PM
Unsung FIRST Hero
Mike Betts Mike Betts is offline
Electrical Engineer
no team
Team Role: Engineer
 
Join Date: Dec 2001
Rookie Year: 1995
Location: Homosassa, FL
Posts: 1,442
Mike Betts has a reputation beyond reputeMike Betts has a reputation beyond reputeMike Betts has a reputation beyond reputeMike Betts has a reputation beyond reputeMike Betts has a reputation beyond reputeMike Betts has a reputation beyond reputeMike Betts has a reputation beyond reputeMike Betts has a reputation beyond reputeMike Betts has a reputation beyond reputeMike Betts has a reputation beyond reputeMike Betts has a reputation beyond repute
Intermittent Loss of Communications During Play

Symptom:
Robot loses communication momentarily after impact with another robot or with field element.

Disclaimer:
As with any real life, non-trivial issue, this is likely a multi-problem problem and the solution described may not mitigate all instances.

Discussion:
I was a robot inspector at the Florida Regional last weekend. There were numerous complaints of momentary loss of communications but no single clearing house to vet all problems… I helped quite a few teams and came to the conclusion that no robot which used the power supply cable which came with the DAP-1522 radio had this issue. In fact, while working with one team, we succeeded in getting the DAP to be completely unpowered even though it appeared securely plugged in. We were able to restore power to the DAP by touching the power connector ever so slightly (virtually a feather’s touch).

All of the teams that I assisted which were experiencing problems were using the power connector from last year’s robot or a connector that “seemed like it fit” from Radio Shack.

It is my (largely subjective) conclusion/theory/assumption that the barrel accepting the male pin in the connector is a few mils smaller on the DAP’s BOM connector than on the connectors giving is trouble. Also, the momentary loss of power to the DAP is just enough to corrupt its driver and/or firmware circuitry but not enough to force its CPU into a reboot condition.

Solution:
  • Find the AC power supply cord that came with the DAP-1522 and cut it in half.
  • Note that the wire has two conductors. The positive conductor is identified by a white stripe printed on the black insulation.
  • Install .250 spade disconnects on both ends so that you can revert to using the cable as an AC source in the future.
  • Now store the half connected to the AC power supply away for future use and wire the other half into your robot. Note that the white stripe conductor gets connected to the yellow lead of the 360-CPR.
Identification:
The power connector which came with the DAP is a molded plastic, right angle connector whereas last year’s connector was an axial leaded barrel connector.

Epilogue:
I strongly suggest that you at least pack the DAP-1522 power supply cable with your spares before departing to your competition. In that way it will be available if you encounter this problem.

Regards,

Mike
__________________
Mike Betts

Alumnus, Team 3518, Panthrobots, 2011
Alumnus, Team 177, Bobcat Robotics, 1995 - 2010
LRI, Connecticut Regional, 2007-2010
LRI, WPI Regional, 2009 - 2010
RI, South Florida Regional, 2012 - 2013

As easy as 355/113...
 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 04:25 AM.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi