← AXIS 2.0

AXIS 2.0 / SERIES BRIDGE

A local link.
A connected station.

Series Bridge is the Windows companion between your Android pendant and RoboDK. It provides the existing telemetry, command worker and independent guardian services for supported simulation functions.

01 / ARCHITECTURE

Keep control on your local network.

The Bridge and RoboDK run on the same Windows PC. AXIS reads station/robot state through the Bridge and submits supported simulation actions only when the existing connection and command checks allow them. Startup and reconnect do not issue motion commands.

02 / REQUIREMENTS

One Windows companion. No development setup.

On the PC

  • Windows 10/11 x64.
  • RoboDK installed and running, with a simulation station open.
  • A writable folder containing the fully extracted Bridge ZIP.
  • A trusted Windows Private-LAN connection.

RoboDK is separate software and may require its own license. No Python installation, VS Code, Codex or development terminal is required.

On the network

Keep the PC and Android device on the same trusted local network. Guest Wi-Fi and client isolation can prevent device-to-device communication even when both devices have internet access.

Use the address displayed by the Bridge, not a sample address from another PC. A wired PC and Wi-Fi phone still need a reachable local path.

Use the existing verified Windows download. The download card, version details and SHA-256 file remain on the product page.

Open the Series Bridge download card →

03 / STARTUP & STATUS

Extract. Open RoboDK. Start the Bridge.

  1. Extract the entire ZIP

    Use a writable folder. Do not run the executable from inside the ZIP.

  2. Prepare the simulation

    Open the intended station in RoboDK and select its robot. Keep physical robot drivers disconnected.

  3. Open AXIS2SeriesBridge.exe

    The GUI starts the embedded services. Wait for service responses, the intended PC address and the RoboDK station status before connecting AXIS.

  4. Keep the GUI running

    Start Bridge starts the services; Stop Bridge stops them when stopping is confirmed safe. Closing the GUI also shuts down the services it owns. Only one Bridge instance may own the configured ports.

Read the connection states separately

A running Bridge window is not proof that RoboDK or the pendant is ready. Confirm the Bridge services, trusted network state and RoboDK station, then confirm the selected robot and live telemetry in AXIS.

NETWORK_UNVERIFIED means the trusted network check has not passed. BRIDGE OFF means AXIS has no healthy Bridge observation; ROBODK OFF means the RoboDK observation is unavailable.

Documented network ports

TCP 8765
Telemetry / AXIS connection
TCP 8767
Guardian
UDP 8766
Local discovery
TCP 8768
Worker — PC loopback only

These are the bundled README’s existing values, not instructions to expose services publicly. The worker remains local to the PC.

04 / TROUBLESHOOTING

Check the path, one link at a time.

Discovery finds nothing

Confirm the same trusted network and the Bridge’s displayed PC address. In AXIS Link, use RESCAN or enter that address manually with port 8765. Manual connection does not remove the network requirements.

BRIDGE OFF or connection timeout

Confirm the GUI/services are running, the PC address is current and the devices can communicate locally. Check guest-network isolation and Windows Private-LAN access. A timeout alone does not establish which part of the path failed.

Private-LAN access is blocked

The extracted package includes the optional Configure-Private-LAN.ps1 for an administrator. Follow the included README; it adds executable/path-scoped local-subnet rules and is not part of normal startup. Moving the executable requires updating those path-scoped rules. Do not disable the firewall broadly.

RoboDK unavailable or no robot listed

Keep RoboDK open on the same PC with the intended simulation station loaded. Confirm the robot is supported and select it in AXIS. An end-effector or external mechanism is not automatically an eligible arm.

Port conflict or Bridge will not stop

Only one instance can own the ports. Stop the intended old Bridge explicitly before starting another. If motion or stop state is active or unconfirmed, do not force shutdown; resolve the existing software stop/idle condition first.

Need support evidence?

Use Open logs or Save report in the GUI. Runtime files are under %LOCALAPPDATA%\AXIS2Bridge\runtime; the desktop log is %LOCALAPPDATA%\AXIS2Bridge\bridge.log. Review any report before sharing it with support.

Follow the setup guide Back to top ↑

AXIS 2.0 / Real A16 screen capture

Full AXIS 2.0 controller screen captured from the Samsung A16

Actual app screen, presented inside a device illustration on this page. This is not a photograph of the phone.

Privacy Policy

ProServ Robotics · AXIS 2.0
Updated November 11, 2026. This policy describes ProServ Robotics / AXIS activation and transactional setup email. Service availability is shown by the deployed service status.

Activation information

AXIS requests your name and email address to create an activation record and send a product setup email. Records include an activation ID, a random app-installation ID for retries, activation status and dates, delivery state, and app version when supplied. Activation has no account password. This flow does not collect a hardware serial number, advertising ID, robot position, station contents or robot-control history.

Product email and optional marketing

The welcome/setup email explains the Windows Series Bridge and links to the official ProServ Robotics download area. It is a transactional product email, separate from newsletters. You may activate AXIS with marketing consent unchecked.

If you explicitly check the optional news/offers box, the service stores your choice, its timestamp and the versioned wording separately from activation. You must also confirm the optional subscription using the personal link in your setup email before your address becomes eligible for the marketing audience. No marketing provider is connected and this service does not send marketing campaigns.

Unsubscribe

Use the personal “Unsubscribe from optional marketing” link in your ProServ email and press Unsubscribe, or contact support@proservrobotics.com. The signed link does not require a password. Viewing it does not change your preference; submitting it suppresses optional marketing across activations for that address. Unsubscribing does not deactivate AXIS or block transactional setup messages. An older subscription-confirmation link cannot undo a later unsubscribe.

Email preferences and help

Security and service providers

Production activation requires HTTPS. Name/email are stored in the private backend database; the Android app keeps its activation receipt in app-private storage. Request bodies and full email preference links are not written to the prepared service access logs. Short-lived rate-limit counters use keyed hashes of network/recipient identifiers rather than storing raw IP addresses. Signed links authorize only the specific email preference action.

Resend delivers ProServ Robotics / AXIS setup emails from axis@proservrobotics.com. Resend processes recipient email addresses and message contents for transactional delivery. See Resend privacy information. Railway hosts the website and private activation database. AXIS uses its own sender, credentials and email templates. This site has no analytics, advertising cookies, public account login or contact form. External Google Play and RoboDK pages follow their own policies.

Retention and deletion requests

Active activation records are retained to recognize the installation until deletion is requested. The prepared maintenance job removes incomplete, non-sending activations after 30 days, expired request-limit counters, local test email captures after 7 days, and private database backups after 30 days. The production service runs maintenance and private backups daily; backup files expire after 30 days.

To request access, correction, deletion or withdrawal of consent, email support@proservrobotics.com from the address used to activate. Support verifies the request before running the private deletion procedure; there is no public erase endpoint. Deletion removes matching live activation and consent records. A keyed suppression value and withdrawal date may remain to prevent accidental marketing re-enrolment; it does not contain your name or email address. Backups age out under the 30-day schedule. Email accepted by Resend may also be present in its delivery systems; support will handle applicable provider-side requests.

Contact

ProServ Robotics · Birmingham, Alabama
support@proservrobotics.com

Open full Privacy Policy

Terms

Updated November 4, 2026. These website and activation notices describe the prepared product workflow. They do not replace the software license and third-party notices supplied with AXIS or RoboDK.

Supported use

AXIS provides the supported RoboDK simulation functions described on this website. It does not establish compatibility with every physical robot or authorize physical-robot operation. RoboDK is supplied separately and may require its own license. ProServ Robotics and AXIS are independent products, not affiliated with or endorsed by RoboDK unless otherwise stated.

Activation and communications

Provide accurate name/email details and use the activation endpoint only to activate your own installation. The service uses fixed product email and rate limits; it cannot be used to send custom messages or bulk marketing. Optional marketing is separate, requires explicit choice and confirmation, and may be withdrawn. Activation has no account password and does not require a newsletter subscription.

Safety

AXIS software controls are not a substitute for a safety-rated emergency stop or the robot manufacturer's required safety systems. Follow the manufacturer's procedures and the requirements of your simulation environment.

Support and privacy

Contact support@proservrobotics.com for setup and product questions. See the Privacy Policy for activation records, optional communications, unsubscribe and deletion requests. No production service or real-email availability is promised by this local review build.

Open full Terms

Connection & setup help

Contact support@proservrobotics.com.

  1. Open your simulation station in RoboDK Desktop on Windows.
  2. Extract the Bridge ZIP, then open AXIS2SeriesBridge.exe. Wait for the services to respond.
  3. Connect the PC and Android device to the same trusted local network. Enter the PC address shown in the Bridge in the app's Link screen, using port 8765.
  4. If the app cannot connect, check the address, network and Windows Private-LAN access. See the included README for the optional, administrator-run firewall configuration.

Use Save report or Open logs in the Bridge for diagnostics. Review reports before sharing: they may contain network and station information.

Test with disconnected physical robot drivers in a simulation station.

Download Series Bridge ↗