Home

TeSys U LULC09 DeviceNet Communication Module

1. Attribute ID Access Name Data Type Value Description 2 Get Max instance UInt 1 Attribute Access Name Data Value Only with Description ID Type 1 Get NumAttr Ulnt LUCM LUCMT Number of Attributes Supported Set Get TripFLCSet UInt 652 LUCM LUCMT of FLA max 4 Set Get TripClass USInt 606 LUCM LUCMT Trip Class Setting 0 to 200 5 Get AvgCurrent Int 466 x FLA LUCM LUCMT 0 1A 6 Get Phimbal USInt 471 LUCM LUCMT Phase Imbalance 7 Get Thermal USInt 465 LUCM LUCMT Thermal Capacity 8 Get IL1 Current Int 467 x FLA LUCM LUCMT 0 1A 9 Get IL2 Current Int 468 x FLA LUCM LUCMT 0 1A 10 Get IL3 Current Int 469 x FLA LUCM LUCMT 0 1A 11 Get Ground Current Int 470 x FLA LUCM LUCMT 0 1A 101 Get IL1 Current Int Idem Att 8 LUCM LUCMT 0 1A 102 Get IL2 Current Int Idem Att 9 LUCM LUCMT 0 1A 103 Get IL3 Current Int Idem Att 10 LUCM LUCMT 0 1A 104 Get Ground Current Int Idem Att 11 LUCM LUCMT 0 1A 105 Get IL1 Current Ratio UInt 467 LUCM LUCMT of FLA 106 Get IL2 Current Ratio UInt 468 LUCM LUCMT of FLA 107 Get IL3 Current Ratio UInt 469 LUCM LUCMT of FLA 108 Get IAV Average Current Ulnt 466 LUCB C D of FLA Ratio LUCBT DT or LUCM LUCMT 109 Get Thermal Capacity Ulnt 465 LUCM LUCMT TripLevel Level 110 Get Ground Current Int Idem Att 11 LUCM
2. Attribute ID Access Name Data Type Value Description 1 Get Revision Ulnt 01 Instance Attributes Attribute ID Access Name Data Type Value Description 1 Get Object list Ulnt List of supported objects e Number Number of supported classes e Classes List of supported classes Get Number available Ulnt Maximum number of connections supported Get Number active Ulnt Number of active connections Get Active connections Struct of List of active connections Ulnt Ulnt Class and Instance Service Service Code Service Name Description OE hex Get Attribute Single Read 1 attribute 1744085 03 2009 83 Object Dictionary Assembly Object Description Class Attributes The Assembly Object binds attributes of multiple objects which enables each object s data to be sent or received over a single connection Assembly objects can be used to bind input data or output data The terms input and output are defined from the network s point of view An input sends produces data on the network and an output receives consumes data from the network Only static assemblies are supported Instance Attributes Class and Instance Service Output Assembly Data
3. Attribute ID Access Name Data Type Value Description 1 Get Revision Ulnt 01 Attribute Access Name Data Value Description ID Type 1 Get State USInt 0 Non existent 3 Established 5 Deferred Delete Get Instance type USInt 0 Explicit Message 3 Get TransportClass trigger USInt 83h Defines behavior of the connection 4 Get Produced connection id UInt 10xxxxxx xxxxxx Node address 011 5 Get Consumed connection id Ulnt 10 ooxxx xxxxxx Node address 100 6 Get Initial_comm_characteristics USInt 21h Explicit messaging via Group 2 7 Get Produced connection size Ulnt 7 8 Get Consumed_connection_size Ulnt 7 9 Get Set Expected_packet_rate Ulnt 2500 2 5 sec TimeOut 12 Get Set Watchdog_timeout_action Ulnt 1or3 1 Auto Delete Default 3 Deferred Delete 13 Get Produced connection path length Ulnt 0 14 Get Produced connection path Ulnt Null empty 15 Get Consumed connection path length Ulnt 0 16 Get Consumed connection path Ulnt Null empty 88 1744085 03 2009 Object Dictionary Instance 2 Attributes Polled I O Message Instance Attribute Access Name Data Value Description ID Type 1 Get State USInt 0 Non existent 1 Configuring 3 Established 4 TimeOut Get Instance type USInt 1 1 0 Message Get TransportClass trigger USInt 82h Class 2 Get Produced connection id UlInt 01111xxx
4. LUBee See LUTMee LU2Bee 2Se base base Fiellox Motor spinning direction Value function p g of Regs Output Outputs Outputs LO1 OA1 13 OAS3 23 Reflex1 Fw forward run 8 Reflexi Reg 685 Reg 686 Reg 687 Reflex1 Rev reverse run 9 2 2007 25 2007 26 2007 24 LSB LSB Bs Reflex2 Fw forward run 10 LSB LSB LSB eflex Reflex2 Rev reverse run 11 MSB MSB NOTE Before using a reflex stop function you need to assign outputs OA1 OA3 to forward reverse run Do it in register 686 2007 25 By default OA1 is assigned to forward run and OAS to reverse run Reflex1 Fw This function is enabled on rising edge not on level Fw LI1 1 makes the motor stop whatever the running direction After a new running order a stop order followed by a run order even though logic input LI1 1 the motor starts again in the chosen direction NOTE Logic input LI2 is not used Reflex1 Rev This function is enabled on rising edge not on level Rev LI1 1 makes the motor stop whatever the running direction After a new running order a stop order followed by a run order even though logic input LI1 1 the motor starts again in the chosen direction NOTE Logic input LI2 is not used 76 1744085 03 2009 Configuration of Predefined Functions Reflex2 Fw Reflex2 Rev This function is enabled on rising edge not on l
5. DeviceNet Bit Description Possible values Acvancog Multifunction path Control Unit Control Unit Reset mode after thermal overload fault bits 0 2 1 bit is set to 1 602 0 Manual default value 1 Y Y 602 1 Remote or multifunction control unit keypad Y Y 602 2 Automatic V Y 602 3 Control Unit communication parity Y 0 none default 1 even 602 4 Communication control enabled disabled Y 6A 1 03 0 disabled 1 enabled default Multifunction control unit port watchdog bits 5 8 1 bit is set to 1 Y 602 5 Ignored default value 1 Y 602 6 Warning Y 602 7 Drop out Y 602 8 Trip Y 602 9 to Reserved Y 602 15 Communication Loss Fallback strategy Communication loss fallback strategy parameter register 682 or DeviceNet path 6B 1 21 is used to adjust the fallback mode in case of a communication loss with the PLC Register 682 Value Fallback Mode 0 Ignored 1 Freeze outputs 2 Stop 3 Signal comm loss warning 4 Force run forward 5 Force run reverse 4 WARNING AUTOMATIC RESTART OF THE MOTOR If communication is stopped the outputs OA1 OA3 take the status corresponding to the selected fallback mode register 682 but the control bits 704 0 and 704 1 are not modified When a loss of communication warning is acknowledged register 703 or pushbutton on the controller the motor will automatically restart if the control bits
6. Word 3 DeviceNet path 68 1 C Sc St C Ad C Mu L R Sc Ad Sc Mu L R bit 0 1 Non significant bit 2 Ground fault warning Y bit 3 Thermal warning Y bit 4 Long start warning V V bit 5 Jam warning y bit 6 Phase imbalance warning V bit 7 Under current warning Y bit 8 9 Non significant bit 10 Communication loss on LUCMT Modbus port Y bit 11 Internal temperature warning V bit 12 Module identification or internal communication warning V bit 13 14 Non significant bit 15 Module warning V Y Y The following table gives a description of the I O Status of the Controller Base Register 459 Word 4 DeviceNet path 68 1 A CAd CMuL R bit O 1 1 local control of output 13 Y Y bit 1 1 2 local control of output 23 Y Y bit 2 1 3 contactor status on output 13 Y Y bit 3 1 4 contactor status on output 23 Y Y bit 4 1 5 input status reset Y Y bit 5 1 6 input status external fault Y Y bit 6 1 7 input status system ready Y Y bit 7 1 8 input status free Y V bit 8 1 9 input status free Y Y bit 9 1 10 input status in local remote mixed mode if 683 2 otherwise free Y Y bit 10 11 Non significant bit 12 Output 13 status 1 01 closed Y Y bit 13 Output 23 status 1 O2 closed Y Y bit 14 Outputs 95 96 and 97 98 status 1 95 96 closed and 97 98 opened Y Y bit 15 Output 05 06 status 1 05 06 closed Y Y 1744085 03 2009
7. 1744085 03 2009 73 Managing faults and warnings Warnings Communication Loss Warning Acknowledgement List of possible warnings unit Registers LULCO9 LUCM LUTM 460 461 R ERE warning number warning bit CE EX XE 2000099 _ warning Warnings 14 a acknowledgement aooe I 4 ERR line 1 FAULT Warning on thermal Wrng Aem when ov rload 4 3 1 overload overload is lower than 85 Acknowledgement aningen ec communication loss 109 14521 5 Comm loss 9 with the master lt adye andimust be i reset to 0 by programming Warning on LUCMe multifunction control 2 and 4 to 13 See LUCM LUCMT Multifunction Control Unit User s Manual Recovery after Communication Loss Following an acknowledgement by setting bit 703 3 to 1 recovery occurs depending on the status of control bits 704 0 and 704 1 74 1744085 03 2009 Configuration of Predefined Functions Overtravel Limit Switch Communication Module Reflex Functions Introduction The Overtravel Limit Switch allows you to perform precise and iterative positionings without any interaction of bus or PLC cycle time It is a module function initiated at the LULCO9 communication module level There are two types of functions e Reflex1 Communication module reflex stop 1 function e Reflex2 Communication module reflex stop 2 function Description
8. DeviceNet path Register Value Comment 690 0 Automatic identification 6B 1 29 1 Forced to LUCB C D 2 Forced to LUCM 1744085 03 2009 61 DeviceNet Communication Module Management Assignment of Outputs LO1 OA1 OA3 13 23 This table describes the assigned values to configure outputs LO1 OA1 OA3 13 and 23 Value Description of assigned value LUCBT LUCMT LUCDT 0 The corresponding output is forced to 0 OV Y Y 1 The corresponding output is forced to 1 24V V V 2 State of register 700 bits 0 4 V V 700 0 gt LO1 700 1 gt OA1 700 2 gt OA3 700 3 gt 13 700 4 gt 23 3 452 3 Thermal overload fault Y Y 4 461 3 Thermal overload warning Y Y 5 457 0 System ready Y Y 6 457 1 Y y 7 State of bit 457 2 Y Y 8 The corresponding output copies the result of Reflex stop 1 forward Y Y 9 The corresponding output copies the result of Reflex stop 1 reverse Y Y 10 The corresponding output copies the result of Reflex stop 2 forward V V 11 The corresponding output copies the result of Reflex stop 2 reverse V V 12 The corresponding output copies the result of Forward direction default V Y OA1 value 13 The corresponding output copies the result of Reverse direction default V Y OAS value 14 452 0 Short circuit fault Y Y 15 452 1
9. Attribute ID Access Name Data Type Value Description 1 Get Revision Ulnt 02 2 Get Max instance UInt 13 Attribute ID Access Name Data Type Value Description 3 Get Data See assembly data description below Service Code Service Name Description OE hex Get_Attribute_Single Read 1 attribute Instance 2 Basic Overload Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Reserved Reserved Reserved Reserved Reserved FaultReset Reserved Reserved Instance 3 Basic Motor Starter Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Reserved Reserved Reserved Reserved Reserved FaultReset Reserved Run 1 Instance 4 Extended Contactor Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Reserved Reserved Reserved Reserved Reserved Reserved Run 2 Run 1 Instance 5 Extended Motor Starter Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Reserved Reserved Reserved Reserved Reserved FaultReset Run2 Run 1 NOTE e FaultReset Register 704 3 e Run2 Register 704 1 e Runt Register 704 0 Instance 100 TeSys U Control Registers This assembly contains several control registers commonly used with a TeSys U device Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 path 6C 01 05 path 6C 01 04 path 6C 01 01 Register 704 Register 703 Register 700 LSB least significant bit MSB most significant bit LSB MSB LSB MSB Instance 101 PKW Request Object
10. eee eee eee eee 69 Viewing a fault 2 3 LER RARE ERRARE Ru ERU GU AGO EDEN ESI Ride EUH 70 Application faults e enc ahaa bets Sar Set PES VIEN S Rb Vacs b kd e 71 Internal Faults eem vvREEEEPASLRE4UME het pit ERE ater e eR MER RUERRR 73 Warnings Communication Loss lslsseeee ee 74 Chapter 5 Configuration of Predefined Functions ssse 75 Overtravel Limit Switch Communication Module Reflex Functions 5 75 idein 79 Appendix A Object Dictionary seeseeeee ii 81 Identity Object 2552665 eosdem ciet reti Lira ciate uds pomis pee UL cte cd qe 82 Message Router Object lilisssesseleleseeee hr 83 Assembly Object T cos kvAecUskeOLeeE e Uu peg Uere x EOD AMETE 84 DeviceNet Object rk exe ui uet 3G Bike EI De STA RO RUEDA EE RC eed rc 87 Connection Object ese e rene en uper re eR AU PO E NUR Es 88 Control Supervisor Object l liiis e 91 Overload Object ov card Si i EI eee eem me eid ee e io ih Y Ree dote 94 DeviceNet Interface Object 0 0 cette ete 96 Index cs E et n i ia need ADR ee RUE OLOR e Gage adt wale TR Aaaa a ee abla 99 1744085 03 2009 3 1744085 03 2009 Safety Information c Important Information NOTICE PLEASE NOTE Read these instructions carefully and look at the equipment to become familiar with the device before trying to install operate or maintain it The following special messages may appear throug
11. 28 Maxi t NALE A 1 5 at 55 C 131 F drawn Resistance to micro ms 3 cuts against overvoltage Yes Protection against reverse polarity Yes 1744085 03 2009 29 Technical Characteristics 24V Bus Technical characteristics of 24V bus for LULCO9 DeviceNet communication module include Unominal V 24V Supply voltage Operating range V 20 28 Maxi t aximum curren A 0 06 drawn Resistance to micro ms 3 cuts against overvoltage Yes Protection against reverse polarity Yes OA OA3 and LO1 Logic Outputs Output characteristics of an LULCO9 DeviceNet communication module include change in the output state Voltage V 24V Nominal output values Current mA 500 Voltage V 20 28 Output limit values Current mA 700 Coincidence factor of 100 the 3 outputs Output response time register 704 Time duration between the request start bit and the ms 10 OA1 OA3 LO1 Protection Against short circuits and overloads Electronic circuit breaker with automatic reset Number of operating cycles In millions 15 Maximum rate In operating cycles per hour 3600 LI1 and LI2 Logic Inputs Intput characteristics of an LULCO9 DeviceNet communication module include AV iti Voltage V 2 l positive logic Nominalinput values Maximum voltage
12. Any changes in the function field will trigger the handling of the request except if Function code 0x00 Toggle bit must change at each consecutive request This mechanism allows the request initiator to detect that a response is ready by polling the toggle bit in response When this bit in the OUT data becomes equal to the response emitted toggle bit in the IN data then the response is ready 1744085 03 2009 65 DeviceNet Communication Module Management PKW IN Data PKW IN Data Response TeSys U device gt DeviceNet Master are mapped in modules supporting PKW The TeSys U device echoes the same register address and function code or eventually an error code Word 1 Word 2 Word 3 Word 4 Register address Toggle bit Function bits Not used Data to write bit 15 bits 8 to 14 bits O to 7 Same register Same as request ERROR 0x00 Error code number as in request Code Ox4E R REG 16 Data read in register Code 0x25 R REG 32 Data read in register 1 Data read in register 2 Code 0x26 W REG 16 2 E Code 0x2A W REG 32 i Code 0x2B Depending on the PLC platform used refer to the PKW IN description in Little and Big endian formats to know the positioning of each field inside each word If the initiator tries to write a TeSys U object or register to an unauthorized value or tries to access an inaccessible register an error code is answered Function code toggle bit Ox4E
13. 6A 1 08 607 Thermal reset time 6A 1 09 608 Thermal reset threshold 6A 1 0A 609 Thermal warning threshold 6A 1 0B 610 Ground fault trip timeout 6A 1 0C 611 Ground fault trip threshold 6A 1 0D 612 Ground fault warning threshold 6A 1 0E 613 Phase imbalance trip timeout at start up 6A 1 0F 614 Phase imbalance trip timeout while running 6A 1 10 615 Phase imbalance trip threshold 6A 1 11 616 Phase imbalance warning threshold 6A 1 12 617 Jam trip timeout 6A 1 13 618 Jam trip threshold 6A 1 14 619 Jam warning threshold 6A 1 15 620 Undercurrent trip timeout 6A 1 16 621 Undercurrent trip threshold 6A 1 17 622 Undercurrent warning threshold 6A 1 18 623 Long start trip timeout 6A 1 19 624 Long start trip threshold 6A 1 1A 625 Long start warning threshold 6A 1 1B 23 626 634 Reserved 6B 1 01 650 Display language 6B 1 02 651 Display of running items 6B 1 03 652 Full Load Amps setting FLA max 6B 1 04 1E 653 679 Reserved 6B 1 1F 680 Communication module identification code setting 6B 1 21 682 Communication loss fallback strategy 6B 1 22 683 Local Remote control 6B 1 23 684 Inversion of output configuration 6B 1 24 685 Output LO1 configuration 6B 1 25 686 Outputs OA1 and OAG configuration 6B 1 26 687 Reserved 6B 1 27 688 Recovery mode 6B 1 29 690 Disable auto identification 1744085 03 2009 55 DeviceNet Communication Module Management Parameters for TeSys U Sc St The following table gives the des
14. B e Vendor amp D Rockwell Automation Allen Bradley Unknown Device Type 126 Rockwell Automation Electro Craft Motion Control Rockwell Automation Reliance Electric Rockwell Automation Entek Ird Intl Rockwell Automation Sprecher Schuh Schneider Automation Inc 1747 SDN Scanner Module TeSys U Sc Mu R B Motor Starter jo TeSys U Sc MuR M4 M Graph Spreadsheet 4 la Ready Offline 40 1744085 03 2009 DeviceNet Communication Module Management Read and Write TeSys U Motor Starter Parameters To read and write to the controller s parameters Step Action Comment starter icon 1 From the project view double click on the motor The motor starter configuration screen appears 2 Select the Parameter tab The parameter lists appears Select Group View The parameter groups appear configuration parameters parameters Select the configuration group to access motor starter Select Setting group to access motor starter setting See TeSys U Communication Variables User s Manualftor a complete list of configuration and setting parameters from or write to it 5 Select the parameter you want to access and read Write access to parameters is not available with the variants TeSys U Sc Mu L and TeSys U C MuL which preserve local configurations The TeSys U Motor Starter Parameter Screen
15. The exact error code can be found in words 3 and 4 The request is not accepted and the object or register remains at the old value If you want to re trigger exactly the same command you must e reset the Function code to 0x00 e wait for the response frame with the function code equal to 0x00 then e set it again to its previous value This is useful for a limited master like an HMI Another way of re triggering exactly the same command is to e invert the toggle bit in the function code byte The response is valid when the toggle bit of the response is equal to the toggle bit written in the answer this is a more efficient method but it requires higher programming capabilities 66 1744085 03 2009 DeviceNet Communication Module Management PKW Error Codes Case of a write error Error Code Error Name Explanation 1 FGP_ERR_REQ_STACK_FULL external request sends back an error frame 3 FGP_ERR_REGISTER_NOT_FOUND register not managed or the request needs super user access rights FGP_ERR_ANSWER_DELAYED external request answer postponed FGP ERR NOT ALL REGISTER FOUND one or both registers cannot be found FGP ERR READ ONLY register not authorized to be written 10 FGP ERR VAL 1WORD TOOHIGH written value not in the range of the register word value is too high 11 FGP ERR VAL 1WORD TOOLOW written value not in the range of the register word value is too l
16. 2 5 mm 24 12 AWG 2 solid conductors 0 2 1 mm 24 18 AWG 2 stranded conductors 0 2 1 5 mm 24 16 AWG aan 2 stranded conductors with cable end non insulated 0 2 1 mm 24 18 AWG insulated 0 5 1 5 mm 20 16 AWG Connectors 5 pins Pitch 5 08 mm 0 12 in Tightening torque 0 5 0 6 N m 4 42 5 31 Ib in Flat screwdriver 3 5 mm 0 14 in 22 1744085 03 2009 Installation of TeSys U DeviceNet Module LULCO9 Connection to the DeviceNet Bus General Characteristics of a DeviceNet Connection The following table provides general characteristics of a connection to the DeviceNet bus Characteristics Description Type of communication protocol ODVA DeviceNet specification Vol 1 Release 2 0 and Vol 2 Release 2 0 Type of hardware interface CAN 2 0 A 2 0 B passive Baud rate 125 500 kbaud Maximum connection distance Depending on the baud rate see Maximum Network Lengths page 26 to 1 master Maximum number of slaves connected 63 Connector type Open style terminal connector Cable structure 2 pairs with separate shielding and a different gauge Shielding is aluminium foil tinned copper braid drain EMC protection See the TSX DG KBL F Guide Electromagnetic compatibility of industrial networks and fieldbuses Electrical Interface The DeviceNet bus uses two twisted pairs to transmit e the d
17. Get Product code Ulnt Product identification Remote mode depends on the Sc St gt 0x11 configuration e Sc Ad gt 0x12 e Sc Mu gt 0x13 e C Ad 5 0x22 e P2 Mu 0x23 Local mode e Sc Mu 0x0113 e C B2 0x0123 4 Get Revision Struct of Product configuration Product version Ulnt Ulnt Get Status Word 01 See the table below Get Serial number UDInt Unique number Read from the EEPROM during start up 7 Get Product name Struct of LULCO9 Read from the controller during start USInt up in registers 64 to 69 String Control Unit Identification Attribute 5 status Bit Definition Values 0 Owned by Master predefined Provided by the stack Master Slave connection 1 Reserved 0 2 Configured NOT 601 0 3 Reserved 0 4 5 6 7 Vendor Specific 4 Warning 455 3 5 Trip Fault 455 4 6 Contactor state 455 1 amp 704 1 7 Reverser contactor state 455 1 amp 704 2 8 Minor recoverable fault 0 9 Minor unrecoverable fault 0 10 Major recoverable fault 1 lt 451 lt 15 11 Major unrecoverable fault 451 lt 15 Service Code Service Name Description OE hex Get Attribute Single Read 1 attribute 05 hex Reset Product reset 82 1744085 03 2009 Object Dictionary Message Router Object Description The Message Router Object provides a messaging connection point through which a Client may address a service to any object class or instance in the physical device Class Attributes
18. Overcurrent fault Y Y 16 452 2 Ground fault N 17 452 3 Thermal overload fault V Y 18 452 4 Long start fault Y 19 452 5 Mechanical locking jam fault Y 20 452 6 Phase imbalance fault Y 21 452 7 Underload fault Y 22 452 8 Shunt trip Y 23 452 9 Test trip Y 24 452 10 Communication loss fault on LUCMT Modbus port Y 25 452 11 Control unit internal fault V V 26 452 12 Module identification or internal communication fault V 27 452 13 Module internal fault Y Y 28 31 Reserved 32 461 2 Ground fault warning N 33 461 3 Thermal overload warning Y Y 34 461 4 Long start warning Y 35 461 5 Mechanical locking jam warning Y 36 461 6 Phase imbalance warning Y 37 461 7 Under current warning Y 38 39 Reserved 40 461 10 Communication loss on LUCMT Modbus port Y 41 461 11 Internal temperature warning Y 42 461 12 Module identification or internal communication warning Y 43 44 Reserved 45 461 15 Module warning Y Y 62 1744085 03 2009 DeviceNet Communication Module Management PKW Objects Overview The TeSys U motor starter supports PKW Periodically Kept in acyclic Words The PKW feature consists of two 8 byte objects the Periodic Registers Service Objects C5h These objects enable a DeviceNet master to read or write any manufacturer specific register class 0x64 to 0x81 using cyclic I O messaging The 8 bytes of the objects are interpreted as a request telegram or respo
19. V 28V Current mA 7 Voltage V 16 State 1 Current mA 6 Input limit values Voltage V 5 State 0 Current mA 2 To state 1 ms 10 30 Response time To state 0 ms 10 30 Input type Resistive Protection gl fuse A 1 Communication DeviceNet Port Technical characteristics of DeviceNet port for the LULCO9 communication module include Physical interface 1 CAN Connector Open style connector Pinout According to the DeviceNet specification see DeviceNet Open Style Connector page 24 Protocol CAN 2 0 and CAN 2 B passive mode Address Range 1 to 63 default 63 Transmission speed Kbit s 125 default 250 500 or Autobaud 30 1744085 03 2009 Software Implementation Hardware implementation of an LULCO9 DeviceNet communication module is being followed by its software implementation It is focused on configuration the different operating modes and functions setting e g protection current measurement What s in this Part This part contains the following chapters Chapter Chapter Name Page 3 DeviceNet Communication Module Management 33 4 Managing faults and warnings 69 5 Configuration of Predefined Functions 75 1744085 03 2009 31 Software Implementation 32 1744085 03 2009 DeviceNet Communication Module Management 3 Introduction to DeviceNet Bus A TeSys U motor starter equipped with the LULCO9
20. 3 PKW IN 3 2 PKW IN2 1 PKW IN 1 0 PKRWINO 3 PKW OUT 3 2 PKW OUT 2 1 PKW OUT 1 0 PKW OUT 0 7 PKW IN 7 6 PKWIN6 5 PKWIN5 4PKWIN4 7 PKW OUT 7 6 PKW OUT 6 5 PKW OUT 5 4 PKW OUT 4 11 10 9 8 11 10 9 8 15 14 13 12 18 12 Function Object Object address Function Object Object address code address code address Value 2 Value 1 Value 2 Value 1 Reg 458 Reg 455 Reg 703 Reg 704 Reg 457 Reg 461 Reg 700 64 1744085 03 2009 DeviceNet Communication Module Management PKW OUT Data PKW OUT Data request DeviceNet Master gt TeSys U device are mapped in modules supporting PKW To access a register you must select 1 of the following function codes e R_REG_16 0x25 to read 1 register e R_REG_32 0x26 to read 2 registers e W_REG_16 0x2A to write 1 register e W REG 32 OX2B to write 2 registers Register numbers are given in TeSys U Communication Variables User s Manual Word 1 Word 2 Word 3 Word 4 Register address Toggle bit Function bits Not used Data to write bit 15 bits 8 to 14 bits O to 7 Register number 0 1 R REG 16 0x00 z Code 0x25 R_REG_32 e Code 0x26 W_REG_16 Data to write in Code 0x2A register W_REG_32 Data to write in Data to write in Code 0x2B register 1 register 2 Depending on the PLC platform used refer to the PKW OUT description in Little and Big endian formats to know the positioning of each field inside each word
21. 49 DeviceNet Communication Module Management The following table gives a description of the Mechanical and Power Supply Status Register 457 Word 4 DeviceNet path 68 1 8 ScSt CAd CMuL R Sc Ad Sc Mu L R bit 0 Button position On 0 Off Y Y V bit 1 Button position Trip 0 Not tripped Y Y V bit 2 Contactor state On Y Y Y bit 3 24 VDC power supply present on outputs Y Y V bit 4 15 Non significant Instance 111 PKW Response Object This assembly is vendor specific It is used to implement the response object of PKW protocol Byte 7 Byte 6 Byte 5 Byte 4 Byte 3 Byte 2 Byte 1 Byte 0 See PKW Objects page 63 for details Instance 112 PKW Response and Extended Motor Starter This assembly is vendor specific Bytes 0 to 7 Byte 8 Byte 9 See Instance 111 above Reserved value 0 See Instance 54 above Instance 113 PKW Response and TeSys U Monitoring Registers This assembly is vendor specific Bytes 0 to 7 Byte 8 to 15 See Instance 111 above See Instance 110 above Create a Customized EDS File Devices that do not correspond to specific EDS files during online network browsing will appear in the project view as Unrecognized Devices If your motor starter is not recognized you must create an EDS using the following procedure Ste
22. 500ms Faulted state MNS LED Blink Patterns Below is a representation of the MNS LEDs showing the different colors and flashing rates 500ms 500ms 500ms 500ms Flash Green 500ms 500ms 500ms 500ms Flash Red 500ms 500ms Flashing S Green Red 500ms 500ms 14 1744085 03 2009 Installation of TeSys U DeviceNet Module LULCO9 Error ERR LED The signalling is active provided that the communication module is powered up by the Bus DeviceNet external power supply The red error ERR LED has 3 different states Error LED Meaning Action Off Working condition No error On Presence of an internal fault See Internal Faults page 73 Blinking Loss of communication Check the cabling of your DeviceNet network A fallback strategy is in progress 24V LED The green 24V LED has 2 different states Off 24V Bus or 24V power is missing On LULCO9 communication module is correctly powered Bottom View of the Module Here is a bottom view of an LULCO9 communication module TUTTO o E 8 Baud rate switches SW7 and SW8 Address switches SW1 to SW6 Power base connector DeviceNet bus connector 24V and I O connector np 1744085 03 2009 15 Installation of TeSys U DeviceNet Module LULC
23. Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Reserved Reserved Reserved Reserved Reserved FaultReset Reserved Reserved Instance 3 Basic Motor Starter Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Reserved Reserved Reserved Reserved Reserved FaultReset Reserved Run 1 Instance 4 Extended Contactor Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Reserved Reserved Reserved Reserved Reserved Reserved Run 2 Run 1 Instance 5 Extended Motor Starter Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Reserved Reserved Reserved Reserved Reserved FaultReset Run 2 Run 1 NOTE e FaultReset Register 704 3 e Run2 Register 704 1 e Runi Register 704 0 Instance 100 TeSys U Control Registers This assembly contains several control registers commonly used with a TeSys U device Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 path 6C 01 05 path 6C 01 04 path 6C 01 01 Register 704 Register 703 Register 700 LSB least significant MSB most significant LSB MSB LSB MSB bit bit The following table gives a description of the Control Register 704 A WARNING AUTOMATIC RESTART OF THE MOTOR The motor will automatically restart if the control bits 704 0 or 704 1 were not previously overwritten to zero by the PLC application in case of a cyclic writing to register 704 and on the occurrence of one of the following events e Loss followed by restoration of the outputs power supply 24 VDC e Change in
24. DeviceNet Interface Group 2 For the PollProdPath parameter select the input PollProdPath consists of data produced by the motor assembly object you want the motor starter to starter on polling sent by the scanner produce 3 For the PollConsPath parameter select the output PollConsPath consists of data sent by polling by the assembly object you want the controller to consume scanner and consumed by the Controller 4 For the COSProdPath parameter select the input COSProdPath consists of data produced by the assembly object you want the motor starter to controller on Change of State COS produce 5 If you selected input assembly object 110 or 113 in Only used with instances 110 and 113 steps 2 or 4 adjust the Monitoring Word O to 3 to the register you want the controller to produce Upload and Download Device Configurations After the online connection of devices you must transfer the required device information Use the following options from the Device menu to transfer the configurations of only selected devices e Download to Device Transfer the offline configuration from the PC to the device e Upload from Device Transfer the configuration from the device to the PC Use the following options from the Network menu to transfer the configurations of all online devices in the project view e Download to Network Transfer the offline configurations from the PC to all online devices e Upload from Network Transfer the
25. Level USInt 621 LUCM LUCMT 10 100 FLA 148 Get Set UL Warn Level USInt 622 LUCM LUCMT 10 100 FLA 149 Get Set Cl Inhibit Time USInt 613 LUCM LUCMT 0 250 Seconds 150 Get Set Cl Trip Delay USInt 614 LUCM LUCMT 0 1 25 0 Seconds 151 Get Set CI Trip Level USInt 615 LUCM LUCMT 10 100 FLA 152 Get Set Cl Warn Level USInt 616 LUCM LUCMT 10 100 FLA 178 Get CT Ratio USInt 628 630 629 LUTM LUCM LUCMT only NOTE In the table above PL Current Phase Loss GF Ground Fault Stall Long Start UL Underload Cl Current Phase Imbalance Calculation of current in Amps In the TeSys U mapping values of currents are given in FLA Here is the formula that must be used to convert them in Amps This formula must be used for both LUB 2B LUS 2S and LUTM bases CurrentInMapping FLA Set FLAmax and GroundCurrent Register_470 FLA Set FLAmin Where CurrentInMapping Registers 466 to 470 given in FLA LUTM FLA Set Register 652 given in of FLAmax FLAmax Register 96 stored in Amps FLAmin Register 96 stored in Amps divided by 4 with an LUB 2B LUS 2S or divided by 3 with an Registers 96 and 652 can be changed at any time therefore the module updates their values cyclically Service Code Service Name Description OE hex Get_Attribute_Single Read 1 attribute Service Code Service Name De
26. OA3 and LO1 To operate the LULCO9 DeviceNet communication module must be powered by a 24V internal power LUBee LUSee LU2Bee LU2S Power bases power up LE 1 MNS ERR 24V 24V LO L1 LI2 1 24V power supply terminal for outputs OA1 OA3 and LO1 2 Prewired coil connection for outputs OA1 and OA3 to terminals A1 A3 A2 on the starter LUTM Controller bases power up 24N Lo1 Lit Li2 1 1 24V power supply terminal for outputs OA1 OA3 and LO1 if required 2 24V power supply terminals for LUTM Power base Coil Terminals Power up You have 2 options for connecting the power base coil terminals e power supply via the LULCO9 DeviceNet communication module with a prewired link e direct power supply with a wire to wire link 20 1744085 03 2009 Installation of TeSys U DeviceNet Module LULCO9 Prewired link References of the 2 prewired coil connections Description with a Power Base Reference LUBee LUSee LU9B N11L Prewired Coil Connection LU2Bee LU2See LU9M RL Illustrations for both types of power bases LULCO9 LU9B N11L Wire to wire link supplying power from outputs OA1 and OAG to coil terminals A1 A2 and A3 This type of link is compulsory in the case of a reversing starter controller created from a separate LU6M reverse
27. PLC Check that the desired DeviceNet network node address and baud rate have been correctly set See Description and Installation of the Module page 13 This example uses an address of 15 Make connections with DeviceNet network cable and end connectors manufactured in accordance with ODVA specifications The cable and end connectors are not supplied Place the system on the network by connecting the PLC to the TeSys U Motor Starter with the DeviceNet cable Connect the RSNetWorx PC to the network using the DeviceNet cable Register the Motor Starter EDS To register the motor starter EDS in RSNetWorx s EDS library follow the procedure in the following table Step Action Comment 1 From the RSNetWorx Tools menu select EDS The Wizard s welcome screen appears Wizard Click Next The Options screen appears Select Register an EDS file s and click Next The Registration screen appears Select Register a directory of EDS files and Browse to You must have already unzipped the Zip file the controller s EDS file containing the EDS files and corresponding icons into a single directory 5 Click Next The EDS File Installation Test Results screen appears 6 Click Next The Change Graphic Image screen appears The TeSys U should be listed in the Product Types field as a motor starter Click Next The Final Task Summary screen appears Verify that the device has been
28. Register 461 Register 457 C Ad Path 68 01 06 Path 68 01 09 Path 68 01 0C Path 68 01 0A Register 455 Register 458 Register 461 Register 459 C Mu L R Path 68 01 06 Path 68 01 09 Path 68 01 0C Path 68 01 0A Register 455 Register 458 Register 461 Register 459 LSB MSB LSB MSB LSB MSB LSB MSB Any byte left vacant at the end of this assembly will not be sent to the bus so if no parameter is attributed to bytes 6 and 7 the assembly data length will be 6 bytes instead of 8 bytes 1744085 03 2009 47 DeviceNet Communication Module Management The following table gives a description of the Status Register 455 of the starter controller Word 1 DeviceNet path 68 1 6 Sc St ScAd Sc Mu L R bit 0 Ready Y Y V LUBee 2Bee the rotary handle is turned to On position and there is no fault LUSee 2See the push button is pressed and there is no fault bit 1 Pole status closed Y Y Y bit 2 All faults vV vV V bit 3 All warnings V V V bit 4 Tripped V V V LUBee 2Bee the rotary handle is turned to Trip position LUSee 2See the push button is depressed bit 5 Fault reset authorized V V bit 6 A1 A2 terminals powered up V bit 7 Motor running with detection of current if greater than 10 FLA V V bit 8 13 Average motor current V Y 32 100 FLA 63 20
29. TeSys U C Ad a controller up to 450kW for a 3 phase motor class 10 20 with an advanced control unit that protects against overloads and short circuits against phase imbalance and insulation breaks and offers a manual or remote automatic reset TeSys U C Mu R or TeSys U C Mu L a controller up to 450kW for a 3 phase motor class 5 30 with a multifunction control unit that protects against overloads and short circuits against phase imbalance and insulation breaks has function warnings log and monitoring functions fault differentiation overtorque and no load running monitoring and offers a manual automatic reset TeSys U Sc Ad a starter or a starter controller up to 15kW for a 3 phase motor class 10 or 20 or a 1 phase motor class 10 0 12 or 0 32A rating with an advanced control unit that protects against overloads short circuits phase imbalance and insulation breaks and offers a manual or remote automatic reset TeSys U Sc Mu R or TeSys U Sc Mu L a starter controller up to 15kW for a 1 phase or a 3 phase motor class 5 30 0 12 or 0 32A rating with a multifunction control unit that protects against overloads and short circuits against phase imbalance and insulation breaks has function warnings log and monitoring functions fault differentiation overtorque and no load running monitoring and offers a manual automatic reset TeSys U Sc St a starter or a starter controller up to 15kW for a 3 ph
30. TeSys U Control Registers All 6 101 PKW Request Object All 8 102 PKW Request and Extended Motor Starter All 10 103 PKW Request and TeSys U Control Registers All 14 1744085 03 2009 43 DeviceNet Communication Module Management Input assembly data size produced by the motor starter Instance Name TeSys U variant Number of bytes 50 Basic Overload All 1 51 Extended Overload All 1 52 Basic Motor Starter All 1 53 Extended Motor Starter 1 All 1 54 Extended Motor Starter 2 All 1 110 TeSys U Monitoring Registers with dynamic configuration TeSys U Sc St 6 TeSys U Sc Ad 7 TeSys U Sc Mu R L 8 TeSys U C Ad 8 TeSys U C Mu R L 8 111 PKW Response Object All 8 112 PKW Response and Extended Motor Starter All 10 113 PKW Response and TeSys U Monitoring Registers TeSys U Sc St 14 TeSys U Sc Ad 15 TeSys U Sc Mu R L 16 TeSys U C Ad 18 TeSys U C Mu R L 16 1 0 Messages Description l O Messages are used to exchange periodic I O data between the PLC and the TeSys U Motor Starter The tables below describe the data exchanges depending on the instance selected in the Assembly Object see page 84 44 1744085 03 2009 DeviceNet Communication Module Management Output Assembly Data Instance 2 Basic Overload Byte Bit 7 Bit 6 Bit 5
31. The TeSys U Motor Starter parameter screen should resemble the following figure 75 TeSysU Sc Mu R General Parameters vo Data EDs File ww Select the parameter that you want to configure and initiate an action using the toolbar Groups Bow I Parameter i 203 Long start trip timeout 5 j 204 Long start trip threshold i 205 Long start warning threshold Setting Display langage Display of running items Full Load Amps setting Comm module id code setting Comm loss fallback strategy Inversion of output config 212 Output LO1 configuration i 213 Outputs OA1 and OA3 corfig i 216 Recovery mode us TRIN Disable auto identification Control HMI monitoring lt i Current Value 00000000 00000001 00000000 00000001 25 FLA max 00000000 00000010 00001101 00001100 00000000 00000000 Automatic identification lt Help When you select a parameter selected parameters are highlighted in blue you can press the keys Ctrl H to access a Help screen that provides the register number Inversion of output contig Help Wrap word 684 Inversion of output config 1744085 03 2009 41 DeviceNet Communication Module Management Select Data Exchanged via I O Messaging To select data exchanged through I O messaging Step Action Comment 1 In the TeSys U Sc Mu R parameter screen select The parameter list appears
32. configurations of all online devices to the PC Add the Motor Starter to the Scanlist To be recognized on the network the motor starter must be added to the master scanner s Scanlist using the online procedure in the following table Step Action Comment 1 From the project view double click the scanner icon The Scanner Configuration screen appears 2 Select the Scanlist tab The Scanner Configuration Applet screen appears 3 Select Upload from scanner Wait for the Uploading from Scanner timer to finish 4 At the Scanlist tab highlight the motor starter at The motor starter now appears in the Scanlist MAC ID 15 in the Available Devices list and click the right arrow 5 With the motor starter selected click the Edit I O The Edit I O Parameters window appears Parameters button 6 Check Polled and enter 1 in the Input Size text field These are the default data sizes Determination of and 7 in the Output Size text field the device s input and output data lengths is described in the next paragraph Click OK The Edit I O Parameters window closes Click Download to scanner The Downloading Scanlist from Scanner window appears 9 Click Download Wait for the Downloading to Scanner timer to finish 10 Click OK The scanner properties window closes 42 1744085 03 2009 DeviceNet Communication Module Management The Edit I O Parameters Screen The motor starter s Edit I O P
33. multifunction control unit The configuration software is Rockwell s RSNetworx for DeviceNet configuration software The stages of this process are described in the following table Stage Description 1 Assemble the DeviceNet network see page 39 2 Register the controller s EDS files see page 39 3 Connect devices to your network see page 40 4 Upload the controller configuration see page 42 5 Add the controller to the Scanlist see page 42 Before you begin make sure e the TeSys U Motor Starter is fully assembled installed and powered according to your particular system application and network requirements e you have properly set the node address and baud rate of the controller See Bottom View of the Module page 15 for more information e you have the basic EDS files and corresponding ico files that are available at www schneider electric com or you have generated an EDS that is specific to the system assembly To configure the motor starter using RSNetWorx you must have a working familiarity with both the DeviceNet fieldbus protocol and RSNetWorx for DeviceNet version 3 21 00 The described procedures cannot practically anticipate every RSNetWorx prompt or option you may encounter during configuration Before assembling the network familiarize yourself with the required hardware connections The following figure shows the DeviceNet network connections between an Allen Bradley PLC the m
34. registered and click The completion screen appears Next 9 Click Finish The EDS Wizard closes 1744085 03 2009 39 DeviceNet Communication Module Management Connect Devices to Your Network This example requires you to add two devices to your project view e astarter controller up to 15 KW with a multifunction control unit configured in remote mode with the address 15 e aDeviceNet scanner in PLC slot 2 with the address 1 You can use RSNetWorx to configure the devices in either offline or online mode e offline The configuration tool and the physical network are not connected e online The configuration tool is connected to the physical network Build the network using the parameters transferred from devices on the physical network Connect to network connections using either the offline or online procedures in the tables that follow These are standard RSNetWorx procedures Offline Device Connection Use this procedure for adding devices to your network when the configuration tool is offline Step Action Comment 1 From the Hardware list double click on the EDS The new device appears in the project view The named TeSys U Sc Mu R under Schneider lowest available MAC ID has been assigned to it Automation Inc Motor Starter even if that ID is inappropriate Double click on the motor starter graphic The motor starter s properties window appears Change the MAC ID in th
35. requirements of the application Type Description of operation polled Aslave configured for polled I O receives output data from the master device This data is received in a sequential order that is defined by the master s scan list The master s polling rate is determined by the number of nodes in the scan list the DeviceNet baud rate the size of messages produced by the master and each node in its scan list and the internal timing of the master device cyclic A device configured to produce a cyclic I O message will produce its data at a precisely defined interval This type of I O messaging allows the user to configure the system to produce data at a rate appropriate for the application Depending on the application this can reduce the amount of traffic on the wire and more efficiently use the available bandwidth change of state A device configured to produce a change of state COS message will produce data whenever it changes or at a base heartbeat rate This adjustable heartbeat rate enables the consuming device to verify that the producer is still present and active on the network DeviceNet also defines a user configurable Production Inhibit Time that limits how often COS messages are produced to prevent nodes from flooding the bandwidth Users can adjust these parameters to provide optimum bandwidth utilization in a given application Idle Message Management When the DeviceNet module receives an Idle Mess
36. safety training to recognize and avoid the hazards involved 1744085 03 2009 1744085 03 2009 About the Book At a Glance Document Scope Validity Note Related Documents User Comments This manual describes the implementation functionalities and operation of the TeSys U DeviceNet communication module LULCO9 Field of application mainly automation systems in industry and building areas This manual is valid for LULCO9 V1 3 and later versions The Idle Message Management function is valid for LULCO9 V1 6 and later versions Title of Documentation Reference Number LULCOO9 DeviceNet Module Instruction Sheet 1639547 TeSys U Communication Variables User s Manual 1744082 LU B LU S TeSys U Starters Instruction Sheet 1629984 LUTMe TeSys U Controller User s Manual 1743233 LUTMe TeSys U Controller Instruction Sheet 1743236 LUCM LUCMT Multifunction Control Units User s Manual 1743237 LUCM LUCMT LUCBT LUCDT Control Units Instruction Sheet AAV40504 LUCA LUCB LUCC LUCD Control Units Instruction Sheet AAV40503 Electromagnetic Compatibility Practical Installation Guidelines DEG999 You can download these technical publications and other technical information from our website at www schneider electric com We welcome your comments about this document You can reach us by e mail at techcomm schneider electric com 1744085 03 2009 1744
37. switches off Signal comm loss warning reg 682 3 OA1 and OA3 keep their status OA1 and OAG keep their status On rising edge by bit 703 3 do not leave set to 1 ERR LED blinking on the front face ERR LED blinking on the front face Every new On Off command is considered and has an impact on OA1 and OA3 ERR LED switches off Force run forward reg 682 4 OA1 is forced to 1 OAS is forced to 0 OA1 is forced to 1 OA3 is forced to 0 On rising edge by bit 703 3 do not leave set to 1 ERR LED blinking on the front face ERR LED blinking on the front face Once the acknowledgement is done the last command stored in register 704 is enabled Every new On Off command is stored but with no impact on OA1 and OA3 ERR LED switches off Force run reverse reg 682 5 OA is forced to 0 OAS is forced to 1 OA1 is forced to 0 OAS is forced to 1 On rising edge by bit 703 3 do not leave set to 1 ERR LED blinking on the front face ERR LED blinking on the front face Once the acknowledgement is done the last command stored in register 704 is enabled Every new On Off command is stored but with no impact on OA1 and OA3 ERR LED switches off 1744085 03 2009 59 DeviceNet Communication Module Management Controller Local Remote Control Mode Controlling LUTM outputs 13 and 23 depends on the operating mode selected in register Cont
38. total data size exchanged through I O messages doesn t exceed the capacity of the DeviceNet scanner 1744085 03 2009 25 Installation of TeSys U DeviceNet Module LULCO9 Maximum Network Lengths End to end network distance varies with data rate and cable size The following table shows the range of bauds that the Controller supports for CAN devices and the resulting maximum length of the DeviceNet network Cable Type 125 kbits s 250 kbits s 500 kbits s Thick Trunk 500 m 250m 100 m Thin Trunk 100m 100m 100m Flat Trunk 420m 200m 75m Maximum Drop Length 6m 6m 6m Cumulative Drop Length 156m 78m 39m The sum of the length of all drop lines Network Model Like any broadcast communications network DeviceNet operates within a producer consumer model Each data packet s identifier field defines the data priority and allows for efficient data transfer among multiple users All nodes isten on the network for messages with identifiers that apply to their functionality Messages sent by producer devices will be accepted only by designated consumer devices DeviceNet supports polled cyclic change of state and explicit data exchange DeviceNet allows users to implement a master slave or multi master network architecture or some combination thereof depending on the device s flexibility and your application requirements Example of Architecture with TeSys U D i in A Power Pow
39. up 96 1744085 03 2009 Object Dictionary Instance Service Service Code Service Name Description OE hex Get_Attribute_Single Read 1 attribute 10 hex Set_Attribute_Single Write 1 attribute 1744085 03 2009 97 Object Dictionary 98 1744085 03 2009 Index A Acknowledgement application fault 77 internal fault 73 warning 74 Application faults 77 assembly object 84 Auto identification disable 61 baud range for devices 26 C CAN bus cable length 26 Communication loss 58 74 Conductor 21 22 configuration DeviceNet master 38 connection object 88 Connector Sub D 9 23 Connectors 13 Control mode 60 control supervisor object 91 Control unit 58 Control units LUC 12 Controller base 17 D DeviceNet 35 CAN based networks 25 connection based 35 data exchange 26 device profile 36 drop line 25 explicit message 35 I O message 35 messaging connections 35 network architecture 26 network length 26 network model 26 network topology 25 physical layer 25 trunk line 25 DeviceNet interface object 96 DeviceNet port 30 Disable auto identification 67 E EDS 36 Electrical connection 18 electronic data sheet EDS 36 error codes PKW 67 F Fallback mode 58 Faults 70 Inputs 30 Internal faults 73 L LED 13 14 Link prewired 27 wire to wire 27 LUCA 12 LUCB C D 12 LUOM
40. xxxxxx Node address XXX 5 Get Consumed_connection_id UlInt 10OXxxxxx Xxxxxx Node address 101 6 Get Initial_comm_characteristics USInt 01h Group1 Group 2 7 Get Produced_connection_size UlInt 4 8 Get Consumed connection size UlInt 4 9 Get Set Expected packet rate UInt 0 12 Get Set Watchdog timeout action USInt 0 10r2 0 Transition to TimeOut 1 Auto delete 2 Auto reset 13 Get Produced connection path length Ulnt 14 Get Set Produced connection path UInt 15 Get Consumed connection path Ulnt length 16 Get Set Consumed connection path UInt 17 Get Set Production inhibit time Ulnt 0 Minimum time between new data production 1744085 03 2009 89 Object Dictionary Instance 4 Attributes Change of State Cyclic Message Instance Attribute Access Name Data Value Description ID Type 1 Get State USInt 0 Non existent 1 Configuring 3 Established 4 TimeOut Get Instance type USInt 1 I O Message Get TransportClass trigger USInt Xx Get Produced connection id UInt 01101xxx xxxxxx Node address XXX 5 Get Consumed_connection_id Ulnt 10xxxxxx xxxxxx Node address 101 6 Get Initial comm characteristics USInt 01h Group1 Group 2 7 Get Produced connection size UInt 4 8 Get Consumed connection size UInt 4 9 Get Set Expected_packet_rate Ulnt 0 12 Get Set Watc
41. 0 FLA bit 14 Non significant Y Y V bit 15 Start in progress V V 1 ascending current is greater than 10 FLA 0 descending current is lower than 150 FLA The following table gives a description of the Status Register 455 of the Controller Word 1 DeviceNet path 68 1 6 CAd CMuL R bit 0 Ready Y Y LUTM is powered on and there is no fault with the communication module 1 7 powered on bit 1 Input 1 3 or 1 4 powered on V V bit 2 All faults V V bit 3 All warnings V V bit 4 Tripped if thermal overload fault reset mode manual V V bit 5 Fault reset authorized V V bit 6 1 1 and 1 2 powered on V bit 7 Motor running with detection of a current if greater than 10 FLA V V bit 8 13 Average motor current V V 32 100 FLA 63 200 FLA bit 14 In local control V V bit 15 Start in progress V V 1 ascending current is greater than 10 FLA 0 descending current is lower than 150 FLA For LUCBT DT timeout is 10s For LUCMT refer to LUCM MT User s Guide The following table gives a description of the I O Module Status Register 458 Word 2 DeviceNet path 68 1 9 ScSt CAd CMuL R Sc Ad Sc Mu L R bit 0 OA status Y V V bit 1 OAS status Y V V bit 2 LO1 status V V V bit 3 7 Non significant bit 8 LI1 status Y Y V bit 9 LI2 status V V V bit 10 15 Non significant 48 1744085 03 2009 DeviceNet Communication Module Management The following table gives a description of the Warning Register 461
42. 085 03 2009 Hardware Implementation This part describes the installation and technical characteristics of a TeSys U DeviceNet communication module LULCO9 What s in this Part This part contains the following chapters Chapter Chapter Name Page 1 Installation of TeSys U DeviceNet Module LULCO9 11 2 Technical Characteristics 29 1744085 03 2009 9 Hardware Implementation 10 1744085 03 2009 Installation of TeSys U DeviceNet Module LULCO9 1 This chapter introduces TeSys U DeviceNet communication module named LULCO9 and describes the different physical installation steps of the product There are different possible configurations that will be described in this chapter What s in this Chapter This chapter contains the following topics Topic Page Presentation of LULCO9 DeviceNet Communication Module 12 Description and Installation of the Module 13 Electrical Connection 18 Connection to the DeviceNet Bus 23 DeviceNet Network Connection 25 1744085 03 2009 11 Installation of TeSys U DeviceNet Module LULCO9 Presentation of LULCO9 DeviceNet Communication Module Reception of the Product Product Functions Data Available When opening the LULCO9 DeviceNet communication module box you will find two items e An Instruction Sheet IS giving brief and illustrated information about the basic installation of a module e An LULCOO9 D
43. 12 19 M Module bottom view 15 front view 13 mounting order 17 N network length 26 1744085 03 2009 99 Index O object DeviceNet interface 96 objects assembly 84 connection 88 control supervisor 91 DeviceNet 87 identity 82 message router 83 overload 94 Output setting 60 Output on illustration 13 Output status revert 60 Outputs 30 overload object 94 Overtravel limit switch 75 P Periodic Registers Service Objects 63 PKW 63 Periodic Registers Service Objects 63 PKW error codes 67 Power base 17 Power supply 18 20 20 29 30 Power up 19 producer consumer model 26 product dimensions 29 Product functions 12 R Reception of the product 12 Reflex1 75 Reflex2 76 Revert output status 60 RSNetworx 38 S Setting output 60 Sub D 9 connector 23 W Warning 74 100 1744085 03 2009
44. 1744085 TeSys U LULCOO9 DeviceNet Communication Module User s Manual 03 2009 me or Sim 440 000 LULCOS wm MNS ERR 24V DeviceNet i OA3 OA1 COM Li Lo1 LM UT 715 Schneider www schneider electric com ES E ec t r i C Schneider Electric assumes no responsibility for any errors that may appear in this document If you have any suggestions for improvements or amendments or have found errors in this publication please notify us No part of this document may be reproduced in any form or by any means electronic or mechanical including photocopying without express written permission of Schneider Electric All pertinent state regional and local safety regulations must be observed when installing and using this product For reasons of safety and to help ensure compliance with documented system data only the manufacturer should perform repairs to components When devices are used for applications with technical safety requirements the relevant instructions must be followed Failure to use Schneider Electric software or approved software with our hardware products may result in injury harm or improper operating results Failure to observe this information can result in injury or equipment damage 2009 Schneider Electric All rights reserved 1744085 03 2009 Table of Contents Safety Information 22 css RR RRER IRI RRRETERTRS 5 About the BOOK
45. 3 2009 Technical Characteristics Service Conditions and Technical Characteristics LULCO9 DeviceNet communication module characteristics include e Service conditions e 24V and 24V internal power supply circuit characteristics e Logic outputs OA1 OA3 and LO1 and logic inputs LI1 et LI2 characteristics Communication characteristics module port are also described Service Conditions LULCOO9 DeviceNet communication module service conditions are Certification UL CSA IEC 62026 1 Overvoltage category III Degree of pollution 3 Conformity to standards C marking In conformity with the essential requirements of European Community XE low voltage LV equipment and electromagnetic compatibility Directives j EMC directives Ambiant air Storage 40 85 C 40 185 F temperature around the device Operation 25 85 C 18 131 F Product Dimensions Dimensions of an LULCO9 DeviceNet communication module are LULCO9 HxLxD 42x45x108mm 1 6x1 8 x 4 25 in Weight 94 4g 0 211b For information about dimensions of overall TeSys U products see Motor starters open version TeSys U Catalogue 24V Power Supply Circuit Technical characteristics of 24V power supply circuit for LULCO9 DeviceNet communication module include Unominal V 24V Supply voltage Operating range V 20
46. 704 0 or 704 1 were not previously overwritten to zero by the PLC application Failure to follow these instructions can result in death serious injury or equipment damage 58 1744085 03 2009 DeviceNet Communication Module Management Description of the different fallback modes Fallback Mode Loss of Communication Communication Recover Loss of Communication Acknowledgement Ignored reg 682 0 No detection of the loss of communication No detection of the loss of communication OA1 and OA3 keep their status OA1 and OAG keep their status No acknowledgement of the loss of communication Freeze outputs OA1 and OA3 keep their status OA1 and OAG keep their status On rising edge by bit 703 3 do not leave set to 1 ERR LED blinking on the front face ERR LED blinking on the front face Once the acknowledgement is done the last command stored in register 704 is enabled Every new On Off command is stored but with no impact on OA1 and OA3 ERR LED switches off reg 682 1 Stop reg 682 2 OA1 and OA3 are forced to 0 OA1 and OA3 are forced to 0 On rising edge by bit 703 3 do not leave set to 1 ERR LED blinking on the front face ERR LED blinking on the front face Once the acknowledgement is done the last command stored in register 704 is enabled Every new On Off command is stored but with no impact on OA1 and OA3 ERR LED
47. 84 1744085 03 2009 Object Dictionary This assembly is vendor specific It is used to implement the request object of PKW protocol Input Assembly Data Byte 7 Byte 6 Byte 5 Byte 4 Byte 3 Byte 2 Byte 1 Byte 0 See PKW Objects page 63 for details Instance 102 PKW Request and Extended Motor Starter This assembly is vendor specific Bytes 0 to 7 Byte 8 Byte 9 See Instance 101 above Reserved value 0 See Instance 5 above Instance 103 PKW Request and TeSys U Control Registers This assembly is vendor specific Bytes 0 to 7 Byte 8 to 13 See Instance 101 above See Instance 100 above Instance 50 Basic Overload Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Reserved Reserved Reserved Reserved Reserved Reserved Reserved Faulted Tr ip Instance 51 Extended Overload Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Reserved Reserved Reserved Reserved Reserved FaultReset Warning Faulted Tr ip Instance 52 Basic Motor Starter Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Reserved Reserved Reserved Reserved Reserved Running1 Reserved Faulted Tr ip Instance 53 Extended Motor Starter 1 Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Reserved Reserved C
48. 9 TeSys U Behaviour at Power up with an LUCM LUCMT Here is a description of the system behaviour at power up of e a power base LUB LUS LU2 with an LULCO9 communication module and LUCM control unit e acontroller base LUTM with an LULCO9 communication module and LUCMT control unit LULCOO Internal LUCM 24V Aux A1 A2 Local Comment Power Supply Control Y V When LULCO9 comm module and LUCM multifunction control unit are powered up simultaneously recommended the system is ready Y LULCOSO is waiting for LUCM identification The motor starter is not seen by the DeviceNet island The ERR LED is on steady red V or V LUCM is waiting for LULCO9 which provokes an M15 fault that must be acknowledged via the LUCM keypad or via the bus once LULCO9 has been powered up LULCOO Internal LUCMT Comment Power Supply Y V When LULCO9 comm module and LUCMT multifunction control unit are powered up simultaneously recommended the system is ready V LULCO9 is waiting for LUCMT identification The motor starter is not seen by the DeviceNet island The ERR LED is on steady red V LUCMT is waiting for LULCO9 which provokes an M15 fault that must be acknowledged via the LUCMT keypad via the bus or via the LUTM push button once LULCO9 has been powered up 1744085 03 2009 19 Installation of TeSys U DeviceNet Module LULCO9 Power Supply for the LULCO9 and Outputs OA1
49. LUCMT 0 1A 111 Get Current phase Ulnt 471 LUCM LUCMT Imbalance imbalance 112 Get Time to trip UInt 511 LUCM LUCMT Seconds 113 Get Set Time to Reset UInt 450 LUCM LUCMT _ Seconds 127 Get Set Single Three Ph Bool O if 601 14 1 LUCM LUCMT 0 Single phase 1 if 601 13 1 1 Three phases 128 Get Set FLA Setting UInt 652 LUCM LUCMT Seconds 129 Get Set Load Class UInt 606 LUCM LUCMT _ Seconds 132 Get Set Thermal Warn Level UInt 609 LUCM LUCMT TripLevel 133 Get Set PL Inhibit Time USInt 613 LUCM LUCMT Seconds 134 Get Set PL Trip Delay USInt 614 LUCM LUCMT Seconds 136 Get Set GF Trip Delay USInt 610 LUCM LUCMT 0 1 25 0 Seconds 137 Get Set GF Trip Level USInt 611 LUCM LUCMT 1 0 5 0 A 138 Get Set GF Warn Level USInt 612 LUCM LUCMT 1 0 5 0 A 139 Get Set Stall Enabled Time USInt 623 LUCM LUCMT 0 250 Seconds 94 1744085 03 2009 Object Dictionary Class Service Instance Service Attribute Access Name Data Value Only with Description ID Type 140 Get Set Stall Trip Level Ulnt 624 LUCM LUCMT 100 600 142 Get Set Jam Trip Delay USInt 617 LUCM LUCMT 0 1 25 0 Seconds 143 Get Set Jam Trip Level Ulnt 618 LUCM LUCMT 0 600 FLA 144 Get Set Jam Warn Level Ulnt 619 LUCM LUCMT 0 600 FLA 146 Get Set UL Trip Delay USInt 620 LUCM LUCMT 0 1 25 0 Seconds 147 Get Set UL Trip
50. O9 Baud Rate The system allows you to assign a baud rate with the following speeds 125 250 500 and AutoBaud using the switches SW7 and SW8 The table below shows how to set the baud rate switches to the required speed SW8 SW7 Baud Rate 0 0 125 kbps default value 0 1 250 kbps 1 0 500 kbps 1 1 Autobaud Autobaud automatically detects the baud rate required NOTE The Autobaud functionality can only be used if a valid communication is already present on the network that is to say that at least one master and one slave are already communicating Address The communication module s address on the DeviceNet bus is the MAC ID You can assign an address from 0 to 63 using the 6 right most switches SW1 to SW6 Example SW10 Baudrate Address Z A TEX ON SW1 Off ee Unused Baud rate Autobaud SW Switch The following table shows examples of address settings the first 5 settings SW8 SW7 SW6 Address 5 SW6 SW5 sw4 SW3 sw2 swi Address 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 1 0 2 0 0 0 0 1 1 3 0 0 0 1 0 4 0 0 0 1 1 5 NOTE The default address is 63 1744085 03 2009 Installation of TeSys U DeviceNet Module LULCO9 Assembly Order The LULCOO9 DeviceNet communication module is installed in a power base or a controller base beneath the control unit which locks it in position To install the modul
51. T1BL Multifunction Control Unit User s Manual Registers LULCO9 LUTM 451 452 aay Fault number Fault bit 2909002 Application faults L Fault reset t E i 4 ERR line 2 FAULT o 8 D E o LUTM external fault 201 021 i 7 3 Automatic with 1 6 set signalled by 1 6 set to 0 8 6 back to 1 ke 2 l o o oO 1744085 03 2009 71 Managing faults and warnings Overload fault with LU B LU S power base After a thermal overload fault rotary button or blue push button on the front can be used whatever the reset mode that was set Configuration Acknowledgment Means register reset anual Iacsl With rotary button on LUsBe With blue push button on LUe Se 602 0 1 en eal remo With kit LU9 APee on LUsBe With kit LU9 on LUeSe 602 1 1 remote Acknowledged by setting bit 704 3 to 1 602 2 1 automatic Managed by control unit Overload fault with LUTM controller base After a thermal overload fault blue push button on the front or input I 5 can be used whatever the reset mode that was set Configuration Acknowledgment H Means register reset manual local With blue push button on the front 602 0 1 z With reset mode on front of the rack or table via manual remote input 1 5 Acknowledged by bit 704 3 This bit is active on 602 1 1 remote rising edge and must be res
52. TeSys U C Ad V1 xx Y Y TeSys U C Mu L V1 xx y TeSys U C Mu R V1 xx V Y E TeSys U Sc Ad V1 xx Y Y TeSys U Sc Mu L V1 xx N TeSys U Sc Mu R V1 xx Y Y TeSys U Sc St V1 xx Y Y The parameters can be set locally by embedded HMI of multifunction control unit on TeSys U Sc Mu R V2 xx and TeSys U C Mu R V1 xx variants if the PLC application does not modify any parameters through the network Parameters for TeSys U C Ad The following table gives the description of parameters for TeSys U C Ad DeviceNet path Parameter Description 6A 1 083 602 Control configuration thermal fault reset mode 6B 1 21 682 Communication loss fallback strategy 6B 1 22 683 Controller Local Remote control mode 6B 1 23 684 Inversion of output configuration 6B 1 24 685 Output LO1 configuration 6B 1 25 686 Outputs OA1 and OAS configuration 6B 1 26 687 Outputs 13 and 23 configuration 6B 1 27 688 Recovery mode 6B 1 29 690 Disable auto identification 52 1744085 03 2009 DeviceNet Communication Module Management Parameters for TeSys U C Mu L R The following table gives the description of parameters for TeSys U C Mu L R DeviceNet path Parameter Description 6A 1 01 600 Define an access code to lock LUCMT keypad 6A 1 02 601 Configuration 6A 1 03 602 Control c
53. UTM output control mode remote via the bus 6B 1 23 684 LULCOSO outputs inversion 0 Outputs status reflects control bits Assignment of 6B 1 24 LSB 685 LSB output LO1 2 LO1 reflects control bit 700 0 6B 1 25 LSB 686 LSB output OA1 12 OA1 reflects control bit 704 0 6B 1 25 MSB 686 MSB output OA3 13 OAS reflects control bit 704 1 on a controller base 6B 1 26LSB 687 LSB output 13 12 13 reflects control bit 704 0 6B 1 26 MSB 687 MSB output 23 13 23 reflects control bit 704 1 6B 1 27 688 Recovery mode after power off 0 Pa outputs recover the status they had before power 6B 1 29 690 Disable auto identification 0 Automatic identification of control unit NOTE For more details refer to TeSys U Communication Variables User s Manual 1744085 03 2009 57 DeviceNet Communication Module Management Customizing your Configuration Parameter Types You can either use the factory settings or customize your configuration Parameters concerning the communication module are described below For other parameters concerning the Control Unit refer to the TeSys U communication variables User s manual Control Configuration Bits 0 1 and 2 of this register are used to configure the reset mode after thermal overload fault Only one of these bits must be set to 1 to select the reset mode Other bits 3 to 8 are dedicated to the configuration of the Modbus port of the multifunction control unit
54. ad Byte Bit 7 Bit 6 Bit5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Reserved Reserved Reserved Reserved Reserved FaultReset Warning Faulted Trip Instance 52 Basic Motor Starter Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Reserved Reserved Reserved Reserved Reserved Running1 Reserved Faulted Trip Instance 53 Extended Motor Starter 1 Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Reserved Reserved CntrlfromNet Ready Reserved Running1 Warning Faulted Trip Instance 54 Extended Motor Starter 2 Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Reserved Reserved CntrlfromNet Ready Running2 Running1 Warning Faulted Trip NOTE CntrifromNet NOT Register 455 14 Ready Register 455 0 Running2 Register 455 7 AND Register 704 1 Running1 Register 455 7 AND Register 704 0 Warning Register 455 3 Fault Trip Register 455 2 OR Register 455 4 Instance 110 TeSys U Monitoring Registers with dynamic configuration This assembly contains several monitoring registers commonly used with a TeSys U device Conf Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 Sc St Path 68 01 06 Path 68 01 09 Empty Empty Register 455 Register 458 Sc Ad Path 68 01 06 Path 68 01 09 Path 68 01 0C Empty Register 455 Register 458 Register 461 Sc Mu L R Path 68 01 06 Path 68 01 09 Path 68 01 0C Path 68 01 08 Register 455 Register 458
55. age sent by the DeviceNet network master it generates a communication loss and the DeviceNet module is in fallback mode see page 58 The conditions to exit the idle mode are the same as to exit the fallback mode 1744085 03 2009 35 DeviceNet Communication Module Management Device Profiles and EDS Files Device Profiles What s an EDS DeviceNet s device models define the physical connections and promote interoperability among standard devices Devices that implement the same device model must support common identity and communications status data Device specific data is contained in device profiles that are defined for various device types Typically a device profile defines the device s e object model e O data format e configurable parameters The above information is made available to other vendors through the device s EDS electronic data sheet For a full description of the objects in the TeSys U Motor Starter profile see Object Dictionary page 81 The EDS is a standardized ASCII file that contains information about a network device s communications functionality and the contents of its object dictionary see page 81 as defined by ODVA Open DeviceNet Vendor Association The EDS also defines device specific and manufacturer specific objects Using the EDS you can standardize tools to e configure DeviceNet devices e design networks for DeviceNet devices e manage project information on diff
56. alue 0 to 45 as described in Assignment of outputs LO1 OA1 OA3 13 23 Assignment control factory setting of LULCO9 output 23 is DeviceNet path Register Value Factory setting Comment 6B 1 26 MSB 687 MSB 0 to 45 13 Output 23 image of register 704 1 Recovery Mode After Stopping Reg 688 If you use register 704 to control outputs OA1 OA3 writing value 1 to register 688 locks the motor and prevents it from restarting after the occurrence of certain events e Loss followed by restoration of 24 VDC outputs OA1 OA3 e Change in position of rotary knob on power base followed by return to Ready position When one of these events occurs control bits 704 0 and 704 1 outputs OA1 OA3 are forced to 0 automatically Once these conditions have disappeared control of the motor can be restored by sending a new run command A WARNING AUTOMATIC RESTART OF THE MOTOR In case of a cyclic writing to register 704 e g an LUFP gateway in its predefined configuration this monitoring function must be used with caution The application program must take this state into account and request that bits 704 0 or 704 1 are written to 0 Otherwise when this event disappears the motor will restart automatically Failure to follow these instructions can result in death serious injury or equipment damage Disable Auto Identification Disable auto identification can be automatic or forced
57. arameters screen should resemble the following figure after you have customized it as described above Edit I O Parameters Strobed Input Size E F v Polled Input Size 16 Output Size 14 Poll Rate Every Scan Bytes Bytes Lj Bytes Cancel 06 TeSysU Se MuR Change of State Cyclic E Input Size Output Size Heartbeat Rate Cc Restore 0 Sizes Bytes msec EN d EJ Bytes Depending on your requirements you can select one of three transmission modes e Polled e Change of State e Cyclic NOTE LULCO9 does not support Strobed I O messages used for very simple I O devices About the Motor Starter s Input and Output Data Lengths In the above procedure you entered the number of input and output bytes produced by the motor starter The master device needs this information to allocate data space for each network node The number of input and output bytes the motor starter produces depends on the instances you select for the DeviceNet Interface object and the TeSys U variant The tables below show the byte size of each assembly object you can select for I O messaging Output assembly data size consumed by the motor starter Instance Name TeSys U variant Number of bytes 2 Basic Overload All 1 3 Basic Motor Starter All 1 4 Extended Contactor All 1 5 Extended Motor Starter All 1 100
58. ase motor class 10 0 12 or 0 32A rating with a standard control unit that protects against overloads short circuits phase imbalance and insulation breaks and offers a manual reset Local L Remote R configuration modes refer to Configuration register 601 read write with motor off supported by Multifunction Control Unit gt V3 x If in a local configuration mode It means that 601 7 1 This mode preserves the local configuration made with the embedded HMI of the multifunction control unit It forbids any configuration managed by PLC application through the network thus preserving your local configuration If in a remote configuration mode It means that 601 7 0 This mode enables the PLC application to remotely configure the TeSys U device Note The parameters overwritten by the PLC application will be lost This mode is useful in case of faulty device replacement By default the TeSys U device equipped with a Multifunction Control Unit gt V3 x is in Remote configuration mode 1744085 03 2009 51 DeviceNet Communication Module Management Setting TeSys U Parameters Depending on the TeSys U variant parameter settings can be managed through different channels Configuration managed by RSNetworx configuration tool Configuration managed through PKW Configuration locally by embedded HMI of multifunction control unit
59. cicna ie VATS ea Iw ha a o a ene 7 Part Hardware Implementation 00 cee eee eee ee eee 9 Chapter 1 Installation of TeSys U DeviceNet Module LULCO9 11 Presentation of LULCO9 DeviceNet Communication Module 0000 eee eee 12 Description and Installation of the Module 0 cece ee 13 Electrical Connection llis rr 18 Connection to the DeviceNet Bus lsssssseeeeee e hn 23 DeviceNet Network Connection liseseseeeeeee 25 Chapter 2 Technical Characteristics 00 cece eee eee eee 29 Service Conditions and Technical Characteristics 0 000 cece cee ee eee 29 Part Il Software Implementation 0000 eee eee eee 31 Chapter 3 DeviceNet Communication Module Management 33 DeviceNet Protocol Principles 0 00 e ee eee I RII 34 Connections and Data Exchange 2 cece eect eee eee 35 Device Profiles and EDS Files 0 0 cece cette IR 36 Configuring the Motor Starter with Configuration Software 20000 eee eee 38 Inserting TeSys U in the DeviceNet Network 0 0 0 cece eh 51 Factory Configuration and Setting l i re 57 Customizing your Configuration lisse n 58 PKW Objects TUBES UP ED e ETE o tp et Dee ane eer dendo noB E CE eds 63 Using of main registers for a simplified management nananana 68 Chapter 4 Managing faults and warnings
60. communication module is managed via the DeviceNet bus This chapter describe basic DeviceNet features as well as the DeviceNet module s object dictionary What s in this Chapter This chapter contains the following topics Topic Page DeviceNet Protocol Principles 34 Connections and Data Exchange 35 Device Profiles and EDS Files 36 Configuring the Motor Starter with Configuration Software 38 Inserting TeSys U in the DeviceNet Network 51 Factory Configuration and Setting 57 Customizing your Configuration 58 PKW Objects 63 Using of main registers for a simplified management 68 1744085 03 2009 33 DeviceNet Communication Module Management DeviceNet Protocol Principles Overview The DeviceNet low level controller area network CAN provides a communications link between simple industrial devices such as actuators and sensors and controlling devices The network transports control information as well as information about the properties of the device being controlled It enables operation in either master slave or peer to peer mode The DeviceNet powered four wire network operates in a trunkline dropline configuration and supports up to 64 nodes 34 1744085 03 2009 DeviceNet Communication Module Management Connections and Data Exchange Connections Messaging I O Message Types Connections are established through the motor starter s communication terminals See De
61. cription of parameters for TeSys U Sc St DeviceNet path Parameter Description 6B 1 21 682 Communication loss fallback strategy 6B 1 23 684 Inversion of output configuration 6B 1 24 685 Output LO1 configuration 6B 1 25 686 Outputs OA1 and OAG configuration 6B 1 27 688 Recovery mode 6B 1 29 690 Disable auto identification 56 1744085 03 2009 DeviceNet Communication Module Management Factory Configuration and Setting Parameter Types Setting communication module parameters allows you to determine e the operation mode e the reset mode on thermal overload fault e the correspondence between the communication module outputs and the LUTM controller inputs Default Configuration and Setting Reglsters Configuration registers 6A 1 xx and Setting registers 6B 1 xx are in a read write access Factory default values are DeviceNet path Register Subject Factory Meaning value 602 0 Reset mode after thermal 1 Manual mode overload fault 6A 1 03 Validate thecomm nic tio Forced to 0 zero this bit forbids any communication 2 4 1 bet LUCM multifuncti trol unit and LUL 60 between LUCM and LULCOO e ween UC multifunction control unit and LULCO9 communication module Forced stop 6B 1 21 682 Sean gate cas l s Power base OA1 and OA3 to 0 SE Controller base 13 and 23 to 0 y Local or bus operation mode i 6B 1 22 683 with LUTM and LULCO9 0 L
62. e Address text field to 15 15 is the MAC ID used throughout this example Click OK Note that the MAC ID of the motor starter is now 15in the project view 5 Repeat steps 1 to 4 to add the 1747 SDN Scanner The scanner s EDS is in the Hardware list at Rockwell Module to the network with MAC ID 00 Automation Allen Bradley Communication Adapter 6 Save your configuration by choosing Online from the Save offline configurations for later use Network menu Online Device Connection Use this procedure for adding devices to your network when the DeviceNet network is already assembled andt he configuration tool is online Step Action Comment 1 From the Network menu select Online The Browse for network screen appears 2 Set a communication path to select a path based on your system and application requirements When the Browsing network screen finishes the physically connected devices will appear in the project view Click OK to transfer the required device information The RSNetWorx Project View The RSNetWorx project view should resemble the following figure after you ve added the motor starter and the master scanner to your network configuration using either the online or offline connection procedure L DeviceNet dnt RSNetworx for DeviceNet p p File Edit View Network Device Diagnostics Tools Help c i SB km Hardware vie aE EE 1 xi a
63. e SUE SIOP oo t Run Stopping i Fault Stop Detected Enable The following table describes the run stop event matrix Event State N A No action Non exist Startup Not_Ready Ready Enabled Stopping Fault Stop Faulted Switch Off N A Transition to Transition to Transition to Transition to Transition to Transition to Transition to Non exist Non exist Non exist Non exist Non exist Non exist Non exist Switch On Transition N A N A N A N A N A N A N A to Startup Initialisation N A Transition to N A N A N A N A N A N A Complete Not Ready Main Power On N A N A Transition to N A N A N A N A N A Ready Run N A N A N A Transition to N A Transition to N A N A Enable Enable Stop N A N A N A N A Transition to N A N A N A Stopping Stop Complete N A N A N A N A N A Transition to N A N A Ready Reset N A N A Transition to Transition to Transition to Transition to Transition to Transition to Startup Startup Startup Startup Startup Startup Main Power Off N A N A N A Transition to Transition to Transition to Transitionto N A Not Ready Faulted Faulted Faulted Fault Detected N A Transition to Transition to Transition to Transition to Transition to N A N A Faulted Faulted Faulted Fault Stop Fault Stop Fault Stop N A N A N A N A N A N A Transition to Complete Faulted Fault Reset N A N A N A N A N A N A N A Transition to Not Ready 92 1744085 03 2009 Object Dictionary Attribute 5 NetCtrl is used t
64. e within the power base or the controller base Step Action 1 Choose the prewired coil connection 2 Insert the LULCO9 DeviceNet communication module 3 Insert the control unit that locks the module The illustration below details the steps Installation of LULCO9 DeviceNet communication module is 2 Numbers correspond both to components assembly order and to their positions LU2B LUB LU2Se LU9M RL LUCA BL LUCB BL LUCC BL LUCD BL LUCM BL LUTM OBL LUCBT1BL LUCDT1BL 1744085 03 2009 17 Installation of TeSys U DeviceNet Module LULCO9 Electrical Connection 24V and Internal Power Supplies Schematic of the 24V 24VDC and internal power supplies 24 V Aux LUCM gt 24 V Bus same cable Power base Controller base LI o LUCMT IF 4 mes LUCBT LUCC LUCD wor 44 l LUCA l l 4 ATIA2 Terminals LUTM eva m LULCO9 24 V Bus LULCOS Bus DN i Internal links Eternal links to wire 1 A cap prevents external power supply connection 24V Bus Communication module power supply V and V 24V Power supply for OA1 OA3 and LO1 24V Aux Power supply for LUCM control unit or LUTM controller 18 1744085 03 2009 Installation of TeSys U DeviceNet Module LULCO
65. er Supply Tap i i m3 A v 6 c HRO TEO num 1 e e C PLC with DeviceNet scanner TeSys U with DeviceNet communication module LULCO9 Line terminators 121 Q resistance 24 VDC power supply DeviceNet power tap DeviceNet thin cable DeviceNet open style connnector tap DeviceNet thick cable ONOahRWD 26 1744085 03 2009 Installation of TeSys U DeviceNet Module LULCO9 Architecture Constraints with TeSys U and One Power Supply The minimum distance between two TeSys U DeviceNet devices is 0 3 m 11 8 in In the case of a complete thin cable daisy chain architecture using one single power supply the 2 curves below indicate the manximum number of TeSyS U devices that can be connected depending on the bus length and temperature 70 60 50 AR o w eo Number of slaves 0 10 20 30 40 50 60 70 80 90 100 Length of network m The number of TeSys U devices connected on the DeviceNet network can be increased if necessary by using a second DeviceNet power supply 1744085 03 2009 27 Installation of TeSys U DeviceNet Module LULCO9 28 1744085 0
66. erent platforms The parameters of a particular device depend on those objects parameter application communications emergency and other objects that reside on the device EDS Download Procedure The different TeSys U starter controller variants are described in EDS Electronic Data Sheet files If the TeSys U starter controllers do not show up in your CANopen configuration tool the corresponding EDS files must be imported The following table describes the steps to follow to download the EDS and icon files associated to Tesys U from the www schneider electric com website Step Action 1 Open the Schneider Electric website www schneider electric com 2 Click Products and Services and then click Automation and Control 3 In the Downloads section of the left menu bar click Current offers 4 e Inthe Choose a function drop down list select Motor Control e Inthe Choose a range drop down list select TeSys U e Inthe Choose a type of document drop down list select Software Firmware Click gt Find 5 Select Communication Module Tesys U Canopen and download LULCO9 EDS DIB files V100 exe file 6 Double click LULCO9 EDS DIB files V100 exe on your hard disk Click Accept in the Licence for software downloaded from Schneider Electric web sites window which opens then browse for a destination folder and click Install 7 Select the EDS file s corresponding to your TeSys U configuration s Fo
67. et to 0 by programming 602 2 1 automatic Managed by control unit NOTE Reset mode must be set 72 1744085 03 2009 Managing faults and warnings Internal Faults Internal Fault Acknowledgement Here is the list of possible internal faults Registers LULCO9 LUTM 451 452 i riui Fault number Fault bit 2000000 Fault t t aeS t I acknowledgement a F A ERR FAULT LULCO9 DeviceNet communication module 14 M14 fault LULCO9 DeviceNet communication module LULCOO and LUCMe not installed or not Off 15 M15 power off then on powered or communication loss with the module LUCe control unit internal 54 41214 M54 fault eM multifunction 21 10 59 99 See LUCM LUCMT Multifunction Control Unit User s Manual control unit internal fault to 63 Write to EEPROM fault 100 248 1 On M100 LULCOS power SIE then on Communication fault with LUCMe multifonction 101 _412 1 On M101 LULCOS power ot then on control unit Cheoksum on EEPROM aye _13 1 On M102 E Rising edge on 704 3 fault x i i a E configuration T ou _13 1 On M104 Rising edge on 704 3 Communication fault with LULCO9 power off LUTM controller base 105 mm en M105 then on Communication fault with 205 LUTM power off then LULCO9 module S on S RU o 248 1 On 5 LUT me No control unit 206 z power ohen Lam on D ER o o on
68. evel Fw Logic input LI1 1 makes the motor stop in forward run Logic input LI2 1 makes the motor stop in reverse run After a new running order a stop order followed by a run order even though logic input LI2 1 the motor starts again NOTE Logic input LI2 does not impact the forward run and logic input LI1 does not impact the reverse run This function is enabled on rising edge not on level Rev Logic input LI2 1 makes the motor stop in reverse run Logic input LI1 1 makes the motor stop in forward run After a new running order a stop order followed by a run order even though logic input LI2 1 the motor starts again NOTE Logic input LI2 does not impact the forward run and logic input LI1 does not impact the reverse run 1744085 03 2009 77 Configuration of Predefined Functions 78 1744085 03 2009 Appendices 1744085 03 2009 79 80 1744085 03 2009 Object Dictionary A Overview The DeviceNet protocol uses object modeling Object modeling organizes related data and procedures into one entity the object An object is a collection of related services and attributes Services are procedures an object performs Attributes are characteristics of objects represented by values which can vary Typically attributes provide status information or govern the operation of an object The value associated with an attrib
69. eviceNet communication module equipped with connectors NOTE Please check that you do have all items described above You must have the IS and the connectors must be present and correctly positioned The communication module allows you to control a motor starter remotely via DeviceNet from A TeSys U starter controller LUBee LU2Bee A TeSys U starter LUSee LU2See A TeSys U controller LUTMee With the communication module you can e read the motor starter states control the motor starter run forward or reverse set the protection functions read the data processed in the advanced and multifunction control units e e e e read the input and output states 4 DANGER IMPROPER CONTROL VOLTAGE Use 24VDC to power the LULCO9 communication module Do not connect voltage in excess of 24VDC Failure to follow these instructions will result in death or serious injury The available protection and control data depend on the control unit with which the LULCO9 DeviceNet communication module is used There are three types of control units e Standard referenced as LUCA e Advanced referenced as LUCB C D LUCBT DT e Multifunction referenced as LUCM LUCMT In order to select the right TeSys U configuration you need the following table lets you check the data and controls you have access to Configuration Data Controls Standard Advanced Mult
70. f output configuration 6B 1 24 685 Output LO1 configuration 6B 1 25 686 Outputs OA1 and OAG configuration 6B 1 27 687 Outputs 13 and 23 configuration 6B 1 28 688 Recovery mode 6B 1 29 690 Disable auto identification 1744085 03 2009 53 DeviceNet Communication Module Management Parameters for TeSys U Sc Ad The following table gives the description of parameters for TeSys U Sc Ad DeviceNet path Parameter Description 6A 1 03 602 Control configuration thermal fault reset mode 6B 1 21 682 Communication loss fallback strategy 6B 1 23 684 Inversion of output configuration 6B 1 24 685 Output LO1 configuration 6B 1 25 686 Outputs OA1 and OA3 configuration 6B 1 27 688 Recovery mode 6B 1 29 690 Disable auto identification 54 1744085 03 2009 DeviceNet Communication Module Management Parameters for TeSys U Sc Mu L R The following table gives the description of parameters for TeSys U Sc Mu L R DeviceNet path Parameter Description 6A 1 01 600 Define an access code to lock LUCMT keypad 6A 1 02 601 Configuration 6A 1 03 602 Control configuration 6A 1 04 603 Control unit communication on LUCMT port address 6A 1 05 604 Control unit communication on LUCMT port baud rate 6A 1 06 605 Overcurrent trip threshold 6A 1 07 606 Load class
71. gister 455 Register 458 Register 461 Register 459 LSB MSB LSB MSB LSB MSB LSB MSB 1 Any byte left vacant at the end of this assembly will not be sent to the bus so if no parameter is attributed to bytes 6 and 7 the assembly data length will be 6 bytes instead of 8 bytes Instance 111 PKW Response Object This assembly is vendor specific It is used to implement the response object of PKW protocol Byte 7 Byte 6 Byte 5 Byte 4 Byte 3 Byte 2 Byte 1 Byte 0 See PKW Objects page 63 for details Instance 112 PKW Response and Extended Motor Starter This assembly is vendor specific Bytes 0 to 7 Byte 8 Byte 9 See Instance 111 above Reserved value 0 See Instance 54 above Instance 113 PKW Response and TeSys U Monitoring Registers This assembly is vendor specific Bytes 0 to 7 Byte 8 to 15 See Instance 111 above See Instance 110 above 86 1744085 03 2009 Object Dictionary DeviceNet Object Overview Class Attributes Instance Attributes Class Service Instance Service The DeviceNet Object is used to provide the configuration and status of a physical attachment to the DeviceNet network A produc can support only one DeviceNet Object per physical connection to the DeviceNet communication terminals Attribute ID Access Name Data Type Value Descrip
72. hdog timeout action USInt 0 10r2 0 Transition to TimeOut 1 Auto delete 2 Auto reset 13 Get Produced connection path length UInt 14 Get Set Produced connection path Ulnt 15 Get Consumed connection path length UInt 16 Get Set Consumed connection path Ulnt 17 Get Set Production_inhibit_time Ulnt 0 Not defined Class Service Service Code Service Name Description 08 hex Create Used to instantiate a Connection Object OE hex Get Attribute Single Read 1 attribute Instance Service Service Code Service Name Description OE hex Get Attribute Single Read 1 attribute 10 hex Set Attribute Single Write 1 attribute 05 hex Reset Reset Inactivity Watchdog timer 90 1744085 03 2009 Object Dictionary Control Supervisor Object Description Class Attributes Instance Attributes Class Service Instance Service This object models all the management functions for devices within the Hierarchy of Motor Control Devices Attribute ID Access Name Data Type Value Description 1 Get Revision Ulnt 02 2 Get Max instance Ulnt 1 Attribute Access Name Data Description ID Type Get Set Run Fwd Bool 704 0 Get Run Rev Bool 704 1 Get State USInt 0 Vendor Specific 1 Startup 2 Not Ready 3 Ready 4 Enabled 5 Stopping 6 Fault_Stop 7 Faulted 7 Get Running Fwd Bool 455 7 AND 704 0 8 Get R
73. hout this documentation or on the equipment to warn of potential hazards or to call attention to information that clarifies or simplifies a procedure The addition of this symbol to a Danger or Warning safety label indicates that an electrical hazard exists which will result in personal injury if the instructions are not followed personal injury hazards Obey all safety messages that follow this symbol to avoid possible injury or death A DANGER DANGER indicates an imminently hazardous situation which if not avoided will result in death or serious injury A WARNING WARNING indicates a potentially hazardous situation which if not avoided can result in death or serious injury This is the safety alert symbol It is used to alert you to potential A CAUTION CAUTION indicates a potentially hazardous situation which if not avoided can result in minor or moderate injury CAUTION CAUTION used without the safety alert symbol indicates a potentially hazardous situation which if not avoided can result in equipment damage Electrical equipment should be installed operated serviced and maintained only by qualified personnel No responsibility is assumed by Schneider Electric for any consequences arising out of the use of this material A qualified person is one who has skills and knowledge related to the construction and operation of electrical equipment and the installation and has received
74. ifferential communication signals CAN_H and CAN_L e the communication module power supply V and V e the connection of a shield cable Shield 1744085 03 2009 23 Installation of TeSys U DeviceNet Module LULCO9 DeviceNet Open Style Connector The bus connector is a five pin connector with pins spaced 5 08 mm 0 2 in apart which can be used with standard DeviceNet thick and thin cables The following diagrams show the connection of a DeviceNet cable to a DeviceNet communication module Female connector module side Male connector cable side CANL CAN H CANH CANL Standard DeviceNet thin cable must be used to connect TeSys U on the network Each TeSys U DeviceNet communication module allows interconnection of the following signals Pin number Signal Description Wire colour 1 V Common 24V bus Black 2 CAN_L CAN Low bus conductor Blue 3 S Shield none 4 CAN_H CAN High bus conductor White 5 V 24V bus Red 24 1744085 03 2009 Installation of TeSys U DeviceNet Module LULCO9 DeviceNet Network Connection Physical Layer Network Topology DeviceNet s data link layer is defined by the CAN Controller Area Network specification and by the implementation of widely available CAN controller chips CAN also implements a differentially driven common return two wire bus line DeviceNet s physical layer contains two twisted pairs of shielded wi
75. ifunction LUCA LUCB C D LUCBT DT LUCM MT Start and stop controls Y V V States ready running faulty V V V Warning V V Automatic reset and remote reset via the bus V V Indication of the motor load V V Differentiation of faults V Y Remote parameter setting and viewing of all d functions Statistics function V Monitoring function V 1744085 03 2009 Installation of TeSys U DeviceNet Module LULCO9 Description and Installation of the Module Front View of the Module Connectors and LEDs of the LULCO9 DeviceNet communication module are described hereafter LULCO9 MNS ERR 24V DeviceNet OA3 OA1 COM DD 24v LOTO EIS eE eala 1 2 color MNS LED indicating DeviceNet module operational status 2 Red ERR LED indicating DeviceNet module fault 3 Green 24V LED indicating voltage presence at outputs OA1 OA3 LO1 and 24V Bus 4 Open style connector and 24V Bus DeviceNet external power supply 5 Connection of the 24V power supply for outputs OA1 OA3 LO1 The 2 terminals marked are internally linked Logic input 2 Logic input 1 Logic output 1 assignable depending on configuration reg 685 LSB 24V wiring coil connector for the power base e OA1 assignment depends on configuration register 686 LSB e OA3 assignment depends on configuration register 686 MSB COND 10 Connector for communication with the advanced or multifunction con
76. ister Value Factory setting Comment 6B 1 24 LSB 685 LSB 0to45 2 Output LO1 image of register 700 0 Output OA1 Configuration To change the assignment factory setting write another value 0 to 45 as described in Assignment of outputs LO1 OA1 OAG3 13 23 Assignment control factory setting of LULCO9 output OA1 is DeviceNet path Register Value Factory setting Comment 6B 1 25 LSB 686 LSB 0to45 12 Output OA1 image of register 704 0 Output OA3 Configuration To change the assignment factory setting write another value 0 to 45 as described in Assignment of outputs LO1 OA1 OA 13 23 Assignment control factory setting of LULCO9 output OAS is DeviceNet path Register Value Factory setting Comment 6B 1 25 MSB 686 MSB 0 to 45 13 Output OA3 image of register 704 1 60 1744085 03 2009 DeviceNet Communication Module Management Output 13 Configuration To change the assignment factory setting write another value 0 to 45 as described in Assignment of outputs LO1 OA1 OA3 13 23 Assignment control factory setting of LULCO9 output 13 is DeviceNet path Register Value Factory setting Comment 6B 1 26 LSB 687 LSB 0 to 45 12 Output 13 image of register 704 0 Output 23 Configuration To change the assignment factory setting write another v
77. nse telegram encapsulated in I O messaging data Examples of I O Messages without PKW The table below shows the byte arrangement of I O messages for the Te Sys U Sc Mu R L when Output Assembly Instance 100 TeSys U Control Register and Input Assembly Instance 110 TeSys U Monitoring Registers IN OUT 0 0 1 1 2 2 3 3 4 4 5 5 6 7 The table below shows the corresponding double word arrangement IN OUT DWO 3 2 1 0 3 2 1 DW1 7 6 5 4 5 Reg 458 Reg 455 Reg 703 Reg 704 Reg 457 Reg 461 Reg 700 1744085 03 2009 63 DeviceNet Communication Module Management Examples of I O Messages with PKW The table below shows the byte arrangement of I O messages for theTeSys U Sc Mu R L when Output Assembly Instance 103 PKW Request and TeSys U Control Register and Input Assembly Instance 113 PKW Response and TeSys U Monitoring Registers IN OUT 0 PKW INO 0 PKW OUT 0 1 PKW IN 1 1 PKW OUT 1 2 PKW IN 2 2 PKW OUT2 3 PKW IN 3 3 PKW OUT 3 4 PKW IN 4 4 PKW OUT 4 5 PKW IN 5 5 PKW OUT 5 6 PKW IN 6 6 PKW OUT 6 7 PKW IN 7 7 PKW OUT 7 8 8 9 9 10 10 11 11 12 12 13 13 14 15 The table below shows the corresponding double word arrangement IN OUT
78. nstance 50 Basic Overload Instance 51 Extended Overload Instance 52 Basic Motor Starter Instance 53 Extended Motor Starter 1 EMS1 Instance 54 Extended Motor Starter 2 EMS2 Default Instance 110 TeSys U Monitoring registers Instance 111 PKW response object Instance 112 PKW response EMS2 Instance 113 PKW response TeSys U monitoring UN OI ANDAARWNHH DIAN DAARWNHH OI ANDOAHRWNH CO 4 Set Get EEPROM Save BYTE do nothing Parameter 0 7 Save All Save Com Parameters Save Appli Parameters Automatically return to 0 when operation is done 5 Set Get EEPROM Restore BYTE 0 do nothing Parameter 0 7 1 Restore All 2 Restore Com Parameters 3 Restore Appli Parameters Automatically return to O when operation is done NOTE The Extended Motor Starter EMS is repeated twice value 3 and 4 in the Poll consumed assembly list of values This is done to be consistent with values 3 and 4 of the Poll produced assembly list of values The AutoBaud enable value attribute 4 is read at power up only When this bit is cleared when disabling auto baud the current baudrate is written to the register Network Port Baud Rate Setting 695 Network Port Baud Rate Setting has priority over this bit in the event of inconsistency checked at power up In this case the AutoBaud enable value is set according to the register Network Port Baud Rate Setting at power
79. ntrlfromNet Ready Reserved Running1 Warning Faulted T rip Instance 54 Extended Motor Starter 2 Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Reserved Reserved CntrlfromNet Ready Running2 Running1 Warning Faulted Trip NOTE CntrifromNet NOT Register 455 14 Ready Register 455 0 Running2 Register 455 7 AND Register 704 1 Running1 Register 455 7 AND Register 704 0 Warning Register 455 3 Fault Trip Register 455 2 OR Register 455 4 1744085 03 2009 85 Object Dictionary Instance 110 TeSys U Monitoring Registers with dynamic configuration This assembly contains several monitoring registers commonly used with a TeSys U device Configuration Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte6 Byte7 LUB LU2B LUS LU2S Path 68 01 06 Path 68 01 09 Empty Empty LUCA Register 455 Register 458 LUB LU2B LUS LU2S Path 68 01 06 Path 68 01 09 Path 68 01 0C Empty LUCB C D Register 455 Register 458 Register 461 LUB LU2B LUS LU2S Path 68 01 06 Path 68 01 09 Path 68 01 0C Path 68 01 08 LUCM Register 455 Register 458 Register 461 Register 457 LUTM Path 68 01 06 Path 68 01 09 Path 68 01 0C Path 68 01 0A LUCBT DT Register 455 Register 458 Register 461 Register 459 LUTM Path 68 01 06 Path 68 01 09 Path 68 01 0C Path 68 01 0A LUCMT Re
80. o request that Run Stop events be controlled from the network You may inhibit these events however if you do not wish to allow Run Stop control from the network under certain circumstances or if your application does not permit it Only when attribute 15 CtrlFromNet is set to 1 by the device in response to a NetCtrl request is Run Stop control actually enabled from the network If attribute 15 CtrlFromNet is 1 then the events Run and Stop are triggered by a combination of the Run1 and Rune attributes as shown in the following table Note that Run1 and Run2 have different contexts for different device types The following table shows the Run1 and Run2 contexts for the devices within the motor control hierarchy Drives and Servos Run1 RunFwd Run2 RunRev If CtriFromNet is 0 Run and Stop events must be controlled using local input s provided by the vendor Run1 Run2 Trigger Event Run Type 0 0 Stop N A 0 21 0 Run Run1 0 0 gt 1 Run Run2 0 gt 1 0 gt 1 No action N A 1 1 No action N A 1 gt 0 1 Run Run2 1 1 gt 0 Run Run1 NOTE Local stop and run signals could override or be interlocked with the run stop control through DeviceNet 1744085 03 2009 93 Object Dictionary Overload Object Description Class Attributes Instance Attributes This object models all the functions specific to an AC motor overload protection device
81. of Reflex1 Sensor 1 logic input LI1 directly controls the motor stop After a new running order stop then run order the motor restarts even with sensing LI1 1 i I Pa i Eu pu M 1 Bus 2 Sensor 1 LI1 NOTE In case of a reversing starter reflex stop impacts both directions Time gt Control from the bus Reg 704 Lu ce ee Hee Motor control via the starter Information chaining data from sensor 1 LI1 presence of a part 1744085 03 2009 75 Configuration of Predefined Functions Description of Reflex2 Sensor 1 logic input LI1 controls the motor stop when running forward Sensor 2 logic input LI2 controls the motor stop when running reverse After a new running order stop then run order the motor restarts even with sensing LI1 1 or LI2 1 1 Bus ooo oL M i ll 2 Sensor 1 LI1 o lt EE 3 Sensor 2 LI2 NOTE Sensor 2 LI2 does not impact the forward direction and sensor 1 LI1 does not impact the reverse direction Reflex Stop Selection In order to use a reflex stop function you have to select it from the register having an output to monitor
82. onfiguration 6A 1 04 603 Control unit communication on LUCMT port address 6A 1 05 604 Control unit communication on LUCMT port baud rate 6A 1 07 606 Load class 6A 1 08 607 Thermal reset time 6A 1 09 608 Thermal reset threshold 6A 1 0A 609 Thermal warning threshold 6A 1 0B 610 Ground fault trip timeout 6A 1 0C 611 Ground fault trip threshold 6A 1 0D 612 Ground fault warning threshold 6A 1 0E 613 Phase imbalance trip timeout at start up 6A 1 0F 614 Phase imbalance trip timeout while running 6A 1 10 615 Phase imbalance trip threshold 6A 1 11 616 Phase imbalance warning threshold 6A 1 12 617 Jam trip timeout 6A 1 13 618 Jam trip threshold 6A 1 14 619 Jam warning threshold 6A 1 15 620 Undercurrent trip timeout 6A 1 16 621 Undercurrent trip threshold 6A 1 17 622 Undercurrent warning threshold 6A 1 18 623 Long start trip timeout 6A 1 19 624 Long start trip threshold 6A 1 1A 625 Long start warning threshold 6A 1 1B 1C 626 627 Reserved 6A 1 1D 628 Current transformer primary 6A 1 1E 629 Current transformer secondary 6A 1 1F 630 Current transformer external passes 6A 1 20 23 631 634 Reserved 6B 1 01 650 Display language 6B 1 02 651 Display of running items 6B 1 03 652 Full Load Amps setting FLA max 6B 1 04 1E 653 679 Reserved 6B 1 1F 680 Communication module identification code setting 6B 1 21 682 Communication loss fallback strategy 6B 1 22 683 Controller Local Remote control mode 6B 1 23 684 Inversion o
83. otor starter and RSNetWorx Allen Bradley SLC 500 PLC PLC processor module 1747 SDN DeviceNet scanner module DeviceNet network cable TeSys U Motor Starter PC running RSNetWorx properly connected to your network DeviceNet power supply NO ROD The scanner module is the control mechanism for all network traffic It reads and writes every piece of I O data that is moved on the network 38 1744085 03 2009 DeviceNet Communication Module Management Assemble the Physical Network The following procedure describes the connections required to construct a physical DeviceNet network 4 WARNING UNINTENDED EQUIPMENT OPERATION The application of this product requires expertise in the design and programming of control systems Only persons with such expertise should be allowed to program install alter and apply this product Follow all local and national safety codes and standards Failure to follow these instructions can result in death serious injury or equipment damage CAUTION INSTALLATION UNDER POWER Disconnect all power to the PLC before making the network connection Failure to follow these instructions can result in injury or equipment damage Step Action Comment 1 Install the DeviceNet scanner module in the desired PLC slot The connection figure see page 38 above shows the scanner in slot 2 of the
84. ow 12 FGP ERR VAL 2BYTES INF TOOHIGH written value not in the range of the register MSB value is too high 13 FGP_ERR_VAL_2BYTES_INF_TOOLOW written value not in the range of the register MSB value is too low 16 FGP_ERR_VAL_INVALID written value not a valid value 20 FGP_ERR_BAD_ANSWER external request sends back an error frame Case of a read error Error Code Error Name Explanation 1 FGP_ERR_REQ_STACK_FULL external request sends back an error frame 3 FGP_ERR_REGISTER_NOT_FOUND register not managed or the request needs super user access rights FGP_ERR_ANSWER_DELAYED external request answer postponed FGP_ERR_NOT_ALL_REGISTER_FOUND one or both registers cannot be found 1744085 03 2009 67 DeviceNet Communication Module Management Using of main registers for a simplified management Before commissioning a motor starter it is interesting to know which registers you access and in which order Illustration of registers used The following illustration gives you basic information about commissioning through registers configuration control and monitoring state of the system measurements faults and warnings acknowledgment Starting from the predefined factory configuration you will be able to visualize and even anticipate the behavior of your system Configuration Factory setting Registers 685 6 7 Communication module output assignment LO1 OA1 3 13 23 Regi
85. p Action Comment 1 In the project view double click the motor starter You will be asked if you want to register the motor starter with the EDS Wizard 2 Click Yes The Wizard s welcome screen appears Click Next The Options screen appears Select Create an EDS file and click Next RSNetWorx will upload the motor starter s identity information displayed in the Device Description Screen 5 Record the product name string TeSysU1 and click The Input Output screen appears Next 6 Check Polled and enter the appropriate values for input and output sizes Also check COS and enter an input size value of 1 Click Next 7 Change the icon if you wish at the Change Graphic The Final Task Summary screen appears Image and click Next 8 Verify that the motor starter has been registered and The completion screen appears click Next 9 Click Finish The EDS Wizard closes 10 Add the motor starter to the Scanlist See Add the Motor Starter to the Scanlist page 42 Saving the Configuration Save your configuration by selecting File Save from the RSNetworx menu This is a standard Windows command 50 1744085 03 2009 DeviceNet Communication Module Management Inserting TeSys U in the DeviceNet Network Introduction To insert TeSys U in the DeviceNet network you must select one of the seven variants described below Selection Criteria of a TeSys U Variant Choose TeSys U variant When you need
86. position of rotary knob on power base followed by return to Ready position e Communication break followed by restoration Failure to follow these instructions can result in death serious injury or equipment damage 1744085 03 2009 45 DeviceNet Communication Module Management Word 1 DeviceNet path 6C 1 5 ScSt CAd CMuL R Sc Ad Sc Mu L R bit 0 Run forward V V V bit 1 Run reverse V V V bit 2 Reserved bit 3 Fault reset if register 451 102 or 104 fault acknowledgment causes a V Y V return to communication module factory settings This bit is active on rising edge and must be reset to 0 by programming bit 4 Reserved bit 5 Launch automatic thermal overload fault test V This bit is active on rising edge and must be reset to 0 by programming bit 6 11 Reserved bit 12 Launch trip test via communication bus V This bit is active on rising edge and must be reset to 0 by programming bit 13 15 Reserved NOTE Fault reset bit must be set to 1 and reset to 0 to acknowledge a fault The following table gives a description of the Control of Communication Module Register 703 Word 2 DeviceNet path 6C 1 4 Sc St C Ad C Mu L R Sc Ad Sc Mu L R bit 0 2 Reserved bit 3 Reset warning communication loss V Y Y This bit is active on rising edge and must be reset to 0 by
87. programming bit 4 15 Reserved NOTE Reset warning bit must be set to 1 and reset to 0 to acknowledge a warning loss of communication The following table gives a description of the Output Control Register 700 Word 3 DeviceNet path 6C 1 1 ScSt CAd CMuL R Sc Ad Sc Mu L R bit O Control of output LO1 if 685 2 V V V bit 1 Control of output OA1 if 686 LSB 2 V V V bit 2 Control of output OA3 if 686 MSB 2 V V V bit 3 15 Reserved Instance 101 PKW Request Object This assembly is vendor specific It is used to implement the request object of PKW protocol Byte 7 Byte 6 Byte 5 Byte 4 Byte 3 Byte 2 Byte 1 Byte 0 See PKW Objects page 63 for details Instance 102 PKW Request and Extended Motor Starter This assembly is vendor specific Bytes 0 to 7 Byte 8 Byte 9 See Instance 101 above Reserved value 0 See Instance 5 above Instance 103 PKW Request and TeSys U Control Registers This assembly is vendor specific Bytes 0 to 7 Byte 8 to 13 See Instance 101 above See Instance 100 above 46 1744085 03 2009 DeviceNet Communication Module Management Input Assembly Dat a Instance 50 Basic Overload Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Instance 51 Extended Overlo
88. r block The wire to wire link is also used to insert for example a local control or an external stop control LULCOO9 Connection Cross Sections The following table shows the conductor cross sections that may be used on LULCOS terminals Connection Conductor type Cross section min max Solid conductor 0 14 1 mm 26 18 AWG Stranded conductor 0 14 1 mm 26 18 AWG 1 conductor Stranded conductor with cable end non insulated 0 25 1 mm 24 18 AWG insulated 0 25 0 5 mm 24 20 AWG 2 solid conductors 0 14 0 5 mm 26 20 AWG 2 stranded conductors 0 14 0 75 mm 26 20 AWG a as 2 stranded conductors with cable end non insulated 0 25 0 34 mm 24 22 AWG insulated 0 75 mm 20 AWG Connectors 3 and 6 pins Pitch 3 81 mm Tightening torque 0 2 0 25 N m 28 3 35 4 Ib in Flat screwdriver 2 5 mm 0 10 in 1744085 03 2009 21 Installation of TeSys U DeviceNet Module LULCO9 DeviceNet Connection Cross Sections The following table shows the conductor cross sections that may be with the DeviceNet open style connector Connection Conductor type Cross section min max Solid conductor 0 2 2 5 mm 24 12 AWG Stranded conductor 0 2 2 5 mm 24 12 AWG 1 conductor Stranded conductor with cable end non insulated 0 25 2 5 mm 24 12 AWG insulated 0 25
89. r information on how to register these EDS files in the RSNetWorx s EDS library system see Register the Motor Starter EDS page 39 36 1744085 03 2009 DeviceNet Communication Module Management The table below gives the associations between the 7 TeSys U variants and the associated EDS files names Variants names EDS file name TeSys U C Ad TE_TESYSU_C_ADeerrE eds TeSys UC Mu L TE TESYSU C MU L E eds TeSys UC Mu R TE TESYSU C MU R e E eds TeSys U Sc Ad TE TESYSU SC AD e E eds TeSys U Sc MuL TE TESYSU SC MU L E eds TeSys U Sc Mu R TE_TESYSU_SC_MU_ReeeeE eds TeSys U Sc St TE_TESYSU_SC_STeee E eds e Sc and C letters stand for Starter Controller and Controller respectively e St Ad and Mu letters stand for Standard Advanced and Multifunction control unit respectively e Rand L letters stand for Remote and Local configuration Local configuration is supported by Multifunction Control Unit gt V3 x For more information on TeSys U variants see Selection Criteria of a TeSys U Variant page 51 1744085 03 2009 37 DeviceNet Communication Module Management Configuring the Motor Starter with Configuration Software Introduction Before You Begin Connection Figure Use these sample instructions to configure an Allen Bradley SLC 500 PLC 1747 SDN with a DeviceNet controller at the head of a TeSys U Motor Starter equipped with a
90. res One twisted pair is for transferring data and one is for supplying power This results in simultaneous support for devices that receive power from the network like sensors and those that are self powered like actuators Devices can be added or removed from the bus line without powering down the fieldbus DeviceNet supports a trunk line drop line network configuration The implementation of multiple branched zero and daisy chained drops should be established during system design The network must be terminated at each end with 121 Q resistors A sample DeviceNet network topology is shown in the following figure o o trunk line drop line 0 to 6 m 0 19 7 ft daisy chain drop off branched drop off network node trunk line tap junction terminating resistor zero drop short drops OOANOORWN Transmission Media Your implementation of thick thin or flat cables for trunk lines and drop lines should be established during system design Thick cables are generally used for trunk lines Thin cables can be used for trunk or drop lines Refer to ODVA litterature for information on how to design and install your complete DeviceNet installation Thin cable must be used to connect TeSys U on the DeviceNet network If a complete daisy chaining solution is selected the total length of the daisy chain must not exceed 100 meters without repeaters You can connect a maximum of 63 TeSys U devices on the DeviceNet network if the
91. roller Local Remote Mode DeviceNet Register Control Comment Value path Mode 6B 1 22 683 Outputs 13 and 23 are controlled only by the bus default value R t es 9 Status of inputs I 1 and I 2 does not affect outputs 13 and 23 Outputs 13 and 23 are controlled only by inputs I 1 and 1 2 Local 1 oda Controlling outputs via the bus is not taken into account If 1 10 1 Local mode Outputs 13 and 23 are controlled by Mixed inputs 1 1 and 1 2 Input Outputs 13 and 23 are controlled only by 1 10 takes the bus MS If 1 10 0 R te M priority Rate Remote Made Status of inputs 1 1 and I 2 does not affect outputs 13 and 23 Inversion of Outputs Configuration Depending on your needs signalling run stop etc you can assign a NO or NC status to outputs OA1 OA3 and LO1 by configuring Inversion of outputs configuration register DeviceNet Register Bit Value Comment path 0 No inversion of output OA1 default value 1 Inversion of output OA1 0 No inversion of output OA3 default value 6B 1 23 684 1 1 Inversion of output OA3 5 0 No inversion of output LO1 default value 1 Inversion of output LO1 Output LO1 Configuration To change the assignment factory setting write another value 0 to 45 as described in Assignment of outputs LO1 OA1 OA 13 23 Assignment control factory setting of LULCO9 output LO1 is DeviceNet path Reg
92. scription OE hex Get_Attribute_Single Read 1 attribute 10 hex Set_Attribute_Single Write 1 attribute 1744085 03 2009 95 Object Dictionary DeviceNet Interface Object Description This object enables you to select the data that will be exchanged on the network through I O messaging A single instance instance 1 of the DeviceNet Interface Object is supported Instance Attributes The following instance attributes are supported Attribute Access Name Data Value ID Type 1 Set Get Poll produced Byte Instance 50 Basic Overload Instance 51 Extended Overload Instance 52 Basic Motor Starter Instance 53 Extended Motor Starter 1 EMS1 Instance 54 Extended Motor Starter 2 EMS2 Default Instance 110 TeSys U Monitoring registers Instance 111 PKW response object Instance 112 PKW response EMS2 Instance 113 PKW response TeSys U monitoring assembly instance 0 7 Instance 2 Basic Overload Instance 3 Basic Motor Starter Instance 4 Extended Contactor Instance 5 Extended Motor Starter EMS Instance 5 Extended Motor Starter EMS Default Instance 100 TeSys U control registers Instance 101 PKW Request object Instance 102 PKW Request EMS Instance 103 PKW Request TeSys U control 2 Set Get Poll consumed Byte assembly instance 0 7 3 Set Get COS produced Byte assembly instance 0 7 I
93. ster 602 Fault reset mode Manual Register 681 Timeout before fallback is initiated Register 682 Fallback on communication loss OA1 and OA3 0 Writing in the Control starter Register 704 Motor run forward command Motor run reverse command Monitoring Warnings Monitoring System status Register 460 Warning code or Reading the Register 455 Register 461 Warning type system status if an error has been detected get more information with Bit 455 2 System fault Bit 455 3 System warning x Bits 455 8 Motor average current ratio Monitoring Faults to 455 13 Register 451 Fault code or Register 452 Faulttype Check if the current value is correct To be used if needed fo unlock the system i Monitoring Measurement Control Acknowledgment Compulsory circuit Register 466 Average current ratio I Optional circuit Bit 703 3 Warning reset command Bit 704 3 Fault reset command 68 1744085 03 2009 Managing faults and warnings This chapter explains how to manage the different types of faults and warnings that may occur What s in this Chapter This chapter contains the following topics Topic Page Viewing a fault 70 Application faults 71 Internal Faults 73 Warnings Communication Loss 74 1744085 03 2009 69 Managing faults and warnings Viewing a fault A fault is signalled by vario
94. tion 1 Get Revision Ulnt 002 Attribute ID Access Name Data Type Value Description 1 Get MAC ID USInt 0 63 Read only attribute 2 Get Baud rate USInt 0 2 0 125 k 1 250 k 2 500 k Read only attribute 3 Get Set BOI Bus OFF Bool Upon Bus Off interrupt Interrupt 0 Hold the CAN chip in its bus off state 1 Reset the CAN chip and continue communicating 4 Get Set BusOff counter USInt 0 255 Number of times CAN was in bus off state 5 Get Allocation information Byte USInt 0 63 Allocation choice Master Address 255 not allocated Service Code Service Name Description OE hex Get Attribute Single Read 1 attribute Service Code Service Name Description OE hex Get Attribute Single Read 1 attribute 19 hex Set AttributesSingle Write 1 attribute OE hex Allocate Master Slave Requests the use of the Connection Set predefined Master Slave Connection Set OE hex Release Master Slave Indicates that the specified Connection Set connections within the predefined Master Slave Connection Set are no longer desired These Connections are to be released deleted 1744085 03 2009 87 Object Dictionary Connection Object Description Class Attributes The Connection Object provides for and manages the run time exchange of messages Instance 1 Attributes Explicit Message Instance
95. trol unit 1744085 03 2009 13 Installation of TeSys U DeviceNet Module LULCO9 MNS LED Description The software controlled MNS Module Network Status is a two color light emitting diode LED alternating between two states a Run state green color and an Error state red color MNS LED colors can be flickering every 50ms or blinking every 200ms or flashing 1 2 or 3 flashes or steady as described below 2 color Color display mode Meaning Action MNS LED Off No power or autobaud detection in progress or no error The LED repeatedly Check the device Flash Green flashes on for 500ms then Device is in pre operational state and no configuration OR off for 500ms connections have been made Wait for the end of auto addressing tional state The device i li G es Steady Operational state The device is online and connected Flash Red The LED flashes on for A minor fault has occured or one or more Restart communication 500ms then off for 500ms I O connections has timed out The device has detected an error that Check the MAC ID then a has made it incapable of communicating cycle power and restart R tical fault or link fail dd Pub Cal Taulit ornare on the network Duplicated MAC ID or communication Bus off Flashin The LED repeatedly The device has detected a network Restart communication OM flashes red for 500ms access error and is in Communication then green for
96. unning Rev Bool 455 7 AND 704 1 9 Get Ready Bool 455 0 10 Get Faulted Bool 455 2 11 Get Warning Bool 455 3 12 Get Set FaultRst Bool 704 3 0 gt 1 rising edge 13 Get FaultCode UInt 451 14 Get WarnCode Ulnt 460 15 Get CtrlFromNet Bool NOT 455 14 16 Get Set DNFaultMode UInt Action on network loss 0 Fault Stop 682 2 1 Ignore 682 0 2 Frozen 682 1 3 Inchange 682 3 4 Force FW 682 4 5 Force RV 682 5 17 Get Set ForceFault Trip Bool 704 12 Service Code Service Name Description OE hex Get Attribute Single Read 1 attribute Service Code Service Name Description OE hex Get Attribute Single Read 1 attribute 10 hex Set Attribute Single Write 1 attribute 05 hex Reset Reset Inactivity Watchdog timer 1744085 03 2009 91 Object Dictionary Control Supervisor State Event The following diagram shows the control supervisor state event matrix Switch Off Y Non Existant Switch 2 Main Power Off Fault Detected Reset e Startup J Faulted Initialization sd Fault A A Reset Not_Ready Fault Detected P Faut Stop Main A main Complete Power ony Power Off Fault Detected Read y a Stop Faul Stop Ha Complet
97. us different indicators e status of LULCO9 communication module s LEDs with a power base status of rotary button on the power base 0 or trip status of outputs with a controller base status of the LEDs on the controller base status of output relays with a standard or advanced control unit internal signals sent to LULCO9 communication module with a multifunction control unit warning message s displayed on screen internal communication with the LULCO9 communication module presence of an exception code PLC report NOTE Warnings and faults are stored in specific registers Refer to Communication Variables User s Manual fault monitoring registers 450 to 452 and warning monitoring registers 460 to 461 70 1744085 03 2009 Managing faults and warnings Application faults Application fault acknowledgment Possible application faults are listed below They can be reset acknowledged manually automatically remotely Registers LULCO9 LUTM 451 452 N Fault number Fault bit 3000000 Application faults I LL Fault reset t E u 4 ERR line 2 FAULT Short circuit fault 1 021 SC Manual reset Over current fault 2 1 1 I off Depending on reset Thermal overload fault 4 _3 1 overload mode set in register 602 LUCMe multifunction control unit application fault 3 and 5 set to 12 See LUCMeeBL LUCM
98. ute may or may not affect the behavior of an object An object s behavior is an indication of how the object responds to particular events Objects within a class are called object instances An object instance is the actual representation of a particular object within a class Each instance of a class has the same set of attributes but has its own set of attribute values which makes each instance in the class unique The Object Dictionary describes the attribute values of each object in the device profile What s in this Chapter This chapter contains the following topics Topic Page Identity Object 82 Message Router Object 83 Assembly Object 84 DeviceNet Object 87 Connection Object 88 Control Supervisor Object 91 Overload Object 94 DeviceNet Interface Object 96 1744085 03 2009 81 Object Dictionary Identity Object Description Class Attributes Instance Attributes This object present in all DeviceNet products provides identification of and general information about Class and Instance Service the device Attribute ID Access Name Data Type Value Description 1 Get Revision Ulnt 01 Attribute Access Name Data Type Value Description ID 1 Get Vendor ID Ulnt 243 243 gt Schneider Automation Inc 2 Get Device type Ulnt 16h Motor Starter
99. viceNet Open Style Connector page 24 for more information The following connection types are established with DeviceNet s connection based model e explicit messaging connections Explicit messaging connections provide multipurpose point to point communication paths between two particular devices Explicit messages are used to command the performance of a particular task and to report the results of performing the task You can therefore use explicit messaging connections to configure nodes and diagnose problems DeviceNet defines an explicit messaging protocol that states the meaning or intended use of an explicit message within the CAN Controller Area Network data field The message consists of a Connection ID and associated messaging protocol information e I O messaging l O messages contain application specific data They are communicated across single or multicast connections between an application producer and its corresponding consuming application Because I O messages carry time critical messages they have high priority identifiers An I O Message consists of a Connection ID and associated I O data The meaning of the data within an I O Message is implied by the associated Connection ID The connection endpoints are assumed to have knowledge of the intended use or meaning of the I O Message Slave devices can produce data using one or more of the following I O message types depending on how the device is configured and the

TeSys U LULC09 DeviceNet Communication Module

Contents

Download Pdf Manuals

Related Search

Related Contents