DSC fieldbus modules SIGNALS AND PINOUT MEANING IN FAIL EXT FAIL LED1 LED2 GREEN GREEN RED/GREEN RED/GREEN Startup - Initial test Waiting for configuration from Master see the modules tables Received configuration from Master Table 2 – Initial/ dynamic view. Module MBC Signal CAN_L...
DSC fieldbus modules Module MBEI LED NET STATE INDICATES/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 INDICATES DESCRIPTION No power GREEN RUN state GREEN blinking Not configured Fatal error...
DSC fieldbus modules Module MBEM LED NET STATE INDICATES/DESCRIPTION No power or no IP address GREEN Module is in Process Active or Idle state GREEN blinking Waiting for connections Duplicate IP address, or FATAL event RED blinking Process Active Timeout LED STS STATE INDICATES...
DSC fieldbus modules DESCRIPTION The MBx communication module gives access to various information related to the DSC system and allows to send commands from the PLC. Each device connected to the DSC inputs is characterized by an ON/OFF status and a possible diagnostic.
DSC fieldbus modules DIAGNOSTICS Each input and each safety output can generate a diagnostic code. When the I/O is connected correctly, the diagnostic code is OK and is not exported to the fieldbus; when a problem on the I/O is detected, the system exports 2 bytes to the fieldbus with: - the index of the I/O in question - the relative diagnostic code The "I/O index"...
DSC fieldbus modules The "Diagnostic code" field The "Diagnostic code" field indicates the diagnostics for the I/O. Possible values for this field are shown in the following tables. Input diagnostics CODE NAME MEANING Input diagnostics OK Not passed from zero Both contacts have not returned to their rest position The two contacts of a generic two-channel input do not close Simultaneous control failed...
Page 12
DSC fieldbus modules Output diagnostics CODE NAME MEANING Output diagnostics OK Enable missing Waiting for OSSD to restart Feedback K1 K2 missing Waiting for other micro Redundancy check failed on the OSSD OSSD power supply missing Exceeded maximum time restart Feedback K1 K2 external not congruous Waiting feedback K1 K2 OSSD output overload...
DSC fieldbus modules EXAMPLES OF DIAGNOSTICS Example 1 Figure 3 In the example shown in , Input 1 (connected to module M1/M1S) is tested with the M1- T1 test signal. During wiring, the 24Vdc is connected to input 1 instead of the M1-T1 test signal. The I/O index and Diagnostic code fields assume the following values: 1 - 20 to indicate the diagnostics on input 1 of module M1/M1S (Connection error).
DSC fieldbus modules Example 3 The example in Figure 5 is similar to example 1, except in this case Input1 is connected to module MI16 and is tested with the MI16-T1 test signal. During wiring, the 24Vdc is connected to input 1 instead of the MI16-T1 test signal. Input 1 has diagnostic code 10 (OUT_TEST error) and OUT_TEST MI16-T1 has diagnostic code 8 (Connection error).
DSC fieldbus modules BUS CONFIGURATOR USER INTERFACE The bus module is configured using the USB miniB interface on the front panel and the “Bus Configurator – User interface” software installed on the DSDESIGNER CD ROM disk. This software can be used for configuration/communication of the DSC system with a PC (using an MBU module) or to monitor the data transmitted on the fieldbus (via connection to the USB port of a bus module).
DSC fieldbus modules Graphical User Interface Module configuration must be performed with the system switched off (outputs OFF). Operator can query module configuration at any time while the module is in use. To configure the MBx module, proceed as follows: 1.
DSC fieldbus modules BACKWARD COMPATIBILITY (VERSION FOR M1 fw < 5.0.0) Process Image in backward compatibility (version for M1 fw < 5.0.0) The backward compatibility mode allows the Bus module to use the "old" process image mapping, i.e.: it will adapt to the hardware installed on the system. This allows to replace an existing Bus module without changing the PLC program.
Page 18
DSC fieldbus modules Diagnostic elements will use 2 bytes which indicate the number of the I/O with the problem and the value of the diagnostic element. If there is more than one diagnostic element, the relative values alternate every 500ms. Each set of information: input status, input diagnostics,...
DSC fieldbus modules Graphical User Interface, backward compatibility (version for M1 fw< 5.0.0.) The backward compatibility mode allows the operator to use the DSD software by having an M1 master module with firmware version lower than 5.0.0. This mode can be enabled from the menu: “ settings ->...
DSC fieldbus modules Process image configuration in backward compatibility The input process image and the output process image can be configured using the Bus Configurator User Interface software. With this software the user can choose which subsection must be exported in the fieldbus, changing the size of each process image and then the size used in the PLC physical memory.
DSC fieldbus modules EXAMPLES OF DSD CONFIGURATION AS PRESENTED BY THE BUS CONFIGURATOR Figure 11 – Example of project on DSD Figure 12 8540467 • 28/03/2019 • Rev.2...
DSC fieldbus modules • Input 1 E-STOP is connected to screws 6 and 7 on M1/M1S. Its status (zero or one) is shown on bit 5 of byte 0 reserved for inputs. The bit 6 is always set to zero, it is kept busy to signal that the E STOP occupies two screws on M1/M1S.
Need help?
Do you have a question about the DSC Series and is the answer not in the manual?
Questions and answers