For system integratorsFAQ


Q What is ORiN?
A ORiN (Open Resource Interface for the Network) is a specification of standard middleware for factory information systems established by ORiN Consortium. It is currently commercialized as ORiN2 SDK, which enables integrated connections of PC application software with no need to adapt to manufacturer-specific access methods for FA devices (such as robots, PLC and NC machine tools).
Q Why has ORiN been developed?
A While industrial robots and machines play key roles in the automation of factories, they are now commonly compatible with networks, making it possible to perform their production management, equipment diagnosis, etc., on PCs with access to the data managed by devices. However, the specifications of the networks connecting PCs and devices (such as media and protocols), as well as mechanisms for using them (such as API specifications to check and connect communication types), were specific to manufacturers and the establishment of systems to combine different communications specifications involved enormous cost and labor.
In this context, ORiN (Open Resource Interface for the Network) was created to serve as an open interface that enables integrated access to devices in a network environment, irrespective of manufacturer or model.
Q What technology is used in ORiN?
A ORiN provides an interface to access industrial robots and machines, involving two modules, namely an interface for applications (engine) and an interface for devices (provider). The engine has the same functions as a standard program interface and provides an application development environment with no need to consider differences between devices. The provider has a communications interface to connect various industrial machines with PCs and absorbs differences between communications specifications, which are different between machines, to offer an integrated access means to high-level applications.
With this technology, application vendors can develop client applications without dependence on industrial machines, and manufacturers can disclose the functions of devices without dependence on client applications.
Q What are clear distinctions between the specifications of ORiN1 and ORiN2?
A The specifications of ORiN1 cover monitoring systems (I/O and variables) only. The specifications of ORiN2 have been further developed from those of ORiN1 to also cover control systems (MOVE, etc.).
Q To what devices can ORiN be connected?
A ORiN can be connected to robots, PLC, processing machines, cameras, sensors and other devices and equipment. It can also be coordinated with cloud and other standards (such as Edgecross, FIELD system, OPC, OPC UA, MQTT, ROS, EtherCAT, FL-net and Modbus).
Q What applications can potentially use ORiN?
A The following applications may use ORiN:
1. Production management system (display of the operation status of equipment)
Display data on the productivity of equipment (e.g. production number, operation time). 2. Equipment operation monitor (simple simulation function)
Visualize equipment operation (3D graphics) and I/O operation on PCs. 3. Facility maintenance and diagnosis system
Collect and analyze data on the control of equipment (present values, current values) in case of abnormality. 4. Analysis of processing and assembly data
Measure and analyze external sensor data (accuracy, variations between products, etc.). 5. Switching of equipment operation
Activate programs and change variables and I/O via PCs. 6. Transmission of operation commands
Directly send operation commands from PCs. 7. Automatic program update
Automatically download programs from PCs when necessary.
Q What effects can be expected from the introduction of ORiN?
A The following economic effects can be expected:
1. Improvement of manufacturing competitiveness
Conversion of know-how into data helps improve production technology. You can also achieve higher product quality and productivity through automation, which will enhance your international manufacturing competitiveness. 2. Expansion of the robot market
It is anticipated that the introduction will expand the processes to which robots can be applied and also promote the growth of the robot market. 3. Software industry entry into the robot market
You can create applications to be shared between robots from different companies on PCs, which can allow the software industry to enter the field of applications for robots. As a result, the software resources that have been developed in various areas can be effectively used in the field of robotics as well.4. Creation of the robot engineering industry
Creating a common communications environment on PCs means that you can create new robotics service sectors, including robotic engineering and consultation services for introducing robots, independently of robot manufacturer. Those sectors also have the potential to interact and produce synergetic economic effects.
Q What do we have to do to use ORiN?
A Middleware called ORiN2 SDK is sold by Denso Wave Incorporated, a member of ORiN Consortium. Application developers can use this product to develop applications compatible with ORiN. In addition, Provider Wizard as part of the product can be used to develop original providers.
Q What programming languages can be used for development with ORiN?
A Development uses the programming languages used in Windows. As examples, sample programs written in Visual Basic, Visual C++, Delphi, Java, VBA, LabVIEW and other languages are included in ORiN2 SDK.
Q As general-purpose programming languages are used for development, what level of programming abilities is required?
A Excel Macro and higher skills, or knowledge of programming in Visual Basic, Visual C++ and other languages, are essential. As the development of more advanced applications requires corresponding programming knowledge, you may decide to outsource the development to professional software developers.
Q When the Python script language is used, can FA devices be controlled by using ORiN2 SDK?
A It’s only necessary to install ORiN2 SDK to control programs if Python can operate in Windows to call COM in the environment.
Q When the LabVIEW development language is used, can FA devices be controlled by using ORiN2 SDK?
A It is possible if the package has been developed for Windows. It’s only necessary to install ORiN2 SDK to control programs if LabVIEW can operate in Windows to call COM in the environment.
Q Are there any sample programs using ORiN?
A When ORiN2 SDK is installed, sample programs are stored in a specified location.
Q How are providers offered?
A Some providers are offered as standard components of ORiN2 SDK while others are offered by members of ORiN Consortium.
Q What are specific distinctions between the binary programs and source programs included in the list of providers?
A Binary programs refer to DLL (dynamic link library) files of providers and can be readily used as providers. Source programs refer to program files (C++) of providers and you can correct and extend providers with them.
Q When a provider is developed, how is it implemented?
A A model is prepared with Provider Wizard and implemented according to the manual. As dynamic binding is applicable, you can perform programming like designing dedicated API.
Q How long (in man-hours) does it take to develop a provider?
A In general, it takes three to seven days for creation, including the period for testing. However, the man-hours required might increase with reduced knowledge of devices, independently of programming skills.
Q Where will the developed providers be embedded?
A They are embedded (stored) on the PC to be used (the PC on which ORiN2 SDK is installed).