This manual explains how to use MiniOCS / MiniRCS / SmartStix.
Copyright (C) 2003 Hor ner APG, LLC., 640 North Sherman Drive Indianapolis, Indiana 46201. All rights
reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval
system, or translated into any language or computer language, in any form by any means, electronic,
mechanical, magnetic, optical, chemical, manual or otherwise, without the prior agreement and written
permission of Horner APG, Inc.
All software described in this document or media is also copyrighted material subject to the terms and
conditions of the Horner Software License Agreement.
Information in this document is subject to change without notice and does not represent a commitment on
the part of Horner APG.
Cscape, SmartStix, and CsCAN are trademarks of Horner APG.
DeviceNet is a trademark of the Open DeviceNet Vendor Association (OVDA), Inc.
Ethernet is a trademark of the Xerox Corporation.
For user manual updates, contact Horner APG Technical Support
Division, at (317) 916- 4274 or visit our website at www.heapg.com.
PAGE 4 15 MAR 2003 PREFACE
MAN0305-04
LIMITED WARRANTY AND LIMITATION OF LIABILITY
Horner APG,LLC. ("HE-APG") warrants to the original purchaser that the MiniOCS/RCS/SmartStix manufactured by
HE-APG is free from defects in material and workmanship under normal use and service. The obligation of HE-APG
under this warranty shall be limited to the repair or exchange of any part or parts which may prove defective under
normal use and service within two (2) years from the date of manufacture or eighteen (18) months from the date of
installation by the original purchaser whichever occurs first, such defect to be disclosed to the satisfaction of HE-APG
after examination by HE-APG of the allegedly defective part or parts. THIS WARRANTY IS EXPRESSLY IN LIEU
OF ALL OTHER WARRANTIES EXPRESSED OR IMPLIED INCLUDING THE WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR USE AND OF ALL OTHER OBLIGATIONS OR LIABILITIES AND HEAPG NEITHER ASSUMES, NOR AUTHORIZES ANY OTHER PERSON TO ASSUME FOR HE-APG, ANY OTHER
LIABILITY IN CONNECTION WITH THE SALE OF THIS MiniOCS/RCS/SmartStix. THIS WARRANTY SHALL NOT
APPLY TO THIS MiniOCS/RCS/SmartStix OR ANY PART THEREOF WHICH HAS BEEN SUBJECT TO
ACCIDENT, NEGLIGENCE, ALTERATION, ABUSE, OR MISUSE. HE-APG MAKES NO WARRANTY
WHATSOEVER IN RESPECT TO ACCESSORIES OR PARTS NOT SUPPLIED BY HE-APG. THE TERM
"ORIGINAL PURCHASER", AS USED IN THIS WARRANTY, SHALL BE DEEMED TO MEAN THAT PERSON FOR
WHOM THE MiniOCS/RCS/SmartStix IS ORIGINALLY INSTALLED. THIS WARRANTY SHALL APPLY ONLY
WITHIN THE BOUNDARIES OF THE CONTINENTAL UNITED STATES.
In no event, whether as a result of breach of contract, warranty, tort (including negligence) or otherwise, shall HEAPG or its suppliers be liable of any special, consequential, incidental or penal damages including, but not limited to,
loss of profit or revenues, loss of use of the products or any associated equipment, damage to associated equipment,
cost of capital, cost of substitute products, facilities, services or replacement power, down time costs, or claims of
original purchaser's customers for such damages.
To obtain warranty service, return the product to your distributor with a description of the problem, proof of
purchase, post paid, insured and in a suitable package.
ABOUT PROGRAMMING EXAMPLES
Any example programs and program segments in this manual or provided on accompanying diskettes are included
solely for illustrative purposes. Due to the many variables and requirements associated with any particular
installation, Horner APG cannot assume responsibility or liability for actual use based on the examples and diagrams.
It is the sole responsibility of the system designer utilizing the MiniOCS/RCS/SmartStix to appropriately design the
end system, to appropriately integrate the MiniOCS/RCS/SmartStix and to make safety provisions for the end
equipment as is usual and customary in industrial applications as defined in any codes or standards which apply.
Note: The programming examples shown in this manual are for illustrative
purposes only. Proper machine operation is the sole responsibility of the
system integrator.
PREFACE 15 MAR 2003 PAGE 5
MAN0305-04
REVISIONS TO THIS MANUAL
This version (MAN0305 -04) of the Mini Hardware Manual contains the following revisions, additions, and
deletions:
1. Removed Mini data sheets from the back of this manual and moved them into a new manual.
Revised Section 1.5: Additional References.
2. Revised Section 1.1. to include the SmartStix product line.
The Mini Hardware User Manual provides information about the following products:
a. MiniOCS (HE500OCSxxx)
MiniRCS (HE500RCSxxx)
The specifications, installation, and configuration procedures of the Operator Control Station (OCS) and
the Remote Control Station (RCS) are covered in detail in this user manual. Information is also provided
for the use of the products in CsCAN and DeviceNet Networks.
Note: Mini data sheets are now located in their own manual. (Refer to Additional References on page
18).
b.SmartStix Modules for CsCAN Networks(HE550xxxxxx).
SmartStix is a family of remote products for the OCS. This manual covers programming information for
SmartStix used in CsCAN networks.
Figure 1.1 - Front View of MiniOCS (Shown on Door in Panel Box)
1.2 MiniOCS and MiniRCS Product Description
1.2.1 Functions and Features
The MiniOCS provides controller, I/O, operator interface, and optional networking capabilities in one unit.
The MiniRCS has the same functionality as the MiniOCS except that it does not have local operator
interface capabilities. Both the MiniRCS and the MiniOCS support a remote operator interface through a
PC connected to the Mini unit’s built-in network or serial port. The remote operator interface (Remote
Text Terminal) is particularly useful when using the MiniRCS, which does not have a physical front panel
screen or keypad.
The MiniOCS is mounted in a panel door; the MiniRCS is designed for backplate mounting. Both the
MiniOCS and the MiniRCS can be used in CsCAN or DeviceNet networks. To use the MiniRCS in a
DeviceNet network, a DeviceNet file can be downloaded from Cscape’s Firmware Update Wizard.
PAGE 10 15 MAR 2003 CH.1
MAN305-04
A variety of MiniOCS / MiniRCS models are available. Each model comes equipped with one factory
installed I/O board. Models of the MiniOCS / MiniRCS, which vary according to the type of I/O board
installed, are available in non-network and network versions. Network versions contain an additional
connector allowing connectivity to networks.
MiniOCS / MiniRCS devices have Serial and CAN (Controller Area Network) communication abilities.
The units contain a standard 9-pin RS -232 port for programming/debugging, monitoring and network
administration from an IBM -compatible PC. MiniOCS / MiniRCS models, which have built-in networking
capabilities, use CsCAN (pronouned “Sea-scan”) protocol and standard CAN network hardware. CANbased network hardware is used in the controllers because of CAN’s automatic error detection, ease of
configuration, low-cost of design and implementation and ability to operate in harsh environments. The
MiniOCS / MiniRCS can also be used in DeviceNet networks. Networking abilities are built-in to the
MiniOCS / MiniRCS and require no external or additional modules. When several MiniOCS / MiniRCS
units are networked together to ac hieve a specific purpose, the system acts like a large parallelprocessing controller.
The MiniOCS / MiniRCS have standard features consisting of the following:
• 24 VDC powered • Integrated Bezel
• One Internal I/O Module • Real-Time Clock
• RS-232 Programming Port • Flash Memory for easy field upgrades
1.2.2 Cscape Software
Cscape Software (pronounced “Sea -scape”) is used with the MiniOCS / MiniRCS, OCS, and RCS
products. (The part number for Cscape is HE500OSW232.) Cscape stands for Control Station Central
Application Programming Environment. The Windows -based software package is easy to use and aids in
the integration of a CAN-based Distributed Control System. The program is used for configuring
controllers and I/O Modules. Cscape is also used for programming MiniOCS / MiniRCS ladder logic,
programming user displays for the MiniOCS, configuring the network for global digital and analog data,
setting system-wide security and monitoring controllers in the system. Provided there is one serial connection to one node on the network (i.e., CsCAN Network), the operator has control over the entire
system. The operator can upload, download, monitor and debug to any node on the network.
CH.1 15 MAR 2003 PAGE 11
MAN0305-04
1.2.3 MiniOCS / MiniRCS Specifications
TBD = To Be Determined
Table 1.1 – Physical Specifications
MiniOCS and MiniRCS
Operating Temperature*
Humidity 5% to 95% non-condensing
NEMA Rating NEMA 4X
Primary Power Range 10-30VDC
Mini OCS Mini RCS
Maxim um Power Draw (Non-network
Version)
Maximum Power Draw (Network
Version)
Maximum Inrush Current ((Nonnetwork Version)
Maximum Inrush Current (Network
Version)
Ladder Execution
Typical Execution Speed
CAN Power Range 12 – 25 VDC
CAN Power Current 75mA maximum
Serial Standard 9 pin RS-232 for programming, monitoring, and network
CAN CsCAN Network / DeviceNet
Input / Output One factory -installed I/O board per model
Keypad 10 user-programmable keys + , Esc, Enter and 4 direction keys
(* Although the MiniOCS / MiniRCS withstands the temperature range of 0°C
to +60°C, such temperatures can decrease the life of the display. The
recommended rating is 0°C to +50°C.)
200mA max. @ 24VDC
200mA max. @ 24VDC
900mA max. @ 24VDC for 1mS
900mA max. @ 24VDC for 1mS
2.0ms. per 1K of Boolean logic.
administration from a IBM compatible PC
Faceplate made of Marnot XL Polyester by Tekra.
Please refer to Compliance Table located at
http://www.heapg.com/Support/compliance.htm
(approximately 2.75” [69.85] including Ground Screw extension)
(approximately 2.33” [59.18] including Ground Screw extension)
0°C to +50°C*
To Be Determined
To Be Determined
To Be Determined
To Be Determined
PAGE 12 15 MAR 2003 CH.1
MAN305-04
1.3 MiniOCS / MiniRCS Resources
1.3.1 Overview
This section defines the resource limits that a programmer needs to know when writing a program using
the MiniOCS / MiniRCS.
A MiniOCS / MiniRCS combine local I/O (analog and digital), networking, and controller, into a single
product. The MiniOCS also provides an operator interface (display and keypad). The controller portion of
the MiniOCS / MiniRCS is programmed in ladder logic via the Windows -based Cscape (Control Station
Central Application Programming Environment) package. Each MiniOCS / MiniRCS provide a set of
resources for use by the ladder logic control program as indicated in Table 1.2. The table shows the
resources available in MiniOCS / MiniRCS products. Note that although each register type inherently
consists of either 1-bit or 16-bit registers, all registers can be accessed via User Screens and/or Ladder
Code as 1, 8, 16 or 32-bit values or as ASCII character strings.
The faceplate is made of Marnot XL Polyester by Tekra. The material is
Keypad
Local MiniOCS Display / Remote Text Terminal for MiniRCS and MiniOCS
Display
Screen Memory 64K Items Per Text Table 20
User Screens 200
Data Fields Per
User Screen
resistant to most corrosive substances found in industrial environments. The
material also holds up well in most industrial conditions. If used outdoors, the
materials can yellow or crack.
2x20 Characters
(Text LCD)
10
None / CsCAN / DeviceNet
16 Keys (Membrane)
Text Tables 200
Ladder Code 64K
CH.1 15 MAR 2003 PAGE 13
MAN0305-04
1.3.2 Resource Definitions
This section defines the resources listed in Table 1.2.
System Registers
System Registers (%S and %SR) are used to store general OCS or RCS status information. This
information is used internally, and is also available to the operator via the System Menu, using the Control
Station’s display and keypad. The System Registers are also available for User Screens and can be
accessed by Ladder Code.
a. %S Registers
%S Registers are 1-bit memory loc ations, containing system status information, implemented as shown in
Table 1.3:
Table 1.3 - %S Registers
Register Name Description
%S1 FST_SCN On during first scan after entering RUN mode
%S2 NET_OK On if Network is functioning properly
%S3 T_10MS On for 5 mS; Off for 5 mS
%S4 T_100MS On for 50 mS; Off for 50 mS
%S5 T_SEC On for 500 mS; Off for 500 mS
%S6 IO_OK On if SmartStack I/O is configured properly
%S7 ALW_ON Always On
%S8 ALW_OFF Always Off
b. %SR Registers
%SR Registers are 16-bit memory locations, containing system status information, implemented as
shown in Table 3. Note: Where 2 %SRs are combined to make a 32-bit value, the lower numbered %SR
is the low word, while the higher numbered %SR is the high word.
Table 1.4 - % SR Registers
Register Name Description Min Max
%SR1 USER_SCR Current User Screen Number (0=none) 0 200
%SR2 ALRM_SCR Current Alarm Screen Number (0=none) 0 200
%SR3 SYS_SCR Current System Screen Number (0=none) 0 11
%SR4 SELF_TEST Bit-Mapped Self -Test Result 0 65535
%SR5 CS_MODE
%SR6 SCAN_RATE Average Scan Rate (in tenths of mS) - 1000
%SR7 MIN_RATE Minimum Scan Rate (in tenths of mS) - 1000
%SR8 MAX_RATE Maximum Scan Rate (in tenths of mS) - 1000
%SR9-10 EDIT_BUF Data Field Edit Buffer 0 232-1
%SR11-12 LADDER_SIZE Ladder Code Size 2 64K
%SR13-14 UTXT_SIZE User Text Screen Table Size 4 64K
%SR15-16 Reserved - - %SR17-18 IO_SIZE I/O Configuration Table Size 16 64K
%SR19-20 NET_SIZE Network Configuration Table Size 34 32K
%SR21-22 SD_SIZE Security Data Table Size - %SR23 LADDER_CRC Ladder Code CRC 0 65535
%SR24 UTXT_CRC User Text Screen Table CRC 0 65535
%SR25 Reserved - - %SR26 IO_CRC I/O Configuration Table CRC 0 65535
%SR27 NET_CRC Network Configuration Table CRC 0 65535
Control Station Mode
(0=Idle, 1=Do I/O, 2=Run)
0 2
PAGE 14 15 MAR 2003 CH.1
MAN305-04
Table 1.4 - % SR Registers
Register Name Description Min Max
%SR28 SD_CRC Security Data Table CRC 0 65535
%SR33 FKEY_MODE Function Key Mode (0=Momentary; 1=Toggle) 0 1
%SR34 SERIAL_PROT
%SR35-36 SERIAL_NUM This Station’s 32-bit Serial Number 0 232-1
%SR37 MODEL_NUM This Station’s Binary Model Number 0 65535
%SR38 ENG_REV Main CPU Engine Firmware Rev Number x 100 0000 9999
%SR39 BIOS_REV Main CPU BIOS Firmware Rev Number x 100 0000 9999
%SR40 FPGA_REV FPGA Image Rev Number x 10 000 255
%SR41 LCD_COLS
%SR42 LCD_ROWS
%SR43 KEY_TYPE
%SR44 RTC_SEC Real-Time-Clock Second 0 59
%SR45 RTC_MIN Real-Time-Clock Minute 0 59
%SR46 RTC_HOUR Real-Time-Clock Hour 0 23
%SR47 RTC_DATE Real-Time-Clock Date 1 31
%SR48 RTC_MON Real-Time-Clock Month 1 12
%SR49 RTC_YEAR Real-Time-Clock Year 1996 2095
%SR50 RTC_DAY Real-Time-Clock Day (1=Sunday) 1 7
%SR51 NET_CNT Network Error Count 0 65535
%SR52 WDOG_CNT Watchdog-Tripped Error Count 0 65535
%SR53-54 BAD_LADDER Bad Ladder Code Error Index 0 65534
%SR55 F_SELF_TEST Filtered Bit -Mapped Self-Test Result 0 65535
%SR56 LAST_KEY Key Code of Last Key Press or Release 0 255
%SR57 BAK_LITE LCD Backlight On/Off Switch (0=Off; 1=On) 0 1
%SR58 USER_LEDS User LED Control / Status 0 65535
%SR59 S_ENG_REV Slave CPU Engine Firmware Rev Number x 100 0000 9999
%SR60 S_BIOS_REV Slave CPU BIOS Firmware Rev Number x 100 0000 9999
%SR61 NUM_IDS This Station’s Number of Network IDs (CsCAN) 1 253
This Station’s Number of Network IDs (DeviceNet) 1 1
%SR62-192 Reserved - - -
This Station’s Primary Network ID (CsCAN) 1 253
This Station’s Primary Network ID (DeviceNet) 0 63
Network Baud Rate (CsCAN)
LCD Text Display Number of Columns 20 20
LCD Graphics Display Number of Columns 240 240
LCD Text Display Number of Rows 2 4
LCD Graphics Display Number of Rows 128 128
Keypad Type
(0=16 Keys; 1=17 Keys; 2=32 Keys; 3=36 Keys)
0 3
0 2
0 3
0 4
0 3
CH.1 15 MAR 2003 PAGE 15
MAN0305-04
User Registers
User Registers (%T, %M and %R) are used to store application-specific Mini data. This data can be
accessed via User Screens and/or by Ladder Code.
a. %T Register
A %T Register is a non -retentive 1-bit memory location, used to store application-specific state
information.
b. %M Registers
A %M Register is a retentive 1-bit memory location, used to store application-specific state information.
c. %R Registers
A %R Register is a retentive 16 -bit memory location, used to store application-specific values.
HMI Registers
HMI Registers (%K and %D) give the user access to the OCS or RCS keypad and display.
The MiniOCS has a membrane keypad and text-based LCD display, allowing the operator to enter and
display general and application -specific information. This same information can be entered and displayed
for the MiniRCS (and MiniOCS if desired) via a remote PC using Cscape’s Remote Display Terminal
function.
a. %K Registers
A %K Register is a non -retentive 1-bit memory location (contact), used to store the state of a function key
on the Control Station’s keypad. If the function keys are set for momentary mode, a function key’s
associated %K register will be ON as long as the function key is pressed. If the function keys are set for
toggle mode, a function key’s associated %K register will toggle each time the function key is pressed.
b. %D Registers
A %D Register is a non-retentive 1-bit memory location (coil), which can be turned ON by Ladder Code to
cause the corresponding User or Alarm Screen to be displayed.
c. User Screens
A User Screen is a combination of fixed text or graphics, along with variable Data Fields (called Graphics
Objects in the MINIOCS), which together fill the LCD display screen. These screens are defined via
Cscape di alogs and are then downloaded and stored into the Control Station’s Flash memory. User
Screens can be selected for display by operator entries on the keypad, or by Ladder Code.
d. Data Fields
A Data Field is an area on a User Screen where variable data is displayed and edited. The source data
for a Data Field can be any of the Control Station’s Register resources as defined above. The field size
and display format is programmable via Cscape dialogs.
PAGE 16 15 MAR 2003 CH.1
MAN305-04
e. Text Tables
A Text Table is a list of Text Items, which can be used in a Data Field, to display descriptive words and
phrases to describe the value of a Register, instead of displaying numeric values. A simple example of
this, would allow the strings “OFF” and “ON” to be displayed, instead of 0 and 1, to describe the state of
the %I4 digital input. The maximum number of Text Tables and Text Items per Text Table is shown in
Table 1, but the number can be further limited by overall User Screen memory usage.
Physical I/O Registers
Physical I/O Registers (%I, %Q, %AI and %AQ) give the user access to the Physical I/O Module
data. This data can be accessed via User Screens and/or by Ladder Code.
a. %I Registers
A %I Register is a 1-bit memory location, which is normally used to store the state of one of the digital
inputs associated with a Physical I/O module. When used in this way, %I registers are non -retentive. All
extra %I registers, which are not associated with physical inputs, are retentive, and can be used just like
%M registers.
b. %Q Registers
A %Q Register is a non-retentive 1-bit memory location, which is normally used to store the state of one
of the digital outputs associated with a Physical I/O module.
c. %AI Registers
A %AI Register is a 16 -bit memory location, which is normally used to store the value of one of analog
inputs associated with a Physical I/O module. When used in this way, %AI registers are non -retentive.
All extra %AI registers, which are not associated with physical inputs, are retentive, and can be used just
like %R registers.
d. %AQ Registers
A %AQ Register is a non-retentive 16-bit memory location, which is normally used to store the value of
one of the analog outputs associated with a Physical I/O module.
Global Data I/O Registers
Global Data I/O Registers (%IG, %QG, %AIG and %AQG) give the user access to the Network Port’s
Global I/O data. This data can be accessed via User Screens and/or by Ladder Code.
a. %IG Registers
A %IG Register is a retentive 1-bit memory location, which is normally used to store a global digital state
obtained from another Control Station on the network.
b. %QG Registers
A %QG Register is a retentive 1-bit memory location, which is normally used to store a digital state to be
sent as global data to the other Control Stations on the network.
CH.1 15 MAR 2003 PAGE 17
MAN0305-04
c. %AIG Registers
A %AIG Register is a retentive 16-bit memory location, which is normally used to store a global analog
value obtained from another Control Station on the network.
d. %AQG Registers
A %AQG Register is a retentive 16 -bit memory location, which is normally used to store an analog value
to be sent as global data to the other Control Stations on the network.
e. Network Port
The CsCAN Network is based on the Bosch Control Area Network (CAN), and implements the CsCAN
Protocol which is designed to take maximum advantage of the global data broadcasting capability of
CAN. Using this network protocol, up to 64 Control Stations can be linked without repeaters, and up to
253 Control Stations can be linked by using 3 repeaters. For more information regarding CsCAN
Protocol, refer to the CsCAN Protocol Specification document.
DeviceNet is an “open” higher layer protocol, which is supported by products from multiple vendors. In an
OCS or RCS, DeviceNet can be loaded as a replacement for the CsCAN Protocol Message Layer, and as
a result, the OCS or RCS becomes a DeviceNet Slave device. Note that the Mini still implements the
CsCAN Protocol Command Layer with respect to the RS -232 programming port. For more information
regarding DeviceNet Protocol, contact the DeviceNet governing body (ODVA).
Ladder Code
The Ladder Code, stores ladder instructions generated by Cscape. This Ladder Code is downloaded and
stored into the Control Station’s Flash memory, to be executed each controller scan, when the controller
is in RUN mode.
1.4 MiniOCS / MiniRCS Models
Because there are several models of MiniOCS / MiniRCS models available, the MiniOCS / MiniRCS can
be used in a wide range of applications. The MiniOCS consists of an Operator Control Station, and the
MiniRCS consists of a Remote Control Station. Each model comes equipped with one factory installed
I/O board. The models vary according to the type of I/O board installed and are available in non-network
and network versions. Network versions contain an additional connector allowin g connectivity to CAN
networks. Refer to Additional References on page 18 to locate model-specific information for each Mini.
PAGE 18 15 MAR 2003 CH.1
MAN305-04
1.5 Additional References
For further information regarding products covered in this manual, refer to the following references:
a. Mini I/O (MAN0581) – Contains a collection of individual data sheets covering model-specific
information.
b. DeviceNet Implementation Using Control Station Modules (SUP0326) - Covers the
implementation of Control Station products in a DeviceNet network.
c. Cscape Reference Manual (MAN0313) – Contains topics specifically selected to assist you
through the programming process.
1.6 Technical Support
For user manual updates, contact Technical Services at the following locations:
North America:
(317) 916 -4274
www.heapg.com
Europe:
(+) 353-21-4321-266
www.horner-apg.com
CH.2 15 MAR 2003 PAGE 19
3 3/16
MAN0305-04
CHAPTER 2: INSTALLATION
2.1 MiniOCS Mounting Requirements
2.1.1 MiniOCS Mounting Procedures (Installed in a Panel Door)
The MiniOCS is designed for permanent panel mounting. To install the MiniOCS, follow the instructions
below.
1. Prior to mounting the MiniOCS, observe requirements for the panel layout design and adequate
clearances. A checklist is provided on page 25.
2. Cut the host panel as described in the Figure 2.1 - Figure 2.6.
Warning: Make sure the power and network connectors are removed from the MiniOCS.
3. Insert the MiniOCS through the panel cutout (from the front). The gasket material needs to lie
between the host panel and the MiniOCS panel.
4. Install and tighten the mounting clips (provided with the MiniOCS) until the gasket material forms a
tight seal. (See Figure 2.7.)
Caution: Do not over-tighten. Over-tightening can potentially damage the case.
5. Connect the communications, programming, and power cables to the MiniOCS ports using the
provided connectors.
6. Begin configuration procedures for the MiniOCS models.
2.1.2 MiniOCS Dimensions and Panel Cut -outs
80.96mm
Programming Port
Figure 2.1 –Right-end View Network Model Figure 2.2 - Left-end View Network Model