How to prevent broken ethernet port on DS

[Bharat Nain]

After having significant amount of trouble with this years control system, we discovered that the ethernet ports on the Driver Station were obviously not designed for a FIRST Robotics environment. Personally, I am extremely disappointed and frustrated with the control system, especially the Driver Station. We have noticed an incredible number of teams having broken driver station ethernet ports. Our theory is it is because of static electricity but that is unconfirmed. It is certainly not a competition worthy equipment and it would be a great demonstration of Gracious Professionalism on behalf of FIRST to never give us such equipment again. Rambling aside, here is the solution.

1) Buy a decent SWITCH. We bought the Linksys 5-port Switch. Link. Apparently, a HUB will not work.

2) Plug one ethernet cable from the Driver station (Any port) to any port on the SWITCH except the Uplink.

3) Plug the laptop and cRio using a Crossover/Ethernet into any open ports on the SWITCH except the Uplink.

This method was requested to be tested by a couple people including the NI guy (Joshua) at NJ. If anything will die, it can be your $10 - $50 SWITCH as opposed to your $162 + Shipping & Tax Driver Station.

Note: This will also work if you only have one working ethernet port on your Driver Station.

This system works for us and I hope it does the same for you. It is one less thing to worry about breaking at the competition.

Cheers and write to FIRST and providing your feedback if your Driver Station has/had problems.

Bharat Nain

[nathanww]

I might be mistaken, but isn't having anything sitting between the FMS and the DS forbidden at the competition?

[artdutra04]

Originally Posted by nathanww

I might be mistaken, but isn't having anything sitting between the FMS and the DS forbidden at the competition?

The problems are arising on the practice field, where the robot is tethered to the driver station.

[EHaskins]

Originally Posted by Bharat Nain

A hub will work. I have tested it. Under most circumstances switches offer better performance, but with the amount of data being transmitted and the number of devices it will not cause any issues.

BTW, I've been using a switch I got a Goodwill for $0.50.

[EricVanWyk]

Some very cheap hubs do not offer ESD protection.

[byteit101]

Someone on our team found out that most of the people with problems on the eth ports were using cat5, and people with no problem were using cat6, which has better shielding and grounding. Our team is ordering a switch and cat6's.

[Kevin Sevcik]

Originally Posted by byteit101

Someone on our team found out that most of the people with problems on the eth ports were using cat5, and people with no problem were using cat6, which has better shielding and grounding. Our team is ordering a switch and cat6's.

Garden variety Cat6 is highly unlikely to have better grounding or shielding than Cat5. I can categorically declare this because most common Cat6 and Cat5 cables are Unshielded Twisted Pair. You can get it in Shielded Twisted Pair, but it's much harder to find and isn't going to make a difference unless you're also using shielded connectors.

The primary difference between Cat6 and Cat5, is that Cat6 meets higher standards for crosstalk and various things, and usually has a higher gauge wire. These things may make a difference in ESD protection, but any ESD protection isn't due to increased shielding.

[Chris_Elston]

We are not having a problem with static, but rather the port itself needs to be mounted to the board more firmly. What I saw was there are only two plastic post that are through holes to the bottom side of the board. When you insert the cat5 cable repeatedly, you seem to cause stress on these anchor posts. When these anchor posts give or break loose, your in trouble because then the connections in the back tip up and break off the pads on the surface mount. You can attempt a trace repair. It's quite alot of work but I believe if that is the only thing wrong, it can be done. Since we had the cover off, we went ahead and put hot clue on the second working port along the sides and the posts on the bottom to give it extra strength. As well as the advice already given, don't take the cat5 cable in and out unless you have to. Take the other end out. You can see from my pictures just how bad the trace pads lift. I lit the board from the bottom side so you can see the traces and how tiny and fragile the trace wires are.

1. So my advice if you have the cover off, hot glue the working ethernet port for extra strength.

2. Don't take the cable in and out unless you have too.

3. Order a spare DS anyway, because you don't want a $162.00 part causing an end to your robotics season.

4. Configure your spare ready to go just in case something bad happens at the competition and get it firmware upgraded and ready to drop in and go.

[Mr. Lim]

Originally Posted by Chris_Elston

We are not having a problem with static, but rather the port itself needs to be mounted to the board more firmly. What I saw was there are only two plastic post that are through holes to the bottom side of the board. When you insert the cat5 cable repeatedly, you seem to cause stress on these anchor posts. When these anchor posts give or break loose, your in trouble because then the connections in the back tip up and break off the pads on the surface mount.

We've also run into physical port damage through daily wear-and-tear as well. We've had traces lifted as well as the plastic posts wear and release from the board, leaving the connector to essentially float on the leads alone. Eventually the leads bend or lift the traces off the board.

Beyond connecting and disconnecting cables from the DS once or twice a day, there hasn't been any unusual or unreasonable stress on the connectors.

Curious to know if others are also encountering physical wear and tear issues with the DS ethernet ports? Some early indicators are the port having more freedom of movement in the up/down direction - or when you insert a cable, the entire port seems to flex backwards and upwards a bit.

[Travis Hoffman]

I wonder if anyone would take issue with combining something like this and something like this such that you'd NEVER have to remove the cable from your DS at a competition....

[Chris_Elston]

Originally Posted by Travis Hoffman

I wonder if anyone would take issue with combining something like this and something like this such that you'd NEVER have to remove the cable from your DS at a competition....

Nice FIX, Travis. I think the more you can prevent the cable coming in and out the better. Great idea.

[pitzoid]

For people having issues with blowing out and breaking RJ45 ports when tethered to the bot, this might help along with some of the other things being talked about here

Surge Protection

We were considering putting them on the field when the DS issues started, but they don't help the EMP events, the DSes still reset.... But it will help with tethered bots.....

[Peter Randall]

We configured a short extension for our ethernet ports after blowing one in Trenton in week one. We were asked to disconnect them from our DS when we were in competition last weekend in Pittsburgh. The rules clearly say nothing between DS and Field System. We blew another port and had to rely on a borrowed DS to compete. Not happy with the DS.

PGR

[Chris_Elston]

Originally Posted by pitzoid

For people having issues with blowing out and breaking RJ45 ports when tethered to the bot, this might help along with some of the other things being talked about here

Surge Protection

We were considering putting them on the field when the DS issues started, but they don't help the EMP events, the DSes still reset.... But it will help with tethered bots.....

Just placed an order for one at Newegg.com we'll try it out at Boilermaker and see how it works. Thanks for the tips!

[Travis Hoffman]

I've just been reminded that my earlier suggestion comes in a unified product called a "port saver". I should have recalled this, as I purchased a very similar crossover adapter from this site a while back.