Ignition Edge on EG5120: How to read data with Ignition Edge on the EG5120

Let's be clear: in today's industrial world, data is everything. But I've seen countless engineers face the same frustrating problem. You're on the factory floor, a critical machine is acting up, and the data you need to diagnose the problem is locked away inside a PLC, accessible only through some proprietary software or a complex SCADA system. It's an information silo, right where you need clarity the most. What if you could tap into that data stream and put a live dashboard right at the machine's location, without needing a massive server or a complex cloud setup?

That’s exactly the problem we're solving today. We're pairing the powerful Ignition Edge on EG5120, a true Industrial Edge Computing Gateway, to do something incredibly practical: grab data from one of the most common industrial protocols on the planet, Modbus TCP, and display it locally. This isn't just about connecting wires; it's about empowering immediate, on-site decision-making. Forget data latency and cloud dependencies for a moment. We’re bringing the power of visualization right to the edge.

Before we dive into the nitty-gritty, let's set the scene. For this walkthrough, I'm assuming you've already got Inductive Automation's Ignition Edge installed and commissioned on your Robustel EG5120. You’ve gone through the initial setup, created your admin user, and you can access the Ignition Gateway web interface. This combination is key because the EG5120 isn't just a router; it's a powerful computing platform designed for exactly these kinds of edge applications. It has the processing power to run Ignition Edge smoothly while handling its other networking duties.

You'll also need a Modbus TCP device to talk to. For this guide, I'm using a simple PC-based simulator, but the steps are identical for a real PLC, power meter, or any other Modbus TCP-enabled hardware on your network. Ready? Let's get that data flowing.

The real 'aha!' moment for many engineers isn't just seeing a complex protocol get simplified; it's realizing how quickly you can do it. Ignition Edge comes packed with an incredible library of drivers, and the Modbus one is a workhorse.

First, we need to tell Ignition where to find our Modbus device.

1. Log into your Ignition Gateway web interface (usually at http://:8088).
2. Navigate to the Config section on the left-hand menu, then scroll down to OPC UA Server > Devices.
3. Click on the link to "Create new Device..." and from the list, select the Modbus TCP driver. You'll see drivers for everything from Allen-Bradley to Siemens here, which is a testament to the platform's flexibility.
4. On the configuration page, you only need to set a few key things:

• Name: Give it a logical name, like Modbus_Power_Meter.
• Hostname: Enter the IP address of your Modbus TCP device.
• Port: Leave this as 502, the standard Modbus TCP port, unless you have a specific reason to change it.

5. Click "Create New Device." After a moment, the status should flip from "Connecting" to "Connected." It's that simple. You've just established a live data connection from your Ignition Edge on EG5120 to your field device.

Now that the connection is live, how do you actually see the data? You don't have to manually map every single register. We'll create Ignition Tags, which are like internal memory locations that hold the live values from our device.

1. Launch the Designer: Open the Ignition Designer Launcher on your PC and log into your EG5120's gateway.
2. Browse OPC Tags: In the bottom-left panel, you'll see the "OPC Tag Browser." Navigate through Ignition OPC UA Server > Devices > and find the device you just created (e.g., Modbus_Power_Meter).
3. Drag and Drop: Here's the magic. Expand your device to see the available registers. Find the one you want to monitor, click on it, drag it over to the "Tag Browser" panel, and release the mouse.
4. Done. You've just created a live Ignition Tag. It will now continuously poll the device for its current value. You can see the value update in real-time right there in the Tag Browser. This is a crucial step when using Ignition Edge on EG5120 for any data project.

Okay, seeing data in a list is cool for an engineer, but it's not very useful for an operator on the floor. Let's build that mini-dashboard we talked about using the Ignition Vision module. This entire process happens within the Designer.

In the Project Browser (top left), right-click on Vision > Windows and select New Window. Give it a name, like "Main_Overview," and click "Create Window." You now have a blank canvas to work on.

This is where your local HMI comes alive.

• Add a Component: From the Component Palette on the right, find the "Display" section and drag a Numeric Label component onto your blank window. This will be used to display our live value.
• Bind the Data: Select the Numeric Label you just added. In the Property Editor (bottom-right), find the "Value" property. To its right, you'll see a small chain-link icon. Click it.
• Link the Tag: A new window will pop up. Select the "Tag" binding type, and then navigate to the Ignition Tag you created in the previous step (e.g., [default]Modbus_Power_Meter/HR1). Click OK.

Instantly, you'll see the component on your screen display the live, real-time value from your Modbus device. You've just built a functional, live HMI that runs directly on your Ignition Edge on EG5120 setup. No cloud, no external servers, just pure edge intelligence.

Now, stop and think about what you just accomplished. With a few clicks, you tapped into an industrial device, created a live data point, and built a visualization for it. While we used Modbus TCP, the process for connecting to a Siemens S7, an Allen-Bradley PLC, or an OPC UA server is nearly identical. That's the power of this platform. The Ignition Edge on EG5120 solution isn't a one-trick pony; it's a universal translator and visualization tool for the industrial edge. It breaks down those data silos, one device at a time.