gefran SBI-DN Instruction Manual
...... Instruction manual
Field bus interface card
SBI-DN
Interface Board
DeviceNet
Industrial Application
The information held in this manual can be modied without notice and it is
not strictly binding for GEFRAN S.p.A.
For no reason no part of this manual can be reproduced in any form or by
any means (including recording and photocopying) without a written consent
of GEFRAN S.p.A.
Before the inverter installation, wiring, commissioning and inspection, read
carefully this instruction manual.
Keep the manual in a safe place and at everyone’s disposal during the drive
functioning period.
GEFRAN S.p.A. is not responsible for those mistakes that may be found in
this manual and for the damages that they may arouse.
All rights reserved.
SBI-DN
3
—————— Interface Board DeviceNet ——————
TABLE OF CONTENTS
1.0 INTRODUCTION .............................................................................. 7
1.1 THE MANUAL ..................................................................................... 7
1.2 DEVICENET GENERAL DESCRIPTION ....................................................7
2.0 HARDWARE DESCRIPTION ...........................................................9
2.1 DIMENSIONS, WEIGHT, PROTECTION DEGREE .....................................9
2.2 INSTALLATION ...................................................................................10
2.3 POWER SUPPLY ................................................................................. 12
2.4 CONNECTORS .................................................................................... 13
2.5 DIP SWITCHES ................................................................................... 13
2.6 LEDS .................................................................................................. 14
2.7 TECHNICAL SPECIFICATIONS ............................................................. 14
2.8 INTERFACE ........................................................................................14
3.0 DEVICENET FUNCTION .................................................................15
3.1 OBJECT DESCRIPTION ...................................................................... 15
3.1.1 Object Model ......................................................................................... 15
3.1.2 How Objects Affect Behavior. .................................................................. 17
3.1.3 Dening Object Interface ........................................................................ 17
3.1.4 I/O Assembly Instances .......................................................................... 17
3.1.5 I/O Assembly Data Attributes Format ......................................................18
3.2 DATA TRANSFER VIA EXPLICIT MESSAGING ...................................... 18
3.2.1 Drive Parameter Access ......................................................................... 18
3.2.1.1 Class code ..................................................................................................... 19
3.2.1.2 Class attributes .............................................................................................. 19
3.2.1.3 Instance Attributes ......................................................................................... 19
3.2.1.4 Common Services .......................................................................................... 19
3.2.1.5 Object Specic services ................................................................................. 19
3.2.1.6 Behavior ......................................................................................................... 19
3.2.1.6.1 Write Drive Parameter ................................................................................. 19
3.2.1.6.1.1 Write Drive Parameter Request ................................................................. 19
3.2.1.6.1.2 Write drive parameter - Reply OK ............................................................. 20
3.2.1.6.1.3 Write drive parameter - Reply Error .......................................................... 20
3.2.1.6.2 Read Drive Parameter .................................................................................. 21
3.2.1.6.2.1 Read Drive Parameter Request ................................................................. 21
3.2.1.6.2.2 Read drive parameter - Reply OK .............................................................. 21
3.2.1.6.2.3 Read drive parameter - Reply Error ........................................................... 21
3.2.2 APC Option Parameter Access ........................................................................... 22
3.2.2.1 Class code ..................................................................................................... 22
3.2.2.2 Class attributes .............................................................................................. 22
3.2.2.3 Instance Attributes ......................................................................................... 22
3.2.2.4 Common Services .......................................................................................... 22
3.2.2.5 Object Specic services ................................................................................. 23
3.2.2.6 Behavior ......................................................................................................... 23
GEFRAN
—————— Interface Board DeviceNet ——————
4
3.2.2.6.1 Write APC Parameter ................................................................................... 23
3.2.2.6.1.1 Write APC Parameter Request .................................................................. 23
3.2.2.6.1.2 Write APC parameter - Reply OK .............................................................. 24
3.2.2.6.1.3 Write APC parameter - Reply Error ........................................................... 24
3.2.1.6.2 Read APC Parameter ................................................................................... 24
3.2.1.6.2.1 Read APC Parameter Request .................................................................. 24
3.2.1.6.2.2 Read APC parameter - Reply OK ............................................................... 25
3.2.1.6.2.3 Read APC parameter - Reply Error ............................................................ 25
4.0 POLLING FUNCTION .....................................................................26
4.1 SETTING OF POLLING PARAMETERS.................................................. 26
4.1.1 Conguration object of the Polling parameters S->M .............................26
4.1.1.1 Class code ..................................................................................................... 27
4.1.2 Class attributes ...................................................................................... 27
4.1.3 Istance attributes ................................................................................... 27
4.1.4 Common services .................................................................................. 27
4.1.5 Object Specic services ......................................................................... 28
4.1.6 Behavior................................................................................................. 28
4.1.6.1 Write Polling S->M Conguration .................................................................. 28
4.1.6.1.1 Write Single Polling S->M Conguration ..................................................... 28
4.1.6.1.2 Write Single Polling S->M Conguration - Reply OK ................................... 28
4.1.6.1.3 Write Single Polling S->M Conguration - Reply Error ................................ 29
4.1.6.1.4 Write Entire Polling S->M Conguration ...................................................... 29
4.1.6.1.5 Write Entire Polling S->M Conguration - Reply OK .................................... 30
4.1.6.1.6 Write Entire Polling S->M Conguration - Reply Error ................................. 30
4.1.6.2 Read S->M Polling Conguration ................................................................... 30
4.1.6.2.1 Read Single Polling S->M Conguration ..................................................... 30
4.1.6.2.2 Read Single Polling S->M Conguration - Reply OK .................................... 31
4.1.6.2.3 Read Single Polling S->M Conguration - Reply Error ................................. 31
4.1.6.2.4 Read Entire Polling S->M Conguration ...................................................... 31
4.1.6.2.5 Read Entire Polling S->M Conguration - Reply OK..................................... 31
4.1.6.2.6 Read Entire Polling S->M Conguration - Reply Error ................................. 32
4.2 OBJECT CONFIGURATION POLLING PARAMETERS M->S ..................32
4.2.1 Class code ............................................................................................. 33
4.2.2 Class attributes ...................................................................................... 33
4.2.3 Instance Attributes ................................................................................. 33
4.2.4 Common Services.................................................................................. 33
4.2.5 Object Specic services ......................................................................... 34
4.2.6 Behavior................................................................................................. 34
4.2.6.1 Write Polling M->S Conguration .................................................................. 34
4.2.6.1.1 Write Single Polling M->S Conguration ..................................................... 34
4.2.6.1.2 Write Single Polling M->S Conguration - Reply OK ................................... 34
4.2.6.1.3 Write Single Polling M->S Conguration - Reply Error ................................ 35
4.2.6.1.4 Write Entire Polling M->S Conguration ...................................................... 35
4.2.6.1.5 Write Entire Polling M->S Conguration - Reply OK .................................... 35
4.2.6.1.6 Write Entire Polling M->S Conguration - Reply Error ................................. 36
4.2.6.2 Read M->S Polling Conguration ................................................................... 36
4.2.6.2.1 Read Single Polling M->S Conguration ..................................................... 36
4.2.6.2.2 Read Single Polling M->S Conguration - Reply OK .................................... 36
4.2.6.2.3 Read Single Polling M->S Conguration - Reply Error ................................. 37
SBI-DN
5
—————— Interface Board DeviceNet ——————
4.2.6.2.4 Read Entire Polling M->S Conguration ...................................................... 37
4.2.6.2.5 Read Entire Polling M->S Conguration - Reply OK..................................... 37
4.2.6.2.6 Read Entire Polling M->S Conguration - Reply Error ................................. 38
5.0 SETTING OF VIRTUAL DIGITAL I/O ...............................................39
5.1 OBJECT CONFIGURATION VIRTUAL DIGITAL INPUTS .......................... 39
5.1.1 Class code ............................................................................................. 39
5.1.2 Class attributes ...................................................................................... 39
5.1.3 Instance Attributes ................................................................................. 40
5.1.4 Common Services.................................................................................. 40
5.1.5 Object Specic services ......................................................................... 40
5.1.6 Behavior................................................................................................. 40
5.1.6.1 Write Virtual Digital Input Conguration .......................................................... 41
5.1.6.1.1 Write Single Virtual Digital Input Conguration ............................................. 41
5.1.6.1.2 Write Single Virtual Digital Input Conguration - Reply OK ...........................41
5.1.6.1.3 Write Single Virtual Digital Input Conguration - Reply Error ........................41
5.1.6.1.4 Write Entire Virtual Digital Input Conguration.............................................. 42
5.1.6.1.5 Write Entire Virtual Digital Input Conguration - Reply OK ............................ 42
5.1.6.1.6 Write Entire Virtual Digital Input Conguration - Reply Error ......................... 42
5.1.6.2 Read Virtual Digital Input Conguration........................................................... 43
5.1.6.2.1 Read Single Virtual Digital Input Conguration ............................................. 43
5.1.6.2.2 Read Single Virtual Digital Input Conguration - Reply OK ............................43
5.1.6.2.3 Read Single Virtual Digital Input Conguration - Reply Error .........................44
5.1.6.2.4 Read Entire Virtual Digital Input Conguration .............................................. 44
5.1.6.2.5 Read Entire Virtual Digital Input Conguration - Reply OK............................. 44
5.1.6.2.6 Read Entire Virtual Digital Input Conguration - Reply Error .........................45
5.2 CONFIGURATION OBJECT VIRTUAL DIGITAL OUTPUT ........................ 45
5.2.1 Class code ............................................................................................. 45
5.2.2 Class attributes ...................................................................................... 45
5.2.3 Instance Attributes ................................................................................. 46
5.2.4 Common Services.................................................................................. 46
5.2.5 Object Specic services ......................................................................... 46
5.2.6 Behavior................................................................................................. 46
5.2.6.1 Write Virtual Digital Output Conguration ........................................................ 47
5.2.6.1.1 Write Single Virtual Digital Output Conguration .......................................... 47
5.2.6.1.2 Write Single Virtual Digital Output Conguration - Reply OK ......................... 47
5.2.6.1.3 Write Single Virtual Digital Output Conguration - Reply Error ...................... 47
5.2.6.1.4 Write Entire Virtual Digital Output Conguration ........................................... 48
5.2.6.1.5 Write Entire Virtual Digital Output Conguration - Reply OK ..........................48
5.2.6.1.6 Write Entire Virtual Digital Output Conguration - Reply Error .......................48
5.2.6.2 Read Virtual Digital Output Conguration ........................................................ 49
5.2.6.2.1 Read Single Virtual Digital Output Conguration........................................... 49
5.2.6.2.2 Read Single Virtual Digital Output Conguration - Reply OK ......................... 49
5.2.6.2.3 Read Single Virtual Digital Output Conguration - Reply Error ...................... 50
5.2.6.2.4 Read Entire Virtual Digital Output Conguration ........................................... 50
5.2.6.2.5 Read Entire Virtual Digital Output Conguration - Reply OK .......................... 50
5.2.6.2.6 Read Entire Virtual Digital Output Conguration - Reply Error ....................... 51
6.0 FUNCTION ERROR CODES ...........................................................52
7.0 KEYPAD INTERFACE ..................................................................... 54
GEFRAN
—————— Interface Board DeviceNet ——————
6
7.1 MAIN MENU STRUCTURE .................................................................. 54
7.1.2 Control of warning and error messages .................................................. 54
7.2 OFFSET MENU ................................................................................... 54
7.2.1 Edit Offset .............................................................................................. 55
7.3 POLLING MENU..................................................................................55
7.3.1 Edit for Drive parameter assignment to the Polling I/O function ............... 56
7.4 VIRTUAL DIGITAL I/O MENU ...............................................................58
7.5 DRIVE VIRTUAL DIGITAL I/O PARAMETER ASSIGNMENT .......................
EDITING..............................................................................................59
7.6 PASSWORD MENU ............................................................................ 60
7.6.1 Password request ..................................................................................60
7.6.2 Edit for the Password setting .................................................................. 61
7.7 SBI INFO MENU .................................................................................. 62
7.7.1 Display node address (MAC ID) .............................................................. 62
7.7.2 Display Baud Rate .................................................................................. 62
7.7.3 Node status............................................................................................ 63
7.7.3.1 DeviceNet ERROR TYPES ................................................................................ 63
7.7.4 Status of allocation................................................................................. 65
7.7.5 CNXN status ........................................................................................... 66
7.7.6 I/O CNXN status ..................................................................................... 66
7.7.7 DUP MAC ID TEST (DMC) ....................................................................... 66
7.7.8 Display Software version (Sotware version) ............................................ 67
7.7.9 Display compatibility index(Compatib. index) .......................................... 67
7.8 EDIT ................................................................................................... 68
8.0 MISCELLANEOUS ......................................................................... 69
8.1 DEFINITIONS ...................................................................................... 69
8.2 REFERENCES ..................................................................................... 69
SBI-DN
7
—————— Interface Board DeviceNet ——————
1.0 INTRODUCTION
The manual describes the optional SBI-DN card for connecting of inverters and
converters to DeviceNet networks.
Drives belonging to TPD32-EV series can be connected in network through the
SBI-DN board.
This manual is intended for design engineeres and technicians responsible for the
maintenance, commissioning and operation of DeviceNet systems.
A basic knowledge of DeviceNet is assumed and may be found in the following
manuals:
- DeviceNet Specications. Volume 1 - DeviceNet Communication Model and
Protocol (Issued by ODVA).
- DeviceNet Specications. Volume 2 - DeviceNet Device Proles and Object
Library (Issued by ODVA).
1.1 THE MANUAL
Chapter 2 Dimensions, board mechanical installation, electric
connections and Dipswitch setting.
Chapter 3 DeviceNet functions: description of the objects control-
led by the board, data transfer via “Explicit messaging”.
Chapter 4 “Polling” operations for the exchange of Drive para-
meters between the Master and the interface board
(M->S and S->M)
Chapter 5 Setting of virtual digital I/Os
Chapter 6 Error codes
Chapter 7 Keypad menus
Chapter 8 Denitions and references.
1.2 DEVICENET GENERAL DESCRIPTION
DeviceNet is a prole of communication for industrial systems based on CAN.
As protocol CAN (ISO 11898) is used CAN2.0A with the 11 bit identier.
The SBI board is developed as “Slave UCMM Capable Device” for operating only
in “Predened Master/Slave Connection Set”.
The data transfer is carried out cyclically; the Master unit reads the data supplied
GEFRAN
—————— Interface Board DeviceNet ——————
8
by the Slaves and writes the Slave reference data; the Baud Rate supported by
the SBI board are:
- 125 kbit
- 250 kbit
- 500 kbit .
The physical support is given by the RS485 serial line; a maximum of 64 Slaves
can be connected to the Bus.
SBI-DN
9
—————— Interface Board DeviceNet ——————
2.0 HARDWARE DESCRIPTION
2.1 DIMENSIONS, WEIGHT, PROTECTION DEGREE
SBI DN
12
3
4
5
6
7
8
PWR RST RUN OP AL0 AL1 AL2
XS
X0
S1
ON
OFF
157mm
(6.18")
110mm
(4.33")
H1
S2
S4
S3
S5
S6
S7
S8
BA
BA
BA
BA
BA
1 2345
BUS
Dimensions [mm/in.] 157/6.18” (H) x 110/4.33” (L) x 23/1” (P)
Weight 200 g (7.1 oz)
Protection degree IP00.
GEFRAN
—————— Interface Board DeviceNet ——————
10
2.2 INSTALLATION
The SBI interface card is delivered with a kit including 6 standoffs (no.4 L=26.5
mm + no.2 L=10mm), 4 screws, washers the WARRANTY label and a 40-pole at
cable with connectors.
Tools required (depending on models): 7x2 mm slotted-head screwdriver
Torx ® screwdriver: T10, T20, T25.
Cross-head screwdriver #1, 2, 3.
Socket wrench 6mm
® Registered trademark of Camcar LLC of Acument
Global Technologies.
WARNING: Before using the product, read the TPD32-EV safety instruction section
(on TPD32-EV manual). Never open the device or covers while the AC Input power
supply is switched on. Wait for at least one minute before working on the terminals
or inside the device.
mounting form A mounting form B, C, D
2
3
3
1
1.5 Nm
1
1.5 Nm
2
4
4
4
4
4
4
4
4
Figure 1
1. The front covers of the devices must be removed to mount the option cards. The
devices can be opened without the use of force. Only use the tools specied.
Removing the lower cover:
To remove the lower cover of devices, use a cross screwdriver. Remove the
screws (1) (2), lift cover (3), and open out to the front. See gure 1..
Removing the upper cover:
- Frame A: there are 2 seal pins on the top. To remove the cover, align the two
slots with the pins and lift the cover as shown in Figure 2:
- Frame B-C-D: loosen the 4 screws (4), align the slots of the cover with the
head of the screws and remove the cover. See gure 1.
Disconnect the keypad cable from the control card.
Note: for Frame D, remove only the keypad cover.
SBI-DN
11
—————— Interface Board DeviceNet ——————
Figure 3A
R-TPD32-EV
R-TPD32-EV
SBI-DN
SBI-OFM-32
SBI-OFS-32
Distanziali/Stands-off
L=26,5mm (x2)
Distanziali/Stands-off
L=26,5mm (x4)
Distanziali/Stands-off
L=10mm (x2)
SBI-DN
Figure 3B
2. Fasten with screws and no.4 standoffs L=26.5mm the SBI board to the regulation board, see gure 3A. In case there is the SBI-OFM/OFS-32 card, fasten
the SBI card to the drive regulation card by means of screws and 2 standoffs
L=10 mm + 2 standoffs L=26.5mm, see gure 3B.
The BUS connector is turned in the same direction as the regulation board
terminals.
3. The at cable is connected between the XO connector placed on the R-TPD32-
EV card and SBI-DN card. In case there is the APC300 card, connect the at
cable from APC300 to XO connector on SBI-DN card.
4. The Baud Rate of the SBI board is set via the Switches 7 and 8 of the Dipswitch S1. The Baud Rate is detected only when the board is switched on and it
can be modied only by switching off and swtching on the board again.Table
2 shows the relation between the DIP-Switches and the selectable Baud Rate
value. The Default value is 125 Kbaud.
GEFRAN
—————— Interface Board DeviceNet ——————
12
Switch 8 Switch 7 Baud Rate
OFF OFF 125 kBaud
OFF ON 250 kBaud
ON OFF 500 kBaud
ON ON 125 KBaud
DN21
5. The dip switch S1 determines the Slave address. The address “0” is reserved
to the Master and it must not be used. The switches S1 -7 and S1-8 do not
determine any address. The address is detected only when the board is switched on. If the address is modied, the Drive has to be switched off and then
switched on in order to assume the new address.
6. Connect the Bus cable to the BUS connection terminal.
7. Switch on the drive.
8. The LEDS PWR and RUN light up.
9. Switch the Device Net power supply on; the LED H1 lights up.
10. The LED OP lights up when the Master/Slave connection has been established.
WARNING: Replace all covers before applying power to the Drive. Failure to
do so may result in death or serious injury.
11. Replace the upper and lower cover by performing the procedures described
in step 1. in the reverse order.
12. To restore the warranty seal, apply the WARRANTY-R label to the TPD32-.EV
converter over the label broken during opening.
Warranty-R label:
2.3 POWER SUPPLY
The power supply is provided by the XO connector, which is used to connect the
data between the SBI board and the Drive regulation board.
Absorbed current: 350 mA
SBI-DN
13
—————— Interface Board DeviceNet ——————
2.4 CONNECTORS
Connector : It allows to connect the ground (GNDE) of the external
power supply to the ground (PE).
Connector XS It allows to connect the ground (PE) to the DeviceNet
cable shield.
Terminal BUS See the gure below. It allows to connect the SBI board
to the DeviceNet network. The pins are the following:
Pin Signal Description
1 CAN_GND Ground/0V/V2 CAN_L Can_L bus line (dominant low)
3 CAN_SHLD CAN shield
4 CAN_H CAN_H bus line (dominant high)
5 CAN_V+
CAN external positive supply
(dedicated for supply of
transceiver and optocouplers)
dn22
2.5 DIP SWITCHES
S3 Interrupt selection from selector S5 (INT1/INT2) to the microcontroller 8032 or
to the interrupt input of the dual port ram (INTR). Default position is A (interrupt
to the dual port ram).
S4 Synchronisation connection for the reset signal of the SBI board to the con-
nected regulation board. Default position is ON.
S5 It is used to connect the signal INT_OPZ to the signal INT1 (S5.B) or to the
signal INT2 (S5.A). The interface board is standard set as OPTION 1, therefore
INT_OPZ is connected to the signal INT1. (Default position is A).
S6 It is used to connect the signal OUT_OPZ to the signal OUT1 (S6.A) or OUT2
(S6.B). Default position is B.
S7 It is used to connect the signal CEM_OPZ to the signal OPZ1 (S7.B) or to the
signal OPZ2 (S7.A). The SBI board is standard set as OPTION 1, therefore
CEM_OPZ is connected to the signal OPZ1. Default position is B.
S8 Connection of the dual port ram BUSY signal to the signal RDY_EXT. Default
position is ON.
GEFRAN
—————— Interface Board DeviceNet ——————
14
2.6 LEDS
PWR +5V power supply.
RST Reset active.
H1 +5V power supply on the RS 485 driver side. It is supplied by
the Bus.
RUN It is on when the microcontroller is operating.
OP It is on when the Master/Slave connection is established.
AL0 It blinks when the “Duplicate MAC ID” test has not been passed.
AL1, AL2 Not used and are always off.
2.7 TECHNICAL SPECIFICATIONS
Storage temperature: -20°... +70°C (-68...+158°F)
Operating temperature: 0°... +55°C (32...+131°F)
Such temperatures are suitable to be used with those of the drive, which they are
connected to.
2.8 INTERFACE
The board has to be installed on the regulation board so that the XO connector of
the SBI board is placed near the XO connector of the regulation board, thus keeping
the DeviceNet connection terminal in a downward position.
As for the mechanical connection use the kit delivered with the board.
As for the electrical connection use the 40-pole at cable included in the kit.
As for the Bus connection use a shielded “twisted pair cable”.
The connection among the single boards is carried out via a shielded cable as
shown in the gure below:
SBI-DN
SBI-DN SBI-DN
PE
Shield
SBI-DN
15
—————— Interface Board DeviceNet ——————
3.0 DEVICENET FUNCTION
In this chapter are described the functions of DeviceNet managed by the SBI board.
The main characteristics of the board are:
1. The board operates only as Slave in “Predined Master/Slave Connection Set”.
2. Within the “Predened Master/Slave Connection Set” the board is a “UCMM
Capable Device”.
3. The “Explicit Messaging” is managed.
4. The “Polling” for the fast cyclical data exchange Master/Slave is managed.
5. The detection mechanism of the “Duplicate MAC ID” is implemented.
Regarding the “Explicit Messaging” the fragmentation of the data frame, with a total
of max. 38 byte, is managed.
3.1 OBJECT DESCRIPTION
Hereafter you nd the description of the objects managed by the SBI board.
3.1.1 Object Model
The Fig. 3.11 shows the SBI board “Object Model”.
GEFRAN
—————— Interface Board DeviceNet ——————
16
Application Objects
DGFC par
PollI/O
Drive par
DgtI/O
Assembly Class
I/OI/O
Message
Router
DeviceNet
IDENTITY
ExplicitI/O
Connection
Figure 3.1: DeviceNet Object Model
The following table shows:
1. The object classes of the SBI-board.
2. If the class is mandatory.
3. The number of instances included in every class.
See “DeviceNet Specications” for the Standard classes.
Object Optional/Required #of Instances
Identity Required 1
Message Router Required 1
DeviceNet Required 1
Connection Required at maximum one Explicit
Assembly Optional 0..2
Drive Parameter Access Optional many
DGFC Parameter Access Optional many
Poll Slave->Master CFG Optional 1
Poll Master->Slave CFG Optional 1
Virtual Digital Input CFG Optional 1
Virtual Digital Output CFG Optional 1
dn310
SBI-DN
17
—————— Interface Board DeviceNet ——————
3.1.2 How Objects Affect Behavior.
The “Affect Behaviour” of the objects is reported in the following table:
Object
Effect on Behavior
Identity
Supports “Reset Service”.
Message Router
No effect
DeviceNet
Port attributes configuration
Connection
Conteins the number of logical ports
internal or external to the SBI board
Assembly
Defines the I/O data format
Drive Parameter Access
Drive parameters read/write
DGFCOption Parameter Access
DGFC parameters read/write
Poll Slave->Master CFG
Assignes Drive parameters to the
Polling Slave->Master Word
Poll Master -> Slave CFG
Assignes Drive parameters to the
Polling Master -> Slave Word
Virtual Digital Input CFG
Assignes Drive parameters to the
“Virtual Digital Input ”.
Virtual Digital Output CFG
Assignes Drive parameters to the
“Virtual Digital Output ”.
3.1.3 Defining Object Interface
The object interface of the SBI board is the following:
Object Interface
Identity Message router
Message Router
Explicit Messaging
Connection Instance
DeviceNet Message router
Connection Message router
Assembly
I/O Connection or
Message Router
Drive Parameter Access Message router
DGF Parameter Access Message router
Poll Slave->Master CFG Message router
Poll Master->Slave CFG Message router
Virtual Digital Input CFG Message router
Virtual Digital Output CFG Message router
dn313ge
3.1.4 I/O Assembly Instances
The following table identies the “I/O Assembly” instances of the SBI board:
Number Type Name
195 Input PMSCS Assembly Cons
194 Output PMSCS Assembly Prod
DN325
GEFRAN
—————— Interface Board DeviceNet ——————
18
3.1.5 I/O Assembly Data Attributes Format
The “I/O Assembly” attributes format for the Input is the following:
PMSCS Assembly Cons:
Instance Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0
1
2
….
….
(n2)-1
n*2
….
word #n to consume, low byte
word #n to consume, high byte
195
word #1 to consume, low byte
word #1 to consume, high byte
word #2 to consume, low byte
….
(n) is the number of consumed Words; it is 4 (8bytes).
PMSCS Assembly Prod:
Instance Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0
1
2
….
….
(n2)-1
n*2
….
word #n to produce, low byte
word #n to produce, high byte
194
word #1 to produce, low byte
word #1 to produce, high byte
word #2 to produce, low byte
….
(n) is the number of produced Words; it is 4 (8bytes).
3.2 DATA TRANSFER VIA EXPLICIT MESSAGING
The data transfer via Explicit Messaging is made through two new objects: one for
accessing the Drive parameters, the other to access the parameters of the APC
option card.
3.2.1 Drive Parameter Access
For reading/writing the drive parameters the Drive Parameter Access object is
dened with the following characteristics:
- Class ID: 66h.
- Class Attribute: Revision
- Instance Attribute: This instance does not provide any attribute.
SBI-DN
19
—————— Interface Board DeviceNet ——————
3.2.1.1 Class code
Class Code: 66hex
3.2.1.2 Class attributes
Number
Need in
implementation
Access Rule Name
DeviceNet
Data Type
Description
of Attribute
Semantics of
values
1 Optional Get Revision UINT
Revision of
this object
3.2.1.3 Instance Attributes
Number
Need in
implementation
Access Rule Name
DeviceNet
Data Type
Description
of Attribute
Semantics of
values
This instance does not provide attributes
3.2.1.4 Common Services
This object has no common services.
3.2.1.5 Object Specific services
Class Instance
32
hex
n/a Required Get_Drive_Value Read drive parameter value
33
hex
n/a Required Set_Drive_Value Writes drive parameter value
dn355
Service
Code
Need in
implementation
Service Name Description of Service
3.2.1.6 Behavior
This object is the interface between the DeviceNet network and all Drive parameters. The access to the Drive parameter is carried out by the parameter index; if the
parameter does not exist or may not be accessed for any reason (for example: try
to write a read only parameter) an error code will be returned.
Drive parameters in text format cannot be accessed.
In the following are repeted patterns of how the data frame of data has to be composed for reading/writing Drive parameters.
3.2.1.6.1 Write Drive Parameter
In this example the writing of a Drive parameter is shown; the cases of positive or
wrong writing are distinguished.
3.2.1.6.1.1 Write Drive Parameter Request
The data frame for writing a drive parameter is composed as follows:
GEFRAN
—————— Interface Board DeviceNet ——————
20
DATA TYPE FIELD VALUE MEANING
Byte
Service
Code
33hex
SetDrive Parameter -
Object Specific Service.
Class ID 66hex
Drive ParameterAccess
Class Object.
Instance
ID
XXXX
Drive ParameterIndexin
format Lowbyte-High
byte.
XX
Lowbyte-Low worddrive
parameter value.
XX
High byte-Low worddrive
parameter value.
XX
Lowbyte-High worddrive
parameter value.
XX
High byte-High word
drive parameter value.
dn360
VALUE
Byte
2)
See Note
1)
1)
Byte or Word depending on the type of allocation executed by the Master.
2)
The number of bytes of the “Value”-eld depends on the length of the Drive
parameter; i.e.: if the Drive parameter type is “Integer” the length of VALUE is
2 bytes.
3.2.1.6.1.2 Write drive parameter - Reply OK
If the Drive parameter is written correctly, the response is:
DATA TYPE FIELD VA LUE MEANING
Byte Service Code 33hex OR 80hex
Set Drive Parameter
Reply code- Object
Specific Service.
Word Result 0000
Result field equal to zero
means writing correctly
executed.
dn365
3.2.1.6.1.3 Write drive parameter - Reply Error
If the writing of the drive parameter has been rejected, the response is the following:
DATA TYPE FIELD VA LUE MEANING
Byte Service Code 33hex OR 80hex
Set Drive Parameter
Reply code- Object
Specific Service.
Word Result
XXXX
1
Drive specific error code.
1) For error codes see chapter 6.0
SBI-DN
21
—————— Interface Board DeviceNet ——————
3.2.1.6.2 Read Drive Parameter
In this example is shown the reading of a Drive parameter; the cases of positive or
wrong reading are distinguished.
3.2.1.6.2.1 Read Drive Parameter Request
The data frame for the Drive parameter reading is composed as follows:
DATA
TYPE
FIELD VALUE MEANING
Byte
Service
Code
32hex
Get Drive Parameter -
Object Specific Service.
See Note
1)
Class ID 66hex
Drive Parameter Access
Class Object.
See Note1)Instance
ID
XXXX
Drive Parameter Index in
format Lowbyte-High
byte.
1) Byte or Word depending on the type of allocation executed by the Master.
3.2.1.6.2.2 Read drive parameter - Reply OK
If the Drive parameter is read correctly, the response is:
DATA TYPE FIELD VALUE MEANING
Byte
Service
Code
32hex OR
80hex
GetDrive Parameter
Replycode- Object
Specific Service.
Word Result 0
Result field equaltozero
means readingcorrectly
executed.
Byte 1) XX
Lowbyte-Low worddrive
parameter value.
Byte 1) XX
High byte-Low worddrive
parameter value.
Byte 1) XX
Lowbyte-High worddrive
parameter value.
Byte 1) XX
High byte-High word
drive parameter value.
dn380
VALUE
1) The number of bytes of the Value-eld depends on the length of the Drive parameter; i.e. if the Drive parameter type is “Integer” the length of VALUE is 2 bytes.
3.2.1.6.2.3 Read drive parameter - Reply Error
If Drive parameter reading is rejected, the response is the following:
Loading...