Home

Configuration of Gateway and Proxy Devices

1. Error Code Definition Value Description CDBM_E_MINERROR 0XC004C849 Error while comparing the Value with the lower range CDBM_E_MAXERROR OXC004C84A Error while comparing the Value with the upper range CDBM_E_RANGE_ERROR 0XC004C84B Value out of Range CDBM_E_TABLE_TYPE1 0XC004C84C Table type 1 doesn t have a unique record length over all records CDBM_E_TABLE_TYPE3_ ADDREC 0XC004C84D Table type 3 doesn t allow to insert more than one Record CDBM_E_TABTYPE1 OXC004C84E It s not allowed to insert more Records than structure definitions in Table Type 1 CDBM_E TOGGLE_NOT_FOUND OXC004C84F Could not find the string for this value in the list of valid toggle strings CDBM_E_TOGGLE_VALUE_IS_ EMPTY_STRING 0XC004C850 The toggle string for this value is empty CDBM_VARIANT2BYTEARRAY_ ERROR 0XC004C851 Error during conversion of Variant to byte array CDBM_E_SET_ELEM PROP_ DEPENDENCY 0XC004C852 The Toggle Type needs also the additional string and the additional number entries in the Method CDBM_E_TABTYPE1_REC_ 0XC004C853 When reading the records of Table type 1 DOESNT_CORRESPOND_ WITH_ELEMENT elementwise the record number must correspond with the element number CDBM_TABTYPE1_NO_DATA_ 0XC004C854 When reading the records of Table type 1 FOUND_FOR_RECORD and structure definitions are present it s assumed that for each structure element a corresponding record must exist CDBM_E_TABTYPE1_WRITE_ OXC004C855 When wri
2. 0xDE80B200 DE lODReadRes negative response of a read request 80 PNIORW User Error B2 invalid slot sub slot invalid slave address invalid slot or sub slot 0OxDF80B200 Invalid slave address for a write request OxDE80AABB DE l ODReadRes negative response of a read request 80 PNIORW User Error AA user spezific BB user spezific All errors except addressing errors detected in the proxy device PROFIBUS Master or PROFIBUS Slave 0xDF80AABB DF lODReadRes negative response of a write request 80 PNIORW User Error AA user spezific BB user spezific All errors except addressing errors detected in the proxy device PROFIBUS Master or PROFIBUS Slave Table 79 PROFINET IO PROFIBUS DP Error Codes 7 3 Alarms Controlled by the PROFIBUS DP Slave PIRIOLFI 1i ed PROFIBUS Alarm BUTS Proxy Device Device Master Controller Figure 108 PROFINET IO PROFIBUS DP Alarm Errors PROFIBUS alarms are mapped to PROFINET alarms as follows Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Acyclic Proxy Communication 239 268 PROFIBUS PROFINET IO Process alarm Process alarm Diagnosstic alarm Diagnosstic alarm Status alarm Diagnosstic alarm with the structure of the PROFIBUS alarm Update alarm Diagnosstic alarm
3. 8 6 2 CIFX API Transport Header State Error Codes Error Code Definition Value Description CIFX_TRANSPORT_ERROR_UNKNOWN 0x800E0001 Unknown error code in transport header CIFX_TRANSPORT_CHECKSUM_ERROR 0x800E0002 CRC16 checksum failed CIFX_TRANSPORT_LENGTH_INCOMPLETE 0x800E0003 Transaction with inclomplete length detected CIFX_TRANSPORT_DATA_TYPE_UNKOWN 0x800E0004 Device does not support requested data type CIFX_TRANSPORT_DEVICE_UNKNOWN 0x800E0005 Device not availableunknown CIFX_TRANSPORT_CHANNEL_UNKNOWN 0x800E0006 Channel not availableunknown CIFX_TRANSPORT_SEQUENCE 0x800E0007 Sequence error detected CIFX_TRANSPORT_BUFFEROVERFLOW 0x800E0008 Buffer overflow detected CIFX_TRANSPORT_RESOURCE 0x800E0009 Device signals out of resources CIFX_TRANSPORT_KEEPALIVE Ox800E000A e connection monitoring error Keep alive CIFX_TRANSPORT_DATA_TOO_SHORT 0x800E000B Received transaction data too short Table 93 CIFX API Transport Header State Error Codes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010106EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Error Codes 8 7 ODM Error Codes DBM V4 254 268 ODM Error Codes DBM V4 Error Code Definition Value Description CDBM_E_MD5_INVALID 0XC004C810 Checksum invalid CDBM_E_INTERNALERROR 0XC004C811 Internal Error CDBM_
4. A communication system for industrial Ethernet designed and developed by Bosch Rexroth and supported by sercos International Slave devices are peripheral devices like for example I O devices or drives Slave devices are also called passive participants They do not receive the bus access authorization That means they may only accept received messages from the Master or send a message to the Master after enquiry of the Master A network component connecting multiple communication partners or even entire branches of a network with each other A switch is an intelligent network component which analyzes network traffic in order to decide on its own For the connected communication partners a switch behaves transparently Sychronisation cycle of the master Transport Control Protocol Internet Protocol connection orientated secure transfer protocol as basis for the Internet protocols Versatile Automation Random Access Network A communication system for industrial Ethernet based on the DIAS BUS developed by Sigmatek The system is supported by the VARAN BUS NUTZERORGANISATION VNO A watchdog timer provides an internal supervision mechanism of a communication system It supervises that an important event happens within a given timeframe the watchdog time which can be adjusted accordingly for instance by a parameter in the _Warmstart message and causes an alarm otherwise usually this is accomplished by changing the operational st
5. In the Memory Card management pane you can e backup the firmware and the configuration from the netTAP device to an MMC memory card e restore the firmware and the configuration from the MMC memory card into the netTAP device On the pane MMC Management you can backup and restore the firmware and the configuration to respectively from an MMC card The Folder on the pane shows the directory structure of the file system of the netTAP device named SYSVOLUME and if an MMC card is inserted also the directory structure of the MMC card named SDMMC Backup To backup the firmware and configuration files insert a formatted Format FAT MMC card into the MMC slot of the netTAP NT 100 device When the directory named SDMMC is shown then click on the button Backup to copy the firmware and configuration files from the netTAP NT 100 device to the MMC card Restore To load the firmware and configuration files from an MMC card into the netTAP NT 100 device insert an MMC card into the MMC slot of the netTAP NT 100 device which contains the firmware and configuration files When the directory named SDMMC is shown then click the button Restore to copy the firmware and configuration files from the MMC card into the netTAP NT 100 device Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 123 268 4 6 Configuration EtherCA
6. gt Enter at the EtherNet IP Scanner for this instance ID 100 the number of data number of send data bytes which were configured in the netTAP or netBRICK device e g 32 gt f adjustable at the EtherNet IP Scanner set that the EtherNet IP Scanner receives the 32 Bit Run Idle header gt You can set at the EtherNet IP Scanner if the Scanner verifies identification numbers of the EtherNet IP Adapter named keying This verification can be activated or deactivated at the EtherNet IP Scanner If the verification is used then use or check for the following values for the NT 100 device vendor 283 0x011B product code 275 0x0113 for NT 50 or product code 271 0x010F for NT 100 product code 273 0x0111 for NB 100 product type 12 Ox000C major revision 1 minor revision 1 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 133 268 4 10 Configuration Open Modbus TCP The netTAP NT 50 and NT 100 device respectively the netBRICK NB 100 device as Open Modbus TCP needs parameter The device can either work as a Client or as a Server These parameter can be edited as follows 1 gt Open the configuration dialog Select from the context menu of the netTAP respectively the netBRICK symbol the entry Configuration gt Open Modbus TCP The Open Modbus TCP settings dialog opens In
7. 240 characters Controller for this device Must be DNS compatible name Default NT 50 EN PNS Gateway nt50enpns NT 100 RE PNS Gateway nt100repns NT 100_RE PNS Proxy nt100reproxy NB 100 RE PNS Gateway nb100repns Type of station Type name of the PROFINET station name can be assigned Character string freely 1 240 characters Default Default Station Type Output data bytes Maximum allowed length of the input data in Byte This 0 1024 Byte parameter should be equal to or higher than the complete Default 128 Byte projected input data length otherwise the IO Device will reject the cyclic communication requests Input data bytes Maximum allowed length of the output data in Byte This 0 1024 Byte parameter should be equal to or higher than the complete Default 128 Byte projected output data length otherwise the IO Device will reject the cyclic communication requests Table 31 PROFINET IO Device Parameters Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 156 268 4 13 2 Settings at the used PROFINET IO Controller Gateway Device Description File To configure the Master a GSDML file device description file is required The GSDML file is on the delivered DVD in the directory EDS PROFINET NT 50 XX EN or NT 50 EN XX GSDML V2 1 HILSCHER NT 50 EN PNS 20100219 xml
8. 4 20 Configuration DeviceNet Slave The netTAP NT 50 and NT 100 device respectively the netBRICK NB 100 device as DeviceNet Slave needs parameter These parameter can be edited as follows 1 Open the configuration dialog gt Select from the context menu of the netTAP respectively the netBRICK symbol the entry Configuration gt DeviceNet Slave The DeviceNet Slave configuration dialog opens 3 In the navigation area the entry Configuration under the folder Configuration is selected and the configuration dialog is displayed 2 Set MAC ID Enter in the field MAC ID the address which the netTAP or netBRICK device uses on the DeviceNet network to be addressed by the DeviceNet Master 3 Set baudrate Set the baudrate for the netTAP or netBRICK device which is used in the DeviceNet network 4 Set produced data length and consumed data length Set in the field Prod Data Length the number of data bytes the netTAP or netBRICK device should send to the DeviceNet Master gt Set in the field Cons Data Length the number of data bytes the netTAP or netBRICK device should receive from to the DeviceNet Master Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 180 268 5 Set more parameter If necessary set more parameter The parameter are described in the following section DeviceNet Slave Param
9. Devicenumber _ Serialnumber xml with a summary info of the order information e the Order Address e the License Information e the License Type e the Device Data e the ordered Licenses gt Send the order e mail License request gt The order process is complete Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 4 3 7 2 gt Click Print Fax Form or Telephone Ordering the License by Fax or by Telephone You can place your order by Fax or by Telephone Print Fax Form 6 Figure 85 License Pane placing the order by Fax or by Telephone 111 268 Telephone 7 The summary of the ordering data PrintOrderRequest_ Devicenum ber _ Serialnumber html is opened in a browser window Note If your browser does not display the order data or the window Move Element or Copy Element are displayed check the safety settings of your system netX License Order Form Doe Example LTD 2000th Rd NY 11417 U S fax 11223344 100 Licensee Information First Name Surname e Mail Telephone Fax Customer No Company Address Country City Zip Order Number Tax Ident Number License Type User Single Device License Device Information Manufacturer Device Number Serial Number Chip Type Step Romcode Revi
10. Figure 27 Gateway Device with Slave Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 45 268 2 3 5 3 Configure the PROFIBUS DP Slave device gt Open the configuration window with a double click on the device icon of the PROFIBUS DP Slave 3 gt The configuration window of the PROFIBUS DP Slave device opens gt Select in the navigation area Configuration gt Modules gt Select from Available Modules the module s and add it them to the Configured Modules to configure the Slave The Configured Modules has to match the configuration of the used PROFIBUS DP slave device More information about the configuration of PROFIBUS DP Slave devices are in the document PROFIBUS Generic_Slave DTM_en pdf on the product DVD in section Configuration 2 3 5 4 Configure PROFIBUS DP Master 1 Open the PROFIBUS DP Master Port X3 configuration window gt Select from the context menu of the gateway device symbol the entry Configuration gt PROFIBUS DP Master gt The PROFIBUS DP Master configuration window opens Y netDevice PROFIBUS DP Master netTAP NT 100 RE DP PROXY lt gt 1 IO Device NT 100 XX XX Device ID Ox0B44 an Vendor Hilscher GmbH Vendor ID 0x011E Navigation Area G 4 Configuration gt Bus Parameters Profile PROFIBUS DP v Process Data Ad
11. Net mask This function is not supported by gateway or proxy devices Mode of data exchange Client Message Mode or IO Server For the Client mode in the navigation area Command Table is displayed For the Open Modbus TCP Client the Command Table is a list with commands for the reading or writing of data For the IO Server mode the communication partner has read write access to the process data memory of the device from outside using of the function codes Data storage mode No Data will not be swapped Yes Data will be swapped If unchecked data are read from the intput area using FC1 FC3 and FC23 If checked data are read from the output area using FC1 FC3 and FC23 FC1 then can be used instead of FC2 and FC3 instead of FC4 Number of sockets to provide for server requests A value of 0 means that the Open Modbus TCP task exclusively works as TCP Client A value of 16 means that the Open Modbus TCP task exclusively works as Server in the Message Mode With the default value 4 there are 4 Server connections provided Then still up to 12 TCP client connections are available The parameters Send Acknowledgement Timeout Send Timeout Connect Acknowledgement Timeout Connect Timeout and Close Acknowledgement Timeout Close Timeout are for the Timeout between the Open Modbus TCP Task and the TCP Task Only for client jobs in Message Mode packet mode The connection to the destination devi
12. 2 4 11 Device Description File to configure the PROFINET IO Controller 71 2 5 Configuration of a NL 51N DPL as Proxy ccecceeeceeeeeeeeeneeeeeeeeneeeeeeeeaeeeeeeeeaaeeeeneaas 72 2 5 1 Requirement for the Configuration cccccccceeeeeseeeeeeeeeeeaeeeeeeeseeeeeseaeeeeaeeteneeees 72 2 5 2 Start SYCON net and User LOQiIN c ccceccceceeeeeeneeeeeeeeceaeeeeeaeeeeeeeesaeeesaeenenees 72 2 5 3 Insert the Proxy Device into the Configuration Window ccccceseeeeereeees 73 2 5 4 Configuration of the secondary Network cccesceceeeeceeeeeeeeeeeeeeeeseaeeesaeeeenes 74 2 5 5 Configuration of the secondary Network ccsccesececeeeeeseaeeeeeeeeseeeeseaeeeenees 77 2 5 6 Establish a Connection to the netLINK NL 51N DPL 00 eeeceeeeeeeteeeeneeees 79 2 5 7 Device ASSIGNMENT EEEO KAFEAREN EOE iol EEEE TKE 82 2 5 8 Load Configuration i irrniieiitrr aiani nna ai ia aaae aai E A AE aaaea 83 2 5 9 SAVE RrojeGt mea ton alee cesta a e a Gh ponent a nace a 83 2 5 10 Device Description File to configure the PROFINET IO Controller 84 2 5 11 Update Firmware ss devcciteeniit eee tacit vn tat E ides eben le 85 Oe MSETAT ING ode acd doce ates a ee bac aet ated cased ate a ere EEEa 86 3 1 Overview SCTINGS ieren tee e eaa asia aaaea eee Setanta 86 3 2 DIANA x teresa E E eee 87 3 2 1 Selecting the Driver ccccecccecceeeeesseceeeeeceeeeeeaaeseeneeceeeeesaaeseeaeeseee
13. 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 31 268 2 2 8 Establish a Connection to the netTAP NT 50 1 Connect an Ethernet cable to the NT 50 gt Build up an Ethernet connection between the Ethernet port of the NT 50 device and to the Ethernet port of the configuration PC 2 Set the IP address of the NT 50 device Set with the Ethernet Device setup software which is part of the SYCON net installation the IP address for the NT 50 With this software it is also possible to read an already assigned IP address from the NT 50 device The IP address is required for the communication with the SYCON net software an IP address has to be assigned before to the NT 50 device How to assign an IP address is described in the document Ethernet Device Configuration Ol xx DE pdf AD To communication from the SYCON net software with the NT 50 device 3 Open the gateway configuration window Select from the context menu of the gateway device symbol Configuration gt Gateway 3 gt The gateway configuration window opens 4 Select driver Select in the navigation area Settings gt Driver and then check netX Driver 3 gt The following figure shows the selected driver ZnetDevice Gateway net TAP NT 50 XX XX lt gt 1 10 Device NT SO Xx Device ID vendor Hilscher GmbH vendor ID 0x011E Navigation area 2 Settings BS iver Driver Yersion 1D n
14. 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 35 268 2 2 10 Load Firmware The firmware has to be loaded into the netTAP only for first commissioning only Therefore do the following steps 1 Open the Gateway configuration window gt Select from the context menu of the gateway device symbol the entry Configuration gt Gateway gt The Gateway configuration window opens 2 Open the Settings window gt Select Configuration gt Settings The window Settings opens J netDevice Gateway netTAP NT 50 XX XX lt gt 1 10 Device NT 50 DP RS Device ID Vendor Hilscher GmbH Vendor ID Ox011E Navigation area A a Settings General 9 Driver netx Driver Description netTAP Device Assignment lt Q Configuration tay Settings Signal Mapping Primary network Port X2 Zi Secondary network Port x3 Required gateway Protocol Combinations Required license None Available Firmware NSDPSMBR NXF ti Browse Download Software class Gateway Software version 1 0 2 0 Basic Settings Mapping Cycle time 10 ms Mapping mode Save operation succeeded Figure 19 Firmware Download 3 Select Firmware gt Mark at Available Firmware the firmware file N5DPSMBR NXF Firmware for PROFIBUS DP Slave to Modbus RTU 4 Load firmware into the device gt Click on Download The firmware is loaded into the netTAP device Important
15. IP Range Configuration Disable IP Range IP Address Use IP Range TCP Port Address Count G 168 60 199 Q 50111 fi Send Timeout 1000 H ms Keep Alive Timeout 2000 ms Reset Timeout 20000 H ms Figure 60 Set IP Address Search Range 2 gt You can enter one IP address of the proxy device at as shown above or you can set an IP address range by a check at Use IP Range and set the IP end address at Make sure that the proxy device can be reached via Ethernet and is reachable via the address range E Note Set the IP address range not to large which results in a long scan time gt After the address range was set click on Save Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 82 268 2 5 7 Device Assignment gt Select Settings gt Device Assignment gt Click on Scan The search process is started Devices found are display in a list then T netDevice Proxy netLINK NL 51N DPL lt gt 1 DER 10 Device NL SIN DPL i Vendor Hilscher GmbH m Scan progress 3 3 Devices Current device Device selection suitable only v n Device Hardware Ports oft Slot nu Serialnu Driver Channel Protocol Access path NL SIN DPL Ethernet PROFIBUS nja 192 168 60 Access path 854C8CC7 F333 413
16. 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 59 268 2 Open dialog for protocol selection gt Select in the Navigation area Configuration gt Settings The configuration window Settings opens ba netDevice Proxy netTAP NT 100 RE XX PROXY lt gt 1 10 Device Vendor Navigation area t 3 Settings 3 Driver netX Driver Device Assignment NT 100 RE XX PROXY Hilscher GmbH General Description Protocol Combinations Device ID vendor ID 0x011E netTAP Configuration g oettings Memory Card Management Licensing Primary network Port x2 Secondary network Port X3 Required gateway Required license Available Firmware Browse NTPNSDNS NXF Software class Software version Basic Settings Mapping Cycle time Mapping mode Cancel f Help Figure 40 Proxy Protocol Selection 1 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 60 268 3 Select the protocol for the primary network and for the secondary network and apply gt Inthe window Configuration gt Settings at Protocol Combinations for the Primary Network Port X2 the protocol PROFINET IO Device is already preselected gt Select then at Protocol Combinations for the Secondary Network Port X3
17. CC Link Slave Parameters Part 1 CC Link Slave Parameters Part 2 CSP File Names for netTAP DeviceNet Slave Parameters Part 1 DeviceNet Slave Parameters Part 2 EDS File Names for netTAP and netBRICK Parameters PROFIBUS DP Slave Part 1 Parameters PROFIBUS DP Slave Part 2 GSD File Names for netTAP and netBRICK Modbus RTU Parameters Parameter of the Command Table Parameter of the Command Table Access from the Modbus RTU Master using Modicon based Addressing 1 Access from the Modbus RTU Master using Modicon based Addressing 2 Access from the Modbus RTU Master using Zero based Addressing 1 Access from the Modbus RTU Master using Zero based Addressing 2 Access from the Modbus RTU Master using One based Addressing 1 Access from the Modbus RTU Master using One based Addressing 2 tion of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC081201006EN Revision 6 English 2014 04 Released Public 261 268 170 171 172 175 176 177 181 182 183 187 188 189 193 195 197 202 202 203 203 204 204 Hilscher 2009 2014 Appendix Table 56 Table 57 Table 58 Table 59 Table 60 Table 61 Table 62 Table 63 Table 64 Table 65 Table 66 Table 67 Table 68 Table 69 Table 70 Table 71 Table 72 Table 73 Table 74 Table 75 Table 76 Table 77 Table 78 Table 79 Table 80 Table 81 Table 82 Table 83 Table 84 Table 85 Table 86 Table 87 Table 88
18. CIFX Device Driver 1 0 3 2 368BECSB 0E92 4COE B449 64F624E744F4 nets Driver 0 9 1 2 787CD349 4CF6 4259 8E4D 109B646BE491 Figure 67 Driver Selection List Driver s selected Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Settings 88 268 3 2 2 Configuring the Driver All drivers for which you can access to an individual driver dialog pane are displayed in the navigation area under the Driver entry In the driver dialog panes you can configure the driver settings Navigation Area amp tex Settings tmp Driver nets Driver Figure 68 Navigation Area Settings To configure a driver 1 Select Settings gt Driver gt Name of the driver The corresponding driver dialog pane is displayed 2 Configure the driver settings gt To get detailed information how to configure the single drivers please refer to the corresponding description of the driver aA You can access to the single descriptions of the drivers as online help via the DTM user interface F1 key To access to the online help with the descriptions of the drivers gt Select Settings gt Driver gt Name of the driver gt Press the F1 key Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Settings 89 268 3 2
19. Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 25 268 4 Enable address switch gt Check Enable to enable that the PROFIBUS station address is set by the rotary switch at the device If Enable is uncheked the the PROFIBUS station address is set by the configuration software ZnetDevice Gateway netTAP NT 50 XX XX lt gt 1 K 10 Device NT 50 XX xXx Device ID Vendor Hilscher GmbH vendor ID OxO11E Navigation area im E Settings General E Driver netX Driver Description netTAP Device Assignment E Configuration om cerns Primary network Port X2 PROFIBUS DP Slave v Secondary network Port x3 Modbus RTU ha Signal Mapping Required gateway NT 50 DP RS Ld Required license None Available Firmware NSDPSMBR NXF Browse Protocol Combinations Software class Multi protocol combinable Gateway Software version ih Basic Settings Mapping Cycle time 10 ms Mapping mode M Network Address Switch Enable v Used by PROFIBUS DP Slave z Cancel Apply Help Figure 10 Gateway Protocol Selection 3 5 Close the Gateway configuration window gt Click OK 3 gt The Gateway configuration window closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released
20. NT 100 RE XX GSDML V2 1 HILSCHER NT 100 RE PNS 20090123 xml NB 100 RE XX GSDML V2 1 HILSCHER NB 100 RE PNS 20091 112 xml Table 32 GSDML File Names for netTAP and netBRICK Configuration Note The settings in the used Controller must comply with the settings in the Device to establish a communication Important parameters are Name of Station Vendor ID Device ID Input and Output data length In order that the PROFINET IO Controller can communicate with the netTAP or netBRICK device as PROFINET IO Device Note Under Name of Station in the PROFINET IO Controller the name must be used which was configured in the netTAP or netBRICK device gt Enter at the PROFINET IO Controller the Name of Station which is configured in the NT 100 device Use for the configuration of the PROFINET IO Controller modules e g 32 Bytes In for receiving data from the netTAP or netBRICK device Several modules can also be used e g 2 times the module 16 Bytes In The number of data counted in bytes that results from the used modules for input data has to match with the number of input data configured in the netTAP or netBRICK device v Vv Use for the configuration of the PROFINET IO Controller modules e g 64 Bytes Out for sending data to the netTAP or netBRICK device Several modules can also be used e g 4 times the module 16 Bytes Out The number of data counted in bytes that results from the used m
21. Part 1 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010Ol06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 207 268 Conflict Priority A conflict occurs when both devices start a data transfer at the High Default same time The conflict priority specifies the behavior for this Low case One device must have high priority the other device must have low priority The device with high priority can continue with the data transfer while the device with low priority must wait with the data transfer Retry Limit When transmission errors occur then the retry limit specifies the 0 65535 maximum number of retries to do a data transfer successfully Default 6 After the maximum number of retries has been reached the data transfer is aborted with error Character Delay Time The value specifies the time in ms within the remote device must 4 65535 ms have sent the next character of a telegram If the time is Default 220 ms exceeded then an error is reported to the superordinated control unit Acknowledge Timeout The value specifies the time in ms the remote device must have 256 65535 ms sent an acknowledge If the time is exceeded then an error is Default 550 ms reported to the superordinated control unit Max Input Maximum telegram length for receive data 0 5736 Received data are stored in the input data area 1024 Default M
22. Port X2 and the click the button Map Signals Or Map the signal using drag and drop For this drag the signal received Port X3 receive and drop it on the signal to be sent Port X2 send 5 Signal Mapping Transfer status info of Port X2 to Port X3 If necessary map the status information of Port X2 Port X2 generated which are generated device internal to signals which should be sent on Port X3 Port X3 send gt For this mark the status signal Port X2 and the signal which should be sent Port X3 and click the button Map Signals Or Map the signal using drag and drop For this drag the status signal Port X2 generated and drop it on the signal to be sent Port X3 send Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 49 268 6 Signal Mapping Transfer status info of Port X3 to Port X2 gt f necessary map the status information of Port X3 Port X3 generated which are generated device internal to signals which should be sent on Port X2 Port X2 send gt For this mark the status signal Port X3 and the signal which should be sent Port X2 and click the button Map Signals Or Map the signal using drag and drop For this drag the status signal Port X3 generated and drop it on the signal to be sent Port X2 send An example of the Signal Mapping window sh
23. Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 2 2 5 1 Configuration of the secondary Network 26 268 Configure the protocol at the secondary network Port X3 gt Select from the context menu of the NT 50 XX XX symbol the entry Configuration gt Modbus RTU 3 The Modbus RTU configuration window opens J netDevice Modbus RTU netTAP NT 50 DP RS lt 2 gt 1 IO Device vendor NT 50 DP RS Hilscher GmbH Navigation area 6 J Configuration p Configuration Signal Configuration Interface Bus Startup Watchdog Time Address Mapping Data Swapping Map FC1 and FC3 Ident Device Bus Protocol Mode Modbus Address Interface type 10 Slave RS 232 Device ID vendor ID N Enable Response Timeout Send Retries Frame Format Sek RTS Control RTS Control Off Baud Rate 9600 Stop Bits 1 Parity Data Number of Register Figure 11 Protocol Configuration Vv Configuration of Gateway and Pr Set protocol parameter Number of Coils es Default Set the parameters To configure the device as a Modbus RTU Slave set for Protocol Mode the value IO Slave Set the following important parameter Modbus Address Interface type RTS Control Baud Rate Stop Bits and Parity These parameter are important that the used Modbus RTU Master can communicate with the gateway device More
24. Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 215 268 ASCII Character Table ASCII ASCII Charac ASCII ASCII Charac ASCII ASCII Charac ASCII ASCII Cha Hex Dez ter Hex Dez ter Hex Dez ter Hex Dez racter 00 0 NUL 20 32 SP 40 64 60 96 01 1 SOH A 21 33 41 65 A 61 97 a 02 2 STX B 22 34 42 66 B 62 98 b 03 3 ETX C 23 35 43 67 C 63 99 c 04 4 EOT D 24 36 44 68 D 64 100 d 05 5 ENQ E 25 37 45 69 E 65 101 e 06 6 ACK F 26 38 amp 46 70 F 66 102 f 07 7 BEL G 27 39 47 71 G 67 103 g 08 8 BS H 28 40 48 72 H 68 104 h 09 9 TAB 29 41 49 73 l 69 105 i 0A 10 LF J 2A 42 4A 74 J 6A 106 j 0B 11 VT K 2B 43 4B 75 K 6B 107 k oc 12 FF L 2C 44 l 4C 76 L 6C 108 oD 13 CR M 2D 45 7 4D 77 M 6D 109 m 0E 14 SO N 2E 46 4E 78 N 6E 110 n OF 15 SI O 2F 47 4F 79 O 6F 111 o 10 16 DLE P 30 48 0 50 80 P 70 112 p 11 17 DC1 Q 31 49 1 51 81 Q 71 113 q 12 18 DC2 R 32 50 2 52 82 R 72 114 r 13 19 DC3 S 33 51 3 53 83 S 73 115 s 14 20 DC4 T 34 52 4 54 84 T 74 116 t 15 21 NAK U 35 53 5 55 85 U 75 117 u 16 22 SYN V 36 54 6 56 86 V 76 118 v 17 23 ETB W 37 55 7 57 87 Ww 77 119 w 18 24 CAN X 38 56 8 58 88 X 78 120 x 19 25 EM Y 39 57 9 59 89 Y 79 121 y 1A 26 SUB Z 3A 58 5A 90 Z 7A 122 z 1B 27 Esc 3B 59 5B 91 7B 123 1C 28 FS 3C 60 lt 5C 92 7
25. Two General Master Licenses PROFIBUS Master CANopen Master DeviceNet Master AS Interface Master PRAFINET IN RT Cantrallar Request Form please fill out User Single Device License 00001 1251100 20007 0x00000001 0x00000000 0x00000000 sa License ae we Figure 75 License Pane gt Note To display further entries under License Type move the scroll box downwards or upwards To display further entries under Request Form please fill out move the scroll box downwards or upwards 1 The title bar contains the notation of the device description Symbolic Name Device Description lt Station Address gt Network ID Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010I106EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 104 268 4 3 3 Which Licenses are present in the Device Check which licenses are present in the device How to proceed gt Open the License pane as described under section Open License Dialog on page 102 License Type _ Master protocols gt 4 Utilities Figure 76 License Pane License Type gt Under License Type click at Master protocols gt The Master protocols overview opens License Type sting Order HE Master protocols i One General Master License NO oO I Two General Master Licenses NO Oo 7 PROFIBUS Master YES Oo i CANopen Maste
26. the protocol PROFIBUS DP Master The proxy configuration window shows the following 3 Proxy netTAP NT 100 RE DP PROXY lt gt 1 10 Device NT 100 RE DP PROXY Device ID ao vendor Hilscher GmbH vendor ID 0x011E Navigation area Settings General I Driver TCPIP Driver for netX Description netTAP tX Dri rok Has abel Protocol Combinations Device Assignment oan Primary network Port X2 Grane Deer network Port X3 Ce D Licensing Required gateway Memory Card Management Required license Yes 1 Available Firmware NTPNSDPM NXF Browse Software class Software version Basic Settings Mapping Cycle time 1 ms Mapping mode Figure 41 Proxy Protocol Selection 2 The Mapping Mode is preselected with Default only selection and works as follows PROFIUS DP Slave devices which are inserted at the bus line are represented by a slot number on PROFINET The PROFINET slot number is equal to the PROFIBUS station address The PROFIBUS modules are represented by a PROFINET sub slot number 4 Close the proxy configuration window gt Click on OK The proxy configuration window closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 61 268 2 4 4 Configuration of the secondary Network If the slave device is not lis
27. 2009 2014 Configuration Sequence for Gateway and Proxy 53 268 2 3 9 Load Firmware The firmware has to be loaded into the netTAP only for first commissioning only Therefore do the following steps 1 Open the Gateway configuration window gt Select from the context menu of the gateway device symbol the entry Configuration gt Gateway gt The Gateway configuration window opens 2 Open the Settings window gt Select Configuration gt Settings The window Settings opens J netDevice Gateway netTAP NT 100 XX XX gt 1 BAE z 10 Device NT 100 RE DP Device ID 2 30 Vendor Hilscher GmbH vendor ID OxO11E Navigation area E Settings General a Driver netX Driver Description netTAP Device Assignment E Configuration ey Settings Protocol Combinations Primary network Port X2 z Secondary network Port X3 Signal Mapping Memory Card Management Required gateway Licensing Required license Yes 1 Available Firmware NTPNSDPM NXF Browse Download Software class Gateway Software version 1 3 3 0 Basic Settings Mapping Cycle time 1 ms Mapping mode Save operation succeeded Figure 35 Firmware Download 3 Select Firmware gt Mark at Available Firmware the firmware file NTPNSDPM NXF Firmware for PROFINET IO Device to PROFIBUS DP Master 4 Load firmware into the device gt Click on Download The firmware is loaded into the netTAP
28. 3 netX Driver The netX Driver is used to connect the DTM to the device via different connection types The DTM communicates with the device via an USB connection a serial RS232 connection or a TCP IP connection The netX Driver establishes e via the USB interface of the device and the USB port of the PC an USB connection to the device e via the RS232 interface of the device and the COM port of the PC a serial connection RS232 to the device e and via Ethernet a TCP IP connection to the device To connect the DTM to the physical layer of the device the netX Driver software works in combination with the software components e USB COM connector for the USB connection and for the serial connection RS232 and e TCP IP connector for the Ethernet connection 3 2 3 1 netX Driver USB RS232 Connection Function and use The communication from the DTM to the device via an USB RS232 Connection is used when the DTM is installed on a PC and between the PC and the device e anUSB connection e ora serial connection RS232 exists The DTM accesses to the device via the USB interface or via the RS232 interface of the device This requires either to connect an USB port of the PC to the USB interface of the device using an USB cable or to connect a physical COM port of the PC to the RS232 interface of the device via a serial cable The netX Driver USB RS232 Connection supports all physical and virtual COM ports available
29. ASCII needs parameter These parameter can be edited as follows 1 gt Open the configuration dialog Select from the context menu of the netTAP respectively the netBRICK symbol the entry Configuration gt ASCII The ASCII settings dialog opens In the navigation area the entry Settings under the folder Configuration is selected and the settings dialog is displayed ASCII settings Select in the dialog window the interface type RTS control baudrate number of data bits number of stop bits and parity The settings are described in the following section ASCII Settings on page 211 Open ASCII parameter dialog Select in the navigation area under Configuration the entry ASCII Parameter The dialog ASCII Parameter is displayed Set parameter Select the operating mode set the telegram structure set the timing and the size of the send and receive buffer The parameter are described in section ASCII Parameters on page 211 Signal configuration The signal configuration is done with default value automatically by SYCON net software Close configuration dialog Click on OK to save the parameter or click on Cancel if the parameter should not be saved The configuration dialog closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 211 268 4 25 1 ASCII Settings Interface type
30. DPS Device CB_AB32 DPS Activate Hilscher GmbH _ More information about the configuration of PROFIBUS DP Master devices are in the document PROFIBUS_Master_netX_DTM_en pdf in section Configuration 3 Close the configuration window gt Click on the button OK 3 gt The configuration window closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 47 268 2 3 6 Configure the Gateway Signal Mapping 1 Open the Gateway configuration window Select from the context menu of the gateway device symbol the entry Configuration gt Gateway The Gateway configuration window opens Open the Signal Mapping window Select Configuration gt Signal Mapping oN Q The window Signal Mapping opens i Gateway netTAP NT 100 RE DP lt gt 1 IO Device NT 100 RE DP Device ID ao Vendor Hilscher GmbH Vendor ID OxO11E Navigation area 4 E Settings Available Signals Driver TCP IP Driver For netX netX Driver 128 Bytes In lt Slot 1 gt CB_AB32 DPS lt Addr 2 gt 7 Device Assignment J 128 Bytes Out lt Slot 2 gt 88 CB_AB32 DPS lt Addr 3 gt 4 Configuration Settings Port x2 Signals 4 Data type Port x3 Signals _ Data type Licensing gt EEE Memory Card Management j 4 Send Output_0001 BYTE Send 128 InBytes BYTE_0000 Sen
31. DTM The current activity e g download is signaled graphically via icons in the status bar ke Disconnected J Data Set 1 2 3456 Figure 3 Status Bar Status Fields 1 to 6 Status Icon Meaning Field 1 DTM Connection States G Connected Icon closed Device is online lt J Disconnected Icon opened Device is offline 2 Data Source States T Data set The displayed data are read out from the instance data set database Li Device The displayed data are read out from the device 3 States of the instance Date Set Valid Modified Parameter is changed not equal to data source 4 Changes directly made on the Device Eer Load configure diagnosis parameters Diagnosis is activated 6 Device Diagnosis Status 7 Save operation succeeded The save operation has been successful Further messages due to successful handling of device data D Firmware Download Firmware Download is running A Save operation failed The save operation has failed Further fail operation messages due to incorrect communication due to malfunction in the field device or its peripherals Table 6 Status Bar Icons 1 ko Disconnected J Data Set Offline State Save operation succeeded Firmware Download Firmware Download successful Online State and Diagnosis JE Disconnected T Data Set K4 Save operation succeeded J Disconnected 0 Data Set D Firmware Download lt Disconnected J
32. Data Set lt Connected Device Figure 4 Status Bar Display Examples Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 19 268 2 Configuration Sequence for Gateway and Proxy 2 1 Gateway and Proxy Device Two networks are connected via a gateway or a proxy device together For the data transfer from one network into the other it is necessary that these data are mapped This mapping is done within SYCON net Gateway Devices The mapping of the data can be done by the user und be configured within SYCON net The following gateway devices are in the device catalog e netTAP NT 50 NT SO XX xx e netTAPNT100 M NT 100 xx xx e netBRICKNB100 NB 100 xX Xx Proxy Devices The mapping of data is already specified and done automatically by SYCON net The following proxy devices are in the device catalog e netTAP NT 100 WA NT 100 RE Xx PROXY e netLINK Proxy 2 NL SIN DPL Note The gateway or proxy device can only be used at the gray main line Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 20 268 2 2 Configuration of a NT 50 as a Gateway This section is valid for netTAP NT 50 devices as a gate
33. Do not remove the cable during the firmware download Do not disconnect the power supply of the device during the firmware download Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 36 268 5 Download of firmware gt Wait until the firmware was transferred completely into the device 6 Close the Gateway configuration window after the download gt Click OK The Gateway configuration window closes 2 2 11 Load Configuration 1 Download configuration gt Select from the context menu of the gateway device symbol the entry Download gt Answer the security question with Yes if the download should start SYCON net builds up an online connection to the device This the indicated by a green highlighted device name 3 gt The configuration is transferred info the gateway device The device performs a reset and then starts with the new configuration Note The device performs a reset after the download Because of that the Ethernet connection gets lost and has to be stopped from SYCON net and then has to be established again Stop the online connection to the device which was established automatically to the device before 2 Disconnect gt Select from the context menu of the proxy device symbol the entry Disconnect gt Note To establish a co
34. IP address Deselect the flag DHCP and BootP Select IP address Enable and enter a valid IP address for the netTAP or netBRICK device Select netmask enable and enter a valid netmask If needed Select the gateway enable and enter a valid IP address for the gateway Set length produced and consumed data length Enter in the field produced data length the number of data bytes the EtherNet IP Scanner should receive from the netTAP or netBRICK device e g 64 bytes Enter in the field consumed data length the number of data bytes the EtherNet IP Scanner should send to the netTAP or netBRICK device e g 32 bytes Set more parameter If necessary set more parameter The parameter are described in the following section EtherNet IP Adapter Parameter on page 130 Note Default values can be used normally for the other parameters Depending on additionally requirements and the design of the EtherNet IP network as well as the used devices parameters needs to be adjusted if necessary Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 129 268 5 Open the signal configuration dialog gt Select in the navigation area under the folder Configuration the entry Signal Configuration 3 gt The signal configuration dialog opens 6 Signal configuration gt Ifyou want to assign own signal names then en
35. Modbus RTU Slaves must comply with the settings in the netTAP or netBRICK device as Modbus RTU Master to establish a communication Important parameters are Modbus RTU address baud rate number of stop bits and parity setting Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 201 268 4 23 3 Modbus RTU Slave Settings at the used Modbus RTU Master Note The settings at the used Modbus RTU Master must comply with the settings in the netTAP or netBRICK device Modbus RTU Slave to establish a communication Important parameters are Modbus RTU address baud rate number of stop bits and parity setting However the Modbus RTU address must be unique e g the Modbus RTU address must be different from device to device The Modbus RTU Master can access to the netTAP or netBRICK device as a Modbus RTU Slave using function codes 1 2 3 4 5 6 7 8 15 16 and 23 Gateway netTAP netBRICK I O Signal Mapping Status Protocol 3 S X2 X3 OUT Superordinated Control Unit d FC 1 3 5 6 15 16 23 FC 2 4 IN with setting with setting Map FC 1 and FC 3 0O Map FC 1 and FC 3 O FC 5 6 15 16 23 FC 1 2 3 4 23 with settin
36. Output_O0C Status Active Slaves Remove link Manual Mapping Auto Mapping off X Cancel Apply Help Figure 31 Gateway Signals mapped The entry Memory Card Management in the navigation area is only available for netTAP NT 100 devices Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 50 268 2 3 7 Establish a Connection to the Gateway Device 1 Connect the USB cable gt Connect with an USB cable the USB connector of the netTAP respectively the netBRICK NB 100 device with the USB connector of the PC 2 Select the driver gt Select Settings gt Driver and then check netXDriver 3 gt The following figure shows the selected Driver J netDevice Gateway netTAP NT 100 XX XX lt gt 1 DER 2 10 Device NT 100 Xx x Device ID Vendor Hilscher GmbH Vendor ID 0x011E Navigation area A E Settings wp Driver Driver Version ID netX Driver oO CIFX Device Driver 1 0 3 1 368BEC5B 0E92 4C0E B449 64F624E7AAFA Device Assignment 35Gateway Driver for netX 3 x 0 9 2 0 787CD349 4CF6 4259 8E4D 109B646BE491 E Configuration netX Driver 1 101 1 1878 B54C8CC7 F333 4135 8405 6E12FC88EE62 Settings Signal Mapping Memory Card Management Licensing Figure 32 Select USB Driver 1 The entry Memory Card Management in the navigation
37. SYCON net OPC Server QVis Minimum Size QVis Standard Size QVis Maximum Size CoDeSys Minimum Size CoDeSys Standard Size CoDeSys Maximum Size For and minimum size standard size or maximum size can be selected only as an alternative Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 107 268 4 3 6 Ordering Data 1 Device Information a The Device Information required for the order are read from the device and automatically filled in the order 2 Ordering Data Enter the Ordering Data into the License pane gt Enter the Data to manage the Order therefore refer to section Data to manage the Order License Information on page 108 4 3 6 1 Device Information Ordering data read from the Device The following ordering data are read from the device and displayed in the License pane e Manufacturer e Device number e Serial number e Chiptype e Step chip revision e Romcode revision e Checksum checksum of the device data The gray fields under Request Form please fill out contain the ordering data read from the device Request Form please fill out gt I Manufacturer 00001 Article number 1251100 Serial number 20007 Chiptype 000000001 Step 000000000 Romeode revision 0x00000000 Checksum G J Fields marked with are mandat
38. Server gt Enter at the Open Modbus TCP Client the IP address of the netTAP or netBRICK device gt Use at the Open Modbus TCP Client port number 502 an Port 502 is used by the netTAP or netBRICK device to receive and send Open Modbus telegrams gt Use at the Open Modbus TCP Client function code 1 2 3 4 or 23 to read data from the netTAP or netBRICK device The following description shows the data assignment function code 23 also writes data into the device gt Use at the Open Modbus TCP Client function code 5 6 15 16 or 23 to write data into the netTAP or netBRICK device The following description shows the data assignment function code 23 also reads data from the device The Open Modbus TCP Client can access to the netTAP or netBRICK device as an Open Modbus TCP Server using function codes 1 2 3 4 5 6 15 16 and 23 Gateway netTAP netBRICK 1 0 Signal Mapping Status Protocol a AY x2 x3 OUT ae Superordinated _ FC 1 3 5 6 15 16 23 FC 2 4 j N with setting with setting Control Unit IN J Map FC 1 and FC 3 D Map FC 1 and FC 3 C1 m FC 5 6 15 16 23 FC 1 2 3 4 23 with setting with setting Map FC 1 and FC 3 m Map FC 1 and FC 3 amp Open Modbus TCP Client Figure 97 Access of the Open Modbus TCP Client to the netTAP and netBRICK Device Registers 16 bit value and coils 1 bit value share th
39. Set FSP Type Set for FSP Type value IO V1 Use this setting only Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 160 268 8 Set Output Data Size for fixed Configuration gt Set in Output Data Size for FixCfg the number of output bytes e g 2 9 Set Input Data Size for fixed Configuration gt Set in Input Data Size for FixCfg the number of input bytes e g 2 10 Set no address change by the master gt Check Master is not allowed to change sercos address by that the sercos Master can t change the address Use this setting only Note If you use a sercos Master which is using SDDML files for the configuration of slave devices then you have to export a new updated SDDML file from SYCON net and import this SDDML file into the configuration software for the sercos Master By that the settings made here can be used at the sercos Master Only then the sercos Master can communicate to the netTAP device respectively netBRICK device via sercos 11 Export SDDML file gt Click Export SDDML gt The file dialog opens gt Enter the file name for the SDDML file Use the following structure for the file name for a better identification Manufacturer DevicelD output data size input data size The file extension is always xml Example Hilscher NT100 RE_S3S_FIXCFG 2out 2in xml 3 gt The setti
40. Set the IP address range not to large which results in a long scan time gt After the address range was set click on Save Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 34 268 2 2 9 Device Assignment gt Select Settings gt Device Assignment gt Click on Scan gt The search process is started Devices found are display in a list then J netDevice Gateway netTAP NT 50 DP RS lt 2 gt 1 10 Device NT 50 DP RS Device ID Vendor Hilscher GmbH vendor ID 0x011E Navigation area Ei E Settings I Driver Scan progress 3 3 Devices Current device netx Driver _ 7 GEUG Device selection suitable only v Configuration Settings Device Hardware Ports 0 17 Slot nu Serial nu Driver Channel Protocol Access path Signal Mapping NT 50 DP RS Ethernet PROFIBUS n a 20004 nets Driver Gateway 4192 168 60 Access path B54C8CC7 F333 4135 8405 6E 12FC88EE62 192 168 60 198 50111 ciFxO_Cch2 Ke ie Save operation succeeded Figure 18 Select Device gt Select the device from the list by a check in the field of the device as shown above gt Click on the button OK 3 gt The configuration window closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English
41. Station type is Remote Device Station then set the number of stations for the netTAP device 1 2 3 or 4 Set number of extension cycles If CC Link Version 2 is to be used then set the number of extension cycles for the netTAP device 1 2 3 or 4 Note The number of O Data bytes depends on the following settings station type number of stations and number extension cycles The number of stations can only be configured with station type Remote Device Station version 1 and version 2 and the number of extension cycles can only be configured with version 2 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 8 gt 174 268 Set more parameter If necessary set more parameter The parameter are described in the following section CC Link Slave Parameter on page 175 Note Default values can be used normally for the other parameters Depending on additionally requirements and the design of the CC Link network as well as the used devices parameters needs to be adjusted if necessary Open the signal configuration dialog Select in the navigation area under the folder Configuration the entry Signal Configuration The signal configuration dialog opens Signal configuration If you want to assign own signal names then enter your signal names Further information is described in s
42. Status ok 0x00000000 5 DPM_SYS 1 0 44 TLR Router DPM Task Status ok Ox00000000 6 DPM_COMO 1 0 50 TLR Router DPM Task Status ok 0x00000000 7 DPM_COMO 1 0 51 TLR Router DPM Task Status ok 0x00000000 8 TLR_TIMER 0 0 39 The task identifie Task Status ok Ox00000000 9 PROFIBUS_DL 1 0 40 PROFIBUS Data Task Status ok Ox00000000 10 PROFIBUS_ 1 2 43 PROFIBUS Maste Task Status ok Ox00000000 11 PROFIBUS _ 1 2 42 PROFIBUS Maste Task Status ok 0x00000000 12 RX_IRQ 0 0 15 The task identifie Task Status ok Ox00000000 Figure 105 Firmware Diagnosis The name of the Firmware is displayed Task Information The table Task Information is listing the task information of the single firmware tasks Goin wen SC CS S C CNCSNNCNNONCSCti NN O Description of the task Table 77 Description Table Task Information Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Online Functions 233 268 6 Online Functions 6 1 Connecting Disconnecting Device Note Several netGateway DTM functions e g Diagnosis or the configuration download in the FDT Framework require an online connection from the netGateway DTM to the netTAP NT 100 device Connecting Device The following steps are needed to establish a connection from the netGateway DT
43. Type of the serial interface which should be used RS232 Default RS485 RS422 RTS Control Specifies if RTS control is activated or deactivated RTS Control Off Default When using the interface type RS 485 then RTS Control on has to RTS Control On be used Baud rate Specifies the baud rate 300 Bit s 600 Bit s 1200 Bit s 2400 Bit s 4800 Bit s 9600 Bit s Default 19200 Bit s 38400 Bit s 57600 Bit s 115200 Bit s Data bits Specifies the number of data bits 7 or 8 A 8 Default Stop bits Specifies the number of stop bits 1 or 2 RRN Specifies the parity bit of the serial data communication None Default None means that no parity bit is used Even Odd Table 58 ASCII Parameter 4 25 2 ASCII Parameters The operating modes are e Receive Only Mode e Send Only Mode e Client Mode first send then receive e Server Mode first receive then send The further configuration parameters specify the e the telegram structure of the send telegram e the telegram structure of the receive telegram e the timing e the size of the send and receive buffer Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010Ol06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 212 268 4 25 2 1 Telegram Structure in Data Stream A send or receive telegram in the simplest case only consists only by user data Many implementations however
44. are sent Table 75 Indication General Diagnosis Parameter Meaning S OSO Communication Error Communication Error Shows the message text of the communication error If the cause of the current error is resolved is displayed Watchdog time Watchdog time Shows the watchdog time in ms Error Count Error Count This field holds the total number of errors detected since power up respectively after reset The protocol stack counts all sorts of errors in this field no matter if they were network related or caused internally Table 76 Parameter General Diagnosis Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Diagnosis 232 268 5 3 Firmware Diagnosis In the dialog Firmware Diagnosis the actual task information of the firmware is displayed Under Firmware or Version the name of the firmware and version including the date are indicated Firmware Firmware Name version 2 0 0 Build 3 Date 1 12 2006 Task information Name of task version Prio Description State 0 RX_IDLE 0 0 63 The task identifie Task Status ok 0x00000000 1 RX_TIMER 0 0 1 The task identifie Task Status ok 0x00000000 2 RX_SYSTEM 1 16 8 Middleware Syst Task Status ok Ox00000000 3 RX_IRQ 0 0 16 The task identifie Task Status ok 0x00000000 4 DPM_SYS_ 1 0 45 TLR Router DPM Task
45. are displayed as they will become visible at the PROFINET IO Controller These slot numbers and sub slot numbers will be exported into the GSDML file which is described later Slot 0 NT 100 RE DP PROXY and slot 1 NT100 PROFIBUS DP are always present Two additional slots slot 2 in this case which represent the PROFIBUS DP Slave with station address 2 slot 3 in this case which represent the PROFIBUS DP Slave with station address 3 are automatically displayed when the PROFIBUS DP Slaves were inserted to the PROFIBUS DP network These Slot and sub slot numbers are used in the GSDML file The GSDML file can be created exported which is described later Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 65 268 2 Set the name of station gt Select in the navigation area General 3 gt The following configuration window opens S netDevice PROFINET IO Device netTAP NT 100 RE DP PROXY lt gt 1 mm IO Device NT 100 RE DP Device ID 0x0106 Vendor Hilscher GmbH Vendor ID Ox011E Navigation Area FE E Configuration wp General Name of station nti00reproxy Modules Address Table Description NT_100 RE DP E Description Device Info IP settings Module Info GSDML Viewer IP address Note These values are set by Network mask the controller of the
46. area is only available for netTAP NT 100 devices Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 4 Select the netXDriver 51 268 gt Select Settings gt Driver gt netXDriver 3 gt The following figure shows the selected Driver ZnetDevice Gateway netTAP NT 100 XX XX lt gt 1 Navigation area A Settings Driver Segnets Driver Device Assignment E Configuration Settings Signal Mapping Memory Card Management Licensing 10 Device Vendor NT 100 X XX Hilscher GmbH Select Port COMI Port Configuration Disable Port Lrs Connection TCP Connection V Enable USB R5232 Connector Restart of ODM required X Baud Rate 115 2 kBit s Stop Bits 1 Stopbit Send Timeout 1000 Reset Timeout 5000 ms ms Device ID Vendor ID OxO11E Byte Size 8 Byte Parity No Parity Keep Alive Timeout 2000 Figure 33 Select USB Driver 2 5 Select the netXDriver gt gt gt Click on Save Restore Save Ce Cancel Help Select the tab USB RS232 Connection Check Enable USB RS232 Connector Note The standard setting of the netX Driver USB RS232 can be used for netTAP respectively netBRICK devices without changes Configuration of Gateway and Pr
47. assignment for registers and coils for zero based Open Modbus TCP Clients The setting Map FC 1 and FC 3 is not set in the configuration of the netTAP or netBRICK device in this case OUT netTAP Coil Register or netBRICK Fc 2 FC 4 Mapping Configuration IN netTAP or netBRICK Mapping 32 47 IN 624 9985 9998 OUT 1 16 31 OUT 2 32 47 OUT 624 9985 9998 Table 25 Access of the Open Modbus TCP Client using Zero based Addressing 1 The following table shows the address assignment for registers and coils for zero based Open Modbus TCP Clients The setting Map FC 1 and FC 3 is set in the configuration of the netTAP or netBRICK device in this case IN netTAP or netBRICK Mapping IN 624 9985 9998 32 47 Register FC 3 FC 6 FC 16 FC 23 schreiben Register FC3 FC 4 FC 23 lesen OUT netTAP Coil or netBRICK Fc 1 Mapping FC 2 OUT 1 16 31 OUT 2 32 47 OUT 624 9985 9998 Table 26 Access of the Open Modbus TCP Client using Zero based Addressing 2 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010106EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 146 268 One based addressing The first register 16 bit value as well as the first coil 1 bit value has address 1 the second register as well as the first coil has address 2 etc independed of the use
48. at the PC Via the RS232 interface or USB interface of the device the device is configured or diagnosis is performed Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Settings 90 268 Driver Parameters for netX Driver USB RS232 Connection The settings of the driver parameters for the USB RS232 connection are made via the netX Driver USB RS232 Connection configuration dialog gt Open the USB RS232 Connection dialog via navigation area Settings gt Driver gt netX Driver gt The USB RS232 Connection dialog is displayed USB RS232 Connection TCP Connection V Enable USB R5232 Connector Restart of ODM required Select Port com Port Configuration I Disable Port Baud Rate Stop Bits Send Timeout Reset Timeout 1000 10000 ms Leb lele 8 Byte 115 2 kBit s v Byte Size 1 Stopbit v Parity No Parity v ms Keep Alive Timeout 2000 ms Restore Save Save All Figure 69 netX Driver gt USB RS232 Connection Parameter Meaning Range of Value Value Enable USB RS232 Connector Restart of ODM required checked The netX Driver can communicate via the USB RS232 interface unchecked The netX Driver can not communicate via the USB RS232 interface If the check mark for Enable USB RS232 Connector is set or removed then the ODM server mu
49. baudrate Set the baudrate for the netTAP or netBRICK device which is used in the CANopen network 4 Set more parameter If necessary set more parameter The parameter are described in the following section CANopen Slave Parameter on page 168 Note Default values can be used normally for the other parameters Depending on additionally requirements and the design of the DeviceNet network as well as the used devices parameters needs to be adjusted if necessary Note The maximum number of output data bytes and input data bytes is for the netTAP or netBRICK device 512 bytes each The number of output data bytes and input data bytes is not adjustable in the Slave and therefore grayed out in the dialog The number of output data bytes and input data bytes which are to be transferred effectively between the CANopen Master and Slave are configured in the used CANopen Master The CANopen Master configures the netTAP or netBRICK device during establishing the communication and set the number of output data bytes and input data bytes at this same time Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 169 268 5 Open the signal configuration dialog gt Select in the navigation area under the folder Configuration the entry Signal Configuration 3 gt The signal configuration dialog opens 6 S
50. ccccccceseeeeseeceeeeeceaeeeeeeeeseeeeeseaeeeeaeeeeaes 166 4 16 Configuration CANopen Master ic accsactt iia ds es ha ee 167 4 17 Configuration CANopen Slave ccccccceeeeeeeeeeeeeeeeeeeeeeeeeceeeeeeseeeeeeeeeaeeeeeeenaeeeeee 168 4 17 1 CANopen Slave Parameter cccscccsecceceeeceeeaeeeeneeceeeeeeaeseenaeeseaeeesaeeeenaeeeaes 170 4 17 2 Settings at the used CANopen Mastel ccccesceceeeeecceeeeeeeeeseeeeeseaeeeeeeeees 172 4 18 Configuration CC Link Slave ssc cststacdaat nadetnuned la ein acted ines Daueieeead 173 4 18 1 CC Link Slave Parameter cccccececeeeeceeeeeeeeeeaeeeeeeeceeeeecaaeeseeeeseeeeseaeeteneeeeaes 175 4 18 2 Settings at the used CC Link Mastel c ccceeeseeeeceeeeeceeeeeeeeseeeeeessaeeeeeeeeaes 177 4 19 Configuration DeviceNet Master cccceecceeeeeeseeeeeeeeeeeeeeeeeeaeeeeeeeeaaaeeeeesaaeeeenas 178 4 20 Configuration DeviceNet Slave cecscceeecessceeeeeesseeeeeeesseeeeeeeeeaeeeeeeaaeaeeeeeeaaeeeens 179 4 20 1 DeviceNet Slave Parameter cc cccccececseeeeeeeeeeeeeeceaeeeseaeeeeaeeseeeesaeeeeaeeeenees 181 4 20 2 Settings at the used DeviceNet Master ccscceeeeeceeeeeeeeeeeeeeeeseaeeteaeeeeaes 183 4 21 Configuration PROFIBUS DP Master cccsssecceeeeeeeeeeeeeeeceeeeeesaceeeeeeneeeeeenes 184 4 22 Configuration PROFIBUS DP Slave ccceccceseeeeeeeeeeeneeeeeeeneeeeesenaeeeeeennaeeeene 185 4 22 1 PROFIBUS DP Slave Parameter c
51. configuration of the netTAP or netBRICK device in this case IN netTAP or i OUT netTAP Coil Register netBRICK or netBRICK Fc 2 FC 4 Mapping Mapping OUT 0 10001 10016 30001 OUT 1 10017 10032 30002 OUT 2 10033 10048 30003 IN 624 9985 9999 40625 OUT 624 19985 19999 30625 Table 23 Access of the Open Modbus TCP Client using Modicon based Addressing 1 The following table shows the address assignment for registers and coils for modicon based Open Modbus TCP Clients The setting Map FC 1 and FC 3 is set in the configuration of the netTAP or netBRICK device in this case IN netTAP Coil Register OUT netTAP Coil Register Register or FC 6 or netBRICK FC 1 FC 4 FC 3 netBRICK FC 15 FC 16 FC 23 Mapping FC 23 read 40001 OUT 0 10001 10016 30001 40001 fie oe ieee ee eee E ee 1 16 17 32 OUT 1 17 32 10017 10032 30002 40002 3 48 owa o ooo o eo _ Table 24 Access of the Open Modbus TCP Client using Modicon based Addressing 2 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 145 268 Zero based addressing The first register 16 bit value as well as the first coil 1 bit value has address 0 the second register as well as the first coil has address 1 etc independed of the used function code The following table shows the address
52. device f Important Do not remove the cable during the firmware download Do not disconnect the power supply of the device during the firmware download Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 54 268 5 Download of firmware gt Wait until the firmware was transferred completely into the device 6 Close the Gateway configuration window after the download gt Click OK The Gateway configuration window closes 2 3 10 Load Configuration 1 Download configuration gt Select from the context menu of the gateway device symbol the entry Download gt Answer the security question with Yes if the download should start 3 SYCON net builds up an online connection to the device This the indicated by a green highlighted device name gt The configuration is transferred info the gateway device 3 gt The device performs a reset and then starts with the new configuration 2 3 11 Save Project Note The configuration downloaded from SYCON net into the device can t be uploaded from the device Only the SYCON net project can be downloaded into additional devices Save the SYCON net project In case of a device replacement the saved project can be opened with SYCON net and loaded into the device gt To save a project select menu File gt Save
53. device description file is required The GSDML file depends on the PROFIBUS DP configuration and is created by an export function How to export the GSDML file and the structure of the GSDML file name is described for the netTAP NT 100 proxy device in section Device Description File to configure the PROFINET IO Controller on page 71 and for the netLINK NL 51N DPL proxy device in section Device Description File to configure the PROFINET IO Controller on page 84 Configuration gt Note The settings in the used Controller must comply with the settings in the Device to establish a communication Important parameters are Name of Station Vendor ID Device ID Input and Output data modules In order that the PROFINET IO Controller can communicate with the netTAP or netLINK device as PROFINET IO Device gt Note Under Name of Station in the PROFINET IO Controller the name must be used which was configured in the netTAP or netLINK device gt Enter at the PROFINET IO Controller the Name of Station which is configured in the netTAP or netLINK device gt Use for the configuration of the PROFINET IO Controller modules based on the exported GSDML file gt The PROFINET IO Controller verifies identification numbers of the netTAP respectively netLINK device Vendor ID value 0x011E 286 device type value for NT 100 as proxy is 0x0106 262 value for NL 51N DPL as proxy is 0x0110 272 The PROFINET IO Controller ge
54. file is saved The structure of the file name is GSDML OO oO Hilscher NL 51N ae 20100721 roy 000 xm Q Fixed prefix Version number of the GSDML specification Manufacturer name Device type Date Format yyyymmdd Time Format hhmmss File extension always xml gt Use the GSDML file to configure the PROFINET IO Controller Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 85 268 2 5 11 Update Firmware To update the firmware an Ethernet connection to the device is necessary To establish a connection do the steps described in section Device Assignment on page 68 To update the firmware proceed then as follows gt Select from the context menu of the NL51iN DPL the entry Configuration gt Proxy 3 gt The following window opens Yx netDevice Proxy netLINK NL 51N DPL lt gt 1 10 Device NL S1N DPL Device ID 5 vendor Hilscher GmbH vendor ID 0x011E Navigation area Settings General I Driver netX Driver Description netLINK Device Assignment 4 Configuration Settings Fe Primary network Port x2 Zi Secondary network Port X3 zj Required gateway Protocol Combinations Required license Yes 1 Available Firmware Browse OJ Software class Software version Basic Settin
55. function is not supported by gateway or proxy devices 0 20 65535 ms default 1000 ms 0 Watchdog timer off I O Data Status Status of the input or the output data Default None For each input and output data the following status information in Byte is stored in the dual port memory Status 0 None default Status 1 1 Byte for future use Status 2 4 Byte for future use Application Mode Mode how the superordinated control unit controls to send a Default Handshake Mode 3964R telegram respectively detects the receipt of a 3964R telegram Handshake Mode The control is done with synchronization registers Device Device name lf Enabled is unchecked the default value is used Interface Type Type of the serial interface which should be used RS232 Default RS422 RS485 RTS Control Specifies if RTS control is activated or deactivated RTS Control Off Default When using the interface type RS 485 then RTS Control on has RTS Control On to be activated On Baud Rate Specifies the baud rate 300 Bit s 600 Bit s 1200 Bit s 2400 Bit s 4800 Bit s 9600 Bit s Default 19200 Bit s 38400 Bit s 57600 Bit s 115200 Bit s Data Bits Specifies the number of data bits 7 or 8 7 8 Default Stop Bits Specifies the number of stop bits 1 or 2 1 Default 2 Parity Specifies the parity bit of the serial data communication None Default None means that no parity bit is used are Table 56 3964R Parameter
56. information about Modbus RTU parameter is in section Modbus RTU Parameter on page 192 Close the configuration window Click OK The configuration window closes oxy Devices netTAP netBRICK and netLINK DOC0812010106EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 27 268 2 2 6 Configuration of the primary Network 1 Configure the protocol at the primary network Port X2 gt Select from the context menu of the NT 50 XX XX symbol the entry Configuration gt PROFIBUS DP Slave gt The PROFIBUS DP Slave configuration window opens ZnetDevice PROFIBUS DP Slave netTAP NT 50 DP RS lt 2 gt 1 10 Device NT SO DP RS Device ID Ox049F Vendor Hilscher GmbH vendor ID OxOlle Navigation area E Configuration Interface configuration Signal Configuration Bus startup Watchdog time 1 0 data status Ident Ident number Enable Bus Station addess 1 Vv Baud rate Auto detect Se Extras Syne supported v DP 1 enable v Freeze supported V Address change not allowed IV Fail Safe supported v Data Output Input Module Type Module Type 1 Byte 5 Byte 2 Byte 6 Byte ind 3 Byte 7 Byte j Byte Byte Configuration data Manual input Output data bytes 2 Input data bytes 2 Default Figure 12 Protocol Configuration 2 Set parameter for protocol at the primary network port
57. information is described in section Signal Configuration on page 228 7 Close configuration dialog Click on OK to save the parameter or click on Cancel if the parameter should not be saved 3 gt The configuration dialog closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 192 268 4 23 1 Modbus RTU Parameter Bus Startup Communication startsautomatically Automatic Default Watchdog Time This function is not supported by gateway or proxy devices 0 20 65535 ms ms default 1000 ms 0 Watchdog timer off Address Mapping Valid address range of the data 0 65535 This parameter can not be edited here Data Swapping Data storage mode Yes No No Data will not be swapped Default Yes Yes Data will be swapped Map FC1 If unchecked data are read from the intput area using FC1 FC3 and checked and FC3 FC23 unchecked If checked data are read from the output area using FC1 FC3 and Default unchecked FC23 FC1 then can be used instead of FC2 and FC3 instead of FC4 Device Device code NT50 NT100 Default If Enabled is unchecked the default value is used NB100 String Protocol Mode Determines the Mode of operation Master or Slave Master For Master mode Command Table is displayed in the navigation area O Slave Default For the Modbus RTU Master the Comma
58. master in certain Fieldbus systems As long as those indications are pending and not serviced this field holds a value unequal to zero If no more diagnostic information is pending the field is set to zero Host Watchdog Master and Slave Note This field is not yet supported Slave Error Log Indicator Master Note This field is not yet supported Slave State Master The slave state field indicates whether the master of the remote network is in cyclic data exchange to all configured slaves In case there is at least one slave missing or if the slave has a diagnostic request pending the status is set to FAILED For protocols that support non cyclic communication only the slave state is set to OK as soon as a valid configuration is found Status Value Undefined 0 Ok 1 Failed 2 Version Master and Slave The version field holds the version number of this structure The value is 1 Watchdog Timeout Master and Slave This field holds the configured watchdog timeout value of the protocol stack of the remote network The value is specified in milliseconds Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 122 268 4 5 Memory Card Management Note This function is only available for the netTAP NT 100 device family because these devices have a MMC card slot
59. or the output data Default None For each input and output data the following status information in Byte is memorized in the dual port memory Status 0 None default Status 1 1 Byte for future use Status 2 4 Byte for future use Ident Number PROFIBUS Identification Number 0x00000000 If Enabled is unchecked the default value is used OxOOOOFFFF hex Default NT 50 0x000000C99 hex NT 100 0x000000C0E hex NB 100 0x00000C9C hex If Enabled is unchecked the default value is used Pe Station Address PROFIBUS address of the device 0 126 Baudrate Network Baud Rate 9 6 kBit s 19 2 kBit s 93 75 kBit s 187 5 kBit s 500 kBit s 1 5 MBit s 3 MBit s 6 MBit s 12 MBit s 31 25 kBit s 45 45 kBit s Auto Detect Default Auto Detect Extras Sync supported If checked the Slave stack supports the SYNC command or the SYNC mode is activated DPV1 Enable If checked DPV1 is supported or the DPV1 functions are activated Freeze supported If checked the Slave stack supports the FREEZE command or the FREEZE Default checked mode is activated Address change not allowed If checked the Slave stack supports the Set Slave Address command The bus address can be changed via the Master Fail safe supported If checked the FAILSAFE operation is supported or the FAILSAFE mode is activated Table 44 Parameters PROFIBUS DP Slave Part 1 Configuration of Gateway and Proxy Devices net
60. respectively File gt Save As or click on icon i When you exit the program and the current configuration differs from the last saved configuration then the following question appears A Save changes to the project no coea Figure 36 Security Question Save Project When you answer with Yes then the project is saved When you answer with No then the project is not saved and the changes are lost When you answer with Cancel then the project is not saved Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 55 268 2 3 12 Device Description File to configure the Master A GSDML file is required to configure the PROFINET IO Controller gt To configure the PROFINET IO Controller use the following GSDML file from the product DVD directory EDS PROFINET for NT 100 GSDML V2 1 HILSCHER NT 100 RE PNS 20090123 xml for NB 100 GSDML V2 1 HILSCHER NB 100 RE PNS 20100226 xml for NT 50 GSDML V2 1 HILSCHER NT 50 EN PNS 20100226 xml Note The product IDs are different for devices used as gateway and devices used as proxy Make sure to use import the right GSDML file at the PROFINET IO Controller gt Load the GSDML file into the configuration software of the PROFINET IO Controller Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC081201
61. table invalid DEV_E CF_INVALID_INPUT_OFFSET 0x8004C097 CONFIG Input offset is invalid DEV_E_CF_NO_INPUT_SIZE 0x8004C098 CONFIG Input size is 0 DEV_E_CF_MISMATCH_INPUT_SIZE 0x8004C099 CONFIG Input size does not match configuration DEV_E_CF_INVALID_OUTPUT_OFFSET 0x8004C09A CONFIG Invalid output offset DEV_E CF_NO OUTPUT SIZE 0x8004C09B CONFIG Output size is 0 DEV_E_CF_MISMATCH_OUTPUT_SIZE 0x8004C09C CONFIG Output size does not match configuration DEV_E_CF_STN_NOT_CONFIGURED 0x8004C09D CONFIG Station not configured DEV_E_CF_CANNOT_GET_STN_CONFIG 0x8004C09E CONFIG Cannot get the Station configuration DEV_E_CF_MODULE DEF MISSING_NO SI 0x8004C0A4 CONFIG Module definition is missing no Slot Idx Table 88 cifX Driver Specific ODM Error Codes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Error Codes 250 268 8 5 Error Codes cifX Device Driver and netX Driver 8 5 1 Generic Error Codes Error Code Definition Value Description CIFX_INVALID_POINTER 0x800A0001 Invalid pointer NULL passed to driver CIFX_INVALID_ BOARD 0x800A0002 No board with the given nameindex available CIFX_INVALID_ CHANNEL 0x800A0003 No channel with the given index available CIFX_INVALID_ HANDLE 0x800A0004 Invalid handle pa
62. the Open Modbus TCP Client produces a telegram for reading or for the writing of data to or from an Open Modbus TCP Server device For every command are indicated e the Open Modbus TCP Server device address Device Address e the Unit identifier to identify a remote Server via gateway e the Function code e the data address in the Open Modbus TCP Server device Address e the number of data Number of Registers Coils e and the data address in the Open Modbus TCP Client device Memory Address internal For writing telegrams FC 5 6 15 and 16 in the column e Trigger you can decide whether the writing telegrams are executed every time Cyclic or only at data modification Change data Furthermore e a Cycle Time can be set for every command The Command Table is processed from the first to the last entry from above to below After the execution of the last command the execution of the first command is started again For reading commands the Open Modbus TCP Client reads out data from the Open Modbus TCP Server and saves them into its data memory For writing commands the Open Modbus TCP Client reads out data from its data memory and writes them into the Open Modbus TCP Server The number of commands which can be defined depends from the firmware and from the Dual Port Memory layout For Open Modbus one connection per IP address is established In maximum 16 Client connections can be supported In this case the pa
63. the connection establishment to a device Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Settings 95 268 3 2 4 Configure netX Driver The following steps are required to configure the netX Driver USB RS232 Connection To set the driver parameters for an USB RS232 connection note Note Adjust the driver parameters netX Driver USB RS232 only if they differ from the default settings After saving the changed driver parameters these parameters are used for the device assignment when scanning devices TCP IP Connection For setting the driver parameters for a TCP IP connection 1 Select Settings gt Driver gt netX Driver gt TCP Connection Set IP Address of the device 2 gt Add an IP Range via Select IP Range 3 Under IP Range Configuration gt IP Address enter the IP Address of the device Use IP Range is unchecked Or 4 Set IP Range Check Use IP Range gt Under IP Range Configuration gt IP Address enter the start address left side and the ending address of the IP scanning range right side 5 Click Save to save the IP address or the IP range Vv gt After saving the changed driver parameters these parameters are used for the device assignment when scanning devices Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revi
64. the navigation area the entry Configuration under the folder Configuration is selected and the settings dialog is displayed Set protocol mode Set the Protocol Mode to I O Server if the netTAP or netBRICK device should work as Open Modbus TCP Server Set for the Protocol Mode to Client if the netTAP or netBRICK device should work as Open Modbus TCP Client If you have set the Protocol Mode to Client then the entry Command Table appears in the navigation are Open Modbus TCP Parameter To set a fix IP address Deselect the flag DHCP and BootP Select IP address Enable and enter a valid IP address for the NT 100 device Select netmask enable and enter a valid netmask If needed Select the gateway enable and enter a valid IP address for the gateway Note Default values can be used normally for the other parameters Depending on additionally requirements and the design of the Ethernet network as well as the used devices parameters needs to be adjusted if necessary Further information is described in section Open Modbus TCP Parameter on page 135 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 4 gt 134 268 Command Table If you have set the Protocol Mode to Client then select in the navigation area the entry Command Table Specify in the Command Table which data the Ope
65. these are transmit PDOs E g the Master can be configured with 4 PDOs with 8 byte user data each 32 bytes in total to be received from the netTAP or netBRICK device Vv Vv Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 173 268 4 18 Configuration CC Link Slave The netTAP NT 50 and NT 100 device as CC Link Slave needs parameter These parameter can be edited as follows 1 gt Open the configuration dialog Select from the context menu of the netTAP symbol the entry Configuration gt CC Link Slave The CC Link Slave configuration dialog opens In the navigation area the entry Configuration under the folder Configuration is selected and the configuration dialog is displayed Set Stationaddress Enter in the field Stationaddress the address which the netTAP device uses on the CC Link network to be addressed by the CC Link Master Set baudrate Set the baudrate for the netTAP device which is used in the CC Link network Set the CC Link version Select with the field CC Link Version the CC Link version the netTAP device should use to communicate with the CC Link Master Set the Station type If CC Link Version 1 is to be used then select with the field Station Type either Remote Device Station or Remote IO Station for the netTAP device Set the Number of Stations If
66. this one first before opening a new one CDBM_ _OLD_WITHOUT_HEADER 0X4004C823 Use of an old DBM file Format without Informational Header CDBM_E_HR_FROM 0XC004C824 An HRESULT was received from a Subroutine CDBM_E_PARAMETER 0XC004C825 A Parameter is invalid CDBM_E_NOTIMPL OXC004C826 Method is currently not implemented CDBM_E_OUTOFMEMORY 0XC004C827 Out of memory CDBM_E_NO_OPEN_TRANSACTION 0XC004C828 No transaction open CDBM_E_NO_CONTENTS 0XC004C829 No contents available CDBM_REC_NO_NOT_FOUND OXC004C82A Record not found CDBM_STRUCTURE_ELEMENT_ NOT_FOUND 0XC004C82B Element of the Structure not found CDBM_E_NO_MORE_RECORDS_IN_TABTYPE 0XC004C82C Table type 3 can contain only one record CDBM_E_WRITE 0XC004C82D The data in the VARIANT must be given in a SafeArray CDBM_E_WRITE_NO_PARRAY 0XC004C82E The VARIANT contains no valid parray element CDBM_E_WRITE_CANT_ACCESS_DATA OXC004C82F Unable to access SafeArray Data in the VARIANT Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010106EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Error Codes 255 268 ODM Error Codes DBM V4 Error Code Definition Value Description CDBM_E_WRITE_DATA 0XC004C830 To write the data of this Element it must be given as a BSTR or as an Array of VT_UN VT_H CDBM_E_WRITE_BSTR_E1 0XC004C831 The BSTR string must have an ev
67. triggered from the superordinated control unit or performed by the device cyclically e triggered Telegram Telegram With each handshake of the superordinated control unit a telegram is send For this set the timing parameter Send Cycle Time to zero e Cyclic The device sends in a constant cycle With each handshake of the superordinated control unit the send data initially are updated in the internal buffer of the device and sent during the next send cycle For this set the timing parameter Send Cycle Time to the cycle time unequal to zero Timing Parameter Parameter Description Range of Value Send Cycle Specifies whether the telegram will be sent cyclically or triggered 0 28 1 Time The value unequal to zero specifies the cycle time of the send telegram Default 0 The value 0 specifies that the send telegram is triggered Table 64 Timing Parameters for the Operating Send Only Mode Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Configuration Example O Receive Only Mode Client Mode Server Mode Send Data Stream Configuration Start x l 2 Data Constant Length bytes 0 Check v ox8005 End 3 Unused z ooo e Unused z Unused z Send Cycle Time o ms Signal Configuration Enabled Ta
68. with the structure of the PROFIBUS alarm Pull alarm Pull alarm Plug alarm Plug alarm Manufacturer specific alarm Ma a alarm with the structure of the PROFIBUS alarm Table 80 PROFINET IO PRPFIBUS Mapping of Alarms Alarm data are forwared unchanged Extended PROFIBUS diagnostic are mapped to PROFINET IO diagnostic with UserStructID 0x2000 x PROFIBUS diagnostic alarms are mapped to PROFINET IO diagnostic with UserStructID 0x4000 x PROFIBUS DPV1 parameter services are not transfered to PROFINET IO and via versa Note Had a PROFIBUS DP slave device generated a pull alarm once and this device module goes into communication again then a manual reset to the proxy device is necessary by a short disconnect of the power supply by example to force the prxy device to reload the configuration data Was the PROFIBUS DP slave device removed only from the PROFIBUS without a generation of a pull alarm then the communication start automatically if the PROFIBUS DP slave device is reconnected to PROFIBUS Note If a PROFIBUS DP slave device generates a plug alarm a new device module was added to PROFIBUS then the proxy device has to be reconfigured with new configuration data by the user Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Error Codes 240 268 8 Error Codes 8 1 Error Code Definition F
69. 00 CO COS 0x001A2020 hex NB 100 CO COS 0x001B3190 hex Revision Revision number of the device as specified by the manufacturer 0x00000000 Number OxFFFFFFFF hex Default 0x00020000 hex Serial Number Serial number of the device 0x00000000 OxFFFFFFFF hex Node Address Node ID of CANopen slave 1 127 Default 2 Baudrate Baud rate of CANopen connection 1 Mbaud 800 Kbaud 500 Kbaud 250 Kbaud 125 Kbaud 100 Kbaud 50 Kbaud 20 Kbaud 10 Kbaud Default 1 MBaud Table 35 CANopen Slave Parameters Part 1 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 171 268 Send Object Send Object Send object index 0x00002000 Receive Object Receive Object Receive object index 0x00002003 hex 0x00002200 0x00002203 hex Size 128 Number of data Bytes to send per send object or number of data Bytes to receive per send object Output Data Total output data Bytes of all send objects 512 Bytes Default 512 Bytes Input Data Total intput data Bytes of all receive objects 512 Bytes Default 512 Bytes Table 36 CANopen Slave Parameters Part 2 Note To configure the Master an EDS file device description file is required The settings in the used Master must comply with the settings in the Slave to establish communication Important parameters are Node Addr
70. 00 device respectively the netBRICK NB 100 device as PROFINET IO Controller needs a configuration e g information about how many PROFINET IO Device devices with how many input and output data are to be connected 1 gt Insert PROFINET IO Device devices Drag from the device catalog PROFINET IO Device device s and drop it to the bus line of the PROFINET IO Controller Configure PROFINET IO Device devices Open the configuration dialog for each PROFINET IO Device device and configure the device Information about how to configure the PROFINET IO Device device is in the operating instruction manual Generic DTM for PROFINET IO Device devices and has the file name PROFINET_IlO_GenericDevice_DTM_en pdf respectively open in the configuration dialog of the slave the online help by the F1 key Configure PROFINET IO Controller gt Select from the context menu of the netTAP respectively the netBRICK symbol the entry Configuration gt PROFINET IO Controller Information about how to configure the PROFINET IO Controller device is in the operating instruction manual DTM for PROFINET IO Controller devices and has the file name PROFINET_lIO_Controller_ DTM_en pdf respectively open in the configuration dialog of the master the online help by the F1 key Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configura
71. 0000111 hex 0x00000000 OxOOOOFFFF hex Default 0x00000000C hex Major revision Major revision of the EtherNet IP Adapter device according to the 0 255 EtherNet IP specification Default 1 Minor revsion Minor revsion of the EtherNet IP Adapter device according to the 0 255 EtherNet IP specification Default 1 Device name Device name of the device station as character string e g EtherNet IP Adapter Slave IP Address Valid IP Address for the device If Enable is unchecked Default setting the device obtains its IP Address from a DHCP server or also from a BOOTP server if this one is checked If Enable is checked the device uses the manually entered value Netmask Valid Network mask for the device If Enable is unchecked Default setting the device obtains its Netmask from a DHCP server or also from a BOOTP server if this one is checked If Enable is checked the device uses the manually entered value Gateway Valid Gateway Address for the device If Enable is unchecked Default setting the device obtains its Gateway Address from a DHCP server or also from a BOOTP server if this one is checked If Enable is checked the device uses the manually entered value Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public 0 31 ASCII characters Examples NT 50 EN EIS NT 100 RE EIS NB
72. 004C076 USER Firmware file BOOTLOADER active Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Error Codes 249 268 cifX Driver Specific ODM Error Codes Error Code Definition Value Description DRV_E_FW_NO_FILE_PATH 0x8004C077 USER Firmware file no file path DRV_E_CF_FILE_OPEN_ FAILED 0x8004C078 USER Configuration file could not be opend DRV_E_CF_FILE_SIZE_ ZERO 0x8004C079 USER Configuration file size zero DRV_E_CF_FILE_NO_MEMORY 0x8004C07A USER Not enough memory to load configuration file DRV_E_CF_FILE_READ_FAILED 0x8004C07B USER Configuration file read failed DRV_E_CF_INVALID_FILETYPE 0x8004C07C USER Configuration file type invalid DRV_E_CF_FILENAME_INVALID 0x8004C07D USER Configuration file name not valid DRV_E_CF_DOWNLOAD_ERROR 0x8004C07E USER Configuration file download error DRV_E_CF_FILE_NO_SEGMENT 0x8004C07F USER No flash segment in the configuration file DRV_E_CF_DIFFERS_FROM_DBM 0x8004C080 USER Configuration file differs from database DRV_E_DBM_SIZE_ZERO 0x8004C083 USER Database size zero DRV_E_DBM_NO_ MEMORY 0x8004C084 USER Not enough memory to upload database DRV_E_DBM_READ_FAILED 0x8004C085 USER Database read failed DRV_E_DBM_NO_FLASH_SEGMENT 0x8004C086 USER Database segment unknown DEV_E_CF_INVALID_DESCRIPT_VERSION 0x8004C096 CONFIG Version of the descript
73. 0l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 113 268 4 3 7 3 Exporting License Request to a File If you are working on a process computer without an e mail client you can export your order information to a file save the file to a removable disk and place your order manually via e mail from a different PC Export License Request O Figure 89 License Pane Ordering by exported File and E Mail Click Export License Request The window Browse For Folder is displayed Choose for or create a new folder on a removable disk Save the automatically generated XML file EmailOrderRequest_ Devicenumber _ Serialnumber xm with a summary info of the order information to this folder Send this file from a PC with an e mail client manually via e mail gt Therefore use an e mail address which is displayed after the subsidiary was selected in the License pane see Position Figure License Pane on page 103 gt The order process is complete VV dv Vv Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 114 268 4 3 8 How to get the License and transfer it to the Device Note License files can only be delivered via e mail The e mail contains a link to download the license file According to the license you ordered you will rec
74. 0l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 56 268 2 4 Configuration of a NT 100 as Proxy For the conversion from PROFINET IO Device to PROFIBUS DP Master with proxy functionality the device NT 100 RE DP can be used Therefore use the device NT 100 RE XX PROXY from the device catalog These devices are called proxy device in the following description The device NT 100 RE DP with one master license is necessary for the protocol conversion from PROFINET IO Device to PROFIBUS DP Master The following steps have to be done to configure the device 2 4 1 Start SYCON net and User Login 1 Start SYCON net gt Select Start gt Programs gt SYCON net System Configurator gt SYCON net 3 SYCON net is started 2 User Login gt In the window SYCON net User Login click OK to login or enter your password and then click OK to login gt SYCON net frame application appears Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 57 268 2 4 2 Insert the Proxy Device into the Configuration Window gt Go to the device catalog under vendor Hilscher GmbH to the category Gateway Stand Alone Slave Use drag and drop with the NT 100 XX XX proxy device to insert it at the gray main line Hil
75. 0x800C002D Timeout during channel initialization CIFX_DEV_BUS_STATE_ON_TIMEOUT 0x800C002E Set Bus ON Timeout CIFX_DEV_BUS_STATE_OFF_TIMEOUT 0x800C002F Set Bus OFF Timeout CIFX_DEV_MODULE_ALREADY_RUNNING 0x800C0040 Module already running CIFX_DEV_MODULE_ALREADY_EXISTS 0x800C0041 Module already exists Table 91 Generic Device Error Codes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010106EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Error Codes 253 268 8 6 Error Codes netX Driver 8 6 1 CIFX API Transport Error Codes Error Code Definition Value Description CIFX_TRANSPORT_SEND_TIMEOUT 0x800D0001 Time out while sending data CIFX_TRANSPORT_RECV_TIMEOUT 0x800D0002 Time out waiting for incoming data CIFX_TRANSPORT_CONNECT 0x800D0003 Unable to communicate to the deviceno answer CIFX_TRANSPORT_ABORTED 0x800D0004 Transfer has been aborted due to keep alive timeout or interface detachment CIFX_CONNECTOR_FUNCTIONS_ READ_ERRO 0x800D0010 Error reading the connector functions from 7 the DLL CIFX_CONNECTOR_IDENTIFIER_TOO_LONG 0x800D0011 Connector delivers an identifier longer than 6 characters CIFX_CONNECTOR_IDENTIFIER_EMPTY 0x800D0012 Connector delivers an empty dentifier CIFX_CONNECTOR_DUPLICATE_IDENTIFIER 0x800D0013 Connector identifier already used Table 92 CIFX API Transport Error Codes
76. 1 10 Device NT 100 RE DP Device ID Jo Vendor Hilscher GmbH Vendor ID 0x011E Navigation area E E Settings E Driver netX Driver Device Assignment F 128 Bytes In lt Slot 1 gt CB_AB32 DPS lt Addr 2 gt QJ Configuration J 128 Bytes Out lt Slot 2 gt J Status Settings tay Signal Mapping Port x2 Signals 4 Data type Port x3 Signals 4 Data type Memory Card Management Licensing Available Signals f ARRA Generated Communication Change of UNSIGNED32 Send 128 InBytes BYTE_0002 Generated Communication State UNSIGNED32 Send 128 InBytes BYTE_0003 Generated Communication Error UNSIGNED32 Send 128 InBytes BYTE_0004 Generated Version UNSIGNED 16 Send 128 InBytes BYTE_0005 Generated Watchdog Timeout UNSIGNED16 Send 128 InBytes BYTE_0006 Generated SlaveConfig 000 007 UNSIGNEDS Send 128 InBytes BYTE 0007 Generated SlaveConfig 008 015 UNSIGNEDS lt Mapped Signals 128 Bytes Out lt Slot 2 gt 128 OutBytes BYTE_0001 CB_AB32 DPS lt Addr 2 gt 2 byte input output lt Slot 1 gt Output_O0 128 Bytes In lt Slot 1 gt 128 InBytes BYTE_0000 CB_AB32 DPS lt Addr 2 gt 2 byte input output lt Slot 1 gt Input_0001 128 Bytes In lt Slot 1 gt 7 128 InBytes BYTE_0001 CB_AB32 DPS lt Addr 2 gt 2 byte input output lt Slot 1 gt Input_O002 Manual Mapping Remove link Auto Mapping off X Figure 91 Signal Mapping The I O mapping is done the following way Data transfer from Port X2 to Port X3 gt Map the si
77. 100 RE EIS Valid IP address Default unchecked Valid network mask Default unchecked Valid gateway address Default unchecked Hilscher 2009 2014 Configuration 131 268 There are three methods available how the device can obtain its IP Address Netmask and Gateway Address one of which must be selected These methods can also be combined The device performs the following sequence in order to obtain the addresses 1 from a DHCP server if DHCP is checked if a DHCP server provides the requested addresses to the device then the device uses these addresses 2 from a BootP server if BootP is checked if a BootP server provides the requested addresses to the device then the device uses these addresses 3 the addresses manually set are used If the IP Address is set manually also the Network Mask must be set manually The manually set Gateway Address is optional If no DHCP server and no BootP server and no manually set addresses exist then the protocol is not ready for initialization or for operation BootP Default unchecked If checked the device obtains its IP Address Netmask Gateway Address from a BOOTP server DHCP Default checked If checked the device obtains its IP Address Netmask Gateway Address from a DHCP server 100Mbit Speed Selection Default unchecked If checked the device will operate at 100 MBit s else at 10 MBit s This parameter will not be in effect when auto negotiation is activ
78. 10l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 68 268 2 4 7 Device Assignment gt Select Settings gt Device Assignment gt Click on Scan The search process is started Devices found are display in a list then J netDevice Proxy netTAP NT 100 RE XX PROXY lt gt 1 e 10 Device NT 100 RE XX PROXY Device ID ao Vendor Hilscher GmbH Vendor ID 0x011E Navigation area E Settings E Driver netX Driver ee Device selection suitable only x Configuration Settings a Device Hardware Ports O 1 Slot nu Serial nu Driver Channel Protocol Access path Memory Card Management NT 100 RE DP Ethernet Ethernet P nja 20060 netX Driver Gateway 4COM3_cif XO Licensing Scan progress 4 4 Devices Current device Access path B54C8CC7 F333 4135 8405 6E 12FC88EE62 COM3_cifxO_Ch2 Cancel Help KE G Save operation succeeded Figure 49 Select Device gt Select the device from the list by a check in the field of the device as shown above gt Click on OK The configuration window closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 69 268 2 4 8 Load Firmware The firmware has to be loaded into the netTAP only for first comm
79. 12010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 226 268 4 26 Configuration Serial with netSCRIPT The netTAP NT 100 device respectively the netBRICK NB 100 device as serial with netSCRIPT needs parameter and beyond a script has to be created and loaded These parameter can be edited as follows 1 Open the configuration dialog gt Select from the context menu of the netTAP respectively the netBRICK symbol the entry Configuration gt netSCRIPT 3 gt The netSCRIPT settings dialog opens 3 In the navigation area the entry Settings under the folder Configuration is selected and the settings dialog is displayed 2 netSCRIPT settings Select in the dialog window the interface type RTS control baudrate number of data bits number of stop bits and parity The settings are described in the following section netSCRIPT Settings on page 227 3 Signal configuration The signal configuration is done with default value automatically by SYCON net software 4 Close configuration dialog Click on OK to save the parameter or click on Cancel if the parameter should not be saved 3 gt The configuration dialog closes Note The programming of a script loading the script into the netTAP or netBRICK device the debugging of the script is described in detail in an own manual netSCRIPT Programming Language for Serial Communication UM xx EN pdf Configuration of Gat
80. 47 Select USB Driver 1 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 4 Select the netXDriver gt Select Settings gt Driver gt netXDriver 3 gt The following figure shows the selected Driver Y netDevice Proxy netTAP NT 100 RE DP PROXY lt gt 1 e IO Device NT 100 RE DP PROXY ao Vendor Hilscher GmbH Navigation area amp Settings I Driver l i netX Driver ersz Connection l TCP Connection Device Assignment E Configuration M Enable USB R5232 Connector Restart of ODM required Settings ender Memory Card Management a comi Licensing Port Configuration I Disable Port Device ID Vendor ID Baud Rate 115 2 kBit s Byte Size 8 Byte Stop Bits 1 Stopbit Parity No Parity Send Timeout 1000 ms Keep Alive Timeout 2000 Reset Timeout 5000 ms 67 268 OxO11E Restore Save Save All Cancel Help Figure 48 Select USB Driver 2 Select the netXDriver Select the tab USB RS232 Connection Check Enable USB RS232 Connector 5 gt gt gt Click on Save Note The standard setting of the netX Driver USB RS232 can be used for netTAP respectively netBRICK devices without changes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC08120
81. 4C030 USER Pointer to send buffer is a null pointer DRV_E_USR_RECVBUF_PTR_NULL 0x8004C031 USER Pointer to receive buffer is a null pointer DRV_E_DMA_INSUFF_MEM 0x8004C032 DMA Memory allocation error DRV_E_DMA_TIMEOUT_CH4 0x8004C033 DMA Read I O timeout DRV_E_DMA_TIMEOUT_CH5 0x8004C034 DMA Write I O timeout DRV_E_DMA_TIMEOUT_CH6 0x8004C035 DMA PCI transfer timeout DRV_E_DMA_TIMEOUT_CH7 0x8004C036 DMA Download timeout DRV_E_DMA_DB_DOWN_FAIL 0x8004C037 DMA Database download failed DRV_E_DMA_FW_DOWN FAIL 0x8004C038 DMA Firmware download failed DRV_E_CLEAR_DB_FAIL 0x8004C039 DMA Clear database on the device failed DRV_E_DEV_NO_VIRTUAL_MEM 0x8004C03C DMA USER Virtual memory not available DRV_E_DEV_UNMAP_VIRTUAL_MEM 0x8004C03D DMA USER Unmap virtual memory failed DRV_E_GENERAL_ERROR 0x8004C046 DRIVER General error DRV_E_DMA_ERROR 0x8004C047 DRIVER General DMA error DRV_E_WDG_IO_ERROR 0x8004C048 DRIVER I O WatchDog failed DRV_E_WDG_DEV_ERROR 0x8004C049 DRIVER Device Watchdog failed DRV_E_USR_DRIVER_UNKNOWN 0x8004C050 USER Driver unknown DRV_E_USR_DEVICE_NAME_INVALID 0x8004C051 USER Device name invalid DRV_E_USR_DEVICE_NAME_UKNOWN 0x8004C052 USER Device name unknown DRV_E_FW_FILE_SIZE_ZERO 0x8004C06F USER Not enough memory to load firmware file DRV_E_FW_FILE_NO_MEMORY 0x8004C070 USER Not enough memory to load firmware file DRV_E_FW_FILENAME NOT FOUND 0x8004C075 USER Firmware file not found in the internal table DRV_E_FW_BOOTLOADER_ACTIVE 0x8
82. 5 8405 6E 12FC83EE62 192 168 60 199 501 1 1 cifx0_Ch2 Lok cme a f o Figure 61 Select Device gt Select the device from the list by a check in the field of the device as shown above gt Click on OK 3 gt The configuration window closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010I06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 83 268 2 5 8 Load Configuration 1 Download configuration gt Select from the context menu of the proxy device symbol the entry Download gt Answer the security question with Yes if the download should start gt The configuration is transferred info the proxy device 3 gt The device performs a reset and then starts with the new configuration Note The device performs a reset after the download Because of that the Ethernet connection gets lost and has to be stopped from SYCON net and then has to be established again Stop the online connection to the device which was established automatically to the device before gt Select from the context menu of the proxy device symbol the entry Disconnect gt To establish a connection again do the steps described in section Device Assignment on page 68 2 5 9 Save Project gt Note The configuration downloaded from SYCON net into the device can t be uploaded from the device Only the SYCON net
83. 812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 115 268 4 4 Signal Mapping The signal mapping determines which user data of the primary network are assigned to which user data of the secondary network and vice versa The signal mapping is relevant for the gateway devices netTAP NT 50 NT 100 und netBRICK NB 100 The mapping of the data for gateway devices can be done by the user und be configured within SYCON net The mapping of data is already specified for proxy devices and done automatically by SYCON net With the mapping for gateway devices e the received data from the primary network are mapped to the send data of the secondary network e the received data from the secondary network are mapped to the send data of the primary network e status information of the primary network is mapped to the send data of the secondary network e status information of the secondary network is mapped to the send data of the primary network With this mapping a device internal list in generated The device work each x ms through this list and copies the data Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 116 268 On the pane I O Data Mapping you can map the I O Data of port X2 to the I O data of port X3 a netDevice Gateway netTAP NT 100 RE DP lt gt
84. 9 DRIVER Error during PCI set run mode DRV_E_DEV_DPM_ACCESS ERROR 0x8004C00A DEVICE Dual port ram not accessable board not found DRV_E_DEV_NOT_READY 0x8004C00B DEVICE Not ready ready flag failed DRV_E_DEV_NOT_RUNNING 0x8004C00C DEVICE Not running running flag failed DRV_E_DEV_WATCHDOG_FAILED 0x8004C00D DEVICE Watchdog test failed DRV_E_DEV_OS VERSION ERROR 0x8004CO0E DEVICE Signals wrong OS version DRV_E_DEV_SYSERR 0x8004C00F DEVICE Error in dual port flags DRV_E_DEV_MAILBOX_FULL 0x8004C010 DEVICE Send mailbox is full DRV_E_DEV_PUT_TIMEOUT 0x8004C011 DEVICE PutMessage timeout DRV_E_DEV_GET_TIMEOUT 0x8004C012 DEVICE GetMessage timeout DRV_E_DEV_GET_NO_ MESSAGE 0x8004C013 DEVICE No message available DRV_E_DEV_RESET_TIMEOUT 0x8004C014 DEVICE RESET command timeout DRV_E_DEV_NO_COM_FLAG 0x8004C015 DEVICE COM flag not set Check if Bus is running DRV_E_DEV_EXCHANGE_FAILED 0x8004C016 DEVICE I O data exchange failed DRV_E_DEV_EXCHANGE_TIMEOUT 0x8004C017 DEVICE I O data exchange timeout DRV_E_DEV_COM_MODE_UNKNOWN 0x8004C018 DEVICE I O data mode unknown DRV_E_DEV_FUNCTION_FAILED 0x8004C019 DEVICE Function call failed DRV_E_DEV_DPMSIZE_MISMATCH 0x8004C01A DEVICE DPM size differs from configuration DRV_E_DEV_STATE_MODE_UNKNOWN 0x8004C01B DEVICE State mode unknown DRV_E_DEV_HW_PORT_IS_USED 0x8004C01C DEVICE Output port already in use DRV_E_USR_OPEN_ERROR 0x8004C01E USER Driver not opened device driver not loaded DRV_E_USR_INIT_DRV_ERROR 0x8004C01F USER Can
85. AB Device not ready CODM3_E_ DRV_INVALIDCONFIGURATION 0x8004C7AC Invalid driver configuration CODM3_E_ DRV_DLINVALIDMODE 0x8004C7C0 Invalid download mode CODM3_E_ DRV_DLINPROGRESS 0x8004C7C1 Download is active CODM3_E_ DRV_ULINPROGRESS 0x8004C7C2 Upload is active Table 87 ODM Error Codes General ODM Driver Error Codess Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010106EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Error Codes 247 268 8 4 3 cifX Driver Specific ODM Error Codes cifX Driver Specific ODM Error Codes Error Code Definition Value Description DRV_E_BOARD_NOT_INITIALIZED 0x8004C001 DRIVER Board not initialized DRV_E_INIT_STATE_ERROR 0x8004C002 DRIVER Error in internal init state DRV_E_READ_STATE_ERROR 0x8004C003 DRIVER Error in internal read state DRV_E_CMD_ACTIVE 0x8004C004 DRIVER Command on this channel is active DRV_E_PARAMETER_UNKNOWN 0x8004C005 DRIVER Unknown parameter in function DRV_E_WRONG_DRIVER_VERSION 0x8004C006 DRIVER Version is incompatible with DLL DRV_E_PCI_SET_CONFIG_MODE 0x8004C007 DRIVER Error during PCI set configuration mode DRV_E_PCl_READ_DPM_LENGTH 0x8004C008 DRIVER Could not read PCI dual port memory length DRV_E_PCl_SET_RUN_MODE 0x8004C00
86. B 100 device as PROFIBUS DP Slave needs parameter These parameter can be edited as follows 1 Open the configuration dialog gt Select from the context menu of the netTAP respectively the netBRICK symbol the entry Configuration gt PROFIBUS DP Slave The PROFIBUS DP Slave configuration dialog opens 3 In the navigation area the entry Configuration under the folder Configuration is selected and the configuration dialog is displayed 2 Set station address Enter in the field Station address the address which the netTAP or netBRICK device uses on the PROFIBUS network to be addressed by the PROFIBUS DP Master 3 Set baudrate Use the setting Auto Detect default if the netTAP or netBRICK device should detect the baudrate on the PROFIBUS network or set the baud rate for the device 4 Set the number of input and output data Enter for the output module type and size of the output module Up to 4 output modules can be set With the output modules the number of data is configured which the netTAP or netBRICK device should receive from the PROFIBUS DP Master gt Enter for the input module type and size of the input module Up to 4 input modules can be set With the input modules the number of data is configured which the netTAP or netBRICK device should send to the PROFIBUS DP Master Note The input and output modules are with consistence Configuration of Gateway and Proxy Devices netTAP netBRICK and netLIN
87. B 100 RE XX 00000044_NB 100 RE PLS XDD Table 30 XDD File Names for netTAP and netBRICK Configuration Note The settings in the used Managing Node must comply with the settings in the Controlled Node to establish communication Important parameters are Vendor ID Product Code Serial Number Revision Number Node ID Output and Input length In order that the POWERLINK Managing Node can communicate with the netTAP or netBRICK device as POWERLINK Controlled Node gt Enter at the POWERLINK Managing Node the Node ID which is configured in the netTAP or netBRICK device gt Enter for the length of output data in the POWERLINK Managing Node as set in the netTAP or netBRICK device for the Output Data Bytes gt Enter for the length of input data in the POWERLINK Managing Node as set in the netTAP or netBRICK device for the Input Data Bytes gt The POWERLINK Managing Node verifies identification numbers of the netTAP or netBRICK device as POWERLINK Controlled Node Use or check for the following values for the netTAP or netBRICK device vendor 68 0x44 serial number 0 product code 24 0x18 for NT 100 respectively product code 23 0x17 for NB 100 revision number 0 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 152 268 4 12 Configuration PROFINET IO Controller The netTAP NT 50 NT 1
88. C 124 1D 29 GS 3D 61 5D 93 7D 125 1E 30 RS 3E 62 gt 5E 94 A 7E 126 1F 31 US 3F 63 5F 95 B 7F 127 DEL Table 62 ASCII Character Table Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010106EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 216 268 4 25 2 2 Size of the Send and Receive Buffer The size of the send or receive buffer is configured Note The send telegram must fit into the send buffer The receive telegram must fit into the receive buffer Sendbuffer Size Size of the send buffer in bytes 0 1024 Default 512 Bytes Receivebuffer Size Size of the receive buffer in bytes 0 1024 Default 512 Bytes Table 63 Size of the Send and Receive Buffer 4 25 2 3 Operating Modes and Timing The modes are e Receive Only Mode e Send Only Mode e Client Mode first send then receive e Server Mode first receive then send Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010106EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 217 268 4 25 2 4 Send Only Mode Basic Principle In the Send Only mode the device only sends The remote device only receives The superordinated control unit has to use a handshake to transfer the data to the device Communication The send operation can be
89. CHER NT 50 EN EIS V1 1 EDS NT 100 RE XX HILSCHER NT 100 RE EIS V1 1 EDS NB 100 RE XX HILSCHER NB 100 RE EIS V1 1 EDS Table 19 EDS File Names for netTAP and netBRICK Configuration Note The settings in the used Scanner must comply with the settings in the Adapter to establish a communication Important parameters are Input Output length Vendor ID Product Type Product Code Major Rev Minor Rev IP Address and Netmask In order that the EtherNet IP Scanner can communicate with the netTAP or netBRICK device as EtherNet IP Adapter gt Enter at the EtherNet IP Scanner the IP address of the netTAP or netBRICK device gt Use at the EtherNet IP Scanner the instance ID 101 to receive data from the netTAP or netBRICK device gt Enter at the EtherNet IP Scanner for this instance ID 101 the number of data number of receive data bytes which were configured in the netTAP or netBRICK device e g 64 Note Some EtherNet IP Scanners need for setting this value number of receive data a value increased by 4 this is the length of the Run Idle header that can be transferred in front of the user data With the example of 64 bytes above therefore 68 64 4 needs to be set for the number of data gt f adjustable at the EtherNet IP Scanner set that the EtherNet IP Scanner sends the 32 Bit Run Idle header gt Use at the EtherNet IP Scanner the instance ID 100 to send data to the netTAP or netBRICK device
90. Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010I06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 24 268 3 Select the protocol for the primary network and for the secondary network and apply gt Select in the window Configuration gt Settings at Protocol Combinations for the Primary Network Port X2 the protocol PROFIBUS DP Slave gt Select then at Protocol Combinations for the Secondary Network Port X3 the protocol Modbus RTU gt Click Apply The Gateway configuration window shows the following J netDevice Gateway netTAP NT 50 XX XX lt gt 1 10 Device NT 50 XX xXx Device ID Vendor Hilscher GmbH vendor ID OxO11E Navigation area Ca E Settings General 9 Driver netX Driver Description netTAP Device Assignment E Configuration tay Settings Signal Mapping Protocol Combinations Primary network Port X2 PROFIBUS DP Slave Secondary network Port X3 Modbus RTU Required gateway NT 50 DP RS x Required license None Available Firmware NSDPSMBR NXF Browse wwe ansa Software class Multi protocol combinable Gateway Software version ESN Basic Settings Mapping Cycle time Mapping mode Network Address Switch Enable Used by Figure 9 Gateway Protocol Selection 2 The Required gateway as shown above depends on the selected protocols
91. DPL proxy device support communication only to one PROFIBUS DP Slave device Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 75 268 2 5 4 3 Configure the PROFIBUS DP Slave device gt Open the configuration window with a double click on the device icon of the PROFIBUS DP Slave 3 gt The configuration window of the PROFIBUS DP Slave device opens gt Select in the navigation area Configuration gt Modules gt Select from Available Modules the module s and add it them to the Configured Modules to configure the Slave The Configured Modules has to match the configuration of the used PROFIBUS DP slave device More information about the configuration of PROFIBUS DP Slave devices are in the document PROFIBUS Generic_Slave DTM_en pdf on the product DVD in section Configuration A 2 5 4 4 Configure PROFIBUS DP Master 1 Open the PROFIBUS DP Master configuration window gt Select from the context menu of the proxy device symbol the entry Configuration gt PROFIBUS DP Master 3 The PROFIBUS DP Master configuration window opens yr netDevice PROFIBUS DP Master netLINK NL 51N DPL lt gt 1 DER 10 Device NL S1N DPL Device ID Ox0B44 5 vendor Hilscher GmbH Vendor ID 0x011E Navigation rea 4 Configuration m Bus Parameters Profile PROFIBUS DP v P
92. Description CIFX_DEV_DPM_ACCESS_ ERROR 0x800C0010 Dual port memory not accessable board not found CIFX_DEV_NOT_READY 0x800C0011 Device not ready ready flag failed CIFX_DEV_NOT_RUNNING 0x800C0012 Device not running running flag failed CIFX_DEV_WATCHDOG_FAILED 0x800C0013 Watchdog test failed CIFX_DEV_SYSERR 0x800C0015 Error in handshake flags CIFX_DEV_MAILBOX_FULL 0x800C0016 Send mailbox is full CIFX_DEV_PUT_TIMEOUT 0x800C0017 Send packet timeout CIFX_DEV_GET_TIMEOUT 0x800C0018 Receive packet timeout CIFX_DEV_GET_NO_PACKET 0x800C0019 No packet available CIFX_DEV_MAILBOX_TOO_SHORT Ox800C001A Mailbox too short CIFX_DEV_RESET_TIMEOUT 0x800C0020 Reset command timeout CIFX_DEV_NO_COM_FLAG 0x800C0021 COM flag not set CIFX_DEV_EXCHANGE_FAILED 0x800C0022 IO data exchange failed CIFX_DEV_EXCHANGE_TIMEOUT 0x800C0023 IO data exchange timeout CIFX_DEV_COM_MODE_UNKNOWN 0x800C0024 Unknown IO exchange mode CIFX_DEV_FUNCTION_FAILED 0x800C0025 Device function failed CIFX_DEV_DPMSIZE_MISMATCH 0x800C0026 DPM size differs from configuration CIFX_DEV_STATE_MODE_UNKNOWN 0x800C0027 Unknown state mode CIFX_DEV_HW_PORT_IS_USED 0x800C0028 Device is still accessed CIFX_DEV_CONFIG_LOCK_TIMEOUT 0x800C0029 Configuration locking timeout CIFX_DEV_CONFIG_UNLOCK_TIMEOUT 0x800C002A Configuration unlocking timeout CIFX_DEV_HOST_STATE_SET_TIMEOUT 0x800C002B Set HOST state timeout CIFX_DEV_HOST_STATE_CLEAR_TIMEOUT 0x800C002C Clear HOST state timeout CIFX_DEV_INITIALIZATION_ TIMEOUT
93. FC2 2000 Coils FC3 125 Registers FC4 125 Registers FC5 1 Coils FC6 1 Registers FC15 1968 Coils FC16 123 Registers Memory Address internal Byte address in the process image of the Open Modbus TCP Client device for input or output data of the Client The configuration software calculates the byte address in the process image of the Client for the input or for the output data automatically Because of this definition for function codes for reading FC 1 2 3 and 4 the data are assigned consecutively in the process image for input data and for function codes for writing FC 5 6 15 and 16 the data are assigned consecutively in the process image for output data 0 5759 Default 0 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 140 268 Parameter Meaning Range of Value Value Trigger Cycle Time Defines for all function codes for writing FC 5 6 15 and 16 if the command is to be executed cyclically Cyclic or only if the data have changed Change Data For function codes for reading FC 1 2 3 und 4 this parameter is not used The cycle time defines after how many milliseconds a writing or a reading command shall be reexecuted The default value 0 ms means that the command is executed as fast as possi
94. IBUS Master e PROFINET IO RT Controller e SERCOS III Master 4 3 3 2 License for Utilities e SYCON net e OPC Server e QVis Minimum Size e QVis Standard Size e QVis Maximum Size e CoDeSys Minimum Size e CoDeSys Standard Size e CoDeSys Maximum Size For the utilities QVis and CoDeSys only one license each may be chosen alternatively as e Minimum Size e Standard Size or e Maximum Size Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 106 268 4 3 4 How to order a License To order a license proceed as follows oe De Refer to Section Page Open the license dialog Open License Dialog 102 Select the required licenses Selecting License 106 Enter the ordering data Ordering Data 107 Place your order Ordering the License 109 4 3 5 Selecting License s You can select licenses for Master protocols and or utilities 1 gt gt Selecting license s for Master protocol s Under License Type click I at Master protocols in the License pane Under Order check as many licenses must run simultaneously on your device One General Master License or Two General Master Licenses And or select license s for utility utilities In the License pane under License Type click at Utilities Under Order check the required utility utilities single or several
95. ICE_SUBSCRIPTIONLIMIT 0x8004C75B Maximum number of servers registered for this device reached CODM3_E_ DEVICE_NOTSUBSCRIBED 0x8004C75C Process is not registered as a server on this device CODM3_E_DEVICE_NO_MESSAGE 0x8004C75D No message available CODM3_E_TRANSFERTIMEOUT 0x8004C760 CODM3_E_MESSAGE_INSERVICE 0x8004C761 Table 86 ODM Error Codes General ODM Error Codes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Error Codes 246 268 8 4 2 General ODM Driver Error Codes Error Code Definition Value Description CODM3_E DRV_OPEN_DEVICE 0x8004C7A0 Packet type unsupported by driver CODM3_E_ DRV_INVALID_IDENTIFIER 0x8004C7A1 Invalid device identifier CODM3_E_ DRV_DEVICE_PARAMETERS _ 0x8004C7A3 Parameters differ from requested device MISMATCH CODM3_E_ DRV_BROWSE_NO_DEVICES 0x8004C7A4 No devices found CODM3_E_ DRV_CREATE_DEVICE_INST 0x8004C7A5 Device instance could not be created CODM3_E_ DRV_DEVICE_NOMORE_TX 0x8004C7A6 Device connection limit reached CODM3_E_ DRV_DEVICE_DUPLICATE_TX 0x8004C7A7 Duplicate transmitter ID CODM3_E_ DRV_DEVICE_NOT_CONFIGURED 0x8004C7A8 Device is not configured CODM3_E_ DRV_DEVICE_COMMUNICATION 0x8004C7A9 Device communication error CODM3_E_ DRV_DEVICE_NO_MESSAGE 0x8004C7AA No message available CODM3_E_ DRV_DEVICE_NOT_READY 0x8004C7
96. K DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 186 268 5 Set more parameter If necessary set more parameter The parameter are described in the following section PROFIBUS DP Slave Parameter on page 187 Note Default values can be used normally for the other parameters Depending on additionally requirements and the design of the PROFIBUS network as well as the used devices parameters needs to be adjusted if necessary Open the signal configuration dialog Select in the navigation area under the folder Configuration the entry Signal Configuration The signal configuration dialog opens Signal configuration If you want to assign own signal names then enter your signal names Further information is described in section Signal Configuration on page 228 Close configuration dialog Click on OK to save the parameter or click on Cancel if the parameter should not be saved The configuration dialog closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 187 268 4 22 1 PROFIBUS DP Slave Parameter Bus Startup Automatic communication start Automatic Default Watchdog Time This function is not supported by gateway or proxy devices 0 20 65535 ms default 1000 ms 0 Off I O Data Status Status of the input
97. LINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 72 268 2 5 Configuration of a NL 51N DPL as Proxy The netLINK Proxy NL 51N DPL device can be used for the protocol conversion from PROFINET IO Device to PROFIBUS DP Master with proxy functionality The device can communicate to one PROFIBUS DP Slave device The following sections describe how to configure the device 2 5 1 Requirement for the Configuration The device is configured via the Ethernet port Therefore it is necessary that the device gets an IP address assigned before Therefore do the followings steps 1 Establish an Ethernet connection between the Ethernet network port of your PC and the Ethernet port of the NL 51N DPL Start the Ethernet Device Setup software Therefore select Start gt Programs gt SYCON net System Configurator gt Ethernet Device Setup Search for connected devices Therefore click on Search Devices Devices are searched in the local network using broadcast telegrams Assign an IP address to the NL 51N DPL device which should be used for the device configuration This address can be stored in a non volatile memory of the device xy Note Use the IP address which is later assigned by the PROFINET IO Controller that you can use SYCON net for diagnostic later 2 5 2 Start SYCON net and User Login 1 gt Start SYCON net S
98. M to a netTAP NT 100 device Under Settings in the Driver pane 1 Verify that the default driver is checked and respectively check another or multiple drivers 2 Configure the driver if necessary Under Settings in the Device Assignment pane 1 Scan for the device 2 Select the device and apply the selection 3 Inthe DTM interface dialog select the OK button to apply the selection and to close the DTM interface dialog 4 Puta right click on the netTAP symbol Select the Connect command from the right mouse button menu The netTAP NT 100 device now is connected to the netGateway DTM via an online connection In the network view the device description at the device symbol is displayed with a green colored background on Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Online Functions 234 268 Disconnecting Device To disconnect an online connection from the netTAP NT 100 device to a netGateway DTM take the following steps 3 In the DTM interface dialog select the OK button to close the DTM interface dialog 1 Right click on the netTAP symbol Select the Disconnect command from the context menu Now the netTAP NT 100 device is disconnected from the DTM M Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Pu
99. P Disconnected T Data Set Figure 56 PROFINET IO Device Table Here the modules with its slot number and sub slot number are displayed as they will become visible at the PROFINET IO Controller These slot numbers and sub slot numbers will be exported into the GSDML file which is described later Slot 0 NL51N DPL and slot 1 NL51N PROFIBUS DP are always present An additional slot slot 2 in this case which represent the PROFIBUS DP Slave with station address 2 is automatically displayed when a PROFIBUS DP Slave was inserted to the PROFIBUS DP network These Slot and sub slot numbers are used in the GSDML file The GSDML file can be created exported which is described later Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 78 268 2 Set the name of station gt Select in the navigation area General 3 gt The following configuration window opens va netDevice PROFINET IO Device netLINK NL 51N DPL lt gt 1 IO Device NL S1N DPL Device ID 0x0110 5 Vendor Hilscher GmbH Vendor ID 0x011E Navigation Area EQ E Configuration a ceneral Name of station Modules Address Table Description NL_51N DPL E Description Device Info IP settings Module Info GSDML Viewer IP address p SSS Note These values are set by Network mask the controller of the n
100. P NT 100 devices Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 41 268 2 Open dialog for protocol selection gt Select in the Navigation area Configuration gt Settings gt The configuration window Settings opens gt netDevice Gateway netTAP NT 100 XX XX lt gt 1 IO Device NT 100 XX xx Device ID ao Vendor Hilscher GmbH Vendor ID 0x011E Navigation area A 2 Settings General 9 Driver netX Driver Description netTAP Device Assignment J Configuration gt Es P oo oo Signal Mapping Primary network Port X2 v Secondary network Port x3 p Memory Card Management Required gateway o Licensing Protocol Combinations Required license Available Firmware NTCOMASC NXF Browse NTCOMCCS NXF NTCOMCOS NXF NTCOMDNS NXF NTCOMDPS NXF NTCOMMBR NXF Software class Software version Basic Settings Mapping Cycle time 1 ms Mapping mode Network Address Switch Enable ja Used by Cancel Help Figure 24 Gateway Protocol Selection 1 The entry Memory Card Management in the navigation area is only available for net TAP NT 100 devices Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configurati
101. RCX_E_SEC_READ_ FAILED 0xC02B002B Security EEPROM Read Failed RCX_E_SEC_WRITE_FAILED 0xC02B002C Security EEPROM Write Failed RCX_E_SEC_ACCESS_ DENIED 0xC02B002D Security EEPROM Access Denied RCX_E_SEC_EEPROM_EMULATED 0xC02B002E Security EEPROM Emulated RCX_E_INVALID_ BLOCK 0xC02B0038 Invalid Block RCX_E_INVALID_ STRUCT_NUMBER 0xC02B0039 Invalid Structure Number RCX_E_INVALID_ CHECKSUM 0xC02B4352 Invalid Checksum RCX_E_CONFIG_LOCKED 0xC02B4B54 Configuration Locked RCX_E_SEC_ZONE_ NOT READABLE 0xC02B4D52 Security EEPROM Zone Not Readable Table 82 RCX General Task Errors Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010106EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Error Codes 8 3 2 RCX Common Status amp Errors Codes 243 268 Error Code Definition Value Description RCX_S_OK 0x00000000 Success Status Okay RCX_E_FAIL 0xC0000001 Fail RCX_E_UNEXPECTED 0xC0000002 Unexpected RCX_E_OUTOFMEMORY 0xC0000003 Out Of Memory RCX_E_UNKNOWN_COMMAND 0xC 0000004 Unknown Command RCX_E_UNKNOWN_DESTINATION 0xC0000005 Unknown Destination RCX_E_UNKNOWN_DESTINATION_ID 0xC0000006 Unknown Destination ID RCX_E_INVALID_ PACKET_LEN 0xC0000007 Invalid Packet Length RCX_E_INVALID_EXTENSION 0xC0000008 Invalid Extension RCX_E_INVALID_ PARAMETER 0xC0000009 Invali
102. RICK device then you can use the SDDML file listed above If you have set at least one setting a different value than the default value then you have to export the device description file from SYCON net and import it into the configuration software of the sercos Master Configuration Note The settings in the used Master must comply with the settings in the Slave to establish communication Important parameters are sercos address vendor code Device ID FSP type with value IO V1 SCP configuration type with value FixCFG the output data size and the input data size Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 167 268 4 16 Configuration CANopen Master The netTAP NT 50 NT 100 device respectively the netBRICK NB 100 device as CANopen Master needs a configuration e g information about how many CANopen Slave devices with how many input and output data are to be connected 1 Insert CANopen Slave devices gt Drag from the device catalog CANopen Slave device s and drop it to the bus line of the CANopen Master 2 Configure CANopen Slave devices gt Open the configuration dialog for each CANopen Slave device and configure the device Information about how to configure the CANopen Slave device is in the operating instruction manual Generic DTM for CANopen Slave devices and has the f
103. Receive Receive Send i Send Communication When configuring the telegram structure the method is defined how the end of the telegram is detected e Character e Length e Time Timing Parameter Parameter Description Range of Value Receive Specifies whether the reception of subsequent telegrams is monitored by time Watchdog Thereby the remote device can be monitored The time is taken from telegram end to Default 0 Time telegram end The value unequal to zero specifies in what time the remote device must have sent the next telegram If the time is exceeded then an error is reported to the host The value 0 specifies that the reception of subsequent telegrams is not monitored Response Specifies whether the reception of telegrams is monitored by time Thereby the Timeout remote device can be monitored The time is taken from the end of the send telegram Default 1000 to the start of the receive telegram The value unequal to zero specifies in what time the remote device must have sent the next telegram If the time is exceeded then an error is reported to the host The value 0 specifies that the reception of telegrams is not monitored Character Specifies whether the time between two characters during reception is monitored by 0 2 1 Delay Time time Default 0 The value unequal to zero specifies in what time the remote device must have sent the next character If the time is exceeded then an error is report
104. STATE_OK 0x00000001 OK RCX_SLAVE_STATE_FAILED 0x00000002 FAILED at least one slave Table 85 RCX Status amp Error Codes Slave State Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010106EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Error Codes 245 268 8 4 ODM Error Codes 8 4 1 General ODM Error Codes ODM3_E_ DESCRIPTION _NOTFOUND 0x8004C701 Description not found in ODM database CODM3_E_ COMCATEGORIE_MANAGER_ 0x8004C712 Component Category Manager could not FAILED be instantiated CODM3_E_ COMCATEGORIE_ENUMERATION__ 0x8004C713 Driver could not be enumerated by the FAILED Category Manager CODM3_E CREATE _DEVICE_THREAD_STOP_ 0x8004C751 Error creating device thread stop event EVENT CODM3_E_CLIENT_NOT_REGISTERED 0x8004C752 Client is not registered at the ODM CODM3_E NO MORE_CLIENTS 0x8004C753 Maximum number of clients reached CODM3_E_ MAX_CLIENT_CONNECTIONS _ 0x8004C754 Maximum number of client connections REACHED reached CODM3_E_ENTRY_NOT_FOUND 0x8004C755 Driver device not found CODM3_E DRIVER_NOT_FOUND 0x8004C757 The requested driver is unknown to the ODM CODM3_E DEVICE_ALREADY_LOCKED 0x8004C758 Device is locked by another process CODM3_E_ DEVICE_UNLOCKED_FAILED 0x8004C759 Device could not be unlocked lock was set by another process CODM3_E_ DEVICE_LOCK_NECCESSARY 0x8004C75A Operation requires a device lock to be set CODM3_E_ DEV
105. Slaves UNSIGNED32 Generated Host Watchdog UNSIGNED32 Generated Slave Error Log Indicator UNSIGNED32 Generated Slave State UNSIGNED32 Generated Version UNSIGNED16 Generated Watchdog Timeout UNSIGNED16 Generated Figure 92 Status information of the Master Signals 4 Data type Port x2 Communication Change of State UNSIGNED32 Generated Communication Error UNSIGNED32 Generated Communication State UNSIGNED32 Generated Error Count UNSIGNED3S2 Generated Error Log Indicator UNSIGNED32 Generated Host Watchdog UNSIGNED32 Generated version UNSIGNED16 Generated Watchdog Timeout UNSIGNED16 Generated Figure 93 Status information of the Slave Some status information belong to the master firmware and to the slave firmware status and are marked with Master and Slave others belong only to the master firmware status and are marked with Master Number of Active Slaves Master The firmware maintains a list of slaves within the remote network to which the remote network s master has successfully opened a connection Ideally the number of active slaves is equal to the number of configured slaves This field holds the number of active slaves Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 119 268 Communication Change of State Master and Slave The communication change of state registe
106. T 100 device a netBRICK NB 100 device respectively a netLINK proxy device where at least a base firmware has to be loaded in the device Installed FDT DTM V 1 2 compliant frame application Loaded DTM in the Device Catalog of the FTD Framework For more information to the hardware installation please refer to the corresponding User Manual of your device Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Introduction 14 268 1 4 Dialog Structure of the netGateway DTM The graphical user interface of the DTM is composed of different areas and elements listed hereafter 1 A header area containing the General Device Information 2 The Navigation Area area on the left side 3 The Dialog Pane main area on the right side 4 OK Cancel Apply Help 5 The Status Line containing information e g the online state of the DTM General Device Information Navi gation Area Dialog Pane OK Cancel Apply Help Status Line Figure 1 Dialog Structure of netGateway DTM Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Introduction 15 268 1 4 1 General Device Information Parameter meaning Oo Vendor name of the device Identification number of the device Vendor ID Identification number of the ve
107. T Master The netTAP NT 100 device respectively the netBRICK NB 100 device as EtherCAT Master needs a configuration e g information about how many EtherCAT Slave devices with how many input and output data are to be connected 1 Insert EtherCAT Slave devices gt Drag from the device catalog EtherCAT Slave device s and drop it to the bus line of the EtherCAT Master 2 Configure EtherCAT Slave devices gt Open the configuration dialog for each EtherCAT Slave device and configure the device Information about how to configure the EtherCAT Slave device is in the operating instruction manual Generic DTM for EtherCAT Slave devices and has the file name EtherCAT_GenericSlave_DTM_en pdf respectively open in the configuration dialog of the slave the online help by the F1 key 3 Configure EtherCAT Master Select from the context menu of the netTAP respectively the netBRICK symbol the entry Configuration gt EtherCAT Master Information about how to configure the EtherCAT Master device is in the operating instruction manual DTM for EtherCAT Master devices and has the file name EtherCAT Master DTM_en pdf respectively open in the configuration dialog of the master the online help by the F1 key Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 124 268 4 7 Configuration EtherCAT Slave The
108. TAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 188 268 Output Module or for output modules Input for input modules Type Byte Default Byte or Word Word each with consistency Size 0 1 2 3 4 8 12 The number of Bytes or Words in the module 16 20 32 64 Byte Words Output Data Total of the output bytes of the modules 1 to 4 0 244 Default 2 Bytes Input Data Total of the input bytes of the modules 5 to 8 0 244 Default 2 Bytes Custom data Custom data Default unchecked If unchecked the field Configuration Data shows the output and input identifier bytes which results from the settings of the output modules and input modules If checked the field Configuration Data is editable Output and input identifier bytes can be entered into the Configuration Data field to configure the device Then the settings of the output modules and input modules have no meaning Configuration Configuration data for the output and input identifier bytes Default A1 91 hex Data The identifier bytes consists of the Type and the Size The identifier bytes are the general identifier bytes according to the PROFIBUS standard Depending on the setting of the field Custom data the field Configuration data is for display only or an entry field Table 45 Parameters PROFIBUS DP Slave Part 2 Note The input and output modul
109. Table 89 Table 90 Table 91 Table 92 Table 93 Table 94 Table 95 Table 96 3964R Parameter Part 1 3964R Parameter Part 2 ASCII Parameter ASCII Telegram Structure Example Telegram Structure Parameter Types ASCII Character Table Size of the Send and Receive Buffer Timing Parameters for the Operating Send Only Mode Telegram Structure for the Operating Send Only Mode Timing Parameters for the Operating Receive Only Mode Telegram Structure for the Operating Receive Only Mode Timing Parameters for the Operating Mode Client Mode Telegram Structure for the Operating Mode Client Mode Timing Parameters for the Operating Mode Server Mode Telegram Structure Parameters for the Operating Mode Server Mode netSCRIPT Settings Explanations to the Dialog Pane Signal Configuration Descriptions of the Diagnosis Panes Indication General Diagnosis Parameter General Diagnosis Description Table Task Information PROFINET IO PROFIBUS Address Mapping of acyclic Data PROFINET IO PROFIBUS DP Error Codes PROFINET IO PRPFIBUS Mapping of Alarms Overview Error Codes and Ranges RCX General Task Errors RCX Common Status amp Errors Codes RCX Status amp Error Codes RCX Status amp Error Codes Slave State ODM Error Codes General ODM Error Codes ODM Error Codes General ODM Driver Error Codess cifX Driver Specific ODM Error Codes Generic Error Codes Generic Driver Error Codes Generic De
110. The NT 100 device respectively the netBRICK NB 100 device as 3964R needs parameter These parameter can be edited as follows 1 gt Open the configuration dialog Select from the context menu of the netTAP respectively the netBRICK symbol the entry Configuration gt 3964R The 3964R settings dialog opens In the navigation area the entry Settings under the folder Configuration is selected and the settings dialog is displayed 3964R settings Select or set in the dialog window at least the interface type RTS control baudrate number of data bits number of stop bits parity and conflict priority The settings are described in the following section 3964R Settings on page 206 Note Please note that the conflict priority one device must have high priority the other device must have low priority 3 4 gt Signal configuration The signal configuration is done with default value automatically by SYCON net software Close configuration dialog Click on OK to save the parameter or click on Cancel if the parameter should not be saved The configuration dialog closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 206 268 4 24 1 3964R Settings Bus Startup Communication start application controlled or automatic Default Automatic Watchdog Time ms _ This
111. USB interface The devices netTAP NT50 and netLINK NL51N DPL are configured via an Ethernet interface of the device or diagnosis is performed via the Ethernet interface Therefore a driver is necessary The Driver dialog pane displays the driver s to be used for a connection from the gateway DTM to the device _ Driver version ID O CIFX Device Driver 1 0 3 2 368BECSB 0E92 4COE B449 64F624E744F4 O nets Driver 0 9 1 2 787CD349 4CF6 4259 8E4D 109B646BE491 Figure 65 Driver Selection List Parameter Meaning O Name of the driver Version of the driver iD ID of the driver driver identification Table 8 Driver Selection List Parameters 3 2 1 Selecting the Driver To establish a connection you need to select a driver first Note Not all the drivers displayed necessarily support the device The used driver must be supported by the device or must be available for the device Use the netX Driver for the devices NT 50 NT 100 NB 100 and NL 51N DPL To select the driver s to be used 1 Select Settings gt Driver in the navigation area The available drivers are listed on the Driver dialog pane _ Driver Version O CIFX Device Driver 1 0 3 2 368BECSB 0E92 4COE B449 64F624E744F4 O netX Driver 0 9 1 2 787CD349 4CF6 4259 8E4D 109B646BE491 Figure 66 Driver Selection List recognized or installed Drivers 2 Check the checkbox for the driver s in the selection list Driver Version Jo S S O
112. W_WRITEREGISTRY 0X8004C812 Error writing to the registry CDBM_E_UNEXPECTED_VALUE_ 0XC004C813 Error in a file containing the old DBM IN_OLD_HEADER_FORMAT Header format CDBM_E_CHECKSUM_INVALID 0XC004C814 The Checksum of the old Header is invalid CDBM_E_DB_ALREADY_LOADED_ FORMAT 0XC004C815 A database is already loaded CDBM_E_NO_VALID_TRANSACTION 0XC004C816 No valid transaction handle given CDBM_E_STD_STRUCT_ERROR 0XC004C817 An error occurred during validation of data CDBM_E_UNSUPPORTED_ 0XC004C818 Unsupported DataType DATA_TYPE_FORMAT CDBM_W_CLASS_DELETED_ FORMAT 0X8004C819 Using an Object which is marked as Warning deleted CDBM_W_CLIENT_DISCONNECTED 0X8004C81A A Client has already an outstanding Warning connection to a Table The connection is now destroyed CDBM_E_STRUCTURE_DEFINITION_ INVALID 0XC004C81B A structure definition of an Element in a Table is invalid CDBM_E_NO_DATA_AVAILABLE 0XC004C81C No data available for this operation CDBM_E_NO_VALID_STRUCTURE 0XC004C81D No valid structure available for this operation CDBM_E_NO_TOGGLE_STRING_ FOUND OXC004C81E No Toggle string found for this number CDBM_E_ELEMENT_OUT_OF_RANGE 0XC004C81F An element wasn t found in the Record of a Table CDBM_E_ELEMENT_NOT_IN_ TABLE 0XC004C820 The element is not part of the Table CDBM_E_ CANNOT CONVERT _ 0XC004C821 The data can t be converted into the Client INTO_CLIENT_TYPE type CDBM_E_TRANSACTION_ ALREADY_OPEN 0XC004C822 A transaction is already open Please close
113. X Driver tries to establish a connection using the configured TCP IP interface checked unchecked Default Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010106EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Settings 94 268 Parameter Meaning Range of Value Value IP Address left Enter the IP address of the device if Use IP Range is not checked Enter the start address of the IP scanning range if Use IP Range is checked valid IP address Default 192 168 1 1 Use IP Range checked An IP address range is used unchecked Only one IP address is used checked unchecked Default unchecked IP Address right Enter the ending address of the IP scanning range only if Use IP Range is checked valid IP address Default 0 0 0 0 Address Count Displays the scanning range address count depending on the selected IP start or IP end address For this read the note given below recommended 10 TCP Port Identifies the endpoint of a logical connection or addresses a specific endpoint on the device or PC 0 65535 Default Hilscher device 50111 Send Timeout ms Maximum time before the transfer of the transmission data is canceled when the send process fails for example because of the transfer buffer is full 100 60 000 ms Default TCP IP 1000 ms Reset Time
114. X2 gt If the PROFIBUS station address is set by the rotary switch at the device then the field Station Address is grayed out If the PROFIBUS station address is set by configuration software then enter in Station Address the PROFIBUS station address for the gateway device gt Set size and type of the modules for Output and Input Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 28 268 gt Default values can be used normally for the other parameters Depending on additionally requirements and the design of the PROFIBUS network as well as the used devices parameters needs to be adjusted if necessary More information about PROFIBUS DP Slave parameter is in section PROFIBUS DP Slave Parameter on page 187 3 Close the configuration window gt Click OK 3 gt The configuration window closes 2 2 7 Configure the Gateway Signal Mapping _h Open the Gateway configuration window Vv Select from the context menu of the gateway device symbol the entry Configuration gt Gateway The Gateway configuration window opens Open the Signal Mapping window VN g Select Configuration gt Signal Mapping J The window Signal Mapping opens netDevice Gateway netTAP NT 50 DP RS lt 2 gt 1 10 Device NT 50 DP RS Device ID Vendor Hilsch
115. YCON net frame application appears Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 21 268 2 2 3 Insert the Gateway Device into the Configuration Window gt Go to the device catalog under vendor Hilscher GmbH to the category Gateway Stand Alone Slave Use drag and drop with the NT 50 XX XX gateway device to insert it at the gray main line A 2 Hilscher GmbH Qj Gateway Stand Alone Slave Q NT 50 xx xx N Fieldbus Vendor DTM Class Figure 5 Insert Gateway Device into the Project 3 gt The gateway device appears in the project netTSP NT SO XX XX lt gt 1 d Figure 6 Gateway Device in the Project Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 22 268 2 2 4 Select the Protocol Conversion of the Gateway 1 Open the Gateway configuration window gt Double click the gateway device symbol or select from the context menu of the gateway device symbol the entry Configuration gt Gateway 3 gt The Gateway configuration window opens J netDevice Gateway netTAP NT 50 XX XX lt gt 1 10 Device NT SO XX XX Device ID Vendor Hilscher GmbH vendor ID OxO11E Navigati
116. a hilsclier COMPETENCE IN COMMUNICATION Operating Instruction Manual Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK Hilscher Gesellschaft fur Systemautomation mbH www hilscher com DOC0812010l06EN Revision 6 English 2014 04 Released Public Introduction 2 268 Table of Contents 1 IN FRODUGC TION a ca tietaie tis tate tie teteh ele A E E a att ail t 7 1 1 ABOU THIS MPU eal ss ccc acct a teal a eeta dicts tea teeuens dase dae cade atudt odake tepeteatiet gue sudan te 7 1 1 1 Online Helpis oren a cre a a tree cece eer erate renee eres 8 1 1 2 List Of ROVIO S a a a a a a a Aaa Ea EA aa 8 1 1 3 Conventions in this Manual ccceececeeeee ee eeeeeeeaee see eeceaeeeeeaeseeeeeseaeeeeaeeseneeees 9 1 2 egal ING CS airouan a a eta deena tote aa aaa eens ee cap da ecto A E E 10 1 2 1 aJo dTa LA EEE E A E sete ttteavteesharevell gaetenesndis 10 1 2 2 Important Noles anain a eli al A i led 10 1 2 3 Exclusion of Liability se niseni aie eee eed i aver eek A 11 1 2 4 Warranty escriit na i aie ice dali niet 11 1 2 5 Export REQUIALIONS ii5 251 besa c2sciblee Seva tales celivcesheibuleg totais ebulte giiieshsbaadii ae chelate ade 12 1 2 6 Registered Trademarks cccccccsceeeeeeeeeneeeeeaeeseeeeeceaeeeseaeeeeaeeseeeeesaaaesseeeseeeeess 12 1 3 About netGateway DTM sca his Hs wecec deca eccvadsthstaas godthcatadtesecepudeeudeacs maatigaataeeatiaeas 13 1 3 1 REQUIFOMONIS 2 c t ac te ba a
117. add to the user data further characters which have a certain meaning such as a start character an end character a checksum or a device address A typical telegram structure is e g Starti D a t a Checksum End with for example in hexadecimal notation 0x02 0x38 0x33 0x33 0x37 0x38 0x30 0x33 0x37 0x36 0x33 0x69 0xA5 0x03 Moda ClientMode ServerMode Send Only Mode Rece Receive Data Stream Configuration Start Hex v 02 Data Constant Lenath bytes 10 Check m CRc16 v 0 8005 End Hex 03 eee eee Table 59 ASCII Telegram Structure Example The serial data stream of the send and receive telegram each can be defined with up to 10 structural elements Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 213 268 Parameter Description Range of Value Parameter Type Structural element is not used Start Start character of the telegram consisting of one or more characters ASCIl The information is given as an ASCII character Char or as hexadecimal Hex Hex For the ASCII character STX enter the hexadecimal value 02 Decimal When sending the start character is inserted in the telegram When receiving the start character is checked for equality Device Device Address ASCII When sending the dev
118. addresses 1 Slaves Fixed value for gateway proxy devices Default 1 sercos Address Address for the sercos Slave 1 511 Default 1 FSP Type Function Specific Profile Type according to IDN S 0 1302 x 01 FSP Type Default IO V1 amp Version The FSP Type indicates the function specific type of the resource Supported FSP profiles FSP_lO FSP_Drive FSP IO A specification for IO Devices FSP Drive A specification for mechanical drives Set always FSP IO V1 for gateway proxy devices SCP SCP config type according to sercos third generation specification Default Fix Version 1 1 1 Configuration 0x0101 SCP_FixCFG Version 1 1 1 Type 0x0201 SCP_VarCFG Version 1 1 1 0x0202 SCP_VarCFG Version 1 1 3 According to the sercos third generation specification the sercos Communication Profiles Classes SCP FixCFG and SCP VarCFG define the basic communication and are mutually exclusive SCP FixCFG Exact two connections are supported one as consumer and one as producer The content of the connections is defined by the Slave and cannot be changed by the Master SCP VarCFG A certain number of connections is supported The Slave defines this number and provides it to the Master The content of all connections has to be configured e g by the Master The Slave provides lists of IDNs that can be cyclically produced and consumed so the Master can find it out FixCFG Version 1 1 1 is fixed for gateway proxy devices Output Data Output D
119. ailures in the software could lead to personal injury or injuries leading to death We inform you that the software was not developed for use in dangerous environments requiring fail proof control mechanisms Use of the software in such an environment occurs at your own risk No liability is assumed for damages or losses due to unauthorized use 1 2 4 Warranty Although the hardware and software was developed with utmost care and tested intensively Hilscher Gesellschaft fur Systemautomation mbH does not guarantee its suitability for any purpose not confirmed in writing It cannot be guaranteed that the hardware and software will meet your requirements that the use of the software operates without interruption and that the software is free of errors No guarantee is made regarding infringements violations of patents rights of ownership or the freedom from interference by third parties No additional guarantees or assurances are made regarding marketability freedom of defect of title integration or usability for certain purposes unless they are required in accordance with the law and cannot be limited Warranty claims are limited to the right to claim rectification Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Introduction 12 268 1 2 5 Export Regulations The delivered product including the technical data is subject
120. al The count of Tables exceeds the DBM32 DLL range of Tables This can cause problems if the file is used with older Tools using the DBM32 DLL CDBM_UNSUPPORTED_DATATYPE_ 0XC004C841 The Data type is not compatible with the IN_ RCS_MODE old database format CDBM_WRITE_UNSTRUCTURED_1 0XC004C842 The data of an unstructured record can only be written with the Write Method not with WriteElement CDBM_READ_UNSTRUCTURED_1 0XC004C843 The data of an unstructured record can only be read with the Read Method not with ReadElement CDBM_WRITE_DATA_LENGTH_ INVALID 0XC004C844 The given data length doesn t correspond with the expected data length CDBM_UNKNOWN_VIEW_MODE 0XC004C845 The View Mode is unknown CDBM_E_DIAG_TABLE 0XC004C846 It doesn t make much sense to add or delete records from a diagnostic table because those changes are never saved CDBM_E_ADR_STRING_ERROR 0XC004C847 The given Address string doesn t fit the required format of this type where all address bytes must be in the range between 0 and FF CDBM_ERROR_FROM_VAR_ CHANGE_TYPE 0XC004C848 Function VariantChangeType return an error when trying to convert the Parameter Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010106EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Error Codes 256 268 ODM Error Codes DBM V4
121. ame of station needs to be set for the device This parameter can be edited as follows 1 Open the configuration dialog gt Select from the context menu of the netTAP respectively the netLINK symbol the entry Configuration gt PROFINET IO Device The PROFINET IO Device configuration dialog opens 3 In the navigation area the entry Configuration under the folder Configuration is selected and the settings dialog is displayed 2 Set name of station The default name for the Name of Station for the NT 100 device as proxy is nt1O00ereproxy and for the NL 51N DPL device nl51ndpl If you need to set an other name of station or you use several netTAP or netLINK devices in the PROFINET network then set a unique name of station as follows gt Select in the navigation area under the folder Configuration the entry General gt Enter in the field Name of Station the name of station which the netTAP or netLINK device should use in the PROFINET network 3 Close configuration dialog Click on OK to save the parameter or click on Cancel if the parameter should not be saved 3 gt The configuration dialog closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 158 268 4 14 1 Settings at the used PROFINET IO Controller Proxy Device Description File To configure the Master a GSDML file
122. and drop it on the signal to be send Port X3 send Transfer status info of Port X3 to Port X2 gt If necessary map the status information of Port X3 Port X3 generated which are generated device internal to signals which should be send on Port X2 Port X2 send gt For this mark the status signal Port X3 and the signal which should be send Port X2 and click the button Map Signals Or Map the signal using drag and drop For this drag the status signal Port X3 generated and drop it on the signal to be send Port X2 send Auto mapping The signal mapping can also be done automatically be the configuration software Set Auto Mapping to From Port X3 to Port X2 and then click on Apply The automatic signal mapping is done Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 118 268 4 4 1 Status Information The status of the remote network coupled by the netTAP NT 100 can be mapped into the I O data It contains the items shown in the figures for master and slave and are described below Signals 4 Data type Port x3 Active Slaves UNSIGNED32 Generated Communication Change of State UNSIGNED32 Generated Communication Error UNSIGNED32 Generated Communication State UNSIGNED32 Generated Configured Slaves UNSIGNED32 Generated Error Count UNSIGNED32 Generated Error Log Indicator UNSIGNED32 Generated Faulted
123. ata Size in Byte 0 124 Byte Size for Fixed for SCP Configuration Type Fix Version 1 1 1 Default 2 Byte Configuration Note The output data size is part of the SDDML device description file If you use a sercos Master which is using SDDML files for configuration and the default output data size was changed then you have to export a new updated SDDML file from SYCON net and import this SDDML file into the configuration software for the sercos Master Input Data Size Intput Data Size in Byte 0 124 Byte for Fixed for SCP Configuration Type Fix Version 1 1 1 Default 2 Byte Configuration Note The input data size is part of the SDDML device description file If you use a sercos Master which is using SDDML files for configuration and the default input data size was changed then you have to export a new updated SDDML file from SYCON net and import this SDDML file into the configuration software for the sercos Master Further see next page Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 165 268 User SCP Up to 20 User SCP Types are possible The following User SCP types SCP_WD Version 1 1 1 Types are already defined SCP_Diag Version 1 1 1 0x0401 SCP_WD Version 1 1 1 for monitoring connections SCP_RTB Version 1 1 1 0x0501 SCP_Diag Version 1 1 1 for bus diagnos
124. ate of the communication system to a more safe state A special kind of Device Description file used by Ethernet POWERLINK Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Appendix 267 268 XML XML means Extended Markup Language It is a symbolic language for structuring data systematically XML is standard maintained by the W3C World wide web consortium Device Description Files often use XML based formats for storing the device related data appropriately Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Appendix 9 5 Contacts Headquarters Germany Hilscher Gesellschaft fiir Systemautomation mbH Rheinstrasse 15 65795 Hattersheim Phone 49 0 6190 9907 0 Fax 49 0 6190 9907 50 E Mail info hilscher com Support Phone 49 0 6190 9907 99 E Mail de support hilscher com Subsidiaries China Hilscher Systemautomation Shanghai Co Ltd 200010 Shanghai Phone 86 0 21 6355 5161 E Mail info hilscher cn Support Phone 86 0 21 6355 5161 E Mail cn support hilscher com France Hilscher France S a r l 69500 Bron Phone 33 0 4 72 37 98 40 E Mail info hilscher fr Support Phone 33 0 4 72 37 98 40 E Mail fr support hilscher com India Hilscher India Pvt Lt
125. ation based on the Modbus protocols for serial communication A communication system for Industrial Ethernet designed and developed by PROFIBUS International It uses some mechanisms similar to those of the PROFIBUS field bus PROFINET IO Controller PROFINET IO Device RE Real Time Ethernet A PROFINET control unit responsible for the defined run up of an I O subsystem and the cyclic or acyclic data exchange A PROFINET field device that cyclically receives output data from its IO Controller and responds with its input data RE stands for Real Time Ethernet Real Time Ethernet Industrial Ethernet is an extension of the Ethernet networking technology for industrial purposes with very good Real Time features and performance There is a variety of different Real Time Ethernet systems on the market which are incompatible with each other The most important systems of these are e EtherCAT Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Appendix Register sercos Slave Switch SYNC TCP IP VARAN Watchdog Timer XDD file 266 268 e EtherNet IP e Ethernet POWERLINK e Open Modbus TCP e PROFINET e sercos e VARAN A register in the meaning defined by Modbus terminology is a 16 bit wide storage area for data which can be accessed and addressed as a unit by some of the Modbus Function Codes
126. ax Output Maximum telegram length for send data 0 5736 Send data are taken from the output data area 1024 Default Table 57 3964R Parameter Part 2 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 208 268 4 24 2 Settings for the 3964R Remote Device gt Note The settings in the used remote device must comply with the settings in the netTAP or netBRICK device to establish a communication Important parameters are Interface type baud rate data bits parity RTS control retry limit character delay timeout and acknowledge timeout The conflict priority has to be set different for the used devices Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 209 268 4 25 Configuration ASCII ASCII American Standard Code for Information Interchange is a coding for characters ASCII is denoted a communication for serial data exchange here and is usually a human readable code and This type of communication contains however less definitions for the detailed communication procedure Many manufacturer specific implementations exist Basic functions are send and receive of exactly one specified telegram The functionality depicted here for send and receive of telegra
127. ay and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Introduction 3 268 2 3 9 toad FINMWANlC ic iets etstt viii de ute cnt cee evi ees eee ee ene 53 2 3 10 Eoad Configu atO sexs aaaea beth Ta aa rice lethtere ia eeaahads shetanaseeneled es 54 2 3 11 SAVE Projet 5 kes Ate a a E a ear Se ae a ati A 54 2 3 12 Device Description File to configure the Master cccceeseeeeceeeeeetteeeeeneeees 55 2 4 Configuration of a NT 100 as Proxy sc sv03 c ctr cine Reed 56 2 4 1 Start SYCON net and User LOQIN c ccceccceceeeeeeeeeeeeeeeceaeeeeaaeeeeeeesaeeeeaeenenees 56 2 4 2 Insert the Proxy Device into the Configuration Window ceceeeeeereees 57 2 4 3 Select the Protocol Conversion of the PrOXxy ccceccecseeeseeeeeeeeeseeeessaeeeenees 58 2 4 4 Configuration of the secondary Network ccscceeeeeseeeeeeeaeeeeeeeeseaeeesaeeeenees 61 2 4 5 Configuration of the primary Network c cccceceeseeceeeeeceeeeeeaeeseeeeesaeeesaeeeenees 64 2 4 6 Establish a Connection to the Proxy Device cccceeeeeeeeseeeeeeeeeteaeeeetaeeneneeees 66 2 4 7 Device ASSIQGNMOMNt oiin eea EEEa eevestades Mectace steal tevestadee declare SK CERATINA 68 2 4 8 Load Firmware asosan ied wed a enn A Ea a N ead alae 69 2 4 9 Load Configuratio Neitiid ie daian 70 2 4 10 Save nd A cl Weer crore perce os na a a a a a aT 70
128. bed in the document Ethernet Device Configuration Ol xx DE pdf 3 Open the Proxy configuration window Select from the context menu of the NL 51N DPL_ symbol Configuration gt Proxy 3 gt The Proxy configuration window opens 4 Select driver Select in the navigation area Settings gt Driver and then check netX Driver 3 gt The following figure shows the selected driver a netDevice Proxy netLINK NL 51N DPL lt gt 1 7 Y 10 Device NL S1N DPL Device ID z 3 vendor Hilscher GmbH vendor ID 0x011E Navigation area E Settings Driver Version ID netx Driver oO CIFX Device Driver 1 0 3 1 368BEC5B 0E92 4C0E B4A9 64F62AE7AAFA 7 Device Assignment 35Gateway Driver for netX 3 x 0 9 2 0 787CD349 4CF6 4259 8E4D 109B6A46BEA91 9 Configuration netX Driver 1 101 1 1761 B54C8CC F333 4135 8405 6E 12FC88EE62 Settings Figure 58 Select Driver Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 80 268 5 Set the IP search range gt Select in the navigation area Settings gt Driver gt netX Driver The window for driver settings opens a netDevice Proxy netLINK NL 51N DPL lt gt 1 i 10 Device NL S1N DPL Device ID t Vendor Hilscher GmbH Vendor ID 0x011E Navigation area E Settings I Driver gt net Dri
129. ble Otherwise the execution can be defined in steps of 10 ms With the cycle time the temporal execution of the command can be influenced If since the last execution of the command the set cycle time or more time has been passed the command is reexecuted If since the last execution of the command less time has been passed then the cycle time the command is skipped If e g from a Open Modbus TCP Server data are required only every 10 seconds as these one change only slowly then for the cycle time enter 10 000 ms 0 Cyclic 1 Changed Data Default Cyclic 0 10 20 30 60 000 ms Default 0 ms Delay Between the single commands a delay time can be parameterized This sometimes is necessary to avoid a too high load of the connected Server devices by a continuous communication 0 The commands are processed without delay 1 60 000 ms Delay time in ms the Open Modbus TCP Client waits before starting the next command 0 60 000 ms Default 0 Table 22 Parameter of the Command Table Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 141 268 4 10 2 3 Adding removing Command To add or to remove data sets for commands to the Command Table proceed as follows Add command gt In the table Command Table put the cursor in the line below which a
130. ble 65 Telegram Structure for the Operating Send Only Mode Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010I06EN Revision 6 English 2014 04 Released Public 218 268 Send Buffer Size bytes Hilscher 2009 2014 Configuration 219 268 4 25 2 5 Receive Only Mode Basic Principle In the Receive Only mode the device only receives The remote device only sends Telegram Telegram The superordinated control unit must acknowledge the reception Communication When configuring the telegram structure the method is defined how the end of the telegram is detected e Character e Length e Time Each telegram received is indicated to the superordinated control unit by handshake The superordinated control unit must acknowledge the reception Only after the acknowledgement the reception of a further telegram can be indicated to the superordinated control unit Timing Parameter Parameter Description Range of Value Receive Specifies whether the reception of subsequent telegrams 0 231 1 Watchdog is monitored by time Thereby the remote device can be Default 0 Time monitored The time is taken from telegram end to telegram end The value unequal to zero specifies in what time the remote device must have sent the next telegram If the time is exceeded then an error is reported to the host The value 0 specifies that the reception of subsequent telegrams is n
131. blic Hilscher 2009 2014 Online Functions 235 268 6 2 Download Configuration lt Note To download configuration parameter data to the netTAP NT 100 device an online connection from the netGateway DTM to the netTAP NT 100 device is required Ar Further information can be found in the Connecting Disconnecting Device AR section on page 233 To transfer the configuration with the corresponding parameter data to the netTAP NT 100 device you must download the data to it using the frame application of the configuration software Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Acyclic Proxy Communication 236 268 7 Acyclic Proxy Communication 7 1 Adress Mapping The read write record service of the PROFINET IO controller are converted to DPV1 read write services to the PROFIBUS DP slave for acyclic communication Thereby the PROFINET IO Controller can access the PROFIUS DP slaves via the proxy device an address mapping exsists The following figure and table describes the mapping of the PROFINET IO slot subslot and index to PROFIBUS station address slot and index Acyclic Communication AGOREL FOE Proxy Device Name of Station Station Address Figure 106 PROFINET PROFIBUS Address Mapping The proxy device is addressed by the PROFINET name of station This makes is possibl
132. btains its IP Address from a DHCP or BOOTP server If Enable is checked the device uses the manually entered value Valid Network mask for the device If Enable is unchecked Default setting the device obtains its Netmask from a DHCP or BOOTP server If Enable is checked the device uses the manually entered value Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public 0 20 65535 ms default 1000 ms 0 Off IO Server default Client Yes No Default Yes checked unchecked Default unchecked Sockets 0 16 Default 4 100 6 000 000 ms Default 1000 ms 100 6 000 000 ms Default 2 000 ms 0 2 000 000 000 ms Default 31 000 ms 0 2 000 000 000 ms Default 31 000 ms 0 2 000 000 000 ms Default 13 000 ms Valid IP address Default unchecked Valid network mask Default checked Hilscher 2009 2014 Configuration 136 268 Gateway Valid Gateway address for the device Valid gateway address If Enable is unchecked Default setting the device obtains its Gateway Default unchecked Address from a DHCP or BOOTP server If Enable is checked the device uses the manually entered value There are three methods available how the device can obtain its IP Address Netmask and Gateway Address one of which must be selected These methods can also be co
133. c independed of the used function code The following table shows the address assignment for registers and coils for one based Modbus RTU Master The setting Map FC 1 and FC 3 is not set in the configuration of the netTAP or netBRICK device in this case IN netTAP i OUT netTAP Coil Register netBRICK netBRICK FC 2 FC 4 Mapping Mapping OUT 624 9986 9999 Table 54 Access from the Modbus RTU Master using One based Addressing 1 The following table shows the address assignment for registers and coils for one based Modbus RTU Master The setting Map FC 1 and FC 3 is set in the configuration of the netTAP or netBRICK device in this case IN netTAP i Register IN netTAP i Register netBRICK FC 3 netBRICK FC3 Mapping FC 6 Mapping FC 4 FC 16 FC 23 read FC 23 write 6 1 32 2 48 3 pa 625 32 OUT 624 9986 9999 Table 55 Access from the Modbus RTU Master using One based Addressing 2 4 23 4 Modbus References 1 MODBUS Application Protocol Specification V1 1 http www modbus org 12 06 02 2 MODBUS Messaging on TCP IP Implementation Guide V1 0b October 24 2006 3 MODBUS APPLICATION PROTOCOL SPECIFICATION V1 1a June 4 2004 http www Modbus IDA org Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 205 268 4 24 Configuration 3964R
134. case of a CAN bus off event e g short circuit of the data lines Checked The device tries independently to continue operation in case of a CAN bus off event Continue On Loss of Network Power NP Function not supported Default unchecked Receive ldle Clear Data Default unchecked Unchecked Received data keep their last state in case of idle state Checked Received data were set to zero in case of idle state Receive Idle keeps Data Default unchecked Function not supported Prod Data Produced data length sets the number of send bytes 0 255 Length Default 8 Cons Data Consumed data length sets the number of receive bytes 0 255 Length Default 8 Table 42 DeviceNet Slave Parameters Part 2 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 183 268 4 20 2 Settings at the used DeviceNet Master Device Description File To configure the Master an EDS file device description file is required The EDS file is on the delivered DVD in the directory EDS DeviceNet Device EpsFile o NT 50 XX DN or NT 50 DN XX NT50_DN_DNS EDS NT 100 XX DN or NT 100 DN XX NT100_DN_DNS EDS NB 100 XX DN or NB 100 DN XX NB100_DN_DNS EDS Table 43 EDS File Names for netTAP and netBRICK Configuration Note The settings in the used Master must comply with the settings in the Slave to establish com
135. cceccecsecceseseeeeeeesecaeeeeeeaeeaeeesnaetaeeeeseaeas 187 4 22 2 Settings at the used PROFIBUS DP Mastel cccccesseeeseeceeeeeseeeteneeeeees 189 4 23 Configuration Modbus RTU Master Slave ccccccceceeceeeeeeeeneeeeeeeeneeeeteeeneeeeeeee 190 4 23 1 Modbus RTU Parameter ecccceeeeeceeeeeenneeeeeseaeeeeeeeaaeeeseeaaeeeeesaeeeeseaeeeesenaes 192 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Introduction 5 268 4 23 2 Modbus RTU Master cccccccccccecececeeeceseeeeeeeeeeaeaeaeaeeeaeasaeaeaeaeeeseasasesasaeaeees 194 4 23 3 Modbus RTU SAVE a ei a en E e r aa a ra ais teveeivesstdeclivevecestiol 201 4 23 4 ModbuS Reference eriet e ee eaa eaan aa a e aaa anat aa AE aea EEEE 204 4 24 Configuration S964 R a an aeaa eea e a a A tices cena serine 205 4 24 1 BOGB4R SENGE eiere A E E NEE A EE SNTE 206 4 24 2 Settings for the 3964R Remote DeViCe ccccececeeeeeceeeeeeneeseeeeeseeeeeeneeeeaes 208 4 25 Configuration ASCI sccssscesvecieecseieebecataentusatg rear aaa AE na ASE EEEE EAE a tates RE eii 209 4 25 1 ASGIMS HINGS creion A enti a ee asthe aad AR aE 211 4 25 2 AN EEE E EEEE E dhte te cleuelveectecleebeehiese Mantis 211 4 25 3 Settings for the remote ASCII DeVICE ceceeeeececeeeeeeeeeeeeeeeeeeeeesaeeeeneeeeaes 225 4 26 Configuration Serial With netSCRIPTP sececiecstade
136. ce reset including the re initialization of the physical interface used for the communication 100 60 000 ms Default RS232 and USB 5000 ms Byte size Number of bits per byte by byte specification 7 Bit 8 Bit Default RS232 8 Bit Parity In the error detection in data transmission using parity bits No Parity parity describes the number of bits occupied with 1 in the Odd Parity transmitted information word Even Parity No Parity no parity bit Mark Parity Odd Parity The parity is odd if the number of bits occupied with 1 in the transmitted information word is odd Even parity The parity is even if the number of bits occupied with 1 in the transmitted information word is even Mark Parity if the parity bit is always 1 this is named mark parity it contains no information Space Parity if the parity bit always 0 this is named space parity it is an empty space Space Parity Default RS232 No Parity Keep Alive Timeout ms The Keep Alive mechanism is used to monitor whether the connection to the device is active Connection errors are detected using a periodic heartbeat mechanism The heartbeat mechanism is initiated after the set time has elapsed if the communication has failed 100 60 000 ms Default RS232 and USB 2000 ms Restore Resets all settings in the configuration dialog to the default values Save Saving all settings made in the configuration dialog
137. ce stays open until timeout is expired Note This timeout starts after receiving the answer to a command For interface programming via Open Modbus TCP the value for Client Connection Watchdog Time Omb Open Time must be divided by the factor of 100 Value range for the interface programming 1 60 000 Only for client jobs in Message Mode packet mode After expiration of this time the job will be canceled and an error is send to the application Note This timeout starts after command is send to the destination device via TCP For interface programming via Open Modbus TCP the value for Response Timeout must be divided by the factor of 100 Value range for the interface programming 1 60 000 Parameter for TCP task in milliseconds Used OMB task internal It specifies the timeout for trying to send messages via TCP IP If the value 0 is selected the default value of 31 000 milliseconds is used Parameter for TCP task in milliseconds Used OMB task internal It specifies the timeout for trying to establish a connection with the TCP task If the value 0 is selected the default value of 31 000 milliseconds is used Parameter for TCP task in milliseconds Used OMB task internal It specifies the timeout for trying to close a connection with the TCP task If the value 0 is selected the default value of 13 000 milliseconds is used Valid IP address for the device If Enable is unchecked Default setting the device o
138. ces netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Introduction 9 268 1 1 3 Conventions in this Manual Notes operation instructions and results of operation steps are marked as follows Notes ae Important lt important note gt Note lt note gt lt note where to find further information gt Operation Instructions 1 lt instruction gt 2 lt instruction gt or gt lt instruction gt Results lt result gt Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Introduction 10 268 1 2 Legal Notes 1 2 1 Copyright Hilscher 2009 2014 Hilscher Gesellschaft fur Systemautomation mbH All rights reserved The images photographs and texts in the accompanying material user manual accompanying texts documentation etc are protected by German and international copyright law as well as international trade and protection provisions You are not authorized to duplicate these in whole or in part using technical or mechanical methods printing photocopying or other methods to manipulate or transfer using electronic systems without prior written consent You are not permitted to make changes to copyright notices markings trademarks or ownership declarations The included diagrams do not take the pa
139. cess Data Address Table peg Station Table More information about the configuration of PROFIBUS DP Master devices are in the document PROFIBUS_Master_netX_DTM_en pdf in section Configuration 3 Close the configuration window gt Click on the button OK 3 gt The configuration window closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010I06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 77 268 2 5 5 Configuration of the secondary Network The PROFINET IO network is at port X2 of the proxy device 1 Open the PROFINET IO Device configuration window gt Select from the context menu of the proxy device symbol the entry Configuration gt PROFINET IO Device The PROFINET IO Device configuration window opens and displays the modules netDevice PROFINET IO Device netLINK NL 51N DPL lt gt 1 DER 10 Device NL S1N DPL Device ID Ox0110 5 Vendor Hilscher GmbH vendor ID OxO11E Navigation Area FF E3 Configuration General Slot Sub Slot ag Modules g Address Table Description Device Info Module Info GSDML Viewer F NL51N PROFIBUS DP 7 CB_AB32 DPS Use of slots 3 3 State of data length Input 2 0 Octets Output 2 0 Octets In Output 4 0 Octets Submodule details Dataset Display mode Direction Consistence_ Data type Text ID Length ceel lt
140. communication system Often these formats are based on XML such as EDS files or GSDML files Contains configuration information Dynamic Host Configuration Protocol This is a protocol simplifying the configuration of IP networks by automatically assigning IP addresses Dual Port Memory Device Type Manager The Device Type Manager DTM is a software module with graphical user interface for the configuration and or for diagnosis of devices Electronic Data Sheet XML based device description file A special kind of Device Description File used by EtherNet IP A communication system for industrial Ethernet designed and developed by Beckhoff Automation GmbH A communication system for industrial Ethernet designed and developed by Rockwell It partly uses the CIP Common Industrial Protocol Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Appendix EtherNet IP Scanner EtherNet IP Adapter 264 268 A Scanner exchanges real time I O data with Adapters and Scanners This type of node can respond to connection requests and can also initiate connections on its own An Adapter emulates functions provided by traditional rack adapter products This type of node exchanges real time I O data with a Scanner Class product It does not initiate connections on its own Ethernet POWERLINK FDT Full duplex Function c
141. configuration window closes v Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 44 268 2 3 5 Configuration of the secondary Network If the slave device is not listed in the device catalog then it has to be imported into the device catalog first 2 3 5 1 Expand PROFIBUS DP Slave Device Catalog If you want to use a PROFIBUS DP slave device that is not listed in the device catalog then you have to import the GSD file into the SYCON net device catalog gt Proceed as follows 1 Missing PROFIBUS DP Slave devices can be added to the device catalog using the menu Network gt Import Device Descriptions 2 Select the new GSD file 3 Answer the question Do you want to reload the device catalog with Yes to reload the catalog 4 More information about the device catalog is in the document ab SYCONnet_netDevice_en pdf in the directory Documentation on the product DVD 2 3 5 2 Insert PROFIBUS DP Slave Device to the PROFIBUS Network gt Go to the device catalog Use drag and drop with one or more PROFIBUS DP Slave devices to insert it them at the PROFIBUS bus line The PROFIBUS DP Slave device icons appear at the PROFIBUS network line Secondary network netTAP NT 100 RE DP lt gt 1 CB_AB32 DPS CB_AB32 DPS lt 2 gt p B oooO
142. cription file If you use a sercos Master which is using SDDML files for configuration and the default device ID was changed then you have to export a new updated SDDML file from SYCON net and import this SDDML file into the configuration software for the sercos Master Vendor Code Identification number of the manufacturer assigned by sercos 0x00000000 International OxFFFFFFFF hex Vendor Code according to the sercos third generation specification as Hilscher 0Ox0000003E8 defined in IDN S 0 1300 x 03 hex Note The vendor code is part of the SDDML device description file If you use a sercos Master which is using SDDML files for configuration and the default vendor code was changed then you have to export a new updated SDDML file from SYCON net and import this SDDML file into the configuration software for the sercos Master Version Version of the sercos Communication Profile SYNC 0 1 of SCP Sync 0 SYNC deactivated With this setting the configuration parameter for Default 0 sercos Communication Profile Class SCP_Sync are not relevant and are displayed grayed out 1 SYNC activates version 1 If the sercos Master uses the telegram sequence MDT then NRT and then AT the gateway proxy device requires that the value is set to 1 Version Version of the sercos Communication Profile NRT Default 0 of SCP NRT 0 NRT deactivated With this setting the configuration parameter for IP communication are not relevant and are displayed g
143. csp and nt100 cc ccs_io csp describe the netTAP device as one Remote IO Station Configuration Note The settings in the used Master must comply with the settings in the Slave to establish communication Important parameters are Slave Station Address Baudrate and Station Type For CC Link Version 1 are additionally important Station type For CC Link Version 2 00 are additionally important number of cycles as well as number of extension cycles In order that the CC Link Master can communicate with the netTAP device as CC Link Slave gt Enter at the CC Link Master the Stationaddress which is configured in the netTAP device gt Set at the CC Link Master the same CC Link Version as configured in the netTAP device gt Set at the CC Link Master the same station type as configured in the netTAP device gt If CC Link Version 1 is to be used then set at the CC Link Master the same Station type as configured in the netTAP device gt If Station type is Remote Device Station to be used then set at the CC Link Master the same the number of stations as configured in the netTAP device gt If CC Link Version 2 is to be used then set at the CC Link Master the same number of extension as configured in the netTAP device Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 178 268 4 19 Config
144. ction to the proxy device gt Select as shown in the figure above Select the tap TCP Connection Is the Select IP Range grayed out as shown above then no IP range is defined Click on to add a new range which enables the field below Otherwise an address range configured earlier can be selected or by a mouse click on a new address range can be configured Set the IP start address and end address the proxy devices are searched for Make sure that the proxy device can be reached via Ethernet and is reachable via the address range 3 gt The fields to configure an IP address range are enabled Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 33 268 Select IP Range IP_RANGEO F Be Scan Timeout 100 H ms IP Range Configuration Disable IP Range IP Address Use IP Range TCP Port Address Count G 168 60 199 Q 50111 fi Send Timeout 1000 H ms Keep Alive Timeout 2000 ms Reset Timeout 20000 H ms Figure 17 Set IP Address Search Range 2 gt You can enter one IP address of the proxy device at as shown above or you can set an IP address range by a check at Use IP Range and set the IP end address at Make sure that the proxy device can be reached via Ethernet and is reachable via the address range E Note
145. ctivate the send data by handshake The superordinated control unit must acknowledge each reception by handshake Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 222 268 Timing Parameter Parameter Description Range of Value Send Cycle Specifies whether the telegram will be sent cyclically or triggered 0 28 1 Time The value unequal to zero specifies the cycle time of the send telegram Default 0 The value 0 specifies that the send telegram is triggered Response Specifies whether the reception of the response telegram is monitored by time Timeout Thereby the remote device can be monitored The time is taken from telegram end to Default 1000 telegram end The value unequal to zero specifies in what time the remote device must have sent the response telegram If the time is exceeded then an error is reported to the host The value 0 specifies that the reception of response telegrams is not monitored Character Specifies whether the time between two characters during reception is monitored by 0 2 1 Delay Time time Default 0 The value unequal to zero specifies in what time the remote device must have sent the next character If the time is exceeded then an error is reported to the host The value 0 specifies that no monitoring is performed Table 68 Timing Parameters for t
146. d New Delhi 110 065 Phone 91 11 26915430 E Mail info hilscher in Italy Hilscher Italia S r l 20090 Vimodrone MI Phone 39 02 25007068 E Mail info hilscher it Support Phone 39 02 25007068 E Mail it support hilscher com 268 268 Japan Hilscher Japan KK Tokyo 160 0022 Phone 81 0 3 5362 0521 E Mail info hilscher jp Support Phone 81 0 3 5362 0521 E Mail jp support hilscher com Korea Hilscher Korea Inc Seongnam Gyeonggi 463 400 Phone 82 0 31 789 3715 E Mail info hilscher kr Switzerland Hilscher Swiss GmbH 4500 Solothurn Phone 41 0 32 623 6633 E Mail info hilscher ch Support Phone 49 0 6190 9907 99 E Mail ch support hilscher com USA Hilscher North America Inc Lisle IL 60532 Phone 1 630 505 5301 E Mail info hilscher us Support Phone 1 630 505 5301 E Mail us support hilscher com Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010106EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014
147. d RCX_E_APPLICATION_NOT_READY 0xC0000182 Application Not Ready RCX_E_TIMER_APPL_PACKET_SENT 0xC002000C Timer App Packet Sent Table 83 RCX Common Status amp Errors Codes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010106EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Error Codes 8 3 3 RCX Status amp Error Codes 244 268 Error Code Definition Value Description RCX_S_OK 0x00000000 SUCCESS STATUS OKAY RCX_S_QUE_UNKNOWN 0xC02B0001 UNKNOWN QUEUE RCX_S_QUE_INDEX_ UNKNOWN 0xC02B0002 UNKNOWN QUEUE INDEX RCX_S_TASK_UNKNOWN 0xC02B0003 UNKNOWN TASK RCX_S_TASK_INDEX_UNKNOWN 0xC02B0004 UNKNOWN TASK INDEX RCX_S_TASK_HANDLE_INVALID 0xC02B0005 INVALID TASK HANDLE RCX_S_TASK_INFO_IDX_UNKNOWN 0xC02B0006 UNKNOWN INDEX RCX_S_FILE_XFR_TYPE_INVALID 0xC02B0007 INVALID TRANSFER TYPE RCX_S_FILE_ REQUEST_INCORRECT 0xC02B0008 INVALID FILE REQUEST RCX_S_UNKNOWN_DESTINATION 0xC0000005 UNKNOWN DESTINATION RCX_S_UNKNOWN_DESTINATION_ID 0xC0000006 UNKNOWN DESTINATION ID RCX_S_INVALID_LENGTH 0xC0000007 INVALID LENGTH RCX_S_UNKNOWN_COMMAND 0xC0000004 UNKNOWN COMMAND RCX_S_INVALID_ EXTENSION 0xC0000008 INVALID EXTENSION Table 84 RCX Status amp Error Codes 8 3 3 1 RCX Status amp Error Codes Slave State Error Code Definition Value Description RCX_SLAVE_STATE_UNDEFINED 0x00000000 UNDEFINED RCX_SLAVE_
148. d Output_0002 BYTE Send 128 InBytes BYTE_0001 Receive Input_0001 BYTE Send 1172 TnRvkee RVTE NNN Dersiva Trek O00 RVTE lt Mapped Signals i E 128 Bytes In lt Slot 1 gt CB_AB32 DPS lt Addr 2 gt I 128 Bytes Out lt Slot 2 gt 3 8 CB_AB32 DPS lt Addr 3 gt Port x2 PROFINET 10 Port x3 PROFIBUS DP Manual Mapping Auto Mapping Off X Cancel Help Figure 30 Gateway Signal Mapping The entry Memory Card Management in the navigation area is only available for net AP NT 100 devices Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 48 268 3 Signal Mapping Data transfer from Port X2 to Port X3 gt Map the signals which are received on Port X2 Port X2 receive with signals which should be sent on Port X3 Port X3 send gt For this mark the signal received Port X2 and the signal to be sent Port X3 and the click the button Map Signals Or Map the signal using drag and drop For this drag the signal received Port X2 receive and drop it on the signal to be sent Port X3 send 4 Signal Mapping Data transfer from Port X3 to Port X2 Map the signals which are received on Port X3 Port X3 receive with signals which should be sent on Port X2 Port X2 send gt For this mark the signal received Port X3 and the signal to be sent
149. d Parameter RCX_E_WATCHDOG_TIMEOUT 0xC000000C Watchdog Timeout RCX_E_INVALID_LIST_TYPE 0xC000000D Invalid List Type RCX_E_UNKNOWN_HANDLE 0xC000000E Unknown Handle RCX_E_PACKET_OUT_OF_SEQ 0xC000000F Out Of Sequence RCX_E_PACKET_OUT_OF_MEMORY 0xC0000010 Out Of Memory RCX_E_QUE_PACKETDONE 0xC0000011 Queue Packet Done RCX_E_QUE_SENDPACKET 0xC0000012 Queue Send Packet RCX_E_POOL_PACKET_GET 0xC0000013 Pool Packet Get RCX_E_POOL_GET_LOAD 0xC0000015 Pool Get Load RCX_E_REQUEST_RUNNING 0xC000001A Request Already Running RCX_E_INIT_FAULT 0xC0000100 Initialization Fault RCX_E_DATABASE_ACCESS_FAILED 0xC0000101 Database Access Failed RCX_E_NOT_CONFIGURED 0xC0000119 Not Configured RCX_E_CONFIGURATION_FAULT 0xC0000120 Configuration Fault RCX_E_INCONSISTENT_DATA_SET 0xC0000121 Inconsistent Data Set RCX_E_DATA_SET_MISMATCH 0xC0000122 Data Set Mismatch RCX_E_INSUFFICIENT_LICENSE 0xC0000123 Insufficient License RCX_E_PARAMETER_ERROR 0xC0000124 Parameter Error RCX_E_INVALID NETWORK_ADDRESS 0xC0000125 Invalid Network Address RCX_E_NO_SECURITY_MEMORY 0xC0000126 No Security Memory RCX_E_NETWORK_FAULT 0xC0000140 Network Fault RCX_E_CONNECTION_CLOSED 0xC0000141 Connection Closed RCX_E_CONNECTION_TIMEOUT 0xC0000142 Connection Timeout RCX_E_LONELY_NETWORK 0xC0000143 Lonely Network RCX_E_DUPLICATE_NODE 0xC0000144 Duplicate Node RCX_E_CABLE_DISCONNECT 0xC0000145 Cable Disconnected RCX_E_ BUS OFF 0xC0000180 Network Node Bus Off RCX_E_CONFIG_LOCKED 0xC0000181 Configuration Locke
150. d Table proceed as follows Add command gt In the table Command Table put the cursor in the line below which a new data set for a command shall be added gt Click Add 3 Under the clicked line a new command is added Remove command gt Inthe table Command Table put the cursor in the line with the data set to be deleted gt Click Remove The command of the clicked line is not shown any more 4 23 2 4 Setting Parameters ay Important When entering the parameters make sure that these address valid data registers Refer to the device description of the Modbus RTU Slave device manufacturer To set the single parameters in the Command Table proceed as follows 1 Device Address Function Code Address Number of Registers Coils The fields for these parameters are editable gt Enter the values for these parameters to the corresponding table cells 2 Trigger In Function Code field select an entry for a writing command FC 5 6 15 or 16 gt Inthe column Trigger select the entry Cyclic or Change Data 3 Cycle Time gt Put the cursor to the table cell and set the cycle time using the spin box a in steps of 10 ms Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 199 268 4 23 2 5 Examples Modbus RTU Reading or Writing Command Unit Indent
151. d function code The following table shows the address assignment for registers and coils for one based Open Modbus TCP Clients The setting Map FC 1 and FC 3 is not set in the configuration of the netTAP or netBRICK device in this case IN netTAP i OUT netTAP Coil Register netBRICK netBRICK FC 2 FC 4 Mapping Mapping IN 624 9986 9999 625 OUT 624 9986 9999 625 IN 2879 OUT 2879 sd Table 27 Access of the Open Modbus TCP Client using One based Addressing 1 The following table shows the address assignment for registers and coils for one based Open Modbus TCP Clients The setting Map FC 1 and FC 3 is set in the configuration of the netTAP or netBRICK device in this case IN netTAP i Register IN netTAP i Register netBRICK FC 3 netBRICK FC3 Mapping FC 6 Mapping FC 4 FC 16 FC 23 read FC 23 write 32 OUT624 9986 9999 Table 28 Access of the Open Modbus TCP Client using One based Addressing 2 4 10 4 Modbus References 1 MODBUS Application Protocol Specification V1 1 htto www modbus org 12 06 02 2 MODBUS Messaging on TCP IP Implementation Guide V1 0b October 24 2006 3 MODBUS APPLICATION PROTOCOL SPECIFICATION V1 1a June 4 2004 http www Modbus IDA org Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 147 268 4 11 Conf
152. des Error Code Definition Value Description CIFX_DRV_NOT_INITIALIZED 0x800B0001 Driver not initialized CIFX_DRV_INIT_STATE_ERROR 0x800B0002 Driver init state error CIFX_DRV_READ_STATE_ERROR 0x800B0003 Driver read state error CIFX_DRV_CMD_ACTIVE 0x800B0004 Command is active on device CIFX_DRV_DOWNLOAD_FAILED 0x800B0005 General error during download CIFX_DRV_WRONG_DRIVER_VERSION 0x800B0006 Wrong driver version CIFX_DRV_DRIVER_NOT_LOADED 0x800B0030 CIFx driver is not running CIFX_DRV_INIT_ERROR 0x800B0031 Failed to initialize the device CIFX_DRV_CHANNEL_NOT_INITIALIZED 0x800B0032 Channel not initialized xOpenChannel not called CIFX_DRV_IO_CONTROL_FAILED 0x800B0033 lOControl call failed CIFX_DRV_NOT_OPENED 0x800B0034 Driver was not opened CIFX_DRV_DOWNLOAD_STORAGE_UNKNOWN 0x800B0040 Unknown download storage type RAMFLASH based found CIFX_DRV_DOWNLOAD_FW_WRONG_CHANNE 0x800B0041 Channel number for a firmware download L not supported CIFX_DRV_DOWNLOAD_MODULE_NO_BASEOS 0x800B0042 Modules are not allowed without a Base OS firmware Table 90 Generic Driver Error Codes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010106EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Error Codes 252 268 8 5 3 Generic Device Error Codes Error Code Definition Value
153. dle 3 Operate 4 Communication Channel Error Master and Slave This field holds the current error code of the communication channel of the remote network If the cause of error is resolved the communication error field is set to zero again All values different from 0 indicate that an error has occurred Errors may be signaled either from the operating system rcX or from the used protocol Number of Configured Slaves Master The firmware maintains a list of slaves within the remote network to which the master has to open a connection This list is derived from the configuration database created by SYCON net This field holds the number of configured slaves Error Count Master and Slave This field holds the total number of errors detected since power up within the remote network respectively after reset The protocol stack counts all sorts of errors in this field no matter if they were network related or caused internally After power cycling reset or channel initialization this counter is being cleared again Error Log Indicator Master and Slave Note This field is not yet supported Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010106EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 121 268 Number of Faulted Slaves Master If a slave of the remote network encounters a problem it can provide an indication of the new situation to the
154. dress Table Station Table Bus Parameters Baud Rate kBit s Station Address Slot Time tBit Target Rotation Time Min Station Delay Time tBit Max Station Delay Time tBit GAP Actualization Factor Quiet Time tBit Max Retry Limit Setup Time tBit Highest Station Address HSA Bus Monitoring Data Control Time Override slave specific Watchdog Control Time Min Slave Interval Watchdog Control Time Calculated Timing Tidi 37 tBit Tid2 150 tBit Values marked with this symbol should be Adjust adjusted to changes in the topology ma lt Disconnected J Data Set Figure 28 PROFIBUS DP Bus Parameter Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 46 268 2 Configure the PROFIBUS DP Master gt Set the parameter Set especially under Configuration gt Bus Parameter the bus parameter and under Configuration gt Stationtable the station addresses stations addresses of the PROFIBUS DP Slave devices J netDevice PROFIBUS DP Master netTAP NT 100 RE DP lt gt 1 s 10 Device NT 100 XX XX Device ID Ox0B44 ao Vendor Hilscher GmbH Vendor ID 0x011E DT Navigation Area J Configuration Bus Parameters Process Data Address Table tay Station Table Figure 29 PROFIBUS DP Slave Station Address Name CB_AB32
155. e FullDuplex Duplex Operation Default unchecked If checked full duplex operation will be used The device will operate in half duplex mode if this parameter is set to zero This parameter will not be in effect when auto negotiation is active Auto neg Auto Negotiation Default checked If checked the device will auto negotiate link parameters with the remote hub or switch Produced data Maximum allowed length of the input data in Byte This parameter should 0 504 Byte length be equal to or higher than the complete projected input data length Default 32 Byte otherwise the EtherNet IP device will reject the cyclic communication requests Consumed data Maximum allowed length of the output data in Byte This parameter 0 504 Byte length should be equal to or higher than the complete projected output data Default 32 Byte length otherwise the EtherNet IP device will reject the cyclic communication requests Table 18 EtherNet IP Adapter Parameters Part 2 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 132 268 4 9 2 Settings at the used EtherNet IP Scanner Device Description File To configure the Scanner an EDS file device description file is required The EDS file is on the delivered DVD in the directory EDS EtherNetIP Device CDS File O_O NT 50 XX EN or NT 50 EN XX HILS
156. e General Diagnosis 230 Table 74 Descriptions of the Diagnosis Panes lt Note Accessing the Diagnosis panes of the netGateway DTM requires an online connection from the netGateway DTM to the netTAP NT 100 device 4 D _ For further information refer to section Connecting Disconnecting Device Li on page 233 Navigation area Ca J Diagnosis D d General Diagnosis Firmware Diagnosis Figure 103 Navigation Area Diagnosis Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Diagnosis 230 268 5 2 General Diagnosis Information regarding the Device State and other general diagnosis parameters are displayed in the General Diagnosis dialog Device State Network State W Communicating Operate Run Idle Ready Stop Eror Offline Configuration State W Configuration locked W New Configuration pending Reset required Bus ON Communication error Watchdog time 1000 ms Error count 0 Figure 104 General Diagnosis Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Diagnosis 231 268 Device State Communicating Communicating Shows that the netTAP firmware executes the network communication w Device is configured Shows that the netTAP firmware has been config
157. e 1 1490 Byte efault 4 Byte Disable PDO Decides whether PDO mapping version is checked hook checked or Default checked mapping version not checked hook unchecked check Select for netTAP and netBRICK devices always unchecked Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 150 268 Configuration Configure default Decides whether default objects are created hook checked or not Default checked objects hook unchecked If the objects will be created the old set of previously existing objects will be cleared Delete application Decides whether application objects are deleted hook checked or not Default checked objects hook unchecked When Configure Default Objects is checked then the firmware automatically does a Delete Application Objects Table 29 POWERLINK Controlled Node Slave Parameters Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 151 268 4 11 2 Settings at the used POWERLINK Managing Node Device Description File To configure the Managing Node a XDD file device description file is required The XDD file is on the delivered DVD in the directory EDS POWERLINK Device o pome O NT 100 RE XX 00000044_NT 100 RE PLS XDD N
158. e iaa aaan naea a aaa a ea a ete 107 4 3 7 Ordering the ICONS euere aea eee enian beta distee ena arched eal as 109 4 3 8 How to get the License and transfer it to the DeVICE i eceseceeeesteeeeeenees 114 4 4 Sha MAp DING e a a T a nee tates delist a ene tested 115 4 4 1 Status Information inaani ania aasia eile 118 4 5 Memory Card Management ssssesssseeesserrseernttrtttesstrrrnernnttttnnrnsernntnenennserr eneee 122 4 6 Configuration EtherCAT Maste ccccccccsssseeeeeeseeeeeeeeeeeeeeeeneaeeeeeeaaaeeeeesaaaeeeeas 123 4 7 Configuration EtherGAT Slave sc soteecdscecscctcssseceeaeneeads talede vied merecies cach ueaaedeeeet paces 124 4 7 1 EtherCAT Slave Parameter cc ccccccceceeeeesceeeeeeeceeeeeeeaeeesaaeeceaeeeseaeeeeaeeeenees 125 4 7 2 Settings at the used EtherCAT Mastet 0 ccccccscceeeeeeeseeeeeneeseeeeeseaeeeeeeeeeas 126 4 8 Configuration EtherNet IP Scanner cccceeeceeeeeeceeeeeeeeeeeeeeeaeeeeeeesaaaeeeeensaaeeeenes 127 4 9 Configuration EtherNet IP Adapter ccccccceeeeesseeeeeeeeeeeeeeeeaaeeeeeeeaaeeeeeesaaeeeeenas 128 4 9 1 EtherNet IP Adapter Parameter 0 ccececeeeeeeeeeeeeeeeaeeeeeeaeeeseeaaeeeeeeaeeeeeeaaes 130 4 9 2 Settings at the used EtherNet IP Scanner cccccceeeeceeeeseeeeeeessneeeeessteeeeeees 132 4 10 Configuration Open Modbus T G Paves saisseecoicuietiec ones eesenratioeveetnmaiaoken Hite cean 133 4 10 1 Open Modbus TCP Parametel ccccccce
159. e same memory for input data IN Registers 16 bit value and coils 1 bit value share the same memory for output data OUT The following tables Table 23 and Table 28 show the data assignment Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 144 268 Adressing types of Open Modbus TCP Clients Open Modbus TCP Clients of different manufacturers use different addressing types The modicon based addressing is very popular Other Open Modbus TCP Clients use a zero based addressing and again other Open Modbus TCP Clients use one based addressing gt Note Read the documentation of the used Open Modbus TCP Client to find out the used addressing of this system Modicon based addressing If function code 3 6 16 and 23 is used the first register 16 bit value has address 40001 the second register has address 40002 etc If function code 4 is used the first register has address 30001 the second register has address 30002 etc If function code 1 5 and 15 is used the first coil 1 bit value has address 1 the second coil has address 2 etc If function code 2 is used the first coil has address 10001 the second coil has address 10002 etc The following table shows the address assignment for registers and coils for modicon based Open Modbus TCP Clients The setting Map FC 1 and FC 3 is not set in the
160. e to address several proxy devices on the PROFINET network The following table shows details of the address mapping PROFINET PROFIBUS Slot SubSlot Index Mapped PROFIBUS Deiail Remark 0 X X DeviceSlot Device Module Not used 1 0 0x000 PB Slave Device 1 Slave Record Data Slot 0 Used Ox00FF 0x0100 PB Slave Device 1 Parameter Data Not used 0x0101 PB Slave Device 1 Configuration Data Not used 0x0102 PB Slave Device 1 Read Input Record Data Used 0x0103 PB Slave Device 1 Read Output Record Data Used 0x0104 Not used OxFFFF 1 254 0x000 PB Slave Device 1 Slave Record Data Slot 1 254 Used Ox00FF 0x0100 Not used OxFFFF 255 X Not used 2 0 254 See Slot 1 PB Slave Device 2 Used And so on with the same mapping for all following slaves from 3 till 125 126 0 254 See Slot 1 PB Slave Device 126 used 127 x X Not used 128 0 254 See Slot 1 PB Slave Device 0 Used Table 78 PROFINET IO PROFIBUS Address Mapping of acyclic Data Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Acyclic Proxy Communication 237 268 7 2 Read Write Controlled by the PROFINET IO Controller PROFINET lO read record is converted to PROFIBUS DPV1 read The data of the PROFIBUS DP Slaves are forwarded unchanged to the PROFINET IO Controller PROFINET IO write record is con
161. eased Public Hilscher 2009 2014 Appendix 258 268 9 Appendix 9 1 User Rights User rights are set within the FDT container Depending on the level the configuration is accessible by the user or read only To access the Settings Configuration and Diagnosis panes of the netGateway DTM you do not need special user rights Also all users can select the decimal or hexadecimal Display mode or sort table entries gt Note To edit set or configure the parameters of the Settings and Configuration panes you need user rights for Maintenance for Planning Engineer or for Administrator The following tables give an overview of the user right groups and which user rights you need to configure the single parameters 9 1 1 Settings Observer Operator Maintenance Planning Adminis Engineer trator Table 95 Settings D Displaying X Editing Configuring 9 1 2 Configuration Observer Operator Maintenance Planning Adminis Engineer trator Table 96 Configuration D Displaying X Editing Configuring Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Appendix 9 2 Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Figure 18 Figure 19 Figure 20 Figure 21 Fi
162. ection Signal Configuration on page 228 Close configuration dialog Click on OK to save the parameter or click on Cancel if the parameter should not be saved The configuration dialog closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 175 268 4 18 1 CC Link Slave Parameter Bus Startup Communication starts automatically Automatic Default Watchdog Time This function is not supported by gateway or proxy devices 0 20 65535 ms default 1000 ms 0 Off I O Data Status Status of the input or the output data Default None For each input and output data the following status information in Byte is memorized in the dual port memory Status 0 None default Status 1 1 Byte for future use Status 2 4 Byte for future use Enabled If Enabled is unchecked for the single Ident parameters each the respective default value is used Vendor Code Code for the Vendor 0 65535 resp 0x00000000 OxOOOOFFFF hex Hilscher 0x00000352 hex Model Type Model type 0 255 Default 1 Software Software version 0 63 Version Default 0 Station Address Station address of CC Link Slave 1 64 Note The number of occupied stations plus station address must not Default 1 exceed the parameter range Baud Rate Network transmission rate 156 kBaud Default 625 kBa
163. ed If Enabled is unchecked for the single Ident parameters each the respective default value is used Vendor ID Identification number of the manufacturer 0x00000000 OxOOOOFFFF hex Hilscher 0x0000001 1B hex Product Code Product code of the device 0x00000000 OxFFFFFFFF hex Default NT 50 DN DNS 0x0000002D hex NT 100 DN DNS 0x00000002B hex NB 100 DN DNS 0x0000002F hex Serial Number Serial number of the device 0x00000000 OxFFFFFFFF hex Product Type Communication Adapter 0x00000000 OxOOOOFFFF hex Default 0x00000000C hex Minor Rev Minor Revision 1 255 Default 1 Major Rev Major Revision 1 255 Default 1 Product Name_ The variable Product Name is a text string that should represent a short 0 31 ASCII description of the product product family Characters Table 41 DeviceNet Slave Parameters Part 1 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 182 268 This parameter defines the DeviceNet address of the device within the 0 68 network Default 2 Baudrate Baud rate of DeviceNet connection 500 kBaud 250 kBaud 125 kBaud Default 500 kBaud Extras Ignore address switch address switches are always ignored Default unchecked Continue on CAN bus off Default unchecked Unchecked A device reset by the user is necessary in
164. ed to the host The value 0 specifies that no monitoring is performed Table 70 Timing Parameters for the Operating Mode Server Mode Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Configuration Example Send Only Mode Receive Only Mode Client Mode Receive Data Stream Configuration 225 268 Start v Hex X eooo Data y Constant Length bytes 10 Check x CRC16 Ios CS i S S End v Hex ha Timeout Signal Configuration Enabled Receive Buffer Size ___si2 bytes Watehdog Time 0 ms Signal Configuration Enabled Send Data Stream Configuration Redeive Start x Hex y 02 Data Constant Length bytes 10 Check v CRC16 v 0 8005 End Hex 03 Send Buffer Size ___s12 bytes Table 71 Telegram Structure Parameters for the Operating Mode Server Mode 4 25 3 Settings for the remote ASCII Device Note The settings in the used remote device must comply with the settings in the netTAP or netBRICK device to establish a communication Important parameters are Interface type baud rate data bits parity check and respectively RTS control Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC08
165. eds a configuration e g information about how many PROFIBUS DP Slave devices with how many input and output data are to be connected 1 gt Insert PROFIBUS DP Slave devices Drag from the device catalog PROFIBUS DP Slave device s and drop it to the bus line of the PROFIBUS DP Master Configure PROFIBUS DP Slave devices Open the configuration dialog for each PROFIBUS DP Slave device and configure the device Information about how to configure the PROFIBUS DP Slave device is in the operating instruction manual Generic DTM for PROFIBUS DP Slave devices and has the file name PROFIBUS _Generic_Slave_DTM_en pdf respectively open in the configuration dialog of the slave the online help by the F1 key Configure PROFIBUS DP Master Select from the context menu of the netTAP respectively the netBRICK symbol the entry Configuration gt PROFIBUS DP Master Information about how to configure the PROFIBUS DP Master device is in the operating instruction manual DTM for PROFIBUS DP Master devices and has the file name PROFIBUS_Master_netX_DTM_en pdf respectively open in the configuration dialog of the master the online help by the F1 key Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 185 268 4 22 Configuration PROFIBUS DP Slave The netTAP NT 50 and NT 100 device respectively the netBRICK N
166. eeceeeeeeeeneeeceeeesaaeeeeeeeseeeeessaeeseeeeeaes 135 4 10 2 Open Modbus TCP Client cccccecceeeeeeeeeeeeeeaeeceeeeecaeeesaaeseeneeseeeesaeeeseneeeaas 137 4 10 3 Open Modbus TCP Serve l cccccccsccesecceceeeceesaeeeeeeeesaeeeeeaeeseneesneeesaeseeaeeesaes 143 4 10 4 Modbus References s 2iacacia ha tal tie aA ei acess 146 4 11 Configuration POWERLINK Controlled Node ecccceeeeeeeeeeeeeeeeeeeeeeeneeeeeeeeneeeeeess 147 4 11 1 POWERLINK Controlled Node Parametet ccccccceseceeseceeeeeseeeeeneeeeenees 149 4 11 2 Settings at the used POWERLINK Managing Node ns 151 4 12 Configuration PROFINET 10 Controller ccccceccceceeeeeeeeeeeeeeneeeeeeeneeeeeeeenaeeeeeee 152 4 13 Configuration PROFINET IO Device Gateway ssssseessssersssrrrnrereeerrsrrrrssrrene 153 4 13 1 PROFINET IO Device Parameter esssesssssrsesrresrnssrnssrnsstrrstrnsrnnrnssrnssrnsnnt 155 4 13 2 Settings at the used PROFINET IO Controller Gateway cceeeeeeeees 156 4 14 Configuration PROFINET IO Device Proxy c cceeeeeeeeeeeeeneeeeeeeeaeeeeeeneaeeeeeees 157 4 14 1 Settings at the used PROFINET IO Controller Proxy 158 4 15 Configuration sercos Slave ss iare cae Gann deck daxalscens nadie aanneadsmeoeaudea seantnads toaciGaatioeabane 159 4 15 1 sercos Slave Parameter ccccccceseseeceeeeeeeaeceeeeeeeeeeecaeeeeaaeseeeeeseeeeseaaeeseneeee 161 4 15 2 Settings at the used sercos MaStel
167. eive an e mail containing a Link to download the License File This leads to a server PC on which the license file is provided Using the received link you will have to save the license file on your PC and then transfer the license to your device If your e mail client is on another PC as your device you must save your license file e g to an USB stick Steps how to proceed 1 Save the license file to a PC or a disk gt Click to the Link to download the License File in the e mail gt Save the license file nx to a PC or a removable disk 2 Download the license file to the device gt Respectively connect the removable disk with the license file to the PC which is connected to your device gt Click Download License E in the License pane in the configuration software Download License Figure 90 License Pane Download License The File selection window Open is displayed Therein select the license file netX License Files nxl Click Open The license file is transferred to the device After this the license is present in the device and is activated with the next device reset G y Vg 3 Activate Device Reset Hint To activate the license in the first device a device reset is required gt To check whether the license has been activated follow the steps in section Which Licenses are present in the Device on page 104 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0
168. elect Start gt Programs gt SYCON net System Configurator gt SYCON net SYCON net is started User Login In the window SYCON net User Login click OK to login or enter your password and then click OK to login SYCON net frame application appears Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 73 268 2 5 3 Insert the Proxy Device into the Configuration Window gt Go to the device catalog under vendor Hilscher GmbH to the category Gateway Stand Alone Slave Use drag and drop with the NL 51N DPL proxy device to insert it at the gray main line S 3 Hilscher GmbH Gateway Stand Alone Slave Se CIFX CC CCS ee Si a CIFX CO COS CIFX CO COS eds NLSIN DPL K Fieldbus vendor ADT Class Or go to the device catalog under fieldbus PROFINET IO to the category Gateway Stand Alone Slave Use drag and drop with the NL 51N DPL proxy device to insert it at the gray main line AlE PROFINET 10 3 Gateway Stand Alone Slave Ja CIFX REJPNS 25 COMX REJPNS 0 NL51N DPL G Master Slave FN Fieldbus A vendor i DTM Class Fi Figure 52 Insert Proxy Device into the Project 3 gt The proxy device appears in the project a netLINK NL 51N DPL lt gt 1 m Eeg Figure 53 Proxy Device in the Project Configuratio
169. elect the protocol for the secondary network which becomes X3 active on port X3 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 101 268 No Name Description Required gateway The required gateway device is shown here after you have select the protocols at and It is also possible to select the gateway device first Then you can select at and protocols that are suitable for this gateway device Required license If you have selected a protocol with master functionality at and or then the number of master licenses required in the device is displayed here How to order and transfer master licenses is described in section Licenses on page 102 Available Firmware Available firmware files for the selected protocols are listed in this area The firmware files are stored in the SYCON net installation directory of the PC in the sub folder netGatewayDTM Firmware 0 Browse Browse opens a dialog to select a firmware file The selected firmware file is shown in area Download Download transfers the selected firmware file into the device which is selected in area This is possible even when no protocols have been selected at and Software class The Software class of the selected firmware is displayed for informati
170. en length CDBM_E_WRITE_BSTR_E2 0XC004C832 The BSTR string must contain only hex digits 0 9 and a A f F CDBM_E_WRITE_CANT_ INTERPRET_ARRAY 0XC004C833 Unable to interpret data in the SafeArray CDBM_E_WRITE_VT_ERROR 0XC004C834 Data type in the SafeArray is not VT_UI1 or VT_I1 CDBM_E_WRITE_LENGTH 0XC004C835 Data length is invalid for write operation of this type CDBM_WRITE_ELEMENT 0XC004C836 Element not found in the Record of the Table CDBM_MIN_MAX_ERROR 0XC004C837 Can t write data because of min underflow or max overflow CDBM_TABLE_EXIST 0XC004C838 Table already exist in the database CDBM_MIN_MAX_INVALID 0XC004C839 The Min value is greater than the Max Value CDBM_DEF_MIN_MAX_INVALID 0XC004C83A The Default Value is not in the range between the Min value and the Max Value CDBM_CANT_CHANGE_STRUCTURE _ 0XC004C83B It s not allowed to change the structure WHILE_RECORDS_EXIST while Records exist in the Table CDBM_NEW_STRUCT_NEEDS_TYPE 0XC004C83C In a newly added structure the data type must be set also CDBM_VALUE_ERROR 0XC004C83D Range error while validating a value CDBM_DATATYPE_ UNSUPPORTED_IN_RCS OXC004C83E The data type is unsupported in the RCS file format CDBM_ _COUNT_OF_TABLES 0X4004C83F The count of Tables exceeds the RCS EXCEEDS_RCS_RANGE Informational range of Tables This can cause problems if the file is downloaded to RCS Systems CDBM_I_COUNT_OF_TABLES EXCEEDS_OLDDBM_RANGE 0X4004C840 Information
171. er devices and has the file name EtherNetIP_GenericAdapter_DTM_en pdf respectively open in the configuration dialog of the slave the online help by the F1 key 3 Configure Ethernet IP Scanner Select from the context menu of the netTAP respectively the netBRICK symbol the entry Configuration gt Ethernet IP Scanner Information about how to configure the Ethernet IP Scanner device is in the operating instruction manual DTM for EtherNet IP Scanner devices and has the file name EtherNetIP_Scanner_DTM_en pdf respectively open in the configuration dialog of the master the online help by the F1 key Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 128 268 4 9 Configuration EtherNet IP Adapter The netTAP NT 50 and NT 100 device respectively the netBRICK NB 100 device as EtherNet IP Adapter needs parameter The device can either work as a Client or as a Server These parameter can be edited as follows 1 gt Open the configuration dialog Select from the context menu of the netTAP respectively the netBRICK symbol the entry Configuration gt EtherNet IP Adapter The EtherNet IP Adapter configuration dialog opens In the navigation area the entry Configuration under the folder Configuration is selected and the settings dialog is displayed EtherNet IP Adapter Parameter To set a fix
172. er GmbH Vendor ID OxO11E Navigation area E3 Settings Driver netx Driver Device Assignment E Configuration Settings Port X2 Signals 4 Data type Port X3 Signals 4 Data type tay Signal Mapping Available Signals Receive OutByte_O000 BYTE 5 C Receive OutByte_0001 BYTE Send 256 InWORDs WORD_O WORD Receive OutByte_0002 BYTE Send 256 InWORDs WORD_O WORD Receive OutByte_0003 BYTE 256 InWORDs WORD_O WORD lt Mapped Signals H 32 Bytes Out lt Slot 1 gt R 256 Registers In lt SlotO gt _ Port x2 PROFIBUS DP Port X3 Modbus RTU Manual Mapping Auto Mapping off v Figure 13 Gateway Signal Mapping Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 29 268 3 Signal Mapping Data transfer from Port X2 to Port X3 gt Map the signals which are received on Port X2 Port X2 receive with signals which should be sent on Port X3 Port X3 send gt For this mark the signal received Port X2 and the signal to be sent Port X3 and the click the button Map Signals Or Map the signal using drag and drop For this drag the signal received Port X2 receive and drop it on the signal to be sent Port X3 send 4 Signal Mapping Data transfer from Port X3 to Port X2 Map the signals which are received on Port X3 Port X3 recei
173. erted in the telegram When receiving the checksum is calculated based on of the received characters and is checked for equality with the received checksum Characters with no meaning Constant Length Bytes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 214 268 Parameter Description Range of Value Parameter Type Constant Length bytes Specifies the number of bytes which have no meaning and which should be ignored When sending the number of characters with a value of zero is inserted in the telegram When receiving the number of characters is ignored and thus filtered out from the telegram Table 60 Telegram Structure Hexadecimals The entry is made as a hexadecimal value A hexadecimal value consists of 2 characters in the range 00 to FF and result in one byte Each character has the range of value 0 1 2 9 A B F ASCII Character The entry is made as a character A character is one of the following characters A Z a z 0 9 amp ly h Pho ars t Decimal Decimal value The entry is made as a decimal value Table 61 Parameter Types Example The specification of the character A is as hexadecimal value 41 as character A or as a decimal value 65 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN
174. es DBM VA eaaa aa aaa steeds es oka a a cates sawed dadvadatest 254 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Introduction 6 268 9 APPENDIX iniiai acta ste seta tt athe a a tabard ebscbe des a TR 258 9 1 WIS Or RINS isimna an a a aes a a oie healed eatin T AA 258 9 1 1 e S E E E A E E N E EEE 258 9 1 2 Configuratore sasea a cde asia a aaa et aa Taaa aa aa Eaa AEE aD aA 258 9 2 Eod me E E EA E T A hacheassmaacdenrodeantem merece 259 9 3 istof TabDleS naea e ea a a ae aS aE a a a aE e ETIS 261 9 4 Glossae e E E E at 263 9 5 ME IMEC Ge a a a aa a a E nancediaamaasndnsdanens 268 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Introduction 7 268 1 Introduction 1 1 About this Manual This manual provides information on how to set and configure the device parameters of e a netTAP device of the NT 50 device family e a netTAP device of the NT 100 device family e anetBRICK device of the NB 100 device family e anetLINK proxy device using the netGateway DTM and what can be read from the diagnosis panes Dialog Panes The table below gives an overview for the individual dialog panes descriptions Section feuse e Device Assinment Je Diagnosis Table 1 Descriptions Dialog Panes Con
175. es each work with consistency Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 189 268 4 22 2 Settings at the used PROFIBUS DP Master Device Description File To configure the Master a GSD file device description file is required The GSD file is on the delivered DVD in the directory EDS PROFIBUS Device GspFile oo NT 50 XX DP or NT 50 DP XX HIL_0C99 GSD NT 100 XX DP or NT 100 DP XX HIL_OCOE GSD NB 100 XX DP or NB 100 DP XX HIL_OC9C GSD Table 46 GSD File Names for netTAP and netBRICK Configuration Note The settings in the used Master must comply with the settings in the Slave to establish a communication Important parameters are Station Address Ident Number Baudrate and Config Data the configuration data for the output and input length In order that the PROFIBUS DP Master can communicate with the netTAP or netBRICK device as PROFIBUS DP Slave gt Enter at the PROFIBUS DP Master the station address which is configured in the netTAP or netBRICK device gt Use for the configuration of the PROFIBUS DP Master module s e g 64 Bytes Out for sending data to the netTAP or netBRICK device Use the module s which are configured in the netTAP or netBRICK device Modules with the size of zero in the netTAP or netBRICK configuration needs not to be considered for
176. esaeeeeaaeenenees 87 3 2 2 Configuring the Driver ss sessssssssssssiessiessissrississerstinstnntstinstnnstnnstnnntnnntnnnnnn tnt 88 3 2 3 OLX DIVE aeaa ee aaaea erea raaa AATE aces beans TEET AAAA ET aatia A aoan y raa Aa aad abenida 89 3 2 4 Configure netX Driver cceccceceeceeeseeceeeeececeeeeeaeeeeeeeseaeeesaaeeseaeeseeeeesaeeneaeeenaees 95 3 3 Device Assignment nerea aa e a a R 96 3 3 1 Scanning for Device Sinu isoeo aani iania ed iaaa iaiia 96 3 3 2 Selecting the DEVICE nren a a end AE 98 4 CONFIGURATION ssela a a ita A anaa Sh de ata EE hd 99 4 1 Overview Configuratio nisn snena as ees ols Ge ae ae 99 4 2 SINS Fe cco cet cca Sea E ease A E E A ieee 100 4 3 NGOS E tie nites felted tended T vas feted tae seals et aca Sa stan cs 102 4 3 1 Open License Dialog vivieeisiseedead ede een Wee fe eee eee day cde ace Seca 102 4 3 2 License Dialog 2 c c cdectiavaaaar eave eed te i anaut Dai 103 4 3 3 Which Licenses are present in the Device ceeececeteeeeeeeeeeeeeeeeeetaeeteneeees 104 4 3 4 How to order a License 0 0 eeeececeeeeneeeeeeeecaeeeeeeaaeeeeeeaaeeeeesaaeeeeeeaaaeeeeeeaeeeeeeaas 106 4 3 5 Selecting License s ceecceceeeeeesteeeeeeeeceeeeeeaaeseeneeceaeeecaaaesseneesneeeesaeseeaeeseaes 106 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Introduction 4 268 4 3 6 Ordering Data meaa e
177. ess and Baudrate Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 172 268 4 17 2 Settings at the used CANopen Master Device Description File To configure the Master an EDS file device description file may be required The EDS file is on the delivered DVD in the directory EDS CANopen NT 50 XX CO or NT 50 CO XX NT50_CO_COS EDS NT 100 XX CO or NT 100 CO XX NT100_CO_COS EDS NB 100 XX CO or NB 100 CO XX NB100_CO_COS EDS Table 37 EDS File Names for netTAP and netBRICK Configuration gt Note The settings in the used Master must comply with the settings in the Slave to establish communication Important parameters are node address and baudrate In order that the CANopen Master can communicate with the netTAP or netBRICK device as CANopen Slave gt Enter at the CANopen Master the Node ID which is configured in the netTAP or netBRICK device Configure at the CANopen Master all PDOs which the Master should send to the netTAP or netBRICK device For the netTAP or netBRICK device these are receive PDOs E g the Master can be configured with 2 PDOs with 8 byte user data each 16 bytes in total to be send to the netTAP or netBRICK device Configure at the CANopen Master all PDOs which the Master should receive from the netTAP or netBRICK device For the netTAP or netBRICK device
178. etX Driver CIFX Device Driver 1 0 3 2 368BEC5B 0E92 4C0E B449 64F62AE7AAFA Device Assignment 35Gateway Driver for netX 3 x 0 9 2 0 787CD349 4CF6 4259 8E4D 109B6A6BEA91 9 Configuration netX Driver 1 101 1 1878 B54C8CC7 F333 4135 8405 6E 1 2FC88EE62 Settings Signal Mapping cei Figure 15 Select Driver Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 32 268 5 Set the IP search range gt Select in the navigation area Settings gt Driver gt netX Driver The window for driver settings opens ZnetDevice Gateway net TAP NT 50 DP RS lt 2 gt 1 10 Device NT 50 DP RS Device ID Vendor Hilscher GmbH vendor ID 0x011E Navigation area A Settings Driver tay netX Driver USB RS232 Connection TCP Connection 9 Device Assignment E Configuration Settings E Signal Mapping Select IP Range 2 WH Scan Timeout 100 ms IP Range Configuration E JV Enable TCP Connector Restart of ODM required IP Address TCP Port Address Count E Send Timeout Keep Alive Timeout 4 Reset Timeout Restore Save Save All cmn Figure 16 Set IP Address Search Range 1 An IP address one or IP addresses several address range are set in this window which SYCON net uses to build up a conne
179. eter indicates the 0 255 multiplier number of pulses of the communication synchronized hardware output Default 2 signal DIV_CLK within a communication cycle For Divided Control Clock Mode1 Here the parameter indicates the number of communication cycles DivClk polarity This communication synchronization flag defines the output state of the Disabled Active high communication synchronized hardware output signal DIV_CLK Active low Default RE S3S devices Active high DivClk mode This communication synchronization flag defines the mode of the Mode 0 Mode 1 communication synchronized hardware output signal DIV_CLK Default RE S3S devices Mode 0 The Div_Clk signal becomes active several times within a Mode 1 communication cycle The following condition must be fulfilled in mode 0 Divided Control Clock Length 100 lt Delay Time of Divided Clock Mode 1 The Div_Clk signal becomes active once after N communication cycles ConClk polarity This communication synchronization flag defines the output state of the Disabled Active high communication synchronized hardware output signal CON_CLK Active low Default RE S3S devices Active high Further see next page Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 164 268 Slave Configuration Number of The number of used sercos
180. eter on page 181 Note Default values can be used normally for the other parameters Depending on additionally requirements and the design of the DeviceNet network as well as the used devices parameters needs to be adjusted if necessary Open the signal configuration dialog Select in the navigation area under the folder Configuration the entry Signal Configuration The signal configuration dialog opens Signal configuration If you want to assign own signal names then enter your signal names Further information is described in section Signal Configuration on page 228 Close configuration dialog Click on OK to save the parameter or click on Cancel if the parameter should not be saved The configuration dialog closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 181 268 4 20 1 DeviceNet Slave Parameter Bus Startup Communication starts automatically Automatic Default Watchdog Time This function is not supported by gateway or proxy devices 0 20 65535 ms default 1000 ms 0 Off I O Data Status Status of the input or the output data Default None For each input and output data the following status information in Byte is memorized in the dual port memory Status 0 None default Status 1 1 Byte for future use Status 2 4 Byte for future use Enabl
181. etwork Gateway address Disconnected J Data Set Figure 57 PROFINET IO Name of Station gt Enter the Name of Station gt Note The name of station is very important and is used by the PROFINET IO Controller to identify the proxy device 3 Close the configuration window gt Click on the button OK 3 gt The configuration window closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 79 268 2 5 6 Establish a Connection to the netLINK NL 51N DPL 1 Connect an Ethernet cable to the NL 51N DPL gt Connect an Ethernet cable to the Ethernet port of the NL 51N DPL device and to the Ethernet port of the configuration PC It is also possible to connect the NL 51N DPL and the configuration PC to an Ethernet switch 2 Set the IP address of the NL 51N DPL device gt Set with the Ethernet Device setup software which is part of the SYCON net installation the IP address for the NL 51N DPL With this software it is also possible to read an already assigned IP address from the NL 51N DPL device The IP address is required for the communication with the SYCON net software To communication from the SYCON net software with the NL 51N DPL a8 device an IP address has to be assigned before to the NL 51N DPL device How to assign an IP address is descri
182. eway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 227 268 4 26 1 netSCRIPT Settings Interface type Type of the serial interface which should be used RS232 Default RS485 RS422 RTS Control Specifies if RTS control is activated or deactivated RTS Control Off Default When using the interface type RS 485 then RTS Control on has to RTS Control On be used Baud rate Specifies the baud rate 300 Bit s 600 Bit s 1200 Bit s 2400 Bit s 4800 Bit s 9600 Bit s Default 19200 Bit s 38400 Bit s 57600 Bit s 115200 Bit s Data bits Specifies the number of data bits 7 or 8 s 8 Default Stop bits Specifies the number of stop bits 1 or 2 eae Specifies the parity bit of the serial data communication None Default None means that no parity bit is used Even Odd Table 72 netSCRIPT Settings 4 26 2 Settings for the netSCRIPT Remote Device Note The settings in the used netSCRIPT remote device must comply with the settings in the netTAP or netBRICK device to establish a communication Important parameters are Interface type baud rate data bits parity check and respectively RTS control Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 228 268 4 27 Signal Configuratio
183. figuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Introduction 8 268 1 1 1 Online Help The netGateway DTM contains an integrated online help facility gt To open the online help click on the Help button or press the F1 key 1 1 2 List of Revisions 4 2011 03 10 1 400 x x netGatewayDTM dll Section Licenses updated netGatewayGUl ocx 4 All sections containing the parameter Watchdog Time changed to This function is not supported by gateway or proxy devices Section Configuration sercos Slave expanded SDDML export added Section Configuration ASCII Default Value for Response Timeout is 1000 5 2013 02 13 1 501 x x netGatewayDTM dll A Section Status Bar updated netGatewayGUl ocx 4 Section Settings address switch added 10 Section Open Modbus TCP Parameter updated Section Configuration sercos Slave updated Function codes 7 8 and 23 added Chapter Acyclic Proxy Communication added 2014 04 02 1 501 x x netGatewayDTM dll 9 Section EtherNet IP Adapter Parameter updated netGatewayGUI ocx Section Open Modbus TCP Parameter updated Section Open Modbus TCP Client updated Section Open Modbus TCP Server and Modbus RTU Slave Modicon based addressing type as well as zero and one based addressing types described Section Modbus RTU Master updated Configuration of Gateway and Proxy Devi
184. fset 2 master gt slave For gateway proxy devices use 2 Real Time Data Offset 3 not supported For gateway proxy devices use 0 Real Time Data Offset 4 not supported For gateway proxy devices use 0 Maximum Real Time Data Maximum Length for the Slave connections 1 2 3 and 4 Default 126 Byte allowed Real Only displayed Time Data Length Table 33 sercos Slave Parameter Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010Ol06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 166 268 4 15 2 Settings at the used sercos Master Device Description File If you use a sercos Master which is using SDDML files for the configuration of slave devices then export with SYCON net your settings into a SDDML file as described in section Configuration sercos Slave on page 159 If you use default settings then you can use the default SDDML file The default SDDML file is on the delivered DVD in the directory EDS SERCOS_III NT 100 RE XX Hilscher NT 100 RE S3S xml NB 100 RE XX Hilscher NB 100 RE S3S xml Table 34 XML File Names for netTAP and netBRICK These device description files includes the following settings e DevicelD NT_100 RE_S3S_FIXCFG respectively NB_100 RE_S3S_FIXCFG e Vendor Code 1000 03e8 hex Hilscher e Output data size 2 e Input data size 2 If you use these default settings for the netTAP device respectively netB
185. g with setting Map FC 1 and FC 3 M Map FC 1 and FC 3 M Modbus RTU Master Figure 102 Access from the Modbus RTU Master to the netTAP and netBRICK Device Registers 16 bit value and coils 1 bit value share the same memory for input data IN Registers 16 bit value and coils 1 bit value share the same memory for output data OUT The following tables Table 50 to Table 55 show the data assignment Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 202 268 Adressing types of Modbus RTU Master Modbus RTU Master of different manufacturers use different addressing types The modicon based addressing is very popular Other Modbus RTU Master use a zero based addressing and again other Modbus RTU Master use one based addressing Note Read the documentation of the used Modbus RTU Master to find out the used addressing type Modicon based addressing If function code 3 6 16 and 23 is used the first register 16 bit value has address 40001 the second register has address 40002 etc If function code 4 is used the first register has address 30001 the second register has address 30002 etc If function code 1 5 and 15 is used the first coil 1 bit value has address 1 the second coil has address 2 etc If function code 2 is used the first coil has address 10001 the seco
186. gnal names Further information is described in section Signal Configuration on page 228 6 Close configuration dialog Click on OK to save the parameter or click on Cancel if the parameter should not be saved 3 gt The configuration dialog closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 125 268 4 7 1 EtherCAT Slave Parameter Bus Startup Communication starts automatically Automatic Default Watchdog Time This function is not supported by gateway or proxy devices 0 20 65535 ms default 1000 ms 0 Off I O Data Status Status of the input or the output data None 1 Byte 4 Byte For each input and output data the following status information in Byte is Default None memorized in the dual port memory Status 0 None default Status 1 1 Byte for future use Status 2 4 Byte for future use Enabled If Enabled is unchecked for the single Ident parameters each the respective default value is used Vendor ID Identification number of the manufacturer 0x00000000 OxFFFFFFFF hex Primary Hilscher Vendor ID 0x00000044 hex Default Secondary Hilscher Vendor ID 0xE0000044 hex Product Code Product code of the device as specified by the manufacturer 0x00000000 OxFFFFFFFF hex Default NT 100 RE ECS 0x0000000D hex NB 100 RE ECS 0x00000019 he
187. gnals which are received on Port X2 Port X2 receive with signals which should be send on Port X3 Port X3 send gt For this mark the signal received Port X2 and the signal to be send Port X3 and the click the button Map Signals Or Map the signal using drag and drop For this drag the signal received Port X2 receive and drop it on the signal to be send Port X3 send Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010I106EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 117 268 Data transfer from Port X3 to Port X2 gt gt Map the signals which are received on Port X3 Port X3 receive with signals which should be send on Port X2 Port X2 send For this mark the signal received Port X3 and the signal to be send Port X2 and the click the button Map Signals Or Map the signal using drag and drop For this drag the signal received Port X3 receive and drop it on the signal to be send Port X2 send Transfer status info of Port X2 to Port X3 gt If necessary map the status information of Port X2 Port X2 generated which are generated device internal to signals which should be send on Port X3 Port X3 send For this mark the status signal Port X2 and the signal which should be send Port X3 and click the button Map Signals Or Map the signal using drag and drop For this drag the status signal Port X2 generated
188. gray main line Hilscher GmbH 4 Gateway Stand Alone Slave NB 100 XX XX WA NT 100 xx xx Fieldbus Yendor DTM Class Figure 21 Insert Gateway Device into the Project 3 gt The gateway device appears in the project netTAP NT 100 XX XX lt gt 1 Figure 22 Gateway Device in the Project NT 100 is shown as example Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 40 268 2 3 3 Select the Protocol Conversion of the Gateway 1 Open the Gateway configuration window gt Select from the context menu of the gateway device symbol the entry Configuration gt Gateway 3 gt The Gateway configuration window opens J Gateway net TAP NT 100 XX XX lt gt 1 3 10 Device NT 100 XX XX Device ID ao Vendor Hilscher GmbH Vendor ID OxO11E Navigation area a Piki Scan progress 0 0 Devices Current device TCP IP Driver For netx netx Driver Device selection suitable only v tay Device Assignment E Configuration Device Hardware Ports 0 1 Slot nu Serial nu Driver Channel Protocol Access path Settings Licensing Signal Mapping Memory Card Management Access path Figure 23 Device Assignment without Device The entry Memory Card Management in the navigation area is only available for net A
189. gs Mapping Cycle time Mapping mode on Figure 63 Firmware update Click with the left mouse on Browse The file dialog of the operating system opens Select the new firmware file The file name is displayed at Select the new firmware file at The file name is L51NPSDL NXF Click with the left mouse on Download The firmware file is transferred into the NL 51N DPL Close the dialog with OK Vi vv GYD Y Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Settings 86 268 3 Settings 3 1 Overview Settings Settings Dialog Panes The table below gives an overview for the individual Settings dialog panes descriptions Section susson p Diver Ss Configuring the Driver S a A E E C i setetng tte Device o Table 7 Descriptions Settings Navigation area 3 Settings EJ Driver nets Driver Device Assignment Figure 64 Navigation Area Settings gt Note To edit the Settings dialog panes you need User Rights for Maintenance Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Settings 87 268 3 2 Driver The devices netTAP NT 100 and netBRICK NB 100 are configured via an USB interface of the device or diagnosis is performed via the
190. guration window gt Click on the button OK 3 gt The configuration window closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 64 268 2 4 5 Configuration of the primary Network The PROFINET IO network is on port X2 of the proxy device 1 Open PROFINET IO Device configuration window gt Select from the context menu of the proxy device symbol the entry Configuration gt PROFINET IO Device The PROFINET IO Device configuration window opens with the view of the modules Yo netDevice PROFINET IO Device netTAP NT 100 RE DP PROXY lt gt 1 Navigation Area FQ E Configuration IO Device Vendor NT 100 RE DP Hilscher GmbH Device ID Vendor ID 0x0106 0x011E General Address Table E Description Device Info Module Info GSDML Viewer Subslot FINT 100 RE DP PROXY 1 3 0x00000001 3 NT100 PROFIBUS DP 1 3 0x00000001 3 CB_AB32 DPS 1 amp 2 byte input output CB_AB32 DPS 1 3 2 byte input output Use of slots 2 2 State of data length Input 0 1024 Octets Output 0 1024 Octets In Output 0 2048 Octets Submodule details froda x Direction Dataset Display mode Text ID Consistence KI Disconnected J Data Set Figure 45 PROFINET IO Device Table Here the modules with its slot number and sub slot number
191. gure 22 Figure 23 Figure 24 Figure 25 Figure 26 Figure 27 Figure 28 Figure 29 Figure 30 Figure 31 Figure 32 Figure 33 Figure 34 Figure 35 Figure 36 Figure 37 Figure 38 Figure 39 Figure 40 Figure 41 Figure 42 Figure 43 Figure 44 Figure 45 Figure 46 Figure 47 Figure 48 Figure 49 Figure 50 Figure 51 Figure 52 Figure 53 Figure 54 Figure 55 List of Figures Dialog Structure of netGateway DTM Navigation Area Status Bar Status Fields 1 to 6 Status Bar Display Examples Insert Gateway Device into the Project Gateway Device in the Project Device Assignment without Device Gateway Protocol Selection 1 Gateway Protocol Selection 2 Gateway Protocol Selection 3 Protocol Configuration Protocol Configuration Gateway Signal Mapping Gateway Signals mapped Select Driver Set IP Address Search Range 1 Set IP Address Search Range 2 Select Device Firmware Download Security Question Save Project Insert Gateway Device into the Project Gateway Device in the Project Device Assignment without Device Gateway Protocol Selection 1 Gateway Protocol Selection 2 Protocol Configuration Gateway Device with Slave PROFIBUS DP Bus Parameter PROFIBUS DP Slave Station Address Gateway Signal Mapping Gateway Signals mapped Select USB Driver 1 Select USB Driver 2 Select Device Firmware Download Security Question Save Project Insert Proxy Device
192. he Operating Mode Client Mode Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Send Only Mode Receive Only Mode Configuration Example Server Mode Send Data Stream Configuration Signal Configuration Enabled Start v Hex F wooo Data v Constant Lenath bytes 10 Check CRCIE os05 End v Hex AB a ed Y z Send Cycle Time o ms Timeout 223 268 Send Buffer Size L 512 bytes ms Receive Data Stream Configuration Start X Hex 02 Data v Constant Length bytes 10 Check z 0x8005 End z Hex 3 liss E lt Receive Buffer Size F E Joo si bytes Table 69 Telegram Structure for the Operating Mode Client Mode Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010I06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 224 268 4 25 2 7 Server Mode First Receive Then Send Basic Principle In the Server Mode the device receives a telegram from the remote device The superordinated control unit must acknowledge each reception by handshake The superordinated control unit must activate by handshake the send operation The device then sends a telegram to the remote device
193. he Required gateway as shown above depends on the selected protocols 4 Close the Gateway configuration window gt Click on the button OK 3 The Gateway configuration window closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 43 268 2 3 4 Configuration of the primary Network 1 Configure the protocol at the primary network Port X2 gt Select from the context menu of the gateway device symbol the entry Configuration gt PROFINET IO Device 3 The PROFINET IO Device configuration window opens J PROFINET IO Device netTAP NT 100 RE DP lt gt 1 DAR e 10 Device NT 100 RE DP Device ID 0x010b ao Vendor Hilscher GmbH Vendor ID OxO1le DT Navigation area Configuration Interface y Configuration Signal Configuration Bus Startup Watchdog Time 1 0 Data Status Ident Vendor ID Enable Device ID Device Type Order ID Name of Station Type of Station Data Input Data Bytes Output Data Bytes Figure 26 Protocol Configuration gt Set the parameters Set especially the number of Input Data Bytes and Output Data Bytes More information about PROFINET IO Device parameter is in section Configuration PROFINET IO Device Gateway on page 153 2 Close the configuration window Click on OK 3 gt The
194. ice e g 64 gt Enter at the EtherCAT Master the number of data bytes number of output data that are configured in the netTAP or netBRICK device e g 32 gt You can set at the EtherCAT Master if the Master verifies identification numbers of the EtherCAT Slave This verification can be activated or deactivated at the EtherCAT Master If the verification is used then use or check for the following values vendor 68 0x0044 product code 13 0x000D for NT 100 respectively product code 25 0x00019 for NB 100 revision number 0 Ox0000 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 127 268 4 8 Configuration EtherNet IP Scanner The netTAP NT 50 NT 100 device respectively the netBRICK NB 100 device as Ethernet IP Scanner needs a configuration e g information about how many Ethernet IP Adapter devices with how many input and output data are to be connected 1 Insert Ethernet IP Adapter devices gt Drag from the device catalog Ethernet IP Adapter device s and drop it to the bus line of the Ethernet IP Scanner 2 Configure Ethernet IP Adapter devices gt Open the configuration dialog for each Ethernet IP Adapter device and configure the device Information about how to configure the Ethernet IP Adapter device is in the operating instruction manual Generic DTM for EtherNet IP Adapt
195. ice address is inserted in the telegram Thereby the Hex receiving device is specified Decimal When receiving the device address is checked for equality Object Object Index or Start Address of the data in the device ASCII When sending the object index start address is inserted in the telegram Hex When receiving the object index start address is checked for equality Decimal Command Command Identifier ASCII When sending the Command Identifier is inserted in the telegram Hex When receiving the Command Identifier is checked for equality Decimal Data Length specification for Data Field or Telegram end Character or Time Constant Length Bytes Length Specification Byte Number Data Constant Length bytes The data field has a fixed length The information is Word Number Data given as number of bytes Character Terminated Byte Number Data The length specification is given in one byte When Unspecific sending this byte is inserted in the telegram directly before the data field When receiving the value of this byte from the telegram is used as the length of the directly following data field Word Number Data The length specification is given in one word When sending this word is inserted in the telegram directly before the data area When receiving the value of this word from the telegram is used as the length of the directly following data field Termination Character Character Terminated The data field is termi
196. ifier Function Code Address Number of Register Coils Memory Address internal Trigger Cycle Time ms 0 Read Holding Registers FC3 10 12 O Cyclic 0 0 Preset Multiple Register FC16 30 2 0 Changed 0 Figure 100 Examples Reading Command with FC 3 Writing Command with FC16 Device Address Example Reading Command with FC 3 From the Modbus RTU Slave device with the Modbus address 8 from data address 40011 onwards 12 registers are read by function code 3 The data are assigned to the memory address internal 0 Example Writing Command with FC 16 To the Modbus RTU Slave with the Modbus address 8 from data address 40031 onwards 12 registers are written by function code 16 The data are read from the process image of the Master from the memory address internal 0 onwards The writing process is only performed if the data in the process image of the Master on the memory addresses internal 0 to 3 have changed as the parameter trigger is set to changed Modbus RTU Slave 8 Modbus RTU Master Input Data 0 40001 1 40002 9 40010 Output Data Figure 101 Examples Reading Command with FC 3 Writing Command with FC16 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 200 268 4 23 2 6 Settings for Modbus RTU Slaves gt Note The settings in the used
197. ignal configuration gt Ifyou want to assign own signal names then enter your signal names Further information is described in section Signal Configuration on page 228 7 Close configuration dialog Click on OK to save the parameter or click on Cancel if the parameter should not be saved 3 gt The configuration dialog closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 170 268 4 17 1 CANopen Slave Parameter Parameter meann OOOO Range ot Vaevae Bus Startup Communication starts automatically Automatic Default Watchdog Time This function is not supported by gateway or proxy devices 0 20 65535 ms default 1000 ms 0 Off O Data Status Status of the input or the output data Default None For each input and output data the following status information in Byte is memorized in the dual port memory Status 0 None default Status 1 1 Byte for future use Status 2 4 Byte for future use Enabled If Enabled is unchecked for the single Ident parameters each the respective default value is used Vendor ID Identification number of the manufacturer 0x00000000 OxOOOOFFFF hex Hilscher 0x00000044 hex Product Code Product code of the device as specified by the manufacturer 0x00000000 OxFFFFFFFF hex Default NT 50 CO COS 0x001ACB60 hex NT 1
198. iguration POWERLINK Controlled Node The netTAP NT 100 device respectively the netBRICK NB 100 device as POWERLINK Controlled Node needs parameter These parameter can be edited as follows 1 Open the configuration dialog gt Select from the context menu of the netTAP respectively the netBRICK symbol the entry Configuration gt POWERLINK Controlled Node gt The POWERLINK Controlled Node configuration dialog opens 3 In the navigation area the entry Configuration under the folder Configuration is selected and the configuration dialog is displayed 2 Set Node ID Enter in the field Node ID the address which the netTAP or netBRICK device uses on the POWERLINK network to be addressed by the POWERLINK Managing Node 3 Set input data length and output data length Set in the field Input Data Length the number of data bytes the netTAP or netBRICK device should receive from the POWERLINK Managing Node gt Set in the field Output Data Length the number of data bytes the netTAP or netBRICK device should send to the POWERLINK Managing Node 4 Enable PDO Mapping Version Check Uncheck the field Disable PDO Mapping Version Check 5 Set more parameter gt f necessary set more parameter The parameter are described in the following section POWERLINK Controlled Node Parameter on page 149 Note Default values can be used normally for the other parameters Depending on additionally requirements and the design of the POWERLINK
199. ile name CANopen_Generic_Slave_DTM_en pdf respectively open in the configuration dialog of the slave the online help by the F1 key 3 Configure CANopen Master Select from the context menu of the netTAP respectively the netBRICK symbol the entry Configuration gt CANopen Master Information about how to configure the CANopen Master device is in the operating instruction manual DTM for CANopen Master devices and has the file name CANopen_Master_netX_DTM_en pdf respectively open in the configuration dialog of the master the online help by the F1 key Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 168 268 4 17 Configuration CANopen Slave K7 The netTAP NT 50 and NT 100 device respectively the netBRICK NB 100 device as CANopen Slave needs parameter These parameter can be edited as follows 1 Open the configuration dialog gt Select from the context menu of the netTAP respectively the netBRICK symbol the entry Configuration gt CANopen Slave The DeviceNet Slave configuration dialog opens 3 In the navigation area the entry Configuration under the folder Configuration is selected and the configuration dialog is displayed 2 Set Node ID Enter in the field Node ID the address which the netTAP or netBRICK device uses on the CANopen network to be addressed by the CANopen Master 3 Set
200. into the Project Proxy Device in the Project Device Assignment without Device Proxy Protocol Selection 1 Proxy Protocol Selection 2 Proxy Device with Slave PROFIBUS DP Bus Parameter PROFIBUS DP Slave Station Address PROFINET IO Device Table PROFINET IO Name of Station Select USB Driver 1 Select USB Driver 2 Select Device Firmware Download Security Question Save Project Insert Proxy Device into the Project Proxy Device in the Project Proxy Device with Slave PROFIBUS DP Bus Parameter Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public 259 268 Hilscher 2009 2014 Appendix Figure 56 Figure 57 Figure 58 Figure 59 Figure 60 Figure 61 Figure 62 Figure 63 Figure 64 Figure 65 Figure 66 Figure 67 Figure 68 Figure 69 Figure 70 Figure 71 Figure 72 Figure 73 Figure 74 Figure 75 Figure 76 Figure 77 Figure 78 Figure 79 Figure 80 Figure 81 Figure 82 Figure 83 Figure 84 Figure 85 Figure 86 Figure 87 Figure 88 Figure 89 Figure 90 Figure 91 Figure 92 Figure 93 Figure 94 Figure 95 Figure 96 Figure 97 Figure 98 Figure 99 PROFINET IO Device Table PROFINET IO Name of Station Select Driver Set IP Address Search Range 1 Set IP Address Search Range 2 Select Device Security Question Save Project Firmware update Navigation Area Settings Drive
201. ioned trademarks are property of their respective legal owners Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Introduction 13 268 1 3 About netGateway DTM You can use the netGateway DTM to configure a netTAP device of the NT 50 device family as a gateway a netTAP device of the NT 100 device family as a gateway a netBRICK device of the NB 100 device family as a gateway a netTAP device of the NT 100 device family as a proxy respectively a netLINK proxy device of the type NL 51N DPL as a proxy within a FDT Framework 1 3 1 Requirements System Requirements PC with 1 GHz processor or higher Windows XP SP3 Windows Vista 32 bit SP2 Windows 7 32 bit or Windows 7 64 bit Administrator rights Internet Explorer 5 5 or higher RAM min 512 MByte recommended 1024 MByte Graphic resolution min 1024 x 768 pixel Keyboard and Mouse xy Note If the project file is saved and opened again or if it is used on another PC the system requirements must match Particularly the DTM must be installed on the used PC Requirements netGateway DTM To configure a netTAP NT 50 device a netTAP NT 100 device a netBRICK NB 100 device or a netLINK proxy NL 51N DPL device with a DTM the following requirements have to be accomplished Completed hardware installation of a netTAP NT 50 device a netTAP N
202. is SCP_Mux Version 1 1 1 0x0601 SCP_RTB Version 1 1 1 for using Real time bits SCP_Sig Version 1 1 1 0x0901 SCP_Mux Version 1 1 1 for multiplexed cyclic data 0x0B01 SCP_Sig Version 1 1 1 for using signal status control words Gateway proxy devices do not support User SCP Types Therefore don t mark any User SCP Type Slave Flags Use a default object dictionary Default checked For gateway proxy devices this is always checked Delete objects created by application on reset checked For gateway proxy devices this is always checked Default checked Master is not allowed to to change sercos address checked unchecked enables unchecked or disables checked that the Master changes the Default checked sercos address For gateway proxy devices this must always be checked Connection Connection Control Offset for the Slave connections 1 2 3 and 4 0 5 758 Control Offset Connection Control Offset 1 slave gt master Default 0 For gateway proxy devices use 0 Connection Control Offset 2 master gt slave For gateway proxy devices use 0 Connection Control Offset 3 not supported For gateway proxy devices use 0 Connection Control Offset 4 not supported For gateway proxy devices use 0 Real Time Data Real Time Data Process Image Offset for the Slave connections 1 2 3 0 5 760 Offset and 4 Default 2 Real Time Data Offset 1 slave gt master For gateway proxy devices use 2 Real Time Data Of
203. issioning only Therefore do the following steps 1 Open the proxy configuration window gt Select from the context menu of the gateway device symbol the entry Configuration gt Proxy The proxy configuration window opens 2 Open the Settings window gt Select Configuration gt Settings The window Settings opens J netDevice Proxy netTAP NT 100 RE XX PROXY lt gt 1 J 10 Device NT 100 RE DP PROXY Device ID 30 Vendor Hilscher GmbH vendor ID OxO11E Navigation area A E Settings General a Driver netX Driver Description netTAP Device Assignment E Configuration ey Settings Memory Card Management Primary network Port X2 z Secondary network Port X3 ZI Licensing Protocol Combinations Required gateway Required license Yes 1 Available Firmware 1 JAE Browse Download Software class Gateway Software version 1 3 3 0 Basic Settings Mapping Cycle time 1 ms Mapping mode Save operation succeeded Figure 50 Firmware Download 3 Select Firmware gt Mark at Available Firmware the firmware file NTPNSDPM NXF Firmware for PROFINET IO Device to PROFIBUS DP Master 4 Load firmware into the device gt Click on Download The firmware is loaded into the netTAP device f Important Do not remove the cable during the firmware download Do not disconnect the power supply of the device during the firmware download Configu
204. ll as the first coil 1 bit value has address 0 the second register as well as the first coil has address 1 etc independed of the used function code The following table shows the address assignment for registers and coils for zero based Modbus RTU Master The setting Map FC 1 and FC 3 is not set in the configuration of the netTAP or netBRICK device in this case IN netTAP or i OUT netTAP Coil Register netBRICK or netBRICK Fc 2 FC 4 Mapping Mapping OUT 624 9985 9998 Table 52 Access from the Modbus RTU Master using Zero based Addressing 1 The following table shows the address assignment for registers and coils for zero based Modbus RTU Master The setting Map FC 1 and FC 3 is set in the configuration of the netTAP or netBRICK device in this case IN netTAP or i Register OUT netTAP Coil Register netBRICK FC 3 or netBRICK FC 1 FC3 Mapping FC 6 Mapping Fo2 FC 4 FC 16 FC 23 lesen FC 23 schreiben 0 15 16 31 32 47 OUT 624 9985 9998 Table 53 Access from the Modbus RTU Master using Zero based Addressing 2 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 204 268 One based addressing The first register 16 bit value as well as the first coil 1 bit value has address 1 the second register as well as the first coil has address 2 et
205. mation Overview Dialog Panes OK Cancel Apply and Help Selecting inserting deleting Table Line Status Bar Icons 1 Descriptions Settings Driver Selection List Parameters Parameters netX Driver gt USB RS232 Connection Parameters netX Driver gt TCP Connection Parameters of the Device Assignment Descriptions of the Dialog Panes Configuration Navigation Area Configuration Device dependent Settings Communication Change of State EtherCAT Slave Parameters XML File Names for netTAP and netBRICK EtherNet IP Adapter Parameters Part 2 EDS File Names for netTAP and netBRICK Open Modbus TCP Parameters Parameter of the Command Table Parameter of the Command Table Access of the Open Modbus TCP Client using Modicon based Addressing 1 Access of the Open Modbus TCP Client using Modicon based Addressing 2 Access of the Open Modbus TCP Client using Zero based Addressing 1 Access of the Open Modbus TCP Client using Zero based Addressing 2 Access of the Open Modbus TCP Client using One based Addressing 1 Access of the Open Modbus TCP Client using One based Addressing 2 POWERLINK Controlled Node Slave Parameters XDD File Names for netTAP and netBRICK PROFINET lO Device Parameters GSDML File Names for netTAP and netBRICK sercos Slave Parameter XML File Names for netTAP and netBRICK CANopen Slave Parameters Part 1 CANopen Slave Parameters Part 2 EDS File Names for netTAP and netBRICK
206. mbined The device performs the following sequence in order to obtain the addresses 1 from a DHCP server if DHCP is checked if a DHCP server provides the requested addresses to the device then the device uses these addresses 2 from a BootP server if BootP is checked if a BootP server provides the requested addresses to the device then the device uses these addresses 3 the addresses manually set are used If the IP Address is set manually also the Network Mask must be set manually The manually set Gateway Address is optional If no DHCP server and no BootP server and no manually set addresses exist then the protocol is not ready for initialization or for operation BootP Default unchecked If checked the device obtains its IP Address Netmask Gateway Address from a BOOTP server DHCP Default unchecked If checked the device obtains its IP Address Netmask Gateway Address from a DHCP server Table 20 Open Modbus TCP Parameters Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 137 268 4 10 2 Open Modbus TCP Client 4 10 2 1 For what does the Command Table serve For the Open Modbus TCP Client the Command Table is a list with commands for the reading or writing of data The Command Table is only relevant if a device works as Client on the Open Modbus TCP From every command line
207. meter Meaning Range of Value Value Device Address Specifies the Modbus RTU Slave device address from which the For Modbus RTU 1 Modbus RTU master device reads out the data or into which it 247 writes the data Default 1 Unit Identifier not relevant here Default 0 Function Code Address Specifies the function code for read and write requests 3 Read Coils FC1 Read Inputs FC2 Read Holding Registers FC3 Read Input Registers FC4 Force Single Coil FC5 Preset Single Register FC6 Force Multiple Coils FC15 Preset Multiple Registers FC16 1 2 3 4 5 6 15 16 Default Read Coils FC1 Address Indicates the data address in the Modbus RTU Slave device The parameter Address contains the register address in the Modbus RTU Slave device The register address is counted for every function code beginning with 0 The following table shows the assignment of the Address to the data address in the Modbus RTU Slave by Function code Data Address Modbus RTU Slave FC 1 FC2 FC4 FC3 FC 5 FC 6 FC 15 FC 16 Parameter 10004 30004 40004 10005 30005 40005 40003 peoo o e de To know which data address with which data of the Modbus RTU Slave devices is provided for reading or for writing refer to the device description of the Modbus RTU Slave device manufacturer 0 65 535 Default 0 Number of Registers Coils Indicates the number of reading or writing data as registe
208. ms can be used when one of the following condition is fulfilled e The send telegram has a fixed structure e The receive telegram has a fixed structure e The polling telegram send telegram without data has a fixed structure and the receive telegram has a fixed structure e The polling telegram send telegram with data has a fixed structure and the receive telegram has a fixed structure The structure of the serial send and receive telegram is specified by configuration The part of the telegram marked as user data is transferred unchanged with a superordinated memory For this data exchange a handshake mechanism has to be used ASCII should not be used when different telegram structures for send telegrams or different telegram structures for receive telegrams or e communication procedures with more complexity are to be used or e the user data needs to be evaluated processed respectively converted Then use Serial with netSCRIPT With Serial with netSCRIPT it can be reached by programming script e that user data is evaluated processed respectively converted e more complex communication procedures and e different telegram structures can be realized Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 210 268 The netTAP NT 50 and NT 100 device respectively the netBRICK NB 100 device as
209. munication Important parameters are MAC ID Baudrate Produced Size Consumed Size Vendor ID Product Type Product Code Major Rev Minor Rev In order that the DeviceNet Master can communicate with the netTAP or netBRICK device as DeviceNet Slave gt Enter at the DeviceNet Master the MAC ID which is configured in the netTAP or netBRICK device gt Enter for the length of output data in the DeviceNet Master the Cons Data Length as set in the netTAP or netBRICK device gt Enter for the length of input data in the DeviceNet Master the Prod Data Length as set in the netTAP or netBRICK device gt You can set at the DeviceNet Master if the Master verifies identification numbers of the DeviceNet Slave named keying This verification can be activated or deactivated at the DeviceNet Master If the verification is used then use or check for the following values for the netTAP or netBRICK device vendor 283 0x011B product code 45 0x2D for NT 50 respectively product code 43 0x2B for NT 100 respectively product code 47 0x2F for NB 100 product type 12 Ox000C major revision 1 minor revision 1 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 184 268 4 21 Configuration PROFIBUS DP Master The netTAP NT 50 NT 100 device respectively the netBRICK NB 100 device as PROFIBUS DP Master ne
210. n At the pane Signal Configuration the data structure and the signal name of the in and output signals is displayed These signal are used for the signal mapping Here for the single signals respectively the names of the signal names are set or the data types are configured SYCON net generates for the signal names default names These names can be overwritten by the user Parameter Range of Value Value Tag Signal name for the single input or output signals String The name can be set by the user Data type Data type of the single input or output signals BIT Depending by the used AS Interface Slave profile the user can select the WORD data type from a list SIGNED16 UNSIGNED 16 etc Default depends on the used protocol IO Type Input or output signal input output Table 73 Explanations to the Dialog Pane Signal Configuration Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Diagnosis 229 268 5 Diagnosis 5 1 Overview Diagnosis The dialog Diagnosis serves to diagnose the device behavior and communication errors For diagnosis the device must reside in online state The Extended Diagnosis helps to find communication and configuration errors when default diagnosis fails Diagnosis Panes The table below gives an overview for the individual Diagnosis dialog panes descriptions Section Pag
211. n Modbus TCP Client has to transfer to and from the Open Modbus TCP Server by reading or writing The Command Table is described in detail in section Open Modbus TCP on page 137 Note To know which data address with which data of the Open Modbus TCP Server devices is provided for reading or for writing refer to the device description of the Open Modbus TCP Server device manufacturer Open the signal configuration dialog Select in the navigation area under the folder Configuration the entry Signal Configuration The signal configuration dialog opens Signal configuration If you want to assign own signal names then enter your signal names Further information is described in section Signal Configuration on page 228 Close configuration dialog Click on OK to save the parameter or click on Cancel if the parameter should not be saved The configuration dialog closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 4 10 1 Open Modbus TCP Parameter 135 268 Bus startup Communication starts automatically Default Automatic Watchdog time Protocol mode Map FC1 and FC3 Provided server connections Client connection watchdog time Response timeout Send acknowledge ment timeout Connect acknowledge ment timeout Close acknowledge ment timeout IP address
212. n of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 74 268 2 5 4 Configuration of the secondary Network If the slave device is not listed in the device catalog then it has to be imported into the device catalog first 2 5 4 1 Expand PROFIBUS DP Slave Device Catalog If you want to use a PROFIBUS DP slave device that is not listed in the device catalog then you have to import the GSD file into the SYCON net device catalog gt Proceed as follows 1 Missing PROFIBUS DP Slave devices can be added to the device catalog using the menu Network gt Import Device Descriptions 2 Select the new GSD file 3 Answer the question Do you want to reload the device catalog with Yes to reload the catalog More information about the device catalog are in the document SYCONnet_netDevice_en pdf in the directory Documentation on the product DVD 2 5 4 2 Insert PROFIBUS DP Slave Device to the PROFIBUS Network gt Go to the device catalog Use drag and drop with one PROFIBUS DP Slave device to insert it at the PROFIBUS bus line The PROFIBUS DP Slave device icon appears at the PROFIBUS network line Secondary network a netLINK NL S1IN DPL lt gt 1 m CB_AB32 DPS CB_AB32 DPS lt 2 gt Figure 54 Proxy Device with Slave 3 Note The NL 51N
213. n the dialog window is closed D Apply The current settings are saved and the dialog window stays open E Help Opens the online help in a separate window Table 14 Settings Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 102 268 4 3 Licenses Using the license dialog you can order licenses for Master protocols or Utilities and download them to your device 4 3 1 Open License Dialog Note A connection to the device is necessary to open the license dialog 1 Open the configuration dialog gt Select from the context menu of the netTAP respectively netBRICK symbol Configuration gt Gateway respectively Configuration gt Proxy The configuration dialog opens 2 Open license dialog Select in the navigation area under the folder Configuration the entry Licensing The license dialog opens Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 103 268 4 3 2 License Dialog In the License pane you can e check which licenses for Master protocols or Utilities are present in the device Position in the figure below e order licenses Positions to e transfer licenses to the device E Master protocols One General Master License
214. nated by a fixed end identifier consisting of one byte When sending this termination character is inserted in the telegram after the data field When receiving this termination character is used to detect the end of the data field The termination character is not part of the data field Telegram end by time Unspecific The end of the data field is done with the character delay time End End of the telegram character consisting of one or more characters ASCIl The information is given as an ASCII character Char or as hexadecimal Hex Hex For the ASCII character ETX enter the hexadecimal value 03 Decimal When sending the end character is inserted in the telegram When receiving the end character is checked for equality Check Checksum CRC8 Any data of the telegram before the checksum are inserted in the initial value zero with the polynomial 1D default and the 1 byte result is used as checksum CRC16 Any data of the telegram before the checksum are inserted in the initial value zero with the polynomial 8005 default and the 2 byte result is used as checksum CRC32 Any data of the telegram before the checksum are inserted in the initial value zero with the polynomial 04C11DB7 default and the 4 byte result is used as checksum Exor Any data of the telegram before the checksum are set off against the initial value zero with exclusive or and the 1 byte result is used as checksum When sending the computed checksum is ins
215. nd Table is a list with commands for the reading or writing of data Response Timeout value specified in milliseconds 10 10000 ms Timeout Only valid for Master mode Defines the maximum waiting time of the Default 1000 master for an answer from the slave Modbus Address Defines the own Modbus address of the Gateway device 1 247 Default 2 Send Retries Defines number of telegram retries when connection fails 0 10 Relevant only for operation as master Default 3 Interface type Serial interface to be used RS232 RS485 RS422 SPI Mode3 Default RS232 RTS Control Signal Rquest to Send can be switched off or on RTS Control Off default See hardware description RTS Control On Baudrate Modbus RTU Network Baud Rate Defines the transmission rate 1 2 kBit s 2 4 kBit s 4 8 kBit s 9 6 kBit s default 19 2 kBit s 38 4 kBit s 57 6 kBit s 115 2 kBit s Stop Bits Stop Bits Defines the quantity of stop bits 1 or 2 to be used in protocol One stop bit default for serial data communication Two stop bits Parity Defines the parity bit for serial data communication None Even Odd Default Even For more see next page Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 193 268 Register Number of register 0 2880 Not editable in protocol mode master Default 2880 Coils Number
216. nd coil has address 10002 etc The following table shows the address assignment for registers and coils for modicon based Modbus RTU Master The setting Map FC 1 and FC 3 is not set in the configuration of the netTAP or netBRICK device in this case IN netTAP or i OUT netTAP Coil Register netBRICK or netBRICK Fc 2 FC 4 Mapping Mapping OUT 0 10001 10016 30001 OUT 1 10017 10032 30002 OUT 2 10033 10048 30003 OUT 624 19985 19999 30625 Table 50 Access from the Modbus RTU Master using Modicon based Addressing 1 The following table shows the address assignment for registers and coils for modicon based Modbus RTU Master The setting Map FC 1 and FC 3 is set in the configuration of the netTAP or netBRICK device in this case IN netTAP Coil Register OUT netTAP Coil Register Register or FC 5 FC 6 or netBRICK FC 1 FC 4 FC 3 netBRICK FC 15 FC 16 Mapping FC 23 Mapping FC 23 read 40001 OUT 0 1 16 10001 10016 30001 40001 e i fe ee e e e fe ee e 17 32 OUT 1 17 32 10017 10032 30002 40002 33 48 jours __ o eo Table 51 Access from the Modbus RTU Master using Modicon based Addressing 2 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 203 268 Zero based addressing The first register 16 bit value as we
217. ndor Table 2 General Device Information 1 4 2 Navigation Area The Navigation Area contains folders and subfolders to open the dialog panes of the DTM Navigation Area i Settings gt Driver Device Assignment Configuration Figure 2 Navigation Area gt Select the required folder and subfolder gt The corresponding Dialog pane is displayed Hide display Navigation E Hiding the navigation area above right side A Show navigation area Opening the navigation area below left side Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Introduction 16 268 1 4 3 Dialog Panes At the dialog pane the Settings Configuration Diagnosis Extended Diagnosis or the Additional Tools panes are opened via the corresponding folder in the navigation area Driver On the pane Driver you can select a driver from the driver list For further information refer to section Driver on page 87 Device Assignment On the pane Device Assignment you must select the device and assign the device to the driver For further information refer to section Device Assignment on page 96 Configuration Setting The Settings pane serves for selection of the protocols for the Gateway respectively the Proxyfunctionality For further information refer to section Settings on page 100 Licensing On the pane Licensing you can verif
218. ndow with a double click on the device icon of the PROFIBUS DP Slave 3 gt The configuration window of the PROFIBUS DP Slave device opens gt Select in the navigation area Configuration gt Modules gt Select from Available Modules the module s and add it them to the Configured Modules to configure the Slave The Configured Modules has to match the configuration of the used PROFIBUS DP slave device More information about the configuration of PROFIBUS DP Slave devices are in the document PROFIBUS Generic_Slave_ DTM_en pdf on the product DVD in section Configuration 2 4 4 4 Configure PROFIBUS DP Master 1 Open the PROFIBUS DP Master Port X3 configuration window gt Select from the context menu of the gateway device symbol the entry Configuration gt PROFIBUS DP Master gt The PROFIBUS DP Master configuration window opens Y netDevice PROFIBUS DP Master netTAP NT 100 RE DP PROXY lt gt 1 P IO Device NT 100 X XX Device ID Ox0B44 g i Vendor Hilscher GmbH Vendor ID 0x011E Navigation rea E 4 Configuration Peg Gus Parameters Profile PROFIBUSDP v Process Data Address Table Station Table Bus Parameters Baud Rate 1500 v kBit s Station Address Slot Time 300 tBit Target Rotation Time Min Station Delay Time 11 tBit Max Station Delay Time 150 tBit GAP Actualization Factor Quiet Time 0 tBit Max Retry Limit Setup Time 1 tBit Highest Station Address HSA B
219. netTAP NT 100 device respectively the netBRICK NB 100 device as EtherCAT Slave needs parameter These parameter can be edited as follows 1 Open the configuration dialog gt Select from the context menu of the netTAP respectively the netBRICK symbol the entry Configuration gt EtherCAT Slave gt The EtherCAT Slave configuration dialog opens 3 In the navigation area the entry Configuration under the folder Configuration is selected and the configuration dialog is displayed 2 Set number of Input Data Bytes and Output Data Bytes Enter in the field Input Data Bytes the number of bytes the EtherCAT Master should send to the netTAP or netBRICK device e g 32 gt Enter in the field Output Data Bytes the number of bytes the EtherCAT Master should receive from the netTAP or netBRICK device e g 64 3 Set more parameter If necessary set more parameter The parameter are described in the following section EtherCAT Slave Parameter on page 125 Note Default values can be used normally for the other parameters Depending on additionally requirements and the design of the EtherCAT network as well as the used devices parameters needs to be adjusted if necessary 4 Open the signal configuration dialog Select in the navigation area under the folder Configuration the entry Signal Configuration 3 gt The signal configuration dialog opens 5 Signal configuration If you want to assign own signal names then enter your si
220. netX Driver gt Save USB RS232 Connection i e only for the selected connection type Save All Saving all settings made in the configuration dialog netX Driver i e for all connection types Table 9 Parameters netX Driver gt USB RS232 Connection Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Settings 92 268 3 2 3 2 netX Driver TCP IP Connection Function and use The communication from the DTM to the device via a TCP IP Connection is used in the following typical application The device has its own Ethernet interface The DTM is installed on a PC and the TCP IP connection is established from this PC to the stand alone device The IP address of the device is used Via the TCP IP interface of the device or of the remote PC the device is configured or diagnosis is performed Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 93 268 Driver Parameters for netX Driver TCP IP Connection The settings of the driver parameters for the TCP IP connection are made via the netX Driver TCP Connection configuration dialog gt Open the TCP Connection dialog via navigation area Settings gt Driver gt netX Driver The dialog netX Driver is displayed gt Select TCP Connecti
221. network Gateway address Cancel Help D gt Disconnected 0 Data Set Figure 46 PROFINET IO Name of Station gt Enter the Name of Station Note The name of station is very important and is used by the PROFINET IO Controller to identify the proxy device 3 Close the configuration window gt Click on the button OK 3 gt The configuration window closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 66 268 2 4 6 Establish a Connection to the Proxy Device 1 Connect the USB cable gt Connect with an USB cable the USB connector of the netTAP device with the USB connector of the PC 2 Select the driver gt Select Settings gt Driver and then check netXDriver 3 gt The following figure shows the selected Driver T netDevice Proxy netTAP NT 100 RE DP PROXY lt gt 1 e 10 Device NT 100 RE DP PROXY Device ID 3p Vendor Hilscher GmbH Vendor ID 0x011E Navigation area m co Settings wp Driver Driver Version ID netX Driver oO CIFX Device Driver 1 0 3 1 368BEC5B 0E92 4C0E B449 64F62AE7AAFA Device Assignment 35Gateway Driver For netX 3 x 0 9 2 0 787CD349 4CF6 4259 8E4D 109B6A6BEA91 3 Configuration netX Driver 1 101 1 1761 B54C8CC F333 4135 8405 6E12FC88EE62 Settings Memory Card Management Licensing Figure
222. network Enter in the field Vendor ID the value 0x011E Enter in the field Device ID for the NT 50 value 0x010F for the NT 100 value 0x010B respectively for the NB 100 value 0x010E Values in the fields Device Type Order ID and Type of Station are optional Note Default values can be used normally for the other parameters Depending on additionally requirements and the design of the PROFINET network as well as the used devices parameters needs to be adjusted if necessary Further information is described in section PROFINET IO Device Parameter on page 155 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 154 268 4 Open the signal configuration dialog Select in the navigation area under the folder Configuration the entry Signal Configuration 3 gt The signal configuration dialog opens 5 Signal configuration gt Ifyou want to assign own signal names then enter your signal names Further information is described in section Signal Configuration on page 228 6 Close configuration dialog Click on OK to save the parameter or click on Cancel if the parameter should not be saved 3 gt The configuration dialog closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 C
223. network as well as the used devices parameters needs to be adjusted if necessary Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 148 268 6 Open the signal configuration dialog gt Select in the navigation area under the folder Configuration the entry Signal Configuration 3 gt The signal configuration dialog opens 7 Signal configuration If you want to assign own signal names then enter your signal names Further information is described in section Signal Configuration on page 228 8 Close configuration dialog Click on OK to save the parameter or click on Cancel if the parameter should not be saved 3 gt The configuration dialog closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 149 268 4 11 1 POWERLINK Controlled Node Parameter Bus startup Communication starts automatically Default Automatic Watchdog time ms This function is not supported by gateway or proxy devices 0 20 65535 ms default 1000 ms 0 Off I O data status Status of the input or the output data Default None For each input and output data the following status information in Byte is memorized in the dual port memory Status 0 None default Status 1 1 Byte fo
224. new data set for a command shall be added gt Click Add 3 Under the clicked line a new command is added Remove command gt Inthe table Command Table put the cursor in the line with the data set to be deleted gt Click Remove 3 The command of the clicked line is not shown any more 4 10 2 4 Setting Parameters valid data registers Refer to the device description of the Open Q Important When entering the parameters make sure that these address Modbus TCP Server device manufacturer To set the single parameters in the Command Table proceed as follows 1 Device Address Function Code Address Number of Registers Coils The fields for these parameters are editable gt Enter the values for these parameters to the corresponding table cells 2 Trigger In Function Code field select an entry for a writing command FC 5 6 15 or 16 gt Inthe column Trigger select the entry Cyclic or Change Data 3 Cycle Time gt Put the cursor to the table cell and set the cycle time using the spin box sa in steps of 10 ms Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 4 10 2 5 142 268 Examples Open Modbus TCP Reading or Writing Command Device Address 192 168 10 101 192 168 10 101 Function Code Address Number of Register Coils Dual Port Memor
225. ngs are exported into a device description file 12 Open the signal configuration dialog gt Select in the navigation area under the folder Configuration the entry Signal Configuration The signal configuration dialog opens 13 Signal configuration gt Ifyou want to assign own signal names then enter your signal names Further information is described in section Signal Configuration on page 228 14 Close configuration dialog gt Click on OK to save the parameter or click on Cancel if the parameter should not be saved 3 gt The configuration dialog closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 161 268 4 15 1 sercos Slave Parameter Bus Startup Communication start automatic Automatic Default Automatic Watchdog Time This function is not supported by gateway or proxy devices Default 0 ms ms 0 Off Device ID Identification number of the device This is a unique device ID managed Default NT_100 by the vendor and identifies the component number The device ID is RE_S3S_FIXCFG fixed for every device Device ID according to the sercos third generation specification as defined in IDN S 0 1300 x 05 The device ID can be changed by the user if an other device ID than the default is useful for the used sercos network Note The device ID is part of the SDDML device des
226. nnection again do the steps described in section Device Assignment on page 34 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 37 268 2 2 12 Save Project gt Note The configuration downloaded from SYCON net into the device can t be uploaded from the device Only the SYCON net project can be downloaded into additional devices Save the SYCON net project In case of a device replacement the saved project can be opened with SYCON net and loaded into the device gt To save a project select menu File gt Save respectively File gt Save As or click on icon mi A When you exit the program and the current configuration differs from the last saved configuration then the following question appears A Save changes to the project wo cma Figure 20 Security Question Save Project When you answer with Yes then the project is saved When you answer with No then the project is not saved and the changes are lost When you answer with Cancel then the project is not saved Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 38 268 2 3 Configuration of a NT 100 or NB 100 as a Gateway This secti
227. ode Gateway GSD GSD file GSDML GSDML file Half duplex A communication system for industrial Ethernet designed and developed by B amp R It partly uses CANopen technologies Field Device Tool FDT specifies an interface in order to be able to use DTM Device Type Manager in different applications of different manufacturers Full duplex denominates a telecommunication system between two communication partners which allows simultaneous communication in both directions is called a full duplex telecommunication system At such a system it is possible to transmit data even if currently data are received Full duplex is the opposite of Half duplex A function code in the meaning defined by Modbus terminology is a standardized method to access i e read or write coils or registers via Modbus A device interfacing between two different communication standards Generic Station Description Device description file A special kind of Device Description File used by PROFIBUS GSD Generic Station Description Generic Station Description Markup Language XML based device description file A special kind of XML based Device Description File used by PROFINET Half duplex denominates a telecommunication system between two communication partners which does not allow simultaneous but alternating communication in both directions is called a_half duplex telecommunication system At such a system receiving data inhibits the
228. odes 8 3 1 RCX General Task Errors 242 268 Error Code Definition Value Description RCX_E_QUE_UNKNOWN 0xC02B0001 Unknown Queue RCX_E_QUE_INDEX_UNKNOWN 0xC02B0002 Unknown Queue Index RCX_E_TASK_UNKNOWN 0xC02B0003 Unknown Task RCX_E_TASK_INDEX_UNKNOWN 0xC02B0004 Unknown Task Index RCX_E_TASK_HANDLE_INVALID 0xC02B0005 Invalid Task Handle RCX_E_TASK_INFO_IDX_UNKNOWN 0xC02B0006 Unknown Index RCX_E_FILE_XFR_TYPE_INVALID 0xC02B0007 Invalid Transfer Type RCX_E_FILE_REQUEST_INCORRECT 0xC02B0008 Invalid File Request RCX_E_TASK_INVALID 0xC02B000E Invalid Task RCX_E_SEC_FAILED 0xC02B001D Security EEPROM Access Failed RCX_E_EEPROM_DISABLED 0xC02B001E EEPROM Disabled RCX_E_INVALID_EXT 0xC02B001F Invalid Extension RCX_E_SIZE_OUT_OF_RANGE 0xC02B0020 Block Size Out Of Range RCX_E_INVALID_ CHANNEL 0xC02B0021 Invalid Channel RCX_E_INVALID_FILE_LEN 0xC02B0022 Invalid File Length RCX_E_INVALID_ CHAR_FOUND 0xC02B0023 Invalid Character Found RCX_E_PACKET_OUT_OF_SEQ 0xC02B0024 Packet Out Of Sequence RCX_E_SEC_NOT_ALLOWED 0xC02B0025 Not Allowed In Current State RCX_E_SEC_INVALID_ZONE 0xC02B0026 Security EEPROM Invalid Zone RCX_E_SEC_EEPROM_NOT_AVAIL 0xC02B0028 Security EEPROM Eeprom Not Available RCX_E_SEC_INVALID_CHECKSUM 0xC02B0029 Security EEPROM Invalid Checksum RCX_E_SEC_ZONE_NOT_WRITEABLE 0xC02B002A Security EEPROM Zone Not Writeable
229. odules for output data has to match with the number of output data configured in the netTAP or netBRICK device The PROFINET IO Controller verifies identification numbers of the netTAP respectively netBRICK device Vendor ID value 0x011E 286 device type value for NT 50 is Ox010F 271 value for NT 100 is 0x010B 267 value for NB 100 is 0x010E 270 The PROFINET IO Controller gets these numbers from the GSDML file name see above Vv Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 157 268 4 14 Configuration PROFINET IO Device Proxy The NT 100 device respectively the netLINK NL 51N DPL device as proxy with PROFINET IO Device needs parameter The number of input and output data for PROFINET IO result from the configuration of the PROFIBUS by the used PROFIBUS DP slave devices and the used I O modules per slave device The configuration of the device for PROFINET IO is determined by the configuration of the PROFIBUS network In this process the station address of a PROFIBUS DP slave device is mapped as slot module on PROFINET IO The IO module of the respective slave device are mapped on PROFINET as subslot modules ieee BJU S Cyclic Communication P Gateway Number of Station Slot Number Station Address SubSlot Modul Figure 98 PROFINET PROFIBUS Adress Mapping Only the n
230. of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC081201006EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Error Codes 257 268 ODM Error Codes DBM V4 Error Code Definition Value Description CDBM_E_DBM_FILE_OVERFLOW 0XC004C861 You try to write a RCS like database which needs too much bytes CDBM_E_PW_ERROR OXC004C862 Password not correct CDBM_E_FILELENGTH_CORRUPT OXC004C863 The file length doesn t correspond to the length given in the Header CDBM_E_STRUCT_TYPE OXC004C864 Error in the file CDBM_E_MD5SUM_INVALID OXC004C865 MD5 sum invalid CDBM_E_STRUCT_LENGTH OXC004C866 Error in the expected and given structure length at a specific offset in the file CDBM_E_APPEND 0XC004C867 Append of data is only allowed if the Record contains only one data field and the field type will support this CDBM_APPEND_NOT_ SUPPORTED OXC004C868 Append of Data not supported by this filed type CDBM_DATA_TYPE_APPEND_ ERROR OXC004C869 Can t append Data of this type CDBM_E_UNSTRUCTURED_TABLE _ OXC004C86A A Table without structure information DOESNT_SUPPORT_LENGTH doesn t support a record length CDBM_E_DISABLED_WHILE_ OXC004C86B The Method is disabled while a transaction TRANSACTION_IS_OPEN is open Please close this one first and call the Method again CDBM_E_UNABLE_TO_CALL_ OXC004C86C The Method is disabled
231. of coils 0 65535 not editable Default Automatic Table 47 Modbus RTU Parameters Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 194 268 4 23 2 Modbus RTU Master 4 23 2 1 For what the Command Table does serve For the Modbus RTU Master the Command Table is a list with commands for the reading or writing of data The Command Table is only relevant if a device works as Master on the Modbus RTU From every command line the Modbus RTU Master produces a telegram for reading or for the writing of data to or from a Modbus RTU Slave device For every command are indicated e the Modbus RTU Slave device address Device Address e the Function code e the data address in the Modbus RTU Slave device Address e the number of data Number of Registers Coils e and the data address in the Modbus RTU Master device Memory Address internal For writing telegrams FC 5 6 15 and 16 in the column e Trigger you can decide whether the writing telegrams are executed every time Cyclic or only at data modification Change data Furthermore e a Cycle Time can be set for every command The Command Table is processed from the first to the last entry from above to below After the execution of the last command the execution of the first command is started again For reading commands the Modb
232. ommand Table Figure 100 Examples Reading Command with FC 3 Writing Command with FC16 Figure 101 Examples Reading Command with FC 3 Writing Command with FC16 Figure 102 Access from the Modbus RTU Master to the netTAP and netBRICK Device Figure 103 Navigation Area Diagnosis Figure 104 General Diagnosis Figure 105 Firmware Diagnosis The name of the Firmware is displayed Figure 106 PROFINET PROFIBUS Address Mapping Figure 107 PROFINET IO PROFIBUS DP Read Write Error Detection Figure 108 PROFINET IO PROFIBUS DP Alarm Errors Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public 260 268 77 78 79 80 81 82 83 85 86 87 87 87 Hilscher 2009 2014 Appendix 9 3 Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16 Table 17 Table 18 Table 19 Table 20 Table 21 Table 22 Table 23 Table 24 Table 25 Table 26 Table 27 Table 28 Table 29 Table 30 Table 31 Table 32 Table 33 Table 34 Table 35 Table 36 Table 37 Table 38 Table 39 Table 40 Table 41 Table 42 Table 43 Table 44 Table 45 Table 46 Table 47 Table 48 Table 49 Table 50 Table 51 Table 52 Table 53 Table 54 Table 55 Configura List of Tables Descriptions Dialog Panes General Device Infor
233. on USB RS232 Connection TCP Connection V Enable TCP Connector Restart of ODM required Select IP Range IP_RANGEO 7 IP Range Configuration Disable IP Range Scan Timeout 100 ms IP Address Use IP Range TCP Port Address Count 192 168 1 1 50111 fi Send Timeout 1000 ms Keep Alive Timeout 2000 ms Reset Timeout 20000 H ms Restore Save Save All Figure 70 netX Driver gt TCP Connection Range of Value Value Parameter Meaning Enable TCP Connector checked The netX Driver can communicate via the TCP IP Restart of ODM interface required unchecked The netX Driver can not communicate via the TCP IP interface If the check mark for Enable TCP Connector is set or removed then the ODM server must be restarted to make the new setting valid 1 Restart the ODM server via the ODMV3 Tray Application In the foot line click to g using the right mouse key In the context menu select Service gt Start checked unchecked Default unchecked Select IP Range Via Select IP Range already created IP ranges can be selected Via an additional IP range can be added Via LJ an IP range can be deleted Scan Timeout ms With the scan timeout can be set how long to wait for a response during a connection is established 10 10000 ms Default 100 ms IP Range Configuration Disable IP Range checked No connection unchecked The net
234. on Sequence for Gateway and Proxy 42 268 3 Select the protocol for the primary network and for the secondary network and apply gt Select in gt Click the button Apply the window Configuration gt Settings at Protocol Combinations for the Primary Network Port X2 the protocol PROFINET IO Device gt Select then at Protocol Combinations for the Secondary Network Port X3 the protocol PROFIBUS DP Master 3 gt The Gateway configuration window shows the following a netDevice Gateway netTAP NT 100 XX XX lt gt 1 IO Device NT 100 XX x Vendor Hilscher GmbH Navigation area Settings General Driver netX Driver Description Device Assignment Configuration tay Settings Signal Mapping Memory Card Management Licensing Protocol Combinations Required gateway Required license Available Firmware Software class Software version Basic Settings Mapping Cycle time Network Address Switch Enable Used by Figure 25 Gateway Protocol Selection 2 Primary network Port X2 Device ID vendor ID 0x011E netTAP PROFINET IO Device NT 100 RE DP Yes 1 _7 Secondary network Port X3 PROFIBUS DP Master NTPNSDPM NXF Multi protocol combinable Gateway 1 5 5 0 1 ms r Browse ewe eiaa Mapping mode mw e The entry Memory Card Management in the navigation area is only available for netTAP NT 100 devices T
235. on a LinkedList READ_ON_LINKED_LIST type Please use the IRecordCollection on this type CDBM_E_ELEMENT_HAS_NO_ 0XC004C86D An Element from a Table has no SUBSTRUCTURE substructure CDBM_STRUCT_ERROR_FROM OXC004C86E Error from calling VariantChangeType VAR_CHANGE_TYPE CDBM_E_FOREIGNKEY_DEF OXC004C86F The definition of a FOREIGNKEY must contain the name of the related Table in the description and this Table must exist at this time CDBM_E_FOREIGNKEY_ REF_TAB 0XC004C870 The description of a FOREIGNKEY must refer to a Table of type eDbmTableTypeLinkedList CDBM_E KEY 0XC004C871 To create a Record Collection with a KEY it s necessary to have the data type KEY at the first position in all Records of the searched Table CDBM_E_KEY_TABLE_TYPE 0XC004C872 This Method needs a Table of type eDbmTableTypeLinkedList CDBM_DATATYPE_NOT_ IMPLEMENTED 0XC004C873 This data type is currently not implemented CDBM_INSERT_POS_NOT_ FOUND 0XC004C874 The position of the Record where the new one should be inserted wasn t found CDBM_E_INSERT_REC_Ql 0XC004C875 Error during insertion of a Record CDBM_E_TAB_PROP 0XC004C876 Invalid Property in Table CDBM_E_KEY_NOT_FOUND 0XC004C877 The KEY wasn t found in the Table CDBM_E_KEY_INVALID 0XC004C878 The KEY is invalid for this operation Table 94 ODM Error Codes DBM V4 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010106EN Revision 6 English 2014 04 Rel
236. on area E Settings E Driver netx Driver _ 7 EUG Device selection suitable only Configuration Settings Device Hardware Ports O 1 Serial nu _ Driver Channel Protocol Access path Signal Mapping Scan progress 3 3 Devices Current device Access path Cancel Help Figure 7 Device Assignment without Device Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 23 268 2 Open dialog for protocol selection gt Select in the navigation area Configuration gt Settings The configuration window Settings opens anetDevice Gateway netTAP NT 50 XX XX lt gt 1 IO Device NT 50 XX Xx Device ID vendor Hilscher GmbH vendor ID 0x011E Navigation area Ap a Settings General 9 Driver net Driver Description netTAP K Device Assignment 4 Configuration iy pettings Signal Mapping Protocol Combinations Primary network Port x2 x Secondary network Port x3 J Required gateway X Required license Available Firmware NSASCEIM NXF Browse NSASCEIS NXF NSASCOMB NXF NSASCPNM NXF NSASCPNS NXF NSBASEFW NXF Software class Software version Basic Settings Mapping Cycle time 10 ms Mapping mode l r Network Address Switch Enable ie Used by Figure 8 Gateway Protocol Selection 1
237. on is valid for netTAP NT 100 and netBRICK NB 100 devices as a gateway These devices are called gateway devices in the following description The configuration of a netTAP NT 100 device is described as example Differences and extras to other devices are pointed out respectively are described in own sections The configuration of the NT 100 devices is explained exemplarily with the protocol conversion PROFINET IO Device to PROFIBUS DP Master The device NT 100 RE DP with one master license is necessary for the protocol conversion from PROFINET IO Device to PROFIBUS DP Master The following steps have to be done to configure the device 2 3 1 Start SYCON net and User Login 1 Start SYCON net gt Select Start gt Programs gt SYCON net System Configurator gt SYCON net 3 SYCON net is started 2 User Login gt In the window SYCON net User Login click OK to login or enter your password and then click OK to login SYCON net frame application appears Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 39 268 Insert the Gateway Device into the Configuration Window gt Go to the device catalog under vendor Hilscher GmbH to the category Gateway Stand Alone Slave Use drag and drop with the NT 100 XX XX respectively NB 100 XX XX gateway device to insert it at the
238. on only Software version The firmware version of the selected firmware is displayed Settings Mapping Cycle time 1 1000 ms Default 1 ms is the cycle time for the device internal transfer of the input and output data from the buffer of port X2 to the buffer of X3 and visa versa olob Mapping mode Always default only displayed Netzwork Address Switch enable a Not checked default The address is set by the configuration software and transferred by a download into the device M Checked The address is used from the slave protocol which is set by the rotary switches at the device and can be used fort he following protocols CANopen Slave to set the node address CC Link Slave to set the station address DeviceNet Slave to set the MAC ID and PROFIBUS DP Slave to set the station address Firmware version 1 1 or higher is required for the netTAP NT 50 device Firmware version 1 5 or higher is required for netTAP NT 100 device The address set and downloaded by the configuration software is always used for master protocols Used by When two slave protocols are used then you have to set if the address switches are valid for the primary network or for the secundary network Common Buttons E OK The current settings are saved and then the dialog window is closed a Cancel The changed settings are discarded and the
239. onfiguration 155 268 4 13 1 PROFINET IO Device Parameter Bus startup Communication starts automatic Default Automatic Watchdog time ms This function is not supported by gateway or proxy devices 0 20 65535 ms default 1000 ms 0 Off I O data status Status of the input or the output data Default None For each input and output data the following status information in Byte is memorized in the dual port memory Status 0 None default Status 1 1 Byte for future use Status 2 4 Byte for future use Enable If Enable is unchecked for the single Ident parameters each the respective default value is used Vendor ID Identification number of the manufacturer assigned by 0x00000000 PROFIBUS Nutzerorganisation e V OxFFFFFFFF hex Hilscher 0x00000011E hex Device ID Identification number of the device fixed for every device 0x00000000 0x0000FFFF hex Default NT 50 EN PNS Gateway 0x0000010F hex NT 100 RE PNS Gateway 0x00000010B hex NT 100_RE PNS Proxy 0x000000106 hex NB 100 RE PNS Gateway 0x00000010E hex Device type Description of the device type freely eligible Character string 0 25 characters Order ID Hilscher device number or order description of the customer Character string for its device 0 20 characters Name of station Station name of the PROFINET IlO Device station It has to Character string match the station name configured in the PROFINET IO 1
240. or COM based application like the ODM Server and ODM drivers a common error definition is used similar to the Microsoft Windows HRESULT definition Error Code Structure COM Errors are HRESULTs which are 32 bit values using the following layout 3 Be 22 2 2 2 22 2 2 Deke DD ED Td Bed Dd 1098 7654321098765 43214098765 432i10 Sev c R Facility Code where Sev is the severity code 00 Success 01 Informational 10 Warning 11 Error Cc is the Customer code flag R is a reserved bit Facility is the facility code Code is the facility s status code In this common error definition several error code regions are already reserved by Windows itself the ODM and some other modules Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Error Codes 241 268 8 2 Overview Error Codes eee Table 81 Overview Error Codes and Ranges ABA The fieldbus specific error codes are described in the manuals of the Aa corresponding protocol tasks Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Error Codes 8 3 General Hardware Error C
241. ort 0 1 2 3 Slot number Serial number of the device Name of the driver Channel Protocol Access path under Device selection last column on the right Access path at the lower side of the dialog pane Shows which hardware is assigned to which communication interface Shows the Slot Number Card ID preset at the cifX card via the Rotary Switch Slot Number Card ID The indication n a means that no Slot Nummer Karten ID exists This occurs if the cifX card is not equipped with a Rotary Switch Slot Number Card ID or for cifX cards equipped with a Rotary Switch Slot Number Card ID if the rotary switch is set to the value 0 zero or all other device types Shows which firmware is loaded to which device channel The data for the used channel consists of the protocol class and the communication class a For devices without firmware Undefined Undefined b For devices with firmware Protocol name corresponding to the used Firmware Depending on the used driver in the column Access path different data to the device are displayed For the cifX Device Driver the following data are displayed a For devices without firmware cifX OftoN _SYS b For devices with firmware cifX OtoN _Ch 0to3 cifX OtoN Board number 0 to N Ch 0to3 Channel number 0 to 3 If under Device selection the check box for a device is checked under Access path at the lower side of the dialog pane the driver iden
242. ory Figure 79 License Pane Request Form please fill out Device Information These ordering data read out from the device are displayed automatically from the device Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 108 268 4 3 6 2 Data to manage the Order License Information For your order you must enter the following data to the License pane 1 Request Form please fill out License Type User Single Device License Value a License type User Single Device License Figure 80 License Pane Request Form please fill out License Type gt Request Form please fill out Select the license type under Request Form please fill out gt Value for future application currently only User Single Device License can be selected Mandatory data to the order request editable fields First Name Surname E Mail address to which the license download link shall be send Telephone Company Address Country City State Zip John Doe License doe com 0011223344 55 0011223344 100 123456789 Doe Example LTD v Fields marked with are mandatory Figure 81 License Pane Request Form please fill out Mandatory data gt Enter all mandatory fields under Request Form please fill out gt Value marked with Additional order data not mandatory edi
243. ot monitored Character Specifies whether the time between two characters 0 231 1 Delay Time during reception is monitored by time Default 0 The value unequal to zero specifies in what time the remote device must have sent the next character If the time is exceeded then an error is reported to the host The value 0 specifies that no monitoring is performed Table 66 Timing Parameters for the Operating Receive Only Mode Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 220 268 Configuration Example Send Only Mode d Client Mode Server Mode Receive Data Stream Configuration Start Hex y 02 Data Constant Length bytes _yifia Check v CRCIB 0 8005 Receive Buffer Size ___si2 bytes Pu ale ee ee fee ee lee feu character Delay Time __0 ms ue Signal Configuration Enabled Receive Watchdog Time 0 ms Table 67 Telegram Structure for the Operating Receive Only Mode Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010I06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 221 268 4 25 2 6 Client Mode First Send Then Receive Basic Principle In the Client Mode the device sends a telegram to the remote device The remo
244. out ms Maximum time for a device reset including the re initialization of the physical interface used for the communication 100 60 000 ms Default TCP IP 2000 ms Keep Alive Timeout ms The Keep Alive mechanism is used to monitor whether the connection to the device is active Connection errors are detected using a periodic heartbeat mechanism The heartbeat mechanism is initiated after the set time has elapsed if the communication has failed 100 60 000 ms Default TCP IP 2000 ms Restore Resets all settings in the configuration dialog to the default values Save Saving all settings made in the configuration dialog netX Driver gt Save TCP IP Connection i e only for the selected connection type Save All Saving all settings made in the configuration dialog netX Driver i e for all connection types Table 10 Parameters netX Driver gt TCP Connection Note Do not use large IP ranges in combination with a low scan timeout Microsoft introduced in Windows XP SP2 a limit of concurrent half open outbound TCP IPconnections connection attempts to slow the spread of virus and malware from system to system This limit makes it impossible to have more than 10 concurrent half open outbound connections Every further connection attempt is put in a queue and forced to wait Due to this limitation a large IP range used in combination with a low scan timeout could prevent
245. ows the following figure A Gateway net TAP NT 100 RE DP lt gt 1 e IO Device a Vendor Navigation area E Settings 8 Driver TCPHIP Driver For netx Device Assignment Configuration Settings Licensing tay Signal Mapping Memory Card Management NT 100 RE DP Hilscher GmbH Device ID Vendor ID 0x011E Available Signals Status Port x3 Generated Generated Generated Generated Goner sted E 128 Bytes Out lt Slot 2 gt Port x2 Signals 4 SlaveDiag 016 SlaveDiag 024 SlaveDiag 032 SlaveDiag 040 SlaveNian NAR Signals Data type UNSIGNEDS UNSIGNEDS UNSIGNEDS UNSIGNEDS LINSTCNENS Send Send Send 128 InBytes BYTE_0006 128 InBytes BYTE_OOO7 A198 TnRukee RVTF NANNA Mapped Signals HE CB_AB32 DPS lt Addr 2 gt F5 Status 128 Bytes In lt Slot 1 gt H 128 Bytes Out lt Slot 2 gt Port x3 PROFIBUS DP 128 Bytes In lt Slot 1 gt 7128 InBytes BYTE_O000 CB AB32 DPS lt Addr 2 gt 2 byte input output lt Slot 1 gt Input 0001 128 Bytes In lt Slot 1 gt 128 InBytes BYTE_0001 128 Bytes Out lt Slot 2 gt 128 OutBytes BYTE_O000 128 Bytes Out lt Slot 2 gt 128 OutBytes BYTE_O001 128 Bytes In lt Slot 1 gt 128 InBytes BYTE_O0002 128 InBytes BYT CB_AB32 DPS lt Addr 2 gt 2 byte input output lt Slot 1 gt Input_0002 CB_AB32 DPS lt Addr 2 gt 2 byte input output lt Slot 1 gt Output_O0C CB_AB32 DPS lt Addr 2 gt 2 byte input output lt Slot 1 gt
246. oxy Devices netTAP netBRICK and netLINK DOC0812010106EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 52 268 2 3 8 Device Assignment gt Select Settings gt Device Assignment gt Click on Scan The search process is started Devices found are display in a list then ZnetDevice Gateway netTAP NT 100 XX XX lt gt 1 IO Device NT 100 XX XX Device ID ao Vendor Hilscher GmbH Vendor ID 0x011E Navigation area E Settings E Driver netX Driver Mad C Device selection suitable only x Configuration Settings Device Hardware Ports 0 17 Slot nu Serial nu f Driver Channel Protocol Access path Signal Mapping NT 100 RE DP Ethernet Ethernet P nja 20060 netX Driver Gateway COM3_cifx0 Memory Card Management Licensing Scan progress 4 4 Devices Current device Access path B54C8CC7 F333 4135 8405 6E12FC8BEE62 COM3_cifxO_Ch2 Cancel Help Save operation succeeded Figure 34 Select Device gt Select the device from the list by a check in the field of the device as shown above gt Click on OK 3 gt The configuration window closes The entry Memory Card Management in the navigation area is only available for netTAP NT 100 devices Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher
247. p For this drag the status signal Port X3 generated and drop it on the signal to be sent Port X2 send 3 gt An example of the Signal Mapping window shows the following figure J netDevice Gateway netTAP NT 50 DP RS lt 2 gt 1 10 Device Vendor Navigation area g E Settings E Driver netx Driver Device Assignment E Configuration Settings Port x2 2ignal Mapping NT 50 DP RS Hilscher GmbH Available Signals J 32 Bytes Out lt Slot 1 gt Signals Data type Send InByte_0000 BYTE Communication Change of UNSIGNED32 Communication State UNSIGNED32 Communication Error UNSIGNED32 Generated Generated Generated lt Mapped Signals 32 Bytes Out lt Slot 1 gt OutByte OO00 OutByte 0001 32 Bytes Out lt Slot 1 gt OutByte_0002 OutByte_0003 32 Bytes Out lt Slot 1 gt OutByte_0004 OutByte_0005 Manual Mapping Remove link Save operation succeeded Figure 14 Gateway Signals mapped Device ID vendor ID 0x011E H 256 Registers In lt Slot 0 gt P Port x3 Signals __ Data type Send 256 InWORDs WORD_O WORD Send 256 InWORDs WORD_O WORD Send 256 InWORDs WORD_O WORD Send 256 InWORDs WORD 0 WORD tay 256 Registers In lt Slot 0 gt 256 InwORDs wORD_0001 tay 256 Registers In lt Slot 0 gt 256 InwWORDs WwORD_0002 Auto Mapping off X Cancel Help Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010106EN Revision 6 English
248. pears A Save changes to the project wo Coren Figure 51 Security Question Save Project When you answer with Yes then the project is saved When you answer with No then the project is not saved and the changes are lost When you answer with Cancel then the project is not saved Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 71 268 2 4 11 Device Description File to configure the PROFINET lO Controller A GSDML file is required to configure the PROFINET IO Controller This file is creates as follows gt o vvv Y Select from the context menu of the proxy device symbol the entry Additional Functions gt PROFINET IO Device gt Export GSDML The dialog to save the XML file appears Select the directory the GSDML file should be saved into A name for the GSDML file is proposed Accept it or change it useful Click on Save The GSDML file is saved The structure of the file name is GSDML V2 2 Hilscher netTAP 20100723 113409 xml Q Fixed prefix Version number of the GSDML specification Manufacturer name Device type Date Format yyyymmdd Time Format hhmmss File extension always xml gt Use the GSDML file to configure the PROFINET IO Controller Configuration of Gateway and Proxy Devices netTAP netBRICK and net
249. pears in the navigation are 3 Set Modbus RTU Parameter gt Set or select in the configuration dialog the Modbus Address the interface type RTS control baudrate number of stop bits and parity for the netTAP or netBRICK device The settings are described in the following section Modbus RTU Parameter on page 192 gt lf you have set the Protocol Mode to Master then set the response timeout and the send retries 4 Command Table If you have set the Protocol Mode to Master then select in the navigation area the entry Command Table Specify in the Command Table which data the Modbus RTU Master has to transfer to and from the Modbus RTU Slave by reading or writing The Command Table is described in detail in section Modbus RTU Master on page 194 Slave devices is provided for reading or for writing refer to the device Note To know which data address with which data of the Modbus RTU description of the Modbus RTU Slave device manufacturer Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 191 268 5 Open the signal configuration dialog gt Select in the navigation area under the folder Configuration the entry Signal Configuration 3 gt The signal configuration dialog opens 6 Signal configuration gt Ifyou want to assign own signal names then enter your signal names Further
250. project can be downloaded into additional devices Save the SYCON net project In case of a device replacement the saved project can be opened with SYCON net and loaded into the device gt To save a project select menu File gt Save respectively File gt Save As or click on icon mi When you exit the program and the current configuration differs from the last saved configuration then the following question appears A Save changes to the project wo cma Figure 62 Security Question Save Project When you answer with Yes then the project is saved When you answer with No then the project is not saved and the changes are lost When you answer with Cancel then the project is not saved Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 84 268 2 5 10 Device Description File to configure the PROFINET lI Controller A GSDML file is required to configure the PROFINET IO Controller This file is creates as follows gt o vvv Y Select from the context menu of the proxy device symbol the entry Additional Functions gt PROFINET IO Device gt Export GSDML The dialog to save the XML file appears Select the directory the GSDML file should be saved into A name for the GSDML file is proposed Accept it or change it useful Click on Save The GSDML
251. r Access path below in the dialog pane the access path to the device e g the driver identification or depending on the used driver additional access data of the device are displayed 2 Select the Apply button to apply the selection Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 99 268 4 Configuration 4 1 Overview Configuration Configuration Dialog Panes The table below gives an overview for the Configuration dialog panes descriptions Ce Signal Mapping 115 Memory Card Management Table 12 Descriptions of the Dialog Panes Configuration E Configuration w EE Licensing Signal mapping Memory Card Management Figure 73 Navigation Area Configuration The following table shows the configuration panes for each device type Device Type Configuration NT 50 as gateway 3 Configuration Settings Signal Mapping NT 100 as gateway J Configuration Settings Signal Mapping Memory Card Management Licensing NT 100 as proxy J Configuration Settings Memory Card Management Licensing NB 100 as gateway Configuration Settings Signal Mapping Licensing NL 51N DPL as proxy J Configuration i Settings Table 13 Navigation Area Configuration Device dependent Configuration of Gateway and Proxy Devices netTAP netBRICK and ne
252. r Selection List Driver Selection List recognized or installed Drivers Driver Selection List Driver s selected Navigation Area Settings netX Driver gt USB RS232 Connection netX Driver gt TCP Connection Device Assignment detected Devices Device Assignment Selecting the Device Navigation Area Configuration Settings License Pane License Pane License Type License Pane License Type Master protocols License Pane License Type Utilities License Pane Request Form please fill out Device Information License Pane Request Form please fill out License Type License Pane Request Form please fill out Mandatory data License Pane Selecting the Subsidiary Ordering Contacts License Pane placing the order by E mail Example Order E Mail License request License Pane placing the order by Fax or by Telephone Example Order Data Form PrintOrderRequest License Pane Fax Number of the selected Subsidiary License Pane Telephone Number of the selected Subsidiary License Pane Ordering by exported File and E Mail License Pane Download License Signal Mapping Status information of the Master Status information of the Slave Pane Command Table Examples Reading Command with FC 3 Writing Command with FC16 Examples Reading Command with FC 3 Writing Command with FC16 Access of the Open Modbus TCP Client to the netTAP and netBRICK Device PROFINET PROFIBUS Adress Mapping Pane C
253. r YES oO E I DeviceNet Master YES Oo AS Interface Master YES oO PROFINET IN AT Controller YEG m Mi Figure 77 License Pane License Type Master protocols gt Or click at Utilities The Utilities overview opens License Type i HE OPC Server NO Oo amp SYCON net NO Oo OVis Minimum Size NO o OVis Standard Size NO oO p j OVis Maximum Size NO oO te fiaGue kdn Cie Nn m v Figure 78 License Pane License Type Utilities gt The column Existing indicates which licenses are present in the device Yes License is present in the device No License is not present in the device i gt Note In newer versions of the present configuration software under License Type may be displayed additional licenses or other protocols that can be ordered later Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 4 3 3 1 License for Master Protocols One General Master License 105 268 On the device maximally 1 communication protocol with master function can be implemented Two General Master Licenses On the device maximally 2 communication protocols with master function can be implemented The license includes the following Master protocols e AS Interface Master e CANopen Master e DeviceNet Master e EtherCat Master e EtherNet IP Scanner e PROF
254. r cies sctitencestnanarstnaet aaeeaeecnaets 226 4 26 1 NEtSCRIPTSOninS iis scecceasscccciasdeacveasaenedveasacvended aa saveadececeivasanedeasaeceeead EEREN EET 227 4 26 2 Settings for the netSCRIPT Remote Device ccccceeeeseeteeteeteteeeeeneeeeaes 227 4 27 Signal Configuration 3 5 hes test tear aed ah aiaeath eat eahceh at dectosaeteee edu aecaae ken Saat 228 5 GIN he AEE E EE E E EA E E A elas 229 5 1 Overview Diagnosi Seere cd tol dea aaaea rae a Aea a aoa vee aoe 229 5 2 General DiagniSi Sienan e e A E E aa aN 230 5 3 Firmware DiAQnOSIS issie eeren iinnakia seteriai isasara dana ATEAK RAAN EAE Eakin 232 6 ONEINE PUNG TIONS rma r eea a a a a E aa a oaa a aaea Toar 233 6 1 Connecting Disconnecting Device ssssesssseseeessrrrrrerrrntrsrtrrtssrernnerrnentssrrrnsrren nne 233 6 2 Download Configuration eect ela seccascciue Pease teetines dacs edaed ye Wi eieest Coe tede near Secmeinaceeh au nauee 235 7 ACYCLIC PROXY COMMUNICATION cccccessseceeccesseeeeeeeeseeeeesenseeeeeeeneeeenes 236 7 1 Adress Mapping erene onr aa aya raed aa aeaa st chad AARAA ATANAN T aari Fae 236 7 2 Read Write Controlled by the PROFINET IO Controller ccecceeseeeeeeeeees 237 7 2 1 Error Detection and Error Codes ccccccscsscececececsesseseaececeeseeeseasaeseeeeeeeeees 237 7 3 Alarms Controlled by the PROFIBUS DP Slave cceccceeeeeeeeeeeeeeeeeseneeees 238 8 ERROR ODE S a A a 240 8 1 Error Code Definit
255. r contains information about the current operating status of the communication channel and its firmware 31 30 12 11 Bi wv ells lal 2 1 0 unused set to zero COMM_COS_READY COMM_COS_RUN COMM_COS_BUS_ON COMM_COS_CONFIG_LOCKED COMM_COS_CONFIG_NEW COMM_COS_RESTART_REQUIRED COMM_COS_RESTART_REQUIRED_ENABLE Table 15 Communication Change of State The Communication Change of State Flags have the following meaning Status Meaning Ready Bit 0 The Ready flag is set as soon as the protocol stack is started properly Then the protocol stack is awaiting a configuration As soon as the protocol stack is configured properly the Running flag is set too Running Bit 1 The Running flag is set when the protocol stack has been configured properly Then the protocol stack is awaiting a network connection Now both the Ready flag and the Running flag are set Bus On Bit 2 The Bus On flag is set to indicate to the host system whether or not the protocol stack has the permission to open network connections If set the protocol stack has the permission to communicate on the network if cleared the permission was denied and the protocol stack will not open network connections Configuration Locked Bit 3 The Configuration Locked flag is set if the communication channel firmware has locked the configuration database against being overwri
256. r e a inde ee eee Gees 240 8 2 Overview Error GOdo Senning pena ae e a a a raa a S 241 8 3 General Hardware Error COS cccccccccccccceesceeceseeeseesseesseeesesesesessesssesseesssessseeeeass 242 8 3 1 RCX General Task Errors ccccccccccccecssessesececeeececseseeseceeeeeeecsessesasaeseeeeeeseees 242 8 3 2 RCX Common Status amp Errors Codes cccccccccccccsesssseceseeecesseesesseaeseeeeeeeenees 243 8 3 3 RCX Status amp Error Codes tats ni Heel o ea eee adei 244 8 4 ODM Error GOdeS cernua aaae e a a a aa r E Malad 245 8 4 1 General ODM Error Code cccceccessecececeeeesseaeececeescecsesaeaeceseeeceessaeaaeeesess 245 8 4 2 General ODM Driver Error Codes c cccccccccssssceceeececeecseaeaeceeeeeeeessaeaeeeeeens 246 8 4 3 cifX Driver Specific ODM Error Codes c cceceeeeeeeeeeeeeeeeneeeeeeeeseaeeeeaeeneneeee 247 8 5 Error Codes cifX Device Driver and netX Driver cccccecceeeceeeseeecseeeeeeeeeeeeees 250 8 5 1 Generic Error CodeS eia neiai a ee Belen es es 250 8 5 2 Generic Driver Error Codes ciic2 03 sinni nc Woks Aiea ees eT eels teen 251 8 5 3 Generic Device Error Code nie iaia aae aiaa a a daa iaai a 252 8 6 Error Codes netX Driver a a id ae ed ed 253 8 6 1 CIFX API Transport Error COde S cccccccececeeeeeeeeneeeceeeeeaeseeeeeseeeeseaeeeeeeeeaes 253 8 6 2 CIFX API Transport Header State Error Codes 0 ccccccssseeeeessneeeeessneeeeeees 253 8 7 ODM Error Cod
257. r future use Status 2 4 Byte for future use Disable host Decides whether host triggered update for input data exchange is Default unchecked triggered input data enabled hook checked or disabled hook unchecked exchange Disable host Decides whether host triggered update for output data exchange is Default unchecked triggered output data enabled hook checked or disabled hook unchecked exchange Enable If Enable is unchecked for the single Ident parameters each the respective default value is used Vendor ID Identification number of the manufacturer 0x00000000 OxFFFFFFFF hex Hilscher 0x00000044 hex Serial number Serial number of the device 0x00000000 OxFFFFFFFF hex Default 0x00000000 hex Product code Product code of the device as specified by the manufacturer 0x00000000 OxFFFFFFFF hex Default NT 100 RE PLS 0x00000018 hex NB 100 RE PLS 0x00000017 hex Revision number Revision number of the device as specified by the manufacturer 0x00000000 OxFFFFFFFF hex Default NT 100 RE PLS NB 100 RE PLS 0x00000000 hex Node Id EPL Node ID EPL Ethernet POWERLINK 1 239 Default 1 DNS node name DNS compatible name of the POWERLINK Controlled Node Slave optional Gateway address Gateway address for IP stack Default 192 168 100 254 Input data bytes Length of the input data in byte 1 1490 Byte Default 4 Byte Output data bytes Length of the output data in byt
258. rameter Open Server Sockets must be set from 4 Default to 0 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 138 268 4 10 2 2 Parameter of the Command Table Delay 0 ms Command Table F Device Address Unit Indentifier Number of Register Coils_ _Dual Port Memory Address Cycle Time ms p 192 168 10 101 0 Read Holding Registers FC3 10 12 0 Cyclically a 192 168 10 101 O Preset Multiple Register FC16 30 2 O Changed D 0 Figure 94 Pane Command Table Each command contains the following parameters data address in the Open Modbus TCP Server device Memory Address internal Data address in the Open Modbus TCP Client device Byte address in the process image of the Open Modbus TCP Client device Trigger for writing commands Cycle Time Cycle time Table 21 Parameter of the Command Table Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 139 268 Parameter Meaning Range of Value Value Device Address Specifies the Open Modbus TCP Server device address from For Open Modbus TCP which the Open Modbus TCP Client device reads out the data or 000 000 000 000 into which it writes the data 255 255 255 255 Default 000 000 000 000 Unit Iden
259. ration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 70 268 5 Download of firmware gt Wait until the firmware was transferred completely into the device 6 Close the Gateway configuration window after the download gt Click OK The Gateway configuration window closes 2 4 9 Load Configuration 1 Download configuration gt Select from the context menu of the proxy device symbol the entry Download gt Answer the security question with Yes if the download should start SYCON net builds up an online connection to the device This the indicated by a green highlighted device name 3 gt The configuration is transferred info the proxy device The device performs a reset and then starts with the new configuration 2 4 10 Save Project xy Note The configuration downloaded from SYCON net into the device can t be uploaded from the device Only the SYCON net project can be downloaded into additional devices Save the SYCON net project In case of a device replacement the saved project can be opened with SYCON net and loaded into the device gt To save a project select menu File gt Save respectively File gt Save As or click on icon i When you exit the program and the current configuration differs from the last saved configuration then the following question ap
260. rayed out 1 NRT version 1 is activated Use always value 0 because the NRT channel is not useable with gateway proxy devices Further see next page Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 162 268 Po Configuration parameter for IP communication Po Enabled If Enabled is unchecked for the single Ident parameters each the checked respective default value is used unchecked IP Address Valid IP address for the device Valid IP address If Enabled is unchecked Default setting the device obtains its IP Default for Enabled Address from a DHCP or BOOTP server unchecked If Enabled is checked the device uses the manually entered value This function is not supported by gateway proxy devices Netmask Valid Network mask for the device Valid network mask If Enabled is unchecked Default setting the device obtains its Default for Enabled Netmask from a DHCP or BOOTP server unchecked If Enabled is checked the device uses the manually entered value This function is not supported by gateway proxy devices Gateway Valid Gateway address for the device Valid gateway address If Enabled is unchecked Default setting the device obtains its Default for Enabled Gateway Address from a DHCP or BOOTP server unchecked If Enabled is checked
261. riting or a reading command shall be reexecuted The default value 0 ms means that the command is executed as fast as possible Otherwise the execution can be defined in steps of 10 ms With the cycle time the temporal execution of the command can be influenced If since the last execution of the command the set cycle time or more time has been passed the command is reexecuted If since the last execution of the command less time has been passed then the cycle time the command is skipped If e g from a Modbus RTU Slave data are required only every 10 seconds as these one change only slowly then for the cycle time enter 10 000 ms 0 Cyclic 1 Changed Data Default Cyclic 0 10 20 30 60 000 ms Default 0 ms Delay Between the single commands a delay time can be parameterized This sometimes is necessary to avoid a too high load of the connected Slave devices by a continuous communication 0 The commands are processed without delay 1 60 000 ms Delay time in ms the Modbus RTU Master waits before starting the next command 0 60 000 ms Default 0 Table 49 Parameter of the Command Table Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 198 268 4 23 2 3 Adding removing Command To add or to remove data sets for commands to the Comman
262. rk cccceeeeseeceeeeeceeeeeeaeeseeeeescaeeesaeenenees 27 2 2 7 Configure the Gateway Signal Mapping cceccceceeeeesseeeeeeeeeseeeeenaeeeenees 28 2 2 8 Establish a Connection to the netTAP NT 50 ceccceceeeeeeeseeeeeeeseeeeeeeeeeeeeeees 31 2 2 9 Device ASSIM uesia aaa a aia aa T ai daira 34 2 2 10 Load Firmwalesensiaoeains iiaei oi i ENEN E aE ATEKA 35 2 2 11 Load Config ralo Msisi aa aa aa e aai nia 36 2 2 12 Save Projet oaa a a a a a e a a aaa a EAS 37 2 3 Configuration of a NT 100 or NB 100 as a Gateway ssssssneessnrnneeernererrressrrrnnee 38 2 3 1 Start SYCON net and User LOQiIN cccccecceceeeceeneeeeeeeeeeaeeeeeaeeeeeeeesaeeesaaeeeenees 38 2 3 2 Insert the Gateway Device into the Configuration Window eeseesseeeeseeeee 39 2 3 3 Select the Protocol Conversion of the GateWal cccccssseseeeseteeeeseeeeenees 40 2 3 4 Configuration of the primary NetworK sssssesssesssesssesssesesnsernnsnnsrnnsrnnnrnnnrennes 43 2 3 5 Configuration of the secondary Network cccsccceeeeceeeeeseaeeeceeeeseaeeeeaeeeneees 44 2 3 6 Configure the Gateway Signal Mapping ccccccecseeeeeseeeseeeeessaeeesneeeeneees 47 2 3 7 Establish a Connection to the Gateway Device ccccceeeeeeeeeeeteeeetteeeeeneeees 50 2 3 8 Device ASSIQNIMONN cccceeseececeeeeneeeeeeeeeeeeeeeeeeseeaaaeeeseeeaeseseeaaeeeseeeeeeeteeeseneess 52 Configuration of Gatew
263. rocess Data Address Table Station Table Bus Parameters Baud Rate 1500 v kBit s Station Address Slot Time 300 tBit Target Rotation Time A Min Station Delay Time 11 tBit Max Station Delay Time 150 tBit GAP Actualization Factor Quiet Time 0 tBit Max Retry Limit Setup Time 1 tBit Highest Station Address HSA Bus Monitoring Data Control Time Override slave specific Watchdog Control Time Min Slave Interval Watchdog Control Time ms Calculated Timing Tidi 37 tBit Tid2 150 tBit Values marked with this symbol should be Adjust adjusted to changes in the topology lt Disconnected 9 Data Set Figure 55 PROFIBUS DP Bus Parameter 2 Configure PROFIBUS DP Master gt Set the parameter Set especially under Configuration gt Bus Parameter the bus parameter and under Configuration gt Station Table the station addresses stations addresses of the PROFIBUS DP Slave device Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 76 268 Yr netDevice PROFIBUS DP Master netLINK NL 51N DPL lt gt 1 10 Device NL S1N DPL Device ID Ox0B44 S 5 vendor Hilscher GmbH vendor ID 0x011E DT Navigation rea G E Configuration Bus Parameters Lntictivate Station A Device ee lt a 3 CB_AB32 DPS CB_AB32 DPS Hilscher GmbH Pro
264. rs or coils The maximum value depends from the function code 1 max value Default 1 max value for FC1 2000 Coils FC2 2000 Coils FC3 125 Registers FC4 125 Registers FC5 1 Coils FC6 1 Registers FC15 1968 Coils FC16 123 Registers Memory Address internal Byte address in the process image of the Modbus RTU Master device for input or output data of the Master The configuration software calculates the byte address in the process image of the Master for the input or for the output data automatically Because of this definition for function codes for reading FC 1 2 3 and 4 the data are assigned consecutively in the process image for input data and for function codes for writing FC 5 6 15 and 16 the data are assigned consecutively in the process image for output data 0 5759 Default 0 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 197 268 Parameter Meaning Range of Value Value Trigger Cycle Time Defines for all function codes for writing FC 5 6 15 and 16 if the command is to be executed cyclically Cyclic or only if the data have changed Change Data For function codes for reading FC 1 2 3 und 4 this parameter is not used The cycle time defines after how many milliseconds a w
265. s W To SMTP license DoeExample com lt license DoeExample com gt License Type gt SYCON net Figure 84 Example Order E Mail License request 3 The order e mail License request contains e the E mail of the selected subsidiary 110 268 W ce User Single Device License Subject License request 9 Device Information F Append 2 EmailOrderRequest 1251100 20007m b Sea Manufacturer 0x0001 Soameesseeseseseneeeenseseesseeesesesesseees Device Number 1251100 netX License Order Serial Number 20007 SSSsessssssssssssssssssssssssssssssessssssss Chip Type 0x00000001 Step 0x00000000 Company Doe Example LTD Romcode Revision 0x00000000 License Flags 1 Ox7f Address 2000th Rd U 5 NY 11417 License Flaas 2 0x0 Fax 49 0011223344 100 Ordered Licenses 9 Licensee Information A Sn a a mas nin noe om een mao ene oom em mo Master Protocols First Name John Surname Doe gt One General Master License e Mail License doe com gt AS Interface Master Telephone 0011223344 55 gt CANopen Master Fax 0011223344 100 gt DeviceNet Master Customer Number 123456789 gt EtherCat Master Company Doe Example LTD gt EtherNet IP Scanner Address 2000th Ra gt PROFIBUS Master Country U S gt PROFINET IO RT Controller City Zip NY 11417 gt SERCOS III Master Order Number 987654321 Tax Ident Number test Utilities a Ow e the automatically generated XML file EmailOrderRequest_
266. scher GmbH J Gateway Stand Alone Slave i NT 100 RE xx PROXY M Fieldbus Yendor DTM Class Figure 37 Insert Proxy Device into the Project 3 gt The proxy device appears in the project 8 netTAP NT 100 RE XX PROXY J lt gt 1 Figure 38 Proxy Device in the Project Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 58 268 2 4 3 Select the Protocol Conversion of the Proxy 1 Open the Proxy configuration window gt Select from the context menu of the proxy device symbol the entry Configuration gt Proxy 3 gt The Proxy configuration window opens 4 Proxy netTAP NT 100 RE DP PROXY lt gt 1 e 10 Device NT 100 RE DP PROXY Device ID Jf Vendor Hilscher GmbH Vendor ID OxO11E Navigation area m E Settings E Driver TCPHIP Driver For netX netx Driver Device selection suitable only tay Device Assignment E Configuration Device Hardware Ports O 1 Serial nu Driver Channel Protocol Access path Settings Licensing Memory Card Management Scan progress 0 0 Devices Current device Access path 25B4406D 7E0E 45D4 B634 21B22C386499 COM8_Ch2 Cancel Help Figure 39 Device Assignment without Device Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English
267. sion License Flags 1 License Flags 2 Ordered Licenses Master Protocols John Doe License doe com 0011223344 55 0011223344 100 123456789 Doe Example LTD 2000th Rd US NY 11417 987654321 test 0x0001 1251100 20007 0x00000001 0x00000000 0x00000000 Ox7f 0x0 One General Master License Sercos III Master Utilities SYCON net Signature Figure 86 Example Order Data Form PrintOrderRequest Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 112 268 The order data form contains the Order Address the License Information the License Type the Device Data the ordered Licenses YV P PDPPP Print the order data form sign it and send it by Fax Print Fax Form Figure 87 License Pane Fax Number of the selected Subsidiary gt Use the Fax number 9 which is displayed after the subsidiary was selected in the License pane Or gt Keep ready the order data form and communicate the order data via telephone Telephone Figure 88 License Pane Telephone Number of the selected Subsidiary gt Use the telephone number which is displayed after the subsidiary was selected in the License pane gt The order process is complete Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC081201
268. sion 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 163 268 Configuration Parameters of the sercos Communication Profile Class SCP_Sync ConClk pulse This timing parameter defines the time how long the communication gt 1000 ns length synchronized hardware output signal CON CLK is set The maximum Default RE S3S devices valid value of the Control Clock Length depends on the configured 1000 ns cycle time In general the signal CON_CLK must go to inactive again before the next cycle starts DivClk pulse This timing parameter defines the delay time from the start of the 0 16 777 210 ns distance communication cycle to the first pulse of the communication Default RE S3S devices synchronized hardware output signal DIV_CLK 20000 ns DivClk Delay This timing parameter defines the delay time respectively the distance 0 6 710 860 ns between two pulses of the communication synchronized hardware output Default RE S3S devices signal DIV_CLK In the Divided Control Clock Mode1 this parameter is 20000 ns ignored DivClk pulse This timing parameter defines the pulse length i e how long the 1000 20 000 ns length communication synchronized hardware output signal DIV_CLK is set Default RE S3S devices 1000 ns All timing values are handled as multiple of 10 ns e g Control Clock Length 1005 ns is handled as 1000 ns DivClk For Divided Control Clock Mode0 Here the param
269. sion 6 English 2014 04 Released Public Hilscher 2009 2014 Settings 96 268 3 3 Device Assignment Note In the Device Assignment you first must assign the device to the DTM by checking the check box This is essential to establish an online connection from the DTM to the device later as described in section Connecting Disconnecting Device on page 233 Therefore in the Device Assignment dialog pane you scan for the device s and select it 3 3 1 Scanning for Devices 1 Select Settings gt Device Assignment in the navigation area The dialog pane Device Assignment is displayed Scan progress 4 4 Devices Current device Device selection suitable only T Scan _ Device Hardware Ports 0 1 Channel Protocol Access path O NT100 RE RS Ethernet Ethernet S n a 20037 netX Driver Undefined Gateway ee ACOM3_cifXO Access path Figure 71 Device Assignment detected Devices 2 Select the list box entry suitable only 3 Select the Scan button to start the scanning process Under Device Selection all devices are displayed which can be connected to the DTM via the preselected driver Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Settings 97 268 Range of Value Value Selecting suitable only or all devices suitable only all Device Device name Hardware P
270. ssed to driver CIFX_INVALID_ PARAMETER 0x800A0005 Invalid parameter CIFX_INVALID_ COMMAND Ox800A0006 Invalid command CIFX_INVALID_BUFFERSIZE 0x800A0007 Invalid buffer size CIFX_INVALID_ACCESS_ SIZE 0x800A0008 Invalid access size CIFX_FUNCTION_FAILED 0x800A0009 Function failed CIFX_FILE_OPEN_FAILED Ox800A000A File could not be opened CIFX_FILE_SIZE_ZERO 0x800A000B File size is zero CIFX_FILE_LOAD_INSUFF_MEM 0x800A000C Insufficient memory to load file CIFX_FILE_CHECKSUM_ERROR 0x800A000D File checksum compare failed CIFX_FILE_READ_ERROR 0x800A000E Error reading from file CIFX_FILE_TYPE_INVALID Ox800A000F Invalid file type CIFX_FILE_NAME_INVALID 0x800A0010 Invalid file name CIFX_FUNCTION_NOT_AVAILABLE 0x800A001 1 Driver function not available CIFX_BUFFER_TOO_SHORT 0x800A0012 Given buffer is too short CIFX_MEMORY_MAPPING_FAILED 0x800A0013 Failed to map the memory CIFX_NO_MORE_ENTRIES 0x800A0014 No more entries available CIFX_CALLBACK_MODE_UNKNOWN 0x800A0015 Unkown callback handling mode CIFX_CALLBACK_CREATE_EVENT_FAILED 0x800A0016 Failed to create callback events CIFX_CALLBACK_CREATE_RECV_BUFFER 0x800A0017 Failed to create callback receive buffer Table 89 Generic Error Codes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010106EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Error Codes 251 268 8 5 2 Generic Driver Error Co
271. st be restarted1 to make the new setting valid 1 Restart the ODM server via the ODMV3 Tray Application In the foot line click to g using the right mouse key In the context menu select Service gt Start checked unchecked Default unchecked Select Port Depending which COM ports interfaces are available on the PC they will be listed under Select Port COM 1 to COM N Port Configuration Disable Port checked No connection checked unchecked The netX Driver tries to establish a connection unchecked Default using the configured USB RS232 interface Baud rate Transfer rate number of bits per second 9 6 19 2 38 4 57 6 or The device must support the baud rate 115 2 kBit s Default RS232 115 2 kBit s Stop bits Number of stop bits sent after the transfer of the send data Stop bit 1 1 5 2 for synchronization purposes to the receiver Default RS232 1 Send Timeout ms Maximum time before the transfer of the transmission data is canceled when the send process fails for example because of the transfer buffer is full 100 60 000 ms Default RS232 and USB 1000 ms Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Settings 91 268 Parameter Meaning Range of Value Value Reset Timeout ms Maximum time for a devi
272. t connect to device DRV_E_USR_NOT_INITIALIZED 0x8004C020 USER Board not initialized DevinitBoard not called DRV_E_USR_COMM_ERR 0x8004C021 USER IOCTRL function failed DRV_E_USR_DEV_NUMBER_INVALID 0x8004C022 USER Parameter DeviceNumber invalid DRV_E_USR_INFO_AREA_INVALID 0x8004C023 USER Parameter InfoArea unknown DRV_E_USR_NUMBER_INVALID 0x8004C024 USER Parameter Number invalid DRV_E_USR_MODE_INVALID 0x8004C025 USER Parameter Mode invalid DRV_E_USR_MSG_BUF_NULL_PTR 0x8004C026 USER NULL pointer assignment DRV_E_USR_MSG_BUF_TOO_SHORT 0x8004C027 USER Message buffer too small Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010106EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Error Codes 248 268 cifX Driver Specific ODM Error Codes Error Code Definition Value Description DRV_E_USR_SIZE_INVALID 0x8004C028 USER Parameter Size invalid DRV_E_USR_SIZE_ZERO 0x8004C02A USER Parameter Size with zero length DRV_E_USR_SIZE_TOO_LONG 0x8004C02B USER Parameter Size too long DRV_E_USR_DEV_PTR_NULL 0x8004C02C USER Device address null pointer DRV_E_USR_BUF_PTR_NULL 0x8004C02D USER Pointer to buffer is a null pointer DRV_E_USR_SENDSIZE_TOO_LONG 0x8004C02E USER Parameter SendSize too large DRV_E_USR_RECVSIZE_TOO_LONG 0x8004C02F USER Parameter ReceiveSize too large DRV_E_USR_SENDBUF_PTR_NULL 0x800
273. tLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 100 268 4 2 Settings In the Settings pane you can e select the protocol for Port X2 respectively for Port X3 e transfer the firmware into the device e set the cycle time of the Gateway and e enable the address switch for a slave protocol i netDevice Gateway netTAP NT 100 XX XX lt gt 1 P IO Device NT 100 Xx xx Device ID 2 aio Vendor Hilscher GmbH Vendor ID OxO11E Navigation area E Settings General amp Driver netX Driver Description a Device Assignment ee S Cubs i Protocol Combinations tay Settings Signal Mapping Primary network Port X2 v Secondary network Port x3 v Memory Card Management Licensing Required gateway Required license Available Firmware Browse Software class Software version Basic Settings Mapping Cycle time Mapping mode Network Address Switch Enable Used by Figure 74 Settings No Name Description General Description Here you can enter a descriptive name also known as symbolic name for the device This name ist displayed in front of the device oO netTAPINT 100 xx xX lt gt 1 ao Protocol Combination Primary network Port X2 Here you can select the protocol for the primary network which becomes active on port X2 Secondary network Port Here you can s
274. table fields Fax Customer Number Order Number Value added tax identification number gt Under Request Form please fill out gt Value enter all fields for the Configuration of Gateway and additional data which are not mandatory Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 109 268 4 3 7 Ordering the License Place your order in the License pane Therefore Cool E mail 5 Print Fax Form 6 Telephone 7 Export License Request Figure 82 License Pane Selecting the Subsidiary Ordering Contacts 1 Select the Subsidiary to which the order shall be send 2 Place the order Refer to Section Page by E Mail Ordering the License by E Mail 110 or by Fax Ordering the License by Fax or 111 or by Telephone by Telephone orinaFile Exporting License Request to 113 a File The Contact Data of the selected subsidiary are displayed under Position Mand A Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 4 3 7 1 Ordering the License by E Mail You can place your order by e mail E mail 5 Figure 83 License Pane placing the order by E mail gt Click E mail The order E mail License request open
275. te device then sends a telegram which is received by the device By this a polling querying of the remote devices can be performed The device can send a polling telegram with or without user data Send T gt Receive g Receive The superordinated control unit must activate the send operation by handshake The superordinated control unit must acknowledge each reception by handshake Communication The send operation can be triggered or performed cyclically e triggered With each handshake of the superordinated control unit a telegram is send For this set the timing parameter Send Cycle Time to zero The remote device then sends a telegram which is received by the device The device can monitor the beginning of the receive telegram by time monitoring via the Response Timeout parameter The superordinated control unit must activate the send operation by handshake The superordinated control unit must acknowledge each reception by handshake e Cyclic The device sends in a constant cycle With each handshake of the host the send data initially are updated in the internal buffer and sent during the next sending cycle For this set the timing parameter Send Cycle Time to the cycle time unequal to zero The remote device then sends a telegram which is received by the device The device can monitor the beginning of the receive telegram by time monitoring via the Response Timeout parameter The superordinated control unit must a
276. ted in the device catalog then it has to be imported into the device catalog first 2 4 4 1 Expand PROFIBUS DP Slave Device Catalog If you want to use a PROFIBUS DP slave device that is not listed in the device catalog then you have to import the GSD file into the SYCON net device catalog gt Proceed as follows 1 Missing PROFIBUS DP Slave devices can be added to the device catalog using the menu Network gt Import Device Descriptions 2 Select the new GSD file 3 Answer the question Do you want to reload the device catalog with Yes to reload the catalog 4 More information about the device catalog is in the document ab SYCONnet_netDevice_en pdf in the directory Documentation on the product DVD 2 4 4 2 Insert PROFIBUS DP Slave Device to the PROFIBUS Network gt Go to the device catalog Use drag and drop with one or more PROFIBUS DP Slave devices to insert it them at the PROFIBUS bus line The PROFIBUS DP Slave device icons appear at the PROFIBUS network line Secondary network netTAP NT 100 RE DP lt gt 1 CB_AB32 DPS CB_A amp B32 DPS lt 2 gt p Figure 42 Proxy Device with Slave Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 62 268 2 4 4 3 Configure the PROFIBUS DP Slave device gt Open the configuration wi
277. tent situation into account The company names and product descriptions included in this document may be trademarks or brands of the respective owners and may be trademarked or patented Any form of further use requires the explicit consent of the respective rights owner 1 2 2 Important Notes The user manual accompanying texts and the documentation were created for the use of the products by qualified experts however errors cannot be ruled out For this reason no guarantee can be made and neither juristic responsibility for erroneous information nor any liability can be assumed Descriptions accompanying texts and documentation included in the user manual do not present a guarantee nor any information about proper use as stipulated in the contract or a warranted feature It cannot be ruled out that the user manual the accompanying texts and the documentation do not correspond exactly to the described features standards or other data of the delivered product No warranty or guarantee regarding the correctness or accuracy of the information is assumed We reserve the right to change our products and their specification as well as related user manuals accompanying texts and documentation at all times and without advance notice without obligation to report the change Changes will be included in future manuals and do not constitute any obligations There is no entitlement to revisions of delivered documents The manual delivered with the prod
278. ter your signal names Further information is described in section Signal Configuration on page 228 7 Close configuration dialog Click on OK to save the parameter or click on Cancel if the parameter should not be saved 3 gt The configuration dialog closes Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 4 9 1 EtherNet IP Adapter Parameter 130 268 Bus startup Communication starts automatically Automatic Default Watchdog time This function is not supported by gateway or proxy devices I O data status Status of the input or the output data For each input and output data the following status information in Byte is memorized in the dual port memory Status 0 None default Status 1 1 Byte for future use Status 2 4 Byte for future use Enable If Enable is unchecked for the single Ident parameters each the respective default value is used Vendor ID Identification number of the manufacturer Product Code Product code of the device as specified by the manufacturer Product Type Communication Adapter 0 20 65535 ms default 1000 ms 0 Off Default None 0x00000000 OxOOOOFFFF hex Hilscher 0x00000011B hex 0x00000000 OxOOOOFFFF hex Default NT 50 EN EIS 0x000000113 hex NT 100 RE EIS 0x00000010F hex NB 100 RE EIS 0x00
279. the BAA i tae 13 1 4 Dialog Structure of the netGateway DTM ececcceeesscceeeeesneeeeeeeseaeeesesseeeeeeeeeaeees 14 1 4 1 General Device INformation 0 cccceeeceeeeeeececeeeeeeeeeeaeeecaaeeeeaeeseaeeesaeeesaaeeenees 15 1 4 2 Navigation Area o oo uaa aE EREEREER EE Aena ARAO EAEn AER 15 1 4 3 DialOg PANGS oraa eE A EA EET AEA TETERA T TER EEE 16 1 4 4 OK Cancel Apply and Help 0 cccceeeccecseeeeeseeeeeeeceeeeseaeeeeaeeseeeeesaaeeneaeeenaees 17 1 4 5 Valle EiMGS iss ccs ceict e eel ectaasay Stet coed Ovals eoletaden a A nett 17 1 4 6 StAtUs Bares Pecese leds catenin detanca acca A E AA eee cece 18 2 CONFIGURATION SEQUENCE FOR GATEWAY AND PROXY eseese 19 2 1 Gateway and Proxy Device sa icccsscscarnicess icematanddetnsaglesncnedesdecensaeectacnsancade cendagedeesandacee 19 2 2 Configuration of a NT 50 as a Gateway vsccccsctenccina tines catnnteatenaeeeed ae 20 2 2 1 Requirement for the Configuration ssesesseessesssiesinesinssrrssrrssrrssrrssrnesrissrnssrnn 20 2 2 2 Start SYCON net and User LOQIN cccccecceceeeeeeeeceeeeeceaeeeeaaeeeceeeeseaeeesaeeeenees 20 2 2 3 Insert the Gateway Device into the Configuration WindowW c cceeeee 21 2 2 4 Select the Protocol Conversion of the Gateway essessseessessrsssresssressressrees 22 2 2 5 Configuration of the secondary Network ccscceceeceseeeeeeeeeeeeereeseaeeeeaeeeenees 26 2 2 6 Configuration of the primary Netwo
280. the configuration of the PROFIBUS DP Master gt Use for the configuration of the PROFIBUS DP Master module s e g 32 Bytes In for receiving data from the netTAP or netBRICK device Use the module s which are configured in the netTAP or netBRICK device Modules with the size of zero in the netTAP or netBRICK configuration needs not to be considered for the configuration of the PROFIBUS DP Master Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 190 268 4 23 Configuration Modbus RTU Master Slave The netTAP NT 50 and NT 100 device respectively the netBRICK NB 100 device as Modbus RTU Master or Slave needs parameter These parameter can be edited as follows 1 Open the configuration dialog gt Select from the context menu of the netTAP respectively the netBRICK symbol the entry Configuration gt Modbus RTU gt The Modbus RTU settings dialog opens 3 In the navigation area the entry Configuration under the folder Configuration is selected and the settings dialog is displayed 2 Set protocol mode Set the Protocol Mode to I O Slave if the netTAP or netBRICK device should work as Modbus RTU Slave gt Set for the Protocol Mode to Master if the netTAP or netBRICK device should work as Modbus RTU Master 3 If you have set the Protocol Mode to Master then the entry Command Table ap
281. the device uses the manually entered value This function is not supported by gateway proxy devices There are three methods available how the device can obtain its IP Address Netmask and Gateway Address one of which must be selected These methods can also be combined The device performs the following sequence in order to obtain the addresses 1 from a DHCP server if DHCP is checked if a DHCP server provides the requested addresses to the device then the device uses these addresses 2 from a BootP server if BootP is checked if a BootP server provides the requested addresses to the device then the device uses these addresses 3 the addresses manually set are used If the IP Address is set manually also the Network Mask must be set manually The manually set Gateway Address is optional If no DHCP server and no BootP server and no manually set addresses exist then the protocol is not ready for initialization or for operation TCP Flags BootP checked If checked the device obtains its IP Address Netmask Gateway unchecked Default Address from a BOOTP server This function is not supported by gateway proxy devices DHCP checked Default If checked the device obtains its IP Address Netmask Gateway unchecked Address from a DHCP server This function is not supported by gateway proxy devices Further see next page Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revi
282. then closes To cancel your latest changes click Cancel Answer to the safety query Configuration data has been changed Do you want to save the data by Yes No or Cancel Yes The changes are saved or the changed values are applied on the frame application database The dialog then closes No The changes are not saved or the changed values are not applied on the frame application database The dialog then closes Cancel Back to the DTM To confirm your latest settings click Apply All changed values will be applied on the frame application database The dialog remains opened Help To open the DTM online help click Help Table 4 OK Cancel Apply and Help 1 4 5 Table Lines In the DTM dialog pane table lines can be selected inserted or deleted To select the first line of a table use First Line EO To select the previous line of a table use Previous Line To select the next line of a table use Next Line ow To select the last line of a table use Last Line BEN Create a new Line inserts new lines into the table E Delete selected Line deletes the selected line from the table Table 5 Selecting inserting deleting Table Line Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Introduction 1 4 6 Status Bar 18 268 The Status Bar displays information about the current state of the
283. tification or depending on the used driver additional data to the device For the cifX Device Driver the following data are displayed a For devices without firmware cifX OtoN _SYS b For devices with firmware cifX OtoN _Ch 0to3 cifX OtoN Board number 0 to N Ch 0to3 Channel number 0 to 3 Table 11 Parameters of the Device Assignment Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Depending on the device and on the driver board or channel number IP address or COM interface driver identification ID depending on the device and on the driver board or channel number IP address or COM interface Hilscher 2009 2014 Settings 98 268 3 3 2 Selecting the Device Note A connection with the DTM can only be established with one device To select the physical EtherNet IP Scanner device with or without firmware 1 In the Device Assignment pane in the selection list Device selection check the check box for the device Scan progress 4 4 Devices Current device Device selection suitable only z _ Device Hardware Ports oj1 Channel Protocol Access path NT 100 RE RS Ethernet Ethernet S nja 20037 netX Driver Undefined Gateway e ACOM3_cifXO Access path B54C8CC F333 4135 8405 6E 12FC88EE62 COM3_cifxO_Ch2 Figure 72 Device Assignment Selecting the Device gt Unde
284. tifier To identify a remote Server connected on a serial line or on other 0 247 buses Default 0 The Unit Identifier is initialized by the Client Do not change for response Function Code Indicates the function code for reading or writing commands 3 Read Coils FC1 Read Inputs FC2 Read Holding Registers FC3 Read Input Registers FC4 Force Single Coil FC5 Preset Single Register FC6 Force Multiple Coils FC15 Preset Multiple Registers FC16 1 2 3 4 5 6 15 16 Default Read Coils FC1 Address Indicates the data address in the Open Modbus TCP Server device The parameter Address contains the register address in the Open Modbus TCP Server device The register address is counted for every function code beginning with 0 The following table shows the assignment of the Address to the data address in the Open Modbus TCP Server by Function code Data Address Open Modbus TCP Server FC 1 FC2 FC4 FC 3 FC5 FC 6 FC 15 FC 16 3 Parameter eee To know which data address with which data of the Open Modbus TCP Server devices is provided for reading or for writing refer to the device description of the Open Modbus TCP Server device manufacturer 0 65 535 Default 0 Number of Registers Coils Indicates the number of reading or writing data as registers or coils The maximum value depends from the function code 1 max value Default 1 max value for FC1 2000 Coils
285. ting the records of Table type 1 ELEMENT _NE_RECORD elementwise and structure definitions are present it s only allowed to write the corresponding element number in each record CDBM_E_TABTYPE1_WRITE_ OXC004C856 When writing the records of Table type 1 ELEMENT _NOT_ FOUND with an array and structure definitions are present it s assumed that a corresponding element number of this record exist CDBM_I_TABLE_NAME_EXCEEDS _ 0X4004C857 The Table name exceeds the maximum RCS_RANGE Informational length of RCS compatible Table names CDBM_W_CUT_STRING 0X8004C858 The string exceeds the maximum length Warning and will be limited to the maximum length CDBM_I_STRING_TOO_SHORT 0X4004C859 The string is below the minimum length Informational The minimum length will be reduced CDBM_I_STRING_TOO_LONG 0X4004C85A The string is exceeding the maximum The Informational maximum length will be extended CDBM_E_STRING_TOO_SHORT 0XC004C85B The string is below the minimum length Error CDBM_E_STRING_TOO_LONG 0XC004C85C The string is exceeding the maximum Error length CDBM_E_WRONG_TYPE_FOR_WRITE 0XC004C85D Writing on the Element type with the given Data type is not implemented CDBM_E_NO_APPEND_IN_ OXC004C85E Method IDbmRecord AppendData is not STRUCTURED_RECORDS allowed for structured records CDBM_E_DATA_UNAVAILABLE OXC004C85F No data available CDBM_E_CANT_CONVERT_ INTO OXC004C860 Unable to convert the value into the Element type Configuration
286. tion 153 268 4 13 Configuration PROFINET IO Device Gateway The netTAP NT 50 and NT 100 device respectively the netBRICK NB 100 device as gateway with PROFINET IO Device needs parameter These parameter can be edited as follows 1 gt Open the configuration dialog Select from the context menu of the netTAP respectively the netBRICK symbol the entry Configuration gt PROFINET IO Device The PROFINET IO Device configuration dialog opens In the navigation area the entry Configuration under the folder Configuration is selected and the settings dialog is displayed Set the number of Input Data Bytes and Output Data Bytes Enter in the field Input Data Bytes the number of data bytes which should be transferred from the PROFINET IO Controller to the netTAP or netBRICK device e g 32 Enter in the field Output Data Bytes the number of data bytes which should be transferred from the netTAP or netBRICK device to the PROFINET IO Controller e g 64 Station name The default name for the Name of Station for the NT 50 device is nt5O0enpns for the NT 100 device nt100repns and for the NB 100 device nb100repns If you need to set an other name of station or you use several netTAP or netBRICK devices in the PROFINET network then set a unique name of station as follows Select Enable in the Ident area Enter in the field Name of Station the name of station which the netTAP or netBRICK device should use in the PROFINET
287. to export or import laws as well as the associated regulations of different counters in particular those of Germany and the USA The software may not be exported to countries where this is prohibited by the United States Export Administration Act and its additional provisions You are obligated to comply with the regulations at your personal responsibility We wish to inform you that you may require permission from state authorities to export re export or import the product 1 2 6 Registered Trademarks Windows XP Windows Vista Windows 7 and Windows 8 are registered trademarks of Microsoft Corporation CANopen is a registered trademark of CAN in AUTOMATION International Users and Manufacturers Group e V CiA Nurnberg CC Link is a registered trademark of Mitsubishi Electric Corporation Tokyo Japan CompoNet DeviceNet and EtherNet IP are trademarks of ODVA Open DeviceNet Vendor Association Inc EtherCAT is a registered trademark and a patented technology of Beckhoff Automation GmbH Verl Germany formerly Elektro Beckhoff GmbH Modbus is a registered trademark of Schneider Electric POWERLINK is a registered trademark of B amp R Bernecker Rainer Industrie Elektronik Ges m b H Eggelsberg Austria PROFIBUS und PROFINET are registered trademarks of PROFIBUS International Karlsruhe sercos and sercos interface are registered trademarks of sercos international e V Suessen Germany All other ment
288. transmission of data Half duplex is the opposite of _Full duplex Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Appendix Hub Industrial Ethernet Master netX Object Dictionary ODMV3 Open Modbus TCP PROFINET 265 268 A network component connecting multiple communication partners with each other A hub does not provide own intelligence thus it does not analyze the data traffic and sends received data to all connected communication partners A hub can be used for setting up a star topology See Real Time Ethernet Master devices initiate the data traffic on the bus In the communication protocol Master devices are called active participants A master may send messages without external request networX on chip next generation of communication controllers An object dictionary is a storage area for device parameter data structures It is accessed in standardized manner The Online Data Manager Version 3 ODMV3 is an application interface The ODMV3 works as a server which can be run as an out proc server or system service lts task is to provide different applications e g SYCON net access to multiple devices and even share one device amongst several applications A communication system for Industrial Ethernet designed and developed by Schneider Automation and maintained by the Modbus IDA organiz
289. ts these numbers from the exported GSDML file Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 159 268 4 15 Configuration sercos Slave The NT 100 device respectively the netBRICK NB 100 device as sercos Slave needs parameter These parameter can be edited as follows 1 gt Open the configuration dialog Select from the context menu of the netTAP respectively the netBRICK symbol the entry Configuration gt SERCOS III Slave The sercos Slave configuration dialog opens In the navigation area the entry Configuration under the folder Configuration is selected and the configuration dialog is displayed Set Device ID Enter in the field Device ID the name which the netTAP or netBRICK device uses on the sercos network to be identified by the sercos Master Accept Vendor Code gt Accept the default Vendor Code 0x000003E8 1000 dec Hilscher Set Version SCP SYNC Set Version SCP SYNC to 0 if the sercos Master uses the telegram sequence MDT AT NRT or Set Version SCP SYNC to 1 if the sercos Master uses the telegram sequence MDT NRT AT Set Version SCP NRT Set Version SCP NRT to 0 Use this setting only Set Address Enter in the field SERCOS Ill Address the address which the netTAP or netBRICK device uses on the sercos network to be addressed by the sercos Master
290. tten Re initializing the channel is not allowed in this state Configuration New Bit 4 The Configuration New flag is set by the protocol stack to indicate that a new configuration became available which has not been activated This flag may be set together with the Restart Required flag Restart Required Bit 5 The Restart Required flag is set when the channel firmware requests to be restarted This flag is used together with the Restart Required Enable flag below Restarting the channel firmware may become necessary if a new configuration was downloaded from the host application or if a configuration upload via the network took place Restart Required Enable Bit 6 The Restart Required Enable flag is used together with the Restart Required flag above If set this flag enables the execution of the Restart Required command in the netX firmware Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 120 268 Configuration Communication State Master and Slave The communication state field contains information regarding the current network status of the communication channel of the remote network Depending on the implementation of the protocol stack of the remote network all or a subset of the definitions below is supported Status Value Unknown 0 Offline 1 Stop 2 I
291. uct applies Hilscher Gesellschaft fur Systemautomation mbH is not liable under any circumstances for direct indirect incidental or follow on damage or loss of earnings resulting from the use of the information contained in this publication Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Introduction 11 268 1 2 3 Exclusion of Liability The software was produced and tested with utmost care by Hilscher Gesellschaft fur Systemautomation mbH and is made available as is No warranty can be assumed for the performance and flawlessness of the software for all usage conditions and cases and for the results produced when utilized by the user Liability for any damages that may result from the use of the hardware or software or related documents is limited to cases of intent or grossly negligent violation of significant contractual obligations Indemnity claims for the violation of significant contractual obligations are limited to damages that are foreseeable and typical for this type of contract It is strictly prohibited to use the software in the following areas e for military purposes or in weapon systems e for the design construction maintenance or operation of nuclear facilities e in air traffic control systems air traffic or air traffic Communication systems e in life support systems e in systems in which f
292. ud 2500 kBaud 5 MBaud 10 MBaud Hold last Hold Clear Mode Behavior in case of bus error Default unchecked received Output Clear output data unchecked Data Hold last received output data checked Table 38 CC Link Slave Parameters Part 1 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 176 268 CC Link CC Link Version 1 1 Default Version CC Link Version 2 2 Station Type Type of CC Link station Remote I O Station 0 Default Remote Device Station 1 Number of Number of occupied stations Stations Remote I O Station 1 Default Remote Device Station Extension Number of extension cycles Cycle Allowed numbers for CC Link version 1 Single One cycle Allowed numbers for CC Link version 2 Single One cycle Double Two cycles Default 1 2 Quadruple Four cycles 4 Octuple Eight cycles 8 lO Data Bytes The number of lO Data bytes depends on the following settings station type number of stations and number extension cycles The number of stations can only be configured with station type Remote Device Station version 1 and version 2 and the number of extension cycles can only be configured with version 2 Firmware stack works according to CC Link Version 2 0 input data 12 368 Bytes output data 12 368 Bytes Firmware stack works according to CC Link Version 1 11 input data 4 48 B
293. uration DeviceNet Master The netTAP NT 50 NT 100 device respectively the netBRICK NB 100 device as DeviceNet Master needs a configuration e g information about how many DeviceNet Slave devices with how many input and output data are to be connected 1 Insert DeviceNet Slave devices gt Drag from the device catalog DeviceNet Slave device s and drop it to the bus line of the DeviceNet Master 2 Configure DeviceNet Slave devices gt Open the configuration dialog for each DeviceNet Slave device and configure the device Information about how to configure the DeviceNet Slave device is in the Operating instruction manual Generic DTM for DeviceNet Slave devices and has the file name DeviceNet_Generic_Slave_DTM_en pdf respectively open in the configuration dialog of the slave the online help by the F1 key 3 Configure DeviceNet Master Select from the context menu of the netTAP respectively the netBRICK symbol the entry Configuration gt DeviceNet Master Information about how to configure the DeviceNet Master device is in the operating instruction manual DTM for DeviceNet Master devices and has the file name DeviceNet_Master_netX_DTM_en pdf respectively open in the configuration dialog of the master the online help by the F1 key Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 179 268
294. ured correctly wv Ready Ready Shows that the netTAP firmware has been started correctly The netTAP firmware waits for a configuration Ld Error Error Shows that the netTAP firmware records a device status error For further information to the error characteristics and the number of counted errors refer to the extended diagnosis wv Network State r Operate Shows that the netTAP firmware is in data exchange Idle Idle Shows that the netTAP firmware is in idle mode w A Stop Stop Shows that the netTAP firmware is in Stop state There is no cyclic data exchange at the network The netTAP firmware was stopped by the application program or it changed to the Stop state because of a bus error Offline Offline The netTAP firmware is offline pending it does not have a valid configuration Configuration State Configuration Configuration locked Shows that the netTAP firmware configuration is locked to avoid the locked configuration data are typed over w New Configura New Configuration pending Shows that a new netTAP firmware configuration is available tion pending Reset required Reset required Shows that a firmware reset is required as a new netTAP firmware configuration has been loaded into the device Bus ON Shows whether the bus communication was started or stopped e whether the device is active on the bus or no bus communication to the device is possible and no response telegrams
295. us Monitoring Data Control Time Override slave specific Watchdog Control Time Min Slave Interval Watchdog Control Time ms Calculated Timing Tid 37 tBit Tid2 150 tBit Values marked with this symbol should be Adjust adjusted to changes in the topology lt Disconnected J Data Set Figure 43 PROFIBUS DP Bus Parameter Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 63 268 2 Configure the PROFIBUS DP Master gt Set the parameter Set especially under Configuration gt Bus Parameter the bus parameter and under Configuration gt Station Table the station addresses stations addresses of the PROFIBUS DP Slave devices ZnetDevice PROFIBUS DP Master netTAP NT 100 RE DP PROXY lt gt 1 f IO Device NT 100 Xx x Device ID Ox0B44 a vendor Hilscher GmbH vendor ID 0x011E DT Navigation Area SQ Configuration Bus Parameters Activate Station Device Name Vendor Process Data CB_AB32 DPS CB_AB32 DPS Hilscher GmbH Address Table 3 CB_AB32 DPS CB_AB32 DPS Hilscher GmbH tay Station Table Figure 44 PROFIBUS DP Slave Station Address More information about the configuration of PROFIBUS DP Master devices are in the document PROFIBUS Master_netX_DTM_en pdf in section Configuration CT 3 Close the confi
296. us RTU Master reads out data from the Modbus RTU Slave and saves them into its data memory For writing commands the Modbus RTU Master reads out data from its data memory and writes them into the Modbus RTU Slave The number of commands which can be defined depends from the firmware and from the Dual Port Memory layout Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 195 268 4 23 2 2 Parameter of the Command Table Delay 0 Command Table Device Address Unit Indentifier Function Code Address Number of Register Coils Memory Addressfintermal Trigger Cycle Time ms 8 0 Read Holding Registers FC3 10 12 0 Cyclic 0 H O Preset Multiple Register FC16 30 2 0 Changed 0 Add Remove Figure 99 Pane Command Table Each command contains the following parameters Unit Identifier not relevant here Number of Registers Coils Number of data Memory Address internal Data address in the Modbus RTU Master device Byte address in the process image of the Modbus RTU Master device Trigger Trigger for writing commands Cycle Time Cycle time Table 48 Parameter of the Command Table Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 196 268 Para
297. ve with signals which should be sent on Port X2 Port X2 send gt For this mark the signal received Port X3 and the signal to be sent Port X2 and the click the button Map Signals Or Map the signal using drag and drop For this drag the signal received Port X3 receive and drop it on the signal to be sent Port X2 send 5 Signal Mapping Transfer status info of Port X2 to Port X3 If necessary map the status information of Port X2 Port X2 generated which are generated device internal to signals which should be sent on Port X3 Port X3 send gt For this mark the status signal Port X2 and the signal which should be sent Port X3 and click the button Map Signals Or Map the signal using drag and drop For this drag the status signal Port X2 generated and drop it on the signal to be sent Port X3 send Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 30 268 6 Signal Mapping Transfer status info of Port X3 to Port X2 gt f necessary map the status information of Port X3 Port X3 generated which are generated device internal to signals which should be sent on Port X2 Port X2 send gt For this mark the status signal Port X3 and the signal which should be sent Port X2 and click the button Map Signals Or Map the signal using drag and dro
298. ver USB RS232 Connection TCP Connection Device Assignment E Configuration JV Enable TCP Connector Restart of ODM required Settings g Select IP Range HL Scan Timeout 100 a ms IP Range Configuration IP Address TCP Port Address Count Send Timeout ms Keep Alive Timeout zj ms Reset Timeout ms Restore Save Save All conen Figure 59 Set IP Address Search Range 1 An IP address one or IP addresses several address range are set in this window which SYCON net uses to build up a connection to the proxy device gt Select as shown in the figure above Select the tap TCP Connection Is the Select IP Range grayed out as shown above then no IP range is defined Click on to add a new range which enables the field below Otherwise an address range configured earlier can be selected or by a mouse click on a new address range can be configured Set the IP start address and end address the proxy devices is searched for Make sure that the proxy device can be reached via Ethernet and is reachable via the address range 3 gt The fields to configure an IP address range are enabled Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration Sequence for Gateway and Proxy 81 268 Select IP Range IP_RANGEO F Be Scan Timeout 100 H ms
299. verted to PROFIBUS DPV1 write The data to be written are forwarded unchanged to the PROFIBUS DP slave A positive confirmation to the PROFINET IO Controller means that the PROFIBUS DP Master in the proxy device has received a positive confirmation from the PROFIBUS DP slave 7 2 1 Error Detection and Error Codes The following figure shows where an error detection is possible Error Detection ae Read Write gaa BJU S Controlle Proxy Device Proxy Master Read Write Figure 107 PROFINET IO PROFIBUS DP Read Write Error Detection Errors detected in the proxy device PROFINET IO device are reported as normal PROFINET IO errors to the controller Errors detected in the proxy device which are not addressing errors are reported with error code 0xDE80AABB to the PROFINET IO controller All errors except addressing errors which are detected on PROFIBUS master or slave are reported with error code OxDE80AABB to the PROFINET IO controller Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Acyclic Proxy Communication 238 268 Error detection by the proxy device for read write record The following error codes can occur Error Code Definition Descrption 0xDE80B000 DE lODReadRes negative response of a read request 80 PNIORW User Error BO invalid index invalid index for a read request
300. vice Error Codes CIFX API Transport Error Codes CIFX API Transport Header State Error Codes ODM Error Codes DBM V4 Settings D Displaying X Editing Configuring Configuration D Displaying X Editing Configuring Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public 262 268 206 207 211 212 214 214 215 216 217 218 219 220 222 223 224 225 227 228 229 231 231 232 236 238 239 241 242 243 244 244 245 246 249 250 251 252 253 253 257 258 258 Hilscher 2009 2014 263 268 Appendix 9 4 Glossary Auto Negotiation Baud rate Coil cifX CSP Auto Negotiation is a feature of an interface An interface with Auto Negotiation will automatically determine a set of correct communication parameters Data transmission speed of a communication channel or interface A coil in the meaning defined by Modbus terminology is a single bit in memory that can be accessed i e read or write via Modbus Communication InterFace based on netX electronic device data sheet required for each CC Link device Device Description File DHCP DPM DTM EDS EDS file EtherCAT EtherNet IP A file containing configuration information about a device being a part of a network that can be read out by masters for system configuration Device Description Files use various formats which depend on the
301. way These devices are called gateway devices in the following description The configuration of the NT 50 devices is explained exemplarily with the protocol conversion PROFIBUS DP Slave to Modbus RTU Slave The device NT 50 DP RS is necessary for the protocol conversion from PROFIBUS DP Slave to Modbus RTU Slave The following steps have to be done to configure the device 2 2 1 Requirement for the Configuration The device is configured via the Ethernet port Therefore it is necessary that the device gets an IP address assigned before Therefore do the followings steps 1 Establish an Ethernet connection between the Ethernet network port of your PC and the Ethernet port of the netTAP NT 50 device Start the Ethernet Device Setup software Therefore select Start gt Programs gt SYCON net System Configurator gt Ethernet Device Setup Search for connected devices Therefore click on Search Devices Devices are searched in the local network using broadcast telegrams Assign an IP address to the NT 50 device which should be used for the device configuration This address can be stored in a non volatile memory of the device 2 2 2 Start SYCON net and User Login 1 gt Start SYCON net Select Start gt Programs gt SYCON net System Configurator gt SYCON net SYCON net is started User Login In the window SYCON net User Login click OK to login or enter your password and then click OK to login S
302. x Revision Revision number of the device as specified by the manufacturer 0x00000000 Number OxFFFFFFFF hex Default 0x00000000 hex Serial Number Serial number of the device 0x00000000 OxFFFFFFFF hex Input Data Length of the input data in Byte 0 200 Byte Bytes Default 200 Byte Output Data Length of the output data in Byte 0 200 Byte Bytes Default 200 Byte Table 16 EtherCAT Slave Parameters Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 126 268 4 7 2 Settings at the used EtherCAT Master Device Description File To configure the Master an XML file device description file is required The CML file is on the delivered DVD in the directory EDS EtherCAT NT 100 RE XX Hilscher NT 100 ECS XX V2 2 xml NB 100 RE XX Hilscher NB 100 ECS XX V2 2 xml Table 17 XML File Names for netTAP and netBRICK Configuration Note The settings in the used Master must comply with the settings in the Slave to establish a communication Important parameters are Vendor ID Product Code Serial Number Revision Number Output and Input length In order that the EtherCAT Master can communicate with the netTAP or netBRICK device as EtherCAT Slave gt Enter at the EtherCAT Master the number of data bytes number of input data that are configured in the netTAP or netBRICK dev
303. y Address Trigger 0 Read Holding Registers FC3 10 12 O Cyclically 0 0 Preset Multiple Register FC16 30 2 O Changed D 0 Figure 95 Examples Reading Command with FC 3 Writing Command with FC16 Example Reading Command with FC 3 From the Open Modbus TCP Server device with the Modbus address 8 from data address 40011 onwards 12 registers are read by function code 3 The data are assigned to the memory address internal 0 Example Writing Command with FC 16 To the Open Modbus TCP Server with the Modbus address 8 from data address 40031 onwards 12 registers are written by function code 16 The data are read from the process image of the Client from the memory address internal 0 onwards The writing process is only performed if the data in the process image of the Client on the memory addresses internal 0 to 3 have changed as the parameter trigger is set to changed Open Modbus TCP Open Modbus TCP Server Client 192 168 10 101 Input Data Output Figure 96 Examples Reading Command with FC 3 Writing Command with FC 16 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 143 268 4 10 3 Open Modbus TCP Server Settings at the used Open Modbus TCP Client In order that the Open Modbus TCP Client can communicate with the netTAP or netBRICK device as an Open Modbus TCP
304. y which licenses are available in the netTAP NT 100 device order licenses and transfer license files into the netTAP NT 100 device For further information refer to section Licenses on page 102 Signal Mapping On the pane Signal Mapping you can map the signals I O Data of port X2 to the signals I O data of port X3 For further information refer to section Signal Mapping on page 115 Memory Card On the pane Memory Card Management you can backup and restore the firmware and the Management configuration to respectively from an MMC card For further information refer to section Memory Card Management on page 122 Diagnosis Diagnosis At the Diagnosis panes diagnosis information can be read For further information refer to section Overview Diagnosis on page 229 Table 3 Overview Dialog Panes gt Note Accessing the Diagnosis panes of the netGateway DTM requires an online connection from the netGateway DTM to the device _ For further information refer to section Connecting Disconnecting Device on page 233 Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Introduction 17 268 1 4 4 OK Cancel Apply and Help OK Cancel Apply and Help you can use as described hereafter To confirm your latest settings click OK All changed values will be applied on the frame application database The dialog
305. ytes output data 4 48 Bytes Default 4 Table 39 CC Link Slave Parameters Part 2 gt Note To configure the Master a CSP file device description file is required The settings in the used Master must comply with the settings in the Slave to establish communication Important parameters are Slave Station Address Baudrate Station Type and Vendor Code For CC Link Version 2 00 are additionally important number of cycles as well as number of extension cycles Configuration of Gateway and Proxy Devices netTAP netBRICK and netLINK DOC0812010l06EN Revision 6 English 2014 04 Released Public Hilscher 2009 2014 Configuration 177 268 4 18 2 Settings at the used CC Link Master Device Description File To configure the Master a CSP file device description file may be required The CSP file is on the delivered DVD in the directory EDS CC Link NT 50 XX CC or NT 50 CC XX nt50 cc ccs_1 csp nt50 cc ccs_2 csp nt50 cc ccs_3 csp nt50 cc ccs_4 csp nt50 cc ccs_io csp NT 100 XX CC or NT 100 CC XX Nt100 cc ccs_1 csp nt100 cc ccs_2 csp nt100 cc ccs_3 csp nt100 cc ccs_4 csp nt100 cc ccs_io csp Table 40 CSP File Names for netTAP The files nt50 cc ccs_1 csp and nt100 cc ccs_1 csp describe the respective netTAP device as one Remote Device Station the files nt50 cc ccs_2 csp and nt100 cc ccs_2 csp describe the respective netTAP device as two Remote Device Station etc The files nt50 cc ccs_io

Configuration of Gateway and Proxy Devices

Contents

Download Pdf Manuals

Related Search

Related Contents