Simulating a 4-20mA Signal in a Pinch: A Field Guide for Control Engineers

No Signal Generator? Here's How to Fake a 4-20mA Signal (When You Have to)

If you've ever needed to test a PLC input, validate an HMI scaling, or troubleshoot a loop-powered transmitter without a proper signal generator, you know the panic. I've been there – scrambling in a control panel at 4 PM on a Friday, with a customer waiting on a calibration certificate. The question is never can you simulate a 4-20mA signal, but how accurately and how fast – and that depends entirely on what gear you have on hand.

This was accurate as of early 2025, but field tools and firmware updates change fast, so verify current specs if you're budgeting for a new solution.

Here's the thing: there's no one-size-fits-all method. What works for a quick diagnostic won't cut it for a formal loop check. So I'll walk through three common scenarios – you decide which fits your situation best.

Scenario A: You Have a Phoenix Contact PLC or HMI in the Loop

If you've got a PLCnext controller or a Phoenix Contact HMI (like the Visu+ or WP series) on the network, you can often generate a 4-20mA signal directly from an analog output channel – no extra hardware needed. I've done this a ton of times when a contractor left their calibrator at the shop.

You just need to write a simple function block or script that outputs a fixed value (e.g., 50% = 12 mA) and map it to an analog output module. Granted, this takes a few minutes of programming, and you lose the ability to sweep the signal live. But for a quick go/no-go test of an input channel, it's fast and free.

The catch? Most analog output modules have a minimum step size. For Phoenix Contact's I/O modules, the resolution is typically 12-bit (about 4 µA per step on a 4-20mA range). That's good enough for 95% of troubleshooting, but not for calibrating a high-accuracy transmitter. My experience is based on about 200 mid-range orders for process plants; if you're working on lab-grade instrumentation, your tolerance requirements are way stricter.

Scenario B: You Have a Power Supply (Like a Phoenix Contact UPS) and a Resistor

This is the classic field trick. Grab a 24V DC power supply – a Phoenix Contact UPS or even a basic QUINT power supply works fine – and a precision resistor. For a 4-20mA loop, you can produce a known current by choosing the right resistor value.

Want 12 mA (50% of span)? Ohm's law says: R = V / I. If your supply is exactly 24V, a 2000-ohm resistor gives you 12 mA. In reality, no resistor is perfect, and your supply might sag. So you build a simple series circuit with a 250-ohm resistor (common for converting 4-20mA to 1-5V) and measure the actual current with a good multimeter.

Here's where it gets tricky: the resistor's tolerance and temperature coefficient matter. A cheap 5% carbon film resistor can drift 10% when it heats up. I always use metal film resistors (1% or better). Last quarter, I had to simulate a 4-20mA for an emergency HMI calibration on a Phoenix Contact breaker monitoring system. I paired a 250-ohm 1% resistor with a QUINT UPS, measured 8.02 mA instead of the expected 8.00 mA – close enough to verify the HMI scaling was correct.

But here's the honest truth: this method is only accurate to about ±2-3%. If you need better than 0.5% accuracy, you need a proper signal source.

Scenario C: You Have Almost Nothing – Just a Battery and a Potentiometer

This is the emergency backup for when you're truly in the field with no test gear. Grab a 9V battery, a 1k-ohm trim pot, and a multimeter. Wire the pot as a variable resistor in series with the battery, and adjust until you see the current you want on the meter. It's crude, unstable, and the battery drains fast, but it works for a one-time sanity check.

I once used this trick to simulate a 4-20mA signal to a remote Phoenix Contact HMI that was showing a stuck reading. The vendor on the phone told me to inject a known signal at the field device. With no calibrator in sight, I built the battery-and-pot circuit in ten minutes. The HMI responded properly – meaning the issue was in the sensor, not the controller. That saved us a costly control cabinet swap.

The downside is obvious: the signal drifts as the battery voltage drops, and you can't maintain a steady current for more than a few minutes. So use this only for a quick pass/fail test.

How to Decide Which Method Is Right for You

Ask yourself three questions:

1. How accurate do you need the signal to be? For troubleshooting a missing input, ±5% is fine. For calibrating a transmitter or loop-powered device, aim for ±0.1% – that means scenario A or a dedicated calibrator.
2. How much time do you have? If you can spare 10 minutes to write logic, scenario A is clean. If you need a signal in 30 seconds, the resistor trick (scenario B) wins.
3. What's at stake? A wrong signal during a shutdown test could cause a false trip. For safety-related loops, don't wing it – call a colleague with a proper 4-20mA simulator, or order one overnight.

To be fair, none of these methods replace a proper calibrator like the Phoenix Contact MINI Analog Pro signal generator. But knowing your limits is part of being professional. The vendor who says, "This isn't our strength – here's who does it better" earns my trust. Similarly, knowing when to use a resistor and when to buy a $500 calibrator is a mark of experience.

My experience is based on about 200 mid-range orders with domestic vendors. If you're working in oil & gas or pharmaceutical, your calibration standards will be way tighter – so treat these shortcuts as last-resort diagnostics, not production tools.

Note: Pricing for a reliable signal generator (e.g., Phoenix Contact MINI Analog Pro) was around $600-850 as of Q4 2024. Market moves fast, so verify current rates before budgeting.