Download
Share
Print this page
  1. Manuals
  2. Brands
  3. BBH Manuals
  4. Media Converter
  5. SMX Series
  6. Installation manual

BBH SMX1 2 Series Installation Manual

Modbus tcp/ip, ethernet/ip, profinet, ethercat, profibus, devicenet, canopen
Hide thumbs

Advertisement

Quick Links

Download this manual
SMX / SCU Series
Field buses
Modbus TCP/IP
EtherNet/IP
PROFINET
EtherCAT
PROFIBUS
DeviceNet
CANopen
Read and observe installation manual before
initial commissioning/ initial startup/ integration of the module!
Observe safety instructions!
Keep for future use!
Installation manual
English

Advertisement

loading
Need help?

Need help?

Do you have a question about the SMX1 2 Series and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for BBH SMX1 2 Series

Summary of Contents for BBH SMX1 2 Series

  • Page 1 Installation manual English SMX / SCU Series Field buses Modbus TCP/IP EtherNet/IP PROFINET EtherCAT PROFIBUS DeviceNet CANopen Read and observe installation manual before initial commissioning/ initial startup/ integration of the module! Observe safety instructions! Keep for future use!
  • Page 2 Nevertheless, we draw your attention, that this document cannot always be updated at the same time as the technical development of our products. Information and specifications can be changed at any time. Please keep yourself informed about the latest version at www.bbh-products.de. BBH Products GmbH Böttgerstrasse 40 D- 92637 Weiden HB-37450-810-01-14F-EN COM Installation Manual.docx...
  • Page 3 Installation manual Table of contents IMPORTANT NOTES ..............6 Definitions ..............................6 Applicable documents ..........................7 Abbreviations used ............................8 SAFETY REGULATIONS ..............9 Intended use ..............................9 General safety regulations ..........................9 Operation and service ..........................11 Transport/Storage ............................11 DESCRIPTION AND FUNCTION OF DEVICE ........
  • Page 4 Installation manual 9.1.2 Input data ....................39 SMX100-x/2/(DNM, xNM, DBM, xBM) ......................40 9.2.1 Output data ....................41 9.2.1.1 Structure Device Profile 0 (=legacy profile) ..........41 9.2.1.1.1 Configuration with axis extension modules (slave devices) ....... 41 9.2.1.1.2 Configuration without axis extension modules (slave device) ....42 9.2.1.2 Data Types ...................
  • Page 5 Installation manual List of tables Table 1: Abbreviations ....................8 Table 2: Field bus specific data for Modbus TCP/IP ............14 Table 3: Field bus specific data for EtherNet/IP ............. 17 Table 4: Field bus specific data for PROFINET ............... 18 Table 5: Field bus specific data for EtherCAT ..............
  • Page 6 Important notes Important notes Definition of individual target groups: Project engineering for safe drive systems: Engineers and technicians Assembly, electrical installation, maintenance and replacement of devices: Maintenance electricians and service technicians Commissioning, operation and configuration: Technicians and engineers Definitions The designation SMX is used as generic term for all derivatives from the SMX product range.
  • Page 7 In case of uncertainties or need for further information, contact the publisher directly. If required, you can also obtain the documentation in printed form from BBH Products GmbH. Note: • Thoroughly read the manuals carefully before you start the installation and the commissioning of the devices.
  • Page 8 Light Emitting Diode Programmable Logic Controller Power on Reset SDDC Safe Device To Device Communication SafePLC² Program for programming PLC, programming interface of BBH for assemblies. SELV Safety Extra Low Voltage Synchronous Serial Interface Verband der Elektrotechnik, Elektronik und Informationstechnik e.
  • Page 9 Safety regulations Safety regulations Intended use The universal communication interface COM is an option for the modules of the following series: SCU-x-EC/NM and SDU-x SMX1x/2/x and SMX1xx/2/x and their variants for non-safe data transfer via an Ethernet or CAN or RS485 based protocol.
  • Page 10 Using our devices contrary to the rules and conditions specified hereunder can lead to injuries or fatalities as well as damage to connected devices and machines! This will also lead to the loss of all warranty and compensation claims against BBH Products GmbH. HB-37450-810-01-14F-EN COM Installation Manual.docx Page 10 of 67...
  • Page 11 Safety regulations Operation and service The module must always be deenergized before installation and removal, or before disconnecting signal lines. For this purpose, all live supply lines to the device must be checked for safe isolation from supply. During installation and removal of the module appropriate measures must be used to avoid electrostatic discharge to terminal or plug connections routed to the outside.
  • Page 12 Description and function of device Description and function of device The universal communication interface COM is permanently integrated into every base module with the option /DNM, /xNM, /NM or /DBM, /xBM. In this connection the COM interface is responsible for non-safe communication based on Ethernet or CAN respectively RS485 bus protocols.
  • Page 13 Description and function of device HB-37450-810-01-14F-EN COM Installation Manual.docx Page 13 of 67...
  • Page 14 Description and function of device Field bus characteristic data 3.1.1 Modbus TCP/IP Reaction time Processing time incoming fieldbus protocols: min.1 ms; Response time depending on SMX/SCU system SMX1x/2: 8ms SMX1xx/2: 16-32ms SCU-x-EC/NM: 16 ms SDU-x/NM: 8 ms Protocol TCP/IP Address range 260 Byte Coils 1..32...
  • Page 15 Description and function of device Memory Layout: Byte Content Holding Input Coil Access Supported Function Register Register Codes Functional Inputs 1..8 Read Coils, 0..7 Read Holding Register, Functional Inputs 9..16 Write Single Coil, Write Single Register, 8..15 Write Multiple Coils, Functional Inputs 17..24 Write Multiple Register...
  • Page 16 Description and function of device 3.1.2 EtherNet/IP Reaction time Cycle Time (Input Trigger) minimum 1ms, Reaction time base on host device SMX1x/2: 8ms SMX1xx/2: 16 – 32ms SCU-x-EC/NM: 16 ms SDU-x: 8 ms Output Data Size (O -> T) 68 Byte Input Data Size (T ->...
  • Page 17 Description and function of device Assemblies 100: Functional Inputs 101: Functional Outputs / Diagnosis 121: Safety Input (T->O) 122: Safety Output (O->T) 123: Safety Config 124: Safety Input Time Coordination (O->T) 125: Safety Output Time Coordination (T->O) Table 3: Field bus specific data for EtherNet/IP Outputs: 4 Byte;...
  • Page 18 Description and function of device 3.1.3 PROFINET Reaction time Cycle Time (Input Trigger) minimum 1ms, Reaction time base on host device SMX1x/2: 8ms SMX1xx/2: 16 – 32ms SCU-x-EC/NM: 16 – 32 ms SDU-x/NM: 8 ms Cyclic Output Data Size 80 Byte Cyclic Input Data Size 204 Byte Baud Rate...
  • Page 19 Description and function of device 3.1.4 EtherCAT Reaction time Cycle Time (Input Trigger) minimum 1ms, Reaction time base on host device SMX1x/2: 8ms SMX1xx/2: 16-32ms SCU-x-EC/NM: 16 – 32 ms SDU-x/NM: 8 ms Cyclic Output Data Size 95 Byte Cyclic Input Data Size 219 Byte Safety I/O data 12 Byte (Extended format)
  • Page 20 Description and function of device 3.1.5 PROFIBUS Reaction time Cycle Time (Input Trigger) minimum 1ms, Reaction time base on host device SMX1x/2: 8ms SMX1xx/2: 16-32ms Cyclic Output Data Size 80 Byte Cyclic Input Data Size 204 Byte Device Class DP Slave Safety I/O data 12 Byte (Extended format) (output)
  • Page 21 Description and function of device 3.1.6 DeviceNet Reaction time Cycle Time (Input Trigger) minimum 1ms, Reaction time base on host device SMX1x/2: 8ms SMX1xx/2: 16-32ms Protocol DeviceNET / CAN Connector Sub-D Type 12 – Communications Adapter Output Data Size 4 Byte functional inputs (Consumed) (Network to Slave) Input Data Size...
  • Page 22 Description and function of device 3.1.7 CANopen Reaction time Reaction time base on host device SMX1x/2: 8ms SMX1xx/2: 16-32ms Device Type NMT Slave Protocol Connector Sub-D Node ID Physical rotary switch Baud Rate Manually configured: 125, 250, 500 kBaud With Auto detection: 10, 20, 50, 100, 125, 250, 500, 800, 1000 kBaud Baud Rate Auto-...
  • Page 23 Device equipment and settings Device equipment and settings Ethernet-based device derivatives (/DNM) The front panel of the Ethernet-based fieldbus derivatives shows the following features: Diagnostics LEDs (see chapter "4.3 Diagnostics LEDs”) Ethernet female connector for Ethernet based fieldbus (see chapter 5.5.1 Female connector for the fieldbus interface with /DNM, /xNM and /NM (RJ45) Figure 1: Front view device Variant (/DNM)
  • Page 24 Device equipment and settings CAN or RS485-based device derivatives (/DBM) The front panel of the CAN or RS485-based fieldbus derivatives shows the following features: Diagnostics LEDs (see chapter “4.3 Diagnostics LEDs”) D-SUB 9P female connector for CAN or RS485- based fieldbus derivatives (see Capture “5.5.2 Female connector for the fieldbus interface with /DBM, /xBM (D-SUB)”) Figure 2: Front view device Variant (/DBM)
  • Page 25 Device equipment and settings Diagnostics LEDs The universal communication interface has 4 bi-color LEDs, regardless of the device model. Name function SMX status SDDC/SMMC communication Field bus feedback Ethernet/IP: Network Status Cross Communication to F-CPU Ethernet/IP: Module Status SD-Bus status Figure 3: Diagnostic LED's The diagnosis LEDs are not reliable indicators and cannot be guaranteed to provide accurate information.
  • Page 26 Device equipment and settings flashing EtherNet/IP: IP address configured, no CIP connections established PROFINET IO: Bus Link, but no integration EtherCAT: Status Preoperational PROFIBUS: Bus Link, but no integration DeviceNet: CANopen: Status Preoperational Short flash EtherNet/IP: Waiting for connection to the scanner (bridge) PROFINET IO: Bus Link but no integration EtherCAT:...
  • Page 27 Device equipment and settings green/orange flashing Traffic Tooling connection Green/red flashing EtherNet/IP: Waiting for TUNID (Out-of-box) Others: 1 /SD green flashing SD-Bus scan active permanent Data Exchange active red/orange flashing Error SD-Bus Scan permanent SD Bus error in cyclic operation No slave connected to SD-bus Table 9: Display functions of diagnostic LEDs HB-37450-810-01-14F-EN COM Installation Manual.docx...
  • Page 28 Connection and installation Connection and installation The COM interface requires no additional voltage supply for non-secure fieldbus communication. The interface is supplied directly from the basic module. The installation of the bus systems must be carried out according to the respective installation regulations of the user organizations (ODVA, PNO, ETG, CiA).
  • Page 29 Connection and installation 5.1 General notes on installation Strictly follow the safety regulations when installing! Type of protection: IP20 In any case isolate 230 VAC voltages from low voltage lines, if these voltages are used in connection with the application. Apply appropriate measures to exclude any faults caused by overvoltage.
  • Page 30 Connection and installation 5.2 Installation of SCU / SMX modules The module is solely to be installed in control cabinets, with a degree of protection of at least IP54. The modules must be vertically fastened on a top hat rail. The ventilation slots must be kept unobstructed, to ensure adequate air circulation inside the module.
  • Page 31 Connection and installation 5.4 Address Selector For SMX modules with option /DBM, /xBM, 2 address selector switches are installed at the bottom of the COM interface. Adresse High-Nibble !"# !"$ Adresse Low-Nibble Figure 6: Address selector switch for SMX derivatives with option /DBM, /xBM HB-37450-810-01-14F-EN COM Installation Manual.docx Page 31 of 67...
  • Page 32 Connection and installation Pin assignment female connector 5.5.1 Female connector for the fieldbus interface with /DNM, /xNM and /NM (RJ45) Name Description Colour Transmit white-orange Data + Transmit orange Data - Receive Data white-green not used Blue not used white-blue Receive Data green not used...
  • Page 33 Connection and installation 5.5.3 Female connector SD-BUS Name Description SD_BUS_24V Power supply SD-BUS +24 VDC SD_BUS_GND Power supply SD-BUS 0 VDC SD_BUS_OUT SD-BUS Output FUNC_EARTH Functional Earth "#! Figure 9: Female connector SD-Bus (Phoenix plug) HB-37450-810-01-14F-EN COM Installation Manual.docx Page 33 of 67...
  • Page 34 Modification / handling changes to the device Repair Repair work on the device can only be performed in the factory of BBH Products GmbH. Warranty By opening or modifying the module, all warranty will become null and void. HB-37450-810-01-14F-EN COM Installation Manual.docx...
  • Page 35 Maintenance Maintenance Exchanging a module The following sequence should be noted when exchanging a module: • De-activate power supply • Remove the connected Ethernet cable • Take the module off the top hat rail and pack up EMC-compliant • Mount a new module on the top hat rail •...
  • Page 36 Technical data Technical data Environmental conditions Class of protection IP 20 Operating ambient 0°C* ... 50°C temperature Storage temperature -25°C … +70°C Climatic category 3k3 acc. to DIN 60 721 Min-, Maximum relative 5% - 85% humidity (no condensation) Overvoltage category Degree of contamination Operating materials 2000m...
  • Page 37 Input/Output Data Input/Output Data The first 128 Bytes of the input assembly are used for Diagnostic data. The following 64 Bytes are used for SD-Bus data which is described in chapter “10 SD- Bus data”. 128 bytes of diagnostic data are always sent, regardless of how much data the superordinate standard control system actually need.
  • Page 38 Input/Output Data The bits of device mode show the status of the control. The states 1-5 are issued on the 7-segment display in parallel. Status 6 indicates an error, status 7 an alarm. NOTICE: The meaning of the error codes in decimal notation can be found in the TS-37350-130- xx-xxF EN Error list SMX or HB-37500-813-02-xxF Error list SCU-SDU modules.
  • Page 39 Input/Output Data 9.1.2 Input data Structure of functional input data Byte Assignment Byte 0 Logic data (Bit ID: 1..8) Byte 1 Logic data (Bit ID: 9..16) Byte 2 Logic data (Bit ID: 17..24) Byte 3 Logic data (Bit ID: 25..32) Byte 4 SD-Gateway - Instruction Byte 5...
  • Page 40 Input/Output Data SMX11 WCS As of firmware version V5.1.3.42, the content of the output data has changed and has the following structure: Byte Assignment 0..3 Device mode 1, 2, 3, 4, 5, 6 = Fatal error, 7 = Alarm Fix 0x1 (always 1) 5..7 Alive Counter (3 Bit) 0..7...
  • Page 41 Input/Output Data SMX100-x/2/(DNM, xNM, DBM, xBM) 9.3.1 Output data Three different profiles can be used; they are determined in SafePLC². 9.3.1.1 Structure Device Profile 0 (=legacy profile) 9.3.1.1.1 Configuration with axis extension modules (slave devices) Structure of the overall frame: Size of diagnostic data: 128 Byte Byte Offset Description...
  • Page 42 Input/Output Data Offset error code of slave device: offset bit data + 6 9.3.1.1.2 Configuration without axis extension modules (slave device) Structure of the overall frame: Total size of diagnostic data: 128 Bytes Byte Offset Description Data Size Bit data type „1“ 8 Byte (Logic data Bit ID1 to Bit ID56) Bit data type „2“...
  • Page 43 Input/Output Data 9.3.1.2 Data Types 9.3.1.2.1 Bit data type “1” Byte „Run“ mode (2, 3, 4) Error case ( A, F) Byte 0 0...3 device mode 1, 2, 3, 4, 5, 6 = Fatal error, 7 = Alarm 0x1 (always 1) 5..7 Alive counter (3 Bit) Byte 1...
  • Page 44 Input/Output Data 9.3.1.2.2 Bit data type “2” Byte Data Byte 0 0...7 Logic data (Bit: 49..56) Byte 1 0...7 Logic data (Bit: 41..48) Byte 2 0...7 Logic data (Bit: 33..40) Byte 3 0...7 Logic data (Bit: 9..16) Byte 4 0...7 Logic data (Bit: 1...8) Byte 5 0..6...
  • Page 45 Input/Output Data 9.3.1.3 Structure Device Profile 1 (=only logic data) Byte „Run“ mode (2, 3, 4) Error case ( A, F) Byte 0 0..3 device mode 1, 2, 3, 4, 5, 6 = Fatal error, 7 = Alarm 0x1 (always 1) 5..7 Alive counter (3 Bit) Byte 1...
  • Page 46 Input/Output Data 9.3.1.4 Structure Device Profile 2 (=logic data and process data for every slave device) Byte „Run“ mode (2, 3, 4) Error case ( A, F) Byte 0 0..3 Device mode 1, 2, 3, 4, 5, 6 = Fatal error, 7 = Alarm 0x1 (always 1) 5..7 Alive counter (3 Bit)
  • Page 47 Input/Output Data Byte 70 0..7 Process data axis slave device 2 Bit 17..24 Byte 71 0..7 Process data axis slave device 2 Bit 25..32 Byte 72 0..7 Process data axis slave device 2 Bit 33..40 Byte 73 0..7 Process data axis slave device 2 Bit 41..48 Byte 74 0..7 Process data axis slave device 2 Bit 49..56...
  • Page 48 Input/Output Data Byte 104 0..7 Process data axis slave device 5 Bit 1..8 Byte 105 0..7 Process data axis slave device 5 Bit 9..16 Byte 106 0..7 Process data axis slave device 5 Bit 17..24 Byte 107 0..7 Process data axis slave device 5 Bit 25..32 Byte 108 0..7 Process data axis slave device 5 Bit 33..40...
  • Page 49 Input/Output Data Following logic data Bit IDs are reserved for compatibility reasons and cannot be used (value is 0): • Bit ID 32 • Bit ID 88 • Bit ID 144 • Bit ID 200 • Bit ID 256 • Bit ID 312 •...
  • Page 50 Input/Output Data SCU-x-EC/NM 9.4.1 Output data Structure of the functional outputs Byte „Run“ mode (2, 3, 4, 8) Error case ( A, F) DEBUG 0 0..3 device mode 1, 2, 3, 4, 5, 6 = FatalError, 7 = Alarm, 8 0x1 (define) 5..7 Alive counter (3 Bit)
  • Page 51 Input/Output Data NOTICE: The meaning of the error codes in decimal notation can be found in the HB-37500-813- 02-xxF EN Error list SCU. 9.4.2 Input data Structure of functional input data Byte Assignment Byte 0 0..7 Functional Input (0..7) Byte 1 0..7 Functional Input (8..15) Byte 2...
  • Page 52 SD-Bus data SD-Bus data The universal communication interface (/DNM, /xNM, /DBM, /xBM) behaves like a gateway with regard to the SD bus data; communication from the SD bus to the fieldbus in both directions. 10.1 Fieldbus data SD-Bus Gateway For the Gateway diagnostics and for the acyclic data request of the SD slaves, 2 bytes are reserved in the request and the response of the fieldbus protocol.
  • Page 53 SD-Bus data 10.2 Fieldbus data SD slave For each SD slave, 2 bytes are reserved in the request and the response of the fieldbus protocol. - SD slave 01 uses byte 02 and 03 of the fieldbus - SD slave 02 uses byte 04 and byte 05 of the fieldbus …...
  • Page 54 SD-Bus data 10.3 Structure of the SD bytes in the fieldbus protocol Request for all fieldbus systems (OUTPUT byte control, transmission of the request data to the SD slaves) Byte no. Byte 00 Byte 01 Byte 02 Byte 03 Byte 62 Byte 63 SD device Gateway...
  • Page 55 SD-Bus data 10.4 Reading acyclic data from the SD slave In a permanently defined cycle, acyclic data of the individual SD slave can be requested through the 2 request bytes (fieldbus request byte 00 and byte 01) and the data byte (fieldbus response byte 01).
  • Page 56 SD-Bus data Instructions, Instruction SD address Data byte Data description acyclic data request byte fieldbus byte fieldbus byte 01 fieldbus (response) byte 00 (request) (request) Delete data byte Hex: 00 Hex: xx Hex: FF Data deleted, ready for new instruction Read number of projected SD slaves Hex: 01 Hex: 00...
  • Page 57 SD-Bus data The following device categories are defined: Hex: 30 CSS 34, Safety sensor Hex: 31 AZM 200, Solenoid interlock „Z“-variant Hex: 32 MZM 100, Solenoid interlock „Z“-variant Hex: 33 AZ 200, Safety sensor Hex: 34 CSS 30S, Safety sensor Hex: 35 MZM 100 B, Solenoid interlock „B“-variant Hex: 36...
  • Page 58 Safety Data Safety Data There are 12 bytes of secure data in each direction. These depend on the device description file, e.g.: ESI, EDS ... already predefined. Configuration of Diagnostic data is done in SafePLC². 11.1 Fieldbus Specific Safety Instructions Depending on the used fieldbus and the underlying safety protocol, additional instructions must be followed.
  • Page 59 Safety Data After a configuration download the user shall visually verify, that all configuration data has been sent correctly. 11.2 SMX1x/2/, SMX1xx/2(DNM, xNM, DBM, xBM) or SDU-x/NM Organization of the frame: Size of safety data: always 12 Byte F-Bus Input or Output: Byte Data BYTE 0...
  • Page 60 Safety Data Example: F-bus input Byte 0: Bit 0 is mapped to Bit 1 (E-Stop EXT) in the SafePLC² in the F-Bus module. Output F-Bus output: Bit 1 (Safety OK) is mapped to byte 0 bit 0 by the SafePLC². HB-37450-810-01-14F-EN COM Installation Manual.docx Page 60 of 67...
  • Page 61 Commissioning and Troubleshooting Commissioning and Troubleshooting 12.1 EtherNet/IP EtherNet/IP is available for all Ethernet based field bus devices. 12.1.1 Enabling Ethernet/IP fieldbus To activate the EtherNet/IP communication, the following steps should be followed: Ü Make sure, a project with a compatible device is created and opened in SafePLC2 Ü...
  • Page 62 Commissioning and Troubleshooting 12.1.2 Setting TCP/IP Parameters An out-of-box EtherNet/IP device does not have an IP address set and is waiting on an assignment through DHCP/BOOTP. The commissioning of a safety device with IP Address and TUNID settings should be done prior to installing it onto a safe network. Ü...
  • Page 63 Commissioning and Troubleshooting Ü Once applied, the device responds on your newly set IP address. This IP address is volatile and does not persist through power-off. Ü To permanently store the IP address in the device press “Disable BOOTP/DHCP” while the assigned device is selected.
  • Page 64 Commissioning and Troubleshooting 12.1.3 Propose and Apply TUNID (SNN) Every CIP Safety device needs a unique device identifier (TUNID, Target Unique Node ID). It has to be unique within the reachable network. The TUNID contains the SNN (safety network number) which also has to be unique. A SNN should be assigned for each safety network or safety sub-net that are unique system-wide.
  • Page 65 Commissioning and Troubleshooting 12.1.3.1 Propose/Apply Ü Stop the device by pressing the “Stop” button on the menu Ü Make sure no TUNID is applied to the device. Ü There are several ways to identify this state: An unset TUNID can be identified with an all FF entry and the specific date §...
  • Page 66 Commissioning and Troubleshooting Visually inspect the target device, both Module and Network LEDs must be § flashing red/green Ü When the correct target device has been addressed, press “Apply” Ü The Device Status label changes to “Idle” Ü The Current TUNID now shows the previously applied TUNID Ü...
  • Page 67 Commissioning and Troubleshooting 12.1.3.2 Reset to Out-Of-Box Ü Stop the device by pressing the “Stop” button on the menu Ü Press the "Reset" button in the "Connection > CIP Safety" window Ü Press the button “Reset” in the “Current TUNID” group box The response label reads “Command successful”...

This manual is also suitable for:

Smx seriesScu seriesSdu nm seriesSmx100 2 seriesScu ec/nm seriesSmx 12a/2 ... Show all