Manual Gerador 37383

37383D
easYgen-3000 Series (Package P1) Genset Control
Interface
Software Version: 1.10xx Part Numbers: 8440-1816 / 8440-1817 / 8440-1818 / 8440-1831
Manual 37383D
Manual 37383D
easYgen-3000 Series (Package P1) - Genset Control
WARNING
Read this entire manual and all other publications pertaining to the work to be performed before installing, operating, or servicing this equipment. Practice all plant and safety instructions and precautions. Failure to follow instructions can cause personal injury and/or property damage. The engine, turbine, or other type of prime mover should be equipped with an overspeed (overtemperature, or overpressure, where applicable) shutdown device(s), that operates totally independently of the prime mover control device(s) to protect against runaway or damage to the engine, turbine, or other type of prime mover with possible personal injury or loss of life should the mechanical-hydraulic governor(s) or electric control(s), the actuator(s), fuel control(s), the driving mechanism(s), the linkage(s), or the controlled device(s) fail. Any unauthorized modifications to or use of this equipment outside its specified mechanical, electrical, or other operating limits may cause personal injury and/or property damage, including damage to the equipment. Any such unauthorized modifications: (i) constitute "misuse" and/or "negligence" within the meaning of the product warranty thereby excluding warranty coverage for any resulting damage, and (ii) invalidate product certifications or listings.
CAUTION
To prevent damage to a control system that uses an alternator or battery-charging device, make sure the charging device is turned off before disconnecting the battery from the system. Electronic controls contain static-sensitive parts. Observe the following precautions to prevent damage to these parts. Discharge body static before handling the control (with power to the control turned off, contact a grounded surface and maintain contact while handling the control). Avoid all plastic, vinyl, and Styrofoam (except antistatic versions) around printed circuit boards. Do not touch the components or conductors on a printed circuit board with your hands or with conductive devices.
OUT-OF-DATE PUBLICATION
This publication may have been revised or updated since this copy was produced. To verify that you have the latest revision, be sure to check the Woodward website: http://www.woodward.com/pubs/current.pdf The revision level is shown at the bottom of the front cover after the publication number. The latest version of most publications is available at: http://www.woodward.com/publications If your publication is not there, please contact your customer service representative to get the latest copy.
Important definitions WARNING

Indicates a potentially hazardous situation that, if not avoided, could result in death or serious injury.
CAUTION
Indicates a potentially hazardous situation that, if not avoided, could result in damage to equipment.
NOTE
Provides other helpful information that does not fall under the warning or caution categories.
Woodward reserves the right to update any portion of this publication at any time. Information provided by Woodward is believed to be correct and reliable. However, Woodward assumes no responsibility unless otherwise expressly undertaken.
Woodward All Rights Reserved.
Page 2/102
Woodward
Manual 37383D
Revision History
Rev. NEW A B C D Date 06-12-08 07-06-29 08-02-07 08-07-25 09-10-23 Editor TP TP TP TP TE Changes Release Update to reflect the new functionality Minor corrections; application examples, remote control and easYgen-3100 sections extended/added Minor corrections; update to reflect the new functionality Minor corrections
Contents
CHAPTER 1. GENERAL INFORMATION ....................................................................................... 7
Document Overview ................................................................................................................................. 7 Abbreviations ............................................................................................................................................ 7 Interface Overview ................................................................................................................................... 8 CAN Interfaces ............................................................................................................................... 9 Serial Interfaces ........................................................................................................................... 10
CHAPTER 2. CAN BUS CONFIGURATION ................................................................................. 12
CAN Interface Parameters ..................................................................................................................... 12 Configure CAN Interface 1 ........................................................................................................... 12 Configure CAN Interface 2 ........................................................................................................... 18 CAN Bus Load Sharing .......................................................................................................................... 22 General Load Share Information.................................................................................................. 22 Configure Load Share Parameters .............................................................................................. 23 Multi-Master Principle................................................................................................................... 23 Definition of CANopen Protocol Descriptions ......................................................................................... 24 Unsigned Integer .......................................................................................................................... 24 Signed Integer .............................................................................................................................. 25 J1939 Protocol Display Messages ......................................................................................................... 26 Displayed Messages .................................................................................................................... 26 Remote Control via CAN ........................................................................................................................ 28 Remote Start/Stop and Acknowledgement .................................................................................. 28 Transmitting a Frequency Set Point via CANopen....................................................................... 33 Transmitting a Voltage Set Point via CANopen ........................................................................... 35 Transmitting a Power Factor Set Point via CANopen .................................................................. 36 Transmitting a Power Set Point via CANopen ............................................................................. 38 Transmitting Multiple Set Points via CANopen ............................................................................ 40 Remotely Changing the Set Point via CANopen .......................................................................... 41 Sending a Data Protocol via TPDO ........................................................................................................ 44 Cyclically Sending of Data............................................................................................................ 44 Sending of Data on Request ........................................................................................................ 44 External DOs for an IKD 1 ...................................................................................................................... 46 Receiving Data from an IKD 1 ................................................................................................................ 46
Woodward
Page 3/102
Manual 37383D
CHAPTER 3. MODBUS COMMUNICATIONS ................................................................................ 47
General Information ............................................................................................................................... 47 Address Range ...................................................................................................................................... 48 Visualization ........................................................................................................................................... 49 Configuration.......................................................................................................................................... 50 Parameter Setting........................................................................................................................ 50 Set Point Setting .......................................................................................................................... 54 Configuration of the LogicsManager Functions via Modbus........................................................ 58 Remote Control via Modbus .................................................................................................................. 60 Remote Control via Modbus ........................................................................................................ 60 Remotely Changing the Set Point................................................................................................ 62 Changing Parameter Settings via Modbus ............................................................................................ 66 Operating Modes ......................................................................................................................... 66 Remote Start/Stop and Acknowledgement ................................................................................. 67 Remote Acknowledging Single Alarm Messages ........................................................................ 71 Remotely Clearing The Event History.......................................................................................... 72 Remotely Resetting the Default Values ....................................................................................... 73 Exception Responses ............................................................................................................................ 75 Modbus Parameters .............................................................................................................................. 76
APPENDIX A. SUPPORTED J1939 ECUS & REMOTE CONTROL MESSAGES ............................... 77 APPENDIX B. DATA PROTOCOLS ............................................................................................ 79
Data Protocol 5003 ................................................................................................................................ 79 Data Protocol 5004 (Generator Data) .................................................................................................... 89 Data Protocol 5005 (Mains Data) .......................................................................................................... 92 Data Protocol 6000 (Load Share Message) .......................................................................................... 93 General ........................................................................................................................................ 93 Timing .......................................................................................................................................... 93 Additional Data Protocol Parameters ..................................................................................................... 96 Remote Control Word 1 - Object 21F7h (Parameter ID 503) ...................................................... 96 Remote Control Word 2 - Object 21F8h (Parameter ID 504) ...................................................... 97 Remote Active Power Set Point - Object 21FBh (Parameter ID 507) ......................................... 98 Remote Power Factor Set Point - Object 21FCh (Parameter ID 508)......................................... 98 Remote Frequency Set Point - Object 21FDh (Parameter ID 509) ............................................. 98 Remote Voltage Set Point - Object 21FEh (Parameter ID 510) .................................................. 98 Remote IKD 1 DI 1 to 8 Request - Object 3F4Bh (Parameter ID 8011) ...................................... 99 Remote IKD 1 DI 9 to 16 Request - Object 3F4Ch (Parameter ID 8012) .................................. 99 Remote External DI Request - Object 3F4Dh (Parameter ID 8013) ........................................... 99 Remote IKD 1 Control - Object 34F0h (Parameter ID 8000)..................................................... 100 Remote IKD 1 DO 1 to 8 Control - Object 34F1h (Parameter ID 8001) .................................... 100 Remote IKD 1 DO 9 to 16 Control - Object 34F2h (Parameter ID 8002) .................................. 100 Remote External DO Control - Object 34F5h (Parameter ID 8005) .......................................... 101
Page 4/102
Woodward
Manual 37383D
Figures and Tables

Figures
Figure 1-1: easYgen - interface overview ............................................................................................................. 8 Figure 1-2: Interface overview - CAN interfaces .................................................................................................. 9 Figure 1-3: Interface overview - serial interfaces ................................................................................................ 10 Figure 1-4: Interface overview - serial interface Modbus full-duplex ................................................................. 11 Figure 1-5: Interface overview - serial interface Modbus half-duplex ................................................................ 11 Figure 2-1: Interfaces - principle of PDO mapping............................................................................................. 15 Figure 2-2: CAN interface 1 - standard values for load sharing.......................................................................... 22 Figure 2-3: Display screen - configure CAN interface 1 ..................................................................................... 29 Figure 2-4: Display screen - Receive PDO 1 ...................................................................................................... 29 Figure 2-5: CANopen request data ..................................................................................................................... 30 Figure 2-6: CANopen request data for Node ID 1 .............................................................................................. 30 Figure 2-7: Display screen - Configure CAN interface 1 .................................................................................... 31 Figure 2-8: CANopen request data for Node ID 2 .............................................................................................. 31 Figure 2-9: Display screen - Additional Server SDOs ........................................................................................ 32 Figure 2-10: CANopen request data for additional Server SDO ......................................................................... 33 Figure 2-11: Display screen - Receive PDO 1 for frequency set point ............................................................... 33 Figure 2-12: CANopen send data for frequency set point ................................................................................... 34 Figure 2-13: CANopen send data for Node ID 1 for frequency set point ........................................................... 34 Figure 2-14: Display screen - Receive PDO 1 for voltage set point.................................................................... 35 Figure 2-15: CANopen send data for voltage set point ....................................................................................... 36 Figure 2-16: Display screen - Receive PDO 1 for power factor set point ........................................................... 37 Figure 2-17: CANopen send data for power factor set point .............................................................................. 37 Figure 2-18: CANopen send data for Node ID 1 for power factor set point ....................................................... 38 Figure 2-19: Display screen - Receive PDO 1 for power set point ..................................................................... 39 Figure 2-20: CANopen send data for power set point......................................................................................... 39 Figure 2-21: Display screen - Receive PDO 1 for multiple set points ................................................................ 40 Figure 2-22: CANopen send data for multiple set points .................................................................................... 41 Figure 2-23: Display screen - Receive PDO 1 for changing the set point ........................................................... 42 Figure 2-24: CANopen send data for changing the set point .............................................................................. 42 Figure 2-25: CANopen send data for Node ID 1 for changing the set point ....................................................... 43 Figure 2-26: Cyclical sending of data - TPDO configuration ............................................................................. 44 Figure 2-27: Sending of data on request - TPDO configuration ......................................................................... 45 Figure 2-28: Cyclical sending of data - Sync Message request ........................................................................... 45 Figure 2-29: Cyclical sending of data - reply ...................................................................................................... 45 Figure 3-1: Modbus - visualization configurations ............................................................................................. 49 Figure 3-2: Modbus - configuration example 1................................................................................................... 51 Figure 3-3: Modbus - configuration example 2................................................................................................... 51 Figure 3-4: Modbus - configuration example 3................................................................................................... 53 Figure 3-5: Set point source configuration.......................................................................................................... 54 Figure 3-6: Modbus - configuration example 4 - active power ........................................................................... 55 Figure 3-7: Modbus - configuration example 4 - active power ........................................................................... 55 Figure 3-8: Modbus - configuration example 4 - active power ........................................................................... 55 Figure 3-9: Modbus - configuration example 4 - active power ........................................................................... 56 Figure 3-10: Modbus - configuration example 4 - power factor ......................................................................... 56 Figure 3-11: Modbus - configuration example 4 - frequency.............................................................................. 57 Figure 3-12: Modbus - configuration example 4 - voltage.................................................................................. 57 Figure 3-13: LogicsManager - Modbus encoding ............................................................................................... 58 Figure 3-14: Modbus - remote control parameter 503 ........................................................................................ 60 Figure 3-15: Modbus - write register - stop request ............................................................................................ 61 Figure 3-16: Modbus - write register - start request ............................................................................................ 61 Figure 3-17: Modbus - write register - external acknowledge............................................................................. 61 Figure 3-18: Modbus - remote control parameter 504 ........................................................................................ 62 Figure 3-19: Modbus - write register - enable active power set point 2 .............................................................. 62 Figure 3-20: Modbus - remote control parameter 504 ........................................................................................ 63 Figure 3-21: Modbus - write register - enable power factor set point 2 .............................................................. 63 Figure 3-22: Modbus - remote control parameter 504 ........................................................................................ 64 Figure 3-23: Modbus - write register - enable frequency set point 2 .................................................................. 64
Woodward Page 5/102
Manual 37383D
Figure 3-24: Modbus - remote control parameter 504 ......................................................................................... 65 Figure 3-25: Modbus - write register - enable voltage set point 2 ....................................................................... 65 Figure 3-26: Modbus configuration - Operat. mode AUTO ................................................................................ 67 Figure 3-27: Modbus configuration - Start req in AUTO .................................................................................... 68 Figure 3-28: Modbus configuration - External acknowledge............................................................................... 69 Figure 3-29: Modbus configuration - Start w/o load ........................................................................................... 70 Figure 3-30: Modbus - remote control parameter 522 ......................................................................................... 71 Figure 3-31: Modbus - write register - acknowledge alarm message ................................................................... 71 Figure 3-32: Modbus - remote control parameter 1706 ....................................................................................... 72 Figure 3-33: Modbus - write register - clear event history................................................................................... 72 Figure 3-34: Modbus - remote control parameter 1704 ....................................................................................... 73 Figure 3-35: Modbus - write register - enable the resetting procedure via RS-232 ............................................. 73 Figure 3-36: Modbus - remote control parameter 1701 ....................................................................................... 74 Figure 3-37: Modbus - write register - resetting the default values ..................................................................... 74 Figure 3-38: Remote control - start/stop priority ................................................................................................. 97
Tables
Table 1-1: Manual - overview................................................................................................................................ 7 Table 1-2: Interfaces - overview ............................................................................................................................ 8 Table 1-3: CAN interface 1 - I/O board combination matrix ................................................................................. 9 Table 2-1: CAN interface 1 - standard values for load sharing ............................................................................ 22 Table 2-2: CAN bus - transfer syntax for data type UNSIGNEDn ...................................................................... 24 Table 2-3: CAN bus - transfer syntax for data type INTEGERn .......................................................................... 25 Table 2-4: J1939 protocol - standard messages ................................................................................................... 26 Table 2-5: J1939 protocol - special EMR messages ............................................................................................ 27 Table 2-6: J1939 protocol - special S6 messages ................................................................................................. 27 Table 3-1: Modbus - address range ...................................................................................................................... 48 Table 3-2: Modbus - address range block read .................................................................................................... 49 Table 3-3: Modbus - address calculation ............................................................................................................. 50 Table 3-4: Modbus - data types ........................................................................................................................... 50 Table 3-5: Modbus - exception responses............................................................................................................ 75 Table 3-6: Load share message - example ........................................................................................................... 93 Table 3-7: Load share line - max. length ............................................................................................................. 93 Table 3-8: Remote control telegram..................................................................................................................... 96
Page 6/102
Woodward
Manual 37383D
Chapter 1. General Information

Document Overview
Type easYgen-3000 Series easYgen-3000 - Installation easYgen-3000 - Configuration easYgen-3000 - Operation easYgen-3000 - Application easYgen-3000 - Interfaces easYgen-3200 - Brief Operation Information easYgen-3100 - Brief Operation Information English German
this manual
37223 37224 37225 37226 37383 37399 37409
GR37223 GR37224 GR37225 GR37399 -
Table 1-1: Manual - overview
Intended Use The unit must only be operated in the manner described by this manual. The prerequisite for a proper and safe operation of the product is correct transportation, storage, and installation as well as careful operation and maintenance.
NOTE
This manual has been developed for a unit fitted with all available options. Inputs/outputs, functions, configuration screens, and other details described, which do not exist on your unit, may be ignored. The present manual has been prepared to enable the installation and commissioning of the unit. Due to the large variety of parameter settings, it is not possible to cover every combination. The manual is therefore only a guide. In case of incorrect entries or a total loss of functions, the default settings may be taken from the list of parameters enclosed in the configuration manual 37224 or from ToolKit and the respective *.SID file.
Abbreviations
The following abbreviations are frequently used in this documents: PDO RPDO TPDO SDO SSDO MSB LSB Process Data Object Receive PDO Transmit PDO Service Data Object Server SDO Most Significant Bit Least Significant Bit
Woodward
Page 7/102
Manual 37383D
Interface Overview
Depending on the respective model and package, the easYgen-3000 provides up to 3 CAN interfaces, 3 serial interfaces and 2 Ethernet interfaces. Table 1-2 indicates the interface set up of respective model and package.
Interface(s) easYgen-3100 easYgen-3200 CAN 2 2 Serial RS-232 1 1 Serial RS-485 1 1 Ethernet 0 0
Table 1-2: Interfaces - overview
ToolKit CANopen
(Protocol 5003)
(ServLink)
Modbus
(Protocol 5003)
CAN bus 1
RS-232
CAN bus 2 CANopen
RS-485 Modbus
J1939 ECU
(IKD 1 and Phoenix expansion boards)
(Protocol 5003)
ToolKit CANopen
(ServLink)
Modbus
(Protocol 5003)
(Protocol 5003)
CAN bus 1
RS-232
CAN bus 2 CANopen
RS-485 Modbus
J1939 ECU
(IKD 1 and Phoenix expansion boards)
(Protocol 5003)
Figure 1-1: easYgen - interface overview Page 8/102 Woodward
Manual 37383D
CAN Interfaces
Figure 1-2: Interface overview - CAN interfaces
CAN Interface 1 Freely Configurable CANopen Interface CAN interface 1 is a freely configurable CANopen interface with 3 RPDOs (receive boxes), 4 TPDOs (send boxes), and 4 additional Server SDOs. CAN Interface 2 (Engine Bus) The CAN interface 2 supports the CANopen and J1939 protocol simultaneously. Pre-Configured CANopen Interface CAN interface 2 is pre-configured for several expansion units. These include the I/O expansion boards Woodward IKD 1, Phoenix BK 16DiDo, and Phoenix Co 16DiDo. The following combinations of I/O expansion boards are possible:
Function RPDO 1 \ 2 OFF IKD 1 #1 IKD 1 #2 BK 16DiDo Co 16DiDo OFF YES YES YES YES YES IKD 1 #1 YES NO YES NO NO IKD 1 #2 YES YES NO NO NO BK 16DiDo YES NO NO YES NO Co 16DiDo YES NO NO NO YES
Table 1-3: CAN interface 1 - I/O board combination matrix
RPDO 1 and RPDO 2 of CAN interface 2 the communication with the configured expansion units) may be monitored individually. Refer to the Configuration Manual 37224 for more information about this monitoring function.
Woodward
Page 9/102
Manual 37383D
J1939 Interface The J1939 protocol enables to connect different Engine Control Units (ECUs) with the easYgen on the CAN bus. The following ECUs are supported: Woodward EGS Scania S6 MTU ADEC Deutz EMR2 Volvo EMS2 Volvo EDC4 MAN MFR/EDC7 SISU EEM2/EEM3
NOTE
If a Volvo EDC4 or a Deutz EMR3 ECU is utilized, all settings are to be configured as described for the Deutz EMR2 ECU in this manual.
Serial Interfaces
Figure 1-3: Interface overview - serial interfaces
Serial Interface 1 RS-232 A freely configurable RS-232 interface is provided to serve as a local service interface for configuring the unit and visualize measured data. It is possible to connect a modem for remote control and alarm signaling. The serial interface 1 provides ServLink and Modbus protocol simultaneously. Serial Interface 2 RS-485 A freely configurable RS-485 Modbus RTU Slave interface is provided to add PLC connectivity. It is also possible to configure the unit, visualize measured data and alarm messages, and control the unit remotely.
Page 10/102 Woodward
Manual 37383D
RS-485 Modbus Half/Full Duplex Application
Figure 1-4: Interface overview - serial interface Modbus full-duplex
Figure 1-5: Interface overview - serial interface Modbus half-duplex
Woodward
Page 11/102
Manual 37383D
Chapter 2. CAN Bus Configuration

CAN Interface Parameters
NOTE
The parameters in the following section are an excerpt of the Configuration Manual 37224. Refer to this manual for all parameters.
Configure CAN Interface 1

Baudrate Baudrate
{2oc}
CAN bus 1: Baud rate
20 / 50 / 100 / 125 / 250 / 500 / 800 / 1,000 kBaud
DE
EN
CL2
3156
{0}
{1o}
{1oc}
This parameter defines the used Baud rate. Please note, that all participants on the CAN bus must use the same Baud rate.
CAN bus 1: Node ID 1 to 127
CL2
8950
{0}
Node-ID CAN-Bus 1 Node-ID CAN-Bus 1

{1o}
DE
EN
{1oc}
{2oc}
A number that is unique to the control must be set in this parameter so that this control unit can be correctly identified on the CAN bus. This address number may only be used once on the CAN bus. All additional addresses are calculated based on this unique device number.
CAN bus 1: CANopen Master Default Master / On / Off
CL2
8993
{0}
{1o}
CANopen Master CANopen Master

{1oc}
DE
EN
{2oc}
One bus participant must take over the network management and put the other participants into "operational" mode. The easYgen is able to perform this task. Default Master The unit starts up in "operational" mode and sends a broadcast message (Start_Remote_Node) after a short delay (the delay is the Node ID (parameter 8950) in seconds, i.e. if the Node ID is configured to 2, the message will be sent after 2 seconds). If more than one easYgen is configured to Default Master, the unit with the lower Node ID will take over control. Therefore, the CAN bus devices, which are intended to act as Default Master should be assigned a low Node ID. No other device on the CAN bus (except the easYgens) may operate as Master). On ................ The unit is the CANopen Master and automatically changes into operational mode and sends broadcast messages (Start_Remote_Node), which cause all other units to change into operational mode as well. Off ............... The unit is a CANopen Slave. An external Master must change into operational mode.
NOTE
If CANopen Master (parameter 8993) is configured to "Off", the Master controller (for example a PLC) must send a "Start_Remote_node" message to initiate the load share message transmission of the easYgen. If no "Start_Remote_node" message would be sent, the complete system would not be operational.
Page 12/102
Woodward
Manual 37383D Producer heartbeat time Producer heartbeat time

{1o}
EN
CAN bus 1: Producer heartbeat time
0 to 65530 ms
DE
CL2
9120
{0}
{1oc}
{2oc}
Independent from the CANopen Master configuration, the unit transmits a heartbeat message with this configured heartbeat cycle time. If the producer heartbeat time is equal 0, the heartbeat will only be sent as response to a remote frame request. The time configured here will be rounded up to the next 20 ms step.
CAN bus 1: COB ID SYNC Message 1 to FFFFFFFF
CL2
9100
{0}
COB ID SYNC Message COB ID SYNC Message

{1o}
DE
EN
{1oc}
{2oc}
This parameter defines whether the unit generates the SYNC message or not.
Complies with CANopen specification: object 1005, subindex 0; defines the COB ID of the synchronization object (SYNC). The structure of this object is shown in the following tables: UNSIGNED 32 The bits in question are found on the following position 31 (MSB) 30 29 28-11 10-0 (LSB) X 0/1 X 000000000000000000 11 bit identifier The meaning of the bits is as follows bit number value meaning 31 (MSB) X N/A 30 0 Unit does not generate SYNC message 1 Unit generates SYNC message 29 X N/A 28-11 0 always 10-0 (LSB) X bits 10-0 of SYNC COB ID
Producer SYNC Message time Producer SYNC Message time CL2 {0} {1o} {1oc} {2oc} 8940
CAN bus 1: Sending time for SYNC Message
0 to 65000 ms
DE
This is the cycle time of the SYNC message. If the unit is configured for this function (parameter 9100) it will send the SYNC message with this interval. The time configured here will be rounded up to the next 10 ms step.
Additional Server SDOs (Service Data Objects)
NOTE
The CAN bus is a field bus and subject to various disturbances. Therefore, it cannot be guaranteed that every request will be answered. We recommend to repeat a request, which is not answered within reasonable time.
NOTE
The first Node ID is the standard Node ID of CAN interface 1 (parameter 8950).
2. Node-ID 2. Node-ID
{2oc}
CAN bus 1: Additional Server SDOs - 2. Node ID
0 to 127
DE
EN
CL2
33040
{0}
{1o}
{1oc}
In a multi-master application, each Master needs its own identifier (Node ID) from the unit. in order to send remote signals (i.e. remote start, stop, or acknowledge) to the unit. The additional SDO channel will be made available by configuring this Node ID to a value different than zero. This is the additional CAN ID for the PLC.
Woodward
Page 13/102
Manual 37383D 3. Node-ID 3. Node-ID

{2oc}
EN
CAN bus 1: Additional Server SDOs - 3. Node ID
0 to 127
DE
CL2
33041
{0}
{1o}
{1oc}
CAN bus 1: Additional Server SDOs - 4. Node ID 0 to 127
CL2
33042
{0}
{1o}
{1oc}
{2oc}
DE
EN
CAN bus 1: Additional Server SDOs - 5. Node ID 0 to 127
CL2
33043
{0}
{1o}
{1oc}
{2oc}
DE
EN
Receive PDOs (Process Data Objects) 1 to 3

COB-ID COB-ID
{2oc}
CAN bus 1: Receive PDO 1 - COB ID
1 to FFFFFFFH
DE
EN
CL2
9300 9310 9320
{0}
{1o}
{1oc}
This parameter contains the communication parameters for the PDOs, the device is able to receive.
Complies with CANopen specification: object 1400 (for RPDO 1, 1401 for RPDO 2, and 1402 for RPDO 3), subindex 1. The structure of this object is shown in the following tables: UNSIGNED The bits in question are found on the following position 32 31 (MSB) 30 29 28-11 10-0 (LSB) 0/1 X X 000000000000000000 11 bit identifier The meaning of the bits is as follows bit number value meaning 31 (MSB) 0 PDO exists / is valid 1 PDO does not exist / is not valid 30 X N/A 29 X N/A 28-11 0 always 10-0 (LSB) X bits 10-0 of COB ID PDO valid / not valid allows to select, which PDOs are used in the operational state.
Page 14/102
Woodward
Manual 37383D Number of Mapped Objects Anzahl der Mapped Objekte CL2 {0} {1o} {1oc} {2oc} 9910
33855 33860
EN
CAN bus 1: Receive PDO 1 - Number of mapped objects
0 to 4
DE
This parameter defines the number of valid entries within the mapping record. This number is also the number of the application variables, which shall be received with the corresponding PDO.
Complies with CANopen specification: object 1600 (for RPDO 1, 1601 for RPDO 2, and 1602 for RPDO 3), subindex 0
CL2
9911 33856 33861
{0}
{1o}
1. Mapped Object 1. Mapped Objekt

{1oc}
CAN bus 1: Receive PDO 1 - 1. mapped object
0 to 65535
DE
EN
{2oc}
This parameter contains the information about the mapped application variables. These entries describe the PDO contents by their index. The sub-index is always 1. The length is determined automatically.
CL2
9912 33857 33862
{0}
{1o}

{1oc}
0 to 65535
DE
EN
{2oc}
CL2
9913 33858 33863
{0}
{1o}

{1oc}
0 to 65535
DE
EN
{2oc}
CL2
9914 33859 33864
{0}
{1o}

{1oc}
0 to 65535
DE
EN
{2oc}
Figure 2-1 shows the principle of PDO mapping.
PDO Mapping 3 0 1 yyyyh 1 2 zzzzh 1 3 xxxxh 1
Object Dictionary xxxxh Application Object 1
yyyyh Application Object 2 zzzzh Application Object 3
PDO: App. Object 2 Application Object 3 App. Object 1

Figure 2-1: Interfaces - principle of PDO mapping
Woodward
Page 15/102
Manual 37383D
Transmit PDOs (Process Data Objects) 1 to 4

COB-ID COB-ID
{2oc}
CAN bus 1: Transmit PDO 1 - COB ID
1 to FFFFFFFH
DE
EN
CL2
9600 9610 9620 9630
{0}
{1o}
{1oc}
This parameter contains the communication parameters for the PDOs the unit is able to transmit. The unit transmits data (i.e. visualization data) on the CAN ID configured here.
Complies with CANopen specification: object 1800 for (TPDO 1, 1801 for TPDO 2, 1802 for TPDO 3, and 1803 for TPDO 4), subindex 1. The structure of this object is shown in the following tables: UNSIGNED 32 The bits in question are found on the following position 31 (MSB) 30 29 28-11 10-0 (LSB) 0/1 X X 000000000000000000 11 bit identifier The meaning of the bits is as follows bit number value meaning 31 (MSB) 0 PDO exists / is valid 1 PDO does not exist / is not valid 30 X N/A 29 X N/A 28-11 0 always 10-0 (LSB) X bits 10-0 of COB ID PDO valid / not valid allows to select, which PDOs are used in the operational state.
CL2
9602 9612 9622 9632
{0}
{1o}
Transmission type Transmission type

{1oc}
CAN bus 1: Transmit PDO 1 - Transmission type
0 to 255
DE
EN
{2oc}
This parameter contains the communication parameters for the PDOs the unit is able to transmit. It defines whether the unit broadcasts all data automatically (value 254 or 255) or only upon request with the configured address of the COB ID SYNC message (parameter 9100).
Complies with CANopen specification: object 1800 (for TPDO 1, 1801 for TPDO 2, 1802 for TPDO 3, and 1803 for TPDO 4), subindex 2. The description of the transmission type is shown in the following table: transmission type 0 1-240 241-251 252 253 254 255 PDO transmission cyclic acyclic synchronous will not be sent X X will not be sent will not be sent will not be sent asynchronous RTR only
X X
A value between 1 and 240 means that the PDO is transferred synchronously and cyclically. The transmission type indicating the number of SYNC, which are necessary to trigger PDO transmissions. Receive PDOs are always triggered by the following SYNC upon receiption of data independent of the transmission types 0 to 240. For TPDOs, transmission type 254 and 255 means, the application event is the event timer. Event-timer Event-timer
{1oc}
CAN bus 1: Transmit PDO 1 - Event timer
0 to 65500 ms
DE
EN
CL2
9604 9614 9624 9634
{0}
{1o}
{2oc}
This parameter contains the communication parameters for the PDOs the unit is able to transmit. The broadcast cycle for the transmitted data is configured here. The time configured here will be rounded up to the next 5 ms step.
Complies with CANopen specification: object 1800 (for TPDO 1, 1801 for TPDO 2, 1802 for TPDO 3, and 1803 for TPDO 4), subindex 5
Page 16/102
Woodward
Manual 37383D Number of Mapped Objects Anzahl der Mapped Objekte CL2 {0} {1o} {1oc} {2oc} 9609
9619 9629 9639
EN
CAN bus 1: Transmit PDO 1 - Number of mapped objects
0 to 4
DE
This parameter contains the mapping for the PDOs the unit is able to transmit. This number is also the number of the application variables, which shall be transmitted with the corresponding PDO.
Complies with CANopen specification: object 1A00 (for TPDO 1, 1A01 for TPDO 2, 1A02 for TPDO 3, and 1A03 for TPDO 4), subindex 0
CL2
9605 9615 9625 9635
{0}
{1o}

{1oc}
CAN bus 1: Transmit PDO 1 - 1. mapped object
0 to 65535
DE
EN
{2oc}
CL2
9606 9616 9626 9636
{0}
{1o}

{1oc}
0 to 65535
DE
EN
{2oc}
CL2
9607 9617 9627 9637
{0}
{1o}

{1oc}
0 to 65535
DE
EN
{2oc}
CL2
9608 9618 9628 9638
{0}
{1o}

{1oc}
0 to 65535
DE
EN
{2oc}
NOTE
CANopen allows to send 8 byte of data with each Transmit PDO. These may be defined separately if no pre-defined data protocol is used. All data protocol parameters with a parameter ID may be sent as an object with a CANopen Transmit PDO. In this case, the data length will be taken from the data byte column (refer to Appendix B: Data Protocols on page 79): 1,2 3,4 5,6 1,2,3,4 3,4,5,6 etc. The object ID is identical with the parameter ID when configuring via front panel or ToolKit.
Woodward Page 17/102
UNSIGNED16 or SIGNED16 UNSIGNED16 or SIGNED16 UNSIGNED16 or SIGNED16 UNSIGNED32 or SIGNED32 UNSIGNED32 or SIGNED32
Manual 37383D
Configure CAN Interface 2

Baudrate Baudrate
{2oc}
CAN bus 2: Baud rate
20 / 50 / 100 / 125 / 250 / 500 / 800 / 1,000 kBaud
DE
EN
CL2
3157
{0}
{1o}
{1oc}
This parameter defines the used Baud rate. Please note, that all participants on the CAN bus must use the same Baud rate.
CAN bus 2: Function for RPDO 1 refer to selection below
CL2
9055
{0}
Function for RPDO 1 Funktion fr RPDO 1

{1o}
DE
EN
{1oc}
{2oc}
The unit provides pre-configured CAN bus settings for the connection of different units. The unit to be connected must be selected here. no func. ........No external unit is selected for connection. The CAN bus is disabled. Values are not sent or received. 1st IKD .........The unit is pre-configured for the connection of a Woodward IKD 1 expansion board. 2nd IKD .......The unit is pre-configured for the connection of a second Woodward IKD 1 expansion board. BK 16 DIDO The unit is pre-configured for the connection of a Phoenix Contact BK 16 DIDO expansion board. Co 16 DIDO .The unit is pre-configured for the connection of a Phoenix Contact Co 16 DIDO expansion board.
CL2
9056
{0}
Function for RPDO 2 Funktion fr RPDO 2

{1o}
CAN bus 2: Function for RPDO 2
refer to selection below
DE
EN
{1oc}
{2oc}
The unit provides pre-configured CAN bus settings for the connection of different units. The unit to be connected must be selected here. no func. ........No external unit is selected for connection. The CAN bus is disabled. Values are not sent or received. 1st IKD .........The unit is pre-configured for the connection of a Woodward IKD 1 expansion board. 2nd IKD .......The unit is pre-configured for the connection of a second Woodward IKD 1 expansion board. BK 16 DIDO The unit is pre-configured for the connection of a Phoenix Contact BK 16 DIDO expansion board. Co 16 DIDO .The unit is pre-configured for the connection of a Phoenix Contact Co 16 DIDO expansion board.
Page 18/102
Woodward
Manual 37383D
J1939 Interface
J1939 device addresses J1939 Gerte-Adresse
{1o}
J1939 Interface: Device address
0 to 255
DE
EN
CL2
15106
{0}
{1oc}
{2oc}
The easYgen sends J1939 request and control messages with this ID. It must be changed for different ECU types according to the following table. The ECU listens only to to control messages, if they are sent on the correct address.
Scania S6 39 EMR2 Deutz 3 EMS2 Volvo 17 MTU ADEC 1 Woodward EGS 234 MAN EDC7 253 SISU EEM2/3 n/a
Details may be found in the manual of the genset control. Note: Changing this parameter becomes only effective after restarting the unit.
Engine control address Adresse Motorsteuerung
{1o}
J1939 Interface: Engine control address
0 to 255
DE
EN
CL2
15107
{0}
{1oc}
{2oc}
Configures the address of the J1939 device, which is controlled.

Scania S6 0 EMR2 Deutz 0 EMS2 Volvo 0 MTU ADEC 128 Woodward EGS 0 MAN EDC7 0 SISU EEM2/3 0 / (1) YES / NO
Reset previous act. DTCs - DM3 Quittieren passiver Fehler DM3 {1o} {1oc} {2oc} CL2 {0} 15108
J1939 Interface: Reset previously active DTCs - DM3
DE
EN
If this parameter is set YES, a DM3 message "Acknowledge passive faults" is sent. After that this parameter is reset automatically to NO. As a result alarms (DM2) which no longer apply are cleared.
J1939 Interface: SPN version Version 1 / Version 2 / Version 3
CL2
15103
{0}
{1o}
{1oc}
SPN version SPN Version

{2oc}
DE
EN
The J1939 protocol provides 4 different versions for formatting Suspect Parameter Number. This is important for a correct display of the alarm messages. With this parameter it is defined if formatting occurs according to Version 1, Version 2, or Version 3. Formatting according to Version 4 is identified automatically. Details may be found in the engine control unit (ECU) J1939 manual.
J1939 Interface: Device type refer to selection below
CL2
15102
{0}
{1o}
Device type Betriebsmodus

{1oc}
DE
EN
{2oc}
The J1939 interface of this device may be operated with different engine control units. This parameter determines the operating mode of the used ECU. Off ................ The J1939 interface is disabled. No messages will be sent/received. Standard ...... Standard J1939 messages will be sent or received. S6 Scania ..... Standard J1939 messages plus special S6 Scania messages. EMR2 Deutz Standard J1939 messages plus special Deutz EMR2 messages. EMS2 Volvo Standard J1939 messages plus special Volvo EMS2 messages. ADEC MTU Standard J1939 messages plus special MTU ADEC messages. EGS .............. Standard J1939 messages plus special Woodward EGS messages. MAN ............ Standard J1939 messages plus special MAN EDC7 messages. SISU EEM ... Standard J1939 messages plus special SISU EEM2/3 messages.
J1939 Interface: ECU remote control via J1939 ON / OFF
CL2
{0}
ECU remote controlled Fernsteuern der ECU ber J1939

{1o} {1oc} {2oc}
DE
EN
ON ................ The unit sends J1939 control messages to the ECU. Depending on
Woodward
Page 19/102
Manual 37383D
15127
the selected device type (Parmater 15102), contains a specific selection of commands. Available messages are speed deviation and droop for all ECUs as well as engine start/stop, enable idle mode, rated speed switch and preglow for some ECUs. Refer to Appendix A: Supported J1939 ECUs & Remote Control Messages on page 77 for the commands, the different ECUs are able to receive. OFF ............. The ECU remote control via the J1939 protocol will be disabled.
Page 20/102
Woodward
Manual 37383D Speed deviation ECU Drehzahlhub

{1o}
J1939 Interface: Speed deviation
0 to 1400 rpm
DE
EN
CL2
5537
{0}
{1oc}
{2oc}
This parameter is only visible if ECU remote controlled (Parameter 15127) is configured to "ON". This parameter adjusts the range of the speed deviation around the rated speed, which is sent to the ECU. It relates to the engine rated speed (parameter 1601). There are two methods of sending the speed set point to the ECU: With a speed offset and a speed setpoint. The frequency and power control must be configured to "PID". Speed offset: Scania S6, Volvo EMS2, EGS The easYgen sends a speed offset with a range of 0 to 100% (every 20 ms). 50% = rated speed. There is also an internal speed offset configured in the ECU, this parameter determines what corresponds with 0% or 100%. If there is a positive and a negative speed offset, they should be symmetrical in the ECU. We recommend to have the same speed offset configured in the ECU and in this parameter here. A different setting will result in an additional "controller gain". How to test this parameter during commissioning: Isolated operation: Disable the frequency controller and change parameter 5508 for the initial state between 0 and 100%, the engine should change the speed as follows: 0 = rated speed negative speed offset from ECU 50 = rated speed 100 = rated speed + positive speed offset from ECU Mains parallel operation: Check with the set point in the display if the engine is able to deliver the full power. Speed set point: Deutz EMR, MTU ADEC, EGS, SISU, Standard The easYgen sends a speed set point in rpm (every 10 ms) that varies around the rated speed in the range of +/- the speed deviation. How to test this parameter during commissioning: Isolated operation: Disable the frequency controller and change parameter 5508 for the initial state between 0 and 100%, the engine should change the speed as follows: 0 = rated speed speed deviation ECU e.g. 1500 120 = 1380rpm 50 = rated speed e.g. = 1500rpm 100 = rated speed + speed deviation ECU e.g. 1500 + 120 = 1620rpm Note: Keep this value as small as possible, i.e. do not enter a speed deviation of 500, if the engine varies only between 1400 and 1600rpm. Mains parallel operation: Check with the set point in the display if the engine is able to deliver the full power.
NOTE
The Wodward EGS ECU supports both types of speed deviation control and may be configured either to "Speed offset" or "Speed set point". In mains parallel operation, the EGS can be configured to receive a real power set point from the easYgen to control the power. In this case, real power control must be disabled in the easYgen.
Woodward
Page 21/102
Manual 37383D
CAN Bus Load Sharing

General Load Share Information
The maximum number of participating easYgen-3000 for load sharing is 32. The CANopen bus load increases with the number of units participating in load sharing. The following parameters effect the bus load: Number of CAN participants Baud rate Transfer rate of load share messages Visualization
We recommend to consider whether all data has to be sent on the CAN bus when planning the CAN bus. It is also possible to send visualization data via RS-485 for example. Typical Load Share Applications Load Sharing of up to 8 Gensets + Visualization Data Display Table 2-1 shows the standard setting for load sharing. These settings allow for load sharing of up to 8 gensets with the fastest transfer rate for the load sharing message and simultaneous transmission of all visualization data.
Index 3156 9921 9602 9604 9609 9605 Parameter Baudrate Transfer rate LS fast message Transmission type Event-timer Number of mapped objects 1. Mapped Object Setting 250 kBd 0.10 s 255 20 ms 1 16382 Comment
Protocol 5003
Table 2-1: CAN interface 1 - standard values for load sharing
Figure 2-2: CAN interface 1 - standard values for load sharing
Load Sharing of up to 16 Gensets + Visualization Data Display If you want to perform load sharing with up to 16 gensets with the fastest transfer rate for the load sharing message and simultaneous transmission of all visualization data, the transfer rate of the visualization data (parameter 9604) should be increased to 150 ms. Load Sharing of up to 32 Gensets without Visualization Data Display If you want to perform load sharing with up to 32 gensets with the fastest transfer rate for the load sharing message you should disable the simultaneous transmission of visualization data by setting the transmission type (parameter 9602) to "0". The minimum baud rate (parameter 3156) for this application is 250 kBd.
Page 22/102 Woodward
Manual 37383D
NOTE
Above settings are only recommendations and may vary depending on your specific application.
Measures for Reducing the Bus Load If you need to reduce the bus load of the load share CAN bus, the following measured may be used: Increase the baud rate (parameter 3156) under consideration of the bus length (refer to Installation Manual 37223) Reduce the transfer rate of the load share message (parameter 9921) Reduce the transfer rate of the visualization message, i.e. the event timer (parameter 9604) Disable the transmission visualization data on the CAN bus and use the RS-485 interface to transmit visualization data
Configure Load Share Parameters

Load share Interface Schnittstelle Lastverteilung
{1o}
CAN Interface: load share interface
CAN #1 / OFF
DE
EN
CL2
9923
{0}
---
---
{1oc}
---
{2oc}
The interface, which is used for transmitting the load share data is configured here.
CAN Interface: transfer rate load share fast message 0.10 to 0.30 s
CL2
9921
Transfer rate LS fast message Sendetakt der Lastverteilung

{0}
DE
EN
---
{1o}
---
{1oc}
---
{2oc}
The transfer rate defines the time delay between two fast CAN messages. In case of CAN systems with a high bus load (e.g. long distance between the units with low baud rate), a shorter transfer rate (higher time setting) helps to reduce the bus load.
CAN Interface: load share CAN ID 2xx Hex / 3xx Hex / 4xx Hex / 5xx Hex
CL2
9920
{0}
Load Share CAN-ID Lastverteilungs CAN-ID

{1o}
DE
EN
---
---
{1oc}
---
{2oc}
The first digit of the CAN ID or the range (i.e. 2xx means 200 through 2FF) is configured here. The last two digits will be assigned by the control with the settings from the device number.
Multi-Master Principle
It is important to know that the load share and load-dependent start/stop functionality is subject to a multi-master principle. This means that there is no dedicated master and slave function. Each easYgen decides for itself how it has to behave. The benefit is that the failure of a master control may cause a complete loss of this functionality. Each control is also responsible for controlling common breakers like a mains circuit or generator group breaker.
Woodward
Page 23/102
Manual 37383D
Definition of CANopen Protocol Descriptions

If a data protocol is used, a CAN message looks like this:
Byte 1 MUX Byte 2 Data byte Byte 3 Data byte Byte 4 Data byte Byte 5 Data byte Byte 6 Data byte Byte 7 Data byte Byte 8 internal
The MUX byte is counted up, the meaning of the data byte changes according to the value of the MUX byte. In the protocol tables is listed which parameter at which MUX on which position is transmitted. The meaning of the parameter can be taken by means of the number of the parameter description ("CANopen Mapping parameter"). Example:
MUX 1 Byte 2 118 Byte 3 Byte 4 Byte 5 Byte 6 147 Byte 7 Byte 8 internal
In MUX 1 (byte 1 has got value 1) the value of parameter 118 is included in the byte 2 up to byte 5 (mains voltage 1-2). In byte 6 up to byte 7 the value of parameter 147 is included (mains frequency). Byte 8 includes internal definitions and can be ignored. The data format is low Byte/high Byte (compare with CiA draft standard 01 on page 26).
Unsigned Integer
UNSIGNED type data has positive integers as values. The range is between 0 and 2n-1. The data is shown by the bit sequence of length n. Bit sequence shows the value
b = b0 to bn-1 UNSIGNEDn(b) = bn-1*2n-1+....+b1*21+b0*20
NOTE
Please note that the bit sequence starts on the left with the least significant byte. Example: Value 266 = 10A hex of type UNSIGNED16 is transmitted on the bus in two octets, first 0A hex and then 01 hex.
The following UNSIGNED data types are transmitted as follows:

Octet Number UNSIGNED8 UNSIGNED16 UNSIGNED24 UNSIGNED32 UNSIGNED40 UNSIGNED48 UNSIGNED56 UNSIGNED64 1. b7 to b0 b7 to b0 b7 to b0 b7 to b0 b7 to b0 b7 to b0 b7 to b0 b7 to b0 2. b15 to b8 b15 to b8 b15 to b8 b15 to b8 b15 to b8 b15 to b8 b15 to b8 3. b23 to b16 b23 to b16 b23 to b16 b23 to b16 b23 to b16 b23 to b16 4. 5. 6. 7. 8.
b31 to b24 b31 to b24 b31 to b24 b31 to b24 b31 to b24
b39 to b32 b39 to b32 b39 to b32 b39 to b32
b47 to b40 b47 to b40 b47 to b40
b55 to b48 b55 to b48
b63 to b56
Table 2-2: CAN bus - transfer syntax for data type UNSIGNEDn
Page 24/102
Woodward
Manual 37383D
SIGNED type data has integers as values. The range is between 0 and 2n-1. The data is shown by the bit sequence of length n. Bit sequence shows the value and with twos complement
Signed Integer
b = b0 to bn-1 SIGNEDn(b) = bn-2*2n-2+...+b1*21+b0*20 SIGNEDn(b) = SIGNEDn(^b)-1

if if
bn-1 = 0 bn-1 = 1
NOTE
Please note that the bit sequence starts on the left with the least significant byte. Example: The value -266 = FEF6 hex of type SIGNED16 is transmitted in two octets, first F6 hex and then FE hex.
The following SIGNED data types are transmitted as follows:

Octet Number SIGNED8 SIGNED16 SIGNED24 SIGNED32 SIGNED40 SIGNED48 SIGNED56 SIGNED64 1. b7 to b0 b7 to b0 b7 to b0 b7 to b0 b7 to b0 b7 to b0 b7 to b0 b7 to b0 2. b15 to b8 b15 to b8 b15 to b8 b15 to b8 b15 to b8 b15 to b8 b15 to b8 3. b23 to b16 b23 to b16 b23 to b16 b23 to b16 b23 to b16 b23 to b16 4. 5. 6. 7. 8.
b31 to b24 b31 to b24 b31 to b24 b31 to b24 b31 to b24
b39 to b32 b39 to b32 b39 to b32 b39 to b32
b47 to b40 b47 to b40 b47 to b40
b55 to b48 b55 to b48
b63 to b56
Table 2-3: CAN bus - transfer syntax for data type INTEGERn
Woodward
Page 25/102
Manual 37383D
J1939 Protocol Display Messages

Messages of a device (for example an ECU) are received on the CAN bus according to J1939 protocol and are shown on the display. This function can be used via the CAN interface parallel to the CANopen protocol or to ToolKit. The Baud rate is similar for all devices connected to the CAN bus independent of the selected protocol.
Displayed Messages
DM1/DM2 The first 10 active alarm messages (Active Diagnostic Trouble Codes - DM1) and the first 10 unacknowledged alarm messages (Previously Active Diagnostic Trouble Codes - DM2) with SPN, FMI, and OC are displayed. The state of the lamps DM1/2 is always displayed. SPN (= Suspect Parameter Number) indicates the measuring value that the alarm code is referring (e.g. SPN = 100 corresponds to oil pressure). FMI (= Failure Mode Indicator) specifies the alarm more precisely (e.g. FMI = 3 means: value is valid but higher than the standard value.) OC: (Occurrence Count) indicates how often an alarm occurred. IF OC = 0, no alarm is present PGN (= Parameter Group Number) defines a particular combination of SPNs. Refer to the J1939 specification for a list of all SPNs. Standard Messages
Suspect Parameter Description Resolution Display with defective Parameter Group sensor in ToolKit Number Number 91 61443 Throttle position 0.1% 6553.4% 92 61443 Load at current speed 1% 65534% 98 65263 Engine oil level 0.1% 6553.4% 100 65263 Engine oil pressure 1kPa 65534kPa 102 65270 Boost pressure 1kPa 65534kPa 105 65270 Intake manifold temperature 1C 32766C 108 65269 Barometric pressure 0.1kPa 65534kPa 110 65262 Engine coolant temperature C 32766C 111 65263 Coolant level 0.1% 6553.4% 172 65269 Air inlet temperature 1C 32766C 173 65270 Exhaust gas temperature 0.01C 21474836.46C 174 65262 Fuel temperature 1C 32766C 175 65262 Engine oil temperature 0.01C 21474836.46C 183 65266 Fuel rate 0.01 l/h 21474836.46 L/h 190 61444 Engine speed 0.1rpm 214748364.6rpm 247 65253 Total engine hours 1 1h 2147483646h 513 61444 Actual engine torque 1% 32766% 1 If the total engine hours sent by the ECU exceed 419,000 hrs, the display in the unit is not correct anymore Display with missing sensor value in ToolKit 6553.5% 65535% 6553.5% 65535kPa 65535kPa 32767C 65535kPa 32767C 6553.5% 32767C 21474836.47C 32767C 21474836.47C 21474836.47 L/h 214748364.7rpm 2147483647h 32767%
Table 2-4: J1939 protocol - standard messages
Page 26/102
Woodward
Manual 37383D
Data transmission by Engine Control Unit (ECU) If the sent values exceed the limits of the specification, the displayed value is not defined. If a value of the ECU is not sent or sent as not available or defective, the value will be displayed as indicated above. Special EMR Messages
Suspect Parameter Number Engine stop Type 0 1 2 3 4 5 6 7 8 9 Parameter Group Number 65301 (FF15h) Display in unit Type 0 Type 1 Type 2 Type 3 Type 4 Type 5 Type 6 Type 7 Type 8 Type 9 Description As Type 0 to 9 Display in ToolKit no stop Type 1. Engine safety Type 2: CAN message engine stop request Type 3: low oil pressure Type 4: low oil level Type 5: high coolant temp Type 6: low coolant level Type 7: intake manifold temp Type 8: reserved (Stop via SAE-J1587) Type 9: reserved (Stop via VP2) Table 2-5: J1939 protocol - special EMR messages
Message acc. to EMR manual Engine stop information Engine safety CAN message engine stop request Low oil pressure Low oil level High coolant temp Low coolant level Intake manifold temp Reserved (Stop via SAE-J1587) Reserved (Stop via VP2)
Special S6 Messages
Suspect Parameter Number DLN2-Proprietary Parameter Group Number 65409 (FF81h) Description Assessed messages: Low engine oil level High engine oil level Low oil pressure High coolant temperature Display in unit NO ---YES Display in ToolKit NO Sensor defect YES
Table 2-6: J1939 protocol - special S6 messages
If DLN2 does not transmit, the following is valid: the screens in the device are suppressed "missing" is displayed in ToolKit
Woodward
Page 27/102
Manual 37383D
Remote Control via CAN

Remote Start/Stop and Acknowledgement
Refer to the Performing Remote Start/Stop and Acknowledgement section in the Special Application Examples section of the application manual 37226 for detailed information. The easYgen may be started, stopped, or acknowledged with CAN/Modbus. Therefore, two logical command variables have to be configured with the LogicsManager: 04.13 04.14 Remote request Remote acknowledge
Two different methods to perform a remote start/stop/acknowledgement are detailed in the following. These are "Remote start/stop/acknowledgement via RPDO" and "Remote start/stop/acknowledgement via default SDO communication channel". The advantages and the disadvantages of these two methods are as follows: Comparison of the Two Methods Start/Stop/Acknowledgement via RPDO Classical communication for CANopen devices One message No validation of the received answer Only working in operational mode Start/Stop/Acknowledgement via Default SDO Communication Channel Configuration process Two messages Validation answer, if message has been received by the unit May take longer in case of communication with two messages Remote Start/Stop/Acknowledgement via RPDO Configuration of CAN Interface 1 Be sure to enable CAN-Open Master if there is no PLC taking over the master function. Navigate to the "Set up CAN interface 1" screen by pressing the following softkeys in this sequence: Parameter -> Configuration -> Configure interfaces -> Configure CAN interface -> Set up CAN interface 1
NOTE
The display field in the upper right corner indicates the path to the displayed screen by displaying the last four display screen levels, cf. Figure 2-3 with above navigation path.
Page 28/102
Woodward
Manual 37383D
Figure 2-3: Display screen - configure CAN interface 1
Navigate to the parameter "CAN-Open Master" by using the and softkeys. Press to change the parameter. Change the parameter value to "On" using the and softkeys. Confirm the change with the softkey. Configuration of the RPDO Press until you return to the start screen. Navigate to the "Configure CAN interface 1" screen by pressing the following softkeys in this sequence: Parameter -> Configuration -> Configure interfaces -> Configure CAN interface -> Configure CAN interface 1 Navigate to the entry "Receive PDO 1" by using the PDO 1" screen. and softkeys and press to enter the "Receive
Figure 2-4: Display screen - Receive PDO 1
Configure the following values for the "Receive PDO 1" parameters using the softkeys and Confirm the change by pressing the softkey: COB-ID 00000201 (hex) Number of Mapped Objects 1 1. Mapped Object 00503
and
as well as
and
Setting the COB-ID to 201 is exemplary; usually, the PDOs are in the range of 181 (hex) to 57F (hex). With this setting, the Receive PDO is set to the address, for which the device is listening on the bus. The number of mapped objects is 1 since 1 mapped object is used. The request on the bus is sent with the control parameter 503 of the device as mapped object 1.
NOTE
Refer to Chapter 3.Appendix B: Additional Data Protocol Parameters starting on page 96 for a list of additional parameter groups.
Woodward
Page 29/102
Manual 37383D
CANopen Request Figure 2-5 shows exemplary request data for the device on the CANopen bus. The data (hex) shows the state of parameter 503 to achieve the required control.
Figure 2-5: CANopen request data
Remote Start/Stop via Default SDO Communication Channel Another possibility for a remote start/stop/acknowledgement is to send the request via default SDO communication channel. The device listens to the CAN ID 600 (hex) + Node ID internally to perform the desired control, the reply is on CAN ID 580 (hex) + Node ID. The following examples show the request format on CANopen with different Node IDs. The request on the bus is sent via the control parameter 503 of the device. The hexadecimal value 2000 is calculated internally. 503(decimal) -- 1F7 (hexadecimal) 1F7+2000 (hexadecimal) = 21F7 Please note that high and low byte are exchanged in the sent address. The data (hex) shows the state of parameter 503 to achieve the required control. Node ID 1 standard Figure 2-6 shows exemplary request data for the device on the CANopen bus.
Figure 2-6: CANopen request data for Node ID 1
Page 30/102
Woodward
Manual 37383D
Node ID (not standard value) If the Node ID of the device is intended to be different from the standard value, the parameter "Node-ID CANBus 1" must be configured accordingly. Node ID 2 is used in the following example. until you return to the start screen. Press Navigate to the "Configure CAN interface 1" screen by pressing the following softkeys in this sequence: Parameter -> Configuration -> Configure interfaces -> Configure CAN interface -> Configure CAN interface 1
Figure 2-7: Display screen - Configure CAN interface 1
Configure the following value for the "Node-ID CAN-Bus 1" parameter using the softkeys and Confirm the change by pressing the softkey: Node-ID CAN-Bus 1 002 With this setting, the Node ID of the CAN interface 1 is set to 002. The request on the bus is sent via the control parameter 503 of the device. The hexadecimal value 2000 is calculated internally. 503(decimal) -- 1F7 (hexadecimal) 1F7+2000 (hexadecimal) = 21F7 Please note that high and low byte are exchanged in the sent address. The data (hex) shows the state of parameter 503 to achieve the required control. Figure 2-8 shows exemplary request data for the device on the CANopen bus.
and
as well as
and
Figure 2-8: CANopen request data for Node ID 2
Woodward
Page 31/102
Manual 37383D
Additional SDO Communication Channels It is also possible to allow several PLCs to start/stop/acknowledge the unit in addition to the default SDO communication channel. Four additional SDO communication channels are provided for this. The additional SDO 127 (decimal) is used in the following example. until you return to the start screen. Press Navigate to the "Configure CAN interface 1" screen by pressing the following softkeys in this sequence: Parameter -> Configuration -> Configure interfaces -> Configure CAN interface -> Configure CAN interface 1 Navigate to the entry "Additional Server SDOs" by using the ceive PDO 1" screen. and softkeys and press to enter the "Re-
Figure 2-9: Display screen - Additional Server SDOs
Configure the following value for the "2. Node-ID" parameter using the keys and Confirm the change by pressing the softkey: 2. Node-ID 127 = 7F (hex)
and
as well as
and
soft-
With this setting, an additional SDO communication channel is configured to 127. The control request is equal to the request via default SDO communication channel, but the device will listen to messages including the configured address as well. The device listens to the CAN ID 600 (hex) + 2. Node ID internally to perform the desired control, the reply from the easYgen is sent on CAN ID 580 (hex) + 2. Node ID. Receive CAN ID 67F (hex) (600 (hex) + 7F (hex)) Receive CAN ID 5FF (hex) (580 (hex) + 7F (hex)) The same is valid for the additional SDO communication channels 3, 4, and 5.
Page 32/102
Woodward
Manual 37383D
Figure 2-10 shows exemplary request data for the device on the CANopen bus.
Figure 2-10: CANopen request data for additional Server SDO
NOTE
If parameters are written or read via two or more SDO communication channels at the same time (before the first has answered), the second one will be refused.
Transmitting a Frequency Set Point via CANopen

It is possible to transmit a frequency set point value via the CANopen interface. Prerequisite for the use of a frequency set point via an interface is the configuration of the frequency set point source (parameter ID 5518 for frequency set point 1 source or parameter ID 5519 for frequency set point 2 source; refer to the Configuration Manual 37224 for detailed information). The respective frequency set point source is to be configured to 05.03 "Interface freq.setp.". Two different methods to transmit a frequency set point via CANopen interface are detailed in the following. Refer to Comparison of the Two Methods on page 28 for the basic differences of these methods. Transmitting a Frequency Set Point via RPDO Configuration of CAN Interface 1 Be sure to enable CAN-Open Master if there is no PLC taking over the master function. Refer to Configuration of CAN Interface 1 on page 28 for the configuration of this parameter. Configuration of the RPDO until you return to the start screen. Press Navigate to the "Configure CAN interface 1" screen by pressing the following softkeys in this sequence: Parameter -> Configuration -> Configure interfaces -> Configure CAN interface -> Configure CAN interface 1 Navigate to the entry "Receive PDO 1" by using the PDO 1" screen. and softkeys and press to enter the "Receive
Figure 2-11: Display screen - Receive PDO 1 for frequency set point
Woodward
Page 33/102
Manual 37383D
and
as well as
and
NOTE
CANopen Request Figure 2-12 shows exemplary send data for the device on the CANopen bus. A frequency set point of 50.60 Hz is transmitted (5060 (dec) = 13C4 (hex) -> C4 13 according to the CANopen protocol).
Figure 2-12: CANopen send data for frequency set point
Transmitting a Frequency Set Point via Default SDO Communication Channel Another possibility for transmitting a frequency set point is to send the value via default SDO communication channel. The device listens to the CAN ID 600 (hex) + Node ID internally to perform the desired control, the reply is on CAN ID 580 (hex) + Node ID. The following example shows the send format on CANopen with Node ID 1. The value is sent on the bus via the control parameter 509 of the device. The hexadecimal value 2000 is calculated internally. 509(decimal) -- 1FD (hexadecimal) 1FD+2000 (hexadecimal) = 21FD Please note that high and low byte are exchanged in the sent value. The data (hex) shows the state of parameter 509 to achieve the required control. Figure 2-13 shows exemplary send data for the device on the CANopen bus.
Figure 2-13: CANopen send data for Node ID 1 for frequency set point Page 34/102 Woodward
Manual 37383D
Transmitting a Voltage Set Point via CANopen

It is possible to transmit a voltage set point value via the CANopen interface. Prerequisite for the use of a voltage set point via an interface is the configuration of the voltage set point source (parameter ID 5618 for voltage set point 1 source or parameter ID 5619 for voltage set point 2 source; refer to the Configuration Manual 37224 for detailed information). The respective voltage set point source is to be configured to 05.09 "Interface volt.setp.". Two different methods to transmit a voltage set point via CANopen interface are detailed in the following. Refer to Comparison of the Two Methods on page 28 for the basic differences of these methods. Transmitting a Voltage Set Point via RPDO Configuration of CAN Interface 1 Be sure to enable CAN-Open Master if there is no PLC taking over the master function. Refer to Configuration of CAN Interface 1 on page 28 for the configuration of this parameter. Configuration of the RPDO until you return to the start screen. Press Navigate to the "Configure CAN interface 1" screen by pressing the following softkeys in this sequence: Parameter -> Configuration -> Configure interfaces -> Configure CAN interface -> Configure CAN interface 1 Navigate to the entry "Receive PDO 1" by using the PDO 1" screen. and softkeys and press to enter the "Receive
Figure 2-14: Display screen - Receive PDO 1 for voltage set point
and
as well as
and
NOTE
Woodward
Page 35/102
Manual 37383D
CANopen Request Figure 2-15 shows exemplary send data for the device on the CANopen bus in line 1. A voltage set point of 412 V is transmitted (412 (dec) = 019C (hex) -> 9C 01 according to the CANopen protocol).
Figure 2-15: CANopen send data for voltage set point
Transmitting a Voltage Set Point via Default SDO Communication Channel Another possibility for transmitting a voltage set point is to send the value via default SDO communication channel. The device listens to the CAN ID 600 (hex) + Node ID internally to perform the desired control, the reply is on CAN ID 580 (hex) + Node ID. The following example shows the send format on CANopen with Node ID 1. The value is sent on the bus via the control parameter 510 of the device. The hexadecimal value 2000 is calculated internally. 510(decimal) -- 1FE (hexadecimal) 1FE+2000 (hexadecimal) = 21FE Please note that high and low byte are exchanged in the sent value. The data (hex) shows the state of parameter 510 to achieve the required control. Figure 2-15 shows exemplary send data for the device on the CANopen bus in line 2.
Transmitting a Power Factor Set Point via CANopen

It is possible to transmit a power factor set point value via the CANopen interface. Prerequisite for the use of a power factor set point via an interface is the configuration of the power factor set point source (parameter ID 5638 for power factor set point 1 source or parameter ID 5639 for power factor set point 2 source; refer to the Configuration Manual 37224 for detailed information). The respective power factor set point source is to be configured to 05.03 "Interface PF setp.". Two different methods to transmit a power factor set point via CANopen interface are detailed in the following. Refer to Comparison of the Two Methods on page 28 for the basic differences of these methods. Transmitting a Power Factor Set Point via RPDO Configuration of CAN Interface 1 Be sure to enable CAN-Open Master if there is no PLC taking over the master function. Refer to Configuration of CAN Interface 1 on page 28 for the configuration of this parameter.
Page 36/102
Woodward
Manual 37383D
Configuration of the RPDO Press until you return to the start screen. Navigate to the "Configure CAN interface 1" screen by pressing the following softkeys in this sequence: Parameter -> Configuration -> Configure interfaces -> Configure CAN interface -> Configure CAN interface 1 Navigate to the entry "Receive PDO 1" by using the PDO 1" screen. and softkeys and press to enter the "Receive
Figure 2-16: Display screen - Receive PDO 1 for power factor set point
and
as well as
and
NOTE
CANopen Request Figure 2-17 shows exemplary send data for the device on the CANopen bus. A power factor set point of 0.85 capacitive/leading is transmitted (64689 (dec) [65536-850] = FCAE (hex) -> AE FC according to the CANopen protocol) in line 1. Please note that negative (capacitive or leading) power factor values are deducted from 65536 (dec) or FFFF (hex). A power factor set point of 0.9 inductive/lagging is transmitted (900 (dec) = 0384 (hex) -> 84 03 according to the CANopen protocol) in line 2. A power factor set point of 1.0 is transmitted (1000 (dec) = 03E8 (hex) -> E8 03 according to the CANopen protocol) in line 3.
Figure 2-17: CANopen send data for power factor set point
Woodward
Page 37/102
Manual 37383D
Transmitting a Power Factor Set Point via Default SDO Communication Channel Another possibility for transmitting a power factor set point is to send the value via default SDO communication channel. The device listens to the CAN ID 600 (hex) + Node ID internally to perform the desired control, the reply is on CAN ID 580 (hex) + Node ID. The following example shows the send format on CANopen with Node ID 1. Thevalue is sent on the bus via the control parameter 508 of the device. The hexadecimal value 2000 is calculated internally. 508(decimal) -- 1FC (hexadecimal) 1FC+2000 (hexadecimal) = 21FC Please note that high and low byte are exchanged in the sent value. The data (hex) shows the state of parameter 508 to achieve the required control. Figure 2-18 shows exemplary send data for the device on the CANopen bus.
Figure 2-18: CANopen send data for Node ID 1 for power factor set point
Transmitting a Power Set Point via CANopen

It is possible to transmit a power set point value via the CANopen interface. Prerequisite for the use of a power set point via an interface is the configuration of the power set point source (parameter ID 5539 for power set point 1 source or parameter ID 5540 for power set point 2 source; refer to the Configuration Manual 37224 for detailed information). The respective power set point source is to be configured to 05.09 "Interface pow. setp.". Please note that the type of the power set point (Constant, Import, or Export) must also be defined (parameter ID 5526 for load set point 1 or parameter ID 5527 for load set point 2). Two different methods to transmit a voltage set point via CANopen interface are detailed in the following. Refer to Comparison of the Two Methods on page 28 for the basic differences of these methods. Transmitting a Power Set Point via RPDO Configuration of CAN Interface 1 Be sure to enable CAN-Open Master if there is no PLC taking over the master function. Refer to Configuration of CAN Interface 1 on page 28 for the configuration of this parameter.
Page 38/102
Woodward
Manual 37383D
Figure 2-19: Display screen - Receive PDO 1 for power set point
and
as well as
and
NOTE
CANopen Request Figure 2-20 shows exemplary send data for the device on the CANopen bus in line 1. A power set point of 1000.0 kW is transmitted (10000 (dec) = 2710 (hex) -> 10 27 according to the CANopen protocol).
Figure 2-20: CANopen send data for power set point
Woodward
Page 39/102
Manual 37383D
Transmitting a Power Set Point via Default SDO Communication Channel Another possibility for transmitting a power set point is to send the value via default SDO communication channel. The device listens to the CAN ID 600 (hex) + Node ID internally to perform the desired control, the reply is on CAN ID 580 (hex) + Node ID. The following example shows the send format on CANopen with Node ID 1. The value is sent on the bus via the control parameter 507 of the device. The hexadecimal value 2000 is calculated internally. 507(decimal) -- 1FB (hexadecimal) 1FB+2000 (hexadecimal) = 21FB Please note that high and low byte are exchanged in the sent value. The data (hex) shows the state of parameter 507 to achieve the required control. Figure 2-20 shows exemplary send data for the device on the CANopen bus in line 2.
Transmitting Multiple Set Points via CANopen

It is possible to transmit multiple objects with one RPDO. The receive PDO can be used for four objects with 16 bytes. If larger objects (for example 32 bytes, like for voltage and power set points) are used, the maximum number of objects is reduced. Configuration of the RPDO until you return to the start screen. Press Navigate to the "Configure CAN interface 1" screen by pressing the following softkeys in this sequence: Parameter -> Configuration -> Configure interfaces -> Configure CAN interface -> Configure CAN interface 1 Navigate to the entry "Receive PDO 1" by using the PDO 1" screen. and softkeys and press to enter the "Receive
Figure 2-21: Display screen - Receive PDO 1 for multiple set points
Configure the following values for the "Receive PDO 1" parameters using the softkeys and Confirm the change by pressing the softkey: COB-ID Number of Mapped Objects 1. Mapped Object 2. Mapped Object 3. Mapped Object 00000321 (hex) 3 00509 00507 00508
and
as well as
and
Page 40/102
Woodward
Manual 37383D
Setting the COB-ID to 321 is exemplary; usually, the PDOs are in the range of 181 (hex) to 57F (hex). With this setting, the Receive PDO is set to the address, for which the device is listening on the bus. The number of mapped objects is 1 since 1 mapped object is used. The request on the bus is sent with the control parameters 509, 507, and 508 of the device as mapped object 1.
NOTE
CANopen Request Figure 2-22 shows exemplary send data for the device on the CANopen bus in line 1. The following set points are transmitted: Frequency 50.6 Hz (5060 (dec) = 13C4 (hex) -> C4 13 according to the CANopen protocol) Power 1000 kW (10000 (dec) = 2710 (hex) -> 10 27 according to the CANopen protocol) Power factor 0.9 lagging (900 (dec) = 0384 (hex) -> 84 03 according to the CANopen protocol)
Figure 2-22: CANopen send data for multiple set points
Remotely Changing the Set Point via CANopen

It is possible to remotely change a set point value via the CANopen interface using the parameter ID 504 (refer to Remote Control Word 2 - Object 21F8h (Parameter ID 504) on page 97). In order to enable the set point 2 of the respective control function, different bits of parameter ID 504 must be enabled: [04.37] Remote voltage set point 2 bit 4 10 00 (hex) must be sent to parameter ID 504 [04.38] Remote frequency set point 2 bit 5 20 00 (hex) must be sent to parameter ID 504 [04.39] Remote Power Factor set point 2 bit 6 30 00 (hex) must be sent to parameter ID 504 [04.40] Remote power set point 2 bit 7 80 00 (hex) must be sent to parameter ID 504
NOTE
For remotely changing the control set points, it is necessary to use the interface set points instead of the internal set points. In order to use the interface set points, the set point source parameters (for example "Frequency setpoint 1 source" or "Frequency setpoint 2 source") of the controller must be configured to the respective interface set points as data source (refer to the Configure Controller section in the Parameters chapter of the configuration manual 37224 for detailed information).
Two different methods for changing a set point via CANopen interface are detailed in the following. Refer to Comparison of the Two Methods on page 28 for the basic differences of these methods. Changing a Set Point via RPDO Configuration of CAN Interface 1 Be sure to enable CAN-Open Master if there is no PLC taking over the master function. Refer to Configuration of CAN Interface 1 on page 28 for the configuration of this parameter.
Woodward
Page 41/102
Manual 37383D
Figure 2-23: Display screen - Receive PDO 1 for changing the set point
and
as well as
and
Setting the COB-ID to 321 is exemplary; usually, the PDOs are in the range of 181 (hex) to 57F (hex). With this setting, the Receive PDO is set to the address, for which the device is listening on the bus. The number of mapped objects is 1 since 1 mapped object is used. The request on the bus is sent with the control parameter 504 of the device as mapped object 1. CANopen Request Figure 2-24 shows exemplary send data for the device on the CANopen bus. The respective bits are enabled by sending the data of the respective lines.
Figure 2-24: CANopen send data for changing the set point
Page 42/102
Woodward
Manual 37383D
Changing a Set Point via Default SDO Communication Channel Another possibility for changing a set point is to enable the bit via default SDO communication channel. The device listens to the CAN ID 600 (hex) + Node ID internally to perform the desired control, the reply is on CAN ID 580 (hex) + Node ID. The following example shows the send format on CANopen with Node ID 1. The value is sent on the bus via the control parameter 504 of the device. The hexadecimal value 2000 is calculated internally. 509(decimal) -- 1F8 (hexadecimal) 1F8+2000 (hexadecimal) = 21F8 Please note that high and low byte are exchanged in the sent value. The data (hex) shows the state of parameter 504 to achieve the required control. Figure 2-25 shows exemplary send data for the device on the CANopen bus.
Figure 2-25: CANopen send data for Node ID 1 for changing the set point
Woodward
Page 43/102
Manual 37383D
Sending a Data Protocol via TPDO

Cyclically Sending of Data
This is a configuration example for sending an object with the index 16382 (data protocol 5003) on CAN ID 2AEh every 20 ms on TPDO1. For this, TPDO1 must be configured as follows: COB-ID Transmission type Event-timer Number of Mapped Objects 1. Mapped Object 2. Mapped Object 3. Mapped Object 4. Mapped Object 2AE (hex) 255 20 ms 1 (there is only one object to be transmitted) 16382 (display value, the object with the index 16382) 0 (will not be used) 0 (will not be used) 0 (will not be used)
Figure 2-26: Cyclical sending of data - TPDO configuration
Sending of Data on Request

The data to be sent (Mapped Objects) may be provided on request by configuring the Sync Message (Parameter 9100) and the Transmission Type (Parameter 9602, 9612, 9622, or 9632) of a TPDO. The unit is requested to send its data by sending a Sync Message. The number of required Sync Messages is determined by the setting of the Transmission Type. If the data is to be sent on request, Bit 31 of the Sync Message (Parameter 9100) must be configured to "1" and the CANopen Master (Parameter 8993) function must be configured to "Off". The Transmission Type of TPDO 1 is configured to "2" in the following example (refer to Figure 2-27). This means that a message of the configured TPDO is sent by the unit after two Sync Messages have been sent to the unit.
Page 44/102
Woodward
Manual 37383D
Figure 2-27: Sending of data on request - TPDO configuration
The recorded data shows that the data of the Mapped Object (in this example Mux 5) is sent (refer to Figure 2-29) after sending the Sync Message twice (refer to Figure 2-28).
Figure 2-28: Cyclical sending of data - Sync Message request
Figure 2-29: Cyclical sending of data - reply
Woodward
Page 45/102
Manual 37383D
External DOs for an IKD 1

This is a configuration example for sending objects with the index 8001 and 3 x 8000 on CAN ID 181h every 20 ms on TPDO1. This is used to send messages to an external device. For this, TPDO1 must be configured as follows: COB-ID Transmission type Event-timer Number of Mapped Objects 1. Mapped Object 2. Mapped Object 3. Mapped Object 4. Mapped Object 181 (hex) 255 20 ms 4 (there are four objects to be transmitted) 8001 (display value, the object with the index 8001) 8000 (display value, the object with the index 8000) 8000 (display value, the object with the index 8000) 8000 (display value, the object with the index 8000)
NOTE
This is an example of how to configure an IKD 1 on CAN interface 1. Usually, IKDs may be configured to CAN interface 2 much easier.
Receiving Data from an IKD 1

This is a configuration example for an RPDO configuration. The data received on CAN ID 201h is interpreted as object with the index 8011 (external DIs 1 to 8). For this, RPDO must be configured as follows: COB-ID Number of Mapped Objects 1. Mapped Object 2. Mapped Object 3. Mapped Object 4. Mapped Object 201 (hex) 1 (there is only one object to be received) 8011 (display value, the object with the index 8011) 0 (will not be used) 0 (will not be used) 0 (will not be used)
NOTE
This is an example of how to configure an IKD 1 on CAN interface 1. Usually, IKDs may be configured to CAN interface 2 much easier.
Page 46/102
Woodward
Manual 37383D
Chapter 3. Modbus Communications

General Information
Modbus is a serial communications protocol published by Modicon in 1979 for use with its programmable logic controllers (PLCs). It has become a de facto standard communications protocol in industry, and is now the most commonly available means of connecting industrial electronic devices. The easYgen-3000 supports a Modbus RTU Slave module. This means that a Master node needs to poll the easYgen slave node. Modbus RTU can also be multi-dropped, or in other words, multiple Slave devices can exist on one Modbus RTU network, assuming that the serial interface is a RS-485. Detailed Information about the Modbus protocol are available on the following website: http://www.modbus.org/specs.php There are also various tools available on the internet. We recommend to use ModScan32 which is a Windows application designed to operate as a Modbus Master device for accessing data points in a connected Modbus Slave device. It is designed primarily as a testing device for verification of correct protocol operation in new or existing systems. It is possible to download a trial version from the following website: http://www.win-tech.com/html/modscan32.htm
Woodward
Page 47/102
Manual 37383D
Address Range
The easYgen Modbus Slave module distinguishes between visualization data and configuration & remote control data. The different data is accessible over a split address range and can be read via the "Read Holding Register" function. Furthermore, easYgen parameters and remote control data can be written with the "Preset Single Registers" function or "Preset Multiple Registers" (refer to Table 3-1).
Modbus address: Modbus function codes:
easYgen visualization data
Read Holding Register (0x03)
450001 450000 easYgen remote control & configuration data Read Holding Register (0x03) Preset Multiple Registers (0x10) Preset Single Register (0x06)
40001
Table 3-1: Modbus - address range
NOTE
All addresses in this document comply with the Modicon address convention. Some PLCs or PC programs use different address conventions depending on their implementation. Then the address must be increased and the leading 4 may be omitted. Please refer to your PLC or program manual for more information. This determines the address sent over the bus in the Modbus telegram. The Modbus starting address 450001 of the visualization data may become bus address 50000 for example.
Page 48/102
Woodward
Manual 37383D
Visualization
The visualization over Modbus is provided in a very fast data protocol where important system data like alarm states, AC measurement data, switch states and various other information may be polled. According to the easYgen Modbus addressing range, the visualization protocol can be reached on addresses starting at 450001. On this address range it is possible to do block reads from 1 up to 128 Modbus registers at a time.
Modbus Read Addresses 450001 450002 ............ ............ ............ ............ 450268 Description Protocol-ID, always 5003 Pickup speed ......... ......... ......... ......... Exhaust Gas Temp. Multiplier 1 ..... ..... ..... ..... 0.01 Units -rpm ..... ..... ..... ..... C
Table 3-2: Modbus - address range block read
NOTE
Table 3-2 is only an excerpt of the data protocol. It conforms to the data protocol 5003 that is also used by CAN bus. Refer to Appendix B: Data Protocol 5003 on page 79 for the complete protocol.
The following ModScan32 screenshot shows the configurations made to read the visualization protocol with a block read of 128 registers.
Figure 3-1: Modbus - visualization configurations Woodward Page 49/102
Manual 37383D
Configuration
The Modbus interface can be used to read/write parameters of the easYgen. According to the easYgen Modbus addressing range for the configuration addresses, the range starts at 40001 and ends at 450000. You can always access only one parameter of the system in this address range. The Modbus address can be calculated depending on the parameter ID as illustrated below:
Modbus address = Parameter ID < 10000 40000 + (Par. ID+1) Parameter ID >= 10000 400000 + (Par. ID+1)
Table 3-3: Modbus - address calculation
Block reads in this address range depend on the data type of the parameter. This makes it important to set the correct length in Modbus registers which depends on the data type (UNSIGNED 8, INTEGER 16, etc.). Refer to Table 3-4 for more information.
easYgen types Modbus registers
1 1 1 2 2 7 X/2
UNSIGNED 16 UNSIGNED 32 INTEGER 32 LOGMAN TEXT/X INTEGER 16
UNSIGNED 8
Table 3-4: Modbus - data types
Parameter Setting NOTE

The example tables below are excerpts of the parameter list in the Configuration Manual 37224. Please refer to this manual for the complete parameter list.
NOTE
Be sure to enter the password for code level 2 or higher for the corresponding interface to get access for changing parameter settings.
NOTE
The new entered value must comply with the parameter setting range when changing the parameter setting.
Page 50/102
Woodward
Manual 37383D
Example 1: Addressing the password for serial interface1:

Par. ID. 10401 Parameter Password for serial interface1 Setting range 0000 to 9999 Data type
UNSIGNED 16
Modbus address = 400000 + (Par. ID + 1) = 410402 Modbus length = 1 (UNSIGNED 16) The following Modscan32 screenshot shows the configurations made to address parameter 10401.
Figure 3-2: Modbus - configuration example 1
Example 2: Addressing the generator rated voltage:

Par. ID. 1766 Parameter Generator rated voltage Setting range 50 to 650000 V Data type
UNSIGNED 32
Modbus address = 40000 + (Par. ID + 1) = 41767 Modbus length = 2 (UNSIGNED 32) The following Modscan32 screenshot shows the configurations made to address parameter 1766.
NOTE
The parameters of above examples are an excerpt of the parameter list in the appendix of the Configuration Manual 37224. Refer to this manual for the complete parameter list.
Woodward Page 51/102
Manual 37383D
Page 52/102
Woodward
Manual 37383D
Example 3: Addressing the generator voltage measuring:

Par. ID. 1851 Parameter Generator voltage measuring Setting range 3Ph 4W {0} 3Ph 3W {1} 1Ph 2W {2} 1Ph 3W {3} Data type
UNSIGNED 16
Modbus address = 40000 + (Par. ID + 1) = 41852 Modbus length = 1 (UNSIGNED 16)
NOTE
If the setting range contains a list of parameter settings like in this example, the parameter settings are numbered and start with 0 for the first parameter setting. The number corresponding with the respective parameter setting must be configured.
The following Modscan32 screenshot shows the configurations made to address parameter 1851, which is configured to "3Ph 4W".
Woodward
Page 53/102
Manual 37383D
Set Point Setting

For a remote setting of the control set points, it is necessary to use the interface set points instead of the internal set points. In order to use the interface set points, the set point source parameters of the controller must be configured to the respective interface set points (refer to the Configure Controller section in the Parameters chapter of the configuration manual 37224 for detailed information). Figure 3-5 shows an exemplary configuration of the load set point 1 source. All other set point sources are configured accordingly.
Figure 3-5: Set point source configuration
The interface set points may be set using the objects for active power, power factor, frequency, and voltage (refer to Additional Data Protocol Parameters on page 96 for detailed information).
Par. ID. 507 508 509 510 Parameter Active Power Setpoint Power Factor Setpoint Frequency Setpoint Voltage Setpoint Setting range 0 to 999999 -710 to 1000 to 710 0 to 7000 50 to 650000 Unit 1/10 [kW] 1/100 [Hz] [V] Data type
INTEGER 32 UNSIGNED 16 UNSIGNED 32 INTEGER 16
Page 54/102
Woodward
Manual 37383D
Example 1: Active Power Interface Set Point The active power set point value must be written to object 21FB (hex), i.e. parameter ID 507 Example: A power value of 50 kw = 500 (dec) =01F4 (hex) is to be transmitted. Modbus address = 40000 + (Par. ID + 1) = 40508 Modbus length = 2 (INTEGER 32) The high word is to be written to the lower address and the low word is to be written to the higher address. Figure 3-6 through Figure 3-9 show how to set the parameter address 507 in ModScan32.
Figure 3-6: Modbus - configuration example 4 - active power
Open the Preset Multiple registers window by selecting Setup -> Extended -> Preset Regs from the menu.
Select OK and enter the desired values.
Figure 3-8: Modbus - configuration example 4 - active power Woodward Page 55/102
Manual 37383D
Select Update to take over the entered values.
Example 2: Power Factor Interface Set Point The power factor set point value must be written to object 21FC (hex), i.e. parameter ID 508 Example: A power factor of 1 = 1000 (dec) =03E8 (hex) is to be transmitted. Modbus address = 40000 + (Par. ID + 1) = 40509 Modbus length = 1 (UNSIGNED 16) Figure 3-10 shows the settings made to parameter address 508 in ModScan32.
Figure 3-10: Modbus - configuration example 4 - power factor
Page 56/102
Woodward
Manual 37383D
Example 3: Frequency Interface Set Point The frequency set point value must be written to object 21FD (hex), i.e. parameter ID 509 Example: A frequency value of 50.00 Hz = 5000 (dec) =1388 (hex) is to be transmitted. Modbus address = 40000 + (Par. ID + 1) = 40510 Modbus length = 1 (UNSIGNED 16) Figure 3-11 shows the settings made to parameter address 509 in ModScan32.
Figure 3-11: Modbus - configuration example 4 - frequency
Example 4: Voltage Interface Set Point The voltage set point value must be written to object 21FE (hex), i.e. parameter ID 510 Example: A voltage value of 400 V = 400 (dec) =0190 (hex) is to be transmitted. Modbus address = 40000 + (Par. ID + 1) = 40511 Modbus length = 2 (UNSIGNED 32) The high word is to be written to the lower address and the low word is to be written to the higher address. Figure 3-12 shows the settings made to parameter address 510 in ModScan32.
Figure 3-12: Modbus - configuration example 4 - voltage
Woodward
Page 57/102
Manual 37383D
Configuration of the LogicsManager Functions via Modbus

Besides HMI and ToolKit, it is also possible to configure the LogicsManager functions via modbus. Used LogicsManager Functions The following LogicsManager functions are used for remote access: 12120 Start req. in AUTO: this LogicsManager function is used for remote request start/stop 12490 Ext. acknowledge: this LogicsManager function is used for remote acknowledge 12540 Start w/o load: this LogicsManager functionr is used for start without load 12510 Operat. mode AUTO: this LogicsManager function is used for AUTOMATIC mode Modbus Encoding of a LogicsManager Function The following section describes how to configure a LogicsManager function via Modbus. A LogicsManager function is defined by several parameters, like delays, commands, signs, or operators.
Command 1
Sign 1
Operator 1
Operator 2 Command 2 Sign 2
Command 3
Sign 3
Figure 3-13: LogicsManager - Modbus encoding
The definition for a LogicsManager function consists of 7 data words:

Word 0 Delay ON Word 1 Delay OFF Word 2 Logic equation 1 Word 3 Logic equation 2 Word 4 Command 1 Word 5 Command 2 Word 6 Command 3
NOTE
The configuration of a LogicsManager function via Modbus requires to reverse the byte order of double-byte words, i.e. low byte before high byte.
The delays are configured as hundredths of a second, i.e. 500 must be configured for a delay of 5 seconds.
Page 58/102
Woodward
Manual 37383D
The logic equation (0xFFFF) contains the information of one operator in each nibble. Logic equation 1: Word 2 High byte Low byte Highest nibble Second highest nibble Third highest nibble Lowest nibble Sign 2 Operator 2 Sign 1 Operator 1 Logic equation 2: Word 3 High byte Low byte Highest nibble Second highest nibble Third highest nibble Lowest nibble not used not used Sign 3 not used Definition of the nibbles: Signs: 0x00 0x10 0x20 0x30 negate value of this element with 'NOT' keep value of this element with '' force value of this element to 'TRUE' force value of this element to 'FALSE' 'AND' with following element 'NAND' with following element 'OR' with following element 'NOR' with following element 'XOR' with following element 'NOT-XOR' with following element
Operators: 0x00 0x01 0x02 0x03 0x04 0x05
The commands are defined by configuring the ID of the respective command variable. Refer to the Logical Command Variables section of the LogicsManager appendix of the configuration manual 37224 for the command variable IDs.
Woodward
Page 59/102
Manual 37383D
Remote Control via Modbus

The easYgen-3000 controller may be configured to perform start/stop/acknowledgement functions remotely through the Modbus. The required procedure is detailed in the following steps. Please also refer to the Application Manual 37226.
Remote Control via Modbus

The easYgen controller may be configured to perform start/stop/acknowledgement functions remotely through the Modbus. The required procedure is detailed in the following steps.
NOTE
The following descriptions refer to the remote control parameter 503 as described under Remote Control Word 1 - Object 21F7h (Parameter ID 503) on page 96. It may be necessary to shift the address by 1 depending on the used PC software. In this case, the address would be 504 for example. Be sure to check both possibilities in case of remote control problems.
Par. ID. 503
Parameter Remote control word 1
Setting range 0 to 65535
Data type
UNSIGNED 16
Modbus address = 40000 + (Par. ID +1) = 40504 Modbus length = 1 (UNSIGNED 16) The following Modscan32 screenshot shows the configurations made to remote control parameter ID 503. It is possible to set the format to binary to view single bits using the "display options".
Figure 3-14: Modbus - remote control parameter 503
Page 60/102
Woodward
Manual 37383D
Example 1: Stop Request By double-clicking the address, a Write Register command may be issued. Figure 3-15 shows how bit 0 is set using the ModScan32 Software.
Figure 3-15: Modbus - write register - stop request
Example 2: Start Request By double-clicking the address, a Write Register command may be issued. Figure 3-15 shows how bit 1 is set using the ModScan32 Software.
Figure 3-16: Modbus - write register - start request
Example 3: External Acknowledge By double-clicking the address, a Write Register command may be issued. Figure 3-15 shows how bit 4 is set using the ModScan32 Software.
Figure 3-17: Modbus - write register - external acknowledge
Woodward
Page 61/102
Manual 37383D
Remotely Changing the Set Point

Active Power Set Point It is possible to remotely change the active power set point through the Modbus using the parameter ID 504 (refer to Remote Control Word 2 - Object 21F8h (Parameter ID 504) on page 97). The required procedure is detailed in the following steps.
Par. ID. 504 Parameter Remote control word 2 Setting range YES / NO Data type
UNSIGNED 16
In order to enable the active power set point 2, bit 7 of object 21F8 (hex), i.e. parameter ID 504, must be enabled. Example: The active power set point 2 is to be enabled. Modbus address = 40000 + (Par. ID + 1) = 40505 Modbus length = 1 (UNSIGNED 16) Figure 3-18 shows the settings made to parameter ID 504 in ModScan32. It is possible to set the format to binary to view single bits using the "display options".
By double-clicking the address, a Write Register command may be issued. Figure 3-19 shows how bit 7 is set using the ModScan32 Software.
Figure 3-19: Modbus - write register - enable active power set point 2
Page 62/102
Woodward
Manual 37383D
Power Factor Set Point It is possible to remotely change the power factor set point through the Modbus using the parameter ID 504 (refer to Remote Control Word 2 - Object 21F8h (Parameter ID 504) on page 97). The required procedure is detailed in the following steps.
UNSIGNED 16
In order to enable the power factor set point 2, bit 6 of object 21F8 (hex), i.e. parameter ID 504, must be enabled. Example: The power factor set point 2 is to be enabled. Modbus address = 40000 + (Par. ID + 1) = 40505 Modbus length = 1 (UNSIGNED 16) Figure 3-20 shows the settings made to parameter ID 504 in ModScan32. It is possible to set the format to binary to view single bits using the "display options".
Figure 3-21: Modbus - write register - enable power factor set point 2
Woodward
Page 63/102
Manual 37383D
Frequency Set Point It is possible to remotely change the frequency set point through the Modbus using the parameter ID 504 (refer to Remote Control Word 2 - Object 21F8h (Parameter ID 504) on page 97). The required procedure is detailed in the following steps.
UNSIGNED 16
In order to enable the frequency set point 2, bit 5 of object 21F8 (hex), i.e. parameter ID 504, must be enabled. Example: The frequency set point 2 is to be enabled. Modbus address = 40000 + (Par. ID + 1) = 40505 Modbus length = 1 (UNSIGNED 16) Figure 3-22 shows the settings made to parameter ID 504 in ModScan32. It is possible to set the format to binary to view single bits using the "display options".
Figure 3-23: Modbus - write register - enable frequency set point 2
Page 64/102
Woodward
Manual 37383D
Voltage Set Point It is possible to remotely change the voltage set point through the Modbus using the parameter ID 504 (refer to Remote Control Word 2 - Object 21F8h (Parameter ID 504) on page 97). The required procedure is detailed in the following steps.
UNSIGNED 16
In order to enable the voltage set point 2, bit 4 of object 21F8 (hex), i.e. parameter ID 504, must be enabled. Example: The voltage set point 2 is to be enabled. Modbus address = 40000 + (Par. ID + 1) = 40505 Modbus length = 1 (UNSIGNED 16) Figure 3-22 shows the settings made to parameter ID 504 in ModScan32. It is possible to set the format to binary to view single bits using the "display options".
Figure 3-25: Modbus - write register - enable voltage set point 2
Woodward
Page 65/102
Manual 37383D
Changing Parameter Settings via Modbus

NOTE
Be sure to enter the password for code level 2 or higher for the corresponding interface to get access for changing parameter settings.
Operating Modes
Two operating modes may be used with remote control: 1. 2. STOP AUTOMATIC
It is possible to fix the operating mode using the LogicsManager function 00.16 "Operat. mode AUTO" (parameter ID 12510). Configuration of the LogicsManager Operation Mode AUTO The Operat. mode AUTO LogicsManager function (parameter ID 12510) can be configured in two different ways: 1. Automatic operating mode is always enabled 2. Automatic operating mode is enabled via discrete input Refer to the Performing Remote Start/Stop and Acknowledgement section of the Application Manual 37226 for a detailed configuration of the LogicsManager via HMI or ToolKit. Example: The following Modbus message must be sent to the easYgen to configure the LogicsManager function accordingly.
Word 0 Delay ON 0000 (hex) Word 1 Delay OFF 0000 (hex) Word 2 Logic equation 1 1020 (hex) Word 3 Logic equation 2 2000 (hex) Word 4 Command 1 0F02 (hex) Word 5 Command 2 0000 (hex) Word 6 Command 3 0000 (hex)
The detailed composition of this message is as follows: Delay ON = 0.00 s -> word 0 = 0000 (hex) Delay OFF = 0.00 s -> word 1 = 0000 (hex) Logic eq. 1: sign 1 = ''; Operator 1 = 'AND'; Sign 2 = 'TRUE', Operator 2 = 'AND' -> word 2 = 1020 (hex) Logic equation 2: sign 3 = 'TRUE' -> word 3 = 2000 (hex) Command 1 = 09.09 Discrete Input 9 = 0 (dec) = 0000 (hex) -> word 4 = 0F02 (hex) Command 2 = 00.01 Flag 1 (default) = 0 (dec) = 0000 (hex) -> word 5 = 0000 (hex) Command 3 = 00.01 Flag 1 (default) = 0 (dec) = 0000 (hex) -> word 6 = 0000 (hex) The complete message of 7 words must be copied to address 12511 ff (12510+1) in one step. This is shown in Figure 3-26 using the ModScan32 software.
Page 66/102
Woodward
Manual 37383D
Figure 3-26: Modbus configuration - Operat. mode AUTO
NOTE
If an shutdown alarm of alarm class C through F occurs in AUTOMATIC operating mode, the control does not return to STOP operating mode if the alarm is cleared after acknowledgement. This means that a restart is initiated.
Remote Start/Stop and Acknowledgement

Refer to the Performing Remote Start/Stop and Acknowledgement section in the Special Application Examples section of the application manual 37226 for detailed information. The easYgen may be started, stopped, or acknowledged with CAN/Modbus. Therefore, two logical command variables have to be configured with the LogicsManager: 04.13 04.14 Remote request Remote acknowledge
Configuration of the LogicsManager Function Start Request in AUTO The Start req. in AUTO LogicsManager function (parameter ID 12120) can be configured in a way that a start request in AUTOMATIC operating mode is enabled as soon as a remote request is issued. Refer to the Performing Remote Start/Stop and Acknowledgement section of the Application Manual 37226 for a detailed configuration via HMI or ToolKit. The remote request may be enabled by setting bit 0 (start) of the remote control word 503 to HIGH and may be disabled by setting bit 1 (stop) of the remote control word 503 to HIGH (refer to Remote Control Word 1 - Object 21F7h (Parameter ID 503) on page 96). Example: The following Modbus message must be sent to the easYgen to configure the LogicsManager function accordingly.
Word 0 Delay ON 0000 (hex) Word 1 Delay OFF 0000 (hex) Word 2 Logic equation 1 1232 (hex) Word 3 Logic equation 2 1000 (hex) Word 4 Command 1 0802 (hex) Word 5 Command 2 0700 (hex) Word 6 Command 3 FB00 (hex)
The detailed composition of this message is as follows:
Woodward
Page 67/102
Manual 37383D
Delay ON = 0.00 s -> word 0 = 0000 (hex) Delay OFF = 0.00 s -> word 1 = 0000 (hex) Logic equation 1: sign 1 = ''; Operator 1 = 'OR'; Sign 2 = 'FALSE', Operator 2 = 'OR' -> word 2 = 1232 (hex) Logic equation 2: sign 3 = '' -> word 3 = 1000 (hex) Command 1 = 09.02 Discrete input 2 = 520 (dec) = 0208 (hex) -> word 4 = 0802 (hex) Command 2 = 00.08 Flag 8 = 0 (dec) = 0000 (hex) -> word 5 = 0700 (hex) Command 3 = 04.13 Remote request = 251 (dec) = 00FB (hex) -> word 6 = FB00 (hex) The complete message of 7 words must be copied to address 12121 ff (12120+1) in one step. This is shown in Figure 3-27 using the ModScan32 software.
Figure 3-27: Modbus configuration - Start req in AUTO
Page 68/102
Woodward
Manual 37383D
Configuration of the LogicsManager Function External Acknowledge The Ext. acknowledge LogicsManager function (parameter ID 12490) can be configured in a way that an external acknowledgement is performed as soon as the remote acknowledge signal is enabled. Refer to the Performing Remote Start/Stop and Acknowledgement section of the Application Manual 37226 for a detailed configuration via HMI or ToolKit. External acknowledge may be enabled by setting bit 4 (external acknowledge) of the remote control word 503 to HIGH (refer to Remote Control Word 1 - Object 21F7h (Parameter ID 503) on page 96). Example: The following Modbus message must be sent to the easYgen to configure the LogicsManager function accordingly.
Word 0 Delay ON 0000 (hex) Word 1 Delay OFF 0000 (hex) Word 2 Logic equation 1 1212 (hex) Word 3 Logic equation 2 3000 (hex) Word 4 Command 1 0B02 (hex) Word 5 Command 2 FC00 (hex) Word 6 Command 3 0000 (hex)
The detailed composition of this message is as follows: Delay ON = 0.00 s -> word 0 = 0000 (hex) Delay OFF = 0.00 s -> word 1 = 0000 (hex) Logic equation 1: sign 1 = ''; Operator 1 = 'OR'; Sign 2 = '', Operator 2 = 'OR' -> word 2 = 1212 (hex) Logic equation 2: sign 3 = 'FALSE' -> word 3 = 3000 (hex) Command 1 = 09.05 Discrete input 5 = 523 (dec) = 020B (hex) -> word 4 = 0B02 (hex) Command 2 = 04.14 Remote acknowledge = 252 (dec) = 00FC (hex) -> word 5 = FC00 (hex) Command 3 = 00.01 Flag 1 (default) = 0 (dec) = 0000 (hex) -> word 6 = 0000 (hex) The complete message of 7 words must be copied to address 12491 ff (12490+1) in one step. This is shown in Figure 3-28 using the ModScan32 software.
Figure 3-28: Modbus configuration - External acknowledge
Woodward
Page 69/102
Manual 37383D
Configuration of the LogicsManager Function Start w/o Load The Start w/o load LogicsManager function (parameter ID 12540) can be configured in a way that it is always enabled. Refer to the Performing Remote Start/Stop and Acknowledgement section of the Application Manual 37226 for a detailed configuration via HMI or ToolKit. Example: The following Modbus message must be sent to the easYgen to configure the LogicsManager function accordingly.
Word 0 Delay ON 0000 (hex) Word 1 Delay OFF 0000 (hex) Word 2 Logic equation 1 2020 (hex) Word 3 Logic equation 2 2000 (hex) Word 4 Command 1 0000 (hex) Word 5 Command 2 0000 (hex) Word 6 Command 3 0000 (hex)
The detailed composition of this message is as follows: Delay ON = 0.00 s -> word 0 = 0000 (hex) Delay OFF = 0.00 s -> word 1 = 0000 (hex) Logic eq. 1: sign 1 = 'TRUE'; Operator 1 = 'AND'; Sign 2 = 'TRUE', Operator 2 = 'AND' -> word 2 = 2020 (hex) Logic equation 2: sign 3 = 'TRUE' -> word 3 = 2000 (hex) Command 1 = 00.01 Flag 1 (default) = 0 (dec) = 0000 (hex) -> word 4 = 0000 (hex) Command 2 = 00.01 Flag 1 (default) = 0 (dec) = 0000 (hex) -> word 5 = 0000 (hex) Command 3 = 00.01 Flag 1 (default) = 0 (dec) = 0000 (hex) -> word 6 = 0000 (hex) The complete message of 7 words must be copied to address 12541 ff (12540+1) in one step. This is shown in Figure 3-29 using the ModScan32 software.
Figure 3-29: Modbus configuration - Start w/o load
Page 70/102
Woodward
Manual 37383D
Remote Acknowledging Single Alarm Messages

It is possible to remotely acknowledge single alarm messages through the Modbus by sending the respective parameter ID of the alarm to be acknowledged on ID 522. The required procedure is detailed in the following steps.
Par. ID. 522 Parameter Reset alarm list Setting range 0 to 65535 Data type
UNSIGNED 16
The parameter ID of the alarm to be acknowledged must be written to object 220A (hex), i.e. parameter ID 522. Example: A "Mains undervoltage 1" alarm (parameter ID 3012) is to be acknowledged (refer to Data Protocol 5003 starting on page 79 or the alarm list in the Operation Manual 37225). Modbus address = 40000 + (Par. ID + 1) = 40523 Modbus length = 1 (UNSIGNED 16) Figure 3-30 shows the settings made to parameter ID 522 in ModScan32. It is possible to set the format to decimal to view the value using the "display options".
By double-clicking the address, a Write Register command may be issued. Figure 3-31 shows how the parameter ID of the alarm to be acknowledged is written using the ModScan32 Software.
Figure 3-31: Modbus - write register - acknowledge alarm message
Woodward
Page 71/102
Manual 37383D
Remotely Clearing The Event History

It is possible to remotely clear the event history through the Modbus. The required procedure is detailed in the following steps.
Par. ID. 1706 Parameter Clear eventlog Setting range YES / NO Data type
UNSIGNED 16
In order to clear the event history, bit 0 of object 26AA (hex), i.e. parameter ID 1706, must be enabled. Example: The event history is to be cleared. Modbus address = 40000 + (Par. ID + 1) = 41707 Modbus length = 1 (UNSIGNED 16) Figure 3-32 shows the settings made to parameter ID 1706 in ModScan32. It is possible to set the format to binary to view single bits using the "display options".
By double-clicking the address, a Write Register command may be issued. Figure 3-33 shows how bit 0 is enabled using the ModScan32 Software.
Figure 3-33: Modbus - write register - clear event history
Page 72/102
Woodward
Manual 37383D
Remotely Resetting the Default Values

Modbus via RS-232 (Serial Interface 1) It is possible to remotely reset the unit to its default values through the Modbus (via RS-232) using the parameter IDs 1704 and 1701. The required procedure is detailed in the following steps.
Par. ID. 1704 1701 Parameter Factory settings via RS-232 Reset factory default values Setting range YES / NO YES / NO Data type
UNSIGNED 16 UNSIGNED 16
In order to enable the resetting procedure, parameter ID 1704 must be enabled. Example: The resetting procedure via RS-232 is to be enabled. Modbus address = 40000 + (Par. ID + 1) = 41705 Modbus length = 1 (UNSIGNED 16) Figure 3-34 shows the settings made to parameter ID 1704 in ModScan32. It is possible to set the format to decimal to view the value using the "display options".
By double-clicking the address, a Write Register command may be issued. Figure 3-35 shows how the parameter is enabled using the ModScan32 Software. The value must be set to "1" to enable the parameter.
Figure 3-35: Modbus - write register - enable the resetting procedure via RS-232
Woodward
Page 73/102
Manual 37383D
In order to reset the default values, parameter ID 1701 must be enabled. Example: The default values are to be reset. Modbus address = 40000 + (Par. ID + 1) = 41702 Modbus length = 1 (UNSIGNED 16) Figure 3-36 shows the settings made to parameter ID 1701 in ModScan32. It is possible to set the format to decimal to view the value using the "display options".
By double-clicking the address, a Write Register command may be issued. Figure 3-37 shows how the parameter is enabled using the ModScan32 Software. The value must be set to "1" to enable the parameter.
Figure 3-37: Modbus - write register - resetting the default values
Modbus via RS-485 (Serial Interface 2) It is possible to remotely reset the unit to its default values through the Modbus (via RS-485) using the parameter IDs 1743 and 1701. The required procedure is the same as described under Modbus via RS-232 (Serial Interface 1) on page 73; however the parameter ID 1743 is used instead of parameter ID 1704.
Par. ID. 1743 1701 Parameter Factory settings via RS-485 Reset factory default values Setting range YES / NO YES / NO Data type
UNSIGNED 16 UNSIGNED 16
Page 74/102
Woodward
Manual 37383D
Exception Responses
The easYgen Modbus interface has multiple exception responses to show that a request could not be executed. Exception responses can be recognized if the response telegram contains the request function code with an offset of 128 (0x80 hex). Table 3-5 explains possible reasons for an exception response that occurred.
easYgen Modbus Exception Responses
Code 01 02 03
Name ILLEGAL FUNCTION ILLEGAL ADDRESS ILLEGAL DATA VALUE
Reason The sent request function code is not supported by the easYgen Modbus interface. Permission to read/write the parameter is denied. The amount of requested registers is wrong to read/write this registers. The data value exceeds the min. and max. limitations of the parameter upon a write request. There is no parameter on the requested address.
Table 3-5: Modbus - exception responses
Woodward
Page 75/102
Manual 37383D
Modbus Parameters
The following parameters are available for configuring the Modbus modules on the Serial Interfaces. Serial Interface 1:
Modbus slave ID Modbus Slave ID
{1oc}
Serial interface 1 Modbus slave ID
0 to 255
DE
EN
CL2
3185
{0}
{1o}
{2oc}
Modbus Slave ID for serial interface 1. [0] means : Modbus is disabled [1 to 255] : These are Slave IDs (default = 1)
Reply delay time Zeitverzgerung der Antwort CL2 {0} {1o} {1oc} {2oc} 3186
Serial interface 1 Modbus reply delay time
0 to 100 (1/10ms)
DE
EN
Serial interface 1 Modbus reply delay time. Adjustable in 10 ms steps. Default = 0 ms
Serial Interface 2:
Modbus slave ID Modbus Slave ID
{1oc}
Serial interface 2 Modbus slave ID
0 to 255
DE
EN
CL2
3188
{0}
{1o}
{2oc}
Modbus Slave ID for serial interface 2. [0] means : Modbus is disabled [1 to 255] : These are Slave IDs (default = 1)
Reply delay time Zeitverzgerung der Antwort CL2 {0} {1o} {1oc} {2oc} 3189
Serial interface 2 Modbus reply delay time
0 to 100 (1/10ms)
DE
EN
Serial interface 2 Modbus reply delay time. Adjustable in 10 ms steps. Default = 0 ms
NOTE
Above parameters are an excerpt of the Configuration Manual 37224. Refer to this manual for all parameters.
Page 76/102
Woodward
Manual 37383D
Appendix A. Supported J1939 ECUs & Remote Control Messages

The following table lists all ECUs, which are supported by the easYgen beyond the J1939 standard with the appropriate settings. We recommend the standard setting for all ECUs, which are not listed here. All other parameters shall be clarified with the ECU manufacturer.
Setting ECU Woodward EGS MTU ADEC Device type (ID 15102) EGS ADEC MTU J1939 Device address (ID 15106) 234 1 Engine control address (ID 15107) 0 128 SPN Version (ID 15103) n/a n/a Comment The easYgen is connected with the SAM via CAN. The SAM communicates with the ADEC using an own bus. The rated speed of the EMS1 and EDC3 cannot be switched via the easYgen. The easYgen is connected with the MFR via CAN. The MFR communicates with the EDC7 using an own bus.
Deutz EMR2 Volvo EDC4 Volvo EMS2 Volvo EMS1 Volvo EDC3 Scania S6 MAN MFR/EDC7
EMR2 Deutz EMS2 Volvo
3 17
0 0
Version 1 n/a
S6 Scania MAN
39 253
0 0
n/a n/a
SISU EEM2 SISU EEM3 Standard ECUs
SISU Standard
n/a 234
0 or 1 0
n/a n/a
The following data is only transmitted to the corresponding ECU, if parameter "ECU remote controlled" is configured to "On", and parameter "Device type" is configured to one of the available ECU modes (if "Off" is configured, no J1939 remote control messages will be sent as well).
NOTE
Please note that some ECU manufacturers require that this functionality must be enabled first. In some cases, this is only possible by the manufacturer. Please consider this when ordering the ECU.
Woodward
Page 77/102
Manual 37383D Remote Woodcontrol ward parameter EGS Engine Start No Scania S6 Yes Deutz EMR2 Volvo EDC4 No Volvo Volvo EMS2 EMS1/ EDC3 Yes Yes MTU ADEC Yes
easYgen-3000 Series (Package P1) - Genset Control MAN SISU EEM2/ EEM3 Only EEM3 Std. Comment
Yes
No
Engine Stop
Yes
Yes
No
Yes
Yes
Yes
Yes
Only EEM3
Yes
Droop mode
Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
If an engine start command is initiated by the easYgen, this information is transmitted in the form of a J1939 message bit to an ECU. If ignition speed is reached, this bit will be reset (LogicsManager command variable 03.02. "Starter"). This J1939 bit information is set, if a "Stop" command in automatic or manual mode is present in the easYgen. The "Stop" bit information remains set, until ignition speed is fallen below. After ignition speed has been fallen below, the "Stop" bit will be reset (LogicsManager command variable 03.27. "Stopping solenoid"). This J1939 bit information is set, if a "Start" command in automatic or manual mode is initiated by the easYgen. The bit remains set until the engine has been stopped.
Important: This message is only sent, if the LogicsManager output 00.25 "Frequency droop active" is TRUE. Yes No Yes Yes No No No No This J1939 bit information is set, Idle Mode No if "Idle" mode is active (LogicsManager command variable 04.15. "Idle run active" is TRUE). The bit will be reset, if "Idle" mode is no longer active (LogicsManager command variable 04.15. "Idle run active" is FALSE). Yes Yes No Yes*2 No Yes No*1 No No The J1939 information for 50 or 50/60 Hz 60 Hz mode is sent to the ECU switch depending on the "Rated system frequency" parameter setting (ID 1750) within the easYgen . Yes Yes Yes Yes Yes Yes Yes Yes Yes Refer to parameter 5537 in the Speed offset absolute offset absolute absolute absolute Configuration Manual 37415 for bias detailed information. No No No Yes Yes No No No No This J1939 bit information is set, Preglow if the easYgen is in "Preglow" mode (LogicsManager command variable 03.04. "Preglow/Ignition" is TRUE). The bit will be reset, if the "Preglow" phase has been expired or aborted. No Yes No No No Yes No No Yes This J1939 bit information is set, Override if the easYgen is in critical mode (LogicsManager command variable 04.27. "Critical mode" is TRUE). The bit will be reset, if the critical mode has been expired or aborted. *1 Please contact manufacturer to clarify whether both frequencies (50/60 Hz) may be controlled by the speed bias. *2 In case the rated speed of the easYgen and the ECU dont match, please make sure that the CAN connections works and change parameter 1750 of the easYgen once. Page 78/102 Woodward
Manual 37383D
Appendix B. Data Protocols

Data Protocol 5003
Modbus Modbus Modicon Start start addr. addr. (*1) 450001 450002 450003 CAN Data byte 1,2 3,4 5,6 Data byte 0 (Mux) 450000 0 450001 0 450002 0 Parameter Description ID Multiplier Units
10100 -
450004 450005 450007 450008 450010 450011 450013 450014 450016 450017 450019 450020 450021 450022 450023 450025 450026 450028 450029 450031 450032 450034 450035 450037 450038 450040 450041 450043 450044 450046 450047 450048 450049 450050 450051 450052 450053 450055 450056 450058 450059 450061 450062 450064
450003 450004 450006 450007 450009 450010 450012 450013 450015 450016 450018 450019 450020 450021 450022 450024 450025 450027 450028 450030 450031 450033 450034 450036 450037 450039 450040 450042 450043 450045 450046 450047 450048 450049 450050 450051 450052 450054 450055 450057 450058 450060 450061 450063
1 1 2 2 3 3 4 4 5 5 6 6 6 7 7 8 8 9 9 10 10 11 11 12 12 13 13 14 14 15 15 15 16 16 16 17 17 18 18 19 19 20 20 21
1,2 3,4,5,6 1,2 3,4,5,6 1,2 3,4,5,6 1,2 3,4,5,6 1,2 3,4,5,6 1,2 3,4 5,6 1,2 3,4,5,6 1,2 3,4,5,6 1,2 3,4,5,6 1,2 3,4,5,6 1,2 3,4,5,6 1,2 3,4,5,6 1,2 3,4,5,6 1,2 3,4,5,6 1,2 3,4 5,6 1,2 3,4 5,6 1,2 3,4,5,6 1,2 3,4,5,6 1,2 3,4,5,6 1,2 3,4,5,6 1,2
160 170 144 171 147 173 208 174 209 216
10110 207 10111 185 10112 161 10115 159 111 112 113 134
135 140 136 10159 150 2112 2113
Protocol ID, always 5003 Pickup speed Control mode (STOP/AUTO/MANUAL) 1=AUTO 2=STOP 4=MANUAL Gen. powerfactor Av. Gen. Wye-Voltage Gen. frequency Av. Gen. Delta-Voltage Mains frequency Av. Mains Wye-Voltage Mains power factor Av. Mains Delta-Voltage Busbar 1: Frequency Av. Busbar1 Delta-Voltage internal internal internal Battery voltage Av. Mains Current Analog input 1 Av. Gen. Current Analog input 2 Meas. ground current Analog input 3 Calculated ground current internal Gen. current 1 internal Gen. current 2 internal Gen. current 3 internal Mains current L1 internal internal internal internal internal internal internal Total gen. power internal Total mains power internal Total gen. reactive power AI Auxiliary excitation D+ Total mains reactive power Overspeed 1 latched Overspeed 2 latched
-1 rpm Mask:000Fh (enum.)
0.001 0.1 0.01 0.1 0.01 0.1 0.001 0.1 0.01 0.1
V Hz V Hz V V Hz V
0.1 0.001 changeable 0.001 changeable 0.001 changeable 0.001 0.001 0.001 0.001 0.001
V A A A A A A A A
1 1 1 0.1 1 Mask: 8000h Mask: 4000h
W W var V var Bit Bit
Woodward
Page 79/102
Manual 37383D Modbus Modbus Modicon Start start addr. addr. (*1) CAN Data byte 0 (Mux) Data byte Parameter Description ID
easYgen-3000 Series (Package P1) - Genset Control Multiplier Units
2162 2163 2652 2457 2504 2603 2604 2623 2624 10017 3325 2560 2561 3,4,5,6 1,2 182 3064 3074 3084 4056 2944 10084 10083 10082 10086 10085 4073 4064 1714 15125 15126
450065 450067
450064 450066
21 22
450068 450069 450070 450071 450072 450073
450067 450068 450069 450070 450071 450072
22 22 23 23 23 24
3,4 5,6 1,2 3,4 5,6 1,2
1912 1913 1962 1963 2012 2013 2062 2063 2218 2219 2220 2262 2263 2314 2315 108 2412 2413 3907 3263 3264 3955 2924 3124 4038 2664
450074 450076
450073 450075
24 25
3,4,5,6 1,2
Underspeed 1 latched Mask: 2000h Underspeed 2 latched Mask: 1000h Unintended stop latched Mask: 0800h Speed det. alarm latched Mask: 0400h Shutdwn malfunct. latched Mask: 0200h GCB fail to close latched Mask: 0100h GCB fail to open latched Mask: 0080h MCB fail to close latched Mask: 0040h MCB fail to open latched Mask: 0020h CAN-Fault J1939 latched Mask: 0010h Start fail latched Mask: 0008h Mainten. days exceeded latched Mask: 0004h Mainten. hours exceeded latched Mask: 0002h internal Mask: 0001h Busbar 1: voltage L1-L2 0.1 GCB syn. timeout latched Mask: 8000h MCB syn. timeout latched Mask: 4000h GGB Timeout latched Mask: 2000h Charge alt. low voltage (D+) latched Mask: 1000h Ph.rotation mismatch latched Mask: 0800h no data receive at RPDO3 at CAN In- Mask: 0400h terface 1 no data receive at RPDO2 at CAN In- Mask: 0200h terface 1 no data receive at RPDO1 at CAN In- Mask: 0100h terface 1 no data receive at RPDO2 (function Mask: 0080h 1) at CAN Interface 2 no data receive at RPDO1 (function Mask: 0040h 1) at CAN Interface 2 Parameter Alignment Mask: 0010h Missing members on CAN Mask: 0008h EEPROM failure latched Mask: 0004h Red stop lamp latched Mask: 0002h Amber warning lamp latched Mask: 0001h internal internal internal internal internal Gen.overfreq. 1 latched Mask: 8000h Gen.overfreq. 2 latched Mask: 4000h Gen.underfreq. 1 latched Mask: 2000h Gen.underfreq. 2 latched Mask: 1000h Gen.overvolt. 1 latched Mask: 0800h Gen.overvolt. 2 latched Mask: 0400h Gen.undervolt. 1 latched Mask: 0200h Gen.undervolt. 2 latched Mask: 0100h Gen. overcurr. 1 latched Mask: 0080h Gen. overcurr. 2 latched Mask: 0040h Gen. overcurr. 3 latched Mask: 0020h Gen. Rv/Rd pow.1 latched Mask: 0010h Gen. Rv/Rd pow.2 latched Mask: 0008h Gen. Overload IOP 1 latched Mask: 0004h Gen. Overload IOP 2 latched Mask: 0002h internal Mask: 0001h Gen. voltage L1-L2 0.1 Unbal. load 1 latched Mask: 8000h Unbal. load 2 latched Mask: 4000h Gen. Asymmetry latched Mask: 2000h Ground fault 1 latched Mask: 1000h Ground fault 2 latched Mask: 0800h Gen. phase rot. misw. Latched Mask: 0400h Gen act.pwr mismatch Latched Mask: 0200h Gen. unloading fault Latched Mask: 0100h Inv.time ov.curr. Latched Mask: 0080h Operating range failed, latched Mask: 0040h
Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit V Bit Bit Bit Bit Bit
Bit Bit Bit
Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit V Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit
Page 80/102
Woodward
450077 450079
450076 450078
25 26
3,4,5,6 1,2
2362 2363 2337 2338 2387 2388 114 2862 2863 2912 2913 2962 2963 3012 3013 3057 3114
3975 450080 450082 450079 450081 26 27 3,4,5,6 1,2 109 3217 3218 3241 3242 2985 2986 3035 3036 2934
450083 450085
450082 450084
27 28
3,4,5,6 1,2
450086 450088 450089 450091
450085 450087 450088 450090
28 29 29 30
3,4,5,6 1,2 3,4,5,6 1,2
115 10600 10601 10602 10603 10604 10605 10607 10608 10609 10610 10611 10612 110 116 16376 16375 16374 16373 16372 16371 16370 16369 16368 16367
Gen. Overload MOP 1 latched Gen. Overload MOP 2 latched Gen. overexcited 1 latched Gen. overexcited 2 latched Gen. underexcited 1 latched Gen. underexcited 2 latched Gen. voltage L1-N Mains ov.freq. 1 latched Mains ov.freq. 2 latched Mains un.freq. 1 latched Mains un.freq. 2 latched Mains ov.volt. 1 latched Mains ov.volt. 2 latched Mains un.volt. 1 latched Mains un.volt. 2 latched Mains phaseshift latched Mains decoupling latched internal internal internal Mains phase rot. misw. Latched internal internal Gen. voltage L2-L3 Mains import power 1 latched Mains import power 2 latched Mains export power 1 latched Mains export power 2 latched Mains overexcited 1 latched Mains overexcited 2 latched Mains underexcited 1 latched Mains underexcited 2 latched internal Mns act.pwr mismatch latched internal internal internal internal internal internal Gen. voltage L2-N State Digital Input 1 lached State Digital Input 2 lached State Digital Input 3 lached State Digital Input 4 lached State Digital Input 5 lached State Digital Input 6 lached State Digital Input 7 lached State Digital Input 8 lached State Digital Input 9 lached State Digital Input 10 lached State Digital Input 11 lached State Digital Input 12 lached Gen. voltage L3-L1 internal Gen. voltage L3-N State ext. Digital Input 16 latched State ext. Digital Input 15 latched State ext. Digital Input 14 latched State ext. Digital Input 13 latched State ext. Digital Input 12 latched State ext. Digital Input 11 latched State ext. Digital Input 10 latched State ext. Digital Input 9 latched State ext. Digital Input 8 latched State ext. Digital Input 7 latched
Mask: 0020h Mask: 0010h Mask: 0008h Mask: 0004h Mask: 0002h Mask: 0001h 0.1 Mask: 8000h Mask: 4000h Mask: 2000h Mask: 1000h Mask: 0800h Mask: 0400h Mask: 0200h Mask: 0100h Mask: 0080h Mask: 0040h Mask: 0020h Mask: 0010h Mask: 0008h Mask: 0004h Mask: 0002h Mask: 0001h 0.1 Mask: 8000h Mask: 4000h Mask: 2000h Mask: 1000h Mask: 0800h Mask: 0400h Mask: 0200h Mask: 0100h Mask: 0080h Mask: 0040h Mask: 0020h Mask: 0010h Mask: 0008h Mask: 0004h Mask: 0002h Mask: 0001h 0.1 Mask: 8000h Mask: 4000h Mask: 2000h Mask: 1000h Mask: 0800h Mask: 0400h Mask: 0200h Mask: 0100h Mask: 0080h Mask: 0040h Mask: 0020h Mask: 0010h 0.1 0.1 Mask: 8000h Mask: 4000h Mask: 2000h Mask: 1000h Mask: 0800h Mask: 0400h Mask: 0200h Mask: 0100h Mask: 0080h Mask: 0040h
Bit Bit Bit Bit Bit Bit V Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit V Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit V Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit V V Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit
Woodward
Page 81/102
450092 450094
450091 450093
30 31
3,4,5,6 1,2
450095 450097
450094 450096
31 32
3,4,5,6 1,2
450098 450100
450097 450099
32 33
3,4,5,6 1,2
450101 450103
450100 450102
33 34
3,4,5,6 1,2
450104 450106
450103 450105
34 35
3,4,5,6 1,2
16366 16365 16364 16362 16361 16360 118 10033 10032 10031 10030 10029 10028 10027 10026 10025 10024 10023 10022 10021 10020 10019 10018 121 10049 10048 10047 10046 10045 10044 10043 10042 10041 10040 10039 10038 10037 10036 10035 10034 119 10057 10056 10055 10054 10053 10052 10051 10050 122 1008 1007 1006 1005 120 10131
450107 450109
450106 450108
35 36
3,4,5,6 1,2
123 10014 10015
State ext. Digital Input 6 latched State ext. Digital Input 5 latched State ext. Digital Input 4 latched State ext. Digital Input 3 latched State ext. Digital Input 2 latched State ext. Digital Input 1 latched Mains voltage L1-L2 Alarm flexible limit 16 latched Alarm flexible limit 15 latched Alarm flexible limit 14 latched Alarm flexible limit 13 latched Alarm flexible limit 12 latched Alarm flexible limit 11 latched Alarm flexible limit 10 latched Alarm flexible limit 9 latched Alarm flexible limit 8 latched Alarm flexible limit 7 latched Alarm flexible limit 6 latched Alarm flexible limit 5 latched Alarm flexible limit 4 latched Alarm flexible limit 3 latched Alarm flexible limit 2 latched Alarm flexible limit 1 latched Mains voltage L1-N Alarm flexible limit 32 latched Alarm flexible limit 31 latched Alarm flexible limit 30 latched Alarm flexible limit 29 latched Alarm flexible limit 28 latched Alarm flexible limit 27 latched Alarm flexible limit 26 latched Alarm flexible limit 25 latched Alarm flexible limit 24 latched Alarm flexible limit 23 latched Alarm flexible limit 22 latched Alarm flexible limit 21 latched Alarm flexible limit 20 latched Alarm flexible limit 19 latched Alarm flexible limit 18 latched Alarm flexible limit 17 latched Mains voltage L2-L3 Alarm flexible limit 40 latched Alarm flexible limit 39 latched Alarm flexible limit 38 latched Alarm flexible limit 37 latched Alarm flexible limit 36 latched Alarm flexible limit 35 latched Alarm flexible limit 34 latched Alarm flexible limit 33 latched Mains voltage L2-N Batt.overvolt.2 latched Batt.undervolt.2 latched Batt.overvolt.1 latched Batt.undervolt.1 latched Mains voltage L3-L1 (unused) Alarm class F latched Alarm class E latched Alarm class D latched Alarm class C latched Alarm class B latched Alarm class A latched Mains voltage L3-N Analog inp. 1, wire brake or shortcut latched Analog inp. 2, wire brake or shortcut latched
Mask: 0020h Mask: 0010h Mask: 0008h Mask: 0004h Mask: 0002h Mask: 0001h 0.1 Mask: 8000h Mask: 4000h Mask: 2000h Mask: 1000h Mask: 0800h Mask: 0400h Mask: 0200h Mask: 0100h Mask: 0080h Mask: 0040h Mask: 0020h Mask: 0010h Mask: 0008h Mask: 0004h Mask: 0002h Mask: 0001h 0.1 Mask: 8000h Mask: 4000h Mask: 2000h Mask: 1000h Mask: 0800h Mask: 0400h Mask: 0200h Mask: 0100h Mask: 0080h Mask: 0040h Mask: 0020h Mask: 0010h Mask: 0008h Mask: 0004h Mask: 0002h Mask: 0001h 0.1 Mask: 0080h Mask: 0040h Mask: 0020h Mask: 0010h Mask: 0008h Mask: 0004h Mask: 0002h Mask: 0001h 0.1 Mask: 0008h Mask: 0004h Mask: 0002h Mask: 0001h 0.1 Mask: 0040h Mask: 0020h Mask: 0010h Mask: 0008h Mask: 0004h Mask: 0002h Mask: 0001h 0.1 Mask: 0002h Mask: 0004h
Bit Bit Bit Bit Bit Bit V Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit V Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit V Bit Bit Bit Bit Bit Bit Bit Bit V Bit Bit Bit Bit V Bit Bit Bit Bit Bit Bit Bit V Bit Bit
Page 82/102
Woodward
Manual 37383D Modbus Modbus Modicon Start start addr. addr. (*1) CAN Data byte 0 (Mux) 36 36 37 Data byte Parameter Description ID
10060 3,4 5,6 1,2
450110 450111 450112
450109 450110 450111
10107
450113 450114
450112 450113
37 37
3,4 5,6
8005
Analog inp. 3, wire brake or shortcut latched internal internal Digital outputs 1 to 12 Relay-Output 1 (inverted) Relay-Output 2 Relay-Output 3 Relay-Output 4 Relay-Output 5 Relay-Output 6 Relay-Output 7 Relay-Output 8 Relay-Output 9 Relay-Output 10 Relay-Output 11 Relay-Output 12 internal internal internal internal internal Output to external CAN-I/O Relay 16 Relay 15 Relay 14 Relay 13 Relay 12 Relay 11 Relay 10 Relay 9 Relay 8 Relay 7 Relay 6 Relay 5 Relay 4 Relay 3 Relay 2 Relay 1
Mask: 0008h
Bit
Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask:
8000h 4000h 2000h 1000h 0800h 0400h 0200h 0100h 0080h 0040h 0020h 0010h 0008h 0004h 0002h 0001h
Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit % %
450115 450116 450117 450118 450119 450120 450121
450114 450115 450116 450117 450118 450119 450120
38 38 38 39 39 39 40
1,2 3,4 5,6 1,2 3,4 5,6 1,2
10310 10311
10202
Analog output 1 Analog output 2 internal internal internal internal Operation modes 13200 = Auxiliary services postrun 13216 = Idle run active 13201 = Aux. services prerun 13250 = Gen. stable time 13202 = Critical mode 13251 = In operation 13203 = Motor Stop 13252 = Power limited prerun
Mask DO 16 8000h Mask DO 15 4000h Mask DO 14 2000h Mask DO 13 1000h Mask DO 12 0800h Mask DO 11 0400h Mask DO 10 0200h Mask DO 09 0100h Mask DO 08 0080h Mask DO 07 0040h Mask DO 06 0020h Mask DO 05 0010h Mask DO 04 0008h Mask DO 03 0004h Mask DO 02 0002h Mask DO 01 0001h 0,01 0,01
(enum.)
Woodward
Page 83/102
450122 450124 450125 450127 450128 450130 450131 450133 450135 450136
450121 450123 450124 450126 450127 450129 450130 450132 450134 450135
40 41 41 42 42 43 43 44 44 45
3,4,5,6 1,2 3,4,5,6 1,2 3,4,5,6 1,2 3,4,5,6 1,2,3,4 5,6 1,2
2520 2540 2522 2558 2568 5541 5542 5640 5641 4153
450137
450136
45
3,4
4154
450138
450137
45
5,6
4155
13204 = Cool down 13253 = AUTO mode ready 13205 = Mains settling 13254 = Ramp to rated 13206 = Start 13255 = GCB open 13207 = Start Pause 13256 = Unloading generator 13208 = Preglow 13257 = MCB open 13209 = GCB dead bus close 13258 = Loading generator 13210 = MCB dead bus close 13259 = Synchronization GCB 13211 = Emergency run 13260 = Synchronization MCB 13212 = Turning 13261 = GCB -> MCB Delay 13213 = Ignition 13262 = MCB -> GCB Delay 13214 = Crank protect 13263 = Start w/o Load 13215 = Emergency/Critical 13264 = Unloading mains Gen. real energy 0,01 MWh Engine, number of startrequests 1 Gen. positive reactive power 0,01 Mvarh Hours until next maintenance 1 h Gen. hours of operation 0,01 h Setpoint frequency 0,01 Hz Setpoint active power 0,1 kW Setpoint voltage 1 V Setpoint power factor 0,001 Idle mode monitoring (suppresses un- Mask: 8000h dervolt, underfreq,...) Idle mode activ Mask: 4000h Start without closing GCB Mask: 2000h Block closing GCB Mask: 1000h internal Mask: 0800h internal Mask: 0400h Cooldown is active Mask: 0200h Auxiliary services generally active Mask: 0100h Engine delay timer has expired Mask: 0080h Breaker delay timer has expired Mask: 0040h Engine shall run Mask: 0020h Critical mode is active in auto mode Mask: 0010h Engine is released Mask: 0008h Auxiliary services prerun is active Mask: 0004h Auxiliary services postrun is active Mask: 0002h Lamp test is active Mask: 0001h Crank (Starter) is active Mask: 8000h Operating Magnet / Gasrelay is ac- Mask: 4000h tive Preglow / Ignition is active Mask: 2000h Mains settling timer is running Mask: 1000h Emergency mode is currently active Mask: 0800h Emergency breaked by override Mask: 0400h Emergency Mains overfrequency Mask: 0200h Emergency Mains underfrequency Mask: 0100h Emergency Mains overvoltage Mask: 0080h Emergency Mains undervoltage Mask: 0040h Stopping Magnet is active Mask: 0020h internal Mask: 0010h The genset runs mains parallel Mask: 0008h internal Mask: 0004h internal Mask: 0002h Increment Start Counter Mask: 0001h Dead Band Contr. Freq./Power raise Mask: 8000h Dead Band Contr. Freq./Power raise Mask: 4000h Woodward
Page 84/102
450139
450138
46
1,2
4156
450140 450141 450142 450143 450144 450145 450146 450147 450148 450149 450150 450151 450152 450153 450154 450155 450156 450157 450158 450159 450160 450161 450162 450163 450164 450165 450166 450167 450168 450169 450170 450171 450172 450173
450139 450140 450141 450142 450143 450144 450145 450146 450147 450148 450149 450150 450151 450152 450153 450154 450155 450156 450157 450158 450159 450160 450161 450162 450163 450164 450165 450166 450167 450168 450169 450170 450171 450172
46 46 47 47 47 48 48 48 49 49 49 50 50 50 51 51 51 52 52 52 53 53 53 54 54 54 55 55 55 56 56 56 57 57
3,4 5,6 1,2 3,4 5,6 1,2 3,4 5,6 1,2 3,4 5,6 1,2 3,4 5,6 1,2 3,4 5,6 1,2 3,4 5,6 1,2 3,4 5,6 1,2 3,4 5,6 1,2 3,4 5,6 1,2 3,4 5,6 1,2 3,4
Dead Band Controller Volt./ReactPow raise Dead Band Controller Volt./ReactPow lower GCB is closed MCB is closed internal Synchronization GCB is active Opening GCB is active Closing GCB is active Synchronization MCB is active Opening MCB is active Closing MCB is active Unloading generator is active Unloading mains is active Power limited prerun internal internal internal internal internal Dead busbar closure request for GCB or MCB or GGB Active power load share is active Reactive power load share is active Generator is requested internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal internal
Mask: 2000h Mask: 1000h Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: 0800h 0400h 0200h 0100h 0080h 0040h 0020h 0010h 0008h 0004h 0002h 0001h 8000h 4000h 2000h 1000h 0800h 0400h 0200h 0100h 0080h 0040h 0020h 0010h 0008h 0004h 0002h 0001h
Woodward
Page 85/102
Manual 37383D Modbus Modbus Modicon Start start addr. addr. (*1) 450174 450175 450176 450177 450178 450173 450174 450175 450176 450177 CAN Data byte 0 (Mux) 57 58 58 58 59 Data byte 5,6 1,2 3,4 5,6 1,2 Parameter Description ID
15109 15304
450179 450180 450181
450178 450179 450180
59 59 60
3,4 5,6 1,2
15305
450182 450183 450184 450186
450181 450182 450183 450185
60 60 61 61
3,4 5,6 1,2,3,4 5,6 15400 15401 15402 15403 15404 15405 15406 15407 15408 15409 15410 15411 15412 15413 15414 15415 15416 15418 15419 15420
450187 450189
450186 450188
62 62
1,2,3,4 5,6
450190 450192
450189 450191
63 63
1,2,3,4 5,6
450193 450195
450192 450194
64 64
1,2,3,4 5,6
450196 450198
450195 450197
65 65
1,2,3,4 5,6
450199 450201
450198 450200
66 66
1,2,3,4 5,6
450202 450204
450201 450203
67 67
1,2,3,4 5,6
internal J1939 MTU ADEC ECU Failure Codes internal internal Engine Stop Information (extracted from DEUTZ-specific J1939-Message; refer to the Deutz documentation for information) internal internal J1939 DLN2-Message Scania S6 Engine Coolant Temperature J1939-Message not available Sensor fault High Temperature. NOT High Temperature Engine Oil Pressure J1939-Message not available Sensor fault Low Pressure NOT Low Pressure High Engine Oil Level J1939-Message not available Sensor fault High Level NOT High Level Low Engine Oil Level J1939-Message not available Sensor fault Low Level NOT Low Level internal internal 1. Active Diagnostic Trouble Code (DM1) SPN FMT OC 2. Active Diagnostic Trouble Code (DM1) SPN FMT OC 3. Active Diagnostic Trouble Code (DM1) SPN FMT OC 4. Active Diagnostic Trouble Code (DM1) SPN FMT OC 5. Active Diagnostic Trouble Code (DM1) SPN FMT OC 6. Active Diagnostic Trouble Code (DM1) SPN FMT OC 7. Active Diagnostic Trouble Code (DM1) SPN FMT
1 1 (enum.)
Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask
8000h 4000h 2000h 1000h 0800h 0400h 0200h 0100h 0080h 0040h 0020h 0010h 0008h 0004h 0002h 0001h
Mask FF00h Mask 00FFh
Mask FF00h Woodward
Page 86/102
15421 1,2,3,4 5,6 15422 15423 15424 15425 15426 15427 15428 15429 15430 15450 15451 15452 15453 15454 15455 15456 15457 15458 15459 15460 15461 15462 15463 15464 15465 15466 15467 15468 15469 15470 15471 15472 15473 15474 15475 15476 15477 15478 15479 15395
450205 450207
450204 450206
68 68
450208 450210
450207 450209
69 69
1,2,3,4 5,6
450211 450213
450210 450212
70 70
1,2,3,4 5,6
450214 450216
450213 450215
71 71
1,2,3,4 5,6
450217 450219
450216 450218
72 72
1,2,3,4 5,6
450220 450222
450219 450221
73 73
1,2,3,4 5,6
450223 450225
450222 450224
74 74
1,2,3,4 5,6
450226 450228
450225 450227
75 75
1,2,3,4 5,6
450229 450231
450228 450230
76 76
1,2,3,4 5,6
450232 450234
450231 450233
77 77
1,2,3,4 5,6
450235 450237
450234 450236
78 78
1,2,3,4 5,6
450238 450240
450237 450239
79 79
1,2,3,4 5,6
450241 450243 450244
450240 450242 450243
80 80 81
1,2,3,4 5,6 1,2
OC 8. Active Diagnostic Trouble Code (DM1) SPN FMT OC 9. Active Diagnostic Trouble Code (DM1) SPN FMT OC 10. Active Diagnostic Trouble Code (DM1) SPN FMT OC 1. Previously Active Diagnostic Trouble Code (DM2) SPN FMT OC 2. Previously Active Diagnostic Trouble Code (DM2) SPN FMT OC 3. Previously Active Diagnostic Trouble Code (DM2) SPN FMT OC 4. Previously Active Diagnostic Trouble Code (DM2) SPN FMT OC 5. Previously Active Diagnostic Trouble Code (DM2) SPN FMT OC 6. Previously Active Diagnostic Trouble Code (DM2) SPN FMT OC 7. Previously Active Diagnostic Trouble Code (DM2) SPN FMT OC 8. Previously Active Diagnostic Trouble Code (DM2) SPN FMT OC 9. Previously Active Diagnostic Trouble Code (DM2) SPN FMT OC 10. Previously Active Diagnostic Trouble Code (DM2) SPN FMT OC DM1 Lamp Status Malfunction Lamp
Mask 00FFh
Woodward
Page 87/102
450245
450244
81
3,4
15445
450246 450247 450249 450250 450252 450253 450255 450256 450258 450259 450260 450261 450262 450263 450264 450265 450266 450267 450268 450270
450245 450246 450248 450249 450251 450252 450254 450255 450257 450258 450259 450260 450261 450262 450263 450264 450265 450266 450267 450269
81 82 82 83 83 84 84 85 85 86 86 86 87 87 87 88 88 88 89 89
5,6 1,2,3,4 5,6 1,2,3,4 5,6 1,2,3,4 5,6 1,2,3,4 5,6 1,2 3,4 5,6 1,2 3,4 5,6 1,2 3,4 5,6 1,2,3,4 5,6
15200 15202 15201 15203 15204 15205 15211 15206 15207 15208 15210 15214 15215 15212 15213 15209 15216
(unused) (unused) On Off Red Stop Lamp (unused) (unused) On Off Amber Warning Lamp (unused) (unused) On Off Protect Lamp (unused) (unused) On Off DM2 Lamp Status Malfunction Lamp (unused) (unused) On Off Red Stop Lamp (unused) (unused) On Off Amber Warning Lamp (unused) (unused) On Off Protect Lamp (unused) (unused) On Off internal Engine Speed (j1939-EEC1) Engine Coolant Temp. (J1939-ET1) Total engine hours (j1939-HOURS) Fuel temperature (j1939-ET1) Engine Oil Temperature (j1939-ET1) Engine Oil Pressure (j1939-EFL/P1) Fuel Rate (j1939-LFE) Coolant Level (j1939-EFL/P1) Throttle position (j1939-EEC2) Load at current Speed (j1939-EEC2) Engine oil level (j1939-EFL/P1) Boost pressure (j1939-IC1) Intake Manifold Temp (j1939-IC1) Barometric Pressure (j1939-AMB) Air inlet temperature (j1939-AMB) Actual engine torque (j1939-EEC1) internal Exhaust Gas Temp.(J1939-IC1) internal
Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask Mask
8000h 4000h 2000h 1000h 0800h 0400h 0200h 0100h 0080h 0040h 0020h 0010h 0008h 0004h 0002h 0001h 8000h 4000h 2000h 1000h 0800h 0400h 0200h 0100h 0080h 0040h 0020h 0010h 0008h 0004h 0002h 0001h rpm C h C C kPa L/h % % % % kPa C kPa C % C
0,1 1 1 1 0,01 1 0,01 0,1 0,1 1 0,1 1 1 0,1 1 1 0,01
Page 88/102
Woodward
Manual 37383D
Data Protocol 5004 (Generator Data)

CAN Data byte 0 (Mux) 0 0 0 1 1 2 2 3 3 4 4 5 Data byte 1,2 3,4 5,6 1,2 3,4,5,6 1,2 3,4,5,6 1,2 3,4,5,6 1,2 3,4,5,6 1,2 Parameter Description ID Multiplier Units
5 6
3,4,5,6 1,2
10100 160 170 144 171 10310 185 10311 161 2112 2113 2162 2163 2652 2457 2504 2603 2604 2623 2624 10017 3325 2560 2561 159 3064 3074 3084 4056 2944 10084 10083 10082 10086 10085 4073 4064 1714 15125 15126 111 112 113 135 1912 1913 1962 1963 2012 2013
6 7 7 8 8 9 9
3,4,5,6 1,2,3,4 5,6 1,2,3,4 5,6 1,2,3,4 5,6
Protocol ID, always 5004 Pickup speed 1 internal Gen. power factor 0.001 Av. Gen. Wye-Voltage 0.1 Gen. frequency 0.01 Av. Gen. Delta-Voltage 0.1 Analog output 1 0,01 Av. Gen. Current 0.1 Analog output 2 0,01 Meas. ground current 0.001 Overspeed 1 latched Mask: 8000h Overspeed 2 latched Mask: 4000h Underspeed 1 latched Mask: 2000h Underspeed 2 latched Mask: 1000h Unintended stop latched Mask: 0800h Speed det. alarm latched Mask: 0400h Shutdown malfunct. latched Mask: 0200h GCB fail to close latched Mask: 0100h GCB fail to open latched Mask: 0080h MCB fail to close latched Mask: 0040h MCB fail to open latched Mask: 0020h CAN-Fault J1939 latched Mask: 0010h Start fail latched Mask: 0008h Mainten. days exceeded latched Mask: 0004h Mainten. hours exceeded latched Mask: 0002h internal Mask: 0001h Calculated ground current 0.001 GCB syn. timeout latched Mask: 8000h MCB syn. timeout latched Mask: 4000h GGB Timeout latched Mask: 2000h Charge alt. low volt latched Mask: 1000h Ph.rotation mismatch latched Mask: 0800h no data receive at RPDO3 at CAN Interface 1 Mask: 0400h no data receive at RPDO2 at CAN Interface 1 Mask: 0200h no data receive at RPDO1 at CAN Interface 1 Mask: 0100h no data receive at RPDO2 (function 1) at CAN In- Mask: 0080h terface 2 no data receive at RPDO1 (function 1) at CAN In- Mask: 0040h terface 2 internal Mask: 0020h Parameter Alignment Mask: 0010h Missing members on CAN Mask: 0008h EEPROM failure latched Mask: 0004h Red stop lamp latched Mask: 0002h Amber warning lamp latched Mask: 0001h Gen. current 1 0.001 Gen. current 2 0.001 internal Gen. current 3 0.001 internal Total gen. power 1 Gen.overfreq. 1 latched Mask: 8000h Gen.overfreq. 2 latched Mask: 4000h Gen.underfreq. 1 latched Mask: 2000h Gen.underfreq. 2 latched Mask: 1000h Gen.overvolt. 1 latched Mask: 0800h Gen.overvolt. 2 latched Mask: 0400h
-rpm V Hz V % V % A Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit A Bit Bit Bit Bit Bit
Bit Bit Bit A A A W Bit Bit Bit Bit Bit Bit
Woodward
Page 89/102
Manual 37383D CAN Data byte 0 (Mux) Data byte Parameter Description ID
10 10
1,2,3,4 5,6
11 11
1,2,3,4 5,6
2062 2063 2218 2219 2220 2262 2263 2314 2315 136 2412 2413 3907 3263 3264 3955 2924 3124 4038 2644 2362 2363 2337 2338 2387 2388 108 10131
12
1,2
4153
12 13 13 14 14 15 15 16 16 17 17 18 18
3,4,5,6 1,2,3,4 5,6 1,2,3,4 5,6 1,2,3,4 5,6 1,2,3,4 5,6 1,2,3,4 5,6 1,2 3,4,5,6
114 109 115 110 116 2522 5541 5542
Gen.undervolt. 1 latched Gen.undervolt. 2 latched Gen. overcurr. 1 latched Gen. overcurr. 2 latched Gen. overcurr. 3 latched Gen. Rv/Rd pow.1 latched Gen. Rv/Rd pow.2 latched Gen. Overload IOP 1 latched Gen. Overload IOP 2 latched internal Total gen. reactive power Unbal. load 1 latched Unbal. load 2 latched Gen. Asymmetry latched Ground fault 1 latched Ground fault 2 latched Gen. phase rot. misw. Latched Gen act.pwr mismatch Latched Gen. unloading fault Latched Inv.time ov.curr. Latched Timeout dead bus op. Latched Gen. Overload MOP 1 latched Gen. Overload MOP 2 latched Gen. overexcited 1 latched Gen. overexcited 2 latched Gen. underexcited 1 latched Gen. underexcited 2 latched Gen. voltage L1-L2 control class latched Alarm class F latched Alarm class E latched Alarm class D latched Alarm class C latched Alarm class B latched Alarm class A latched Idle mode monitoring (suppresses undervolt, underfreq,...) Idle mode activ Start without closing GCB Block closing GCB A manual START has been requested A manual STOP has been requested Cooldown is active Auxiliary services generally active Engine delay timer has expired Breaker delay timer has expired Engine shall run Critical mode is active in automatic mode Engine is released Auxiliary services prerun is active Auxiliary services postrun is active Lamp test is active Gen. voltage L1-N Gen. voltage L2-L3 internal Gen. voltage L2-N internal Gen. voltage L3-L1 internal Gen. voltage 3-N internal Positive reactive gen power internal Frequency Active Power
Mask: 0200h Mask: 0100h Mask: 0080h Mask: 0040h Mask: 0020h Mask: 0010h Mask: 0008h Mask: 0004h Mask: 0002h Mask: 0001h 1 Mask: 8000h Mask: 4000h Mask: 2000h Mask: 1000h Mask: 0800h Mask: 0400h Mask: 0200h Mask: 0100h Mask: 0080h Mask: 0040h Mask: 0020h Mask: 0010h Mask: 0008h Mask: 0004h Mask: 0002h Mask: 0001h 0.1 Mask: 0040h Mask: 0020h Mask: 0010h Mask: 0008h Mask: 0004h Mask: 0002h Mask: 0001h Mask: 8000h Mask: 4000h Mask: 2000h Mask: 1000h Mask: 0800h Mask: 0400h Mask: 0200h Mask: 0100h Mask: 0080h Mask: 0040h Mask: 0020h Mask: 0010h Mask: 0008h Mask: 0004h Mask: 0002h Mask: 0001h 0.1 0.1 0.1 0.1 0.1 0,01 0,01 0,1
Bit Bit Bit Bit Bit Bit Bit Bit Bit var Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit V Bit Bit Bit Bit Bit Bit Bit
V V V V V Mvarh Hz kW
Page 90/102
Woodward
Manual 37383D CAN Data Data byte byte 0 (Mux) 19 1,2,3,4 19 5,6 20 1,2 Parameter Description ID
5640 5641 4154
20
3,4
4155
20
5,6
4156
Voltage Power Factor Crank (Starter) is active Operating Magnet / Gas relay is active Preglow / Ignition is active Mains settling timer is running Emergency mode is currently active Emergency breaked by override Emergency Mains overfrequency Emergency Mains underfrequency Emergency Mains overvoltage Emergency Mains undervoltage Stopping Magnet is active internal The genset runs mains parallel internal internal Increment Start Counter Dead Band Controller Freq./Power raise Dead Band Controller Freq./Power raise Dead Band Controller Volt./ReactPow raise Dead Band Controller Volt./ReactPow lower GCB is closed MCB is closed internal Synchronization GCB is active Opening GCB is active Closing GCB is active Synchronization MCB is active Opening MCB is active Closing MCB is active Unloading generator is active Unloading mains is active Power limited prerun GGB is closed GGB is released Synchronization GGB is active Opening GGB is active Closing GGB is active Dead busbar closure request for GCB or MCB or GGB Active power load share is acitve Reactive power load share is acitve Generator is requested internal internal internal internal internal internal internal
1 0,001 Mask: 8000h Mask: 4000h Mask: 2000h Mask: 1000h Mask: 0800h Mask: 0400h Mask: 0200h Mask: 0100h Mask: 0080h Mask: 0040h Mask: 0020h Mask: 0010h Mask: 0008h Mask: 0004h Mask: 0002h Mask: 0001h Mask: 8000h Mask: 4000h Mask: 2000h Mask: 1000h Mask: 0800h Mask: 0400h Mask: 0200h Mask: 0100h Mask: 0080h Mask: 0040h Mask: 0020h Mask: 0010h Mask: 0008h Mask: 0004h Mask: 0002h Mask: 0001h Mask: 8000h Mask: 4000h Mask: 2000h Mask: 1000h Mask: 0800h Mask: 0400h Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: Mask: 0200h 0100h 0080h 0040h 0020h 0010h 0008h 0004h 0002h 0001h
Woodward
Page 91/102
Manual 37383D
Data Protocol 5005 (Mains Data)

CAN Data byte 0 (Mux) 0 0 0 1 1 2 2 3 3 4 4 5 5 6 6 7 Data byte 1,2 3,4 5,6 1,2 3,4,5,6 1,2 3,4,5,6 1,2,3,4 5,6 1,2 3,4,5,6 1,2 3,4,5,6 1,2 3,4,5,6 1,2 Parameter Description ID Multiplier Units
3,4
7 8 8 9 9 10 10 11 11 12 12 13 13
5,6 1,2,3,4 5,6 1,2,3,4 5,6 1,2,3,4 5,6 1,2,3,4 5,6 1,2,3,4 5,6 1,2,3,4 5,6
10100 147 173 208 174 207 10111 134 10112 140 10115 150 2862 2863 2912 2913 2962 2963 3012 3013 3057 3114 3975 3217 3218 3241 3242 2985 2986 3035 3036 2934 118 121 119 122 120 123 -
Protocol ID (always 5005) Pickup speed internal Mains frequency Av. Mains Wye-Voltage Mains power factor Av. Mains Delta-Voltage Av. Mains Current internal Analog input 1 Mains current L1 Analog input 2 Total mains power Analog input 3 Total mains reactive power Mains ov.freq. 1 latched Mains ov.freq. 2 latched Mains un.freq. 1 latched Mains un.freq. 2 latched Mains ov.volt. 1 latched Mains ov.volt. 2 latched Mains un.volt. 1 latched Mains un.volt. 2 latched Mains phaseshift latched Mains decoupling latched internal internal internal Mains phase rot. misw. Latched internal internal Mains import power 1 latched Mains import power 2 latched Mains export power 1 latched Mains export power 2 latched Mains overexcited 1 latched Mains overexcited 2 latched Mains underexcited 1 latched Mains underexcited 2 latched internal Mns act.pwr mismatch latched internal internal internal internal internal internal internal Mains voltage L1-L2 internal Mains voltage L1-N internal Mains voltage L2-L3 internal Mains voltage L2-N internal Mains voltage L3-L1 internal Mains voltage L3-N internal
1 0.01 0.1 0.001 0.1 0.1 (changeable) 0.001 (changeable) 1 (changeable) 1 Mask: 8000h Mask: 4000h Mask: 2000h Mask: 1000h Mask: 0800h Mask: 0400h Mask: 0200h Mask: 0100h Mask: 0080h Mask: 0040h Mask: 0020h Mask: 0010h Mask: 0008h Mask: 0004h Mask: 0002h Mask: 0001h Mask: 8000h Mask: 4000h Mask: 2000h Mask: 1000h Mask: 0800h Mask: 0400h Mask: 0200h Mask: 0100h Mask: 0080h Mask: 0040h Mask: 0020h Mask: 0010h Mask: 0008h Mask: 0004h Mask: 0002h Mask: 0001h 0.1 0.1 0.1 0.1 0.1 0.1
-rpm Hz V V V A W var Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit V V V V V V Woodward
Page 92/102
Manual 37383D
Data Protocol 6000 (Load Share Message)

General
The load share message contains all data, which is required for load/var sharing, load-dependent start/stop and dead bus detection. Further data, which are to be exchanged between the control units concern time synchronization and parameter alignment. Parameter alignment is intended for those parameters, which must be configured identically for all units participating in load sharing, to ensure a proper operation of load sharing or load-dependent start/stop. In order to lower the bus load, the messages are divided into "fast", "normal", and "slow" refreshed data. The mux is identified accordingly with "F", "N", and "S" (refer to the following tables). The load share message contains one fast, two normal, and four slow messages, which are made up as shown in Table 3-6.
Timing
The time interval between two fast messages (TFast , i.e. the time for refreshing a fast message) is configured with the parameter "Transfer rate LS fast message" (parameter 9921 on page 23). The time intervals between refreshing a normal or slow messages depend on this parameter as well according to the following sequence: S0 F N0 F N1 F S1 F N0 F N1 F S2 F N0 F N1 F S3 F N0 F N1 F TFast = time interval between refreshing the fast message TNormal = time interval between refreshing a normal message = 3 x TFast TSlow = time interval between refreshing a slow message = 12 x TFast Example: The parameter "Transfer rate LS fast message" (parameter 9921 on page 23) is configured to "0.10 s". The sequence of the sent messages for TFast = 100 ms (i.e. 0.10 s) is shown in Table 3-6. This means that a new message is sent every 50 ms.
Time [ms] Sent message Mux # Time [ms] Sent message Mux # 0 S0 0 600 S2 5 50 F 3 650 F 3 100 N0 1 700 N0 1 150 F 3 750 F 3 200 N1 2 800 N1 2 250 F 3 850 F 3 300 S1 4 900 S3 6 350 F 3 950 F 3 400 N0 1 1000 N0 1 450 F 3 1050 F 3 500 N1 2 1100 N1 2 550 F 3 1150 F 3
Table 3-6: Load share message - example
The maximum length of the CAN bus load share line depends on this parameter as well. The values in Table 3-7 are valid for 32 participants and a bus load of approx. 30 %.
TFast [ms] 100 200 300 TNormal [ms] 300 600 900 TSlow [ms] 1200 2400 3800 Baud rate 250 kBaud 125 kBaud 50 kBaud Distance 250 m 500 m 1000 m
Table 3-7: Load share line - max. length
Woodward
Page 93/102
Manual 37383D
Load share bus communication - "fast" refreshed data Mux Byte Bit Function F 0 3 1 Generator real load capacity utilization rate, L-Byte 2 Generator real load capacity utilization rate, H-Byte 3 Generator reactive load capacity utilization rate, L-Byte 4 Generator reactive load capacity utilization rate, H-Byte 5 0 Active power load sharing is enabled 1 Reactive power load sharing is enabled 2 GCB is closed 3 MCB is closed 4 GGB (generator group breaker) is closed 5 Dead bus closure request is active 6 Mains settling time is running 7 Shutdown alarm is active (alarm class C,D,E,F) 6 0-4 Bus segment / node 5 Not used 6 LDSS: add-on request enabled 7 LDSS: add-off request enabled (reserved) 7 Not used Load share bus communication - "normal" refreshed data Mux Byte Bit Function N0 0 1 1 Generator real load, L-Byte, L-Word 2 Generator real load, H-Byte, L-Word 3 Generator real load, L-Byte, H-Word 4 Generator real load, H-Byte, H-Word 5 0-3 Real load control state
Remark Mux identifier Integer [], unsigned Integer [], unsigned
Dead bus detection Back synchronization to mains Max. 32 nodes possible Load dependent start / stop Load dependent start / stop
Remark Mux identifier Long [W]
4-7
Reactive load control state
0-3
Engine state
4,5
Operating mode
6 7 7
Generator request Not used Not used
2: Static 3: Isochronous 4: Base load control 5: Export/import control 10:Load share 0, 1, 6, 7, 8, 9, 11, : internal 2: Static 3: Isochronous 4: Reactive load control 5: Import/export reactive load 10:Reactive load share 0, 1, 6, 7, 8, 9, 11, : internal 1: Locked out 2: Off 3: Preglow 4: Crank 5: Run 6: Cool down 7: Spin down 8: Start pause 9: Idle 0, 10, 11, : internal 0: Not available 1: STOP 2: MANUAL 3: AUTOMATIC Generator is in AUTOMATIC mode and able to produce rated active power
Page 94/102
Woodward
Manual 37383D
Load share bus communication - "normal" refreshed data Mux Byte Bit Function N1 0 2 1 Generator reactive load, L-Byte, L-Word 2 Generator reactive load, H-Byte, L-Word 3 Generator reactive load, L-Byte, H-Word 4 Generator reactive load, H-Byte, H-Word 5 0 Generator voltage and frequency ok 1 Busbar voltage and frequency ok 2 Mains voltage and frequency ok 3 Fourth system voltage and frequency ok 4 Not used 5 Not used 6 Not used 7 Not used 6 Not used 7 Not used Load share bus communication - "slow" refreshed data Mux Byte Bit Function S0 0 0 1 Protocol-Identifier 2 3 Generator rated real power, L-Byte, L-Word 4 Generator rated real power, H-Byte, L-Word 5 Generator rated real power, L-Byte, H-Word 6 Generator rated real power, H-Byte, H-Word 7 Not used S1 0 4 1 Generator rated reactive power, L-Byte, L-Word 2 Generator rated reactive power, H-Byte, L-Word 3 Generator rated reactive power, L-Byte, H-Word 4 Generator rated reactive power, H-Byte, H-Word 5 Not used 6 0-4 Priority 5-7 Not used 7 Not used S2 0 5 1 Operating hours L-Byte, L-Word 2 Operating hours H-Byte, L-Word 3 Operating hours L-Byte, H-Word 4 Operating hours H-Byte, H-Word 5 0 Alarm class A occurred 1 Alarm class B occurred 2 Alarm class C occurred 3 Alarm class D occurred 4 Alarm class E occurred 5 Alarm class F occurred 6 Warning alarm class occurred 7 Not used 6 Not used 7 Not used S3 0 6 1 Remaining days before maintenance, L-Byte 2 Remaining days before maintenance, H-Byte 3 Remaining operating hours before maintenance, L-Byte 4 Remaining operating hours before maintenance, H-Byte 5 Checksum parameters L-Byte 6 Checksum parameters H-Byte 7 Not used
Woodward
Remark Mux identifier Long [var]
Remark Mux identifier Long [0.1 kW]
Mux identifier Long [0.1 kvar]
Up to 32 Mux identifier Long [h]
Mux identifier Integer [d] Integer [h] Load share and load-dependent start / stop parameters
Page 95/102
Manual 37383D
Additional Data Protocol Parameters

Remote Control Word 1 - Object 21F7h (Parameter ID 503)
This object is required for remote control. The data type is UNSIGNED16. The internal parameter 503 of the easYgen must be set to react on the remote control instructions. This is performed by sending rising signals for the respective bits (refer to Figure 3-38 for the priority of start and stop signals).
Name Unit Data type Note
Parameter no.
503
21F7h
Object ID
Control word 1 Bit 15 Not used Bit 14 Not used Bit 13 Not used Bit 12 Not used Bit 11 Not used Bit 10 Not used Bit 9 Not used Bit 8 Not used Bit 7 Not used Bit 6 Not used Bit 5 Not used Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Ext. Acknowledge (rising edge) Must be set twice to acknowledge Must always be set to 0 Must always be set to 0 Stop bit (rising edge) Start bit (rising edge)
Bit field
unsigned16
To acknowledge, a 0 must be written and then a 1 To stop, a 0 must be written and then a 1 To start, a 0 must be written and then a 1
Table 3-8: Remote control telegram
Bit 0 Start bit With the rising edge of the bit, the easYgen activates the remote request command (LogicsManager input command variable 04.13). The condition of the start command will be stored and may be used as command variable for the LogicsManager. Bit 1 Stop bit With the rising edge of the bit, the easYgen deactivates the remote request command (LogicsManager input command variable 04.13). The condition of the start command will be stored and may be used as command variable for the LogicsManager. Bit 4 "Reset alarms" This bit controls the LogicsManager input command variable 04.14. The remote acknowledge bit must be set and reset twice to acknowledge an alarm completely. The first rising edge disables the horn and the second rising edge acknowledges the alarm.
Page 96/102
Woodward
Manual 37383D
Remote start /stop: The command variable "04.13 Remote request" changes to "1" (high) if the start bit is enabled and changes back to "0" (low) if the stop bit is enabled. Ext. Acknowledge: The command variable "04.14 Remote acknowledge" is the reflection of the control bit. The easYgen deactivates the horn with the first change from "0" to "1" of the logical output "External acknowledge", and acknowledges all alarm messages, which have occurred and are no longer active, with the second change from "0" to "1". Figure 3-38 shows the reaction of the command variable on the various status changes of the bits:
Start bit
Stop bit
Com. var. 04.13 Remote request no reaction, because simultanous stops, because higher prioritized
Figure 3-38: Remote control - start/stop priority
ATTENTION
The easYgen does NOT react on the disabling of the start bit, but only on the enabling of the stop bit. This has the advantage that it is not required to maintain the connection established for the whole time in case of a remote start via a modem.
Remote Control Word 2 - Object 21F8h (Parameter ID 504)

This object is required for remote control. The data type is UNSIGNED16.
Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 =1 =1 =1 =1 =1 =1 =1 =1 =1 =1 =1 =1 =1 =1 =1 =1
Request active power set point 2 this bit activates the LogicsManager input [04.40] "Remote power set point 2" and is dedicated for switching from active power set point 1 to active power set point 2 Request power factor set point 2 this bit activates the LogicsManager input [04.39] "Remote PF set point 2" and is dedicated for switching from power factor set point 1 to power factor set point 2 Request frequency set point 2 this bit activates the LogicsManager input [04.38] "Remote frequency set point 2" and is dedicated for switching from frequency set point 1 to frequency set point 2 Request voltage set point 2 this bit activates the LogicsManager input [04.37] "Remote voltage set point 2" and is dedicated for switching from voltage set point 1 to voltage set point 2
Woodward
Page 97/102
Manual 37383D
Remote Active Power Set Point - Object 21FBh (Parameter ID 507)

This object is required to transmit the active power set point for active power control. The data type is INTEGER32. The value is scaled in [kW * 10]. Example: 100 kW = 1000 = 03E8h
Remote Power Factor Set Point - Object 21FCh (Parameter ID 508)

This object is required to transmit the power factor set point for power factor control. The data type is INTEGER16. The valid range for this value is [-710 to 1000 to 710]. Example: PF (cosphi) = c0.71 (capacitive) = -710 = FD3Ah PF (cosphi) = 1.00 = 1000 = 03E8h PF (cosphi) = i0.71 (inductive) = 710 = 02C6h
Remote Frequency Set Point - Object 21FDh (Parameter ID 509)

This object is required to transmit the frequency set point for frequency control. The data type is UNSIGNED16. The value is scaled in [Hz * 100]. Example: 50.00 Hz = 5000 = 1388h
Remote Voltage Set Point - Object 21FEh (Parameter ID 510)

This object is required to transmit the voltage set point for voltage control. The data type is UNSIGNED32. The value is scaled in [V]. Example: 400 V = 400 = 190h 10000 V = 10000 = 2710h
Page 98/102
Woodward
Manual 37383D
Remote IKD 1 DI 1 to 8 Request - Object 3F4Bh (Parameter ID 8011)

This object is required to receive the state of the external discrete inputs 1 to 8 of an IKD 1. The data type is UNSIGNED8. This object cannot be read.
Byte 1 Bit 1 to 7 Bit 0 Byte 2 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Byte 3 to 8 Bit 0 to 7 Always 0 Always 1 External discrete input 8 [DIex08] External discrete input 7 [DIex07] External discrete input 6 [DIex06] External discrete input 5 [DIex05] External discrete input 4 [DIex04] External discrete input 3 [DIex03] External discrete input 2 [DIex02] External discrete input 1 [DIex01] Always 0
Remote IKD 1 DI 9 to 16 Request - Object 3F4Ch (Parameter ID 8012)

This object is required to receive the state of the external discrete inputs 9 to 16 of an IKD 1. The data type is UNSIGNED8. This object cannot be read.
Byte 1 Bit 1 to 7 Bit 0 Byte 2 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Byte 3 to 8 Bit 0 to 7 Always 0 Always 1 External discrete input 16 [DIex16] External discrete input 15 [DIex15] External discrete input 14 [DIex14] External discrete input 13 [DIex13] External discrete input 12 [DIex12] External discrete input 11 [DIex11] External discrete input 10 [DIex10] External discrete input 9 [DIex09] Always 0
Remote External DI Request - Object 3F4Dh (Parameter ID 8013)

This object is required to receive the state of the external discrete inputs 1 to 16 (e.g. of a Phoenix expansion card). The data corresponds to the data in the objects 8011 and 8002 and the data type is UNSIGNED16.
Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 External discrete input 16 [DIex16] External discrete input 15 [DIex15] External discrete input 14 [DIex14] External discrete input 13 [DIex13] External discrete input 12 [DIex12] External discrete input 11 [DIex11] External discrete input 10 [DIex10] External discrete input 9 [DIex09] External discrete input 8 [DIex08] External discrete input 7 [DIex07] External discrete input 6 [DIex06] External discrete input 5 [DIex05] External discrete input 4 [DIex04] External discrete input 3 [DIex03] External discrete input 2 [DIex02] External discrete input 1 [DIex01]
Woodward
Page 99/102
Manual 37383D
Remote IKD 1 Control - Object 34F0h (Parameter ID 8000)

This object is required to assemble a message to the IKD 1(s). The bits in this object are always 0.
Remote IKD 1 DO 1 to 8 Control - Object 34F1h (Parameter ID 8001)

This object is required to control the external outputs (relays) 1 to 8 of an IKD 1. The data type is UNSIGNED16.
Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 External discrete output 8 [Rex08] External discrete output 7 [Rex07] External discrete output 6 [Rex06] External discrete output 5 [Rex05] External discrete output 4 [Rex04] External discrete output 3 [Rex03] External discrete output 2 [Rex02] External discrete output 1 [Rex01] Always 0 Always 0 Always 0 Always 0 Always 0 Always 0 Always 0 Always 0
Remote IKD 1 DO 9 to 16 Control - Object 34F2h (Parameter ID 8002)

This object is required to control the external outputs (relays) 9 to 16 of an IKD 1. The data type is UNSIGNED16.
Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 External discrete output 16 [Rex16] External discrete output 15 [Rex15] External discrete output 14 [Rex14] External discrete output 13 [Rex13] External discrete output 12 [Rex12] External discrete output 11 [Rex11] External discrete output 10 [Rex10] External discrete output 9 [Rex09] Always 0 Always 0 Always 0 Always 0 Always 0 Always 0 Always 0 Always 0
Page 100/102
Woodward
Manual 37383D
Remote External DO Control - Object 34F5h (Parameter ID 8005)

This object is required to control the external outputs (relays) 1 to 16 (e.g. of a Phoenix expansion card). The data corresponds to the data in the objects 8001 and 8002 and the data type is UNSIGNED16.
Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 External discrete output 16 [Rex16] External discrete output 15 [Rex15] External discrete output 14 [Rex14] External discrete output 13 [Rex13] External discrete output 12 [Rex12] External discrete output 11 [Rex11] External discrete output 10 [Rex10] External discrete output 9 [Rex09] External discrete output 8 [Rex08] External discrete output 7 [Rex07] External discrete output 6 [Rex06] External discrete output 5 [Rex05] External discrete output 4 [Rex04] External discrete output 3 [Rex03] External discrete output 2 [Rex02] External discrete output 1 [Rex01]
Woodward
Page 101/102
We appreciate your comments about the content of our publications. Please send comments to: stgt-documentation@woodward.com Please include the manual number from the front cover of this publication.
Woodward GmbH Handwerkstrasse 29 - 70565 Stuttgart - Germany Phone +49 (0) 711-789 54-0 Fax +49 (0) 711-789 54-100 sales-stuttgart@woodward.com Homepage http://www.woodward.com/power
Woodward has company-owned plants, subsidiaries, and branches, as well as authorized distributors and other authorized service and sales facilities throughout the world. Complete address/phone/fax/e-mail information for all locations is available on our website (www.woodward.com). 2009/10/Stuttgart

Manual Gerador 37383

Uploaded by

Copyright:

Available Formats

Manual Gerador 37383

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manual Gerador 37383

Uploaded by

Copyright:

Available Formats

37383D

easYgen-3000 Series (Package P1) Genset Control

easYgen-3000 Series (Package P1) - Genset Control

Important definitions WARNING

Woodward All Rights Reserved.

easYgen-3000 Series (Package P1) - Genset Control

CHAPTER 2. CAN BUS CONFIGURATION ................................................................................. 12

easYgen-3000 Series (Package P1) - Genset Control

CHAPTER 3. MODBUS COMMUNICATIONS ................................................................................ 47

easYgen-3000 Series (Package P1) - Genset Control

Figures and Tables

easYgen-3000 Series (Package P1) - Genset Control

easYgen-3000 Series (Package P1) - Genset Control

Chapter 1. General Information

37223 37224 37225 37226 37383 37399 37409

GR37223 GR37224 GR37225 GR37399 -

Table 1-1: Manual - overview

easYgen-3000 Series (Package P1) - Genset Control

Table 1-2: Interfaces - overview

CAN bus 2 CANopen

(IKD 1 and Phoenix expansion boards)

CAN bus 2 CANopen

(IKD 1 and Phoenix expansion boards)

Figure 1-1: easYgen - interface overview Page 8/102 Woodward

easYgen-3000 Series (Package P1) - Genset Control

Figure 1-2: Interface overview - CAN interfaces

Table 1-3: CAN interface 1 - I/O board combination matrix

easYgen-3000 Series (Package P1) - Genset Control

Figure 1-3: Interface overview - serial interfaces

easYgen-3000 Series (Package P1) - Genset Control

RS-485 Modbus Half/Full Duplex Application

Figure 1-4: Interface overview - serial interface Modbus full-duplex

Figure 1-5: Interface overview - serial interface Modbus half-duplex

easYgen-3000 Series (Package P1) - Genset Control

Chapter 2. CAN Bus Configuration

Configure CAN Interface 1

CAN bus 1: Baud rate

20 / 50 / 100 / 125 / 250 / 500 / 800 / 1,000 kBaud

Node-ID CAN-Bus 1 Node-ID CAN-Bus 1

CANopen Master CANopen Master

Manual 37383D Producer heartbeat time Producer heartbeat time

easYgen-3000 Series (Package P1) - Genset Control

CAN bus 1: Producer heartbeat time

COB ID SYNC Message COB ID SYNC Message

CAN bus 1: Sending time for SYNC Message

Additional Server SDOs (Service Data Objects)

CAN bus 1: Additional Server SDOs - 2. Node ID

Manual 37383D 3. Node-ID 3. Node-ID

easYgen-3000 Series (Package P1) - Genset Control

CAN bus 1: Additional Server SDOs - 3. Node ID

Receive PDOs (Process Data Objects) 1 to 3

CAN bus 1: Receive PDO 1 - COB ID

easYgen-3000 Series (Package P1) - Genset Control

CAN bus 1: Receive PDO 1 - Number of mapped objects

1. Mapped Object 1. Mapped Objekt

CAN bus 1: Receive PDO 1 - 1. mapped object

2. Mapped Object 2. Mapped Objekt

CAN bus 1: Receive PDO 1 - 2. mapped object

3. Mapped Object 3. Mapped Objekt

CAN bus 1: Receive PDO 1 - 3. mapped object

b = b0 to bn-1 UNSIGNEDn(b) = bn-12n-1+....+b121+b0*20

b = b0 to bn-1 SIGNEDn(b) = bn-22n-2+...+b121+b0*20 SIGNEDn(b) = SIGNEDn(^b)-1