When replacing or introducing an industrial robot teach pendant, screen size and unit price are only the visible part of the purchase. A pendant may power up yet fail to communicate with the controller, load the expected program, or support the cell’s manual operating and safety functions. Procurement should define whether the scope ends at the handheld unit or includes cables, controller software, data migration, safety verification and on-site acceptance. This guide is for maintenance, engineering and purchasing teams at Thailand factories.
The decision: buy a working, recoverable and accepted configuration
Record the robot model and serial number, controller model and serial number, current pendant part number, cable part number, software release and installed options before asking for a replacement. Obtain written, configuration-specific compatibility confirmation from the robot OEM or its authorized support channel. Take a verified backup while the existing system is accessible. Then test the delivered combination against its manual operation, safeguards, program data and real workpieces. A visually similar pendant is not proof of compatibility.
Troubleshooting comes before a purchase order. ABB’s FlexPendant manual, for example, lists checks of the joystick lock, controller manual mode and connection before recommending replacement for a joystick problem. A unit that displays a screen but cannot jog may have a cause elsewhere. That example is specific to the documented ABB configuration; follow the manual for the equipment actually installed.

Separate three reasons for the project
Failure recovery. Document the symptom, error history and conditions under which the screen, keys, joystick, emergency stop, enabling device or cable fails. Diagnose the fault with an authorized technician and the OEM procedure. Establish whether the pendant, cable, connector or controller needs attention. Preserve data before sending a faulty component away and clarify warranty and local support.
Usability or maintainability improvement. A newer interface, diagnostics or language option can require a controller or software change. Check licenses, user rights, custom screens and available support. A new terminal does not automatically make a legacy controller capable of new features. Include the safety review, revised training and rollback plan when the change reaches beyond a like-for-like part replacement.
New robot cell. Specify the robot, controller, pendant, wiring, safeguards and operating roles as a system. Decide who may teach, who can restore a backup, where an operator stands during teaching and how a portable device is stored. New-cell integration has a broader acceptance scope than replacing a documented spare part in an existing cell.
Five layers of teach pendant selection
Robot and controller identity
Capture nameplate photos, serial numbers, software screens, controller drawings, installed options and the old pendant and cable labels. Put the current and proposed configurations side by side, with a column for the OEM evidence and unresolved conditions. “Same brand” and “same family” are insufficient procurement descriptions. A suffix, revision or option may matter. The ABB OmniCore FlexPendant documentation references several controller manuals and variants, illustrating why a general product description cannot certify a specific plant’s combination.
Software, options and access rights
Successful power-up and login do not prove that jogging, teaching, I/O inspection, program editing and restoration will work. Inventory the controller release, licenses, language packs, user accounts and custom applications. If a software update is required, specify the upgrade path, prerequisites, reactivation, backups and rollback. Universal Robots’ service guidance says to identify the current software release before an update; its Magic Files guidance explicitly calls for backing up programs and installation files before updating. These are examples of the discipline required, not procedures to apply to another manufacturer’s robot.
Cable, connector and physical layout
Survey cable length and part number, connector type, bend points, routing, holder and teaching position. A compatible handheld unit is unusable if its lead will not reach a safe operating location or is trapped by a door. Do not improvise extension leads: confirm permitted components and total length with the OEM. ABB’s OmniCore V250XT parts manual lists the FlexPendant, holder, different cable lengths and extension cables as separate parts. Ask bidders to identify each supplied item by part number and quantity.
Safety functions and cell integration
Use the cell’s risk assessment and circuit drawings to determine what changes. Review the pendant emergency stop and enabling device, operating mode, restricted motion, safety doors, external emergency stops and restart behavior. ABB’s FlexPendant manual describes the three-position enabling device and the stop behavior when it is released or compressed beyond the enabling position. The actual test must use the installed configuration and approved safety procedure. Never treat a bypassed safeguard as an acceptable commissioning shortcut.
ISO 10218-1:2025 addresses safety requirements for the industrial robot itself; ISO 10218-2:2025 addresses robot applications and cells, including integration and commissioning. A standard number on a quotation does not establish that an existing cell complies. Assess the equipment’s age, modifications, local rules and the scope of work, and retain the applicable test evidence and residual-risk decisions.
The ISO public page also states that ISO 10218-1:2025 does not apply to robots manufactured before its publication. Do not declare a legacy cell compliant merely because a spare pendant was installed, or assume that publication alone creates a retrofit obligation. Have qualified personnel assess the change and applicable scope.
Support and continuity
Ask about spare supply, repair lead time, local stock, end-of-support status, software maintenance, warranty start date and field service. Headquarters’ preferred part number may not match what a Thailand site can obtain quickly. If rapid recovery matters, decide whether a tested spare should be kept on site. “Equivalent” should be replaced by an exact item and documented support terms.
| Layer | Evidence to collect | If there is a mismatch |
|---|---|---|
| Robot and controller | Model, serial, OEM configuration | Hold order for OEM confirmation |
| Software and rights | Release, options, screen settings | Add migration and restoration tests |
| Wiring and layout | Cable part, length, route | Redesign with approved parts |
| Safety | Circuit, risk review, test plan | Extend assessment and acceptance |
| Support | Supply, warranty, local service | Reset spare and recovery plan |

Back up and migrate before removing the old unit
Copying a robot program to a USB drive does not necessarily constitute a recoverable backup. Depending on the model, the scope may include programs, tool and work coordinates, calibration data, I/O mapping, network settings, user rights, safety settings, options and a system image. Confirm each data type and its restoration method against the OEM instructions. Decide what data may leave the site and how portable media will be protected.
The backup record should include the equipment ID, controller serial number, software release, date, operator, medium, filenames, integrity check and storage location. Verify that files can be read; where possible, perform a restoration test in an approved spare or test environment. A production-system restoration needs a planned outage and a return path. A file’s existence is weaker evidence than a successful, configuration-matched restoration.
Distinguish data that resides on the pendant from data held by the controller. The pendant is an interface, but storage architecture differs between products. An unresponsive handheld device may still leave a controller-side backup path. Conversely, recreating a custom screen can be a separate task. Agree on the expected screens and operator scenarios before FAT. After acceptance, save a new final backup and clearly distinguish it from the pre-change version.
Divide FAT and SAT responsibilities
Factory acceptance testing (FAT) verifies what the supplier can reproduce before shipping: part identity, connection to the intended controller, software release, login, screens, rights, data import and simulated functional checks. Record anything that cannot be tested as an open SAT item. A demonstration screen alone cannot stand in for acceptance in the actual robot cell.
Site acceptance testing (SAT) uses the actual wiring, guards, operating positions, operators and workpieces. Confirm the safe reach and routing of the cable, manual and automatic mode behavior, emergency stop and enabling functions, guard integration, representative programs, coordinates, I/O, product quality and abnormal recovery. Hazardous tests require an approved procedure and controlled access. This list defines evidence to request; it is not a model-specific instruction to operate a robot.
For each test, record the initial state, action or stimulus, expected response, observed result, proof, verdict and person responsible for retesting. “It worked” is not a useful acceptance record. A revised key layout or permission system also calls for operator and maintenance training. Release the cell for production only under the site’s approved acceptance criteria, with open issues assigned and a verified final backup.
| Test area | FAT | SAT addition |
|---|---|---|
| Identity and connection | Part, release, boot, login | Real wiring, connector, holder |
| Data | Backup read, screen reproduction | Programs, coordinates, I/O |
| Manual control | Mode, jog, permissions | Operator position and cable route |
| Safety | Designed I/O in a test setup | Integrated cell safeguards |
| Production | Simulated sequence | Real work, quality, recovery |

Agree on acceptance evidence before ordering
Write the FAT and SAT plan before issuing the purchase order. The buyer and supplier should agree on the exact tested configuration, pass criteria, measurement method, witnesses and record format. Put the controller serial number, software release, options and cable part number beside the proposed pendant part number on the test sheet. Compare the delivered nameplates with that sheet. A supplier’s proposed substitution needs prior approval and a new compatibility basis.
For safety functions, test permitted actions and stopping behavior in each relevant mode, including who must act before restart. Use the installed model’s OEM instructions and the site’s risk assessment. Never bypass a safeguard to obtain a pass. A warning disappearing from the screen alone does not prove the safety circuit. Keep expected and observed results in separate fields, linked to photos, event logs and software identification.
For data, compare the backed-up file inventory with the restored programs, coordinates, I/O and access rights. If every product variant cannot be run during SAT, name the representative variants, the untested variants and the person accepting the residual risk. Test custom screens and external PLC communication separately from standard pendant functions. Update the local work instructions and training materials if screen names or operating steps change.
Agree beforehand on what follows a failure. A minor display difference, a control defect and a safety-related defect need different correction, retest and production-release rules. State who fixes each issue, by when, who pays for a return visit, whether temporary operation is allowed and how acceptance affects payment. Clarify whether warranty begins on delivery or commissioning when those dates are far apart. Record first support contact, remote-diagnosis conditions, spare location, repair shipping and treatment of intermittent faults. These conditions matter at the next outage even if they are invisible in a unit-price comparison.
Make the request for quotation comparable
“Teach pendant replacement, complete” leaves too much unspecified. Attach the equipment inventory, symptoms, nameplate photographs, software release, available backup and allowable production outage. Break the requested scope into pendant, cable, connector, holder, licenses, software update, data migration, site installation, FAT, SAT, training and spares. State whether night or weekend work and production supervision are required.
Request a part number, quantity, compatibility basis, price, lead time, warranty, labor allowance, assumptions and exclusions for each line. If one supplier sells the part and another commissions it, name the first responder for a connection or restoration failure. Include drawing revisions, risk assessment and test records when safety-related changes are made. Compare total cost, including production downtime, travel, migration, education and re-testing. There is no universal downtime cost; use the plant’s own production plan and loss estimate.
Diagnose before replacing
A dark display, intermittent communication, unresponsive keys and failed jog are different symptoms. Safely stop the cell and let authorized personnel capture errors, controller state, supply, visible cable condition and connector condition under the manufacturer’s maintenance procedure. Do not disconnect live connectors or bridge circuits as an informal test. Preserve initial logs and photos so that later resets do not erase the trail.
Record when the issue occurs, in which mode, under which operation and whether it can be reproduced. An intermittent fault associated with cable movement suggests a route for inspection, but the OEM procedure should confirm the cause. For failed jog, inspect rights, mode, lock, connection and interlocks in the prescribed sequence. A pendant reset may not reset the controller. If rebooting appears to fix the issue, still document recurrence conditions and the root cause before calling the job complete.
Compare a like-for-like replacement, OEM repair, compatible successor and controller modernization. A successor may be easier to source yet add software and safety work. Continuing to repair an old model may shorten the current outage but lengthen the next one if spares are scarce. Send the diagnosis record with the RFQ to reduce uncertainty in bids.
Plan the Thailand implementation and handover
The Thailand production and maintenance teams, headquarters, OEM and local integrator may all have a role. Assign who approves the configuration, owns the backup, performs safety tests and signs acceptance. Share operating and recovery instructions in languages the site team can use. Coordinate the engineer visit, customs or domestic delivery and the production outage before dispatching the part.
Set gates for survey, OEM confirmation, RFQ, backup, FAT, replacement, SAT, training and final backup. The survey closes when part identities, releases, wiring and safety drawings are collected. FAT closes with evidence and a named SAT carryover list. SAT closes with verdicts and owners for unresolved issues. In a breakdown, shorten the calendar where feasible while explicitly retaining essential checks.
Classify the impact of the proposed change
A specified like-for-like spare still needs diagnosis and site checks. A successor with a new cable, software release or interface needs migration, training and broader testing. A controller or safety-circuit modification demands a cell-level assessment. For each quotation, identify which class it represents and who authorizes the work. “To be confirmed after survey” should come with a survey deliverable and a date for firm price and lead time. The classification is not an OEM compatibility declaration: the actual serial number, revision and options still need confirmation.
Plan the production outage and rollback
The outage plan should include final backup, safe isolation, removal, connection, startup, functional and safety tests, representative workpiece checks and release approval. Estimate each step from measured or supplier-supported time and set a decision time if the work slips. Define the resources for rollback. Whether rollback is possible depends on the old part, software reversibility and a verified backup; do not assume it. State who authorizes a return to the old configuration and what evidence must be checked before production restarts. Confirm the OEM’s support availability for any night or weekend change.
Keep a complete handover set
Retain the old and final versions separately, with a current configuration list, before-and-after part numbers, drawings, OEM confirmation, restoration instructions, FAT/SAT records, open items, training and support contacts in a controlled equipment folder. Record the software release shown by the real controller so a future technician can identify differences from the paper specification. Monitor alarms, communication, cable routing and operator mistakes during an agreed early-operation period; treat new observations as change records rather than informal anecdotes. For a fleet, pilot one unit first while checking every other unit’s serial number, options and modifications separately. One passing unit does not certify the others.
For the wider work of programming and downtime, see our robot teaching and programming guide. For supplier responsibility across a complete project, use the robot integrator selection guide. This article focuses on the pendant’s selection, replacement and acceptance boundaries.
FAQ
Is the robot brand enough to select a teach pendant?
No. Match the robot and controller models and serial numbers, software release, options, pendant part number and cable against configuration-specific OEM information. Ask for written confirmation of the proposed combination.
Is a backup unnecessary for a pendant-only replacement?
Do not assume so. Data placement and recovery methods differ by model. Preserve the OEM-specified program, settings, calibration and safety-related information, and test readability and restoration. Ask the OEM about controller-side recovery if the old pendant is dead.
How do we confirm controller compatibility?
Compare the actual nameplate, release and options with the OEM configuration table, parts information or support response. For a used or third-party item, also document warranty, safety functions, software support and local service. Keep the purchase conditional if compatibility is unresolved.
What is the difference between teach pendant FAT and SAT?
FAT checks the proposed pendant/controller configuration and data functions before shipment. SAT checks real wiring, safeguards, workpieces, I/O, operator location and abnormal recovery at the plant. Record untested FAT items as explicit SAT obligations.
Can production restart when the new screen powers on?
Screen startup is not acceptance. Complete the approved site tests for manual and automatic behavior, safeguards, representative production and recovery; assign any open issues; train the operators; and save a verified final backup.
Summary
An industrial robot teach pendant replacement is successful when the delivered part is compatible with the specific controller and software, the data can be recovered, the cell’s safety functions are verified, and the real process passes SAT. Build the RFQ and test plan around those outcomes rather than the handheld unit alone.
TOMAS TECH helps Thailand manufacturers map existing robot-cell configurations, clarify OEM and integrator responsibilities, and prepare practical acceptance criteria. If you are still deciding whether the work is a spare-part replacement or a wider controller and safety update, you can contact us at that stage.
References
- ABB FlexPendant Product Manual, Revision D (2026)
- ABB OmniCore V250XT Product Manual, FlexPendant parts
- Universal Robots, Using Magic Files
- Universal Robots, Update Procedure
- ISO 10218-1:2025
- ISO 10218-2:2025
Use the manufacturer instructions for the actual model and release. The standards’ application and local compliance must be assessed for the specific equipment.