EDAS separates engineering tasks from runtime execution. Engineers use Design, Programming, and Metrology Modes to configure the cell. EDAS GO sits atop the Execution Mode, enabling operators to run fully validated projects without accessing any engineering tools. This separation ensures that the runtime environment remains simple, secure, and consistent.
EDAS GO’s interface is built for simplicity: operators select a project and press play. There’s no access to the command tree or engineering settings. Projects are prepared and validated in EDAS; EDAS GO simply ensures safe, repeatable execution. The interface uses the same Execution Mode under the hood, guaranteeing consistency.
Configuration for EDAS GO is handled in the main EDAS application. A Go folder is defined in the settings, and an auto-load option can launch the correct project automatically. This eliminates manual navigation. Once the PC boots, EDAS GO is ready with the right project preloaded. Operators can focus on supervision, not setup.
EDAS connects to robots, PLCs, and sensors via Ethernet/IP, Profinet, TCP/IP, and USB. With integration-tested connectivity and proven 24/7 uptime, the system supports automated signals, interlocks, and continuous operation. EDAS GO leverages this architecture to deliver seamless execution in live production environments.
Observers are configured in EDAS to watch for changes in variables, program states, or system events. They function like the cell’s nervous system, sensing key changes like part presence or device readiness. Observers can visually indicate their state using UI widgets, enabling operators to instantly assess system status.
When an observer condition is met, triggers execute specific actions. These include starting a program, stopping execution, displaying a message, or even switching projects. Together, observers and triggers enable classic zero-touch patterns: automatic start, automatic stop, and automatic changeover, all without external scripting.
EDAS offers multiple built-in recovery paths. If execution fails, the system can back-trace machines home, plan a safe home motion, or continue from the point of failure. Operators can choose the safest option without restarting the entire cycle. These behaviors are inherited by EDAS GO from Execution Mode, supporting robust inline performance.
EDAS includes features like automatic reconnect for disconnected devices and auto-homing for robots. Data housekeeping is also built-in: dedicated commands delete all data or just the latest data group, ensuring disk space remains under control. These functions help maintain uninterrupted, long-term operation.
With engineering handled upfront in EDAS, runtime simplified through EDAS GO, and automation handled by observers and triggers, the system becomes an appliance. Operators launch EDAS GO and the cell executes inspections with minimal intervention. This structure allows production teams to trust the system’s reliability, even under 24/7 inline conditions.
