← AXIS 2.0

AXIS 2.0 / CAPABILITIES

Your station.
Your control.

An Android pendant for working with a RoboDK simulation on your Windows PC. Select a robot, inspect its live state and use the supported controls for that station. Physical-robot execution is not included.

01 / CONTROL

Deliberate inputs. Clear feedback.

01

JOINT & TOOL jogging

The current arm panel uses JOINT controls. The right-hand selector offers TOOL XYZ, TOOL ROTATION and JOINT J4/J5/J6. Use only the modes enabled for the selected simulation robot; release a held jog to stop further jog pulses.

Cartesian movement depends on the selected tool, robot configuration and reachable pose. A rejected move is a reason to inspect the station, not force the control.

02

Guarded HOME

Request the selected robot’s configured HOME in simulation. HOME requires an eligible idle robot and a valid home configuration; an unavailable or unconfigured HOME remains blocked.

Check the station and intended home before using it. HOME is a motion request, not a connection test.

03

TEACH native targets

Record the current simulation pose as a native RoboDK target associated with the selected robot. Inspect the resulting target in RoboDK before adding it to a program.

Teaching records the current pose; it is not an instruction to move to a different pose.

04

Program selection & execution

Choose an eligible native RoboDK program and explicitly press RUN. PAUSE pauses the active simulation; RUN resumes that paused execution. STOP requests a software stop.

Execution depends on a fresh connection, the correct selected robot and an eligible station state. Connection or reconnect does not automatically start a program.

05

Jog scale & step size

Set JOG SCALE from 1–100% and choose a step of 0.1, 1, 5, 10 or 50. The pendant shows displacement in millimetres for translation or degrees for joint/rotation controls.

Jog scale is a software setting, not a safety-rated speed limit. Begin with a small step and low scale in simulation.

06

Compatible simulation grippers

OPEN/CLOSE supports compatible one-axis simulated grippers associated with the selected robot. Supported vacuum tools use OPEN for vacuum OFF/release and CLOSE for vacuum ON/pick.

Tool capability and confirmed state determine availability and feedback. Unsupported tools remain unavailable; no universal hardware-gripper support is claimed.

02 / FEEDBACK

See the state before you act.

Live telemetry & status

Read the selected robot’s joint values and TCP position, together with Bridge, RoboDK, station and connection status. STATUS is the first check after selecting a robot.

A station name alone does not establish readiness. Confirm CONNECTED and live values; stale or unavailable state must not be treated as a fresh connection.

Diagnostics you can share

Use the pendant’s DIAGNOSTICS and SAVE REPORT controls, and the Bridge’s Open logs or Save report actions, to investigate problems. Review reports before sending them to support: network and station information may be included.

Missing capability, connection loss or an unconfirmed stop is a blocked state, not a prompt to bypass checks.

03 / STATION & NETWORK

One selected robot. A local connection.

Supported multi-robot stations

List and select supported robots within a RoboDK station, then inspect telemetry for the active selection. Recheck the robot name and readiness after every selection change.

Selection and telemetry switching have been verified in supported multi-robot stations. This is not simultaneous coordinated multi-robot control or a claim that every station/robot is supported.

Wi-Fi / LAN operation

The Android pendant talks to Series Bridge on the Windows PC over a trusted local network. Use the Bridge’s displayed PC address, with discovery or a manual connection from AXIS.

The PC may use wired LAN while the phone uses Wi-Fi, provided they can reach each other on the same trusted network. Initial AXIS activation requires access to the production activation service.

Understand Series Bridge 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 ↗