MERRICK Genetix GCM Configuration And Troubleshooting Manual

Genetix GCM Configuration and Troubleshooting for DF-1
Both serial ports in a Genetix GCM can be configured to support Allen-Bradley DF-1 point to
point protocol. This allows for establishing direct communications to Allen-Bradley PLCs, using
•
Ch0, usually the built-in serial port,
•
DeviceNet using the 1761-NET-DNI interfaces,
•
EtherNet/IP using 1761-NET-ENI interfaces, or
•
Data Highway Plus using KF2 or similar interfaces.
We currently support all methods described above.
The host can take control over and/or monitor the GCM, using CIT data table exchange. For
details of the CIT structure, see
System Requirements
All versions of the Merrick Genetix GCM controller support Allen-Bradley (A-B) DF-1 Serial
Communications protocol and exposes a standardized Common Interface Table (CIT),
compatible with the A-B "Common Interface File" (CIF) specification. PCCC functions 1 (PLC2
Unprotected Read, 485CIF Read), 8 (PLC2 Unprotected Write, 485CIF Write) and 6 (PLC-2
Diagnostic Status) are supported.
The physical interface is normally 3-wire RS232, but 4-wire RS-422 can also be used. The host
or interface is assumed to maintain a cyclic conversation with the GCM, which exposes a
Common Interface Table (CIT), making it possible to monitor and/or supervise the GCM
completely.
Different data types are used for control/status bits, integer numbers and floating-point numbers.
Control/Status bits and Integer numbers are organized in 16 bit words. Parameters are organized
as IEEE 32 bit floating point numbers, located in two consecutive 16 bit words. For PLC's that
don't support floating point numbers, it is possible to split parameters into two 16 bit integers, one
containing the integer part and one containing the fractional part multiplied by 10,000 (four
implied decimal places).
Configuring the GCM
Configuring the GCM includes setting up communications parameters, register tags, warnings,
faults and external inputs and outputs. The register tags are set to make any internal GCM
parameter appear in Tag 1 R to Tag 5 R values. Standard feeder parameters are always
available. Warnings and faults are user preference qualified, associated with any logical I/O point
in the GCM. This configuration is done regardless if communications is used or not. Any logical
inputs you want to control from the PLC must be mapped to a network input. In the same way,
logical outputs must be mapped to network outputs for monitoring purposes.
It is recommended that you use the built in Terminal Monitoring and Configuration Interface
(TMCI) for setting up, troubleshooting and monitoring the DF-1 interface.The following menu
references and screen shots were taken using the GCM 101.1.6.8 Belt Feeder Controller
application. Operation and Maintenance Manuals as well as register specifications are available
at the Merrick Web Site:
http://www.merrick-inc.com/mct/GENApps/GENApps.htmTo enable network control parameters,
set Advanced Setup, Configuration, Network IO to Y.
http://www.merrick-inc.com/mct/GCMDF1.pdf
Genetix GCM Configuration and Troubleshooting for DF-1
http://www.merrick-inc.com/mct/CIT.PDF
Page 1
Merrick Industries, June 2011
2011-06-14/Lars