Home

DTSC-200 Series Interfaces Interface Description

1. Parameter Setting range Data type 1774 Rated voltage Sl 50 to 650000 V UNSIGNED 32 Modbus address 40000 Par ID 1 41775 Modbus length 2 UNSIGNED 32 The following Modscan32 screenshot shows the configurations made to address parameter 1774 ModScan32 DTSC File Connection Setup View Window Help Dani jaa amp v N nje sa oa aja Device Id EN Number of Polls 3 Address 1775 MODBUS Point Type Valid Slave Responses 3 Length 103 HOLDING REGISTER 41775 000003 41776 lt 00400 gt For Help press Fl Polls 3 Resps 3 Figure 3 4 Modbus configuration example 2 Page 18 83 O Woodward Manual 37389 DTSC 200 Series Interfaces Example 3 Addressing source 2 voltage measuring a Parameter Setting range Data type 3Ph 4W 0 1861 S2 voltage measuring e a UNSIGNED 16 1Ph 3W 3 Modbus address 40000 Par ID 1 41862 Modbus length 1 UNSIGNED 16 i NOTE If the setting range contains a list of parameter settings like in this example the parameter settings are numbered and start vvith 0 for the first parameter setting The number corresponding vvith the respec tive parameter setting must be configured The following Modscan32 screenshot shows the configurations made to address parameter 1861 which is con figured to 3Ph 4W ModScan32 DTSC File Connection Setup View Window Help Deg a a
2. __ 252 253 A PDO will not be sent 254 255 A PDO will be sent cyclically This sub index does not change the PDO communication parameter screen This sub index can be set in the dis play screen Transmission type in sub menu CAN OPEN TPDO 1 2 3 4 Sub index Sh The time is rounded up to the next full 5 ms The sub index can be set in the display screen Event timer in sub menu CAN OPEN TPDO 1 2 3 4 Object 1A00h 1A1Fh Transmit PDO Mapping Parameter The mapping for the PDOs which the participant can send is located here An exact description of the entries can be found in the chapter Parameter description CAUTION The parameter can be configured only if the respective PDO is valid Object 1800 Sub index 1 Bit 31 is set Object description A 1A00h 1A1Fh K Transmit PDO mapping Object code RECORD Data type PDO figure Category conditioned obligatory for every supported PDO Page 64 83 Woodward Manual 37389 DTSC 200 Series Interfaces Entry description Sub index 0h Description number of mapped application objects in PDO Entry category obligatory ACCESS scrii Read Only Read Write if dynamic mapping is supported PDO figure no Value range 4 Default value 4 Sub index 1h 4h Description PDO mapping for the n application object to be mapped Ent
3. CAN bus Server gt Client COB ID tx 1 to FFFFFFFF In a multi master application each Master needs its own identifier Node ID from the unit in order to receive remote signals i e acknowledge 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 unit The COB IDs must be entered in decimal numbers in LeoPC1 Page 36 83 Woodward Manual 37389 DTSC 200 Series Interfaces CANopen Receive PDO RPDO x x 1 2 Two RPDOs are available E COB ID Receive PDO 1 2 COB ID 1 to FFFFFFFF A COB ID CL2 This parameter contains the communication parameters for the PDOs the device is 300 able to receive This corresponds to object 1400h sub index 1h see Object 1400h 141Fh Receive PDO Communication Parameter on page 62 CAUTION The COB IDs have to be configured different even if one RPDO is configured to no func 2 E Function Function for RPDO 1 2 no func 1st IKD 2nd IKD Bk 16DIDO Co 16DIDO A Funktion CL2 The unit provides pre configured CAN bus settings for the connection of different i 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 Ist IKD The unit is pre configured for the connection of a Woodward IKD 1 expansion board 2nd IKD The unit is pre configured fo
4. Manual 37389 DTSC 200 Series Interfaces The following Modscan32 screenshot shows the configurations made to remote control parameter 503 It is pos sible to set the format to binary to view single the bits using the display options ModScan32 Remote Acknowledge Modbus E nm x Fille Connection Setup View Window Help Siss Remote Acknowledge Modbus Device Id EN Add 0504 Number of Polls 1876 ES MODBUS Point Type Di Glave TARA 1876 Length fl 03 HOLDING REGISTER gt Reset Ctrs fosos lt D000000000010000 gt For Help press Fi Figure 5 14 Modbus remote control parameter 503 By double clicking the address a Write Register command may be issued Figure 5 15 shows how bit 4 is set us ing the ModScan32 Software xi Node f Address 504 Bit Pattern HEHE EEE ER Cancel Figure 5 15 Modbus write register NOTE Be sure to enter the password for code level 2 or higher for the corresponding interface to get access for changing parameter settings Woodward Page 81 83 Manual 37389 DTSC 200 Series Interfaces Sending a Data Protocol via TPDO Cyclically Sending of Data This 1s a configuration example for sending an object with the index 3190 data protocol 4007 on CAN ID 2AEh every 20 ms on TPDOI For this TPDO1 must be configured as follows COB ID 2AE hex Transmission type 255 Event timer 20 ms Number of Mapped Objects 1 there is
5. Bit 11 Discrete input DEx12 Bit 10 Discrete input DEx11 Bit 9 Discrete input DEx10 Bit 8 Discrete input DEx09 Bit 7 Discrete input DEx08 Bit 6 Discrete input DEx07 Bit 5 Discrete input DEx06 Bit 4 Discrete input DEx05 Bit 3 Discrete input DEx04 Bit 2 Discrete input DEx03 Bit 1 Discrete input DEx02 Bit 0 Discrete input DEx01 15603 5CF3 Source 1 values unsigned 64 Data Protocol 15604 5CF4 Source 2 values unsigned 64 Data Protocol Woodward Page 75 83 Manual 37389 DTSC 200 Series Interfaces Appendix C Application Examples HA Remote Control The DTSC 200 controller may be configured to perform acknowledgement functions remotely through the CAN bus The required procedure is detailed in the following steps i NOTE Refer to the operation manual 37387 for a detailed description of the navigation through the various display screens A detailed description of the individual parameters may be found in the configuration manual 37386 Be sure to enter the password for code level 2 or higher to be able to access the required configuration screens The DTSC may be acknowledged with CAN Modbus Therefore a logical command variable has to be config ured with the LogicsManager 04 14 Remote acknowledge Configuration of the LogicsManager Functions Open the main menu by pressing the C softkey and navigate to Configure monitoring screen by using the softkey di the Confi
6. 450049 450050 450051 450052 000005 18432 00000 00000 00060 00000 00000 00064 00000 000005 00283 000005 00000 00000 00000 00000 00000 00000 00000 00000 000600 00003 00000 lt D0000 gt lt D0000 gt lt 00000 gt 450053 450054 450055 450056 450057 450058 450059 450060 450061 450062 450063 450064 450065 450066 450067 450068 450069 450070 450071 450072 450073 450074 450075 450076 450077 450078 00000 lt 00000 gt lt D0000 gt lt 00000 gt lt 00003 gt 00100 00000 00003 00000 lt 00000 gt lt 00000 gt lt D0000 gt 00000 lt 00001 gt lt 00480 gt 00000 lt D0000 gt lt 13223 gt 00000 00003 00000 00000 lt 00000 gt lt 00000 gt 00000 lt 00000 gt 450079 450080 450081 450082 450083 450084 450085 450086 450087 450088 450089 450090 450091 450092 450093 450094 450095 450096 450097 450098 450099 450100 450101 450102 450103 450104 lt 01600 gt lt 21248 gt lt 33280 gt lt 00033 gt lt 00272 gt lt 16384 gt lt 00064 gt lt 00128 gt lt 00000 gt 19968 00000 00003 04700 lt 00000 gt lt 00000 gt lt 04700 gt lt 00000 gt lt 00000 gt lt 04700 gt lt 00000 gt lt 00000 gt lt 04700 gt lt 00000 gt lt 00000 gt l
7. Mask 0002h Mask 0001h Page 50 83 Woodward Manual 37389 DTSC 200 Series Interfaces Modbus Modbus Data Para Description Multiplier Units Data Type Byte meter Modicon Start ID start addr 450088 450087 29 1 2 10337 Start Delay timer S1 is expired Mask 8000h unsigned 16 Start Delay timer S2 is s expired Mask 4000h inemal Woodward Page 51 83 Manual 37389 DTSC 200 Series Interfaces Data Protocol 4800 Source 1 Data Data Para Byte meter ID EXI MA E 3 3 10167 RES ER gt besch Description Multiplier Units Data Type CO m mA Mask 4000h Mask 2000h Mask 1000h Mask 0800h Mask 0400h Mask 0200h Latched Alarm S2 voltage imbalance Latched Alarm S1 Phase rotation mismatch Latched Alarm S2 Phase rotation mismatch Latched Alarm Inphase Check timeout Latched Alarm Startfailure S2 Latched Alarm Unintended Stop S2 qunsignedl AAA BE NEE unsigned16 unsigned16 Mask 8000h Bit unsignedl internal internal Mask 0001h Source 1 Voltage 3 N Latched Alarm S1 voltage imbalance Mask 8000h Page 52 83 O Woodward Manual 37389 DISC 200 Series Interfaces Data Para Description Multiplier Units J Data Type Byte Eed Latched Alarm Startfailure S1 Latched Alarm Unintended Stop SI Latched Alarm EE time exceeded internal pem tt internal os internal internal internal
8. This parameter defines the baud rate for communications Please note that all participants on the service interface must use the same baud rate Serial interface 2 Parity no even odd The used parity of the service interface 1s set here Serial interface 2 Stop bits one two The number of stop bits 1s set here Serial interface 2 Full halfduplex mode Fullduplex Halfduplex CL2 Fullduplex Fullduplex mode is enabled Ra Halfduplex Halfduplex mode is enabled a ModBus Slave ID Serial interface Modbus Slave ID 0 to 255 A ModBus Slave ID CL2 The Modbus device address is entered here which is used to identify the device 3185 via Modbus If 0 is entered here the Modbus Slave module is disabled Modbus Reply delay time Serial interface Reply delay time 0 00 to 1 00 s 2 Modbus Zeitverz ger der Antwort CL2 This 1s the minimum delay time between a request from the Modbus master and 3186 the sent response of the slave This time is also required if an external interface converter to RS 485 is used for example Please note that you also need the DPC in this case Page 14 83 O Woodward Manual 37389 DTSC 200 Series Interfaces Modbus Addressing and Data Model The DTSC Modbus slave module distinguishes between visualization data and configuration amp remote control data The different data 1s accessible over a split address range and may be read via the Read Holding Register function Furthermore DTSC parameters a
9. Woodward Page 43 83 Manual 37389 DTSC 200 Series Interfaces Modbus Modbus Data Para Description Multiplier Units Data Type Byte ee Modicon Start signed32 3 4 5 6 Gp Some Tere dov signed32 450025 450024 L2 10169 unsigned16 HET mus ws p ssp sweervdaem fu va 450028 450027 10106 unsigned16 Lewes uses 9 3S6 H2 A A Page 44 83 O Woodward Manual 37389 rr DTSC 200 Series Interfaces Modbus Modbus Data Para Description Multiplier Units Data Type Byte S Modicon Start Em 150050 10107 unsigned lp svi ao i6 ASA Sere ia fr vig EE 1450035 450034 11 3456 123 Sourel Voltage3 N 01 V signed32 1450037 450036 12 12 jinema 01 VW signedl 450038 450037 12 134 5 6 111 LoadCurentPhae A 0001 A signed32 rasooa 4sonss 13 12 Pineal signed GE 450040 L13 3436 112 Load Curent Phase El EMEN _ 450043 450042 10133 unsigned16 mn sen e BASA Londen Pass oO A igit 450046 150048 10134 unsigned16 HEAT CRE A A AAA 1450048 450047 15 56 atea LI 450049 450048 16 12 itemi TI Woodward Page 45 83 Manual 37389 DTSC 200 Series Interfaces Modbus Modbus Data Para Description Multiplier Units Data Type Byte eg Modicon Start 450050 450049 3 4 5 6 136 Load Reactive Power If Load is powered by signed32 Source E I 450052 4
10. Woodward Page 79 83 Manual 37389 DTSC 200 Series Interfaces The same is valid for the additional SDO communication channels 3 4 and 5 Figure 5 13 shows exemplary request data for the device on the CANopen bus lol xi ES TransmitClient Remote Acknowledge opt File Edit View Function Options Trace Help PrE T Qux LES Cm SES o D GN u Jesi Wes Deseipion keet Tics 2 byt GF Remote Acknowledge S00 12 dec 0 2B Fr 21 01 1000 Figure 5 13 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 be fore the first has answered the second one will be refused Remote Control via Modbus The DTSC controller may be configured to perform 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 Con trol Telegram on page 77 It may be necessary to shift the address by 1 depending on the used PC software In this case the ad dress would be 504 for example Be sure to check both possibilities in case of remote control problems o Parameter Setting range Data type 503 Remote control word 0 to 65535 UNSIGNED 16 Modbus address 40000 Par ID 1 504 Modbus length 1 UNSIGNED 16 Page 80 83 O Woodward
11. a i a i a pu ul Table 3 1 Modbus address range block read NOTE Table 3 1 is only an excerpt of the data protocol lt conforms to the data protocol that is also used by CAN bus Refer to Appendix A Transmission Telegram on page 43 for the complete protocol The following exemplary ModScan32 screenshot shows the configurations made to read the visualization proto col with a block read of 128 registers ModScan32 DTSC File Connection Setup View Window Help D d M x Device Id EN MODBUS Point Type 03 HOLDING REGISTER N Address 50001 Number of Polls 91 alid Slave Responses 90 Reset Ctrs Length ERR 1450002 1450003 450004 1450005 f 450006 450007 1450008 7450009 450010 q450011 1150012 450013 8450014 1450015 i4500156 1450017 450018 i450013 450020 1450021 f 450022 1450023 450024 M450025 Jasoo26 lt 04700 gt 00000 000005 00000 00000 000005 000005 00000 00000 01000 00000 000005 000855 lt 00000 gt 00000 00000 00000 000005 00282 lt 00000 gt lt 00000 gt lt 00000 gt lt 00000 gt lt 00000 gt lt 01024 gt lt 00000 gt For Help press Fi 450027 450028 450029 450030 450031 450032 450033 450034 450035 450036 450037 450038 450039 450040 450041 450042 450043 450044 450045 450046 450047 450048
12. and so on No PDOs will be sent for the remaining values Data in the PDO The data which is transmitted with the PDO is to be configured at the unit The parameters Mapped Object are provided for this The parameter Number of Mapped Objects 1s used to configure the number of mapped objects Then up to four objects may be entered whose data is to be transmitted The identifiers of the objects may be found in the operating instructions O Woodward Page 25 83 Manual 37389 DTSC 200 Series Interfaces Setting the Transmit PDO Examples With the TPDOs up to 8 data bytes can be send Configuration of a data protocol Number of mapped objects Parameter no 1 to 4 1 Mapped Object for example parameter no 3191 2 Mapped Object 3 Mapped Object 4 Mapped Object Configuration of a TPDO message A TPDO can contain one or more mapped objects with a maximum of 4 data bytes each The TDPO message has a maximum combined total of 8 bytes Example 1 Number of mapped objects_ Parameter no 2 O 3 Mapped Object Parameterno 0 4 Mapped Object Parameterno O The TPDO has a length of 6 bytes Example 2 Mapped Offa Pater ro 108 ange ge UUO 1 Mapped Object Parameter no 108 unsigned32 gt 4Byte 3 Mapped Object Parameter no OJ S O 4 Mapped Object Parametermo0 OOOO The TPDO has a length of 8 bytes Example 3 sen gt E 1 Mapp
13. 16 Senece RE m 17 Exception TS SO A E D T TD ETT 20 CHAPTER 4 CAN AD ias 21 Woodward Page 3 83 Manual 37389 DTSC 200 Series Interfaces CHAPTER 5 CANOPEN cta 22 bela E 22 Server Data Objects SDO Communication ii 23 Process Data ODJECIS RTE 25 Setting the Transmit PDO Examples anen eaaeee eee nete eee e eee vene e eee eee nnns 26 NOTI 27 Using a CANopen Configuration Program 27 Settings for Connection with External DEViICESs ii 28 Expansion with One IKD 1 8 Additional External DI DO e eee nene e eee eee eee 29 Expansion with Two IKD 1 16 Additional External DI DO nenen eee ee eee eee eee eee 30 Expansion with the Phoenix terminal IL CAN BK ILB CO 24 16DI 16DO 16 DI DO 32 Description of the DTSC Parameters nane nnnnn e eee eee ee denon e tete e eee eee nenet eee nnn rni ee tete reve enen eee tee 34 ice Ac a 34 General CANopen Parameters ii 35 CANopen Receive PDO RPDO x X 1 2 eee 37 Combine Functions with Each Ober 37 CANopen Transmit PDO TPDO x x Tfo l eee e eee eee ete zeze zere eeeeti 38 FACO AN BU e 40 Recommendations of Woodward enne nennen anne nna nnn nnns 40 Device Combinations and Bus Load nennen nnns ede eee eee 40 APPENDIX A TELEGRAMS du red eeeeeksgaeh eege ENEE MEE dr 43 Transmission Telegram
14. 7 1234 23 HER Source Voltage 3 N EE 7 86 finemi ll LI LL 8 1123412520 Realenergy s Jan Jinemal LL 9 1234 2522 ReaciveEnergy o Z JUL Mvarh unsigned32 9 56 A A cde uu tl Woodward Page 53 83 Manual 37389 DTSC 200 Series Interfaces Data Protocol 4801 Source 2 Data Data Para Description Multiplier Units Data Type Byte Ge i unsigned16_ internal RE A NEN EE V signed32 1 A S iena __A gt signed32 on z s 160 Source 2 Power factor EE 3 1234 110 Source 2 Voltage 31___ 1_1v_ signed32__ 3 56 10134 unsigned 16 LUMINE aa Ea S H A Ja sisi 4 56 10166 unsigned 16 S asa a Load Current Phase B coi a spo 56 10167 unsigned16 internal o l6 11 234 Eet 0 001 SSC signed32 l6 156 10132 Digital input 1 is set Mask 8000h unsigned16 Page 54 83 Woodward Manual 37389 Data Para Byte meter DTSC 200 Series Description Multiplier Units ID Interfaces Data Type Digital input 3 is se input 31 1s set Digital input 7 is se input 7i is set AE O EE 5 6 10133 unsigned 16 internal internal AAA A ui jy sisi 56 10141 unsigned16 internal 9 1128341116 Source 2 Voltage 3 N Sa Valesi OS Y EE 56 10168 unsigned 16 Woodward Page 55 83 Manual 37389 DTSC 200 Series Interfaces Data Para
15. Bit 9 Flag 7 is TRUE Bit 8 Flag 8 is TRUE Bit 7 Internal Bit 6 Internal Bit 5 Internal Bit 4 Internal Bit 3 Internal Bit 2 Internal Bit 1 Internal Bit O Internal Page 74 83 Woodward Manual 37389 DTSC 200 Series Interfaces 3 Name Unit Data type Note 10146 47A2h Internal flags of the LogicsManager Bit field unsigned16 Bit 15 Internal Bit 14 Internal Bit 13 Horn output Bit 12 Internal Bit 11 Internal Bit 10 Internal Bit 9 Daily time set point 1 exceeded Bit 8 Daily time set point 2 exceeded Bit 7 Actual weekday is in group of active weekdays Bit 6 Actual day is active day Bit 5 Actual hour is active hour Bit 4 Actual minute is active minute Bit 3 Actual second is active second Bit 2 Internal Bit 1 Internal Bit 0 Internal 10302 Source 2 real power P 1 10 KW unsigned16 These variables 10303 Source 2 reactive power Q 1 10 kvar unsignedl6 are necessary to Source 2 povver factor cosphi cos1 100 unsignedl6 ensure downward 10306 compatibility with LeoPCl V2 1 xxx 10307 External discrete inputs with alarm class Bit filed unsigned 16 Bit 15 Discrete input DEx16 Bit 14 Discrete input DEx15 Bit 13 Discrete input DEx14 Bit 12 Discrete input DEx13
16. By entering 80000000h 2147483648 dec for the CAN ID the CAN identifiers can be disabled if they are not necessary i Client 2 Server configurable Master Slave Device number 1 1 Client gt Server COBID free 1 Server gt Client COBID free PLC 1 Client gt Server COBID free 1 Server gt Client COBID free Figure 5 1 CANopen interface overview NOTE If the DTSC 200 is configured to CAN Open Master Yes and one external terminal it sends configu ration messages to the default service data objects to the connected terminal as SDO client Page 24183 O Woodward Manual 37389 DTSC 200 Series Interfaces Process Data Objects PDO Process data objects are used to transmit real time data No one or several recipients are possible with this Process data objects may be sent cyclically or continuously other transmission types are not supported by the DTSC this is configured using the parameter Transmission Type The values 254 and 255 define an asynchronous transmission In case of the asynchronous transmission the PDOs are sent after a certain time This will be configured using the event timer The values 1 to 240 are used for a synchronous transmission The PDO will be sent as a response to a received SYNC message here If the value is configured to 1 the PDO will be sent for every received SYNC message 1f the value 1s configured to 2 the PDO will only be sent for every 2nd SYNC message
17. Description Multiplier Units Data Type Byte n dl EE internal internal a e signed32 10169 Latched Alarm Sl voltage imbalance Mask 8000h Bit unsignedl Latched NEI S2 voltage imbalance Mask 4000h Latched Alarm S1 Phase rotation mismatch Mask 2000h Latched Alarm S2 Phase rotation mismatch Mask 1000h internal internal lte Lond Reactive Power GFlond is powered by Sonne Je signed 11 5 6 110306 Load Power Factor if load is powered by Source2 signedl Page 56 83 Woodward Manual 37389 DTSC 200 Series Interfaces Remote Control Telegram Name Unit Data type Note E m 503 21F7h Control word 1 Bit field Unsigned16 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 Remote acknwledgement Bit 4 reset alarm messages rise of the pulse Transmit first a 0 then a 1 to acknowledge Bit 3 Must always be configured to 0 Bit 2 Must always be configured to 0 Bit 1 Not used Bit 0 Not used Bit 4 Remote acknowledgement reset alarm messages This bit controls the logical command variable 04 14 This command must be executed twice The first rise of the pulse resets the horn and the
18. FF Refer to Appendix A for the interface telegram Woodward Page 21 83 Manual 37389 DTSC 200 Series Interfaces Chapter 5 CANopen Introduction Extract from Controller Area Network Basics Protocols Chips and Applications By Prof Dr Ing K Etschberger ISBN 3 00 007376 0 also see IXXAT GmbH http www ixxat de The CANopen family profile defines a standardized Communication Object Application application for distributed industrial automation systems based SE ma SES on CAN as well as the communication standard CAN CAL CANopen is a standard of CAN in Automation CIA that after its release found a broad acceptance especially in Europe CANopen can be considered the leading standard for CAN based industrial and embedded system solutions Client SDOS Loqical addres sing scheme for I O Signals Rx PDOs accessing the Device communication function and device Tx PDOs parameters as The CANopen family profile is based on a Communication E Profile which specifies the basic communication mechanisms NMT SYNC and their description Emergency Time Stamp hes The most important device types such as digital and analog I O modules drives operating devices controllers programmable controls or encoders are described by Device Profiles The device profiles define the functionality parameters and access to process data corresponding to the types of standard devices These standardized profiles permit de
19. 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 5 11 shows exemplary request data for the device on the CANopen bus ES TransmitClient Remote Acknowledge opt File Edit View Function Options Trace Help je peja gt 7 T Gr cs LEE alo ec GES vr Wes pesen ber 2 byt BU Remote Acknowledge 2B Fr 21 01 1000 Tics Figure 5 11 CANopen request data for Node ID 2 Page 78 83 Woodward Manual 37389 DTSC 200 Series Interfaces Additional SDO Communication Channels It 1s also possible to allow several PLCs to 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 or 7F hex 1s used in the following example Press M until you return to the start screen Open the main menu by pressing the C softkey and navigate to Set up Comm interfaces by using the hd softkey Open the Set up Comm interfaces menu by using the amp softkey and navigate to Set up CAN interfaces by us ing the ka softkey Open the Set up CAN interfaces menu by using the amp softkey and navigate to CAN Op
20. are Device Id EN Number of Polls 3 Address MODBUS Point Type Valid Slave Responses 3 Length H 03 HOLDING REGISTER m 00000 gt For Help press Fi Polls 3 Resps 3 Figure 3 5 Modbus configuration example 3 O Woodward Page 19 83 Manual 37389 DTSC 200 Series Interfaces Exception Responses The DTSC Modbus interface has multiple exception responses to show that a request could not be executed Ex ception responses can be recognized if the response telegram contains the request function code with an offset of 128 0x80 hex Table 3 4 explains possible reasons for an exception response that occurred DTSC Modbus Exception Responses 01 ILLEGAL FUNCTION e The sent request function code is not supported by the DTSC Modbus interface 02 ILLEGAL ADDRESS Permission to read write the parameter is denied The amount of requested registers is wrong to read write this reg isters 03 ILLEGAL DATA VALUE The data value exceeds the min and max limitations of the pa rameter upon a write request There 1s no parameter on the requested address Table 3 4 Modbus exception responses Page 20 83 Woodward Manual 37389 DTSC 200 Series Interfaces Chapter 4 CAN CAL LeoPC1 DTSC 200 Baudrate 125kBd Transmit ID 831 Protocol type 3 Expand block 1 YES Baudrate 9600Bd Device Gateway RS 232 CAN Protocol LeoPC1 Baudrate 125kBd Figure 4 1 CAN CAL interf
21. arr s variabile b n aaa 43 D la Protocol 400 A e o In 43 Data Protocol 4800 Source 1 Data 52 Data Protocol 4801 Source 2 Data 54 Klee Aa nv 57 APPENDIX B CANOPEN A e mE RF CE EMI E ee eee e 58 Description of the Common Data TYPES i 58 Structure of the PDO COB ID Entry UNGIOGNETOZ eee ee ee eee vene eee eseve ee eeesi 58 Description of the Object Parameter eee nena ee eee eee ee eee nennen eee eee eee eee ee tee eee eee eee eee 59 Data Format of Different Functions i 66 Receiving MESSAGES rina 66 Definition of Protocol Descriptions i 67 En o 67 SIONSA EE 68 Transmission TOIGGT AT Micra m 69 CANopen Mapping Parameter 71 APPENDIX C APPLICATION EXAMPLES ccccsecseccecceccuecucceecuscuecuseuscuecuecsecnsnueceeeseceeesessesesneess 76 Remote CON O ke aun 76 Configuration of the LogicsManager Functions nan enen den anita eee eee tere eee eee eee eee eee reve nese tee 76 Remote Control Telegram 77 Remote A A 77 Remote Acknovvledgemen ti nana nenen ne eee eee eee teke eee ee eee eee e nenne e eee den ete eee eee eee 77 Remote Control via MODUS teicasscsincsascccesaenSncdanscosusedansecdenaceaus see aiar 80 Sending a Data Protocol via TPDO eee nenet eee ee eee nn eee eee eee eee nete tete eee 82 Gyclicaly Sending Or D ii RETENTO TONO TE TET 82 90 0 0 82 Page 4 83 Woodward Manual 37389 DTS
22. high speed exchange of small process data portions through Process Data Objects PDO as well as the ac cess to entries in the object dictionary through Service Data Objects SDO The latter ones are primarily used for the transmission of parameters during the device configuration as well as in general for the transmission of larger data portions Process data object transmissions are generally event triggered cyclic or requested as broad cast objects without the additional protocol overhead A PDO can be used for the transmission of a maximum of 8 data bytes In connection with a synchronization message the transmission as well as the acceptance of PDOs can be synchronized through the entire network Synchronous PDOs The assignment of application objects to a PDO Transmission Object is adjustable through a structure description PDO Mapping which is stored in the object dictionary thus allowing the adjustment of a device to the corresponding application requirements The transmission of SDOs is performed as a confirmed data transfer with two CAN objects in form of a peer to peer connection between two network nodes The addressing of the corresponding object dictionary entries 1s ac complished by specifying the index and the sub index of the entry Transmitted messages can be unlimited in length The transmission of SDO messages involves an additional protocol overhead Standardized event triggered Emergency Messages of high priorit
23. if not avoided could result in damage to equipment NOTE Provides other helpful information that does not fall under the warning or caution categories A A e 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 O Woodward All Rights Reserved Page 2 83 Woodward Manual 37389 DTSC 200 Series Interfaces Revision History EH Rev NEW 07 12 12 Contents AAA CHAPTER 1 GENERAL INFORMATION 1 1 uu unioni esse stisi tete S tE SEE SEP SEE SEP SEE SEPSE SEE SEPSE SEE ESE LESS LESS 6 Related DOCUMENTS i eseje ee me OO ODE mm 6 iO eo PA 7 Modbus Half Full Duplex Application sese enne 8 eu My ee aa 9 CHAPTER 2 DATA TELEGRAMS nana ann ana sense sie i nates te Ste SEE SEP SEE SEP SEP SEE SEE SEP nea SEPSE SEPSE ESE SS ESSE REN 10 Ae AG GA MONL ONTI ENTRE Tm 10 ici E AA E o e E OE E 10 alo AA PP e OOO n 10 CANI OA e eae e E A O o 10 cn o E o 10 ass ele dE 11 e Eo 11 SAA 12 ce o lili ju o o 12 CHAPTER 3 SERIAL INTERFACE ocooccocconooncononnronco nono ESSE SEP SEE SEE SEP SEE SEE SEE SEPSE SEPSE SEPSE ESSE SS tE SS ESSE 13 Suc pete 13 MODES TT SIUS E 14 General MOM aaa 14 COMU Ee 14 Modbus Addressing and Data Model 15 o EE
24. no standard profile Object 1001h Error Register This object is an error register for the participant Object description io o RR 1001h IN AT corra Error Register Object code VAR Data type UNSIGNEDS Category obligatory Entry description Access Read Only PDO figure no Value range UNSIGNED8 Default value no Note This object is always value 0 DTSC 200 Series Interfaces O Woodward Page 59 83 Manual 37389 DTSC 200 Series Interfaces Object 1005h COB ID SYNC Message The index 1005h defines the COB ID of the synchronization object SYNC Description of the SYNC COB ID entry UNSIGNED32 28 11 Ip IK Jor In falo llebit Identifier 29 Bit ID 29 bit Identifier Description of the SYNC COB ID entry 30 Device does not generate SYNC message O Z o o S O __ LDevice generates SYNC message SSS O 29 i AL bit ID CAN 20A o ot 29 bitID CAN 2 0B 2811 ON Ifbit 29 0 and if bit 29 1 bits 28 11 of 29 bit S YNC COB ID 10 0 LSB XX Bits10 0ofSYNC COB ID Object description TOK A nat s 1005h Nalin COB ID SYNC Object code VAR Data Ly risit banese UNSIGNED32 Entry description ACCESS ds ees Read Write PDO figure no Value range UNSIGNED32 Default value 80 hex Note Bit 31 29 are ignored Writing these bits does not cause fau
25. with CANopen specification object 1800 for TPDO 1 1801 for TPDO 2 1802 for TPDO 3 and 1803 for TPDO 4 subindex 5 CAN bus 1 Transmit PDO 1 Number of mapped objects 0 to 4 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 LAOI for TPDO 2 1402 for TPDO 3 and 1A03 for TPDO 4 subindex 0 Page 38 83 O Woodward Manual 37389 DE 9605 9615 9625 9635 NOTE 1 Mapped Object 1 Mapped Objekt 2 Mapped Object 2 Mapped Objekt 3 Mapped Object 3 Mapped Objekt 4 Mapped Object 4 Mapped Objekt DTSC 200 Series Interfaces CAN bus 1 Transmit PDO 1 1 mapped object 0 to 65535 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 1s determined automatically Complies with CANopen specification object 1A00 for TPDO 1 1A01 for TPDO 2 1402 for TPDO 3 and 1A03 for TPDO 4 subindex 1 CAN bus 1 Transmit PDO 1 2 mapped object 0 to 65535 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 1s determined automatically Complies with CANopen specification obje
26. 03 Bit 1 Discrete input DEx02 Bit O Discrete input DExOI Page 72 83 Woodward Manual 37389 DTSC 200 Series Interfaces 3 Name Unit Data type Note 10106 Discrete inputs status Bit field unsigned 16 Bit 15 Discrete input D1 Bit 14 Discrete input D2 Bit 13 Discrete input D3 Bit 12 Discrete input D4 Bit 11 Discrete input D5 Bit 10 Discrete input D6 Bit 9 Discrete input D7 Bit 8 Discrete input D8 Bit 7 Discrete input D9 Bit 6 Discrete input D10 Bit 5 Discrete input D11 Bit 4 Discrete input D12 Bit 3 Internal Bit 2 Internal Bit 1 Internal Bit 0 Internal 10107 Relay outputs status Bit field unsigned 16 Bit 15 Relay output ROI Bit 14 Relay output R02 Bit 13 Relay output R03 Bit 12 Relay output R04 Bit 11 Relay output R05 Bit 10 Relay output R06 Bit 9 Relay output R07 Bit 8 Relay output R08 Bit 7 Relay output R09 Bit 6 Internal Bit 5 Internal Bit 4 Internal Bit 3 Internal Bit 2 Internal Bit 1 Internal Bit 0 Internal 10110 477Eh Battery voltage 1 10 V unsigned16 10134 4796h Generator watchdog 1 Bit field unsigned16 Bit 15 Internal Bit 14 Intern
27. 3 Name Unit Data type Note 8002 3F42h Outputs of the 2 IKDI Bit field unsigned16 Bit 15 Relay output REx16 Bit 14 Relay output REx15 Bit 13 Relay output REx14 Bit12 Relay output REx13 Bit11 Relay output REx12 Bit10 Relay output REx11 Bit 9 Relay output REx10 Bit 8 Relay output REx09 Bit 7 always 0 Bit 6 always 0 Bit 5 always 0 Bit 4 always O Bit 3 always O Bit 2 always 0 Bit 1 always 0 Bit 0 always 1 8003 3F43h External relay outputs status Bit field unsigned16 Bit 15 Relay output REx16 Bit14 Relay output REx15 Bit 13 Relay output REx14 Bit12 Relay output REx13 Bit11 Relay output REx12 Bit10 Relay output REx11 Bit 9 Relay output REx10 Bit 8 Relay output REx09 Bit 7 Relay output REx08 Bit 6 Relay output REx07 Bit 5 Relay output REx06 Bit 4 Relay output REx05 Bit 3 Relay output REx04 Bit 2 Relay output REx03 Bit 1 Relay output REx02 Bit 0 Relay output REx01 013 3F43h External discrete inputs status Bit field unsigned16 Bit 15 Discrete input DEx16 Bit 14 Discrete input DEx15 Bit 13 Discrete input DEx14 Bit12 Discrete input DEx13 Bit 11 Discrete input DEx12 Bit 10 Discrete input DEx1 Bit 9 Discrete input DEx10 Bit 8 Discrete input DEx09 Bit 7 Discrete input DEx08 Bit 6 Discrete input DEx07 Bit 5 Discrete input DEx06 Bit 4 Discrete input DEx05 Bit 3 Discrete input DEx04 Bit 2 Discrete input DEx
28. 37389 AN WOODWARD DTSC 200 Series Interfaces DTSC 200 Ww WOODWARD Interface Description Software Version 1 0xxx Manual 37389 Manual 37389 DTSC 200 Series Interfaces WARNING Read this entire manual and all other publications pertaining to the work to be performed before install ing 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 overtempera ture 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 gov ernor 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 cer
29. 50051 17 internal bel ar il d n dea 6 Load Real Power If Load is bri by signed32 Source bri 450055 450054 10141 unsigned16 450056 450055 18 34 lintema Rp 450058 450057 10306 Load Power Factor If Load is powered by AA signed16 2 jintmal 50080 4s0055 Lis 136 i o AS EEN AEN 12 intemal inten U E d 450067 450066 12 10140 unsigned16 inemal r4s0070 409 jes 12 intemal funs ned 16 450071 450070 23 34 internal ll 450072 450071 23 56 Jinemal ll 450073 450072 24 12 pinte II 450074 450073 24 34 5610308 inemal LL Page 46 83 Woodward Manual 37389 DTSC 200 Series Interfaces Modbus Modbus Data Para Description Multiplier Units Data Type Byte SE Modicon Start 450076 1450075 8003 External discrete output 16 Rex16 Mask 8000h unsigned16 eso e SL a AED External discrete output 15 Rex15 Mask 4000h LE terna disen output 14 RIA Mask 20001 Bit pT Extmaldisreteoutput 13 Rex13 Mask 1000h_ Bit__ ss External discrete output 12 Rex12 Mask 0800h Bit ss External discrete output 11 Rex1 Mask 0400h Bit ss yoo External discrete output 10 Rex10 Mask 0200h Bit yo External discrete output 9 Rex9 Mask 0100h Bit Extemaldisreteoutput8 Rex8 Mask 0080h Bit yy External discrete ou
30. C 200 Series Interfaces Illustrations And Tables SSS Illustrations Elika 7 Figure 1 2 Interface overview serial interface Modbus full duplex aaa e aaa eee eee eee 8 Figure 1 3 Interface overview serial interface Modbus half duplex cccccccccccccececceecececeeeeeeeeeeeeeeeeees 8 Heure 124 AlN IDWS TOP O08 Y amarse iia e adi acanto si 9 Pieure l 3 Ime Ce E ENEE H Figure 2 1 Data telegrams remote control via CAN 12 ure s Sera ee A E 13 Figure 3 2 Modbus visualization configurations nennen enne eene eene eene eene esee sese ee eee 16 Figure 3 3 Modbus configuration example LL see resa st e raa aea ona etapa dee v 18 Figure 3 4 Modbus configuration example 7 18 Figure 3 5 Modbus configuration example 3 19 Figure 4 1 CAN CAL interface 9 OY CL TE 21 Figure 5 1 CANopen interface OVELVIEW mencionado tese etat eon cid eo ee noe ead eoe alea eon coda eod nda Hon cud oda eu nude 24 Figure 5 2 CANopen interface CANopen configuration software nennen nennen 27 Figur 5 5 CANopen interface external dEVIC S iia ia ese e saa Ra ar ES 28 Figure 5 4 CANopen Schnittstelle Einstellungen f r externe Ger te 29 Figure 5 5 CANopen interface expansion with two IKD 1 nnne enne 30 Figure 5 6 CANopen interface expansion with Phoenix terminal aaa eee eee 32 Bisufe9 7 Display screen Ext acknoWwled RE arad
31. CL2 9026 5 4th Client gt Server COB ID rx A 4 Client gt Server COB ID rx CL2 9028 4th Server gt Client COB ID tx 4 Server gt Client COB ID tx DE EN CL2 9030 Sth Client gt Server COB ID rx A 5 Client gt Server COB ID rx CL2 9032 amp 5th Server gt Client COB ID tx A 5 Server gt Client COB ID tx CL2 9034 NOTE DTSC 200 Series Interfaces CAN bus Client gt Server COB ID rx 1 to FFFFFFFF In a multi master application each Master needs its own identifier Node ID from the unit in order to send remote signals i e acknowledge to the unit The addi tional SDO channel will be made available by configuring this Node ID to a value different than zero This 1s the additional CAN ID for the PLC CAN bus Server gt Client COB ID tx 1 to FFFFFFFF In a multi master application each Master needs its own identifier Node ID from the unit in order to receive remote signals i e acknowledge 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 unit CAN bus Client gt Server COB ID rx 1 to FFFFFFFF In a multi master application each Master needs its own identifier Node ID from the unit in order to send remote signals i e acknowledge to the unit The addi tional SDO channel will be made available by configuring this Node ID to a value different than zero This 1s the addition
32. Cyclical sending of data reply Page 82 83 O Woodward 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 AN WOODWARD Woodward GmbH Handwerkstrasse 29 70565 Stuttgart Germany Phone 49 0 711 789 54 0 e Fax 49 0 711 789 54 100 stgt info 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 2007 12 Stuttgart
33. DTSC200 1 0x1 CANopen Object Dictionary Browser File Edit Options Help p d e 2093 Battery overvoltage 2 Delayed by e Subli Denotat Actual V DataT vp Low Lim High Lim amp ccT up Default PDO Me ZE SE een LS o Number 0401 Unsigne o Do N e attery overvoltage elay OD e OAL Battery undervoltage 1 Monitoring MM value 1 E i i xz DAD Battery undervoltage 1 Alarm class P 2DAE Battery undervoltage 1 Self ackno rz 2DAF Battery undervoltage 1 Delayed by xz DB0 Battery undervoltage 1 Limit 0 081 Battery undervoltage 1 Delay 0 SDB Battery undervoltage Monitoring UF 2DB3 Battery undervoltage 2 Alarm class x 2064 Batter undervoltage 2 Self acknm o x SDBS Battery undervoltage 2 Delayed by x DEE Battery undervoltage 2 Limit xz SDB Battery undervoltage 2 Delay x FSC Voltage asymmetry Monitoring rz F30 Voltage asymmetry Alarm class UE F3E Voltage asymmetry Self acknowledi mm x 2F3F Voltage asymmetry Limit x 2F40 Voltage asymmetry Delay dec 1 xz 2F41 Voltage asymmetry Delayed by engi hex O01 2F44 Voltage asymmetry Delay bin 00000007 mere m G Il gt 2eDAC Battery undervoltage 1 Monitoring 1 Figure 5 2 CANopen interface CANopen configuration software The DTSC parameters may be changed after loading the eds file The values are only overwritten by the DTSC if the correct password has been entered prior to attempting to make any changes other
34. Interfaces i e e istor resistor e SS Pod da e MX P d resisto K e e Y e e e Bus ls e Bus line Bus Ze e d Bus line Ya Bus participant Bus participant Bus participant Bus participant Bus participant Bus participant Bus participant Figure 1 4 CAN bus topology Characteristics of the CAN interface used by Woodward e Standard Compatible with ISO 11898 e Electrically isolated Isolation voltage 1 500 Vpc NOTE Please note that the CAN bus must be terminated with an impedance which corresponds to the wave impedance of the cable e g 120 Ohm 14 VV The CAN bus is terminated between CAN H and CAN L Node 1 Node 30 120 Ohm 120 Ohm Figure 1 5 Interface The CAN bus loop Woodward Page 9 83 Manual 37389 DTSC 200 Series Interfaces Chapter 2 Data Telegrams ER Interface Monitoring It is possible to monitor the CAN interface for received data of an external I O board Refer to the configuration manual for more information about this monitoring function Transmit Telegram The transmit telegram provides all measuring and status data of the DTSC The data have different addresses and will be transmitted in the respective format depending on the selected interface Modbus Data transmission in Modbus format is performed in the order of the transmit telegram refer to Appendix A Transmission Telegram on page 43 The data ad
35. KD 8DIDO 4 PDO every 20ms 1 PDO every 20 ms for DO visualization 4 PDO every 20ms PLC with 1 PDO every 20ms for DO visualization 1 PDO every 20ms Sometimes the Phoenix CO 16DIDO fails with this baud rate 250kBaud and above The maximum load of the CAN bus cannot be reached with combinations of DTSC and external terminals A maximum baud rate of 500kBaud may be configured at the IKD Page 42 83 Woodward Manual 37389 DTSC 200 Series Interfaces Appendix A Telegrams Transmission Telegram Data Protocol 4700 Modbus Modbus Data Para Description Multiplier Units Data Type Byte See Modicon Start asooo 450000 jo 12 3190 Protocol ID always 4900 1 Punsigned 6 450002 450001 O 42610 JSource 2 Voltage12 101 JN signed32 450010 450009 3 112 1160 Source 2 power factor Cd OTs Lsienedig 450011 450010 3 3456113 Souree 2 Voltage 2N__ 0 1_ V_ signed32__ 450013 450012 1 2 10166 unsigned 16 Actual du Transfer switch mechanical Mask 0800h pem 450014 450013 f4 3456 110 Source 2 Voltage 31 EE 450016 450015 12 10167 unsigned 16 pee failure 450017 450016 5 3456 116 Source 2 Voltage 3 N O M SEP 450019 450018 6 12 10110 Battery voltage 01 JN Tsienedi6 450020 450019 6 3 5556 118 Source 1 Voltage12 101 JN signed32 450022 450021 10168 Actual Alarm S1 voltage imbalance Mask 8000h unsigned16
36. SC 200 Series Interfaces Setting of the receive PDO 2 COB ID 202h 514 Dec CAN ID on which the data are received 2 IKD The data received on the COB ID were assigned to the external DI 9 to DI 16 device default value ext device 1 default value Settings of transmit PDO e g PDO 2 The PDO is sent circular PDO is sent circular So TT objects HE NE 4 Mapped Object Parameter no 8000 s O Settings of DIs on IKD 1 2 Node ID ci That the entries of CAN IDs are accepted data for operation Settings on IKD 1 2 Node ID O So that the entries of the CAN IDs are taken over CAN ID transmit 202h 514 Dec The DTSC receives on this ID ting data Settings for DIS on IKD 1 2 Physical state Only the physical state of the inputs is transmitted The settings under idle current tripping delay revert delay enabling self resetting and acknowl edgeinput are without effect These settings have to be selected for devices which include these parameters e g the DTSC 200 Check of the settings Actuate an external DO via the LogicsManager and check whether the respective relay at the IKD operates Scroll the display screens to view the ext discrete inputs 9 to 16 A set of discrete inputs will be shown that cor respond to the IKD Use the FAQ CAN Bus chapter on page 40 to troubleshoot any CAN bus faults Woodward Page 31 83 Manual 37389 DTSC 200 Series Interfaces Expansion
37. ace overview NOTE The transmission rate is configurable default 125 kBaud If a GW 4 is used for data transfer a trans mission rate of 125 kBaud must be configured The CAN ID on which the DTSC is transmitting is calculated as follows CAN ID d 800 Item number or H 320 item number The item number is an adjustable parameter in the DTSC which directly influences the CAN ID that the unit sends the visualization message A visualization message which is send out of an DTSC has got 8 Byte and is built as follows H DD MUX Data word 1 Data word 1 Data word2 Data word 2 Data word 3 Data word 3 number High Byte Low Byte High Byte Low Byte High Byte Low Byte The byte 0 is always used to show the hexadecimal value H DD in a visualization message This defines the mes sage as a visualization message As the complete transmission telegram of the DTSC includes more than three words byte 1 sends additionally a MUX number starting with 0 Therefore it is theoretically possible to send 256 x 3 768 words via the CAN ID The whole telegram is built up as follows line 1 MUX number 0 word 1 line 2 MUX number 0 word 2 line 3 MUX number 0 word 3 line 4 MUX number 1 word 1 line 5 MUX number 1 word 2 line n MUX number n 1 3 word 1 line n 1 MUX number n 1 2 word 2 line n 2 MUX number n 1 1 word 3 n depends on the total length of the unit special telegram and can not be larger than H
38. al Bit 13 Internal Bit 12 Internal Bit 11 Internal Bit 10 Internal Bit 9 Internal Bit 8 Internal Bit 7 Load overcurrent limit 1 Time overcurrent Bit 6 Load overcurrent limit 2 Time overcurrent Bit 5 Load overcurrent limit 3 Time overcurrent Bit 4 Internal Rev red load Bit 3 Internal Rev red load Bit 2 Load overload limit 1 Bit 1 Load overload limit 2 Bit 0 Internal Woodward Page 73 83 Manual 37389 DTSC 200 Series Interfaces E e Name Unit Data type Note 2 10136 4798h Latched alarm bits analog input Bit field unsigned16 Bit 15 Internal Bit 14 Internal Bit 13 Internal Bit 12 Internal Bit 11 Internal Bit 10 Internal Bit 9 Internal Bit 8 Internal Bit 7 Internal Bit 6 Internal Bit 5 Internal Bit 4 Internal Bit 3 Alarm bit monitoring battery voltage overvoltage threshold 2 Bit 2 Alarm bit monitoring battery voltage undervoltage threshold 2 Bit 1 Alarm bit monitoring battery voltage overvoltage threshold 1 Bit O Alarm bit monitoring battery voltage undervoltage threshold 1 10140 Flag of the LogicsManager Bit field unsigned 16 Bit 15 Flag lis TRUE Bit 14 Flag 2 1s TRUE Bit 13 Flag 3 is TRUE Bit 12 Flag 4is TRUE Bit 11 Flag 5 is TRUE Bit 10 Flag 6is TRUE
39. al CAN ID for the PLC CAN bus Server gt Client COB ID tx 1 to FFFFFFFF In a multi master application each Master needs its own identifier Node ID from the unit in order to receive remote signals i e acknowledge 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 unit CAN bus Client gt Server COB ID rx 1 to FFFFFFFF In a multi master application each Master needs its own identifier Node ID from the unit in order to send remote signals i e acknowledge to the unit The addi tional SDO channel will be made available by configuring this Node ID to a value different than zero This 1s the additional CAN ID for the PLC CAN bus Server gt Client COB ID tx 1 to FFFFFFFF In a multi master application each Master needs its own identifier Node ID from the unit in order to receive remote signals i e acknowledge 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 unit CAN bus Client gt Server COB ID rx 1 to FFFFFFFF In a multi master application each Master needs its own identifier Node ID from the unit in order to send remote signals i e acknowledge to the unit The addi tional SDO channel will be made available by configuring this Node ID to a value different than zero This 1s the additional CAN ID for the PLC
40. ct 1A00 for TPDO 1 1A01 for TPDO 2 1402 for TPDO 3 and 1A03 for TPDO 4 subindex 2 CAN bus 1 Transmit PDO 1 3 mapped object 0 to 65535 This parameter contains the information about the mapped application variables These entries describe the PDO contents by their index The sub index is alvvays 1 The length is determined automatically Complies with CANopen specification object 1A00 for TPDO 1 1A01 for TPDO 2 1402 for TPDO 3 and 1A03 for TPDO 4 subindex 3 CAN bus 1 Transmit PDO 1 4 mapped object 0 to 65535 This parameter contains the information about the mapped application variables These entries describe the PDO contents by their index The sub index is alvvays 1 The length is determined automatically Complies with CANopen specification object 1A00 for TPDO 1 1A01 for TPDO 2 1402 for TPDO 5 and 1A03 for TPDO 4 subindex 4 CANopen allovvs to send 8 byte of data vvith each Transmit PDO These may be defined separately if no pre defined data protocol is used All data protocol parameters vvith a parameter ID may be sent as an object vvith a CANopen Transmit PDO In this case the data length will be taken from the data byte column refer to the Data Protocols section in the Interface Manual 37389 1 2 UNSIGNED16 or SIGNED16 3 4 UNSIGNED16 or SIGNED16 5 6 UNSIGNED16 or SIGNED16 1 2 3 4 UNSIGNED32 or SIGNED32 3 4 5 6 UNSIGNED32 or SIGNED32 etc The object ID is identical with the parameter ID when c
41. dresses may be taken from the respective column of the transmit telegram CAN CAL The DTSC sends its data via cyclic CAN messages If a GW 4 is used the baud rate must be configured to 125 kBaud NOTE Instead of using a GW 4 a CAN to USB or RS 232 converter may be used CANopen Using the mapped objects which are described in detail starting on page 25 enables you to send data by setting the object ID 2C76h on the basis of the CANopen protocol This document contains tables of further mapped objects which may be configured Refer to Appendix A Transmission Telegram on page 43 NOTE When using the mapped objects listed in the appendix instead of the complete transmit telegram the refresh rate of the messages may be reduced Page 10 83 Woodward Manual 37389 DTSC 200 Series Interfaces Receive Telegram The receive telegram enables to acknowledge alarm messages which are no longer active via remote control In order to execute the desired command a rise of the pulse of the respective signal from Low to High is re quired An acknowledgement command must be sent twice The first rise of the pulse resets the horn The second rise of the pulse acknowledges the unit 1f the fault 1s not present anymore NOTE Please note that the respective remote control parameters must be configured in the LogicsManager of the unit Refer to the application manual 37388 for more detailed information about this Modbus I
42. e transmitted as follows Octet Number 1 2 4 5 6 7 8 SIGNED8 briobo Il LIT SIGNEDI6 bytobo bistobs SIGNED bytoby bistobg bstobig SIGNED32 brtobo bistobg bstobig byitoby o o y SIGNED40 brtobo bistobs bstobig bs toby bstobo y SIGNED48 brtobo bistobs bstobig bytobo bstoby bgtobig SIGNEDS6 brtobo bistobs bastobig bytobo bstoby bytobso bsstobag Page 68 83 Woodward Manual 37389 DTSC 200 Series Interfaces Transmission Telegram NOTE When using the listed Mapped Objects instead of the complete transmission telegram the refresh rate of the individual messages may be reduced Data Protocol Parameter No 3190 Object 2C76h In this protocol the LeoPC display messages were sent Parameter 3190 Object 2C76h pf Parameter Now Internal pa Parameter No 12 emd Parameter No 1O134 fetter os Parameter No 135 Intema Parameter No 10141 e y Intema Parameter No 10306 ft Parameter No 1O202 y Lem 27 Parameter No 10837 j emd o 4 6 8 9 27 Woodward Page 69 83 Manual 37389 DTSC 200 Series Interfaces Data Protocol Parameter No 15603 Object 5CF3h Source 1 Values If the object SCF3h is read out the protocol known value is re
43. eceiver 2 PDOs every 100 ms only receiver 2 PDOs every 150 ms 1 PDO every 150 ms 2 PDOs every 150 ms only receiver 1 PDO every 160 ms If the IKD sends only every 160ms the respective discrete inputs have a jitter of 160ms it is recommended to re ceive two messages therefore the delay of the ext discrete inputs should also be configured greater than 160ms Page 40 83 Woodward Manual 37389 DTSC 200 Series Interfaces 50 kBaud 1 PDO every 20ms only receiver 1 PDO every 20ms for BK 16DIDO 1 PDO every 200ms for PLC 1 PDO every 20ms 1 PDO every 20 ms Not existing for PLC e g DOs if the DTSC is the 1 PDO every 150ms NMT master set for PLC e g visu data Time re init ext de vices to O off 1 PDO every 20ms only receiver 1 PDO every 20ms for IKD 1 PDO every 200ms for PLC 2 PDO every 40ms 1 PDO every 40ms 1 PDO every 40ms for IKD PLC may also be the 1 PDO every 200ms 2 IKD for PLC Sometimes the Phoenix CO 16DIDO fails with this baud rate 100 kBaud 1 PDO every 20ms 1 PDO every 20 ms for PLC e g DOs 1 PDO every 20ms for PLC e g visu data 2 PDO every 20ms 1 PDO every 20ms 1 PDO every 20ms for PLC e g DOs may also be the 2 IKD 1 PDO every 40ms for PLC e g visu data The Phoenix terminals do not support this baud rate Woodward Page 41 83 Manual 37389 DTSC 200 Series Interfaces 125 kBaud DTSC PLC Phoenix BK 16 DIDO I
44. ed Object Parameter no 108 unsigned32 gt 4byte 4 Mapped Object Parametermo0 OOOO The TPDO has a length of 12 bytes as only 8 bytes are admissible an idle TPDO is sent Configuration of a SYNC message Number of bytes Number of mapped objects Parameter no 0 1 Mapped Object Parameter no 0 O oo ed 4 Mapped Object Parameter no 0 o O The TPDO has a length of 0 bytes If the COP ID is configured accordingly for example 80h 128dez it is working like a SYNC message Thereby the DTSC has the possibility to send a SYNC message to the attached devices to arrange a reaction with a PDO however the time of the transmission is not appraised Page 26 83 Woodward Manual 37389 DTSC 200 Series Interfaces SYNC Message The SYNC message 1s a CAN message without data The CAN ID on which the DTSC sends appropriately con figured PDOs is configured with the parameter COB ID SYNC Message Using a CANopen Configuration Program If the DTSC is used as a single unit the default settings provide useful operation possibilities already If the DTSC is used together with other CANopen devices a detailed configuration will be necessary An eds file is enclosed with the unit for this purpose An example of this file being used with the CANopen Configuration Studio of IX XAT is shown in the following Please refer to IX XAT for a more detailed explanation about this tool 5
45. ed internally 503 decimal 1F7 hexadecimal 1F7 2000 hexadecimal 21F7 Woodward Page 77 83 Manual 37389 DTSC 200 Series Interfaces 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 5 9 shows exemplary request data for the device on the CANopen bus E TransmitClient Remote Acknowledge opt File Edit View Function Options Trace Help T re LES C PrE n n Se Dr ene Bee LLL 2 byt so Remote Acknowledge 0 2B Fr 21 01 1000 Tics El Figure 5 9 CANopen request data for Node ID 1 Node ID not standard value If the Node ID of the device is intended to be different from the standard value the Device number parameter must be configured accordingly Node ID 2 is used in the following example Press t until you return to the start screen Open the main menu by pressing the C softkey and M to Set up Comm interfaces by using the M softkey Open the Set up Comm interfaces menu by using the amp softkey and navigate to Device number by using the softkey and enter the Device number screen by pressing the amp softkey Figure 5 10 Display screen configure device number Configure 002 by using the M and M softkeys and confirm your selection by pressing the amp softkey With this setting the Node ID of the CAN interface is set to 002
46. ed multiple times CANopen Transmit PDO TPDO x x 1 to 4 4 TPDOs are available EN COB ID A COB ID CL2 9600 9610 9620 9630 EN Transmission type DE Transmission type 9602 9612 9622 9632 EN Event timer Event timer DE 9604 9614 9624 9634 6 Number of Mapped Objects 5 Anzahl der Mapped Objekte CL2 CAN bus 1 Transmit PDO 1 COB ID 1 to FFFFFFFF 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 CAN bus 1 Transmit PDO 1 Transmission type 0 to 255 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 CAN bus 1 Transmit PDO 1 Event timer 0 to 65000 ms 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
47. en interface by using the M softkey Open the CAN Open interfaces menu by using the amp softkey and navigate to Additional Server SDOs by using the ka softkey Enter the Additional S SDO screen by pressing the amp soft key Navigate to 2nd Client gt Server COB ID rx by using the M softkey and press the amp softkey to edit this pa rameter Configure 0000067F by using the M and M softkeys and confirm your entry by pressing the amp softkey Navigate to 2nd Server gt Client COB ID tx by using the M softkey and press the amp softkey to edit this pa rameter Configure 000005FF by using the M and W softkeys and confirm your entry by pressing the amp softkey Figure 5 12 Display screen configure Server SDOs NOTE Be sure to remove the leading 8 from the COB IDs to enable them For example change the standard value of 2nd Client Server COB ID rx which is 80000601 to 0000067F In this example an additional SDO communication channel is configured to 127 decimal or 7F hex 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 Node ID internally to perform the desired control the reply from the DTSC is sent on CAN ID 580 hex Node ID Receive CAN ID 67F hex 600 hex 7F hex Transmit CAN ID 5FF hex 580 hex 7F hex
48. eral Information DTSC 200 Series Interfaces Modbus RTU Slave Modbus is a serial communications protocol published by Modicon in 1979 for use with 1ts 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 DTSC supports a Modbus RTU Slave module This means that a Master node needs to poll the DTSC 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 1s 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 Configuration a Baudrate A Baudrate CL2 3170 Parity A Parity CL2 3171 Stop bits A Stop Bits CL2 3172 a Full halfduplex mode 8 Voll Halbduplex Modus Serial interface 2 Baud rate 2 4 4 8 9 6 14 4 19 2 38 4 56 115 kBaud
49. ers as values The range is between 0 and 2n 1 The data is shown by the bit sequence of length n Bit sequence b boto by shows the value UNSIGNEDn b b xn by 21 4922 NOTE Please note that the bit sequence starts on the left vvith the least significant byte Example Value 266 10Ah of type UNSIGNED16 is transmitted on the bus in two octets first OAh and then 01h The following UNSIGNED data types are transmitted as follows UUNIGNEDE to UNSIGNEDIG byob onos ST TT UNSIGNED24 by to bu b amp tob bebe ST UNSIGNED32 b toby bistobg bstobig Lbuiob J ll UNSIGNED40 b toby bistobg bstobig bs tob bstobo y UNSIGNED48 by toby bistobg bstobig bajtobzs bstoby bgtobi UNSIGNEDS6 b tobo bistobg bastobig bytobo bstoby byrtobso bsstoba O Woodward Page 67 83 Manual 37389 DTSC 200 Series Interfaces Signed Integer SIGNED type data has integers as values The range is between 0 and 2 1 The data is shown by the bit se quence of length n Bit sequence b boto by shows the value SIGNEDn b b 2 2 7 b 21 4 pp20 if b 1 0 and with two s complement SIGNEDn b SIGNEDn b 1 if bn 1 1 NOTE Please note that the bit sequence starts on the left with the least significant byte Example The value 266 FEF6h of type SIGNED16 is transmitted in two octets first F6h and then FEh The following SIGNED data types ar
50. erver rx Sub index 2 contains the COB ID Server gt Client tx Reading out and changing these objects is performed using an SDO This data exchange will be implemented using at least two CAN telegrams where each on is using an own CAN identifier The CAN identifiers of the default service data object are fixed in the object 1200h and are changed using the Node ID The values are CAN identifier for the reception Client gt Server Node ID 1536 600h CAN identifier for the reply Server gt Client Node ID 1408 580h Woodward Page 23 83 Manual 37389 DTSC 200 Series Interfaces Some applications require that several SDO clients access one SDO server To ensure a proper communication the SDO server must provide several service data objects These are described in the objects 1201h to 127Fh The DTSC provides five additional service data objects These may be configured under the point Additional S SDO 2 to 5 Client gt Server COP ID tx CAN IDs on which SDO requests are received 2 to 5 Server gt Client COP ID rx CAN IDs on which SDO replies are sent If a unit 1s not only intended to work as a server but also as a client 1t requires client service data objects These may be configured under the point Additional C SDO client SDO 1 Client gt Server COP ID rx CAN IDs on which SDO requests are sent 1 Server gt Client COP ID tx CAN IDs on which SDO replies are received
51. fer to Table 3 3 for more information DTSC types e registers UNSIGNED 8 1 UNSIGNED 16 1 INTEGER 16 l UNSIGNED 32 2 INTEGER 32 2 LOGMAN 7 TEXT X X 2 Table 3 3 Modbus data types NOTE The parameters of the following examples are an excerpt of the parameter list in the appendix of the Configuration Manual 37386 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 Woodward Page 17 83 Manual 37389 DTSC 200 Series Interfaces Example 1 Addressing the password for the CAN interface Parameter Setting range Data type 10402 Password for CAN interfacel 0000 to 9999 UNSIGNED 16 Modbus address 400000 Par ID 1 410403 Modbus length 1 UNSIGNED 16 The following Modscan32 screenshot shows the configurations made to address parameter 10402 ModScan32 ModScal al x File Connection Setup View Window Help Device Id Address 10403 evice ld 1 Number of Polls 4 MODBUS Point Type Valid Slave Responses 4 Length 1 03 HOLDING REGISTER gt m lt 1C14H gt Figure 3 3 Modbus configuration example 1 Example 2 Addressing the rated voltage of source 1
52. gned16 A erch Test is active HEAT Woodward Page 49 83 Modbus Modbus Modicon Start start addr 450087 450086 Logicsmanager Output Flag Mask 0080h SI priority is requested Start Delay timer S2 is timing at the moment Mask 4000h Manual 37389 DTSC 200 Series Interfaces Logicsmanager Output Flag Mask 0040h S2 priority is requested Logicsmanager Output Flag Mask 0004h Gen 2 Gen mode is requested Stable timer S1 is timing at the moment Mask 2000h Data Para Description Multiplier Units Data Type Byte eg Logicsmanager Output Flag Mask 0020h External timer Bypass is EE NE internal Mask 0002h Bit Stable timer S2 is 3 timing at the moment Mask 1000h ATS Controller is in Inhibit Mode Remote Peak Shave mode is requested Inhibit Transfer to Sl is requested Inhibit Transfer to S2 is egei Logicsmanager Output Flag Mask 0800h SE power rate provisions are re nli Delayed transition mode is forced Extended parallel time is Li No Load Test is requested internal Logicsmanager Output Flag Mask 0100h Load shed is requested Logicsmanager Output Flag Mask 0008h Load Test is requested 10336 Start Delay timer S1 is timing at the moment Mas 8000h Outage timer S2 is timing at the moment Mask 0400h Switch Eeer timer Sl is timing at the mo Mal 0020h i Switch reply timer S2 is timing at the mo sa Transfer pause timer Sl is timing at the mo a n A men
53. gure monitoring menu by using the amp softkey Navigate to External acknowledge by using the M softkey and enter the External acknowledge LogicsManager screen by pressing the amp softkey Logics Manager gt External acknowledge gt Delay ON gt Delay OFF 000 00 sec 000 00 sec 04 14 Remote acknowledge y Cancel Help Figure 5 7 Display screen Ext acknowledge Configure the respective values for the External acknowledge LogicsManager function using the M and M as well as the amp softkey and Confirm the change by pressing the amp softkey With this setting the External acknowledge LogicsManager output becomes TRUE as soon as the remote ac knowledge signal is enabled NOTE The LogicsManager commands 2 and 3 may be used to configure additional conditions like discrete inputs which must be energized to be able to issue the remote command Page 76 83 O Woodward Manual 37389 DTSC 200 Series Interfaces Remote Control Telegram The internal parameter 503 of the DTSC must be set to react on the remote control instructions This is per formed by sending rising signals for the respective bits Refer to the Remote Control Telegram section on page 57 for detailed information about the telegram structure and the control bits Ext Acknowledge The command variable 04 14 Remote acknowledge is the reflection of the control bit bit 4 The DTSC deactivates the horn with the first change from 0 t
54. lts The bit 28 11 should be configured to 0 This pa rameter can be configured using the parameter COB ID SYNC Message If a SYNC message is to be sent the PDO can be configured in that way that it contains no values Page 60 83 Woodward Manual 37389 DTSC 200 Series Interfaces Object 1017h Producer Heartbeat Time The object Producer Heartbeat Time defines the heartbeat cycle time in ms If no Producer Heartbeat NMT Er ror Control is to be sent this is to be configured to 0 Object description tee E 1017h Names Producer Heartbeat Time Object code VAR Data type UNSIGNED16 Entry description ACCESS ee Read Write PDO figure no Value range UNSIGNEDI16 Default value 240 Note The time is extended to the next full 20 ms If the time is 0 the NMT Error Control will be sent as response to a remote frame Object 1018h Identity Object The object contains common information of one participant Object description Index AA 1018h Names Identity Object Object code RECORD Data type Identity Category obligatory Entry description Sub index Oh Description Number of entries Entry category obligatory PROCESS Sidi eege Read Only PDO figure no Value range 1 Default value 1 Sub index 1h Description Vendor ID E
55. mmPar Cate COTY oodd conditioned obligatory for every supported PDO Entry description Sub index Oh Description Largest Sub index supported Entry category obligatory ACCESS EG Read Only PDO figure no Value range 5 Sub index 1h Description COB ID used by PDO Entry category obligatory AECE MEME Read Only Read Write if COB ID can be configured PDO figure no Value range UNSIGNED32 Figure 65 Default value Index 1800h 181h Index 1801h 281h Index 1802h 381h Index 1803h 481h because Default value for Node ID is 1 Sub index 2h Description Transmission type Entry category obligatory Eet Read Only Read Write 1f transmission type can be changed PDO figure no Value range UNSIGNEDS Table 54 Default value 0 Sub index 5h Description Event timer Entry category optional EE Read Write PDO figure no Value range 0 not used UNSIGNED16 Default value 20 Woodward Page 63 83 Manual 37389 DTSC 200 Series Interfaces Note Sub index 1h The bits 31 29 were ignored Writing these bits does not cause faults The bits 28 11 should be configured to 0 This sub index can be set in the display screens COB ID in sub menu CAN OPEN TPDO 1121314 Sub index 2h 0 APDO will not be seni
56. n IKD Physical state Only the physical state of the inputs is transmitted The settings under idle current tripping delay revert delay enabling self resetting and acknowledge input are without effect These settings have to be selected for devices which include these parameters e g the DISC 200 Check of the settings Actuate an external DO via the LogicsManager and check whether the respective relay at the IKD operates Scroll the display screens to view the ext discrete inputs 1 to 8 A set of discrete inputs will be shown that corre spond to the IKD Use the FAQ CAN Bus chapter on page 40 to troubleshoot any CAN bus faults Expansion with Two IKD 1 16 Additional External DI DO The first IKD will be adjusted like described above For the second IKD the following settings must be config ured CAN Open RPDO1 function 18 IKD COB ID 513 1st IKD 1 extension card RPDO function 2 IKD COBID 514 COBID Transmission Type Event Timer Number mapp objects 1 Mapped object 2 3 4 Mapped object CAN Node ID CAN ID receive data CAN ID send data Physical state only 2nd IKD 1 extension card CAN Node ID CAN ID receive data COBID Transmission Type Event Timer Number mapp objects 1 Mapped object 2 3 4 Mapped object CAN ID send data Physical state only Figure 5 5 CANopen interface expansion with two IKD 1 Page 30 83 Woodward Manual 37389 DT
57. nd remote control data can be written with the Preset Single Regis ters function or Preset Multiple Registers refer to figure below Modicon Modbus commande address DTSC visualization data gt Read Holding Register 0x03 450001 450000 DTSC gt Read Holding 0x03 remote control amp fi tion dat MO lt Preset Multiple Registers 0x10 Preset Single Register 0x06 40001 NOTE All addresses in this document comply with the Modicon address convention Some PLCs or PC pro grams 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 O Woodward Page 15 83 Manual 37389 DTSC 200 Series Interfaces 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 DTSC Modbus addressing range the visualization protocol can be reached on addresses starting at 450001 On this ad dress range it is possible to do block reads from 1 up to 128 Modbus registers at a time Addresses AAA 450088 Timer state feedback signals EE i i
58. ngs Actuate an external DO via the LogicsManager and check whether the respective relay at the Phoenix terminal operates Scroll the display screens to view the ext discrete inputs 1 to 8 and ext discrete inputs 9 to 16 A set of discrete inputs will be shown that correspond to the Phoenix terminal Use the FAQ CAN Bus chapter on page 40 to troubleshoot any CAN bus faults Woodward Page 33 83 Manual 37389 DTSC 200 Series Interfaces Description of the DTSC Parameters Interfaces General 5 Devicenumber CAN bus Device number 1 to 127 A Ger tenummer CL2 So that this control unit may be positively identified on the CAN bus the unit ad Dale dress must be set in this parameter The address may only be represented once on the CAN bus All other addresses on the CAN bus are calculated on the basis of the address entered in this parameter NOTE If the protocol is CANopen the Node ID is defined with the device number 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 rea sonable time EN Protocol CAN bus Protocol OFF CANopen LeoPC Protocol TTT CL2 The CAN bus of this unit may be operated with different protocols and Baud rates 3155 This parameter defines the protocol to be utilized Please note that all participants on the CAN bus must use the same pro
59. ntry category obligatory ACC SS on nk Read Only PDO figure no Value range UNSIGNED32 Default value 0 Object 1200h 1201h Server SDO Parameter Objects are not supported The receive SDO is 600h Node ID The transmit SDO for answers is 580h Node ID The Node ID can be entered using the parameter Unit number Woodward Page 61 83 Manual 37389 DTSC 200 Series Interfaces Object 1400h 141Fh Receive PDO Communication Parameter This object contains the communication parameter for the PDOs that can be received from the participant The sub index Oh contains the number of valid entries within the communication recording The sub index 1h con tains the COB ID of the PDO The interpretation of the entry occurs according to the tables Structure of the PDO COB ID entry and the Description of the POD COB ID entry Object description AA 1400h 141Fh A Receive PDO parameter Object code RECORD Dalai PDO CommPar Category conditioned obligatory for every supported PDO Entry description Sub index Oh Description Largest Sub index supported Entry category obligatory EE Read Only PDO A Ur vi nicas no Value range 2 Sub index Ih Description COB ID used by PDO Entry category obligatory INCCESS tidad Read Only Read Write if variable COB ID is sup
60. o 1 of the logical output External ac knowledge and acknowledges inactive alarm messages with the second change from 0 to 1 Remote Control via CAN It is possible to perform a remote acknowledgement via a default SDO communication channel Remote Acknowledgement Configuration of CAN Interface Be sure to enable CAN Open Master if there is no PLC taking over the master function Open the main menu by pressing the C softkey and navigate to Set up Comm interfaces by using the M softkey Open the Set up Comm interfaces menu by using the amp softkey and navigate to Set up CAN interfaces by us ing the M softkey Open the Set up CAN interfaces menu by using the amp softkey and navigate to CAN Open interface by using the M softkey Open the CAN Open interface menu by using the amp softkey navigate to CAN Open Master by using the B softkey and enter the CAN Open Master screen by pressing the amp softkey Figure 5 8 Display screen configure CAN interface Select Yes by using the W softkey and confirm your selection by pressing the amp softkey General Information 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 calculat
61. o 76 Figure 5 8 Display screen configure CAN interface eee 71 Figure 5 9 CANopen request data Tor Node ID Lion ii Peu et a ume oin iei 78 Figure 5 10 Display screen configure device number 78 Figure 5 11 CANopen request data for Node ID Vivo rca ri A s 78 Figure 5 12 Display screen configure Server SOS c s v s 79 Figure 5 13 CANopen request data for additional Server SDO enne 80 Figure 5 14 Modbus remote control parameter 2072 81 EURES E 81 Figure 5 16 Cyclical sending of data Sync Message request i 82 Figure 5 17 Cyclical sending or dala TED Via tl cedoneutialaudeianiastoiecreduates 82 Tables Table 1t Mangal OV VIJ N nn 6 Table 3 1 Modbus address range DIOCK Ted E 16 Table 352 Modbus address E et nin LI Table 2 3 Modbus Gala yE Siae e Aide 17 Table 3 4 Tele e CET fer en 20 Woodward Page 5 83 Manual 37389 DTSC 200 Series Interfaces Chapter 1 General Information Related Documents Type English German DTSC 200 Series DTSC 200 Installation DTSC 200 Configuration DTSC 200 Operation DTSC 200 Application DTSC 200 Interfaces this manual gt Additional Manuals IKD 1 Manual 37135 GR37135 Discrete expansion board with 8 discrete inputs and 8 relay outputs that can be coupled via the CAN bus to the control unit Evalua tion of the discrete inputs as well as control of the relay outpu
62. oducer heartbeat time is equal 0 the heartbeat will only be sent as response to a remote frame re quest The time configured here will be rounded up to the next 20 ms step COB ID SYNC Message 1 to FFFFFFFF This parameter defines whether the unit generates the SYNC message or not Com plies to object 1005h see Object 1005h COB ID SYNC Message on page 60 Max response time ext devices 0 1 to 9 9 s CL2 The maximum time that an attached external device has to answer an SDO mes 2010 sage If the external device fails to answer before this time expires an abort mes sage 1s sent and the SDO message will be sent again This 1s only effective 1f DTSC 200 CAN open master is enabled E Time re init ext devices Time re init re initialization ext devices 0 to 9 999 s A Zeit Re init ext Ger te CL2 An external device will be configured again with SDO messages after the time set 2009 for this parameter If 0 is input in this parameter the external device will not be configured again with SDO messages This only functions if DTSC 200 CAN open master is enabled O Woodward Page 35 83 Manual 37389 5 2nd Client gt Server COB ID rx A 2 Client gt Server COB ID rx CL2 9020 5 2nd Server gt Client COB ID tx A 2 Server gt Client COB ID tx CL2 9022 5 3rd Client gt Server COB ID rx amp 3 Client gt Server COB ID rx CL2 9024 amp 3rd Server gt Client COB ID tx A 3 Server gt Client COB ID tx
63. on with the respective device and may differ the default values CAUTION AN The ID settings are entered in hexadecimal format in the DTSC and are therefore listed in decimal and hexadecimal format in the follovving tables Page 28183 O Woodward Manual 37389 DTSC 200 Series Interfaces Expansion with One IKD 1 8 Additional External DI DO CANopen 1st IKD 1 extension card CAN Node ID CAN ID receive data i st RPDO1 function 1 E CAN ID send data COB ID Physical state only COBID 385 Transmission Type 255 Event Timer 20 ms Number mapp objects 4 1 Mapped object 8001 2 3 4 Mapped object 8000 Figure 5 4 CANopen Schnittstelle Einstellungen f r externe Ger te Configuration of the receive PDO 1 Comment COB ID 201h 513 Dec CAN ID on which the data are received 1 IKD The data received on the COB ID were assigned to the external DI 1 to DI 8 vice default value ext device 1 default value Configuration of transmit PDO e g PDOI Number of mapped 4 objects 1 Mapped Object 2 Mapped Object_ Parameterno 8000 gt oS O 3 Mapped Object J Parameter no 8000 gt SS 4 Mapped Object _ Parameter no 8000 o Settings at the IKD Node ID O So that the entries of the CAN IDs are taken over CAN ID transmit 201h 513 Dec The DTSC receives on this ID ting data Woodward Page 29 83 Manual 37389 DTSC 200 Series Interfaces Settings for DIs o
64. onfiguring via front panel or LeoPC 1 NOTE Configuration examples may be found on page 26 Setting the Transmit PDO Examples O Woodward Page 39 83 Manual 37389 DTSC 200 Series Interfaces FAQ CAN Bus The following are reason that no data 1s transmitted e T structure bus is utilized e CAN L and CAN H are interchanged e Not all devices on the bus are using identical Baud rates e Terminating resistor are missing e Baud rate to high for vviring length Recommendations of Woodward The maximum length of the communication bus wiring is dependent on the configured Baud rate Max length 1000 kbit s 800 kbit s Source CANopen Holger Zeltwanger Hrsg 2001 VDE VERLAG GMBH Berlin und Offenbach ISBN 3 8007 2448 0 The maximum specified length for the communication bus wiring might not be achieved if wire of poor quality is utilized there is high contact resistance or other conditions exist Reducing the baud rate may overcome these is sues Device Combinations and Bus Load The baud rate has a direct effect on the number of messages which may be exchanged via the bus per time unit A bus load should not exceed approx 40 capacity to prevent long waiting times or loss of messages The following information provides clues for reasonable device configurations at certain baud rates The exact configuration is to be taken from the respective operation manuals 20 kBaud IKD 8DIDO 1 PDO every 50ms only r
65. only one object to be transmitted 1 Mapped Object 3190 display value the object with the index 3190 2 Mapped Object 0 will not be used 3 Mapped Object 0 will not be used 4 Mapped Object 0 will not be used Sending of Data on Request The data to be sent Mapped Objects may be provided on request by configuring the Sync Message and the Transmission Type of a TPDO The unit is requested to send its data by sending a Sync Message The number of required Sync Messages 1s determined by the setting of the Transmission Type If the data is to be sent on request Bit 31 of the Sync Message must be configured to 1 and the CANopen Mas ter function must be configured to Off The Transmission Type of TPDO 1 is configured to 2 in the following example This means that a message of the configured TPDO is sent by the unit after two Sync Messages have been sent to the unit The recorded data shows that the data of the Mapped Object in this example Mux 5 is sent refer to Figure 5 17 after sending the Sync Message twice refer to Figure 5 16 ES Transmitclient untitled opt B x File Edit View Function Options Trace Help en n aje s sja M ores Na esee JET Data he 1 but Bu 0 Tics T Vite DES LE ES ReceiveClient Overwrite Mode File Edit View Functions Trace Options Help asu 99 7217 soje Bl 5 9 3 1 EA 05 00 OO OO OO OO OO 28 E 4 Ld For Help press Fi Figure 5 17
66. placed Parameter No 15603 Object 5CF3h X 0 Parameter No 15603 pa internal Parameter No 118 Parameter No 147 Parameter No 119 Parameter No 10166 Parameter No 120 Parameter No 10167 4 ParameterNo 121 Parameter No 10110 Internal 6 ParametrNo 125 Parameter No 10169 Intemal 8 Parameter No 2510 0 Lelinternal 9 LParameter No 2522 Internal Data Protocol Parameter No 15604 Object 5CF4h Source 2 Values If the object SCF4h is read out the protocol known value is replaced Parameter No 15604 Object 5CF4h Parameter No 15604 10 tte Page 70 83 Woodward Manual 37389 DTSC 200 Series Interfaces CANopen Mapping Parameter 3 Name Unit Data type Note 2 108 206Ch Source 2 Voltage Vj 1 10 V signed32 109 206Dh Source 2 Voltage V 23 1 10 V signed32 110 206Eh Source 2 Voltage V 31 1 10 V signed32 111 206Fh Source 2 Current I mA signed32 112 2070h Source 2 Current Ir mA signed32 113 2071h Source 2 Current I 3 mA signed32 114 2072h Source 2 Voltage Num 1 10 V signed32 115 2073h Source 2 Voltage Vian 1 10 V signed32 116 2074h Source 2 Voltage Vian 1 10 V signed32 118 2076h Source 1 Vol
67. ported PDO figure no Value range UNSIGNED32 Table 54 Default value Index 1400h 200h Node ID Index 1401h 300h Node ID Index 1402h 400h Node ID Index 1403h 500h Node ID Index 1404h 15FFh disabled Sub index 2h Description Transmission type Entry category obligatory ee Read Only PDO figure no Value range UNSIGNEDS Table 55 Default value Device Profile dependent Note The device possesses only two RPDOs Therefore the objects 1402h 141Fh are not available Sub index 1h The bits 30 29 were ignored Writing these bits do not cause faults The bits 28 11 should be configured to 0 This value can be set in the display mask COB ID in sub menu CAN OPEN RPDO 1 2 Sub index 2h This value is always set OXFF Page 62 83 Woodward Manual 37389 DTSC 200 Series Interfaces Object 1600h 161Fh Receive PDO Mapping Parameter Is not used The receive PDOs can be assigned to defined functions The corresponding parameter can be set in the display screen Function in sub menu CAN OPEN RPDO 1 2 Object 1800h 181Fh Transmit PDO Communication Parameter Includes the communication parameter for the PDOs that can be sent from the participant Object description Inde X EE 1800h 181Fh NAM pipi Transmit PDO parameter Object code RECORD Data type PDO Co
68. r 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 Combine Functions with Each Other Bk 16DIDO Co 16DIDO Read If PDOI is configured as 1 IKD then PDO2 can only be configured as either 2 IKD or no func E Node ID of the device Node ID of the device 1 to 127 A Node ID des Ger tes CL2 Node ID of the attached device The SDO messages vvere sent on the standard i SDO IDs or the answers were expected 5 RPDO COP ID ext device x RPDO COB ID ext device 1 1 to FFFFFFFF 8 RPDO COP ID ext Ger t x CL2 Value to be written in the object 1800h sub index 1h of the external device 9070 9072 Woodward Page 37 83 Manual 37389 CAUTION DTSC 200 Series Interfaces COB IDs which are already used should not be used COB IDs in a CANopen device after loading the standard values 280h Node ID 640 Node ID Object 1801h Subindex 1 380h Node ID 896 Node ID Object 1802h Subindex 1 480h Node ID 1152 Node ID Object 1803h Subindex 1 The receiving COB IDs are preallocated 300h Node ID 768 Node ID Object 1401h Subindex 1 400h Node ID 1024 Node ID Object 1402h Subindex 1 500h Node ID 1280 Node ID Object 1403h Subindex 1 Problems may be encountered if a COB ID is assign
69. ry category conditioned dependent on the number and size of the objects ACCESS ME Read Write PDO figure no Value range UNSIGNED32 Default value Device profile dependent Note Sub index Oh The sub index 0 cannot be changed Writing does not cause fault messages however the value will not be saved For configuration of the other sub indexes the sub index Oh has to be set not 0 Sub index 1h 4h You have to enter the object numbers from the EDS file into the sub indexes 1h 4h The sub indexes 1h 4h can be set in the display masks 1 4 Mapped Object in sub menu CAN OPEN TPDO 1 2 3 4 CAUTION With configuration over CAN open the object ID is to be used see EDS file With configuration over display LeoPC1 the parameter number is to be used see CANopen Mapping Parameter after page 71 Woodward Page 65 83 Manual 37389 DTSC 200 Series Interfaces Data Format of Different Functions Depending on the selected RPDO function a different data format will be expected Receiving Messages 1 IKD 2 IKD Bit 0 DI not analyzed not analyzed not TT notanalyzed notanalyzed not analyzed Bit 1 DI 2 Bit 7 DI 8 Phoenix16 Bit 0 DI 9 not analyzed not analyzed not analyzed not analyzed not analyzed not analyzed Bit 1 DI 10 Bit 7 DI 16 CAUTION Please note for combination of the different functions CAUTION Configuration of the Phoenix
70. second rise of the pulse acknowledges a fault which is not pre sent anymore Woodward Page 57 83 Manual 37389 DTSC 200 Series Interfaces Appendix B CANopen Description of the Common Data Types Structure of the PDO COB ID Entry UNSIGNED32 28 11 ip jon Io In jalO A bitidentifier 29bitID 01 o 129 bit identifier Description of the PDO COB ID entry 31 MSB 0 PDOexistsfisvalid ss 1 PDO does notexist isinvalid S O 30 20 Device does not generate SYNC message O O Z o o o o 1 LDevice generates SYNC message SS O AAA l OD CAN BS gt 28 11 OX Ifbit29 0andif bit 29 1 bits 28 11 of 29 bit SYNC COB ID 10 0 LSB XX Bits10 0 of SYNC COB ID Transmission Types PDO Transmission __ ceyclicaly continuously synchronous asymchromous RTR only p TT 1 oa E e gt TT 2 _ ET oo oo CO A la not supported Page 58 83 Woodward Manual 37389 Description of the Object Parameter Object 1000h Device Type This contains information about the type of the participant Object description IX AA 1000h Name oeiiienssesssssseeee Device Type Object code VAR Data type UNSIGNED32 Category obligatory Entry description ACCES van e Read Only PDO figure no Value range UNSIGNED32 Default value 0 h
71. t 04700 gt lt 00000 gt Polls 92 450105 450106 450107 450108 450109 450110 450111 450112 450113 450114 450115 450116 450117 450118 450119 450120 450121 450122 450123 450124 450125 450126 450127 450128 lt 00000 gt lt 04700 gt lt 00000 gt lt 00000 gt 04700 00000 lt 00000 gt lt 04700 gt lt 00000 gt lt 00000 gt lt 04700 gt lt 00000 gt lt 00000 gt lt 04700 gt lt D0000 gt lt 00000 gt lt 04700 gt lt 00000 gt lt 00000 gt lt 04700 gt lt 00000 gt lt 00000 gt lt 04700 gt 00000 Figure 3 2 Modbus visualization configurations Page 16 83 O Woodward Manual 37389 DTSC 200 Series Interfaces Configuration The Modbus interface can be used to read write parameters of the DTSC According to the DTSC Modbus ad dressing range for the configuration addresses the range starts at 40001 and ends at 450000 You can always ac cess only one parameter of the system in this address range The Modbus address can be calculated depending on the parameter ID as illustrated below Parameter ID lt 10000 Parameter ID gt 10000 Modbus address 40000 Par ID 1 400000 Par ID 1 Table 3 2 Modbus address calculation Block reads in this address range depend on the data type of the parameter This makes it important to set the cor rect length in Modbus registers which depends on the data type UNSIGNED 8 INTEGER 16 etc Re
72. t is possible to remote control the DTSC using the bits 2 to 4 of control word 1 on address 503 The Remote Control Telegram in Appendix A on page 57 is valid for both CANopen as well as Modbus and indicates the ar rangement of the remote control bits Woodward Page 11 83 Manual 37389 DTSC 200 Series Interfaces CAN CAL The Woodward LeoPC1 software may be used to remote control the DTSC via a connected PC After selecting the desired remote control command the remote control command must be confirmed by selecting the Set but ton Remote Control Please select the device that has to be remote controlled System 5418_ 2487 413 DTSC200 10005 1 Remote control data Control word i Remote stop Remote start Figure 2 1 Data telegrams remote control via CAN NOTE The control words Remote stop and Remote start have no effect on the DTSC 200 CANopen It is possible to remote control the DTSC using the bits 2 to 4 of control word 1 on address 503 The Remote Control Telegram in Appendix A on page 57 is valid for both CANopen as well as Modbus and indicates the ar rangement of the remote control bits Page 12 83 O Woodward Manual 37389 DTSC 200 Series Interfaces Chapter 3 Serial Interface EH Overview via DPC Serial 2 PLC RS 485 port PC RS 232 port LeoPC1 Figure3 1 Serial interface overview O Woodward Page 13 83 Manual 37389 Gen
73. tage V gt 1 10 V signed32 119 2077h Source 1 Voltage V 23 1 10 V signed32 120 2078h Source 1 Voltage V 31 1 10 V signed32 121 2079h Source I Voltage Vy in 1 10 V signed32 122 207Ah Source I Voltage Vian 1 10 V signed32 123 207Bh Source 1 Voltage Vian 1 10 V signed32 135 2087h Source 2 Real power P W signed32 136 2088h Source 2 Reactive power Q var signed32 144 2090h Source 2 Frequency 1 100 Hz signed16 147 2093h Source 1 Frequency f33 1 100 Hz signed16 160 20A0h Source 2 Power factor coso 1 1000 dimls signed16 2520 29D8h Source 2 Real energy 1 100 MWh unsigned32 2522 29DAh Source 2 Reactive energy 1 100 Mvarh unsigned32 8000 3F40h always 0 unsigned 16 8001 3F41h Output of the 1 IKDI Bit field unsigned16 Bit 15 Relay output REx08 Bit 14 Relay output REx07 Bit 13 Relay output REx06 Bit 12 Relay output REx05 Bit 11 Relay output REx04 Bit 10 Relay output REx03 Bit 9 Relay output REx02 Bit 8 Relay output REx01 Bit 7 always O Bit 6 always O Bit 5 always 0 Bit 4 always O Bit 3 always 0 Bit 2 always 0 Bit 1 always 0 Bit 0 always 1 Woodward Page 71 83 Manual 37389 DTSC 200 Series Interfaces
74. terminal if the DTSC is not CAN open master If the discrete inputs of the Phoenix terminal shall be evaluated by the DTSC it must be configured this way that the corresponding discrete inputs in byte 1 and byte 2 are available for the received PDO This PDO must be sent independently from the terminal The DTSC does not pick up PDOs with remote frames The receiving PDO of the Phoenix terminal and the corresponding transmitting PDO of the DTSC must be ad justed on both units Page 66 83 Woodward Manual 37389 DTSC 200 Series Interfaces Definition of Protocol Descriptions If in a PDO a protocol number is entered as 1 Mapped object a data array with 8x unsigned8 is sent The denotation is 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 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 integ
75. tifications 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 dam age to these parts e 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 e Avoid all plastic vinyl and Styrofoam except antistatic versions around printed circuit boards e Do not touch the components or conductors on a printed circuit board with your hands or with conductive devices A 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
76. tocol DE OFF The CAN bus is disconnected Values are not sent or received CANopen The CANopen protocol is used LeoPC s The CAN CAL protocol is used EN Baudrate CAN bus Baudrate 20 50 100 125 250 500 800 1 000 kBaud Baudrate Z 00000 CL2 The CAN bus of this unit may be operated with different protocols and Baud rates 3156 This parameter defines the used Baud rate Please note that all participants on the CAN bus must use the same Baud rate DE Page 34 83 Woodward Manual 37389 DTSC 200 Series Interfaces General CANopen Parameters al CAN Open Master A CAN open Master CL2 9000 a Producer heartbeat time A Producer heartbeat time CL2 9120 a COB ID SYNC Message A COB ID SYNC Message CL2 9100 4 Max answer time ext devices A Max Antwortzeit ext Ger te CANopen Master YES NO NES A The DTSC 200 is the CANopen Master The unit automatically changes into operational mode and sends broadcast messages Start Remote Node which cause all other units to change into operational mode as vvell Attached external devices vvere configured from the unit vvith SDO messages The unit sends a SYNC message all 20ms on COB ID 80 Hex NO The DTSC 200 is a CANopen Slave CAN bus Producer heartbeat time 20 to 65 530 ms Independent from the CANopen Master configuration the unit transmits a heart beat message with this configured heartbeat cycle time If the pr
77. tput 7 Rex7 Mask 0040h Bit yo External discrete output 6 Rex6 Mask 0020h Bit oy External discrete output 5 Rex5 Mask 00l0h Bit ss External discrete output 4 Rex4 Mask 0008h Bit yy External discrete output 3 Rex3 Mask 0004h Bit hh s r t t pa E R _ External discrete output 1 Rex1 Mask 0001h Bit amen Ta 8013 unsigned16 5 6 Linternal pintermal JE E 450079 450078 L2 10328 unsigned16 FT HEAT Woodward Page 47 83 Manual 37389 rr DTSC 200 Series Interfaces Data Para Description Multiplier Units Data Type Byte eg 10329 unsigned 16 inemal OOOO Modbus Modbus Modicon Start start addr E A transfer failure occured OPEN CLOSE Mask 0001h E ger 450081 450080 10330 unsigned16 HET eae check in progress for transfer direc Mask 0080h SE EH check in progress for transfer direc Mask 0040h dd Both Sources are ble and stable Mask 0004h 450082 45008 1 Page 48183 O VVoodyvard 10331 unsigned16 Errani RR tem Eric il tem internal OOOO Manual 37389 rr DTSC 200 Series Interfaces Data Para Description Multiplier Units Data Type Byte S Modbus Modbus Modicon Start start addr 450083 450082 10332 unsigned16 cla pired Poi sii pired rr et al pired a pired FEAT 450084 450083 10333 unsigned16 inemal o HET 450085 450084 10334 unsi
78. ts is done via the control unit LeoPC1 User Manual 37146 GR37146 PC program for visualization configuration remote control data logging language upload alarm and user management and man agement of the event recorder This manual describes the set up of the program and interfacing with the control unit LeoPC1 Engineering Manual 37164 GR37164 PC program for visualization configuration remote control data logging language upload alarm and user management and man agement of the event recorder This manual describes the configuration and customization of the program 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 op eration 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 man
79. ual 37386 Page 6 83 Woodward Manual 37389 DTSC 200 Series Interfaces Interface Overview The DTSC 200 provides the following communication interfaces e Serial interface 1 DPC LeoPC1 e Serial interface 2 RS 485 Modbus e CAN interface CANopen or CAN CAL dependent on application om emm emm emm emm emm N TR E E E A E E E E EN Mem eg een KS SS i CAN interface CANopen protocol Serial interface 2 RS 485 Serial interface 1 RS 232 PLC Modbus RTU Slave KD 1 IO module Phoenix IO module CAN interface CAN CAL protocol PFree f mm em emm i mm emm emm zm zm Gateway to LeoPC1 Profibus PLC GW4 Figure 1 1 Interface overview WARNING When connecting the direct configuration interface the Woodward DPC with RJ45 connector must be used Failure to do so may destroy the unit Woodward Page 7 83 Manual 37389 DTSC 200 Series Interfaces Modbus Half Full Duplex Application RS 485 A O JU nc HS 4 GO la PLC Master Dr orme TT Ke E ONE DTSC Slave 2 Figure 1 2 Interface overview serial interface Modbus full duplex RS 485 A ESO Ummom o PLC Master DTSC Slave 2 Figure 1 3 Interface overview serial interface Modbus half duplex Page 8 83 O Woodward Manual 37389 DTSC 200 Series
80. vices from different manufacturers to be ac cessed via the bus in exactly the same manner CAN Bus Process The fundamental element of the CANopen standard is the description of the device functionality through an ob ject dictionary OD The object dictionary is divided into two sections The first section contains general device information like device identification manufacturer name etc as well as communication parameters The sec ond section describes the specific device functionality A 16 Bit index and an 8 Bit sub index identify the entry object in the object dictionary Each entry in the ob ject dictionary provide a basis for a standardized network access to the Application Objects of a device such as input and output signals device parameters device functions or network variables The functionality and characteristics of a CANopen device can be described by means of an Electronic Data Sheet EDS using the ASCII format The EDS acts as a kind of template that describes the data and features which are accessible via the network The Device Configuration File DCF describes the actual device set tings EDS and DCF can be provided in the form of a data carrier which can be downloaded from the Internet or stored inside the device Page 22 83 O Woodward Manual 37389 DTSC 200 Series Interfaces Similar to other well known field bus systems CANopen also distinguishes two basic data transfer mechanisms The
81. wise a fault message will be issued which states that the parameter may not be overwritten The configuration of the mapped objects of a send PDO is very clear and easy with this program Configuration of the transmission type The following transmission types are supported e asynchronous Profile Event and asynchronous Manuf Event both send a message after the event timer has expired e synchronous cyclic with the according transmission rate O Woodward Page 27 83 Manual 37389 DTSC 200 Series Interfaces Settings for Connection with External Devices Determines the node ID for CANopen Determines the protocol select this for CANopen Determines the baud rate NOTE The standard values of the DTSC enable to connect devices on the basis of the CANopen protocol quickly and easily Figure 5 3 shows an overview of the different device combinations which are possible mm gt PLC e u s de extension card 8 DOS 2nd IKD 1 8 Dis S dl extension card 8 DOs A Phoenix 16 Dis extension card 16 DOs Figure 5 3 CANopen interface external devices PLC PLC of the plant IKD 1 2 extension cards each for 8 additional external inputs and outputs Phoenix extension card Extension card for 16 additional external inputs and outputs NOTE 1 The parameters which are highlighted red in the follovving figures must be observed particularly be cause these are essential for a communicati
82. with the Phoenix terminal IL CAN BK ILB CO 24 16DI 16DO 16 DI DO The specified settings are valid for a Phoenix terminal with Node ID 2 CAN Open Y a a a a Ze Ze Phoenix extension card woo T RPDO 1 function Phoenix COBID 513 Node ID 2 COB ID ext 385 COB ID 385 Transmission Type 255 Event Timer 20 ms Number mapp objects 4 1 Mapped object 8003 2 3 4 Mapped object 8000 Figure 5 6 CANopen interface expansion with Phoenix terminal CAN open Master PE Max time for reply ext devices AA O Time for re init ext devices 100 If this time is set O the attached Phoenix terminal may not be configured correctly Setting of the receiving PDO 1 COB ID 201h 513 Dec CAN ID to receive data BKIODIDO The received data via the COB ID are copied to the ext DI 1 to 16 vice ext device 1 PDO on that COB ID CAUTION The 2 PDO this function must be configured to OFF NOTE The DTSC is the CANopen master Page 32 83 Woodward Manual 37389 DTSC 200 Series Interfaces Settings of the transmitting PDO i e PDO3 COB ID 381h 385 Dec CAN ID which is used to send data Has to be the same as parameter RPDO COB ID of the ext device 1 FFh 255 Dec The PDO is cyclically sent The PDO is sent every 20 ms PS O NNI objects 2 Mapped Object_ Parameterno 0 J oo SOS 3 Mapped Object J Parameter no 0 J o OS 4 Mapped Object Parameterno O O Check of the setti
83. y are reserved to report device malfunctions A common system time can be provided through a central timing message not included yet Management functionality like controlling and monitoring the communication status of the nodes is accom plished by a network management protocol NMT organized according to a logical master slave relationship Two alternative mechanisms Node Guarding and Heartbeat messages are available to implement node monitoring functionality The assignment of CAN message identifiers to PDOs and SDOs is possible by direct modifications of entries in side the data structure of the object dictionary or for simple system structures through the use of pre defined identifiers Server Data Objects SDO Communication As already mentioned in the introduction each CANopen device has an object directory All parameters status variables measurement values and input values of the device are stored in this object di rectory These parameters are called objects in the CANopen protocol description The single objects may contain up to 254 values If an object has more than one value these contain a sub index Example Object 1017h with One Value Name of the object Producer Heartbeat Time Contains a value which may be read and written Example Object 1200h with Several Values Name of the object Server SDO parameter Sub index 0 contains the number of sub indices Sub index contains the COB ID Client gt S

DTSC-200 Series Interfaces Interface Description

Contents

Download Pdf Manuals

Related Search

Related Contents