Skip to main content

Where to Start

If you are new to Zeus, do not start by reading every concept page. Pick the path that matches your goal, run a working example, then come back to the terminology.

Pick Your Goal

What you want to doRead firstOutcome
Verify Zeus runsConsole SampleA minimal app that writes PING, receives the echo, and exits cleanly
Build a WinForms host appFirst WinForms AppA form with send button, state display, and echo display
Build a WPF host appFirst WPF AppA WPF window that updates safely through the Dispatcher
Connect a serial deviceSerial PortReplace the virtual channel with real COM3 / 9600 settings
Read a Modbus meterModbusRead coils and registers, or simulate a slave first
Read Mitsubishi PLCsMitsubishi MCAccess common Mitsubishi devices and virtual PLC simulation
Read Siemens PLCsSiemens S7Read/write DB/I/Q/M areas with virtual PLC simulation
Read Omron PLCsOmron FINS / Omron Host LinkUse FINS over UDP/TCP or Host Link over ASCII serial/TCP tunnel
Read Allen-Bradley PLCsEtherNet/IPRead/write CIP tags and attributes
Deliver with a config fileJSON ConfigurationMove ports, unit ids, point maps, and polling intervals into zeus.json

Four Terms to Remember

TermPlain meaningWhere it appears
HostThe Zeus runtime containerStarts, stops, and disposes resources
ChannelA communication lineSerial, TCP, UDP, and virtual channels
ProtocolHow bytes are interpretedModbus, MC, S7, FINS, Host Link, EtherNet/IP, or custom frames
PointA business data itemTemperature, pressure, switch state, alarm state
  1. Read Installation and confirm .NET 8 SDK is available.
  2. Run Console Sample to verify host and channel behavior.
  3. Pick WinForms or WPF if you are building a desktop UI.
  4. Keep using virtual channels until the workflow is stable; replace with serial, TCP, or UDP when hardware is ready.
  5. After the protocol path is clear, move on to acquisition, configuration, and troubleshooting.

When Not to Use Zeus

Zeus is not a low-code SCADA system and does not ship charting, permissions, recipes, or reports. It targets the infrastructure that host applications most often reimplement incorrectly: channel lifecycle, protocol sessions, polling, UI thread marshaling, and hardware-free simulation.

Next: Installation.