﻿Zeus PLC IDE 0.1.0.13 - Windows x64
Zeus Automation / Biosoft Engineering Ltd.

GETTING STARTED
  Double-click "Zeus PLC IDE.cmd". A window opens - no address bar, no tabs.
  Nothing is installed. To remove this software, delete this folder.

WHAT IS IN HERE
  node\node.exe        Node v24.12.0, unmodified (MIT - see licences\)
  bin\zeus-check.exe   the IEC 61131-3 Structured Text compiler
  bin\zeus-sim.exe     the simulator - runs your program with no hardware
  ide\                 the IDE itself
  projects\example\    a small program that compiles as-is

  Nothing is downloaded at any point. This package runs on a machine with no
  internet connection, which is where most controllers live.

REQUIREMENTS
  Windows 10 or 11, 64-bit.
  A Chromium-based browser for the app window - Edge ships with Windows, so
  this is normally already satisfied. Firefox cannot provide the window; the
  IDE still runs and prints a URL you can open in any browser.

THE SIMULATOR
  Devices -> Simulator -> Start. It runs your project with no hardware: every
  IO device is replaced by a simulated one keeping its exact %I/%Q sizes, so
  the process image, every address and the symbol table match the controller.
  Download to it, watch live values, force points, set breakpoints, drive a
  sequence - all of it, with nothing plugged in.

  It is the REAL scan engine, process image, ST compiler and VM, alarm engine
  and monitor protocol, built from the same source the controller runs.

  It is NOT a controller. Windows has no real-time scheduling, so its timing
  figures are not comparable with a controller's and its scan period floor is
  1 ms rather than the CM4's 500 us. It also has no fieldbus: scanning for
  remote IO reports that it is a simulator rather than finding nothing, which
  would look like a cabling fault.

WHAT THIS PACKAGE DOES NOT INCLUDE
  The controller RUNTIME. zeus-plcd wants a PREEMPT_RT kernel, isolated cores
  and real IO; it runs on the controller, not on Windows.

  Both the compiler and the simulator here are built from the same source the
  controller runs, and the compiler's diagnostics are verified byte-for-byte
  identical against it - so a program that compiles and behaves here compiles
  and behaves there, up to the timing a PC cannot provide.

CONNECTING TO A CONTROLLER
  Target... in the status bar, then Add. The monitor port is 5020 and binds to
  loopback on the controller, so a remote connection is an SSH tunnel - the
  IDE can raise one for you.

SUPPORT
  yehuda@biosoft.co.il
