OSACA JOP OMAC

1
OSACA / JOP / OMAC
Cooperative Project
Global HMI API
2
Background

• Improve international cooperation among open
  control organizations at the three regions
• initiated in the June, 98 Meeting in Tokyo
• definition of a common Human Machine Interface
  (HMI) to controller API standard
• CNC focus initially, easily extended for other
  control applications
• Short-term Focus
• Targeted for PC front-end to CNC applications

3
Objectives

• Achieve one common HMI and controller API set for
  all controllers
• reduce the development effort that is necessary
  to interface between PC HMIs with different
  controllers
• reduce end users costs
• suppliers compete based on product features, cost
  advantages, capabilities etc
• Reduce control vendors resource requirements to
  develop their own proprietary API standards and
  promote their usage

4
Scope of the Project

• HMI Set should be valid for the following
  architectures
• PC-based HMI to Proprietary Controller
• Integrated PC-based HMI and PC-based Controller
• Proprietary HMI to PC-based Controller
• The HMI to Controller API specification defines a
  software interface and should be physical network
  independent
• Do not define display screens and input devices

5
Features (1)

• Software and hardware neutral to ensure technical
  innovations
• Support the following major functional areas
• Operator Interface
• Maintenance
• File Management
• Configuration Control
• OEM Specifics

6
Features (2)

• Operator Interface
• Functions to support the displays of controller
  information and the initiations of machine
  operation commands
• Does not include functions to display information
  or gather inputs.
• Maintenance
• Functions to facilitate the diagnostics of
  machine behaviors
• Does not include specifications on how to perform
  diagnostic functions.

7
Features (3)

• File Management
• Functions to facilitate the upload and download
  of machine control programs, tool offset files,
  supplementary text and graphics, etc.
• Does not specify methods on how to accomplish
  upload, download and other file management
  functions
• Configuration Control
• Functions to support the retrievals of controller
  software/firmware versions

8
Features (4)

• OEM Specifics
• Expendable and include abilities and provisions
  for OEMs to add specific I/O features when
  necessary
• enable the develop of applications which are
  specialized to particular user requirements, but
  can be used commonly for different models of NC
  controllers

9
Proposed Procedures

• Use or adopt comparable API sets are already
  available
• study the existing APIs from OMAC, OSACA and JOP
• Global Project Coordination Team and Technical
  Team

10
Current Status

• OMAC CNC HMI and Discrete Device API WG
• Dick Mathias, Jim Robinson
• OMAC / OSACA Joint Meeting
• use style guides and data structures of the OSACA
  HMI-API set as a baseline to establish a common
  API set
• review naming conventions, data structures and
  semantics from OSACA
• JOP Activities
• HILO API

11
JOP Activities Update

• HILO API has been renamed JOP Principal API (JOP
  PAPI)
• Naming conventions, data structures, and
  semantics of the preliminary version are being
  reviewed
• The API is close of being approved as Japanese
  Common API by major control vendors and machine
  tool builders
• Revised version of PAPI will be released in 2-3
  months

12
Next Steps

• OMAC HMI WG
• complete standard data structure proposal
• Proposed Global Meeting in March / April 99
• Define formal project plan
• Statements of work
• Project Schedule
• Define technical approach