Extreme Design: When radar failure at 12,000 feet is not an option

(Editor's note: this is the latest in our on-going Extreme Design series, where a single design or test objective—not low cost—dominates the engineering challenge. To see all the previous entries in the Extreme Design series, click here.)

High above the Fryingpan Valley in Colorado looms Red Table Mountain, a massive 18-mile long sandstone ridge protruding sharply from the valley below. The mountain top is accessible by a 4-wheel drive vehicle just two months of the year, a bumpy ride up a single lane road so rough it can wear out the wheels of an army jeep in a single trip. The rest of the year, the only way to the top is by helicopter. Here, at the clear altitude of 12,000 feet, FAA maintains a radar site for guiding aircraft over the Continental Divide. It is arguably one of the worst locations for a radar failure to happen, Figure 1.

Most radar sites are operated on commercial power, and are backed up by a generator with a Power Conditioning System (PCS). The PCS supports the Critical Radar Loads during power bumps, power spikes, voltage sags and transitions from commercial to engine-generated power. The static switch and the PCS unit have to make the transition in less than 4 milliseconds to ensure uninterrupted function of the beacon, radio transmitters and other radar equipment.

The PCS at the Red Table Mountain site had a frustrating problem: PCS batteries were supposed to last up to 4 years, but they only lasted a year to year and a half. The frequent replacement of the batteries was costly and time-consuming. The site personnel suspected that the PCS unit was going to batteries frequently, without the engine sensing a power failure. It was not clear why this would be happening, so they requested assistance in identifying the problem.

The person sent to solve the puzzle was Jerry Taylor, an engineering technician with the FAA’s Western Service Area Technical Support Center in Denver, Figure 2. Taylor had worked as a resident engineer for a number of years, installing Power Systems all over the United States, including Alaska and Guam. He was often called to assist facilities in solving critical electrical issues.

Before heading to Red Table, Taylor had asked for two PQubes to be delivered to the station. The PQube (www.pqube.com) is a tiny but highly accurate instrument for monitoring and recording power quality, Figure 3. Taylor knew it had the unique ability to automatically email all data, including waveform captures, to anyone anywhere. It could also email daily, weekly, and monthly reports about critical power parameters, including digital and analog data.

Taylor had not used the PQube before but a colleague at the FAA Training Academy in Oklahoma City had recommended the instrument. Engineers there used the PQube to verify 4 millisecond static switch transfers, which other instruments could not always capture. The colleague described the PQube as a plug-and-play device that requires minimal setup—just input power and a few CTs to begin monitoring and recording the system’s voltage and current.

Unlike the bulky and expensive portable testing equipment technicians typically brought with them to test for problems, the PQube seemed like the near-ideal instrument to send to Red Table. Technicians could have several for the price of their regular testing equipment, and could receive the data right away and anywhere.

Taylor’s intention was to leave the two PQubes at the site to collect data on the commercial incoming power, the transfer time to the engine generator during power failure, the time the generator was on, the quality of generator power, the transfer back to commercial power, the PCS input and output power, and the transfer times of the PCS. Two PQubes could do all that, and provide the digital, analog and waveform data in real time. By leaving them connected to the equipment over a period of time, Taylor hoped to gather enough information to see if any events or patterns appeared—something he couldn’t do with a portable analyzer in a day.

When he arrived, Taylor found that just one PQube had been sent, so he installed it on the PCS input. He also connected two temperature/humidity probes that had been purchased with the unit because he felt the room might be too hot for the PCS and batteries. He installed one probe in the PCS room and one in an adjacent room, using an extension cable. As soon as it was hooked up, the PQube began monitoring and recording power data. Taylor returned to his duty station.

Two weeks later, the site technicians forwarded to Taylor the data from the PQube’s SD card (.HTM summaries and .GIF and .CSV files he could open on any computer). The evidence was incontrovertible: In just two weeks, the PQube had detectedand recorded 30 power-quality events, noting the exact type, depth and duration of each event (Figure 4). The PCS interpreted all of these deviations from normal voltage as power outages. The system switched from commercial to battery power every single time, then switched back in a few seconds when it did not detect continuous outage.

The PQube data revealed a second problem. To prevent the battery from freezing, employees were careful to keep the door of the PCS room shut all the time—raising temperature in the room above 100° Fahrenheit (38° C)! Not only was the battery working overtime, it was working in an extremely overheated environment, well above its maximum rating.

Taylor kept digging into the data. The shape of the waveform, Figure 5, captured during the transfers alerted him to the possibility of bad capacitors in the PCS module—something the PCS manufacturer was quick to address. Graphs like these, generated by the PQube directly, can be emailed as attachments and can be viewed in any picture viewer program—no special software is required.

Armed with the information from the PQube, the engineers at the site began to implement small but important changes to reduce wear on the PCS unit. They installed a filtering system to improve ride-through capability, and they tightened the timing of the transfer based on the voltage sag information from the PQube. They also called the utility company and asked it to address the voltage sags on its end. Finally, they installed an exhaust fan and a thermostat in the PCS room, to maintain optimal temperature and humidity.

The Red Table technicians then followed up on Taylor’s original intention and installed a second PQube permanently on the output side of the PCS. This allows them to compare input and output data to make sure the PCS continues to function properly.

“The technicians do not want to give the PQubes back because they work so well and are so easy to use,” says Taylor about his experience with taking PQubes around different sites, Figure 6. “I tell them next time they talk about buying an expensive monitor to instead buy ten PQubes so all the technicians have them.”

The cost of a PQube (right-side of) is a tiny fraction of the cost of a sophisticated backup system, and the knowledge and peace of mind it provides are absolutely priceless, says Taylor.

“What the PQube allows us to do is be proactive in how we deal with power problems,” he adds. “It’s like magic glasses: Suddenly you can see how much current you are drawing, what the voltage is doing, and see it as things are happening; the whole system becomes alive.”

About the author

Ani Dimusheva is a Marketing Communications Specialist at Power Standards Lab (PSL), Alameda, CA. (Jerry Taylor can be reached at jerry.taylor@faa.gov.)

Editor's note: Liked this? Want more?

If you are interested in "power" issues such as components; efficiency; thermal concerns; AC/DC and DC/DC supply topologies; batteries; supply ICs; complete supplies; single- and multi-rail management; and supply monitoring: then go to the Power Management Designlinehome page here for the latest in design, technology, trends, products, and news. Also, sign up for our weekly Power Management Designline Newsletter here.

Thank you for your comments. The article I wrote clearly discusses a product but my intent was to write a story that would be interesting, informative, and possibly helpful to other people in Mr. Taylor's situation.
My apologies to those not familiar with some of the acronyms, it's always a tough call whether to use them or not in technical writing. As far as the Jeep statement, I was quoting Mr Taylor, who I'm sure has driven a jeep up there.

As manager and editor of this site, I made the judgment call that this was a good story for our audience. Yes, it does promote a product, but it is also interesting and problem solving, talks about a tough situation and what was done about it. It went well beyond the usual "let me tell you about our product and why it is great."
As for advertising, this company has never advertised with us, nor do I expect them to do so ever—it's not in the picture at all. And we have many companies who advertise but we never have articles from or about, and vice versa.
As for CT: it's always a tough call, which things to spell out. Some readers want everything spelled out, but many are annoyed when you do that. Either way—someone will be upset!

CT = Current Transformer, standard AC current measuring device, see
http://en.wikipedia.org/wiki/Current_transformer
Yes this is an advertising piece, pushing the company's products, but as a case study it's instructive and they DO seem to have a good product to push.

I must say that this was a very constructive and informative!
I would like to thank you for taking the time to write
this post and share this with us all!
Thanks,
http://www.comprehensivebackgroundcheck.info