← AXIS 2.0

AXIS 2.0 / GET STARTED

From setup
to live telemetry.

Prepare the PC and phone, connect to the intended RoboDK station, then verify live feedback before any simulation motion. Keep the Windows Bridge README beside you for package-specific details.

BEFORE YOU BEGIN

Start with an isolated simulation.

You need AXIS on Android, Windows 10/11 x64, RoboDK installed on that PC, the verified Series Bridge ZIP and a trusted Private LAN. RoboDK must have a supported simulation station open. Keep physical robot drivers disconnected throughout this first setup and test.

Requirements & network details →

01 / STEP BY STEP

Make each connection explicit.

  1. Activate AXIS

    Open AXIS on the phone. If activation is required, enter your name and email and submit the activation form. Marketing consent is optional. The setup email contains the Bridge setup/download link.

    When activation succeeds, press Continue to AXIS. If activation fails, follow the displayed error; do not attempt to bypass the activation requirement.

  2. Prepare RoboDK on Windows

    Open RoboDK on the same PC that will run Series Bridge. Load the intended simulation station and identify the robot you want to use. Leave physical robot drivers disconnected; confirm the station is in simulation.

  3. Download and extract Series Bridge

    Use the existing verified Windows download card. Extract the entire ZIP into a writable folder. Keep the bundled README and other package files together. Do not run the EXE from inside the ZIP.

  4. Start the Windows companion

    Double-click AXIS2SeriesBridge.exe. The GUI starts its services; no separate Python installation or terminal is required. Wait for the service responses and RoboDK station information. Note the PC address displayed by the Bridge and keep its GUI open.

  5. Check the local network

    Connect the Android device and PC to the same trusted local network. The PC’s Windows connection must be Private. Avoid guest Wi-Fi or client isolation that blocks local device communication. Internet access alone does not prove the phone can reach the PC.

  6. Connect AXIS to the displayed PC address

    Open Link or the BRIDGE selector in AXIS. Use a discovered Bridge, or enter the PC address shown by its GUI. Manual entry accepts a host/IPv4 address with optional :port; the documented connection port is 8765. Press CONNECT. Use RESCAN to refresh discovery if needed.

    Do not paste a website URL, guess another PC’s address or change ports to work around a failed connection.

  7. Select the intended robot

    Open the robot selector and choose the supported robot from the loaded station. Verify its name against RoboDK. In a multi-robot station, only the active selection should be treated as your current control target.

  8. Verify live telemetry first

    Check the station and robot names, CONNECTED status, joint values and TCP position. Compare them with the selected simulation robot in RoboDK. If status is unavailable, stale or inconsistent, stop setup and troubleshoot before trying any motion control.

02 / FIRST SIMULATION CHECK

Telemetry first. A small jog only when ready.

A connection test needs no motion

A healthy Bridge, correct selected robot and matching live telemetry are the first success criteria. Connecting or reconnecting AXIS must not launch a program or move the robot automatically.

Keep the real robot disconnected. Software readiness is not authorization for physical operation.

Optional simulation-only jog

After all connection checks pass, confirm again that physical drivers are disconnected. Use JOINT mode, a small step such as 0.1 and a low JOG SCALE. Briefly hold one direction, then release it and verify the simulated movement stops before another action.

If the control is unavailable, feedback is stale or stopping is unconfirmed, stop the test. Do not bypass a blocked state. Do not use HOME or RUN as a first connection probe.

03 / COMMON SETUP QUESTIONS

Resolve the prerequisite, not the symptom.

Activation succeeded, but the email is missing

Check spam/junk and search for “Welcome to AXIS 2.0” from axis@proservrobotics.com. If activation already succeeded, do not submit it again just to request another email. Use this setup guide and contact support to check delivery.

The app says BRIDGE OFF or NET CHECK

Check the current PC address, running Bridge services and the trusted Private-LAN path. NET CHECK / NETWORK_UNVERIFIED means the network check has not passed. Review the Bridge troubleshooting guide and bundled README before changing network settings.

Connected, but no usable robot or telemetry

Verify the loaded RoboDK station and active robot selection. Confirm the item is a supported robot rather than an external mechanism. Wait for fresh values; a station name or old screen values alone do not establish readiness.

HOME, RUN or GRIP is unavailable

These controls require the matching station capability and an eligible current state. Check HOME configuration, selected program/robot, compatible tool and whether another action is active or still stopping. A gripper button is not a universal hardware control.

The connection drops

Release controls and inspect the Bridge, RoboDK and local network status. Wait for a fresh connection and recheck the selected robot/telemetry before deliberately continuing. Never assume an earlier command should replay after reconnect.

Still blocked?

Use the pendant DIAGNOSTICS / SAVE REPORT and Bridge Open logs / Save report tools. Review reports for network or station information before sending them to support@proservrobotics.com. Do not send passwords, activation receipts or API keys.

Explore the supported controls 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 ↗