Go Back | Back to KitCAD2.exe | Configure
Real-time KP2 Scada HMI help page.
Help and Information for kphmi.exe and kphmi_client.exe applications.
Download hmic.zip and Extract to C:\ (with 'restore to folder' option selected)
The HMI SCADA example here is used for Tracking multiple Objects as Jobs in a specific KP2 file for alocating floor space to Job numbers.
For KP2 users the File= command relates to jobs in a work system, and not KPD object items of parts of a drawing (So a Job may aquire floor space consideration).
No Tracking example for parts is offered with this HMI SCADA system but the example can altered and employed on a per-KP2 file basis (design files with KPD File= commands) to track parts at verious work stations, within each job.
The SCADA HMI version of this interface allows administrators to view the progress of work, or in general keep tabs on a job.
Both Client and Server are designed to be run 24/7.
The Server displays controls (15 x 4 = 60 in total) that can be configured to suit a working environment using TXT and BMP file formats.
The Server has a external web page for easy linking to existing formats of communication/s.
The Client side of this application can vary from use and environment where clients are installed on Network locations. The example included here is in relation to KitCAD2 uses; these files required some information to be included as an example.
The demo client software example known as kphmi_client.exe, kphmi_client and [inf config link] may be located in the C:\Program Files\Kitchen\hmic\ sub-folder [link].
The demo server software example known as kphmi.exe, kphmi and [inf config link] may be located in the C:\Program Files\Kitchen\scada\ sub-folder [link].
A web link page can be located in the C:\Program Files\Kitchen\scada\html\ sub-folder [link].
These applications help track parts for a KP2 file through the manufacturing processes. An advantage of using KP2 file types is that of conversion to 3D or RSS output formats.
These applications do not load or save KP2 or RSS formatted files. For network congestion and update rate default is set to 35 seconds; it is advised that no more then 15 controls be loaded on any-one server exe or machine.
Due to the use of KP2 KitCAD 2 files this limitation (described above) of 15 controls can be over-come, these applications update KP2 file types that can be used to generate additional infromation like 3D maps to RSS feeds.
To resolve such issues another server application is required to run the next group of controls from 15-30, etc. (it should be noted that work-stations by default do not move).
The configuration of the HMI server allows a different process where collected information from gathered 'down-stream' can be viewed 'up-stream' with KitCAD2 applications.
These files do not communicate with external devices. It is intended that KERMIT, MODBUS, RS-32, RS, RTU, ASCII communication be used for requirements of administration where actual control is needed over systems processes.
To implement with KERMIT as an example: a MSDOS batch can be created to copy a default of STATION.txt file in allowing a changed status at the begining of a process; and to end in replacement of previous file. This kind of administration can be achived using the web page (when modified to suit) link option of the HMI server version.
The server has a limit of 15 controls (in line with RSS 0.91) shown on its application interface - each one of these
icons is a symbol of a known process/work station.
Each client version of this process can modify/create object item part locations within a KP2 job file.
Each server version of this process can modify/create object item locations within a KP2 job file (if a process moves the workstation to new location).
For the terms of MODBUS in this section, the text defines a relation between allowing advanced
users communication with external devices. MODBUS is one protocol of many but seems to be one of
the most documented - another RFID devices support other protocols, and many environments have existing BARCODE systems - apart from well documented
protocols like RFC2839 for INTERNET KERMIT, and RFC2840 for TELNET KERMIT whose function is varied
somewhat to the end use of protocols like that of MODBUS, RIFF, and BARCODE reader devices.
This informaion is supplied to aid in the deployment of such systems.
Updated on the 02nd of October, 2005.