FAIRINO Controller and Software: Checks to Put in the Purchase Order

Identify the controller that will actually arrive

Request a configuration schedule that identifies the arm, controller, teaching device, interface equipment and supplied cables. Ask for the controller's orderable identifier and a photograph or drawing of the delivered arrangement. An arm model alone is not a sufficient description of the control package. FAIRINO's FR5 product page separates controller information and optional communications, which makes it especially useful to distinguish the base offer from additions in a reseller quotation.

Have the supplier state which site requirements it expects the buyer to provide, including the reviewed electrical installation, network connection and mounting space. Where a web page and a quotation appear inconsistent, request written clarification against the exact hardware being sold. Do not resolve ambiguous supply information by inference. Keep installation details with the qualified electrical and integration specialists, while making the scope and evidence clear enough for purchasing to compare offers.

参考资料： FR5 product page: controller and optional communication specifications

Freeze a compatible version baseline

Ask for a baseline listing the controller software, web interface, firmware, external SDK and any application modules used in the proposed solution. FAIRINO's C++ Basics chapter documents separate software, hardware and firmware queries. Request a saved version record from the offered or acceptance-test system, plus the supplier's statement that the listed components are supported together. A single phrase such as latest software is not a reproducible configuration.

The references here use the versioned 3.8.3 documentation; that is a documentary baseline, not a claim that it is the newest release or the correct release for your purchase. Ask the supplier to name the manual and release notes applicable to the delivered system. If a demonstration uses a different baseline, require an explanation of the differences and the checks needed before carrying its result over to your order.

参考资料： C++ SDK: Basics, communication and version queries · User Manual 3.8.3: Version introduction and changelog

Buy the complete communication path

List each external device, the required exchange and the party responsible for each end. For a PLC interface, describe ordinary process commands, acknowledgements, status, errors and recovery behaviour. FAIRINO's custom-protocol chapter describes industrial-bus integration using additional board hardware and notes a board-specific EtherCAT limitation. A protocol name in marketing therefore does not establish that the necessary hardware and supported configuration are included in the controller offer.

Request the exact board, protocol role, configuration files and device-description files where applicable. Have the integrator demonstrate the required exchange with the intended PLC family or an explicitly agreed equivalent. Keep ordinary process communication distinct from the independently designed safety architecture. If the quotation says compatible but nobody owns the PLC program, mapping or acceptance test, the buyer still has an integration gap to resolve before treating that interface as delivered.

参考资料： User Manual 3.8.3: Custom protocol slave commands and board configuration

Test the software your team plans to maintain

For an SDK-based application, ask for a small proof using the planned language, operating environment and deployment computer. It should establish the required connection, report identifiable controller state, handle errors and produce useful diagnostic records. Motion testing belongs in the integrator's controlled procedure. A successful connection from the supplier's laptop leaves unanswered whether the delivered project can be built and maintained in the buyer's environment.

Hypothetical example: a supplier demonstrates a custom inspection application but only offers the executable. The buyer expects to change part recipes and camera behaviour later. Ask for the source project, dependency list, build instructions and ownership terms needed for those changes, or explicitly purchase a supported managed solution. Neither arrangement is inherently the right choice for every buyer; the problem is discovering the restriction after delivery. FAIRINO's SDK documentation establishes interfaces, not rights to a supplier's custom application.

参考资料： C++ SDK: Basics, communication and version queries

Confirm account and project access

Define who needs to operate, teach, configure and administer the delivered system. FAIRINO's System chapter documents account and permission management, while its teaching-software chapter describes login roles. Ask the supplier to demonstrate the agreed tasks using the intended buyer accounts. A working administrator session during a sales visit does not establish that the buyer will receive the same rights, or that routine operators should use them.

The System documentation also describes program-encryption settings and a web-interface usage-period lock. Ask whether either applies to the offer, who controls it and how any agreed restrictions are resolved through authorised support. Do not assume these functions are enabled on every robot. Record project editability, account handover and remote-support arrangements in plain language, with a clear route for the buyer to regain authorised access when personnel or service providers change.

参考资料： User Manual 3.8.3: System, accounts, permissions and custom information · User Manual 3.8.3: Teaching pendant software and login roles

Require a recovery package that has been explained

Ask for the accepted application backup and an inventory of separately required material, such as external computer projects, device configurations and supplier drawings. FAIRINO's Application chapter describes backup content and checks when importing a package. Require the integrator to state which equipment and configuration that backup matches, what it restores and what commissioning checks remain necessary afterward. Do not equate the existence of an archive with a verified recovery process.

Define how a replacement controller would be commissioned and who would supply compatible software and configuration. A planned rehearsal on suitable equipment can expose missing material without disturbing the accepted system. Request readable recovery instructions, the location of controlled copies and a named support owner. Keep access credentials under the buyer's normal secure handling process rather than embedding them in broadly shared project documentation or assuming a publicly documented default is a handover plan.

参考资料： User Manual 3.8.3: Application, upgrades and data backup · User Manual 3.8.3: Teaching pendant software and login roles

Agree update and support ownership

Ask who recommends updates, who checks compatibility and who performs application verification afterward. FAIRINO publishes release notes, and its Application chapter distinguishes software and firmware upgrade activities. Use those facts to request a controlled support process, not to schedule an automatic update of an unreviewed production system. The support proposal should explain how the team decides whether a particular change is necessary for the buyer's application.

Specify the evidence a support request should contain: equipment identity, baseline versions, event description and relevant logs. Agree the initial response route, the escalation owner and what assistance is included, with supplier-provided commercial terms rather than assumed service promises. Ask what happens when an external SDK, computer operating system or peripheral is changed. A support boundary that ends at the robot controller may leave the most difficult application problem between several vendors.

参考资料： User Manual 3.8.3: Version introduction and changelog · User Manual 3.8.3: Application, upgrades and data backup · User Manual 3.8.3: System, accounts, permissions and custom information

Make the purchase order testable

Convert broad claims into deliverables and demonstrations. Replace supports our PLC with an identified interface configuration and a defined exchange test. Replace software included with an itemised baseline and a statement about editable project material. Replace training included with the actual tasks the authorised buyer team should be able to perform. Keep unresolved items attached to the order review so that assumptions do not disappear between sales and integration.

At handover, compare the delivered configuration with the accepted schedule and record substitutions. Confirm that the required project material, configuration files and recovery records can be located by the buyer. A missing optional interface board or inaccessible custom program should become a visible acceptance issue, not an informal promise to help later. The purpose of these checks is maintainable ownership: the buyer knows what was supplied, what it can do and who is responsible when the application needs attention.

参考资料： User Manual 3.8.3: Custom protocol slave commands and board configuration · User Manual 3.8.3: System, accounts, permissions and custom information · User Manual 3.8.3: Application, upgrades and data backup

检查清单

• Identify the exact controller and included accessories.
• Capture software, firmware, hardware and SDK versions.
• Verify communication boards, roles and configuration files.
• Demonstrate required interfaces in the intended environment.
• Confirm authorised account access and project editability.
• Obtain a documented backup and recovery package.
• Agree update, compatibility and support responsibilities.
• Compare delivered equipment against the accepted schedule.

常见问题