← AXIS 2.0

DOCUMENTATION / USER GUIDE

From installation
to simulation.

Your guide to the AXIS 2.0 pendant and Series Bridge. Connect deliberately, verify live state, and operate the selected RoboDK simulation.

Regular AXIS 2.0.0 · Simulation workflows

01 / AXIS 2.0

AXIS 2.0 overview

AXIS 2.0 turns a supported Android device into a robot-control pendant for RoboDK simulation and supported development workflows. The pendant connects to the Windows companion on your local network; RoboDK supplies the simulation station, robot and programs.

AXIS 2.0 Android Pendant→Wi-Fi / LAN→AXIS 2.0 Series Bridge→RoboDK

This guide describes the regular AXIS 2.0.0 release, not kiosk or development builds. Physical robot operation is outside this guide. RoboDK is separate software and may require its own license.

02 / AXIS 2.0

Getting started

  1. Install AXIS 2.0

    Use the official Google Play destination shown on the AXIS product page when available. If the page says the listing is not yet available, contact support about release availability. Do not substitute a kiosk, beta or test APK.

  2. Activate on first launch

    Enter your name and email in the activation form and submit it while online. Marketing consent is optional. Follow any displayed error; after success, choose Continue to AXIS. The welcome/setup email provides Bridge guidance. Activation success does not mean a local Bridge connection exists.

  3. Download the Windows companion

    Use the Series Bridge download card or download the existing Bridge ZIP. On Windows 10/11 x64, extract the entire ZIP into a writable folder and keep its README and files together. Do not run inside the ZIP.

  4. Prepare RoboDK

    Open RoboDK on the same PC. Load the intended station with a supported robot. Confirm simulation and disconnected physical drivers.

  5. Start Series Bridge

    Open AXIS2SeriesBridge.exe. Wait for responding services, Network ONLINE and the correct RoboDK station. Note the displayed PC address and keep the window running. No Python installation or development terminal is needed.

  6. Check the network

    Use the same trusted local network for phone and PC. A wired PC and Wi-Fi phone work if they can reach each other. The Windows network must be trusted Private LAN. Guest networks and client isolation can block discovery and direct connections.

  7. Connect from AXIS

    Tap LINK or BRIDGE. Select the discovered Bridge or enter its displayed PC address, optionally followed by :8765. Choose CONNECT; RESCAN refreshes discovery. Use your own PC address, not the address in a screenshot.

  8. Select and verify

    Use the top robot selector. Confirm CONNECTED, Bridge Online, the intended station and robot names, and fresh joint/TCP values matching RoboDK. Open STATUS or DIAGNOSTICS for details. Resolve missing or stale information before motion.

See the existing setup guide for additional activation and connection help.

03 / AXIS 2.0

Pendant interface & control reference

Real AXIS 2.0 pendant with numbered connection, arm, program, tool, telemetry, scale, station and action areas
Annotated documentation copy of the approved release capture. Numbers 1–8 match the reference below; the underlying UI is unchanged. Select the image to view it at full size.
  1. Connection and robot selection.
  2. Left arm JOINT controls and STEP.
  3. Program selection, browser, play and manager.
  4. Right tool/wrist controls and gripper state.
  5. Status, views and live telemetry.
  6. JOG SCALE and per-pulse readout.
  7. Station identity, Bridge Online and LINK.
  8. Motion actions and utility panels.

Use the table as a reference while operating the pendant. On narrow screens, scroll the table horizontally. A visible button may be unavailable until the connection, selected robot and station state meet its requirements.

Production control reference · numbers match the annotated image
ControlPurposeHow to use itExpected resultImportant notes
2 · JOG ARM / JOINTJog arm joints J1–J3.Hold a direction with JOINT shown.Repeated joint displacement while held.Arm is JOINT-only; WORLD is disabled.
2 · Arm N / SChange J2.Hold N to decrease J2; S to increase.Selected joint changes in degrees.Screen compass labels do not guarantee a universal Cartesian direction.
2 · Arm W / EChange J1.Hold W for negative; E for positive.J1 decreases / increases.Check the selected robot and joint limits.
2 · Arm J3 arrowsChange J3.Hold upper arrow for negative; lower for positive.J3 decreases / increases.Release to stop further pulses.
2 · STEPChoose the base displacement.Tap 0.1, 1, 5, 10 or 50.Selected value highlights.Actual displacement per pulse is STEP × JOG SCALE / 100; units depend on mode.
3 · PROGRAM dropdownSelect a native RoboDK program.Open and choose the intended entry.Program name becomes selected.Selection does not execute it.
3 · Folder / libraryBrowse available programs.Tap folder; refresh when needed; select an entry.Program browser opens.Browsing does not execute a program.
3 · Play triangleRun the selected eligible program.Check robot and station, then press play.Native simulation program starts, or paused execution resumes.Same run path as bottom RUN; an explicit press is required.
3 · Program list / managerInspect and manage programs.Tap the list icon and choose an entry.Program Manager shows details and permitted actions.Create/edit/rename/duplicate/delete depend on eligibility and ownership; changes affect the current station.
5 · STATUS / telemetryRead readiness, TCP XYZ and J1–J6.Select STATUS and compare with RoboDK.Fresh state for the active robot.Unavailable or stale values are not readiness proof.
5 · VARIABLESInspect connection context.Select VARIABLES.Station, robot, driver and session state display.Read-only context; this is not a general variable editor.
5 · PATHInspect selected program movement details.Select a program, then PATH.Available path/instruction details display.Inspection is separate from RUN.
5 · 3D VIEWView the live RoboDK viewport.Tap 3D VIEW; CLOSE returns.RoboDK image opens.Requires a healthy simulation connection.
6 · JOG SCALE / − / + / sliderScale commanded displacement per pulse.Set 1–100% with slider or buttons.Displayed percentage and pulse amount change.Not rated velocity or a safety-rated speed limit; see the jogging example.
4 · JOG TOOL / TOOL / JOINTChoose the right-hand control mode.TOOL opens TOOL XYZ / TOOL ROTATION / JOINT J4/J5/J6; JOINT selects wrist joints.Right-hand labels and units follow the selected mode.Does not change the left arm from JOINT.
4 · Right N / S / E / WJog the selected right-hand mode.JOINT: N/S = J5 +/−, E/W = J6 +/−. TOOL XYZ: N/S = Y +/−, E/W = X +/−.Joint or tool-relative displacement.TOOL ROTATION uses corresponding Ry/Rx signs; reachable poses and tool configuration apply.
4 · J4 / right arrowsJog remaining right-hand axis.JOINT: upper/lower = J4 −/+. TOOL XYZ: upper/lower = Z +/−.J4 or tool Z changes.TOOL ROTATION uses Rz +/−; labels change with mode.
4 · GRIP OPENOpen a compatible simulated gripper.Wait for an eligible idle state, then tap.Confirmed OPEN is indicated after feedback.Supported vacuum tools instead show VACUUM OFF / release.
4 · GRIP CLOSEClose a compatible simulated gripper.Tap only when the tool is available.Confirmed CLOSED is indicated after feedback.Supported vacuum tools instead show VACUUM ON / pick.
4 · GRIP NONE / stateShow capability and confirmed tool state.Read the label before using gripper actions.NONE means no compatible detected tool; pending/unknown confirms neither endpoint.NONE is an indicator, not a third gripper command.
7 · Station informationIdentify the connected station.Read its name; tap for station information.Station name/detail appears.The station control does not load a different station.
1 · Robot selectorSelect the active robot.Choose a supported robot in the dropdown.Selection and telemetry update.Recheck after each change; this is not coordinated multi-robot control.
1 / 7 · CONNECTED / BRIDGE / LINKCheck and choose connectivity.Tap BRIDGE or LINK; select/enter PC address; CONNECT.Healthy connection and fresh station data.CONNECTED alone does not prove a robot is ready; RESCAN refreshes discovery.
1 · ROBODKCheck RoboDK connection.Tap ROBODK.Connection notice appears.Does not launch RoboDK on the PC.
8 · HOMEMove to configured simulation HOME.Verify destination and idle robot, then tap.Guarded HOME request or a blocked-state message.Requires valid HOME configuration; it is a motion request.
8 · TEACHRecord the current pose.Wait for idle at the desired simulation pose, then tap.Native RoboDK Target N is created and verified.Does not automatically create or run a program.
8 · RUNStart or resume native simulation execution.Select program; check context; press RUN.Selected program starts, or the same paused execution resumes.Blocked if prerequisites are not met.
8 · PAUSEPause active native simulation execution.Press while a started program is running.Pause feedback; RUN resumes the same execution.Unavailable when idle, not started, stopping, or unsupported by the connected Bridge; inspect feedback.
8 · STOPRequest a software stop.Tap STOP and verify idle/stop feedback.Software stop is requested.Not a safety-rated emergency stop. Resolve unconfirmed stopping before another action.
8 · I/OInspect/change simulated station signals.Open I/O; use ON/OFF on a signal when idle.Simulated DI test inputs / DO outputs update.Station parameters only; no physical driver I/O. Writes blocked during active operations.
8 · TOOLSInspect robot, frame, tool and gripper details.Open TOOLS and read the reported values.Tool/frame and support information appears.Change tool/frame in RoboDK; this panel does not provide a tool editor.
8 · SETTINGS / top menuConfigure saved pendant defaults and Bridge address.Edit available fields, then SAVE SETTINGS.Validated defaults are saved for the next app start.Read-only while busy; WORLD is disabled. RESTORE BRIDGE requires a previous known-good address.
8 · DIAGNOSTICSInspect health, events and faults.Open STATUS / EVENT LOG / LAST FAULT; SAVE REPORT exports JSON.Health information or saved report.Review device/network/station details before sharing.

04 / AXIS 2.0

Jogging a robot

Use the numbered areas in the pendant image: connect in area 1, confirm telemetry in 5, choose controls in 2 or 4, then set scale in 6. This sequence commands simulation motion.

  1. Start RoboDK and load the intended simulation station. Disconnect physical robot drivers.
  2. Start Series Bridge and wait for healthy services and the correct station.
  3. Connect AXIS through LINK and confirm CONNECTED / Bridge Online.
  4. Select the intended robot and compare fresh telemetry with RoboDK.
  5. Choose the mode: left JOG ARM stays JOINT for J1–J3. Right JOINT controls J4–J6. Right TOOL offers TCP translation (TOOL XYZ) or TOOL ROTATION relative to the current tool.
  6. Set a low JOG SCALE using the slider or −/+ controls.
  7. Select a small STEP, such as 0.1, and check the displayed per-pulse amount and units.
  8. Briefly press and hold one enabled direction. Observe the selected simulated robot.
  9. Release to stop further commanded jogging. Verify motion/stop feedback and RoboDK before another input.

STEP and scale work together

Displacement per pulse = STEP × JOG SCALE / 100. For STEP 10 at 5%, each pulse is 0.5 degrees for joint/rotation controls or 0.5 mm for TOOL XYZ. Holding repeats pulses; network and verification timing affect their rate. Scale is not a rated robot velocity setting.

JOINT versus TOOL

JOINT changes individual joint values regardless of the screen compass orientation. TOOL XYZ translates the TCP in its current tool axes; TOOL ROTATION rotates in those axes. Tool orientation, robot configuration and reachability affect the result. If a Cartesian move is rejected or a configuration jump is reported, inspect the pose, reduce the step or use JOINT. Do not force an unavailable control.

05 / AXIS 2.0

Teaching targets

TEACH records a pose; it does not run a program. Find TEACH in area 8 of the annotated pendant image.

  1. Confirm the connected station, selected simulation robot and fresh telemetry.
  2. Jog to the desired pose, release all controls and wait for idle.
  3. Tap TEACH once. Wait for success or a blocking/error message.
  4. Inspect the resulting native Target N (for example, Target 1) in RoboDK. The implementation verifies the selected robot, joint values, pose and frame information returned with the target.
  5. Review the target before using it in a program. Program creation and RUN are separate deliberate actions.

HOME, jogging, program execution, gripper work and other busy states can block teaching. A missing confirmation is a reason to inspect RoboDK and Diagnostics before repeating the action.

06 / AXIS 2.0

Programs

  1. Load the required native program in the connected RoboDK station and select the intended robot.
  2. Tap the PROGRAM dropdown or folder browser; refresh and select the program. Verify its name and context.
  3. Use the list icon for Program Manager details. Selecting or browsing never executes the program.
  4. When ready in simulation, deliberately press the play triangle or bottom RUN. Check execution feedback.
  5. PAUSE is implemented for started native simulation execution. When pause is confirmed, RUN resumes the same execution. PAUSE is unavailable outside an eligible active run; an older or incompatible Bridge can report it unavailable. If pause/resume cannot be confirmed, the controller requests stopping.
  6. STOP requests a software stop. Wait for confirmed idle and inspect any fault before continuing. Reconnecting is not an instruction to replay or restart a program.

Program Manager exposes creation and supported management actions according to eligibility and ownership. Review targets and movement details in PATH before execution. This guide does not imply that every externally authored program is editable.

07 / AXIS 2.0

Gripper controls

GRIP OPEN and GRIP CLOSE act only on compatible available simulation tools associated with the selected robot. A healthy simulation connection, supported tool definition and eligible idle state are required.

  • GRIP NONE: no compatible gripper is reported. The action buttons remain unavailable. NONE is not an action.
  • OPEN / CLOSE: tap the intended action, then wait for feedback. Highlighting confirms a reported endpoint, not simply the last button pressed.
  • Unknown / pending: a pending command, failed read or intermediate position confirms neither OPEN nor CLOSED. Check the reported tool state before another action.
  • Busy / unavailable: motion or program work can temporarily block gripper actions even while a previously confirmed position is still displayed.
  • Supported vacuum tools: the labels become VACUUM OFF (release) and VACUUM ON (pick). Pickup depends on a compatible tool and suitable simulated part; no universal hardware support is implied.

The pendant image shows NONE with disabled buttons. Check TOOLS for the end-effector association and reported support.

08 / AXIS 2.0

Series Bridge guide

Real AXIS 2.0 Series Bridge window with responding services, PC address, Network ONLINE, RoboDK station and Bridge Running
Real Series Bridge capture from the approved branding/release assets; its PC address is an example from the capture, not a value to copy. Select the image to view it at full size.
PC address
The local address to enter in AXIS LINK. Use the address shown on your own PC.
TELEMETRY :8765
The pendant connection and live state service. Wait for Responding.
WORKER :8768
The PC-local service handling supported RoboDK work. It stays on loopback; do not expose it to the network.
GUARDIAN :8767
The companion service supervising supported software operations. Responding is a software status, not safety certification.
Discovery UDP 8766
Helps AXIS find the Bridge. This is not the worker port in the shipped package.
Network ONLINE
The trusted Private network check passed. If unverified, resolve the local network configuration.
RoboDK station
Check this is the simulation station you intended to open.
Bridge Running
The Bridge services are running. Check their individual responses and AXIS telemetry too.

Keep the GUI open while using AXIS. Stop Bridge stops owned services when stopping is confirmed safe; Start Bridge starts them again. Closing the GUI shuts down its owned services. Use only one Bridge instance for these ports.

Use Save report and Open logs for support. Follow the README inside the existing verified download. The existing Series Bridge guide remains available.

09 / AXIS 2.0

Troubleshooting

AXIS cannot find Bridge

Check the current PC address, same trusted LAN, and client/guest isolation. Use LINK → RESCAN, or enter the displayed address with port 8765. A manual address still requires local reachability.

Bridge Offline

Check the GUI is open, its services respond, and the PC address has not changed. Verify the network path before trying CONNECT again. A window alone does not prove the services are healthy.

RoboDK not detected

Run RoboDK on the Bridge PC and load the intended simulation station. Inspect Bridge status and logs. If the RoboDK API is unresponsive, stop operations, restore RoboDK, then manually restart the Bridge after stopping is resolved.

Robot not appearing

Load a supported robot in the active station, refresh selection and confirm the station. An end-effector or external mechanism is not automatically an eligible arm.

Robot selected but not moving

Check fresh telemetry, simulation mode, disconnected physical drivers, idle state, selected mode, step and scale. Read the feedback/last fault. HOME needs a configured destination; Cartesian moves need a reachable pose. Do not bypass a blocked state.

Program not appearing

Confirm it exists in the loaded station and is eligible for the selected context. Refresh the dropdown/browser. Merely selecting it must not run it.

Gripper unavailable

Check a compatible simulated tool is associated with the selected robot. Inspect TOOLS and Diagnostics, wait for idle and distinguish NONE from an unconfirmed position. Do not use gripper buttons as a hardware connection test.

Connection lost

Release held controls. Inspect AXIS, Bridge, RoboDK and LAN status; do not assume motion has stopped solely because telemetry disappeared. Resolve stopping/idle, reconnect and recheck robot/station/telemetry before a fresh deliberate action. Commands must not replay on reconnect.

Windows Firewall / local network

Use a trusted Private network and follow the bundled README. If required, an administrator can use the optional Configure-Private-LAN.ps1 from the extracted package; its rules are scoped to that executable and the local subnet. Moving the executable requires updating those rules. Do not disable the firewall globally or expose Bridge ports to the public internet.

Activation or missing welcome email

Follow the activation error shown. After successful activation, check spam/junk for Welcome to AXIS 2.0 from axis@proservrobotics.com; do not repeatedly activate just to resend mail. Use the existing setup guide and contact support.

10 / AXIS 2.0

Safety

This documentation covers RoboDK simulation and supported development workflows. Keep physical robot drivers disconnected. A green status, confirmed software stop or low jog scale is not a safety certification or authorization for physical robot operation.

Verify the selected station, robot, tool, mode, reachability and fresh telemetry before commands. Release held controls before changing context. If feedback is stale, conflicting or unconfirmed, stop work and resolve the state before another deliberate action. Follow the robot and RoboDK manufacturers’ requirements for any separately supported system.

11 / AXIS 2.0

Support

Contact the existing ProServ Robotics support address: support@proservrobotics.com. Include your AXIS version, Bridge version, Windows/RoboDK versions, selected station/robot, the exact displayed message, and steps to reproduce the issue.

Use DIAGNOSTICS → SAVE REPORT in AXIS or Save report / Open logs in Series Bridge. Review reports before sharing; they may include device, network and station details. Do not send passwords or API keys.

Setup guide · Series Bridge guide · Capabilities · Privacy · Data deletion

Production AXIS 2.0 Settings screen
Settings in the approved regular AXIS 2.0.0 release. Select the image to view it at full size.
Production AXIS 2.0 Diagnostics screen
Diagnostics in the approved regular AXIS 2.0.0 release. Select the image to view it at full size.
Production AXIS 2.0 live RoboDK viewport
The real RoboDK view captured through the release pendant. Select the image to view it at full size.

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 ↗