Reer MOSAIC Micron Installation And Use Manual
  1. Manuals
  2. Brands
  3. Reer Manuals
  4. Control Unit
  5. MOSAIC Micron
  6. Installation and use manual

Reer MOSAIC Micron Installation And Use Manual

Fieldbus modules
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Fieldbus modules
FIELDBUS MODULES
Installation and use

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the MOSAIC Micron and is the answer not in the manual?

Questions and answers

Related Manuals for Reer MOSAIC Micron

Summary of Contents for Reer MOSAIC Micron

  • Page 1 Fieldbus modules FIELDBUS MODULES Installation and use...

  • Page 2: Table Of Contents

    Fieldbus modules MOSAIC FIELDBUS MODULES TABLE OF CONTENTS MOSAIC FIELDBUS MODULES ..........................2 INTRODUCTION ........................4 DESCRIPTION ................................5 ELECTRICAL CONNECTIONS ....................5 Possible connections of MBx / MI-Bx modules ..............6 Possible connections of MBU / MI-BU modules ..............7 MODULES FW VERSION <...
  • Page 3 Fieldbus modules Open Command ......................45 Save Command ......................45 Exit Command ......................45 Setting Menu ........................46 Select Language Command .................... 46 Update Command (Firmware, Eeprom, Firmware Network) ..........46 Select Stack Command ....................46 Enable Backward Compatibility Command ............... 47 Factory Reset Command ....................

  • Page 4: Introduction

    Fieldbus modules INTRODUCTION The following tables describe the main characteristics of the BUS modules of the MOSAIC series according to the firmware version. Firmware version <3.0.0 Base Code Installed stacks Data source Ethernet PROFIBUS DP-V1 MOSAIC Master DeviceNet MOSAIC Master CANopen MOSAIC Master MBCCL...

  • Page 5: Description

    Fieldbus modules DESCRIPTION The MBx communication modules give access to various information relating to the Mosaic system, while the MI-Bx communication modules give access to information relating to the Micron barriers. Both modules allow sending of commands from the PLC. Each device connected to the Mosaic inputs is characterized by an ON/OFF status and possible diagnostics.

  • Page 6: Possible Connections Of Mbx / Mi-Bx Modules

    Fieldbus modules POSSIBLE CONNECTIONS OF MBX / MI-BX MODULES In this case, the MBx and MI-Bx modules are connected to the data source (Master M1/M1S or Micron barrier). The connection of the PC via USB cable (USB "C" interface) is used to configure the module and, if desired, to monitor the data arriving from the source.

  • Page 7: Possible Connections Of Mbu / Mi-Bu Modules

    Fieldbus modules POSSIBLE CONNECTIONS OF MBU / MI-BU MODULES In this case, the MBU and MI-BU modules are connected to the data source (M1/M1S Master or Micron barrier). The connection of the PC via USB cable (USB "C" interface) is used to configure the module and, if desired, to monitor the data arriving from the source.

  • Page 8: Modules Fw Version < 3.0.0

    Fieldbus modules MODULES FW VERSION < 3.0.0 Each module is equipped with four connectors (Figure 1): MSC five-way connector to the MOSAIC system Mini-USB connector to a PC BUS/LAN connectors to the fieldbus or the Ethernet network (not present on MBU) Front terminal strip supply TERMINAL STRIP CONNECTIONS (SIDE A - TOP)

  • Page 9: Signals And Pinout

    Fieldbus modules SIGNALS AND PINOUT Initial / Dynamic view MEANING IN FAIL EXT FAIL LED1 LED2 GREEN GREEN RED/GREEN RED/GREEN Startup - Initial test Waiting for configuration from M1/M1S Received configuration from M1/M1S see the modules tables Table 2 - Initial/dynamic view Diagnostics signals FAULT DIAGNOSIS MEANING...

  • Page 10: Module Mbc / Mi-Bc

    Fieldbus modules MODULE MBC / MI-BC Signal CAN_L CAN_GND CAN_SHIELD CAN_H DB9 – male (front view) Housing CAN_SHIELD LED OPR STATUS INDICATION DESCRIPTION GREEN OPERATIONAL OPERATIONAL status GREEN blinking slow PRE-OPERATIONAL PRE-OPERATIONAL status GREEN 1 flash STOPPED STOPPED status GREEN blinking fast Autobaud Baud rate detection EXCEPTION...

  • Page 11: Module Mbd / Mi-Bd

    Fieldbus modules MODULE MBD / MI-BD Signal Description Negative BUS power supply CAN_L CAN low bus line SHIELD Cable shield CAN_H CAN high bus line Positive BUS power supply (front view) LED NET STATUS INDICATION DESCRIPTION GREEN On-line connected 1 or more connections established GREEN blinking (1Hz) On-line non connected No connection established...

  • Page 12: Module Mbp / Mi-Bp

    Fieldbus modules MODULE MBP / MI-BP Signal Description B-line Positive RxD/TxD, RS485 level Request to send GND Bus 0VDC (isolated) +5VDC (isolated/short circuit protected) DB9 – female A-line Negative RxD/TxD, RS485 level (front view) Internally connected to the Anybus protective earth via Housing Cable shield cable shield filters according to the PROFIBUS standard...

  • Page 13: Module Mbec / Mi-Bec

    Fieldbus modules MODULE MBEC / MI-BEC LED STS STATUS INDICATION DESCRIPTION INIT INIT or no power GREEN OPERATIONAL OPERATIONAL state GREEN blinking PRE-OPERATIONAL PRE-OPERATIONAL state GREEN blinking (1 flash) SAFE-OPERATIONAL SAFE-OPERATIONAL state Flickering BOOT Module in BOOT state (Fatal Event) System locked LED ERR STATUS...

  • Page 14: Module Mbei / Mi-Bei

    Fieldbus modules MODULE MBEI / MI-BEI LED NET STATE INDICATION / DESCRIPTION No power or no IP address GREEN On-line, connected GREEN blinking On-line, not connected Duplicate IP address RED blinking Connection timeout LED STS STATE INDICATION DESCRIPTION No power GREEN RUN state GREEN blinking...

  • Page 15: Module Mbep / Mi-Bep

    Fieldbus modules MODULE MBEP / MI-BEP LED NET STATE INDICATION DESCRIPTION • No power Offline • Connection with IO controller not present • Established connection with IO controller GREEN Online (RUN) • IO controller in RUN state • Established connection with IO Controller GREEN blinking Online (STOP) •...

  • Page 16: Module Mbem / Mi-Bem

    Fieldbus modules MODULE MBEM / MI-BEM LED NET STATE INDICATION / DESCRIPTION Module in EXCEPTION state or no IP address GREEN On-line, at least one message received GREEN blinking On-line, waiting for first message IP address conflict, FATAL ERROR RED blinking Connection Timeout.

  • Page 17: Module Mbccl / Mi-Bccl

    Fieldbus modules MODULE MBCCL / MI-BCCL Signal Description Positive RS485 RxD/TxD Negative RS485 RxD/TxD Signal Ground Cable shield Protective Earth (front view ) LED NET STATUS DESCRIPTION No network participation, timeout status (no power) GREEN Participating, normal operation Major fault (FATAL error) LED ERR STATUS INDICATION...

  • Page 18: Module Mbmr / Mi-Bmr

    Fieldbus modules MODULE MBMR / MI-BMR Direction Signal Description Housing Protective Earth Bus polarization 0VDC (isolated) Bus polarization +5VDC (isolated) Connect to pin 2 for RS-232 / Leave unconnected for RS-485 Bidirectional B-line RS-485 B-line DB9 – female (front view) RS-232 Data Receive RS-232 Data Transmit Bidirectional...

  • Page 19: Module Mbepl

    Fieldbus modules MODULE MBEPL LED STS STATE INDICATION DESCRIPTION Module is off, initializing, or not active. GREEN fast flashing Basic Ethernet state: NMT_CS_BASIC_ETHERNET (on 50ms - off 50ms) no POWERLINK traffic has been detected. GREEN single flash NMT_CS_PRE_OPERATIONAL_1 Only asynchronous data. Asynchronous and synchronous data.

  • Page 20: Module Mbu / Mi-Bu

    Fieldbus modules MODULE MBU / MI-BU LED CONNECT STATE INDICATION DESCRIPTION GREEN USB connected Module connected to Pc via USB USB not connected Module not connected 8541654 • 12/04/2023 • Rev.0...

  • Page 21: Modules Fw Version ≥ 3.0.0

    Fieldbus modules MODULES FW VERSION ≥ 3.0.0 Each module is equipped with four connectors (Figure 2): MSC 5-way connector to the MOSAIC system USB "C" connector to a PC BUS/LAN connectors to the fieldbus or the Ethernet network (not present on MBU) Front terminal strip power supply TERMINAL STRIP CONNECTIONS (SIDE A - TOP)
  • Page 22 Fieldbus modules When the module is switched on, the presence or absence of the data source is checked (be it a M1/M1S Master module or a Micron barrier). If no data source is detected within ten seconds, the module will start anyway the Ethernet communication and will start with a default process map having the following dimensions: MBx modules: 4 bytes of fieldbus inputs / 33 bytes of I/O...

  • Page 23: Signals And Pinouts

    Fieldbus modules SIGNALS AND PINOUTS Initial/Dynamic Phase Signalling LEDs MEANING IN FAIL EXT FAIL LED1 LED2 GREEN GREEN RED/GREEN RED/GREEN Power-on - Initial TEST Awaiting configuration from M1/M1S Configuration received from M1/M1S See single modules tables Blinking FWUPDATE_NNNN.ZIP file update quickly Table 5 - Opening/dynamic display Diagnostics Signalling...

  • Page 24: Mbec / Mi-Bec Module

    Fieldbus modules MBEC / MI-BEC MODULE MS LED ("RUN STATUS") STATUS INDICATION DESCRIPTION INIT INIT state or no supply GREEN Blinking (2.5Hz) PRE-OPERATIONAL PRE-OPERATIONAL status GREEN (1 blink) SAFE-OPERATIONAL SAFE-OPERATIONAL status GREEN OPERATIONAL OPERATIONAL status NS LED ("ERROR STATUS") STATUS INDICATION DESCRIPTION NO ERROR...

  • Page 25: Mbei / Mi-Bei Module

    Fieldbus modules MBEI / MI-BEI MODULE MS LED ("MODULE STATUS") STATUS INDICATION DESCRIPTION NO POWER The device is off GREEN DEVICE OPERATIONAL The device works perfectly On steady GREEN STANDBY The device was non configured Blinking (1Hz) The device is performing the power-on test. The test sequence of the module status indicator occurs before the test sequence of the network status indicator, in the following...

  • Page 26: Mbep / Mi-Bep Module

    Fieldbus modules MBEP / MI-BEP MODULE MS LED ("SYSTEM FAILURE") STATUS INDICATION DESCRIPTION NO ERROR No error DCP signal service is started via the bus Blinking (1Hz, 3s) Channel, generic or extended diagnostics present; WATCHDOG TIMEOUT On steady system error NS LED ("BUS FAILURE") STATUS INDICATION...

  • Page 27: Mbem / Mi-Bem Module

    Fieldbus modules MBEM / MI-BEM MODULE MS LED ("MODULE STATUS") STATUS INDICATION DESCRIPTION NOT READY OMB task is not ready. GREEN OMB task has established a communication. CONNECTED On steady At least a TCP connection is established. GREEN READY, NOT OMB task is ready, but not configured yet.

  • Page 28: Mbecom / Mi-Becom Module

    Fieldbus modules MBECOM / MI-BECOM MODULE The MBECOM/MI-BECOM module is a multi-stack module. Therefore, the user, through of the BUS software configurator can choose which stack to install the module on. The available stacks are: EtherNet/IP -> MBEI / MI-BEI Module Modbus TCP ->...

  • Page 29: Mbu / Mi-Bu Module

    Fieldbus modules MBU / MI-BU MODULE LED CONNECT STATUS INDICATION DESCRIPTION GREEN USB connected Module connected to PC via USB USB not connected Module not connected 8541654 • 12/04/2023 • Rev.0...

  • Page 30: Process Map

    Fieldbus modules PROCESS MAP MBx MODULES: CYCLIC DATA System and I/O status is available on the cyclic process map. Cyclic data is listed in the table below Data direction: from the module to the PLC Data Notes Indicates the status of the Master, the presence of diagnostics System status (status byte) and errors.

  • Page 31: Mbx Modules: Acyclic Data

    Fieldbus modules MBx MODULES: ACYCLIC DATA Acyclic data is listed in the table below: Data Notes System I/O System status + input/output status I/O diagnostics System errors Available with firmware version ≥ 2.0.0 (if a fault is present) Available only with M1/M1S in version ≥ 5.0 CRC program loaded on M1/M1S Available only with M1/M1S in version ≥...
  • Page 32 Fieldbus modules If two or more modules of the same type are installed, the one with the lowest node number is displayed first. Each module equipped with digital inputs occupies several BITs corresponding to the number of physical inputs; M1/M1S, MI8, MI8O2, MI8O4 modules will therefore use 1 byte, MI12T8 and MI16 modules will use 2 bytes.

  • Page 33: Mbx Modules: Troubleshooting

    Fieldbus modules MBx MODULES: TROUBLESHOOTING Each safety input and output can generate a diagnostics code. When the I/O is connected correctly, the diagnostics code is "DIAGNOSTICS_OK". When diagnostics are generated on an input or output, the system exposes 2 bytes: - the index of the input or output which generated the diagnostics ("I/O index").

  • Page 34: I/O Index" Field

    Fieldbus modules "I/O INDEX" FIELD This field indicates the number used to identify the I/Os with a diagnostics code other than "DIAGNOSTICS_OK". The I/O index range depends on the system version used. Please refer to the following tables for the values of these data.

  • Page 35: Diagnostics Code" Field

    Fieldbus modules "DIAGNOSTICS CODE" FIELD To examine the diagnostics in question, read the document ”8547781 - ERRORS CODE / DIAGNOSTICS” which can be downloaded from the website "www.reersafety.com" 8541654 • 12/04/2023 • Rev.0...

  • Page 36: Mi-Bx Modules: Cyclic Data

    Fieldbus modules MI-Bx MODULES: CYCLIC DATA The beam status or Micron barrier measurements are available on the cyclic process map. Cyclic data is listed in the table below: Data direction: from the module to the PLC Data Notes Beams status/measurements Data direction: from the PLC to the module Data transmission request command...

  • Page 37: Mi-Bx Modules: General Information

    Fieldbus modules MI-Bx MODULES: GENERAL INFORMATION The process map provides the beam status or the barrier measurements. The map can range from a minimum of 1 byte up to a maximum of 58 bytes. The BITs of each byte represent the status of each beam or measurement, depending on how the Micron barrier was configured by the user.

  • Page 38: Bus Configurator

    The bus module is connected to the configuration PC via the USB "C" or "mini-USB" interface located on the front panel. Configuration is performed with the "Bus Configurator - User interface" software that can be downloaded from the ReeR website. Starting from version 5.0.0, the software is supplied in two versions: ▪...
  • Page 39 Fieldbus modules At the top right there are the boxes "CPU Error 0" and "CPU Error 1", which show the error information if Mosaic module fails. The box highlighted in black contains information about the inputs and outputs, together with diagnostics.

  • Page 40: User Interface For Mi-Bx Modules

    Fieldbus modules User interface for MI-Bx modules If the BUS module connected to the PC belongs to the MI-Bx series, then the user interface will be similar to the following image. At the top right, there is the "CPU Error 0" box which shows the error information if the Micron barrier fails.
  • Page 41 Fieldbus modules At the bottom right (circled in red) there are five types of information: ▪ network status o EtherNet/IP stack: it indicates whether there is or not a network connection if the PLC is not connected. When the PLC is connected to the module, then it indicates the presence or not of the connection to the PLC.

  • Page 42: Connect Button (Command)

    Fieldbus modules CONNECT BUTTON (COMMAND) The Connect button is available as soon as a powered BUS module is connected to the configuration PC via a USB cable. Figure 4 - Software interface without the BUS module. ➔ The Connect button is not available, the "BUS Module" label at the bottom right shows the module as "Not Present".
  • Page 43 Fieldbus modules Figure 5 If the communication is successful: 1) information regarding the network configuration, network status, module status and process map status will be received (i.e., if "Analogue data" or "Restart Input Status" have been previously selected). 2) the monitor will automatically start enabling the process data cyclical reception from the BUS module.

  • Page 44: Write Button (Command)

    Fieldbus modules WRITE BUTTON (COMMAND) The Write button is used to write the configuration on the module. The configuration concerns the network and the process map parameters (either fixed or in backwards-compatible mode). The configurable network parameters depend on the type of stack installed. The process map parameters regard: •...

  • Page 45: File Menu

    Fieldbus modules FILE MENU Open Command This command is used to open a previously saved configuration from a file. Save Command This command is used to save the current configuration of the BUS module on a file. Exit Command exit This command is used to the software and close.

  • Page 46: Setting Menu

    Fieldbus modules SETTING MENU Select Language Command This command is used by the user to change the language of the software. Update Command (Firmware, Eeprom, Firmware Network) ➔ Warning: The Update -> Firmware Network command is only available for BUS modules with firmware ≥...

  • Page 47: Enable Backward Compatibility Command

    Fieldbus modules The software autonomously recognizes the type of connected module and enables or not this command according to the detected module. Progress is displayed when the command is performed. Figure 9 If the command has been performed successfully, the following image will appear Figure 10 Enable Backward Compatibility Command ➔...
  • Page 48 Fieldbus modules A new "Backward compatibility" tab will then appear (see Figure 11) enabling the user to choose the subsection to be exported to the fieldbus (ref. Figure 11) by changing the size of each process map and, therefore, the size used in the physical memory of the PLC. When the module is connected, all data is displayed in the main software window.
  • Page 49 Fieldbus modules Process map in backwards compatibility (version for M1 fw < 5.0.0) The backwards compatibility mode allows the Bus module to use the variable process map. This allows to replace an existing Bus module without modifying the PLC program. ➔...
  • Page 50 Fieldbus modules If two or more modules of the same type are installed, the one with the lowest node number is displayed first. Each module equipped with inputs has a number of BITs corresponding to the number of physical inputs; M1, MI8, MI8O2 modules will therefore use 1 byte, and MI12T8 and MI16 modules will use 2 bytes.

  • Page 51: Factory Reset Command

    Fieldbus modules Factory Reset Command This command is used to reset the network parameters and process map parameters to the factory default settings. For example, if the module process map was configured with "Analogue Data", after a "Factory Reset" it will go back to being without "Analogue Data". Confirmation is requested before performing the command.

  • Page 52: Menu

    Fieldbus modules "?" MENU "About..." Command When this command is performed, a window is displayed that summarizes some information about the currently connected module. Figure 14 Namely: • App fw Network SoC: firmware version of the network controller (if available) •...

  • Page 53: Msd Configuration Examples As Shown By The Bus Configurator

    Fieldbus modules MSD CONFIGURATION EXAMPLES AS SHOWN BY THE BUS CONFIGURATOR Figure 15 – Example of a project on MSD Figure 16 8541654 • 12/04/2023 • Rev.0...

  • Page 54: Input Status Of The Mv Modules

    Fieldbus modules • E-STOP input 1 is connected to screws 6 and 7 on M1/M1S. Its status (zero or one) is contained in BIT 5 of byte 0 reserved for inputs. BIT 6 is always set to zero: it is kept fixed to signal that the E-STOP occupies two screws on M1/M1S.

  • Page 55: Process Maps

    Fieldbus modules PROCESS MAPS To examine the process map in question, read the document ”8547782 - PROCESS DATA MAPPING” which can be downloaded from the website “www.reersafety.com” 8541654 • 12/04/2023 • Rev.0...

Table of Contents