AXIS 2.0 SERIES BRIDGE

Windows 10/11 x64. RoboDK must be installed and running with a station open.
Python, VS Code, Codex and a development terminal are not required.

1. Extract the entire ZIP into a writable folder. Do not launch inside the ZIP.
2. Open RoboDK and select the intended robot in a simulation station.
3. Double-click AXIS2SeriesBridge.exe. The Bridge GUI starts its services.
4. Put the AXIS Android controller and PC on the same trusted Private LAN.
5. In AXIS, connect to the PC address displayed in the Bridge GUI, port 8765.
6. Use Stop Bridge to stop its services; Start Bridge starts them again.
   Closing the GUI also shuts down its owned services.

Normal startup shows only the GUI; no console or PowerShell is required.
This package is intended for RoboDK simulation. Do not enable physical drivers.
Startup and reconnect do not issue motion commands.

NETWORK
Telemetry TCP 8765; guardian TCP 8767; discovery UDP 8766.
Worker TCP 8768 is local to this PC (loopback only).
If trusted Private-LAN access is blocked, an administrator can run the optional
Configure-Private-LAN.ps1 from this extracted folder. It adds rules scoped to
this executable and the local subnet. It is not part of normal startup.
Moving the extracted executable requires updating those path-scoped rules.

LOGS AND SETTINGS
Runtime files and background logs are created outside the package:
%LOCALAPPDATA%\AXIS2Bridge\runtime
%LOCALAPPDATA%\AXIS2Bridge\bridge.log
Use Open logs or Save report in the GUI for troubleshooting.
Only one Bridge instance may own the configured ports at a time.

All Python runtime files, dependencies, worker and guardian components are
embedded in the executable and unpack privately at launch. No project files
or local Python installation are needed. RoboDK remains a separate prerequisite.
See THIRD-PARTY-NOTICES.txt for bundled dependency notices.
