Archive for category Communications

Why does my Honeywell UDC controller flash UNPLUG at me?

Posted by danstips in Ethernet, Honeywell, Installation, Loop Controllers, Troubleshooting on February 15, 2017

Honeywell UDC Controller.jpg

Honeywell UDC UNPLUG Error Message

People will fire up a new UDC 1/4 DIN loop controller, like a UDC2500 or UDC3200, and discover that the lower display periodically flashes an error code: UNPLUG. But what does it mean? Is something wrong?

A search of the pdf version of the manual hints that the Modbus Ethernet communications is involved:

The Ethernet status screen shows the network status of the Ethernet Link. This may be accessed either via Ethernet or via Infrared Communications. For example, if the Ethernet cable is unplugged, then the instrument cannot send up the EUNPLGED diagnostic message via Ethernet.

But the word UNPLUG is nowhere else in the manual.

Read the rest of this entry »

, , ,

2 Comments

How to Avoid Honeywell Process Instrument Explorer (PIE) Software Communication Errors

Posted by danstips in Analytical Measurement Devices, Communications, Configuration, Control, Loop Controllers, Process Automation Controllers, Serial, Software, Troubleshooting on August 26, 2016

Honeywell’s Process Instrument Explorer (PIE) configuration software used for configuring UDC controllers and the UDA analytical controller communicates with the instruments via RS-485, Ethernet, or Infrared (IR).

Since most newer PCs don’t ship with built-in serial ports to connect an IR adapter, you can use a USB-to-RS-232 converter, and then connect using the Actisys serial-to-infrared adapter (ACT-IR220L+). The USB converter will plug directly into your PC’s USB port, but install on a virtual COM port.

Here’s where it gets tricky: That COM port has to match the COM port used in PIE, and PIE doesn’t support ports above COM8.

Read the rest of this entry »

, , , , , , , , , , , , , , , , , , , ,

Leave a comment

Get More Combustion System Data into your PLC

Posted by danstips in Combustion, Communications, Flame Safeguard Controls, Flame Safety, Honeywell, Modbus on July 14, 2016

Written by: A.J. Piskor

Traditionally, combustion control panels have been living in a hard-wired world. More often than not, the status of a burner system is communicated by indicator lights on a Flame Safeguard (FSG) terminal.

With the increased use of Programmable Logic Controllers (PLCs) controlling all aspects of a combustion system, customers are demanding more information from the FSG, as many operators manage their systems from a centralized control room.

While some customers have traded in their indicator lights for relays with dry contacts that feed back into their PLC, other customers are looking to simplify the communication between the FSG and PLC, while extracting more information on the operation of their burner system.

Here, we will go over some examples of technologies that are available today, and how you can get the information you need to where you need it.

Read the rest of this entry »

, , , , , , , , , , , , , , , , , , , , , ,

Leave a comment

Changing the COM port for a USB HART modem in Pactware

Posted by danstips in Communications, Configuration, HART, Troubleshooting on November 4, 2015

Written by: Dan Weise

I couldn’t communicate with a HART device. The configuration software I was using, Pactware, thought the USB HART modem was on COM 3, while Windows’ Device Manager showed it was actually on COM 6.

COM Port Post

COM Port Post 2

To change the COM port in Pactware to COM 6, I right clicked COM 3 and selected Parameter:

Read the rest of this entry »

, , , , ,

1 Comment