Global TMW:
Login  |  Register          Free Newsletter Subscription
Subscribe
Email
Print
Reprint
Learn RSS

Test for the digital battlefield at Harris RF Communications

Test Engineer of the Year John Gmitter manages a team charged with developing test stations that support his company’s high-volume manufacturing of tactical communications equipment.

Rick Nelson, Chief Editor -- Test & Measurement World, 3/1/2007

In our September 2006 issue, we profiled the accomplishments of six outstanding test engineers from various industries, and we asked our readers to vote for the Test Engineer of the Year. Your choice? John Gmitter of Harris RF Communications.

As part of his award, John has designated Monroe Community College to receive a $30,000 engineering grant, courtesy of award sponsors Agilent Technologies, Keithley Instruments, and National Instruments.


2007 AWARDS:
Test Engineer of the Year
Test Product of the Year
Test of Time Award

Overview of Awards Program

READ OTHER MARCH ARTICLES: 
Contents, March 2007

ROCHESTER, NY—Team sports are a natural fit for Test Engineer of the Year John Gmitter, whose college baseball program competed with his engineering course work as he earned his first college degree. His teamwork skills serve him well at Harris RF Communications, where he was charged with taking control of a diverse group of engineers to upgrade Harris’s test capabilities to keep up with ever-increasing production volumes for the company’s products.

Those products include the Falcon II series of complete tactical vehicular, base-station, and handheld communications systems. Combined with the Harris RF-6010 Tactical Network Access Hub, the radios form the basis of the Harris Tactical Network, which speeds critical voice, data, and position information to and from the digital battlefield, allowing radio operators to send and receive phone calls and enabling radio outstations to have wireless IP connectivity.

Navy experience

It was his experience with Harris communications products as an aviation technician in the US Navy that led Gmitter to seek employment with the company. He served in the Navy for four years, he said, where his duties included working on F-14 Tomcats onboard the USS Constellation.

“In my last deployment in the Navy,” Gmitter explained, “I was troubleshooting a station that we used to test the black boxes in the planes, and I had to call Harris customer support”—his first contact with the company. When the Rochester native left the Navy in 1999, it seemed natural to him to apply to Harris.

As for the Navy service itself, that also came naturally: “My father and my father’s father were both in the Navy, and I had heard lots of stories about military life.” On obtaining his degree in electrical engineering, he was drawn toward enlisting. “I figured, if I don’t do it now, I will never do it. And it was a fantastic, outstanding experience. It was hard work, but I really enjoyed it.”

Test Engineer of the Year John Gmitter deploys a production test station at Harris RF Communi-cations’ new Carlson Road facility. Courtesy of Harris RF Communications.

Before joining the Navy, Gmitter earned two degrees. A long-time interest in technology prompted him to take engineering courses at Monroe Community College, but that’s one time where his teamwork got him into trouble. “One of my profs told me right when I signed up for his class, 'Oh, you’re a baseball player. If you go on the spring trip, you will fail my class, I guarantee it.’”

Gmitter was unconvinced. “I said to myself, that really doesn’t sound right—I think I can handle it. So, I went with the team on the spring trip and when I came back, sure enough—he gave me a failing grade—because I’d missed some labs and classes.”

Gmitter had plenty of credits to graduate from MCC at that point, but not enough credits for a degree in engineering. That prompted him to enroll in Utica Tech, where he redoubled his engineering efforts and earned his bachelor’s degree in electrical engineering.

Becoming a test engineer at Harris

With his college and Navy experience behind him, Gmitter found himself employed as a TE 1 (for test engineer level 1) in product support at Harris, working with Falcon I systems. He was promoted to TE 2 level and became the lead engineer responsible for deployment of a test cell for the new Falcon II.

At that time, Harris had recently acquired a new building—the Carlson Road building—that would allow it to expand its manufacturing capacity to meet the growing demand for Falcon and other Harris products.

Engineering manager Kenneth Parfitt recognized the need to revamp the Harris RF Communications test strategy to accommodate higher production volumes.

“We used to be a low-volume, niche, very customer-oriented division” known for quality and fast turnaround, Gmitter said. “But we started to produce in higher volumes, and as a test organization, we realized the deficiency of our standard platform, which was basically a one-at-a-time test system. We might be asked to test 10 products per day now on 10 test stations, but in six months, we might be asked to do 100 per day, requiring 100 test stations.”

It became clear to engineering managers Ken Parfitt and Joseph Zingo that—to effectively use the manufacturing space the company had acquired—it would be necessary to develop a test strategy that would allow for faster and more flexible deployment of test stations. They promoted Gmitter to TE 3 and charged him with heading up the new-product-introduction (NPI) test group’s efforts.

Gmitter and his team faced not only the challenge of expanding capacity. They also had to accommodate new modulation schemes and higher frequencies (up to 2 GHz on the forthcoming Falcon III vs. 512 MHz on the Falcon II multiband version). In addition, they had to find replacements for obsolete instruments and preserve 10 years worth of software-development effort, all while developing small-footprint test stations that wouldn’t take up much production-floor space.

Essentially a player-manager in the process, Gmitter applied his knowledge of RF testing hardware and software architectures and leadership skills to build consensus among the NPI team and deliver upgraded test stations, all within the tight timelines. He found no shortage of talent within the eight- to 10-member NPI test group. “We had a lot of type A personalities in one room who had a lot of great ideas. It could get tense and political,” he said, with respect to whose idea would prevail. “When I came over, it was my job to oversee the overall direction, get these guys to come together, and be responsible for the final decisions.”

Developing a software strategy

The software strategy the team came together on is based on National Instruments’ TestStand 3.1. “We had been using LabView for eight to 10 years and had looked at TestStand, but so far hadn’t had a need for it. But after further review, we decided that, well, we could really start to take advantage of some of its key features, such as resource allocation, instrument locking, and parallel autoscheduling.”

Engineering manager Joseph Zingo charged Gmitter with the responsibility of guiding and focusing the talented engineers on the NPI test team.

Choosing TestStand was only the beginning, however: “TestStand and LabView could do so many things that it was almost paralyzing.” The challenge, Gmitter said, was basically “making a decision and putting a stake in the ground,” defining what functions to implement immediately and what ones to save for later.

One goal of the team was to leverage its old software structure while eliminating some of the drawbacks. “For example, our instrument base structure had a handler and a driver; the top level was a handler, and every piece inside that handler had to be present on the hard drive and be executable, so it was really hard to get a station set up. You could be troubleshooting some digital I/O function that you would never use on the station, but if you didn’t make it work, you couldn’t use anything else. It was really difficult for someone to set up a station just to do a simple thing,” he said.

“So, we decided we were going to change our driver-handler structure to a true object-oriented class-based structure.” To that end, the team enlisted the help of an Endevo OOP wizard, which Gmitter described as a speedy class-based generation tool. The object-oriented programming approach enabled the team to detach functions from the   lower-level software so they could execute only the functions they needed. “Everything didn’t need to be present and executable, so if you had a simple function that you wanted to deploy in a half hour, you could do it pretty easily.”

The Harris NPI test team based its test-station architecture on the PXI platform, which offers sufficient flexibility to accommodate other types of instruments. Courtesy of Harris RF Communications.

The team employed XML to describe test assets. “So that the test software knows what’s connected to it, we implemented XML-based station-description documents. The station initialization software could read the XML files and say, 'OK, I know you have two PXI audio analyzers and a GPIB signal generator, and I know what the addresses are.’ This allows our stations to be rapidly reconfigured or changed or edited in some way.” To control source code during software editing, the team relies on Microsoft Visual SourceSafe.

PXI-based hardware

As for hardware, Gmitter’s team focused on a PXI platform that allowed sufficient flexibility to accommodate legacy GPIB instruments as well as future USB and LXI instruments, should the need arise. A typical test station now might include NI PXI digitizers, Aeroflex PXI signal generators, Pickering PXI switches, Agilent GPIB signal analyzers, Anritsu GPIB RF power meters, Virginia Panel mass-interconnect hardware, and Cytec GPIB switching systems.

Commenting on PXI, Gmitter said, “I like what the PXI chassis does for us. It’s overkill to begin with, but it always provides the ability for production to say, 'we were doing two a day but now we want to do 20 a day.’ If you have a chassis there with spare slots and you designed your station such that it takes advantage of parallel processing, autoscheduling, and resource allocation, you can say, 'Station, I just plugged in two more audio analyzers,’ or 'I put in two more signal generators. Please recognize them and make use of them.’”

PXI switch cards from Pickering Interfaces add flexibility to Harris test stations.

The trend for Gmitter’s team is to adopt more PXI instruments as they become available—sometimes out of necessity. For example, he said, “Agilent discontinued its entire 89xx series of instruments. Fortunately, we found we could replace them with the NI PXI-5421 arbitrary waveform generator, PXI-4461 audio analyzer, and PXI-5660 modulation analyzer.” Such substitutions aren’t always ideal, he said, but satisfactory results can be had by making careful tradeoffs. For a spectrum analyzer, for example, such tradeoffs might involve resolution bandwidth, measurement speed, and dynamic range.

When asked if any one factor contributed most heavily to the project success, Gmitter said, “Teamwork. I just provided the direction and some of the technical expertise.” As for winning the Test Engineer of the Year award, he said, “This is a credit not only to me but to all the engineers and managers at Harris that made the project possible. This was a tremendous team effort.”

Email
Print
Reprint
Learn RSS

Talkback

We would love your feedback!

Post a comment

» VIEW ALL TALKBACK THREADS

Related Content

Related Content

 

By This Author

Sponsored Links



 
Advertisement
SPONSORED LINKS

More Content

  • Blogs
  • Podcasts

Blogs

  • Martin Rowe
    Rowe's and Columns

    November 5, 2008
    Technical articles retain value
    I'm always amazed, and pleased, when I hear from readers who still find value in old T&MW articl...
    More
  • Martin Rowe
    Rowe's and Columns

    October 31, 2008
    Measurement proverbs
    The other day, I received some measurement proverbs that I'd like to share. The proverbs come from K...
    More
  • » VIEW ALL BLOGS RSS

Podcasts

Advertisements





NEWSLETTERS
Click on a title below to learn more.

Test Industry News (3 Times Per Month)
Machine-Vision & Inspection (Monthly)
Communications Test (Monthly)
Design, Test & Yield (Monthly)
Automotive, Aerospace & Defense (Monthly)
Instrumentation (Monthly)
Resource Center E-Alert (Monthly)
©2008 Reed Business Information, a division of Reed Elsevier Inc. All rights reserved.
Use of this Web site is subject to its Terms of Use | Privacy Policy
Please visit these other Reed Business sites