Voices: Rezabek

Wireless Smart Devices: Unhand Me, Handheld!

Handhelds: What's Not to Love?

By John Rezabek

Where's the HART communicator? A little crisis ensued when a multiplexer channel became finicky about detecting a new HART transmitter; we needed to configure the proper range, signal conditioning and tag number. We've grown accustomed to interacting with "smart" devices—both fieldbus and HART 4-20 mA—from the comfort of the engineering or asset management interface. Our head technician stopped sending in our old 275 HART communicators for updates years ago. As with many of the tools of yore, not only do we forget how to operate them, but we also forget where we put them. "I hope the batteries aren't dead," I thought.

Eventually, the 275 turned up, and we even remembered how to store the configuration from one of its triple-redundant siblings and blast it into the new device. Whew! I guess we better take care of those old 275s.

Then a valve came back from vendor's shop with a brand-new, fieldbus-capable DVC6000 positioner on it. Now, every one of the hundreds of devices we've connected to our DCS has dutifully appeared in the engineering interface before, but this positioner didn't. Could there have been a mix-up? Was it actually a HART device? No, physical inspection confirmed it was Foundation fieldbus (FF).

The vendor suggested we might want to check the address. Since our DCS couldn't "see" the device, we didn't know how to do that. We needed—a handheld. Since our 275s don't speak FF, we had to borrow a 375 from a neighbor. Sure enough, the address had been set at the vendor's shop to "123," which happens to be an address where the DCS interface card (the H1 link master) doesn't knock. The 375 allowed us to set a compatible address, and commissioning resumed without issue.

Also Read "Getting the Most from the HART Handheld Device"

More recently, we wanted to add a new WirelessHART transmitter to our existing WiHART network. We'd set up the original dozens of devices in the comfort of the shop, powering up each device individually and configuring it when it appeared in the browser interface. But now the new transmitter didn't want to join its siblings on the original network. The new device needed to be configured with a compatible network ID and a join key before it could be seen through our gateway. Drat! I believe I need a handheld! This time we had to find a neighbor with a 475, the latest incarnation of Emerson's smart communicators. Lucky I have nice neighbors.

The other routine function for which handhelds prove hard to beat is in-place calibration. It's a challenge to drag a dead-weight tester around in the field, so if you don't want to bring every device into the shop for calibration, you'll likely need a handheld. Calibrators from Fluke, Meriam and GE (Druck) have innate HART capability, and Beamex also includes connectivity for fieldbus.

There's also a cadre of communicators that enable "BYOD." If you have Windows notebooks or tablets that can be safely used in your operating areas, adapters for HART and FF are available, as well as custom software and more standardized FDT-DTM applications. I have a feeling iOS and Android apps for interacting with smart devices are in the not-distant future.

Handhelds: what's not to love? For one thing, they're an agent of database entropy, increasing fragmentation, randomness and undetected/undocumented configuration changes and errors. Without a centrally maintained database, a team of technicians can cause your management-of-change some stress.  Conceivably, any organization can develop the procedures and discipline to track instrument changes, but you'd like a method that relies less on the multiple keystrokes of a random instrument specialist on a HART communicator. If only handhelds connected directly to a single host database.
Even with their disadvantages, I can't seem to shake loose of handhelds. It looks like they'll have a "hand" in my budget for many years to come. 

 

More from this voice

Title

Everyone, Do Your Own Math

The Incremental Costs to Add Spurs to These Fieldbus Segments make WirelessHART at Best a Break-Even Option in Many Circumstances

08/30/2010

Failed Bus Blame Game

If You Allow Yourself to Be Dour, Defeated and Critical of Your Selected System, You Could Be Headed for Disaster

04/09/2010

Fieldbus Flavor of the Month

We May Be Missing Real Innovation in Our Field. Lets Adopt the Latest Controls or Instrument or Network Technology Flavor

01/03/2013

Fieldbus for Safety Instrumented Functions

FF-SIF Transcends the Limitations of Conventional Safety System Design by Introducing New and Innovative Ways of Thinking About Safety

06/12/2008

Fieldbus is Dead! Long Live Fieldbus!

The Competing Communications Technology That Presumably Will Replace All These Buses, Including Process Fieldbuses, Is Ethernet

05/02/2013

Fieldbus on a Shoestring

Use the Wire You Have. Unless You’re Really Challenging the Limits of the Physical Layer, Ordinary Twisted/Shielded Pair Will Work Reliably

01/12/2009

Fieldbus Savings the Same in Dollars or Yuan

There's Been Too Much Hype About the Cost Savings of Fieldbus. The Same Thing Can Be Done With Remote I/O

06/11/2013

Fieldbus-Where's the Love?

How Does Fieldbus Bring Flux and Uncertainty Where There Used to Be Order?

02/14/2011

Fieldbus: Do Fence Me In!

Just Because You Can Put 12 Devices on Each Fieldbus Segment, Doesn't Mean You Should

01/14/2014

Fieldbus: Lion or Lamb?

Ways Fieldbus End Users Can Avoid Increasing Stress for Their EPC Consulting Firm

03/09/2011

Finally, Registered Hosts

"Compliant Host" Came to Be Because Users Were Seeking Objective Ways to Evaluate Different Hosts's Capabilities

07/13/2009

Finding Freebies in Fieldbus

Can We Use the Standard Deviation Method to Flag a Suspicious Measurement?

03/02/2009

Foolproof Fieldbus II

Sometimes Our Well-Intentioned Attempts to Make a System "Foolproof" Create as Many Hazards as We Were Aiming to Prevent

11/07/2013

How Can Incompatible DCS and Asset Management Suppliers Get Along?

One Throat to Choke: When a Site Has an Installed Base of Incompatible DCS and Asset Management Suppliers, It May Have to Revert to the Host's Offerings

09/04/2012

How's Your Fieldbus Resume?

What Kind of Qualifications Should You Be Displaying to Qualify for the Jobs That Are Available?

10/12/2009

Instrinsic Safety Obsolete Yet?

Like Most End Users, I Truly Value the Credibility and Security That Organizations Such as Factory Mutual, the Canadian Standards Association, CENELEC and Their Ilk Bring to the Devices We Use in Hazardous Environments. But Perhaps One Practice is Ready to Be Relegated to the ISA Museum of How We Used to Do Things. Here’s Why.

03/07/2008

Is Field-Based Control More Secure?

If We Hide Our Controls in Field Devices, Are We More Immune From the Infections of the Higher-Level Networks?

04/03/2013

Is Field-Based Control Really All That?

Recent Studies Shown That the Fieldbus-for-I/O-Only Approach Is Likely a Source of Compromised Performance and Unknown Latencies

02/02/2010

Is Fieldbus a Three-Beanie Copter Problem?

There Is Work Going on to Simplify Selecting and Designing Useful Fieldbus Applications. It Remains to Be Seen if We'll Ever Get to Fieldbus for Dummies

07/11/2013

Is Lick-'n-Stick Wireless the Future?

Wireless Networks Don't Come Cheap Nor Does Running Lengthy Wiring That Is Also Time Consumming. Are You Waiting on Standards Convergence or on the Right Application?

02/06/2012