Subscribe to EDN
RSS
Reprints/License
Print
Email
PDF Version

Murphy's Law applies even under water

While working on a hydroelectric feed tunnel through the Andes in Peru, one engineer learns that Murphy’s Law is relevant when it comes to a manipulator and a mountain.

David Jeffrey, Marine Applied Research and Exploration -- EDN, November 11, 2011

MurphyOne of the most ambitious projects I worked on was the inspection of a hydroelectric feed tunnel through the Andes in Peru. The principal tool was a specially-designed ROV (Remotely Operated Underwater Vehicle) which swam through the tunnel taking measurements. All ROVs function in much the same way. They are connected via an electrical umbilical, which carries power and control signals from the surface. There, the umbilical connects to the control console where the operator has joysticks to drive the vehicle and a video monitor to see the image it sends back. (Think grown-up video game.) ROVs often carry more than one video camera, and a selection of other accessories—depth gauge, compass, lights, sonars, etc. Most have an umbilical a few hundred, or thousand, feet long. Because of the tunnel length, this one was 10km in length.

Amongst the accessories was a manipulator arm. It was controlled by an RS232 serial link. Because of a drop-dead development time, we arrived in Peru before the final testing of the manipulator. However, over a test cable it had performed fine and we didn’t anticipate any problems. Classic Murphy’s Law. I now know better—get Murphy underwater and he goes on steroids.

The only difference (we thought) between the test cable and the umbilical was that in the latter the serial link was carried over an optic fiber. The main ROV control used an identical link which performed flawlessly during trials. However, when we tried the manipulator, it refused to work. I could see the RS232 signals as they left the optical converter in the ROV, but the arm didn’t respond. Looking at the manipulator electronics, I found that the TTL level output from the RS232 level shifter didn’t move from ground. Clearly the level shifter chip was faulty.

Tales From The Cube Tell us your Tale contest voting image
This Tale is a runner-up in EDN’s Tales from the Cube: Tell Us Your Tale Contest, sponsored by Tektronix. Read the other finalists’ entries here.

So I replaced it—but with the same results. The output seemed nailed to ground. I checked for a short in the PCB, but the trace was fine. In desperation, I shut the entire system down so I could watch it come to life. I found a curious phenomenon. As the first commands were sent to the manipulator, I could see a few good pulses on the “bad” pin, but after that, nothing. This suggested another explanation. Most microcontroller I/O pins can be set as input or output. Suppose the microcontroller was changing the pin in question to output mode and setting it low? That would explain what we were seeing. When two TTL logic signals argue, the low side always wins.

The manipulator was designed and manufactured in Scotland. I was on top of a mountain in Peru, with a very shaky telephone link and a significant time difference. But desperate times require desperate measures, so I called the Scottish company and, as luck would have it, managed to speak to one of the engineers familiar with the code. I asked if he could provide a small software patch that would force the “bad” pin to input mode on every program cycle, about 10 times a second. After a few minutes he called back with a single line of code for us. Fortunately I had an EPROM eraser and programmer with me, and was able to insert the code with some difficulty. (I did not have a compiler or other aid—we had to work editing the raw hex.)

Read more Tales from the CubeOn testing we at last saw some activity from the arm. Clearly we were on the right path. Again I spoke to my engineer in Scotland, explaining what had happened and asking for a more comprehensive code revision. He came back with a version he said should fix the problem. Great, I thought—but how can we get it here? “It” was four pages of hex code that we would have to get into the programmer somehow. Finally, Scotland faxed it to our office in Lima, where someone read it to us over the phone—very slowly and carefully. At the end I took the four pages of handwritten hex characters and, again very carefully, entered them into the EPROM programmer. Eventually, we were done. The EPROM was put back in the manipulator, and the system powered up. With all of us holding our breaths, I pushed the manipulator joystick. And the arm worked!

We never did find out what caused the problem in the first place. It was probably an RS232 timing issue between the fiber optic output and the microcontroller input, and we didn’t have time to do any digging. But we had a solution and that was enough.


David Jeffrey is an electronics engineer who has specialized in applications where water plays an important role, from wave power devices to robotic submarines.
RSS
Reprints/License
Print
Email
PDF Version
Canon Resource Center

Featured Company


Most Recent Resources

Advertisement
Related Content

No related content found.

  • 0 rated items found.
Advertisement

KNOWLEDGE CENTER

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)
Featured Job On
Scroll for More Jobs
Advertisement
About EDN   |   Site Map   |   Contact Us   |   Subscription   |   RSS
© 2012 UBM Electronics. All rights reserved.
Use of this Web site is subject to its Terms of Use | Privacy Policy

Please visit these other UBM Canon sites

UBM Canon | Design News | Test & Measurement World | Packaging Digest | EDN | Qmed | Pharmalive | Appliance Magazine | Plastics Today | Powder Bulk Solids | Canon Trade Shows