42 RT Flex Bus System
42 RT Flex Bus System
42 RT Flex Bus System
Chapter 42
Wrtsil Land & Sea Academy 1 Chapter 42
There are many possibilities to connect the various sensors, controllers, switches, transmitters, actuators, etc.
Page 2
Chapter 42
Traditional Cabling
Page 3
Chapter 42
Bus Connections
Bus Connections
Sensor cables
Bus cables
Wrtsil Land & Sea Academy
Page 4
Chapter 42
Bus Connections
Bus elements ( (so called nodes) ) are communicating g very y fast by y exchanging digital messages in a defined, Bus specific language (so called protocol) over a two-wire cable. Different systems may use different protocols protocols. In a Bus system all nodes are connected in series, one after the other. There are clearly defined two ends of each Bus. Bus systems MUST NOT be connected in parallel as star-connection.
Page 5
Chapter 42
Bus Connections
Less cabling g work with low risk of malfunctioning. g Bus systems are robust in electromagnetically noisy environments. Special BusBus or Data cables have to be used used. At each end of the Bus cable, there must be a terminating resistor of p p specified resistance matched with the wave impedance of the Bus cable.
Page 6
Chapter 42
Bus Systems
Bus systems y used for WECS-9520: CANopen (System Bus and Module Bus) ModBus SSI Bus
Page 7
Chapter 42
CAN Bus
CAN Bus
CAN (Controller Area Network) is a multicast shared, differential serial bus standard, originally developed by Bosch for connecting l t i control t l units it i t ti i d t electronic in th the automotive industry. CANopen is a standard CAN protocol for process control systems according to ISO 11898. WECS-9520 uses two different CANopen Busses: System Bus and Module Bus. Each FCM-20 module has three CANopen interfaces. The System Bus is used for the communication between FCM-20 modules and is not leaving the rail unit box. There are two S-Buses y reasons. for redundancy The Module Bus is connecting only one specific FCM-20 module to internal or external devices.
Page 8
Chapter 42
Alarm System
Digital Governor
dPSC
MMI
FCM 1
CAN
FCM 2
CAN
FCM 3
CAN
FCM 4
CAN
FCM 5
CAN
Parameters and indications from and to Crew Operator Interface Al t Alarms to AMS
Wrtsil Land & Sea Academy
Modbus
ModBus
Modbus is a data transmission protocol for process control systems. It was developed p by y the company p y Gould Modicon, which named their bus protocol by the company's name. The basic function of the ModBus system is the same as with CAN but using a different language. Each FCM-20 has one RS-485 interface used for ModBus connection to either a Lyngs Propulsion Control System or to any external Alarm Monitoring System which required such protocol. ModBus system is used for some Propulsion Control System and AMS.
Page 10
Chapter 42
Modbus
This protocol defines, how data is exchanged between different h d hardware d devices. i E Each hd data t message i is wrapped d up i in an envelope. l In the Modbus protocol they are called message frames or application data units (ADU). They are sent by the master through a port and carried across the bus to the addressed device, the slave. A message contains the address of the intended receiver, a code to define what the receiver shall do do, the data to perform this action with and a bit frame to check the content for errors. Once the slave received the message through its port, it reads out the data and the request, checks for errors and, if no none found, carries out the requested operation. Then it updates the same stored message, returns it back to sender, so the master knows, that the requested action was carried out (normal reply). p y) This is called handshaking. g
Wrtsil Land & Sea Academy
Page 11
Chapter 42
Modbus
Else if, the execution fails or the data was faulty, the slave returns an error error reply reply to the master master. The data transmission mode for the Modbus data is the RTU [Remote Terminal Unit] mode. Possible is also ASCII [American Standard Code f. Information Interchange) mode like on a normal PC, but RTU is twice as fast as the ASCII and therefore default in the modbus protocol. p The RTU coding format is 1 byte = 11bit, z 1 start bit z 8-bit binary for the data, least significant bit first, 2x 4bit hexadecimal characters z 1 bit for parity completion (not used with WECS9520 and therefore:) z 2 stop bits (instead of 1 bit, because of no parity).
Page 12
Chapter 42
Modbus
A message g normally y contains more than one byte y of data information. The slaves recognize separate messages from each other by a silent interval of a certain length between the different messages (or packets). Only the master addresses actions from the slave. Therefore the each slave needs to have its own address address, while the master does not require one. In the WECS application always the propulsion control or the alarm monitoring system is the master. The FCM-20 modules only work as slave and respond to requests from PCS or AMS. All FCM-20 modules have the hexadecimal address 11h.
Page 13
Chapter 42
Modbus
The Alarm Monitoring System reads out WECS failure messages and flexView data from FCM-20 #3 and #4. Both busses carry out exactly the same actions, i.e. the bus traffic is redundant. The Propulsion Control System delivers all required maneuvering data fuel command data, command, data for manual control panels (MCP) and safety system states to FCM-20 #1 and #2.
Page 14
Chapter 42
SSI Bus
SSI Bus
The SSI Bus is a very fast Bus system. The SSI Bus is used for transmission of Crank Angle Encoders signals to FCM-20 modules (except the spare on line one). The SSI Bus consist of two lines: Clock Bus and Data Bus. Always the last and one before the last cylinder modules are generating Clock Pulses send over the Clock Bus to synchronize transmission and reception of data trough the Data Bus. Termination resistors are required on the end of the Bus lines except the E96 box (Crank Angle Encoders are equipped with built in terminators). terminators)
Page 15
Chapter 42
Bus Telegram
Bus Telegram
The Bus message, the Bus Telegram, consist of the following information:
SOF 1 bit Arbitration 12 bits Control 6 bits Data 1-64 bits CRC 9 bits Ackn. 2 bits EOF 1 bits
The Telegram can not be read with normal instruments It can only be read by suitable Bus Analyzer Analyzer. Physical condition of the Bus can be assessed by oscilloscope.
Page 16
Chapter 42
Bus cabling
Special p attention has to be put p on the Bus cabling. g Only special CAN or Bus cables may be used
Page 17
Chapter 42
Bus cabling
Terminator resistors
At each end of the Bus cable a terminator resistor of 120 must be installed to avoid signal reflection.
Page 18
Chapter 42