Best RTU for a Demo Ignition (Easiest to bring into the GW)

Folks,

This is a bit of an odd request: I have worked before as the supervisor of an EMS Development Team before on a SCADA system that spanned the better part of 3 midwestern states, but I REALLY work in cybersecurity and particularly NERC CIP compliance.

I'm looking for the easiest RTU to bring into a small demo network. I really only want to let the Ignition GW see it... be able to turn something on and turn it off with an HMI. VERY small potatoes. Maybe something like:

  • A couple of the cheap MODBUS RTUs
  • A couple USB-to-485 adapters

That's what I don't know. Maybe there's a way better way?

I'm thinking of maybe a simple function, like a DC servo motor with an encoder to measure speed. So one RTU can turn it motor on and off and the other RTU can monitor rotations per minute... something like that. And also something visual (I can put a disk on the motor help people see it spinning).

One kinda like this:

It looks like this essentially. I'd love any and all feedback. With this basic layout, I am able to grant myself access and remove access to each piece granularly, take a flat network and put into the Purdue model at will, prevent lateral movement, etc.

But now, I want to add something more real-world than just a camera and a power switch.

The goal is really to demonstrate our micro-segmentation, secure remote access, and network cloaking technology - but everyone who sees my demo will see ignition featured prominently as well.

1 Like

Moxa IoLogik E1212, 8 dig in, 8 dig out, ModBus TCP.

Wire one of the outputs back to an input and configure it (in the moxa config) to pulse on off 1000mS. That gives you a heartbeat.

Connect a push button up to an input.

Connect one of the outputs to a relay, even one with an LED built into the socket.

E1240, E1241, if you want to play with analogue.

Very cool. That should do it. I guess I probably don't need two. Seems pointless, with 8 contacts... I'll get one on it's way. And it's a lot easier (for me) than converting to serial - last time I used RS485 was hand soldering DIN connectors to Kronos timeclocks for dialing up remote factory floors. :slight_smile: Anyway, I'll just modify my diagram slightly. Thank you! I'll post back how things look when I get it all configured.

I don't think I need to... This will simplify my demo AND since it's on the network, I can actually cloak it with BlastWave and bring it into its own cybersecurity micro-segment.

1 Like

Cool, if you want to write to the setpoint to dynamically change the pulse width of the heartbeat, you can do that: