These instructions do not purport to cover all details or variations in
equipment, nor to provide every possible contingency to be met during
installation, operation, and maintenance. If further information is desired
or if particular problems arise that are not covered sufficiently for the
purchaser’s purpose, the matter should be referred to GE Industrial
Systems.
This document contains proprietary information of General Electric
Company, USA and is furnished to its customer solely to assist that
customer in the installation, testing, operation, and/or maintenance of
the equipment described. This document shall not be reproduced in
whole or in part nor shall its contents be disclosed to any third party
without the written approval of GE Industrial Systems.
Table 2.2.2.3: Alarm code 6 cause .................................................................................. 34
Table 2.2.2.4: Alarm code 14 (AL_BRICKS_DP) cause ................................................... 35
Table 2.2.2.5: Alarm code 15 (AL_REGISTER) cause ...................................................... 35
Table 2.2.2.6: Alarm code 16 (AL_CCZ) cause ............................................................... 35
Table 2.2.2.7: Alarm code 22 (AL_DNET) cause ............................................................. 36
Figure 2.4.1: DGF Communication ................................................................................... 40
GEI-100430
1. GENERAL DESCRIPTION
1.1 INTRODUCTION
The optional Digital General Function Card (DGF) is mounted on the AV300i drives
for special functions such as winder/unwinder control, positioning, etc. It connects
with the drive regulation card via the connector for an optional card. The connection
with the drive also provides the power supply for the DGF.
The communication between the two cards uses a 2Kbytes dual-port ram (DPRAM).
The 6KCV301DGF card is based on an Intel 80C386EX-25 with a numerical processor
80C387SX-25.
The standard user communication on the card is RS-485 serial link.
It is possible to mount an option module with CAN controller for DeviceNet
communication.
It is also possible to read and write DGF parameters using all the drive communications
[serial link, local keypad and an additional optional communication card (e.g. GENIUS,
INTERBUS-S or PROFIBUS-DP)]. All these communications use the drive
microprocessor and DPRAM.
This manual comprises four chapters:
-Chapter 1 describes the DGF hardware. Its installation and configuration settings
are detailed. Settings for serial communications are explained.
-Chapter 2 details the software architecture of the DGF. It describes the MARTE
operating system, task organization, DGF parameters and variables, the five card
status states, and the DGF alarm conditions. Permissible data formats are described.
Drive keypad programmer operation is also described.
-Chapter 3 describes the HIBS software, which is used to download compiled user
programs to the DGF Card ; it is also used to load .BLK files (explained in chapter
4) to create supervision pages to monitor drive operation.
-Chapter 4 details .BLK file syntax. The .BLK file is an ASCII file which is used
to configure DGF DPRAM (Dual-Ported Random Access Memory) and create
supervision pages.
6
—————— Digital General Function Card ——————
6KCV301DGF
1.2 HARDWARE DESCRIPTION
The power supply is external to the card and comes directly from the drive.
The DGF is defined as the option 2 card in the drive
A module with DNet interface can be mounted on the 6KCV301DGF card, if desired.
The main 6KCV301DGF hardware characteristics are:
-Intel “embedded” 80386EX 25MHz microprocessor
-Numerical processor 80387 SX 25MHz
-Two static RAM memories (128Kword)
-A FLASH-EPROM boot block memory (256Kword)
-2 Kbytes serial EEPROM
-VPP signal 12V circuit generator for flash clear/programming
-Microprocessor supervisory circuit for supply surveillance and reset generation
-Serial link RS-485 with SLINK3 protocol.
-2 Kbytes DPRAM (Dual Port Ram)
-CPU OK (Hardware Watchdog)
-Led for PWR, RST,VPP,CPU OK, CAN and status
The following picture shows the connections between 6KCV301DGF card and the
other cards.
AV-300i Regulation cardDGF card
RV33-1
X0X0
1
1
36
36
Dnet
DeviceNet
(optional)
RS485
(S-LINK3)
Figure 1.2.1: 6KCV301DGF connections
1.2.1 MEMORY MAP
The RAM address must start at 0:0 because the vector interrupts area is in the lowest
address. The flash EPROM must be mapped on the top area because the reset address
is FFFF:0. The DPRAM is mapped at the end address of RAM area.
—————— Digital General Function Card ——————
7
GEI-100430
MEMORY MAP
FFFF:FH
FLASH EPROM
8000:0H
4800:0H
DPRAM
SRAM
Figure 1.2.1.1: 6KCV301DGF memory map
The flash EPROM boot-block programming is done once at time of manufacture.
Thereafter, all the software is downloaded using the boot code and the serial link.
The firmware is loaded starting from the first main block (8000:0H) while the data
block will be used to save parameters and block information.
DGFC-386: FLASH MEMORY MAP
4000:0H
0000:0H
FFFF:FH
BOOT BLOCK
DATA BLOCK 2
DATA BLOCK 1
MAIN BLOCK 3
MAIN BLOCK 2
MAIN BLOCK 1
MAIN BLOCK
FC00:0
FA00:0
F800:0
E000:0H
C000:0H
A000:0H
8000:0H
Figure1.2.1.2: 6KCV301DGF flash Eprom memory map
1.2.2 SERIAL LINE RS-485
The RS-485 interface allows data transfer using a two-wire twisted conductor with
shield. The transfer rate is 9.6 Kbaud. The serial link circuit is the same of the drive.
For download applications programs directly to the RS485 port, use a 6KCV300CTI
and a standard 9 pin m/f cable.A 9-socket female connector allows communication
with an external device in a multidrop configuration. The serial link may be used either
with or without signal isolation. When using signal isolation an external power supply
is necessary for 5V. This is the default configuration. The configuration without signal
isolation is possible only with short connections and with HIBS during the card
8
—————— Digital General Function Card ——————
6KCV301DGF
configuration. When you use RS-485, the line terminator resistors are connected through
S23 and S24 jumpers and must be ON only on the line end device. The protocol used
is SLINK3, detail provided in separate manuals.
X3
470R
470R
0VS
+5VS
120R
S23
S24
TXB/RXB
TXA/RXA
100R
GND
+5V
5
9
4
8
3
7
2
6
1
Figure 1.2.2.1: RS-485 interface
PinSignalDescription
1
2
3RXA/TXA (+) Positive differential I/O
4GNDS
5GNDS0V External power supply
6+5V
7RXB/TXB (-)Negative differential I/O
8GND
9+5VS5V External power supply Max 120 mA
-Reserved
Connected with pin 8 GNDS with 110 ohm for
equipotential connection
Internal +5V . You need to join with pin 9 for internal
supply
Internal GND. You need to join with pin 5 for internal
supply
d0010g
In this configuration you need to join pin 5 with pin 8 and pin 9 with pin 6 of X3
connector. DGF connectors are female connectors.
The configuration without signal isolation is possible only with short connections: for
example, with HIBS during the card configuration. On the drive, you need to use
signal isolation as described below.
Figure 1.2.2.2 shows a single-point connection between a PC or PLC RS-232 interface
and one 6KCV301DGF.
An adapter RS-232/485 is necessary to convert the PC RS-232 COM to an RS-485
signal. A simple two wire twisted cable is necessary to transmit the RS-485 differential
signals TXA/RXA - TXB/RXB.
—————— Digital General Function Card ——————
9
DGFC
X3 RS485
59 6837
GEI-100430
S23=ON
S24=ON
RS485
RS232
RS232
PC/PLC
Figure 1.2.2.2: RS-485 single point comm. without signal isolation
The DGF jumpers are:
NameDefaultFunction
S23ON"ON" RS-485 line end device (for terminal resistor)
S24ON"ON" RS-485 line end device (for terminal resistor)
d0020g
Figure 1.2.2.3 shows an RS-485 communications link with three 6KCV301DGF cards
with signal isolation.This is the recommended configuration for applications that use
the serial link. The card at the end of the line (both ends) must have the terminator
resistor inserted, and thus S23=S24=ON while the other two 6KCV301DGF cards
must have S23=S24=OFF.
DGFCDGFCDGFC
593759375937
S23=OFF
S24=OFF
X3 RS485X3 RS485X3 RS485
S23=OFF
S24=OFF
S23=ON
S24=ON
+5V
RS485
COM
Figure1.2.2.3: RS-485 communications with signal isolation
DGF connectors are female connectors. In this configuration, all 6KCV301DGF cards
need external power supply for serial interface.
10
—————— Digital General Function Card ——————
6KCV301DGF
1.2.3 LEDS
The LEDs on 6KCV301DGF card have the following meanings:
NameColorFunction if LED ON
PWRGreenPower 5V
RSTRedReset
OKGreenHardware watchdog = OK
VPPGreenFlash eprom programming voltage
PRGGreenFlash eprom programming voltage command
H1YellowStatus LED 1 (see table 2.2.1)
H2RedStatus LED 2 (see table 2.2.1)
H3RedStatus LED 3 (see table 2.2.1)
H4RedStatus LED 4 (see table 2.2.1)
d0030g
PWR is on when 5V supply is present; this LED must be always on when the regulation
board of the drive is supplied.
RSTled indicates that a hardware reset occurs. This LED is always OFF; the only
operation that puts the LED ON briefly is the power on and off operation
during the firmware download sequence.
OKis always ON during normal operation and indicates that the card is working
normally. If it is OFF during normal operation, this indicates a card malfunction;
this condition forces an alarm on the drive. The LED should be OFF only
during the firmware download sequence.
VPPindicates the presence of the flash eprom programming voltage (12V). This
LED must be ON only during the firmware download sequence or during the
archive operation (save parameters).
PRG indicates the enable of the flash eprom programming voltage generation. This
LED must be ON only during the firmware download sequence or during the
archive operation (save parameters).
H1 – H4 These LEDs are controlled by the software of the card. Refer to Chapter 2 for
The only jumpers that it is possible to move are the RS-485 serial link jumpers. For
more information see section 1.2.2.
ON only on the RS-485 line end device (for terminal
resistor)
d0040ge
12
Figure 1.2.4.1: 6KCV301DGF Jumper Locations
—————— Digital General Function Card ——————
6KCV301DGF
1.2.5 CAN CONNECTOR
The DNet (CAN) interface provides signal isolation and uses a 4- wire cable : two for
signals and two for external power supply. The 6KCV301DGF connectors have the
following meanings:
PinSignalDescription
1V-Negative external power supply
2CAN-Negative CAN signal
3SHIELDCable shield
4CAN+Positive CAN signal
5V+Positive external power supply
6
7
Note that the line terminator resistor is external to the card according to DeviceNet
specification.
GNDGround: connect to ground
d0050g
—————— Digital General Function Card ——————
13
GEI-100430
1.3 MECHANICAL LAYOUT
Figures 1.3.1 shows the location of the 6KCV301DGF card on the drive. The DNET
module are optional and therefore they may not be present. The connector connects
only the Drive Regulation Board to DGF.
For more information about the connections see Figure 1.2.1 of this manual.
Regulation board
14
DGF card
DNET module
Figure 1.3.1: DGF Location
—————— Digital General Function Card ——————
6KCV301DGF
2. DGF OVERVIEW
2.1 INTRODUCTION
DGCF is a general purpose, where the final user can load the custom firmware which
carry out the desidered applications.
The DGF option is mounted on the drive with which it communicates through a DUAL
PORT RAM. Therefore it is possible to read drive parameters (including parameters
connected to analog and digital I/O), perform the algorithms, and write the result or
other parameters necessary to realize the desired functions.
The functional blocks also allow the reading of inputs and writing of outputs, physically
present on the optional I/O card and available to the DGF.
I/O
Firmware
D
Standard
Dbase
P
R
Communication
card
Analog I/O
Serial Link
(Profibus-DP, Interbus-S,...)
DRIVE
Digital I/O
Serial Link
(Slink3)
A
M
User
HIB
Figure 2.1.1: DGF block diagram
2.1.1 Firmware organization
The firmware of the DGF is divided in two parts: a fixed part, factory developed, and
a personalized one which can be developed even by the final user.
The final user has different possibilities to personalize the firmware of the DGF. The
main tools are the developing environment Win+Drive. Users with a programming
knowledge can develop directly with a C or Assembler language.
—————— Digital General Function Card ——————
15
GEI-100430
2.1.2 DGF application
Application code can be obtained these ways:
1Graphical development tool Win+Drive and design the specific application.
2Graphical development tool Win+Drive and a factory predeveloped application.
The standard application can be modified with Win+Drive according to the specific
needs.
3Use a factory developed and tested application and load it on the DGF unmodified.
In this case the Win+Drive can be used.
4Demo version
DRIVEPC
SLINK3
DPRAM
I/O
OPTIONAL
CARD
ARCHIVE
DBASE
EEPROMSTORE AREADBASE AREA
CAN
Controller
COPROCESSOR
387
386
Firmware
DBASE
Figure 2.1.1.1: Logical structure
NUCLEUS & FIRMWARE The firmware core of the DGF consists of the operati-
ve system multi-task real time MARTE. The core regulates the
times and the task priorities forming the firmware.
16
—————— Digital General Function Card ——————
6KCV301DGF
CPMMathematical co-processor 387.
DPRAMDPRAM is a bi-accessible storage device that allows the DGF
to communicate with the connected drive. Various connection
structures are available, with different exchange capacity and
priority.
I/O OPTIONAL CARDIt is possible to add additional cards to expand the
hardware capability of the DGF. The detailed description of
these devices can be found in their specific documentation.
The DGF can be provided with various I/O cards.
DBASEDBASE is a block used for the communication with the external
world. It is a catalog of variables provided by the DGF and
containing different information on the system. For each
variable access modes are specified, for example:
- read-only or read and write
- limits of the variable value
- access level, etc.
All information coming from or directed to the external world
goes through DBASE.
ARCHIVEArchive is a particular storage area where DBASE data are
stored so that the DGF can restart after a supply voltage failure.
2.1.2 Working of the DGF
The software of the card is based on the multi-task real-time operating system called
MARTE.
The structure of the program comprises a nucleus of 5 tasks with the following
characteristics (see Figure 2.1.3.1):
TASK SYN DPRAM This task executes the communications with the drive, for the
parameters at high priority , using the SYN DPRAM structure
of the DPRAM. The connection is executed with the maximum
priority at constant frequency. The event which wakes up the
task is a signal coming from the drive, whose execution is
synchronous with the regulation task of the drive.
TASK PERIODThis task carries out the regulation program developed by the
user. The task is normally carried out as a sub-routine of the
task SYN DPRAM. As a consequence, it inherits the main
characteristics:
- execution at the maximum priority ,
- constant priority
- synchronous with the drive.
In particular applications the task could be carried out in an independent way from the
task SYN DPRAM. In this case the execution of the task is carried out in an
asynchronous, with respect to the drive.
—————— Digital General Function Card ——————
17
GEI-100430
The execution cycle of the above-mentioned two tasks is fixed through a parameter
and can vary from 2 to 20 milliseconds with a tick of 2 milliseconds. The reason the
execution time of these important tasks is variable is that the TASK PERIOD carries
out the program developed by the user, and is dependant on the size of the custom
application program. A later chapter explains how to choose a correct execution time.
T ASK MEDIUMThis task executes code with medium importance; in the futu-
re parts of the user-developed program will be allowed to
execute in this task. The execution time is fixed at 50
milliseconds.
T ASK ASYN DPRAM This task in the applications code executes with the drive for
the parameters at low priority, using the structure ASYN
DPRAM of the DPRAM. The connection is carried out
asynchronous from the regulation task of the drive.
T ASK POLLINGThis task carries out checks of very low importance. The
execution time is fixed at 500 milliseconds. The DGF interacts
with the external environment through two devices:
DRIVE DGFCyCan read and write some parameters of the drive and through
these modify the working of the drive. Moreover, the DGF
has the ability to manage directly the physical I/O of the drive.
For additional information, refer to section 2.1.7.
I/O CARDSIf the physical I/O of the drive is insufficient for the application
it is possible to add additional optional cards with specific
functions. Further information is given in their respective
documentation.
The DGF operation can be configured through DGF parameters. The access from the
external world to these parameters is managed by the DBASE. The DBASE is a set of
procedures and data which coordinates and manages the access to DGF parameters.
The DBASE is the interface between the operating system of the DGF and the external
world. The devices which can access the DBASE
of the DGF are the following:
-Serial port RS-485 of the DGF in modality SLINK2, SLINK3 and SLINK4
-Serial port RS-232 of the DGF in modality SLINK2, SLINK3 and SLINK4
-Serial protocol DeviceNet
-Drive keypad from the application card or Opt 2 menu
-Optional communication cards on the drive
-Serial port RS-485 of the drive in modality SLINK3 for DGF
Further information regarding the DBASE is given in section 2.1.6.
18
—————— Digital General Function Card ——————
Loading...
+ 42 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.