AXL F BK ETH
Contents
1. Note on dimensions General data Color Weight Ambient temperature operation Ambient temperature operation Ambient temperature storage transport Permissible humidity operation Permissible humidity storage transport Air pressure operation Air pressure storage transport Degree of protection Protection class Mounting position Connection data Designation Connection method Conductor cross section solid stranded Conductor cross section AWG Interface Ethernet Number Connection method Transmission speed Transmission physics Transmission length 8515 en 06 AXL F BK ETH 45 mm 125 9 mm 74 mm The depth is valid when a TH 35 7 5 DIN rail is used according to EN 60715 traffic grey A RAL 7042 177g with connector and bus base module 25 C 60 C Mounting position wall mounting on horizontal DIN rail 25 C 55 C Mounting position any 40 C 85 C 5 96 95 non condensing 5 96 95 non condensing 70 kPa 106 kPa up to 3000 m above sea level 70 kPa 106 kPa up to 3000 m above sea level IP20 Ill IEC 61140 EN 61140 VDE 0140 1 Any observe temperature derating Axioline F connector Push in technology 0 2 mm 1 5mm 0 2mm 1 5mm 24 16 2 RJ45 socket auto negotiation and autocrossing 10 100 MBit s Half or full duplex mode automatic detection can be adjusted manually Ethernet in RJ45 twisted pair2. Ethernet Figure 3 Connection of the cables en PHOENIX CONTACT 7 8515 en 06 8 Configuration via rotary encoding switch You can configure the address assignment and other func tions using rotary encoding switches After modifying the switch position restart the bus coupler as the modification to the switch position does not take ef fect during operation 14 n MU 9 Pd Pd XN 2 8 x10 FO E 2 Dus 2 Cad 4AN Ag B 6 x1 Figure 4 Rotary encoding switch The code results from the sum of S1 x 10 plus S2 x 1 The image shows code 77 7 x 10 7 Function 5 159 DHCP name assignment OE 1A Activate connector and play mode 1B Deactivate connector and play mode 12C Resetting to the default set tings 8515_en_06 AXL F BK ETH 8 1 Remote access Switch position 00 At this switch position itis possible to remotely configure the device using corresponding tools e g Startup web based management WBM Behavior during initial startup after resetting the IP parameters or after resetting to default settings Default BootP activated DHCP deactivated A valid IP address is not assigned 0 0 0 0 and communica tion is therefore not possible The device transmits continuous BootP requests 2 s 4 s 8 s 2s until a valid IP address has been received Valid IP parameters are then automatically saved as config uration data on the device Each additional sta
3. Activate hardware acceleration for Modbus UDP Ili only following restart Command register 2006 E 0800 Deactivate hardware acceleration for Modbus UDP applied only following restart 8FOO Restart bus coupler 8FO1 Read parameter file again config svc When commands 8F00 and 8F01 are being executed the substitute value behavior of the outputs is active The hardware acceleration for Modbus UDP shortens the processing time of Modbus UDP requests It is enabled by default In the event of compatibility problems deacti vate the hardware acceleration with code 0800hex in the command register and perform a restart This setting is stored retentively PHOENIX CONTACT 21 16 9 Electronic rating plate 2075 2089 The electronic rating plate contains the basic information on the module Only read access is enabled to the registers Modbus register Maximum length of the register Name of device 2089 Manufacturer name 8515 en 06 AXL F BK ETH 16 10 Status register 7996 The status register indicates the status of the bus coupler Each bit has a different meaning Several bits can be set si multaneously No bit is set in normal operation without er rors Code hex 0001 1 An error occurred in the local bus e g a bit in the diagnostic register is set o Noemor lt 1 0002 1 A Net Fail occurred active substitute values match the reference configuration un 3
4. ses 9999 For further information on the assignment of bytes and words please refer to the module a specific documentation data sheet user manual 8515_en_06 PHOENIX CONTACT 19 16 6 Register tables for the bus configuration frame 1401 1649 1701 1763 Both register tables map the currently loaded bus configura tion frame of the connected devices When plug and play mode is activated the bus configuration frame that is physically present is sent When plug and play mode is deactivated the stored refer ence configuration is sent Any differences between the stored reference configuration and the bus configuration that is physically present are indi cated by diagnostic registers 7997 to 7999 The register ta bles can be used to monitor the bus configuration in the user application The entire table can always be read the Num ber of entries register indicates how many entries there ac tually are Register table for DeviceType 1401 1649 The DeviceType is a manufacturer specific module identifi cation It can be used to replace and operate modules of the same type within a bus configuration For example a 16 channel output module with screw connection technology can be replaced by a module with spring cage connection technology even though it does not have the same order number On the other hand a different functionality e g 32 channels instead of 16 is indicated by a different Device
5. Type In this case the DeviceType acts as a uniquely assigned ID but the module functionality cannot be directly derived from it e g by evaluating a specific bit Should this be neces sary use the relevant PDI objects for this see module spe cific data sheet Structure of the register table Index Contents CT cU DeviceType 1st device 1402 E We RE exo der device 1647 1648 Re 8515 en 06 AXL F BK ETH Register table for the number of process data registers for local bus devices 1701 1763 This register table indicates the number of registers in the process data register tables occupied by each device 8000 8999 9000 9999 This information can be used to dynamically adapt the user application to changes in the bus configuration The offset for the relevant device in the pro cess data register table can therefore be calculated in the user application Structure of the register table index Contents o 1700 Number of entries 1 63 1701 Number of process data reg 1st device isters 1763 Number of process data reg 63rd device isters PHOENIX CONTACT 20 16 7 1989 The register table shows the error number priority channel group module and error code information contained in diag nostic object 0018 for every device Register for I O diagnostics 1800 For every device the first message is displayed with the highest priority You can
6. max 100 m PHOENIX CONTACT 4 Interface Axioline F local bus Connection method Transmission speed Interface Service Number Connection method System limits Number of supported devices NOTE Electronics may be damaged when overloaded AXL F BK ETH Bus base module 100 MBit s 1 Micro USB type B max 63 per station Observe the logic current consumption of each device when configuring an Axioline F station It is specified in every module specific data sheet The current consumption can differ depending on the individual module The permissible number of devices that can be connected therefore depends on the specific station structure Protocols supported Protocols supported Supply of the bus coupler Supply of communications power UL Maximum permissible voltage range Current supply at Upus Current consumption from UL Power consumption at U D Error messages to the higher level control or computer system to ensure that it blows in the event of an error None Mechanical tests Vibration resistance in acc with EN 60068 2 6 IEC 60068 2 6 Shock in acc with EN 60068 2 27 IEC 60068 2 27 Continuous shock according to EN 60068 2 27 IEC 60068 2 27 Conformance with EMC Directive 2004 108 EC Noise immunity test in accordance with EN 61000 6 2 Electrostatic discharge ESD EN 61000 4 2 IEC 61000 4 2 Electromagnetic fields EN 61000 4 3 IEC 61000 4 3 Fast transients burst EN 61000 4 4
7. tion error in the controlling process the bus coupler can re spond appropriately via the process data watchdog When activating the process data watchdog it is started by the first write process and the next write process is expected within the timeout period During error free operation the write process is performed during the timeout period and the watchdog is restarted triggered Reading calls do not trigger the process data watchdog 8515 en 06 AXL F BK ETH Net fail If there is no triggering during the timeout period an error oc curred Two responses follow All outputs are set to the configured substitute value The Net Fail signal is set NET LED is red and bit 1 in status register 7996 is set For safety reasons the user cannot stop the watchdog once it has been activated If the user terminates the controlling application there is no watchdog triggering when the timeout period elapses the Net Fail signal is set and the parameterized substitute value behavior is executed After the watchdog has performed its task the outputs are only enabled again after acknowledg ment Acknowledge error message To reset the error it must be acknowledged The following options are available Web based management Modbus register 2006 l Configuring the process data watchdog When the error is acknowledged the watch dog is restarted This means that it must be triggered during the
8. 8042hex Response to Write PDI object 8041 pex Amount of data read in bytes 8042hex 0 8515 en 06 PHOENIX CONTACT 25 Error class error code 0000 No error 0000 An error has occurred negative response ID of error message Additional code More detailed information about the error cause Should an error occur the error message details the error class error code and additional code For the meaning of this error code please re fer to the AXL F SYS DIAG user manual 8515_en_06 AXL F BK ETH 17 3 Example read PDI object The PDI read service can be conveniently used with the Modbus function code FC23 read write Alternatively you can use FC16 write and FC3 read The contents of the VendorlD object manufacturer identifi cation of the first module should be read after the first bus coupler To this end PDI channel 1 6010 6210 should be used Read request Write the following values via FC16 or FC23 to register 6010 onwards Modbus Byte Con address 6010 0 Command i exe 6011 2 00 Slot 6012 4 00 Subst Head PDI object 1st local bus device No subslot 8 00 Reserved Reserved 6013 6 00 PDlobject 00025 Ven 7 02 dorlD manufac turer identification 6014 8 00 Subindex Nosubindex Number of Read therefore PDI data bytes 00 Response The result is provided in register 6210 and onwards As described before
9. IEC 61000 4 4 Transient surge voltage surge EN 61000 4 5 IEC 61000 4 5 Conducted interference EN 61000 4 6 IEC 61000 4 6 Noise emission test according to EN 61000 6 3 Radio interference properties EN 55022 Approvals For the latest approvals please visit phoenixcontact net products 8515 en 06 NOTE Electronics may be damaged when overloaded Modbus TCP UDP SNMP HTTP BootP DHCP FTP TFTP 24 V DC 19 2 V DC 30 V DC including all tolerances including ripple 2A typ 105 mA without I Os and U 24 V max 583 mA with 2 A at Ugus for the I Os and U 24 V typ 2 5 W without I Os max 14 W with 2 A load at Ugus for the I Os Provide external fuses for the 24 V U area The power supply unit must be able to supply four times the nominal current of the external fuse 5g 30 g 10g Criterion B 6 kV contact discharge 8 kV air discharge Criterion A Field intensity 10 V m Criterion B 2 kV Criterion B DC supply lines 0 5 kV 0 5 kV symmetrical asymmetrical field bus cable shield x1 kV Criterion A Test voltage 10 V Class B PHOENIX CONTACT 5 5 Internal circuit diagram FE Service Reset i 24 Figure 1 8515 en 06 Bop V Internal wiring of the terminal points Key FE Service Heset Local bus RJ45 licite r3 Usus AXL F BK ETH Functional earth ground Service interface Reset button Axioline F local bus hereinafter referred t
10. M RC RESTE Et PIT Rte Ht EP MUN NU E NR 1 2 Table OF COMP NE E OUI 2 3 rers dino oz t PN EE 3 4 l Tenlrezibeorio e LP 4 5 Iriternial Cir CUIU dagran saion a a eerta citm N AN 6 6 Connecting Ethernet and SUDDIY anreisen a e a E 7 7 GOnNectonexamMplE nsession 7 8 Configuration via rotary encoding switch ccccccseeeeceeeeceeeeeeeeeeceeeeesaeeeseeeeesaeeeseeeesseeesseeeetas 8 9 Local status and diagnostic indicators esses 11 10 MEeSorDUWON rurea E TN 13 11 Service INLET ACE P ETT 14 12 Startup behavior of the bus coupler seessessssessssesseeeeneee nennen nnn nnn nnns 15 lo ennieiloebre t dda 16 14 Monitoring of communications power UL UL MOnitOr ccceccccseeeeseeeeeeeeeeneeeesseeeeneeeeees 17 15 Substitute Value DENA VION eee eee soe eae i ee eed aad 17 16 MOGDUS Protocols and registers 125r Ure Srudud abu pe oe exa Epi Dedc Se aec patet Uno dE dn kee edd ee ene 17 Tf JJAGCOSSIO TDI ODIJOGCISCidesuetaxi faciie aded eet Otaed dE hdsent hediiae Iietm Rides patema uUo abe seus anunedsmnmed vines 23 18 Simple Network Management Protocol SNMP ccceecccseeeeceeeeeeeeeeseeeeeseeeeneeeesseeeeseeeeeas 31 19 WBM Web based management sseesseesseeeeeee eene nenne nnn nnne he nasus esses anna nnus 31 20 Prw Upda ei es i tdietud eaa etatcetsc tai Pai
11. can use the PDI service with Modbus function code FC23 very easily access to the request and the confirmation table is possible with just one access The confirmation table can only be accessed as read only whereas both read and write access are enabled for the re quest table In the case of read only access to the request table the most recently written data is output not the PDI confirmation The 6xx5 data registers e g 6015 6215 have a virtual length This means that data can be transmitted as long as the maximum length of the Modbus telegram is not ex ceeded The data is mapped internally onto the following registers not directly thereby ensuring a higher packing density of the PDI channels Use a Modbus function code for access which allow access to multiple registers in one re quest FC3 FC16 or FC23 As such the register e g 6215 functions as a start ad dress Always use 125 as the register number when read accessing a PDI object PDI read In the case of write ac cess to a PDI object PDI write use the corresponding length Please see the following examples As such read access to the confirmation table is granted with a specified length The specified number of registers is always output If the actual data length is lower e g PDI ob ject is smaller or contains a negative confirmation all re maining registers are filled with 0000 The actual length of the PDI object can be found in the fi
12. details The objects are addressed via an object index e g 001845 DiagState For detailed information on the objects present on a module please refer to the module specific documentation You can access the PDI channel via Modbus TCP as well as via Modbus UDP To this end register sets are used with which a tunnel method can be implemented This method is explained below y o 01010101010101 01010101010101 01010101010101 01010101010101 01010101010101 01010101010101 Process data Application register 8000 8999 Process data 9000 9999 Modbus TCP or Modbus UDP PDI tunnel register Objects 6010 6089 Fp cnanne 6210 6289 Axioline F Axioline F Controller Ethernet Bus coupler P local bus I O module Figure 8 Access to PDI objects 8515 en O6 PHOENIX CONTACT 23 17 1 Functional description Eight Modbus PDI channels are provided which are to be assigned to the Modbus masters in the application without causing conflict NOTE Data loss Q Use an appropriate channel assignment to ensure that one channel is only ever used by one master Each Modbus PDI channel features a request table and con firmation table The data necessary for a PDI request PDI read or PDI write is written to the request table by means of Modbus write ac cess FC16 FC23 Subsequently the PDI confirmation is read out of the confir mation table via Modbus read access FC3 FC4 FC23 You
13. register 6215 has an internal virtual length Use a Modbus function code for access to the reg isters marked with which allow access to multiple registers in one request Register 6210 functions as the start address 125 can always be used as the register number in the case of read access PHOENIX CONTACT 26 Positive response Modbus Con address hex e210 o 80 6211 2 00 Slot Let IEEE 6212 4 00 Subslot 5 00 Reserved 6213 6 00 PDlobject NE Copy of request 7 index 00 Subindex Number of PDI data bytes read 00A045 7 bytes includ ing zero termi nator ASCII coded Message code Hesponse to Read PDI object Copy of request Copy of request 6214 MCN Bl 6215 10 00 Error class 00 Error code Read data 13 30 a 35 30 core 36 34 UT ae bes Eid Top up to an even number of bytes 8515 en 06 AXL F BK ETH Negative response Modbus Byte Con address O NO O Message code Response to Read PDI object Slot Copy of request Copy of request Copy of request Copy of request Error message therefore 0 Error message O NO E O NO NO Subslot Reserved PDI object index Subindex Number of PDI data bytes Error class Error code Additional code O NO C2 O NO I NO XX XX 6215 6216 XX XX PHOENIX CONTACT 27 17 4 E
14. 0008 iai 4 0010 Nul x 5 0020 Te e 000 Reserved 7 00 Reewd 0100 Pee 0200 adm m HO 040 Resemwed 11 0800 mE Reserved 12 1000 1 U Monitor communications power too low Voltage OK 13 2000 U Monitor communications power too high LL Voltage OK 14 4000 U Monitor communications power too low acknowledge code 0080hex via register 2006 a 15 8000 1 UL Monitor communications power too high acknowledge code 0080 via register 2006 0 Noemrstred PHOENIX CONTACT 22 AXL F BK ETH 16 11 Diagnostic status register 7997 16 12 Diagnostic parameter register 7998 7999 For the meaning of this register please refer For the meaning of this register please refer to the AXL F SYS DIAG user manual to the AXL F SYS DIAG user manual 17 Access to PDI objects PDI stands for parameter diagnostics and information The PDI channel is used in addition to the process data channel in the Axioline F system for the demand oriented acyclic transmission of parameter and diagnostic data as well as other information Each Axioline F device has this channel and can use it independently of the process data Objects created in the Axioline F device can be accessed via the PDI channel using services These objects can be used for example to set measuring ranges to specify the substitute value behavior of outputs in the event of a bus error or to read diagnostic
15. AXL F BK ETH Axioline F bus coupler for Ethernet PHOENIX CONTACT 2014 05 14 Data sheet 8515 en O6 1 Description Valid from firmware version 1 10 Ethernet features The bus coupler represents the link between an Ethernet 2 Ethernet ports with integrated switch network Modbus TCP and the Axioline F system Transmission speed of 10 Mbps and 100 Mbps You can connect up to 63 Axioline F devices to an existing Rotary coding switches for setting the IP address as Ethernet system with the help of the bus coupler signment and other functions Modbus TCP UDP support BootP and DHCP Firmware can be updated Features of Axioline F Upto 63 additional Axioline F devices can be connect ed Runtime in the bus coupler is negligible almost O us for Modbus UDP Typical cycle time of the Axioline F local bus is around 10 us Diagnostic and status indicators NOTE In the event of a connection abort outputs retain their last state By default upon delivery the process data watchdog is deactivated Observe the specifications in Monitoring This data sheet is only valid in association with the UM EN AXL F SYS INST user manual Make sure you always use the latest documentation It can be downloaded from the product at phoenixcontact net products ej OO D OGD OO GD GD 0 GD OO OD Likconracr GDC INSPIRING INNOVATIONS AXL F BK ETH 2 Table of contents 1 DES CUDUO
16. BK ETH 16 Modbus protocols and registers The bus coupler supports a Modbus TCP server and a Mod bus UDP server The Modbus protocol can be used in both in a connection related TCP and wireless UDP manner 16 1 Modbus connections The bus coupler supports up to eight Modbus TCP connec tions simultaneously The connection can access different addresses simultane ously Since eight connections are supported a connection can quickly be restored This means that the client can success fully restore an interrupted Modbus connection The UDP server is wireless l In applications with high demands on the re sponse time it is recommended that Modbus UDP is used to access the process data In this case the runtime in the bus coupler is negligible just a few us 16 2 Modbus conformance classes The bus coupler supports Modbus conformance class 0 16 3 Modbus function codes The following function codes are supported ER NN NN code registers and inputs isters C6 i F Write single reg Write word for output data isters FC16 Write multiple Write several output words registers FC23 Read write mul Read and write several pro tiple registers cess data for inputs and out puts PHOENIX CONTACT 17 AXL F BK ETH 16 4 Modbus register Modbus register table Access with function code 16 bit word Number of local bus devices entries FC3 FC4 Device type of local bus devices 4 registe
17. CT 12 10 Reset button The reset button is located beneath the top marking label on the bus coupler _ A Nae I L as S Figure 6 Reset button 1 Labeling field 2 Reset button The reset button has two functions Restarting the bus coupler Resetting of the default settings 10 1 Restarting the bus coupler The bus coupler is restarted when the button is pressed dur ing operation The outputs of the station are set to the parameterized sub stitute values The process image of the inputs is not re read 8515 en 06 AXL F BK ETH 10 2 The bus coupler is supplied with the following default set tings Restoring the default settings Password private IP settings IP address 0 0 0 0 Subnet mask 0 0 0 0 Default gateway 0 0 0 0 BootP activated Firmware update Firmware update on next deactivated restart TFTP server IP address 172 16 40 201 Name of firmware update c2688459 fw file System identification Name of device AXL F BK ETH Description Ethernet bus terminal Installation location Unknown Contact Unknown Process data monitoring Process data watchdog timeout Plug and play mode 0 deactivated activated If you wish to restore the default settings proceed as fol lows e Disconnect the power to the module e Press and hold the reset button e Switch on the power The LEDs indicate the initialization phase Starting firmware LED HDY HDY Yellow Initializing firm
18. Plug and play mode is activated mode Plug and play mode is deactivated RDY Greeny Ready yellow Flashing low i UL CO Configuration Yellow ON The startup parameterization is faulty Red ON _ The active configuration of the local bus differs from the saved con figuration Yellow Firmware update is being performed flashing Flashing Firmware update has failed yellow red Hed ON Rotary encoding switches are set to an invalid reserved position Device is not ready to operate 8515 en O6 PHOENIX CONTACT 11 AXL F BK ETH Designation Color Meaning State Description to transmitted Active configuration is active data exchange with invalid process flashing data PDI channel can be used flashing yellow red ing Red ON General local bus error Communication error Local bus device has been removed or configured device is missing Reset at a local bus device Serious device error at a local bus device local bus device can no longer be reached Yel Error Yellow ON I O warning at a local bus device low Red ON I O error at a local bus device red No I O messages present LNK 1 2 Green Link port 1 2 Connection via Ethernet to a module via port 1 2 established OFF No connection established via port 1 2 ACT 1 2 Yellow Activity port 1 2 Transmission or reception of Ethernet telegrams at port 1 2 OFF No transmission or reception of Ethernet telegrams at port 1 2 8515 en O6 PHOENIX CONTA
19. age therefore 0 Error message E NO Q i O N C2 NO Subslot Reserved PDI object index Subindex Number of PDI data bytes Error class Error code Additional code O N C2 oo O N Co gt XX X 6235 6236 x lt O A NO NO XX XX PHOENIX CONTACT 29 8515_en_06 AXL F BK ETH 17 5 Exception Codes In order to increase user comfort the main problems that can occur when accessing the PDI channel are indicated directly via a Modbus exception In addition to the standard exception codes 01 04 see Modbus specification some user defined exception codes have been defined specifically for PDI channel handling ILLEGAL FUNCTION ILLEGAL DATA ADDRESS General ILLEGAL DATA VALUE 3 3 Write to data register 60x5 even though PDI read was se lected in the Service command code field PDI length register 60x4 length of the data to be written in bytes does not match the actual length DEVICE FAILURE 4 4 Internal failure e g maximum number of connections ex ceeded mM Device cannot be reached timeout 16 10 MBUS PDI ERR DOUBLE USE CH An attempt was made to use the same communication channel with multiple TCP connections An attempt was made to use a communication channel used with a TCP connection via UDP MBUS PDI ERR ILLEGAL SVC CODE 17 11 The Service code field register 60x0 does not contain a valid service code 0041 is valid for PDI Read and 004216 for PDI Writ
20. e MBUS PDI ERR USER PROBLEM 18 12 An error occurred on a PDI Write request triggered by writing to register 60x5 For additional information referto the confirmation register 62xx MBUS PDI ERR INVALID DATA 19 13 No valid confirmation that can be read via the confirmation table register 62xx In this case an access attempt re turns the specified exception 8515 en O6 PHOENIX CONTACT 30 18 Simple Network Management Protocol SNMP The bus coupler supports SNMP v1 and v2c Management Information Base MIB For the object descriptions please refer to the ASN1 de scriptions for this product The corresponding latest MIBs are available on the Internet at phoenixcontact net prod ucts The password for read access is public and cannot be changed By default upon delivery the password for write read access is private and can be modified at any time 8515 en 06 AXL F BK ETH 19 WBM Web based management The device has a web server which generates the required pages for web based management and depending on the requirements of the user sends them to a standard web browser Web based management can be used to access static infor mation e g technical data MAC address or dynamic infor mation e g IP address status information local bus struc ture and local bus diagnostics Calling web based management The device web server can be addressed using the IP ad dress if configu
21. eld Number of PDI data bytes If the actual length is longer only the requested data is output 8515 en 06 AXL F BK ETH PHOENIX CONTACT 24 AXL F BK ETH 17 2 Structure of the Modbus PDI communication channels Modbus PDI communication channel 1 PDI request PDI confirmation Modbus Byte Modbus Byte Positive response Negative register oe response 6010 II ow rm Fari Sia Sia sore 4 Subsil ere 4 Subio Subsoi 5 Reserved 8 Reserved Reseved 6013 P PDI object index 6213 p depo PDI object index PDI object index ara e Sibindex G4 8 Suinde Subndek d uem cemere data bytes bytes pes per DU a E soie e216 Additional code pe 3 EB e017 ge OT IZZ I lx es we SC Le ee ee ee ee Modbus PDI channels and corresponding Modbus Slot registers Position of the module in the local bus Modbus PDI communication channel Subslot Specify a subslot if you wish to access a submodule PDI request e g IO Link Not used at present 0 6010 6015 6020 6025 6080 6085 PDI confirmation PDI object index 6210 6215 6220 6225 6280 6285 Seemodule specific data sheet PDI object subindex Command code See module specific data sheet 004112 Read PDI object 0042 Write PDI object Number of PDI data bytes For command code Message code 0041 hex 0 0042hex Amount of data to be written in bytes 8041hex Response to Read PDI object For message code
22. eo em cdatea ss e id tee eee ORI RE 31 8515 en 06 PHOENIX CONTACT 2 3 Ordering data Description Axioline F bus coupler for Ethernet including bus base module and con nectors Accessories Axioline F bus base module for housing type BK Replacement item Axioline F short power connector for e g AXL F BK Replacement item RJ45 connector shielded with bend protection sleeve 2 pieces gray for straight cables for assembly on site For connections that are not crossed itis recommended that you use the connector set with gray bend protection sleeve Connector Adapter RJ45 connector shielded with bend protection sleeve 2 pieces green for crossed cables for assembly on site For connections that are crossed it is recommended that the connector set with green bend protection sleeves is used Connector Adapter CAT5 SF UTP cable J 02YS ST C HP 2 x 2x24 AWG heavy duty instal lation cable 2 x 2 x 0 22 mm solid conductor shielded outer sheath 7 8 mm diameter inner sheath 5 75 mm 0 15 mm diameter Cable conduc tor CAT5 SF UTP cable J LIO2YS ST C H 2 x 2 x 26 AWG light duty flexi ble installation cable 2 x 2 x 0 14 mm stranded shielded outer sheath 5 75 mm x 0 15 mm diameter Cable conductor Crimping pliers for assembling the RJ45 plugs FL PLUG RJ45 for as sembly on site Tools Zack marker strip for Axioline F device labeling in 2 x 20 3 mm pitch un printed 25 section for indi
23. he I O modules as well as the bus configuration After the bus configuration has been changed e g module replacement the bus coupler prevents process data from being written bit 3 is set in the status register 7996 and the LED CO lights up yellow Modify the parameterization as appropriate and acknowl edge this with code 0008 in the command register 2006 The bus coupler will then enable the output of pro cess data PHOENIX CONTACT 15 13 Monitoring Ethernet communication is monitored by a process data watchdog The following actions are monitored Client application Ethernet connection Process data exchange If the timeout period expires for the activated process data watchdog OUT process data is blocked The parameter ized substitute value behavior of I O modules is performed The error is indicated by the NET LED red on In this state Net Fail OUT process data can continue to be updated by the application Following a Net Fail reset sub stitute values are then replaced by the latest process data NOTE In the event of a connection abort outputs retain their last state The process data watchdog is deactivated by default Activate the process data watchdog before starting up an application Function of the process data watchdog If station outputs are set the controlling process must be able to access the station In the event of an error e g network line interrupted or func
24. name consists of one set part which is based on the order designation and a variable part which is deter mined by the switch position The first part of the station name is AXL F BK ETH The set number is added This results in the following station names AXL F BK ETH 051 AXL F BK ETH 159 Behavior during initial startup after resetting the IP parameters or after resetting to default settings A valid IP address is not assigned 0 0 0 0 and communica tion is therefore not possible The device transmits continuous DHCP discover messages until a valid IP address has been received Each additional startup Within the first minute DHCP requests are transmitted with the last valid IP address Three cases are possible 1 The DHCP server accepts the desired address The device starts with this IP address 2 The DHCP server assigns a new IP address The device applies the new IP parameters 3 The DHCP server does not respond The device transmits continuous DHCP Discover messages until new IP parameters have been received 8515 en 06 AXL F BK ETH 8 4 Fixed address Switch position 0A Behavior during initial startup after resetting the IP parameters or after resetting to default settings A valid IP address is not assigned 0 0 0 0 and communica tion is therefore not possible Assign an address initially with another switch position Each additional startup After a voltage reset the device maintai
25. ns the IP address which was assigned last l 8 5 Resetting IP parameters With this switch position modifying the IP ad dress via tools or web based management is not possible Switch position OE The IP parameters stored on the device are reset All other settings made on the device are retained A BootP is activated for switch position OO P address subnet mask 0 0 0 0 As long as the switch position OE remains selected no con nection to the device can be established IP communication is deactivated LED NET static yellow PHOENIX CONTACT 9 8 6 Plug and play mode Switch position 1A activate connector and play mode Switch position 1B deactivate connector and play mode Plug and play mode enables local bus modules connected in the field to be started up using the bus coupler without a higher level computer engineering system If connector and play mode is enabled the writing of pro cess data is rejected Read access to process data is possi ble If connector and play mode is disabled the bus is only started up if the configuration of the connected bus matches the saved configuration See also section Startup behavior of the bus coupler 8 7 Resetting to the default settings Switch position 12C All settings are reset to default settings including IP param eters ing up as soon as the RDY LED lights up green A connection to the device however cannot be established in this s
26. o as local bus RJ45 interface Power supply unit with electrical isolation Microcontroller Power supply unit LED Electrically isolated areas PHOENIX CONTACT 6 AXL F BK ETH 6 Connecting Ethernet and supply 6 1 Connecting Ethernet Connect Ethernet to the bus coupler via an 8 pos RJ45 con nector The Ethernet connections are set to autocrossing auto crossover l Shielding The shielding ground of the connected twist ed pair cables is electrically connected with the socket When connecting network seg ments avoid ground loops potential trans fers and voltage equalization currents via the braided shield Observe bending radii The housing dimensions specified under Di mensions refer to the bus coupler with I O connectors without Ethernet connection When installing the bus coupler in a control box observe the bending radii of the Ethernet cables and the connectors used e g FL CAT5 FLEX 30 mm for fixed installation and FL CAT5 HEAVY 30 mm without outer sheath and 45 mm with outer sheath If re quired use angled RJ45 connectors to main tain these bending radii l 6 2 Connecting the supply voltage terminal point assignment a1 SE bi a2 s b2 Figure 2 Terminal point assignment Supply voltage input me a2 T M DC Supply of the logic voltage internally jumpered unl b2 Blue Sus Reference potential of the supply voltage internally jumpered 7 Connection example
27. or each of the four channels Filter 30 Hz bas A a aoa 17 04 Databyte7 age value Measuring range OMA 20 mA 6039 18 00 Databyte8 According to the 19 Data byte 9 module specific data sheet Data format IB IL 6040 20 00 Data byte 10 According to the 21 Data byte 11 module specific data sheet iii mali Response The result is provided in register 6230 onwards As described before register 6235 has an internal virtual length Use a Modbus function code for access to the reg isters marked with which allow access to multiple registers in one request Register 6230 functions as the start address 125 can always be used as the register number in the case of read access PHOENIX CONTACT 28 AXL F BK ETH Positive response Modbus Byte Con address 6230 6231 6232 Message code Hesponse to Write PDI object Copy of request Copy of request PDI object Copy of request index Copy of request Subindex Number of Forwrite access PDI data bytes 0 No error Perera PDI data Not available for write access to the confirma tion for this rea son 0 6233 6234 6235 6236 NO hex RN EE Ea o 00 M o hdl o o EA Negative response Modbus Byte Con address O N C O Message code Response to Write PDI object Slot Copy of request Copy of request Copy of request Copy of request Error mess
28. play mode must be deactivated The deactivation is to be saved at the same time as saving the signal active configuration and refer ence configuration Plug and play mode inactive When connector and play mode is deactivated the refer ence configuration is compared to the physical configura tion If they are the same the bus coupler is set to the RUN state on the first write access If the reference configuration and the physical configuration differ the CO LED lights up red and process data exchange is no longer possible for safety reasons In order to operate the bus despite this you have the follow ing two options 1 Restore the original configuration so that the reference configuration and the physical configuration are the same again 2 Activate connector and play mode and restart the bus coupler so that the active physical configuration is ac cepted as the reference configuration 8515 en 06 AXL F BK ETH 12 2 Startup parameterization There are Axioline F modules that can be parameterized e g measuring ranges substitute value behavior in the event of a bus error These modules can be parameterized via Startup or via the PDI channel see also Access to PDI objects The parameterization is stored retentively on the I O mod ules which is why this information only has to be written once on system startup When connector and play mode is deactivated the bus cou pler checks the parameterization of t
29. red accordingly The homepage web page of the device is accessed by entering the URL http ip ad dress Example http 172 16 113 38 The default password is private l 20 Firmware update If you cannot access the WBM pages check the connection settings in your browser and deactivate the proxy if set In order to update the firmware of the bus coupler provide the bus coupler with a firmware container via a TFTP server or load it onto the bus coupler via FTP Any FTP client or TFTP server can be used for this e g the Factory Manager If the Factory Manager is not used initialize the firmware up date via web based management When carrying out the firmware update the RDY LED flashes yellow For detailed information on firmware update via TFTP please refer to application note TFTP FIRMWARE UPDATE AXL F BK PHOENIX CONTACT GmbH amp Co KG 32823 Blomberg Germany 31 phoenixcontact com
30. rs per device 1700 Number of local bus devices entries 1701 1763 n Number of process data registers Bxxx or 9xxx 1400 1401 1649 for local bus devices 1 register per device Number of local bus devices entries I O diagnostics of local bus devices 3 registers per device Special register 2000 Timeout for process data watchdog FC3 FCA FC6 FC16 2006 FCG FC16 2075 2089 Ro Electronic rating plate FC3 FC4 6010 6089 Tunnel register for PDI requests channel 1 8 FC3 FC4 FC6 FC16 FC23 6210 6289 um Tunnel register for PDI confirmations channel 1 FC3 FC4 FC23 8 7696 R Sauegse FOFO FOA 7997 R Diagnostic status regse 7698 R Diagmosicparamelerregsteri 7090 R Diagnostic parameterregister2 1800 1801 1989 8000 8999 Ro o Input process data 9000 9999 Output process data FC3 FC4 FC6 FC16 FC23 R Read W Write In write access to the Modbus TCP clients on the Read only register the data is not trans ferred and is answered with exception code 02 8515 en O6 PHOENIX CONTACT 18 AXL F BK ETH 16 5 Figure showing process data on Modbus registers 8000 8999 9000 9999 The process data of the modules connected to the bus cou pler are mapped in one register range The registers are as signed in the same way for all function codes they are not differentiated according to the data types implicated in the function codes e g Modb
31. rtup BootP activated Three BootP requests are transmitted even in the case of a valid configuration If the device receives a BootP reply the new IP parameters are applied Otherwise the device starts with the last valid configuration DHCP activated For behavior see switch position 51 159 The station name can be selected in WBM the default station name is the MAC address with used as the separator Static BootP and DHCP deactivated The device starts with the last valid assigned IP configura tion 8 2 Manual address assignment Switch position 01 50 BootP deactivated DHCP activated The first three octets in the IP address are preset as 192 168 0 x The subnet mask is 255 255 255 0 Specify the last byte with the switch position As such you can select IP addresses between 192 168 0 1 and 192 168 0 50 Prior to transferring the IP address a test is performed to check for any potential IP address conflicts If a conflict is detected the bus coupler temporarily switches the IP ad dress to 0 0 0 0 no IP communication In this case the NET LED flashes red Eliminate the conflict and restart the bus coupler PHOENIX CONTACT 8 8 3 DHCP name assignment Switch position 51 159 This switch position is used to easily specify the DHCP host name for the device The host name is provided to the DHCP server via DHCP options This is therefore able to send a DNS update to the DNS server The DNS
32. timeout period otherwise an error is detected again e To activate the watchdog specify the desired timeout value in the range between 200 ms and 65000 ms e To deactivate the watchdog specify the value O You have the following options for changing the timeout pe riod Web based management Modbus register 2000 PHOENIX CONTACT 16 14 Monitoring of communications power U UL Monitor A monitoring function monitors the supply of communica tions power U If the value is outside the specified voltage range this is indicated in status register 7996 Undervoltage Bit 12 Set as long as the communications power is too low Bit 14 Still set after a brief undervoltage Surge voltage Bit 13 Set as long as the communications power is too high Bit 15 Still set after a brief surge voltage Very brief voltage disturbances are also registered with bits 14 and 15 Both bits remain set until the UL Monitor has been acknowledged with code 0080hex via command register 2006 15 Substitute value behavior If Ethernet communication fails or an error occurs in the local bus all outputs of the station are set to the substitute values previously parameterized on the module In order to do this plug and play mode must be deactivated and the process data watchdog must be activated For the possible substitute values of a mod ule please refer to the relevant module spe cific data sheet 8515 en 06 AXL F
33. us register and Modbus input reg ister For address assignment all IN process data of the con nected modules is mapped according to the physical bus configuration from Modbus register 8000 up to 8999 maxi mum All OUT process data is mapped according to the physical bus configuration from Modbus register 9000 up to 9999 maximum Example figure of process data on the Modbus register A number of registers is assigned to each module according to the data width Each register comprises 16 bits A module with a data width of 8 bits is mapped on one register a mod ule with 32 bits is mapped on two registers No differentiation is made between digital and analog mod ules l The current mapping of process data to the Modbus register for the I O modules connect ed to the bus coupler can be viewed via the web based management for the bus coupler under Information Modbus I O table Example of a station AXL F BK ETH AXLDI 16 4 AXL AO 8 AXL DI 32 1 AXL DO 8 2 2A AXL AI 8 AXL CNT 2 INC 2 Input process data AXL DI 16 4 8000 AXL AO 8 Output process data Byieo Byen 00 Ghannel amp 1 Channeli6 9 Si WS Wi S95 our a a E OUTa A ao Gs AXL DI 32 1 8009 Byte 0 Byte 1 Channel 8 1 Channel 16 9 9009 3010 3010 bO O 17 25 AXL DO 8 2 2A 8011 9011 AXL AI 8 eS Se 5 IN8 AXLCNT2 8020 3020 INC 2 8033 Word 13 9033 Word 13 Reserved
34. vidual labeling with B STIFT 0 8 X PEN or CMS P1 PLOTTER Marking Zack marker strip flat in 10 mm pitch unprinted 10 section for individual labeling with M PEN 0 8 X PEN or CMS P1 PLOTTER Marking Insert label Roll white Unlabeled can be labeled with THERMOMARK ROLL THERMOMARK X THERMOMARK S1 1 Mounting type snapped into marker carrier Lettering field 35 x 18 7 mm Marking Documentation Application note English Starting up the AXL F BK ETH bus coupler User manual English Axioline F System and installation User manual English Axioline F Diagnostic registers and error messages Application note English Handling an Axioline station under Startup Application note English Updating the firmware of an Axioline F bus coupler 8515 en 06 Type AXL F BK ETH Type AXL BS BK AXL CN S UL FL PLUG RJ45 GR 2 FL PLUG RJ45 GN 2 FL CAT5 HEAVY FL CAT5 FLEX FL CRIMPTOOL ZB 20 3 AXL UNPRINTED ZBF 10 5 8 AXL UNPRINTED EMT 35X18 7 R Type AH EN AXL F BK ETH UM EN AXL F SYS INST UM EN AXL F SYS DIAG UM QS EN STARTUP AH EN TFTP FIRMWARE UPDATE AXL F BK AXL F BK ETH Order No Pcs Pkt 2688459 1 Order No Pcs Pkt 2701422 5 2701421 5 2744856 1 2744571 1 2744814 1 2744830 1 2744869 1 0829579 25 0829580 50 0801831 1 Order No Pcs Pkt PHOENIX CONTACT 3 4 Technical data Dimensions nominal sizes in mm 125 9
35. view the entire table at any time This table should not be read cyclically Bits O and 1 in diagnostic status register 7997 indi cate that an error message is present This register can be read cyclically together with the process data If either of these bits is set read the registers for I O diagnostics acycli cally Modbus Device High byte Low byte register 1800 Number of valid entries number of devices ii fi 1802 Priority Channel group mod ule 1808 i967 esra 1988 Priority Channel group mod ule 1989 For details of the contents of the fields for er ror number priority channel group module and error code from PDI object 0018 please refer to the module specific documen tation data sheet user manual 8515_en_06 AXL F BK ETH 16 8 The bus coupler behavior can be controlled via the com mand register Only write access is enabled for the register In the event of invalid requests codes that are not sup ported an error message is returned eo S hex 0001 Switch on connector and play mode applied only following restart 0002 Switch off connector and play mode applied immediately 0008 Acknowledge startup parameterization applied immediately parameterization is perma nently acknowledged i e successful restart does not result in another message 0010 Set Net Fail 0020 Acknowledge Net Fail 0080 Reset UL Monitor see Monitoring of communi cations power U
36. ware ON Initialization complete e When the RDY LED lights up green release the button The default settings are restored HDY PHOENIX CONTACT 13 AXL F BK ETH 11 Service interface The service interface is located beneath the top marking field on the bus coupler I Figure 7 Service interface 1 Labeling field 2 Service interface You can connect the bus coupler to a PC on which the Startup startup diagnostic tool is running via USB using the service interface Startup offers the following functions Parameterization of the station I O modules Ocheck Diagnostics For detailed information on Startup please a refer to the UM QS EN STARTUP user man ual 8515 en O6 PHOENIX CONTACT 14 12 Startup behavior of the bus coupler 12 4 Plug and play mode Plug and play mode active The bus coupler supports connector and play mode Plug and play mode enables local bus modules connected in the field to be started up using the bus coupler without a higher level computer engineering system The connector and play mode status active or inactive is stored retentively on the bus coupler The current mode is displayed via the PP LED In connector and play mode the connected local bus mod ules are detected and their function checked If this physical configuration is ready to operate it is started however writing outputs is not enabled Toenable writing outputs connector and
37. witch position As soon as the RDY LED lights up green a new switch position can be selected on the ro H The device is ready for operation after power tary encoding switch and the device can be restarted restored via the reset button see Reset but ton Alternatively the default setting can also be 8 8 Reserved invalid switch position The device starts with the previous settings e g with the settings that were valid before the device was restarted An invalid switch position is indicated by the RDY LED red on 8515 en 06 AXL F BK ETH PHOENIX CONTACT 10 AXL F BK ETH 9 Local status and diagnostic indicators Figure 5 Local status and diagnostic indicators State Description Green Ui ogic Communications power supply present OFF Communications power supply not present NET Green Network status flashing IP configuration IP address is invalid 0 0 0 0 Yellow BootP requests or DHCP requests discover messages are being flashing transmitted Red ON Network error the process data watchdog was activated the substi tute value behavior of the outputs is performed Red flash An IP address conflict has occurred during static configuration via ro ing tary coding switches IP address assigned twice Device is not ready to operate m The active configuration of the local bus matches the saved configu ration OFF Yellow Plug and Play ON
38. xample write to PDI object The PDI write service can be conveniently used with the Modbus function code FC23 read write Alternatively you can use FC16 write and FC3 read All process data channels of the AXL F Al4 1H module should be parameterized In the physical bus configuration the module is the second module The parameterization is performed via the ParaTable object 0080 PDI channel 3 6030 6230 should be used Write request Write the following values via FC16 or FC23 to register 6030 onwards As described before register 6035 has an internal virtual length Use a Modbus function code for access to the reg isters marked with which allow access to multiple registers in one request Register 6030 functions as the start address the total length must be specified as a register number In the example the total length is 11 register 6030 to 6040 8515 en 06 AXL F BK ETH Modbus Byte Con address 6030 o 00 Command UU TIR eons 2 00 Slot 2nd local bus device O32 4 00 Subsiot No subslot 5 00 Reserved Reseved 6033 le PDI object 0080hex ParaT able parameter 1206 5034 atu siii OC Number of 12 bytes length PDI data bytes of the parameter table kal 10 00 DatabyteO Accordingtothe as Data byte 1 module specific data sheet Write PDI object Fi bam 04 Data byte 3 pu 14 00 Data byte 4 15 04 Data byte 5 F
Download Pdf Manuals
Related Search