Broken programming port on RC

[neoshaakti]

last night, our mentor accidently tripped over a DP9 cable that was connected into the programming port resulting in the breaking of the programming port
our other mentor has suggested trying to resolder a 9 pin DP9 female port back onto the controller
to any1 experienced with motherboards and microprossesors...do you think this is a good idea?
any suggestions on how we can possibly get a new controller, or work arounding not being able to program our robot...
thank you!

[Jonathan Norris]

We done that exact same thing too many times before, you learn very quickly not to secure the pins in your programing port. The first thing you need to do is contact IFI and arrange for a replacement, then depending if you have an older controller lying arrond (seeing that you are rookie team i doubt that), or you can try and resolder the programing connections for the time being (we have done this sucessfully before, but it takes a skilled electrician and lots of time). But you will need a replacement to compete.

[EHaskins]

I've replaced the main power connectors on four of the last five years control boards, because they always seem to break a competition.

I see no reason why you can't replace the port, other than the voiding the warenty issue. My theory is that if you can make it work for competition this year, then you're fine, since you'll get a replacement next year.

However, you should contact IFI and see what they can do.

[dtengineering]

Been there, done that... we ripped our tether port out at GTR in '05.

While the recommended way of doing the repair is to contact IFI, request an RMA and send it in, then wait for it to come back, time is of the essence.

Since the damage is likely not covered by warranty... although IFI is usually pretty understanding about stuff like this, the mentor's foot is hardly a "manufacturing defect"... you may as well void the warranty anyways and take a look inside the case to survey the extent of the damage.

If you have had a "clean break" and the pins have just pulled out of the board, then soldering them back in... or replacing the socket... with a new one shouldn't be too difficult. If the pins are still soldered in, then that is a bit more difficult as the holes are through-plated, making extracting the remnants of the damaged port more of challenge... although far from impossible. If the board is damaged... well, then you have a bigger problem.

One thing you may want to do once you get this fixed is to permanently mount a programming cable and tether cable on your robot, then tie them down to the robot frame. That way if you trip over them, the only thing that will be damaged is an easily replacable serial cable.

Again, the "right" way to solve this problem is to contact IFI and have them do a warranty approved (if not warranty covered) repair, and if you were a veteran team with a spare controller to pull off an old robot to refine your code in the final week... well, then that would make sense. But you simply can't afford to lose the RC for the next week. Even three or four days is going to be a huge loss.

If you have a neighbouring veteran team, and contacted them, there is a good chance they would lend you an old controller and you could courier yours to IFI... but if that isn't an option then going ahead and doing some repairs on your own could have you back up and running in a couple of hours.

Jason

P.S. By the time you compare the cost of express-shipping your RC to IFI and back to the value of a four-month warranty on a $450 piece of equipment, it probably makes financial sense to attempt the repair yourself, too.

[jsfinne]

Everyone has done this. We keep a supply of replacement DB9's. A little careful surgery and you are as good as new and, besides, time is short. If you need a DB9, contact me and we can make arrangements. I am local to JPS.

Jim Finne
jsfinne@optonline.net
Team 136, Plainfield. NJ

[neoshaakti]

thank you all for your support
in the next day or two Ill post a picture of our RC
hopefully it will be fixed when I do

[frc2008]

Originally Posted by jsfinne

Everyone has done this. We keep a supply of replacement DB9's. A little careful surgery and you are as good as new and, besides, time is short. If you need a DB9, contact me and we can make arrangements. I am local to JPS.

Jim Finne
jsfinne@optonline.net
Team 136, Plainfield. NJ

Jim,

can you send me your phone number on viswanatham@gmail.com. I will contact you and let me know when can I call you. I am awake for this tonite and want to finish it tomorrow morning after getting the part.

[Mr. Freeman]

I've never really understood people's obsessions with tightening the screws on those cables. Just because they're there does not mean they should be used. I'm just waiting for IFI to make an RC & OI that has a connector with a magnet next to it and a cable interface with little to no friction, like the new apple laptop power cords. Tip over it and the cable goes flying, but the laptop stays where it should.

[ay2b]

Originally Posted by Mr. Freeman

I've never really understood people's obsessions with tightening the screws on those cables.

I've found that the solution to this, at least in some cases, is to remove the screws from the cables.

On the other hand, I firmly believe that you SHOULD screw in the cable that connects the radio to the RC.

[whitetiger0990]

If the our programming cable is somewhere where it can be tripped over, I make sure to wrap it around something. When it gets pulled it tightened around whatever it's wrapped around instead of putting a whole lot of stress on the port. Several years ago one had been broken, so I've made sure to keep it more protected and away from direct strain.

[Mark McLeod]

Originally Posted by ay2b

On the other hand, I firmly believe that you SHOULD screw in the cable that connects the radio to the RC.

I'd normally agree. I did just visited a team that ripped out their radio port connector though...

In several cases of destroyed RC DB9 connectors that I've seen, the culprit wasn't screwed in connectors, but just a bad angle that put a lot of side pressure on the connector. For instance, when the robot took off the cable was stretched back lengthwise over the RC and the connector was yanked up and back.

In all cases I'd recommend strain reliefs for DB9 cables, power lines, PWM-style connectors, pig-tails, etc. connected to delicate parts of the RC.

[d25inferno]

Hey guys although we got our programming port working for the regionals we believe it is malfunctioning again. When we try to connect w. our robot we get an error message on EasyC that our programming light isn't yellow when it is. Th computer can "see" that the RC is connect, it just cant access the RC since it thinks the button wasnt pressed. If any teams have had this problem before and know a solution Team 2554 would be much obliged. Thanks!

[tdlrali]

Connect your RC to your laptop, and open up the terminal window in ifi-loader (or any other serial terminal). Hit the reset button a bunch of times, then put the robot controller into programming mode (hold the button). Do you see an "IFI>" prompt printed to the terminal?