DIOLINE PLC 746033 · 2018-04-03 · DIOLINE PLC Safety 8 3Safety 3.1 Content of the Manual Read...

Operating Instructions

DIOLINE PLCMVB-COM, Part-No. 746033

Version 03

Lütze Transportation GmbHBruckwiesenstraße 17-19D-71384 WeinstadtTel.: +49 (0) 7151 6053-545Fax: +49 (0) 7151 6053-6545Sales.Transportation@luetze.dewww.luetze-transportation.com

DIOLINE PLC ▪ Content

Content1 Introduction .................................................................................................. 52 General Information ..................................................................................... 62.1 Symbol Description................................................................................................................. 62.2 Copyright ................................................................................................................................ 62.3 Disclaim of Liability ................................................................................................................. 62.4 Related Documents ................................................................................................................ 7

3 Safety............................................................................................................. 83.1 Content of the Manual ............................................................................................................ 83.2 Intended Use .......................................................................................................................... 83.3 Recipients............................................................................................................................... 83.4 Operating Employees ............................................................................................................. 83.5 Responsibility of the Operator ................................................................................................ 93.6 Protective Clothing and Equipment ........................................................................................ 93.7 Labeling .................................................................................................................................. 93.8 Reconstruction and Modifications of the Product ................................................................. 103.9 Safety Arrangement.............................................................................................................. 103.10 Special Safety Messages ..................................................................................................... 10

4 Product Overview....................................................................................... 114.1 Product Description .............................................................................................................. 114.2 Hardware Options................................................................................................................. 114.3 Software Options .................................................................................................................. 124.4 System Overview.................................................................................................................. 134.5 Field of Application ............................................................................................................... 14

5 Transport and Storing................................................................................ 156 Scope of Delivery ....................................................................................... 167 Product Assembly...................................................................................... 177.1 LED Display.......................................................................................................................... 187.2 LED Display-Digital Inputs .................................................................................................... 19

8 Technical Data ............................................................................................ 209 Mounting ..................................................................................................... 239.1 Mounting Options ................................................................................................................. 23

10 Initial Operation – Hardware...................................................................... 2410.1 Power Supply ....................................................................................................................... 2410.2 L-Bus – Interface .................................................................................................................. 2510.3 Serial Interface ..................................................................................................................... 2710.4 Ethernet Interface ................................................................................................................. 2810.5 Fieldbus 1 MVB Interface ..................................................................................................... 2910.6 Fieldbus 2 Interface – CANopen .......................................................................................... 31

11 Initial Operation – Software....................................................................... 3211.1 Installation ............................................................................................................................ 3311.1.1 MULTIPROG ........................................................................................................................ 3311.1.2 ProConOS OPC Server ........................................................................................................ 3411.1.3 Lütze Addons........................................................................................................................ 3511.2 IP Configuration.................................................................................................................... 3611.2.1 PC IP Address ...................................................................................................................... 3611.2.2 Communication Check ......................................................................................................... 3811.2.3 PLC IP Address .................................................................................................................... 3911.2.4 Resetting the TCP/IP Address.............................................................................................. 40

DIOLINE PLC ▪ Content

11.3 Development Environment System – MULTIPROG............................................................. 4111.3.1 Creating a MULTIPROG Project .......................................................................................... 4111.3.2 Ressource Settings .............................................................................................................. 4311.3.3 Function Blocks and Firmware Libraries .............................................................................. 4511.3.4 ProConOS.INI....................................................................................................................... 5011.3.5 Variables............................................................................................................................... 5111.4 Configuration of the Fieldbusses and other Interfaces ......................................................... 5711.4.1 L-Bus Configuration.............................................................................................................. 5711.4.2 SD Card Configuration ......................................................................................................... 6311.4.3 PFD – Parallel Flash Disk..................................................................................................... 6611.4.4 Real Time Clock Configuration............................................................................................. 7211.4.5 MVB Slave Configuration ..................................................................................................... 7511.4.6 CANopen Master Configuration............................................................................................ 8411.5 Compiling and Loading....................................................................................................... 10511.5.1 Download of Configuration Files......................................................................................... 10511.5.2 Downloading a MULTIPROG Project ................................................................................. 10611.5.3 Deleting the Flashdisk ........................................................................................................ 10811.6 Visualization – ProVisIT...................................................................................................... 109

12 Operation .................................................................................................. 11012.1 Hardware Architecture ........................................................................................................ 11012.2 Software Architecture ......................................................................................................... 11212.3 Memory Architecture (non volatile memory) ....................................................................... 11312.3.1 RAM Architecture (volatile memory) ................................................................................... 11412.3.2 Monitoring the PLC tasks and CPU Capacity ..................................................................... 11912.3.3 L-Bus Performance............................................................................................................. 122

13 Maintenance Software ............................................................................. 12313.1 Update Firmware (ProConOs) ............................................................................................ 12313.1.1 Update via MULTIPROG .................................................................................................... 12313.1.2 Updating the PLC via the SD Card..................................................................................... 125

14 Demounting .............................................................................................. 13015 Final Shutdown and Disposal ................................................................. 13116 Service....................................................................................................... 13217 Error Treatment ........................................................................................ 13317.1 Error Messages of the Function blocks .............................................................................. 13317.1.1 L-BusInfo ............................................................................................................................ 13317.1.2 MVBInfo, Sink and Source ................................................................................................. 13317.1.3 CoRec and CoSend............................................................................................................ 13417.1.4 SetDateTime....................................................................................................................... 13517.1.5 FILE_OPEN........................................................................................................................ 13517.1.6 FILE_READ ........................................................................................................................ 13517.1.7 FILE_WRITE ...................................................................................................................... 13617.1.8 FILE_CLOSE...................................................................................................................... 136

18 Appendix ................................................................................................... 13718.1 Content of the Firmware Libraries ...................................................................................... 13718.1.1 MVB-IKS Firmware Library ................................................................................................. 13718.1.2 ProConOS Firmware Library .............................................................................................. 13818.2 DIOLINE 20 Module Types................................................................................................. 14318.3 Autoexec.bat Commands ................................................................................................... 144

19 Revision of the Document ....................................................................... 145

DIOLINE PLC ▪ Introduction

5

1 IntroductionThis manual is part of the DIOLINE PLC. It contains important information about the handling and safety. To avoid hazardous situations read the manual before installing the product and using it.

Store the manual at a handy place. If selling, renting or in case of a divestiture pass the manual to the authorize person.

DIOLINE PLC ▪ General Information

2 General Information2.1 Symbol Description

The manual contains several safety messages. Each safety message contains a defined signal word and a color. The color and the word are referring to an alert level. There are 4 levels. The safety messages point out hazardous situations and give information to avoid those.

2.2 CopyrightThis manual is intended for the operator and his staff. It is forbidden to give the content to a third party, to duplicate, exploit or impart it. The Lütze Transportation GmbH has to allow it explicit in writing.

General data, text, images and drawings are copyrighted and are liable to the industrial property right. Contravention can be prosecuting criminally. The named brands and product names in this document are trademarks or registered trademarks by titleholder.

2.3 Disclaim of LiabilityThe manual was written under consideration of the applied standards, regulations and the current state of technology. The content is verified of accuracy. Discrepancies are not excluded. For those discrepancies we disclaim liability. Applicable changes and additional information will be in the next version of the manual.

The Lütze Transportation GmbH does not assume liability for any damages and accidents of following reasons:

▪ Nonobservance of the manual

▪ Untrained and unqualified employees

▪ Non conventional use

▪ Non approved reconstructions and functional modifications of the product

▪ Using non original or non admitted parts or equipment

▪ The real-time capability of the controller

Indicates a hazardous situation which, if not avoided will result in death or serious injury.

Indicates a hazardous situation which, if not avoided could result in death or serious injury.

Indicates a hazardous situation which, if not avoided could result in minor or moderate injury.

Is used to address practices not related to personal injury.

6

DIOLINE PLC ▪ General Information

2.4 Related DocumentsThe programming environment of the DIOLINE PLC is a product of the company KW Software and Hilscher. The companies are responsible for the documentation and the compliance of standards. This document contains short parts of the software documentation. In particular cases apply to:

KW-Software GmbHLagesche Straße 3232657 LemgoTel. +49 52619373-0Fax. +49 52619373-26

Hilscher Gesellschaft für Systemautomation mbHRhein Straße. 1565795 HattersheimTel. +49 61909907-0Fax. +49 61909907-50

7

DIOLINE PLC ▪ Safety

3 Safety3.1 Content of the Manual

Read and follow the manual before using the product the first time.

This applies to every person which is getting in touch with the product. Trained employees and experts especially qualified persons which had worked with similar products before have to read and understand the manual.

3.2 Intended UseThe DIOLINE PLC is designed for the exclusive use in railway vehicles.

For:

▪ automation of simple vehicles

▪ as a subsystem controller or

▪ as a high capacity gateway for the realization of different vehicle specific bus signals

Use the DIOLINE PLC just for the listed cases and just with external devices recommended and allowed by Lütze Transportation GmbH.

3.3 RecipientsThe operating manual adresses planers, project manager and programmers. It also adresses the operating employees which are responsible for the initial operation, the operating and for the maintenance of the products and systems. Regarding the employees different qualification levels are differentiated.

3.4 Operating Employees

Trained EmployeesThe employee was trained by the employer on the task and possible hazardous situations. The employee does not have any technical knowledge.

ExpertsThe employee has a technical education, knowledge and/or experience in the required field. The employee is capable to do specific operations on and with the product.

Electrically Qualified Persons The employee has a technical education in the required field. The employee is capable to do special operations on and with the product.

The different sections referringt to the qualification level of the operating employees.

Risk of injury by deploying insufficient qualified operating employees. Inappropriate use of not qualified or insufficient personal can cause property damages and personal injuries. Tasks which apply special procedures should be done by trained and qualified employees or experts, especially electrically qualified persons.

8


3.5 Responsibility of the OperatorThe operator is obligate by the law of occupational safety, if the product is used in a commercial field.

▪ The operator is responsible to train the employees and to inform himself about the industrial safety regulation.

▪ The operator is responsible that safety-, environment protection regulations and rules for accident prevention are observed.

▪ The operator has to run a risk assessment at the working environment/place of installation to expose hazards and to alert those.

▪ The manual has to be stored near the product.

▪ The manual has to be obeyed.

▪ The product can just be run in a faultless technical condition.

3.6 Protective Clothing and EquipmentIf working with or on the PLC special ESD clothing and equipment is mandatory. Also follow the instructions and regulations of the employer.

3.7 Labeling

On the product following label with following data can be found:

Fig. 1: Example Label

▪ Part-Number

▪ Hardware Revision

▪ Assembly Term

▪ Software-Version

▪ Serialnumber

Mind the original adhesive labels. Keep them readable.

9


3.8 Reconstruction and Modifications of the Product

3.9 Safety Arrangement

3.10 Special Safety Messages

Reconstructions and modifications of the product can cause property damages or personal injuries. Do not reconstruct or modify the product if the manufacturer does not allow it explicit in writing.

Do not bypass protection equipment and safety arrangements. The product can be damaged by overvoltage and electric shocks are possible.

Use a nominal operating voltage of 24 Volts. The lower (16.8 Volts) and upper (30 Volts) threshold voltage is given in the technical data. A higher voltage can cause electric shocks and damage the product.

Dismount all electronic modules and their connections from the frame if you intend to do some welding. The product can be damaged by compensating current.

10

DIOLINE PLC ▪ Product Overview

4 Product Overview4.1 Product Description

The DIOLINE PLC is a programmable compact controller in the automation system DIOLINE20. The product is based on a high-performance ARM = Microprocessor (Advanced Risk Machine). It is possible to connect several I/O modules over the L-Bus interface. The L-Bus is a Lütze invention. The product can provide up to 4 bus interfaces. The interfaces can be flexible configured. The DIOLINE PLC can be programmed and configured by the application development system MULTIPROG from KW software. The programming can be done in the established languages which are based on the IEC 61131 standard. The software can handle multiuser projects over a network access.There are several options regarding the interfaces and software.

4.2 Hardware Options

Option Item Number

DIOLINE PLC-COM-COM-LUE 746026

DIOLINE PLC-COM-CAN-LUE 746027

DIOLINE PLC-MVB-CAN-LUE 746028

DIOLINE PLC-COM-NFB-RS485-LUE 746029

DIOLINE PLC-COS-COM-LUE 746032

DIOLINE PLC-MVB-COM-LUE 746033

DIOLINE PLC-NFB-NFB-LUE 746034

DIOLINE PLC-MVB-CAN-RS485-LUE 746036

DIOLINE PLC-MVB-CAN-DI-LUE 746037

DIOLINE PLC-MVB-COM-DIO-LUE 746038

DIOLINE PLC-CAN-NFB-LUE 746039

DIOLINE PLC-MVB+-COM-LUE 746040

DIOLINE PLC-COS-CAN-LUE 746041

Legend:

CAN Controlled Area Network

MVB Multi Vehicle Bus (Slave) (EMD)

MVB+ Multi Vehicle Bus (Slave) (ESD+)

COM CANopen Master

COS CANopen Slave

DI Local Digital Inputs (24V)

DO Local Digital Outputs (24V)

11


4.3 Software Options

RS485 Two Wire Serial Bus

RSBUS One Wire Serial Bus

NFB No Field Bus

Option Description Item Number

DR-PC-SW-KWS KW MULTIPROG Development Suite+ V 4.8

▪ Multiprog development environment

▪ IEC61131 Editor

▪ SYCON.NET CANopen fieldbus configurator

▪ ProVisIT visualizing editor

▪ ProVisIT runtime license

746090

DR-PC2-SW-KWPD KW ProVisIT Development enviroment

746091

DR-PC2-SW-KWM KW MULTIPROG Monitoring Pro+ V 4.8

▪ MULTIPROG download and debugging environment

746092

DR-PC2-SW-KWOPC ProConOS OPC Server 2.1 Desktop 746093

DR-PC2-SW-KWPR ProVisIT Runtime 746095

DR-PC2-SW-KWP KW MULTIPROG Development Pro+ V 4.8

▪ Multiprog development environment

▪ IEC61131 Editor

746096

12


4.4 System OverviewThe DIOLINE PLC can be integrated in the product line of the DIOLINE 20 automating system as follows. The DIOLINE product line contains modular components. A unit consists of a controller with an integrated CPU and an extension module. It is possible to connect max. 10 local I/O extension modules on the controller. The extension modules are connected over the L-Bus. The graphic shows the DIOLINE product after their intelligence. The first module is the most intelligent one. The last one is a module with the fewest intelligence.

DIORAIL PC 2Vehicle Control Unit

DIOLINE PLCCompact Control Unit

DIOLINE20Buscoupler Ethernet IP Adapter Remote I/O Modules

DIOLINE20Buscoupler MVB SlaveRemote I/O Modules

DIOLINE20Buscoupler CANopen SlaveRemote I/O Modules

DIOSWITCHUnmanaged Ethernet Switch

13


4.5 Field of ApplicationThe DIOLINE PLC is designed for use in railway vehicles. It can be used for automation of simple vehicles, as subsystems or for high-capacity gateways to transfer vehicle specific bus signals. The graphic below shows possible application areas in trains:

Fig. 2: Example Application 1: Powerpack Control Unit

Fig. 3: Example Application 2: Fire Protection Control Unit

14

DIOLINE PLC ▪ Transport and Storing

15

5 Transport and Storing▪ Protect the product from humidity. Store the product in a dry room

between -40 and 85°C.

▪ Make sure that the PLC is safely packaged for transporting, that possible crushes can be absorbed.

▪ Dust can destroy electronic components. The circuit board of the PLC is coated. But try to store and transport it in a dust free environment to avoid damages of the PLC.

DIOLINE PLC ▪ Scope of Delivery

16

6 Scope of Delivery

▪ DIOLINE PLC

▪ Dummy connector for L-Bus interface

▪ Shielding Cover for SUB-D interface

▪ Instruction Leaflet

The software for the DIOLINE PLC can be downloaded in the internet. The Link and the password will be send by e-mail.

DIOLINE PLC ▪ Product Assembly

7 Product Assembly

1 LED-Diagnosis Display

2 User and Reset Button

3 L-Bus Interface X8

4 RS 232 Interface X7

5 Ethernet Interface X6

6 Fieldbus 2 – MVB Slave Interface outgoing X5

7 Fieldbus 2 – MVB Slave Interface incoming X4

8 Fieldbus 1 – CANopen Master outgoing X3

9 Fieldbus 1 – CANopen Master incoming X2

10 Mounting Tab X0

11 Power Supply

17


7.1 LED Display

LED Color State Description

PLC yellow 0.1s on/0.9s off0.5s on/0.5s off0.8s on/0.2s offonoff

PLC is ready – no projectPLC is in STOP modePLC alert an errorPLC is in RUN modePLC is defect

APP greenred

onon

User defined greenUser defined red

FB1ST– MVB green You can configure the LED with the functional block MVBInfo. Please see Seite 81.

FB1ERR– MVB red You can configure the LED with the functional block MVBInfo. Please see Seite 81.

FB2ST– CANopen green flashes one timeflashingon

Stop mode.Preoperational mode.Operational mode.

FB2ERR– CANopen red offflashes one time

flashes two times

on

At least one error counter of the CAN-Controller has reached the warning limit.

An error control event or a heartbeat event occured.

CAN-Controller is in the mode: bus off

L-Bus green

red

flashing

on

on

Initialization of L-Bus is OK, waiting on PLC.

L-Bus in RUN mode-configuration is OK

L-Bus error

UL green on

off

Power supply of the logic is OK.

Power supply is defect.

LNK green on

off

Ethernet connection is OK.

No Ethernet connection.

ACT yellow flashing

off

Ethernet data transfer is OK.

No Ethernet data transfer.

18


7.2 LED Display-Digital Inputs

LED Color State Meaning

I1-I4 yellow on Input is active

I1-I4 off Input is inactive

19

DIOLINE PLC ▪ Technical Data

8 Technical Data

Mechanics

Dimensions 123x141.5x64.1 mm (wxhxd)

Weight 0.550kg/piece

Housing Aluminum, anodized surface

Mounting Top Hat Rail TS 35 7.5 mm

Electrical Characteristics

Power Supply DC 24 V (voltage range 16.8-30 V)

Ripple Max. 10 %

Power Consumption 5 W + L-Bus Module Consumption

Protective Device Inverse-polarity protection, overvoltage protection

Potential Separation AC 500 V CAN and electronic AC 500 V Ethernet and electronic AC 500 V MVB and electronic

20


Interfaces

▪ RS232

▪ Ethernet 100Base TX

▪ SD Card Slot

Fieldbus Interfaces ▪ L-BUS

▪ CANopen

▪ MVB

Software

Operating System Real-Time Operating System rcX

Controller Software IECX 61131 Soft-PLC ProConOS KW Software

CPU

Processor ARM9-CPU NetX 500, 32 Bit

Monitoring External Watchdog voltage monitor of the control software

Boot time Run up time state: “ready“ after switching on the power supply <15s

Memory

Internal Serial Flash Memory

4 MB Serial Flash Memory

Internal RAM 32 MB SDRAM

Internal FRAM 4 kB

Internal parallel Flash Memory

2 MB

Diagnosis

Diagnosis Interface Ethernet 100BaseTX

Diagnosis LED 10 LED for visual device diagnosis

Switches/Key-Buttons 1 reset key button, 1 key button, evaluated in the control software

Clock Real Time Clock RTC

Enviromental Condition

Operating Temperature -40°C to +70°C

Storage Temperature -40°C to +85°C

Relative Humidity 100% short time condensation allowed

21


International Protection Class (IP)

IP20

Standards

EN 50155 Electronic Equipment on Railway Vehicles

EN 5021-3-2 Electromagnetic Compability

EN 50124-1 Insulation Coordination

EN 61373 Vibration and Shock

22

DIOLINE PLC ▪ Mounting

23

9 Mounting

9.1 Mounting OptionsThe DIOLINE PLC can be mounted on a top-hat rail. Following mounting options are possible:

Risk of injury by electric current. Persons can be injured by electric current and the product can be damaged. De-energize the system before mounting.

Mount the product with a distance of 5 mm minimum to other products to provide good air conditions.

1. Hook the product into the lower part of the top-hat rail.

2. Push the product a little bit up.

3. Push the product back that it catches the top-hat rail.

▪ horizontal

▪ vertical

▪ across

DIOLINE PLC ▪ Initial Operation – Hardware

24

10 Initial Operation – Hardware

10.1 Power Supply

The initial operation has to be done by expert employees.

Short circuits and electric shocks by wrong voltage application and wrong wiring. Switch off the power of the whole system before wiring. Make sure that the connectors are wired correctly before switching on the power. Use a direct voltage of 24 V according to the train standard EN 50155.

Do not operate the product without the protective conductor. If the product is defect, the housing can be energized and can cause electric shocks.

1. Switch off the power.

2. Connect the devices regarding the pin assignment.

3. Switch on the power.

4. The device is booting.

The PLC LED is flashing yellow.

Fig. 1: Cage Clamp with Mounting Tab X1, X0

If the LED is not flashing or is permanently on the product might be defect. For possible error solutions see chapter "Error Treatment" on page 133. If problems are still occuring please contact Lütze Transportation GmbH.

Pin Signal Description1 VCC 24 V

Supply Voltage

2 VCC 24 V Supply Voltage

3 PE Protective Earth

4 0V 0 V Supply Voltage

5 0V 0 V Supply Voltage

DIOLINE PLC ▪

10.2 L-Bus – InterfaceThe L-Bus interface is for connecting DIOLINE20 I/O modules. The L-Bus, also called Lütze Bus, is a special Bus invented by company Lütze.

Switch off the power when connecting or disconnecting the I/O modules. If not observe, the whole system can be damaged. Hot Plugging is not supported by the system.

Connect max 10 I/O modules over the L-Bus interface. Mind the current consumption of the single modules. In the appendix on Seite 143 you can find a table with the according values. A total current of max 1 A is possible on the L-Bus.

1. Switch off the power

2. Mind the pin assignment

Fig. 2: L-Bus Master, X8

Pin Signal Description

1 24 V Supply Voltage

2 24 V Supply Voltage

3 GND 0 V Potential

4 /L_BUS_

RESET

Module Reset

5 BUS_END Identifier Bus End

6 OUT_OK Data Confirmation

7 SDIN Receiving Serial Data

8 SCK Clock

9 SDOUT Transmitting Serial Data

10 GND 0 V Potential

It is not possible to change the pin assignment.

25

DIOLINE PLC ▪

3. Connect the DIOLINE 20 I/O Modules over the L-Bus interface.


5. The LB LED is green.The device is ready.

Fig. 3: L-Bus connector

Fig. 4: PLC with connected I/O Modules

26

DIOLINE PLC ▪

27

10.3 Serial InterfaceThe serial interface can be programmed by MULTIPROG and should only be used for diagnosis.

It is not possible to program or parameterize the PLC over the serial interface RS232. The serial Interface can be programmed out of MULTIPROG. The access to the serial interface is only possible by the user specific applicationsoftware. We recommend to use the interface only for diagnosis.

1. Connect the PLC and the devices with a suitable cable. “Hot Plugging“ is possible.

Fig. 5: Serial Interface SUB-D, X7


Connector Housing

PE Protective Earth

1 NC Not connected

2 RXD Receiving Data

3 TXD Transmitting Data

4 NC Not connected

5 GND 0 V Potential

6 NC Not connected

7 RTS Request to Send

8 CTS Clear to Send

9 NC Not connected

DIOLINE PLC ▪

28

10.4 Ethernet InterfaceThe Ethernet interface is for the communication between PLC and PC. Over this interface the PLC can be programmed, visualized, parameterized and debugged in the application software.

The Ethernet interface is hot plugging compatible. There is no need to switch of the power when connecting or disconnection the Ethernet interface.

1. Connect the PLC with the PC with a suitable cable over the Ethernet interface.

2. The Ethernet connection is active. The ACT LED is on.

Fig. 6: Ethernet Interface M12, X6


Connector Housing

PE Protective Earth

1 TXD+ Transmitting Data

2 RXD+ Receiving Data

3 TXD- Transmitting Data

4 TXD- Receiving Data

DIOLINE PLC ▪

10.5 Fieldbus 1 MVB Interface

The MVB is a special made field bus for trains to transmit commands. It is a part of the train communication network and can also be used with the wire train bus. In that case the date can be exchanged through the whole train. According to the IEC 61375 Electric railway equipment – Train bus the MVB works according to the EMD (Electrical Middle Distance) transmitting medium. The EMD medium allows a cable length of 200 m.

The PLC supports the MVB Slave mode only.


2. Connect the PLC with the devices over a suitable bus cable.


4. The FB1st LED is green.

Abb. 7: Fieldbus 1, SUB-D, 9-pole, X2X3

Pin Signal DescriptionConnector Housing

PE Protective Earth

1 A_Data_P Positive Signals of Wire A

2 A_Data_N Negative Signal of Wire A

3 NC Not connected

4 B_Data_P Positive Signals of Wire B

5 B_Data_N Negative Signal of Wire B

6 A_Term_P Positive Terminator of Wire A

7 A_Term_N Negative Terminator of Wire A

8 B_Term_P Positive Terminator of Wire B

9 B_Term_N Negative Terminator of Wire B

29

DIOLINE PLC ▪

The LEDs for the MVB can be configured by the function block “MVBInfo”. Please see Seite 81.

The EMD mode has to be set in the PROCONOS.INI. Please see Seite 75

30

DIOLINE PLC ▪

10.6 Fieldbus 2 Interface – CANopen


2. Connect the PLC with the devices over a suitable bus cable.


4. The FB2st LED is green, if all devices are communicating .

Fig. 8: Fieldbus 2 Interface, Sub-D, 9 pole, X4,X5

Pin Signal DescriptionConnector Housing

PE Protective Earth

1 PE Not connected

2 CANL CAN-Signal low

3 DGND CAN-Signal ground

4 NC Not connected

5 NC Not connected

6 NC Not connected

7 CANH CAN-Signal high

8 NC Not connected

9 NC Not connected

If the FB2ERR LED is red, an error occurred. Please see chapter “LED Diagnosis” on Seite 19.

31

DIOLINE PLC ▪ Initial Operation – Software

11 Initial Operation – Software1. Download the software under the sent link. The software has to be requested

at Lütze.

2. Install the Software in the following order:

1.MULTIPROG

2.ProConOS Server

3.Lütze Addons

Install all software package into one and the same directory. Otherwise the software package does not work right.

System Requirement

MULTIPROG Basic Pro 4.8

MULTIPROG Suite/Suite+ 4.8

Processor Pentium 500 MHz Pentium 1 GHz

RAM 64MB (128MB recommended)

Hard Drive 250 MB disk space 350 MB disk space

Communication TCP/IP

Operating System Win 95/98/ME/NT 4.0 (>SP5), Win 2000 (SP2), Win XP (SP1)

Win NT 4.0 (>SP5) Win 2000 (SP2) Win XP (SP1)

Internet Explorer 4.02 or newer version

32


11.1 Installation

11.1.1 MULTIPROG

Before installing the software mind the system requirements. The MULTIPROG software is an integrated development environment according to the IEC 61131 standard. With the software you program your application software and parameterize the PLC.

1. Open the setup file MULTIPROG 4.8 Development Suite.

The automatic installation assistant starts.

2. Follow the steps of the installation assistant. Click Next to confirm the settings. To cancel the installation, click Exit.

3. Click OK to complete the installation.

4. After a successful installation, restart the PC.

5. Start MULTIPROG.

6. Click the question mark in the menu bar.

7. Choose Register….

Following window appears:

8. Type in the license key.

9. Click OK to confirm the key.

If not having any license key, please contact us. It is mandatory to purchase a license key to use the full version of MULTIPROG.

33


11.1.2 ProConOS OPC ServerThe ProConOS OPC Server realizes the communication between PLC and OPC Client. The client is the visualizing program ProVisIT. The data exchange is done by TCP/IP.

If using the Multiprog Suite the ProVisIT visualization Software is installed automatically.

1. Double click ProConOs OPC-Server 2.1.

The automatic installation assistant starts.

2. Follow the steps of the installation assistant. Click Next to confirm your settings. To cancel the installation, click Exit.

3. Click OK to complete the installation.

4. After a successful installation, restart your PC.

5. Start the ProConOs OPC-Server 2.1.

6. Click right on the symbol in the windows task bar.

a) Choose Register.


b) Type in the license key.

3. Click OK to confirm the key.

If not having any license key, please contact us. It is mandatory to purchase a license key to use the full version of ProConOS Server.

34


11.1.3 Lütze AddonsThe addons contain functions for the programming system MULTIPROG. The addons implementing necessary resources for embedding the PLC in the integrated development environment.

1. Double click setup Luetze_Addons_V4.0 .

2. The automatic installation assistent starts.

3. Choose a language.

4. Follow the steps of the installation assistant. Click Next to confirm your settings. To cancel the installation, click Exit.

5. Click Install to confirm the installation.

35


11.2 IP Configuration

To configure the IP address and subnet mask follow those steps:

11.2.1 PC IP Address

Mind choosing the same subnet for all communication devices by configuring the subnet mask. Every communication node must have a different IP address. The standard IP address for the PLC is 192.168.0.215 and the standard subnet mask is 255.255.255.0.

The file TCPIP.CFG configures an individual PLC address. You can find more information about this file in chapter on Seite 40.

1. Open the windows start menu.

2. Choose Network Connections.


3. Open Network Connection by double clicking.

4. Make a right click on LAN- connection. Make sure configuring the networkcard the PLC is connected to.

5. Choose Properties.

36



6. Double click Internet protocol (TCP/IP).

Do not use the PLC IP address.

7. Choose Using following IP address.

8. Type in an IP address. For example: 192.168.0.10

9. Type in a subnet mask: 255.255.255.0

10.Click OK to confirm the settings.

37


11.2.2 Communication CheckTo program and monitor the PLC with MULTIPROG make sure, that the communication between PC and PLC is working. Proceed as follows:

1. Open Windows Start Menu > Run.


2. Type in: cmd.

3. Click OK.


4. Type in: ping 192.168.0.215 (standard address of the PLC) or the PLC IP address according to the changes.

5. Press enter.

▪ If you receive an answer:the communication is working.

▪ If you do not receive an answer:check the IP address and the networks.

38


11.2.3 PLC IP Address

To configure the IP address and subnet mask follow those steps:

Mind choosing the same subnet for all communication devices by configuring the subnet mask. Every communication node must have a different IP address. The standard IP address for the PLC is 192.168.0.215 and the standard subnet mask is 255.255.255.0.

Before changing the IP Address the communication with the standard IP address has to work.

Do not use the PC TCP/IP address. Just choose the same subnet. Otherwise there will be no communication between PLC and PC. An example file can be found in the download area, the link will be sent within an e-mail request.

1. Open the TCPIP.CFG file.

The TCPIP.CFG is a default Lütze standard file. It contains the following IP configuration parameters as shown in the picture.

2. Change the existing IP address by the new one.

3. If needed set a new subnet mask.

4. Save the settings.

The DefaultGateway has to be in the network of the IP address.

To Download the configuration file see chapter see chapter "Download of Configuration Files" on page 105.

To Reset the TCP/IP to the standard value 192.168.0.215 by the PLC buttons see chapter "Resetting the TCP/IP Address" on page 40.

39


11.2.4 Resetting the TCP/IP Address

The resetting of the TCP/IP is just possible during the start of the PLC.

The resetting of the TCP/IP is not possible if an SD card with the autoexec.bat is inserted.

1. Switch on the PLC.

2. Press and hold the J1USER button.

3. Still holding the J1USER button, Press shortly the J2RESET button,

4. After pressing the J2RESET button keep holding the J1USER button for 10 more seconds, until the PLC and APP LED flashes 20 times with 10 Hz alternately.

5. Check the communication between PC and PLC using the standard ip 192.168.0.215, see chapter "Communication Check" on page 38.

40


11.3 Development Environment System – MULTIPROG

11.3.1 Creating a MULTIPROG ProjectTo program the PLC, it is necessary to create a project with the MULTIPROG software. To create a project use the project assistant.1. Start the MULTIPROG software.

2. Click on in the tool bar or choose File > New Project in the menu bar.


3. Double click following symbol:

Step 1- Project Assistant

1. Type in any project name. Following characters are forbidden: ':-=;<>[]/?|*".The name can have a length of 24 characters. But only 12 characters can be read in the info dialog out of the PLC.

In the field Project Path a standard path is entered. The Project Path should be no longer than 171 characters.

If you want to change the path, follow those steps:

a) Click

The window FOLDER appears:

b) Choose any path.

c) Click OK.

2. Click NEXT.

41


Step 2 Project Assistant

1. Type in any name for the first program organization Unit (POU) in the field Name of POU.

2. Choose a language for the POU.

3. Click NEXT.


1. Choose any configuration name.

2. Choose the configuration type ARM_L_33.

3. Click NEXT.


1. Type in any resource name.

2. Choose PCOS_ARM_IKS as resource type.

3. Click NEXT.


1. Type in any task name.

2. Choose the task type CYCLIC

3. Click NEXT.


The settings are listed in the overview.

Click Finish to confirm the settings.

42


11.3.2 Ressource SettingsIn the resource settings you configure MULTIPROG specific parameters for the communication between the PLC and PC.

1. Start MULTIPROG.

2. Click with the right mouse button on Ressource:PROCONOS in the Project tree window.

3. Choose Settings.


4. Choose DLL under Port.

5. Choose:

▪ Array boundary check on PLCChecks the access to not defined array elements.

▪ Force Bool 8 for Boolean variablesSaves any boolean variables as a byte without a defined storage location.

▪ TCP/IP for DLLThe name for the dynamic library DLL.

43


Other options are:

▪ Stack check on PLCIf activated the stack will be checked for overflows. A possibility of a decreased operation speed can occur. A higher security is provided.

▪ Generate bootproject during compileThe MULTIPROG generated Bootfile.pro is a inbetween code which is translated to a machine code on the PLC after the donload procedure.

6. Under “parameter” type in the standard IP as follows:

▪ ip 192.168.0.215 -TO2000

▪ -TO2000 defines the timeout between the PLC and the Multiprog sofware in ms. If the PLC does not response in this time on a request of the PC an Timout Message will be generated in the Message-Window of Multiprog.

7. Choose Marked Variables under PDD and OPC.

▪ PDD (Process Data Directory)The operating system can directly access those variables. For example the variables are needed for serial interface or symbolic variables access.

▪ OPC (OLE for Process Control, Object Linking for Embedding) Needed for the visualization of variables in ProVisIT.

8. Choose All POUs under Use reserve.Allows to change and upload the MULTIPROG project during the runtime. While changing a storage reserve is used.

9. To confirm the settings click OK.

This file cannot be loaded on the PLC. Because after the download through MULTIPROG the machine code is translated on the PLC a second time. To download this file from the PLC see chapter "Maintenance Software" on page 123.

44


11.3.3 Function Blocks and Firmware LibrariesFunction blocks can be inserted from the firmware or user libraries in MULTIPROG. There is also the option to program your own function blocks.

The fieldbusses and other interfaces are controlled and monitored in MULTIPROG by function blocks from the firmware libraries which are coming with the software package. The table below shows the related firmware libraries of the fieldbusses and other interfaces.

To load the firmware libraries and use the function blocks follows those steps:

For further information to program your own function blocks, read the KW Software MULTIPROG manual.

Interface Firmware Library

CANopen CIFNetx

SD Card PROCONOS

L-Bus (analog and digital monitor) IKS

CAN2.0 IKSCAN20

COM IKSCOM

MVB MVB-IKS

Serial Interface PCOSCom

The function blocks of the firmware libraries may not be triggerd several times before the operation process of the block is completed. The state of those function blocks are written by the outputs Done and Error. Non compliance can cause errors.

1. Open MULTIPROG.

2. Make a right click on Libraries.

3. Choose Insertion >Firmware Library.

4. Choose any firmware library.

5. Click Include.

6. The library appears under the folder library in the project tree menu.

45


7. In the project tree menu double click on the POU in which the function block should be insert.

8. Click on the work sheet. A cross will appear.

9. In the toolbar click .

On the right side the menu Edit Wizard appears.

10.Choose under Groups the firmware library.The names of the function blocks will appear in a list.

11.Double click on the function block which should be insert.

12.Define the function block.

13.Click OK to confirm your settings.

46


Adding the POU to the Task

1. Click right in the project tree window on any task.

2. Choose Insert.

3. Click Program Instance.

The window Insert appears.

4. Define a name for the program instance.

5. Choose the program type (POU).

User defined functions and function blocks cannot be selected.

6. Confirm your settings by clicking OK.

47


11.3.3.1 Hardware Watchdog – IKSMonitor DigitalThe function block controls the hardware watch dog. At every execution a signal is sent to the hardware watch dog. This signalizes the correct operation of the PLC. The outputs are displaying the different supply voltages of the system. Additional the controlling of the APP LED (Input L0 and L1) and a hardware reset of the PLC can be done by this function block.

If the PLC is in the RUN mode the IKSMonitorDigital function block has to be triggered every 2 seconds. Otherwise there will be a hardware reset. The POU which includes this function block has to be inserted in the task with a lower cycle time than 2 seconds.

If the function block is not included in the bootproject , a reset is done every two seconds, after the boot process (Endless Loop). To avoid the start up of this bootproject see chapter "Maintenance Software" on page 123.

Input Description Type

L0 Input L0 controls the green state of the APP LED.

BOOL

L1 Input L0 controls the red state of the APP LED.

BOOL

L2 Input L2 – NOT USED BOOL

Reset In case of an increasing slope the system is reseted after 2 seconds.

BOOL

Output Description Type

Supply_5 Displays the value “TRUE” if the power supply is in the thresholds of 4.75 V..5.25 V.

BOOL

Supply_3_3 Displays the value “TRUE” if the power supply is in the thresholds of 3.15 V..3.45 V.

BOOL

Supply_1_5 Displays the value “TRUE” if the power supply is in the thresholds of 1.4 V.. 1.6 V.

BOOL

ResetRequest Displays if there is a request for a restart. BOOL

48


11.3.3.2 IKSMonitor AnalogShows all measured voltage values by the controller and the version of the PLC firmware and the MAC address of the ethernet interface.


Supply_5 Displays the analog power supply of 5 V. REAL

Supply_3_3 Displays the analog power supply of 3.3 V. REAL

Supply_1_5 Displays the analog power supply of 1.5 V. REAL

Version Displays the PLC firmware version. STRING

MacAdr Displays the MAC address of the TCP/IP stack.

STRING

49


11.3.4 ProConOS.INIThe ProConOS.INI is an initialization file which contains application specific settings for following parameters:

▪ CANopen Slave

▪ CAN2.0

▪ Serial Interface 1 and 2

▪ Parallel Flashdisk

▪ MVB

▪ Retain Data Storing

The specific settings for the ProConOS.INI can be found in the different configuration chapters.The file can be created with any text editor or an example file can be downloaded in the download section.

The entries of the file are case sensitive.

If the file was deleted on the PLC, default values will be set.

To Load the file on the PLC, see chapter "Download of Configuration Files" on page 105.

50


11.3.5 VariablesThe valid area of the variables is local or global. The variables are declared by the location, type and the name. Following types are supported by MULTIPROG:

Type Description Bit length

Range

TIME Time length 32 +#4.294.976.295 ms till +#4.294.976.295 s

STRING string with max. 80 characters

BOOL Boolean 1 0 or 1

BYTE Bit string 8 0x00 till 0xFFh

REAL Floating point number

32 +/-1.18x10^-38 till +/-3.40x10^38

LREAL Long floating point number

64 +/-1.798x10^+308till +7-2.225x10^-308

WORD Bit string 16 0x0000h till 0xFFFFh

DWORD Bit string 32 0x00000000h till 0xFFFFFFFFh

INT Integer with algebraic sign

16 -32768 till +32767

UINT Integer without algebraic sign

16 0 till 65535

SINT 8 bit integer with algebraic sign

8 -128 till 127

USINT 8 bit integer without algebraic sign

8 0 till 255

DINT Double integer with algebraic sign

32 -2.147.483.648 till 2.147.483.647

UDINT Double integer without algebraic sign

32 0 till 4.294.967.295

51


11.3.5.1 Globale VariablesThe global variables can be used in the whole project. The variable has to be declared as VAR_GLOBAL in the global variable datasheet. In the single POUs, where the variable is used, it has to be declared as VAR_EXTERNAL. To allocate global variables proceed as follows:

1. Double click Global Variable of the used ressource.

The variable sheet appears:

2. Make a right click in the cell “Default” (The name can be changed).

3. Choose Insert variable.

A new row appears.

4. Make a right click in any cell.

5. Choose Properties....

52


Type in one of the expressions followed by an address like in the following example:

▪ %IB 1Adresses the first bit of the first byte.%IX 1.1The first number adresses the first byte. The second number addresses the first bit of the first byte.

6. Set the properties:

▪ NameType in a unique name for the variable.

▪ TypeChoose a type for the variables. The different types are listed in the chapter “Variables“.

▪ UsageThe usage will be automatically set to VAR_GLOBAL.

▪ Initial ValueAn initial value can be defined for the variable which will be set at PLC starup.

▪ AddressWith the address it is possible to link a memory address, which can be used by a driver. With this operation variables can be mapped for the fieldbus communication.For the fieldbus address configuration see chapter "Configuration of the Fieldbusses and other Interfaces" on page 57.

▪ DescriptionYou can type in any notes you want.

To define the mapping between the variable and the driver it is necessary to choose one of the expressions:

%IX Input Bit

%IB Input Byte

%IW Input Word

%QX Output Bit

%QB Output Byte

%QW Output Word

%MX Memory Bit

%MB Memory Byte

%MW Memory Word

53


▪ %IW 1The first number adresses the first and second byte at the same time.

▪ InitType in a start value for the variable. Depending on the data type.

▪ RetainThe marked variables are defined with the memory cycle time in the PROCONOS.INI or by triggering the WriteRetain function block. More Information can be found in the chapter see chapter "Retain Variables" on page 56“.

▪ PDD – Process Data DirectoryThe operating system can directly access those variables. For example the variables are needed for serial interface or symbolic variables access.

▪ OPC – OLE for Process Control, Object Linking for EmbeddingNeeded for the visualization of variables in ProVisIT. Check the box if you want to visualize this variable in ProVisIT.

Function block instances are used like local variables.

54


11.3.5.2 Local VariablesLocal Variables can just be declared in the POUs datasheets. To allocate local variables proceed as follows:

1. Double click Global Variable of the selected POU in the project tree.

2. The variable sheet appears:Make the same settings as described in chapter “Global Variables”.

3. Different settings have to be made under Usage.

▪ UsageChoose between:

▪VAR – for a local variable

▪VAR_EXTERNAL – for a link to a global variable. The parameters name and type have to be the same as set in the global variable.

If defining variables in function blocks, additional options under Usage can be set. For more information read the MULTIPROG KW Software manual.

Do not use the option VAR_IN_OUT for variables in function blocks. It can cause data inconsistency.

55


11.3.5.3 Retain VariablesAll variables which are marked with RETAIN can be stored in the FRAM.The storing cycle time can be configured in the ProConOS.INI.

The function block WRITE_RETAIN can also be used to trigger the storing cycle time through a MULTIPROG project. If using the function block set the interval in the ProConOS.INI to 0.

Function Block Insert the firmware library PROCONOS and insert the function block WRITE_RETAIN if the saving time of the variables should be controlled by the function block.

ProConOS.INI

[Retain]Intervall=2000

Cyclic storage interval in ms. (0=disabled)


IN At a increasing slope all checked retain variables will be written on the FRAM

BOOL


DONE If the value TRUE is set, the data was written on the FRAM.

BOOL

If using the FRAM variable at the same time as the function block set date time, a delay of the tasks can occure.

56


11.4 Configuration of the Fieldbusses and other Interfaces

11.4.1 L-Bus ConfigurationTo control the DIOLINE20 modules, which are connect via the L-Bus, it is necessary to configure the driver of the L-Bus.

The L-Bus driver is byte organized. Every L-Bus module has a predefined amount of input and output bytes. The total configuration of the bus is the sum of all module bytes. The bytes are counted from left to right. It starts with the first module connected to the PLC to the last module in the L-Bus chain.

The second driver needs the parameter offset. The offset is the amount of bytes, which are used before the first analog module byte. If problems occurring during the L-Bus configuration contact us.In the I/O configuration set up the drivers with input and output bytes. Out of that configuration a start address is defined. Input- and output addresses can be equal, like in the following example. From the start address the first byte of the L-Bus module chain is reachable.

11.4.1.1 L-Bus I/O ConfigurationThe following steps are describing the configuration of a 8 DI/8 DO module.

If working with analog modules the modules can be adressed by words. The modules have to be physically on an even byte address, otherwise a new start address has to be defined for the analog modules in a second driver configuration.

If using the SD-Card and the L-Bus interface at the same time there might be some delays in the data transfer of the L-Bus. The L-Bus and SD card sharing the SPI interface.

1. Double click I/O_Configuration in the project-tree window.

The window I/O_Configuration appears.

Configuration INPUT

1. Click on the register INPUT,

2. Click Add to add an input driver.

57


The window Adding I/O group appears:

3. Type in the name of the interface.

4. Choose the task of the L-Bus driver in which it should be processed

5. Type in an unused start address.

6. Type in the length of input bytes which are used by the L-Bus. The length in this case is 1.

7. Choose under Board/I/O-Modul the item IKS LBUS.

8. Click on Driver parameters.

The window driver information appears.

9. Set the offset to 0, if using one driver.

10.Confirm the settings by clicking OK.

11.Confirm the settings in the window Add I/O Groups by clicking OK.

The driver should not run in the Default task. It can cause data inconsistency.

Do not press enter. The configuration will not be set.

58


12.Confirm the settings in the window Add I/O Groups by clicking OK.

Configuration OUTPUT

1. Click on the register OUTPUT,

2. Click Add to add an Output.

The window Adding I/O group appears:

3. Type in the name of the interface.

4. Choose the task of the L-Bus driver in which it should be processed.

5. Type in an unused start address.

6. Type in the length of output bytes which are used by the L-Bus. The length in this case is 1.

7. Choose under Board/I/O-Modul the item IKS LBUS.

8. Click Driver Parameters.

9. The window Driver Information appears.

10.Set the offset to 0, if using one driver.

11.Confirm the settings by clicking OK.

Do not press enter. The configuration will not be set.

To allocate the variables for the L-Bus bytes read chapter see chapter "Globale Variables" on page 52.

The driver should not run in the Default task. It can cause data inconsistency.

59


11.4.1.2 L-Bus Function BlocksThe embedding of following function blocks from the IKSL-Bus library is necessary.

L-BusInfoThe function block displays the state of the L-Bus interface and is used for the parameterization.The function block has to be implemented in a POU which is executed in the task of the L-Bus I/O driver.

In the case of data inconsistency the L-Bus data will still be transmitted to the used task. To avoid wrong data values in the program the function block L-Bus Info must be executed and checked for errors before using the L-Bus data.


Restart An increasing slope restarts the initialization process of the L-Bus chain.

BOOL

ClearMax At an increasing slope the Output MaxCycleTime is resetted.

BOOL

ContinueOnTime If the input is TRUE the L-Bus will still run at a time error.

BOOL

ContinueOnOccurence If the input is TRUE the L-Bus will still run at a occurrence error.

BOOL

MinMeasureTime Defines the minimal time of the cycle. The L-Bus is not served faster than the pending time. The function can be disabled by the value 0. The default value is 20 ms.

TIME

Use the MinMeasureTime value to process the L-Bus as often as needed and as unusual as possible. By using this value the total system load of the PLC can be kept low.

FailureAcceptanceTime Defines the maximal cycle time. The standard value is 500 ms.

TIME

MaxErrorOccurence Defines the amount of error cycles without a correct one in between. The input is set 5, because the L-Bus is just allowed to lose 5 frames in a row till an error is displayed or the L-Bus is stopped.

INT


LastCycleTime Displays the time of the last L-Bus cycle.

TIME

MaxCycleTime Displays the max. cycle time. TIME

60


L-Bus DeviceThe L-Bus device function block displays the state of the connected DIOLINE20 modules. You need to insert one function block for every device.

AverageCycleTime Displays the average time of the 10 last cycles.

TIME

SlaveCount Displays the number of the connected DIOLINE20 modules.

INT

Run Signalizes that the L-Bus is initialized correct. The L-Bus is running.

BOOL

Stop Signalizes that the L-Bus is stopped. No communication of the L-Bus.

BOOL

Init The Output is active during the initialization process of the L-Bus.

BOOL

Error Displays an error number. For the error numbers see chapter "L-Bus Configuration" on page 57.

INT

CycleErrorCount Displays the number of incorrect cycles. Every report fault increases the value multiplied by 1000. Every correct report decreases the value by 1.

UINT

WD_LBus Watch Dog of the L-Bus, signalizes if the time of the L-Bus is exceeded.

BOOL

WD_PLC Watch dog of the PLC, signalizes if the time of the PLC is exceeded.

BOOL

ComError Displays TRUE if the last L-Bus cycle has a protocol error.

BOOL

TimeError Displays TRUE if the FailureAcceptanceTime is exceeded.

BOOL

OccurenceError Displays TRUE if the value of MaxErrorOccurence is exceeded.

BOOL

Version Displays the version of the L-Bus software.

REAL

After a frame break of 130 ms the L-Bus modules will go in the status failsafe. This is a L-Bus module characteristic and can not be influenced by the PLC.

The stop mode does not reset the L-Bus moduls. After the failsafe time the outputs of the modules will be adjusted to zero.


SlaveNo Defines the number of the connected I/O modules. The first connected module to the PLC is counted 0. The number is increasing with every module.

INT

61



Type Displays the type ID. For a ID list see chapter "DIOLINE 20 Module Types" on page 143.

INT

Error Displays an error number. For the description of error number, see chapter "Error Treatment" on page 133.

INT

InputLen Displays the length of the input bytes of the module.

INT

OutputLen Displays the length of the output bytes of the module.

INT

62

DIOLINE PLC ▪

11.4.2 SD Card Configuration

With the SD card it is possible to read and write data during the runtime. The data format is FAT. The written files will be stored in the ASCII format.

11.4.2.1 SD Card Function BlocksFileOpenThe function block opens an existing file or creates a new one.

FileReadThe function block reads data from a file.

Make sure that you are using a special industrial card which is specified by Lütze.

If using the L-Bus interface and the SD-Card at the same time there might be some delays in the data transfer of the L-Bus. The L-Bus and SD card sharing the SPI interface.


Execute Opens an existing file or creates a new one if a increasing slope is pending

BOOL

Name Defines the name of the file.Filename: 8 characters for the name and 3 for the extension

STRING


Done Is TRUE if the file are opened or created successfully.

BOOL

Handle Displays a handle value (≠ 0) for the chosen file. UINT

Error Is TRUE if an error occurred, otherwise the output is FALSE.

BOOL

ErrorID Displays an error number. For an explanation of the error numbers see chapter "FILE_OPEN" on page 135.

UINT


Execute At an increasing slope the data of the specified file will be read.

BOOL

Handle The output handle from the function block. UINT

Buffer The received data are stored in the buffer. ANY

MaxLength Defines the number of the characters which have to be read.

UDINT

63

DIOLINE PLC ▪

FileWriteThis function block writes data in a file.

FileCloseThe function block closes an opened file.


Done Is TRUE if the data could be read correctly, otherwise the output will be FALSE.

BOOL

LengthRead Displays the number of the characters which were read.

UDINT

Buffer The received data are stored in the buffer. ANY

Error Is TRUE if an error occurred, otherwise the output is FALSE.

BOOL

ErrorID Displays an error number. For an explanation of the error numbers see chapter "FILE_READ" on page 135.

INT


Execute At an increasing slope the data of the specified file will be written.

BOOL

Handle The output handle from the function block. FileOpen has to be used.

UINT

Buffer The written data are stored in the buffer. ANY

Length Defines the number of characters which has to be written.

UDINT


Done Is TRUE if the data could be written correctly, otherwise the output will be FALSE.

BOOL

LengthWritten Displays the number of written characters. UDINT

Buffer The written data are stored in the buffer. ANY

Error Is TRUE if an error occurred, otherwise the output will be FALSE.

BOOL

ErrorID Displays an error number. For an explanation of the error numbers see chapter "FILE_WRITE" on page 136.

UINT


Execute At an increasing slope the specified open file will be closed.

BOOL

Handle The output handle from the function block FileOpen has to be used.

UINT

64

DIOLINE PLC ▪


Done Is TRUE if the file could be closed correctly, otherwise the output will be FALSE.

BOOL

Error Is TRUE if an error occurred, otherwise the output will be FALSE.

BOOL

ErrorID Displays an error number. For an explanation of the error numbers see chapter "FILE_CLOSE" on page 136.

UINT

65

DIOLINE PLC ▪

11.4.3 PFD – Parallel Flash DiskThe Parallel Flash Disk saves diagnostic data, which are defined by the user. The memory is permanent. It can save a defined amount of data.

ProConOs.INI

The PFD is organized in two superior data sections.

The section size can be configured by the user, the sum of the two sections cannot be bigger than 2 MB (2048KB). At the configuration, notice that the size of one section must be divisible by 128 the sum must be an integer. The minimum size of one section must be 256 kB. The sections are divided into slots. The slots are the actual entries of the PFD. The slot size can also be user defined. The size has to be organized in bytes. The amount of bytes has to be divisible by 2, the sum must be an integer. Additional to every slot a header of 16 Bytes will be automatically added.

The header contains the following data:

Byte Description

0 – 1 CRC Checksum

2 – 3 Res1

4 – 7 Internal Timestamp

8 – 9 Defect1

10 – 11 Defect2

12 – 15 ID Counter

Use the following formula to calculate the usable amount of slots (entries):

[ParFlashSect@1]Mode=RingSlotSize=1024SctSize=256

[ParFlashSect@2]Mode=RingSlotSize=2024SctSize=512

Section1Saving mode Ring or OnceSlot Size in ByteSection Size in kByte

Section 2Saving mode Ring or OnceSlot Size in ByteSection Size in kByte

66

DIOLINE PLC ▪

11.4.3.1 Saving ModesRing ModeThe flash memory is physically organized by pages. Every page has a size of 128 kB. If deleting data the flash will always delete the minimal amount of one page (128 kB). If the memory is full and additional data want to be saved, in that mode the oldest data will be deleted and the new data will be written. The slots which are stored in this page will be lost.

Example:

▪ Section Size 1024 kB

▪ Slot Size 128 Byte

7281 Slots=(1024 kB)/(128 Byte+16 Byte)

One page contains:

Slots in one Page 910=(Page Size 128 kB)/(Slot Size 128 Byte+ Header 16 Byte )

Slots which are saved in every case: 7281 Slots - 910 Slots = 6371 SlotsIn the worst case 12.5% of the section is empty.

Once ModeThe slot size and the section size has to be defined. In the memory data can be written till the section is full. The section will signalized the end of memory. The calculation of the slot number can also be done as for the Ring Mode. In the once mode pages are not automatically deleted. If the section is full, the application will signalize. The section can be deleted completely or described from the beginning.

11.4.3.2 PFD Functional BlocksThe embedding of following function blocks from the PFD library is necessary.

PFDStatusThe function block displays the state of the two sections.With this block it is also possible to delete data manually out of the application.


ActErase1 At an increasing slope the memory of section 1 will be deleted.

BOOL

ActErase2 At an increasing slope the memory of section 2 will be deleted.

BOOL


Status1 Displays the current state of section 1. INT

EraseDone1 Displays that the section 1 is deleted. BOOL

67

DIOLINE PLC ▪

PFDWriteDiagEntryThe function block writes a slot (entry) in the diagnosis memory.

NrEntriesMax1 Displays the maximum quantity of slots in section 1.

DINT

NrEntriesUsed1 Displays the number of used slots in section 1. DINT

NrEntriesDefect1 Displays the number of defect slots in section 1.

DINT

Status2 Displays the current state of section 2. INT

EraseDone2 If this output is TRUE section 2 will be deleted. See EraseDone1.

BOOL

NrEntriesMax2 Displays the maximum quantity of slots in section 2.

DINT

NrEntriesUsed2 Displays the number of used slots in section 2. DINT

NrEntriesDefect2 Displays the number of defect slots in section2.

DINT

The input data can just be as big as the slot size. It is possible that the input data are smaller than the slot size. At a bigger size of data as the size of the slot an error will occur.


Data Any data type can be chosen. Structures and arrays are also transferred. The writing data will be transferred at the input/output.

ANY

Act Activates the writing of data at an increasing slope.

BOOL

Section The diagnosis section (1 or 2) have to be defined

INT


Data Any data type can be chosen. Structures and arrays are also transferred. The writing data will be transferred at the input/output.

ANY

Done At the end of the writing process the input will be TRUE. Even if an error occurs.

BOOL

SlotID Displays the ID for every written Slot. DINT

Error Displays an error number. For an explanation of the error numbers see chapter "Error Messages of the Function blocks" on page 133.

INT

68

DIOLINE PLC ▪

PFDReadByIDWith the function block it is possible to read the slots by the slot ID. The slot ID is assigned for every written slot. An ID is assigned unique and once.

If a section is been deleted the counting of the ID starts all over again.If a page is deleted in the ring mode, the slot ID will be incremented by every new entry.Defective entries are transparent for the user and are not relevant when reading the data. This information shows how many incorrect entries are still saved in the memory.

PFDReadDiagEntryWith this function block it is possible to read a couple of slots at one time without using the slot ID.


Data Any data type can be chosen. Structures and arrays are also transferred. The data to be read will be transferred at the input/output.

ANY

Act Activates the reading of data at a increasing slope. BOOL

Section The diagnosis section (1 or 2) can be displayed. INT

SlotID Transfer of the slot ID which should be read. INT


Data Any data type can be chosen. Structures and arrays are also be transferred. The data to be read will be transferred at the input/output.

ANY

Done At the end of the writing process the input will be TRUE. Even if an error occurs.

BOOL


DINT


Data Any data type can be chosen. Structures and arrays are also transferred. The data to be read will be transferred at the input/output. Depending on the input “Length” the size of the data variable must be defined.

ANY

Act Activates the reading of the data at a increasing slope. BOOL

Section The diagnosis section (1 or 2) has to be entered. INT

69

DIOLINE PLC ▪

PFDCopy2SDWith this function block you can copy a complete section to the SD card. Only the taken slots will be copied. You can choose between an ASCII or binary format. It is also possible to name the files.

Start If a 0 is pending the reading will start with the oldest entry. If a 1 is pending the reading will start with the second oldest entry. If a -1 is pending the reading will start with the newest entry. If a -2 is pending the reading will start with the second newest entry. With the negative values counted from -1 you can go from the newest entry to the oldest. With the positive values counted from 0 you can go from the oldest entry to the newest.

DINT

Length Defines how many slots (entries) should be read. DINT

Entries with an error are not counted and can be ignored.


Data Any data type can be chosen. Structures and arrays are also transferred. The data to be read will be transferred at the input/output. Depending on the input Length the size of the data variable must be defined.

ANY

Done At the end of the reading process the input will be TRUE. Even if an error occurs.

BOOL


INT

The copying of a big data volume can take some time. The copying progress is not displayed.


Act An increasing slope activates the coyping process. BOOL

Section Defines the section (1 or 2) which has to be copied. INT

FileName Defines the name for the created file on the SD card. 8 name characters and 3 characters file extension.

STRING

Mode Defines the memory mode. 1 for CSV and 2 for binary.

INT

70

DIOLINE PLC ▪


Done At the end of the copying process the input will be TRUE. Even if an error occurs.

BOOL

Error Displays an error number. For an explanation of the error numbers see chapter "Error Messages of the Function blocks" on page 133

INT

71

DIOLINE PLC ▪

11.4.4 Real Time Clock ConfigurationThe real time clock works with a battery. If the power of the system is switched off, the clock is still running.

The embedding of following function blocks from the Clock library is necessary.

11.4.4.1 Real Time Clock Function Blocks Sec_1970The function block displays the seconds since 1970.

SecToTime

The function block converts the UNIX time in a standard time and date format.

The real time clock uses the I2C bus when progressing and while setting. During that time the I2C bus is busy. The smallest supported time unit is a second. There is no point in using a faster processing time. The processing of the RTC should done with a task time less than 1 second.

If you are using the Real Time Clock and the FRAM at the same time it can cause timing constraints. Read “Using RTC (Real Time Clock) and FRAM”.


Second Displays the seconds since 1970 in a UNIX format. UDINT


TimeUnix The seconds since the year 1970 are pending. UDINT


Year Displays the calculated years. INT

Month Displays the calculated months. INT

Day Displays the calculated days. INT

Hour Displays the calculated hours. INT

Minute Displays the calculated minutes. INT

Second Displays the calculated seconds. INT

72

DIOLINE PLC ▪

SetDateTimeThe function block sets the time with the values of the system. Following ranges are valid:

TimeToSecThe function block converts the standard time and the date into the UNIX format. You can specify the values. The values are converted into seconds since 1970.


Year Defines the year, greater than 2000. INT

Month Defines the month between 1 and 12. INT

Day Defines the day between 1 and 31. INT

Hour Defines the hours between 0 and 23. INT

Minute Defines the minutes between 0 and 59. INT

Second Defines the seconds between 0 and 59. INT

Set At an increasing slope the time for the RTC(Real Time Clock) will be set.

BOOL



INT


Year Defines the year, greater than 2000. INT

Month Defines the month between 1 and 12. INT

Day Defines the day between 1 and 31. INT

Hour Defines the hours between 0 and 23. INT

Minute Defines the minutes between 0 and 59. INT

Second Defines the seconds between 0 and 59. INT


TimeUnix Displays the seconds since 1970. INT


INT

73

DIOLINE PLC ▪

11.4.4.2 Using RTC (Real Time Clock) and FRAM

In this case the function block SetDateTime of the RTC will block the progress until the I2C bus is free. This results in an increased task time.

In the following example you can find a possible solution to avoid the timing constraints when using the RTC and FRAM at the same time.

ProConOS.INIThe Retain Interval of the FRAM has to be set to 0. The triggering of the time is done by the function block WRITE_RETAIN out of application software.

Programming ProposalThe Write Retain is triggered and the data will be saved. At the same time a RETAIN_JUMP is set. This avoids the processing of the Sec1970 and SetDateTime function blocks. If the write retain task is done, the retain jump will be reset. The task of the Sec1970 and SetDateTime function blocks will be processed.

If you are using the Real Time Clock and the FRAM at the same time it can cause timing constraints. The RTC and FRAM are using the same I2C interface.

74

DIOLINE PLC ▪

11.4.5 MVB Slave ConfigurationA configuration file named MVBCFG.bin has to be created with the Lütze Slave Configurator. The program can be found under downloads on our website. An example configuration file (MVBCFG.bin) can also be found there. The file can be created or opened in the MVB Configurator to make adjustments.

ProConOS.INI

11.4.5.1 MVB ConfiguratorThe following steps describe the configuration of the MVB slave with the MVB Configurator.

The name of the configuration file must always be named MVBCFG.bin.

[MVB]MVB4DIConfig=0

MVBM=0ESDmode=0Devicenumber=1

BusSwitch=0

0 – Device selection will be done through the PROCONOS.INI [If you are using a MVBCFG.BIN with more than one device configuration])

1 – Device selection will be done through the local digital PLC inputs [If you are using a MVBCFG.BIN with more than one device configuration])

MVB is off, MVB =1 – MVBM is onEMD, ESDmode=1 – ESDDevice Selection for a Multiple Configuration file if MVB4DIConfig option is 0. Switches wire A with wire B (Not implemented yet)

1. Start the MVB Configurator.


75

DIOLINE PLC ▪

Basic settings for the MVB slave can be done under Administrativ Data and MVB-Slave Data. If some configuration are already done the checksum and the length will appear in the columns.

With the sink time supervision the pending time of the values for the PLC sink ports can be defined. Set the sink time supervision on a multiple integer value of 32 ms. The shortest sink time supervision which can be defined is 32 ms. If you are not choosing a value after those specifications, the value will be ignored and set automatically on a value which can be divided by 32.

2. Click File in the menu bar.

3. Choose New MVBCFG-File.

4. Choose Lütze PLC as target.

5. Click Add.

6. In the menu tree on the left the folder 1.Device appears.

7. Click on the folder 1.Device.

8. Type in the version number.

9. Type in the date.

10.Type in the device address.

11.Type in the time of the base cycle for the sink time of the supervision in the column base-cycle.

12.Click Copy, to set up a second device.

In the settings of the 2. device change the device address.

76

DIOLINE PLC ▪

In the column number a sequential number is defined. If a new port is defined the number will be incremented. The number cannot be changed.

In the column Number a sequential number is defined. If a new signal is compiled the number increments. The number cannot be changed.

To delete a device click on Device which you want to delete and click DELETE.

13.Click on + in front of the folder 1.Device to see the subfolders.

Source Port Configuration

1. Click on the folder Source Ports.


2. Type in the address of the port. The address should be between 0 and 4095.

3. Define the length of the ports. Allowed values are : 1,2,4,8,16,32 bytes. Choose the value regarding the number of reference data, which are supposed to be in the port.

To delete a port:

a) Click on the row of the port.

b) Click on the symbol at the beginning of the row.


c) Click YES to delete the row.

4. Click on + infront of the folder Source Ports to see the subfolders. A folder for every port is displayed.

Signal Configuration Source Port

1. Click on the port folder for configuring the signals.

77

DIOLINE PLC ▪

Type in a 0 if do not want to use the sink time supervision.

Following table appears:

2. Type in a Signal Name.

Use the same signal names in the application software (MULTIPROG) as in the configuration.

3. To combine signals in a group, type in a Group Name. Group names are not evaluated, they are just for overview purposes.

4. Type in the Port Offset.

5. Choose a Signal Type from the drop down list.

6. Type in the Signal Size [words].

7. Choose if a Check Variable should be allocated to the signal.

A check variable shows if a signal is valid or invalid on the bus.

a) Type the Bit-offset in the column CV Port-Offset

b) The check variable is 2 bits long. The length of the check variable will appear in the column CV-Length [bits]

Sink Port Configuration

1. Click on the folder sink ports in the menu tree.


2. Do the same steps like in the source port configuration.

In the column Number of Base Cycles Type in the sink time value the base cycle should be multiply by. The amount is the actual sink time supervision for the sink port.

78

DIOLINE PLC ▪

Signal Configuration Sink Ports

1. Click on the port folder for which you want to configure the signals.


Do the same steps like in the source port signal configuration.

Saving the Configuration

1. Click File in the menu bar.

2. Choose Save as MVBCFG-File.

The window Save as appears.

3. Type in a file name.

4. Always save the configuration under following file name: MVBCFG.bin. Otherwise the PLC cannot interpret the file.

79

DIOLINE PLC ▪

Graphical View of the Configuration

1. Click View in the menu bar.

2. Choose Port Map.


3. Choose under Port address the port you want to display.

4. The port is displayed by bits.

▪ Signals are marked blue with the letters Sn. The index n is according to the variable.

▪ Under signal mapping you can see the names of the variables.

▪ Check variables are marked green with the letters Cn. The index n is according to the variable.

▪ No allocation.

▪ Undefined area.

▪ The area L-Bus Mapping and the PV (process variables) are not relevant for a MVB configuration of the PLC.

To load the MVB configuration file on the PLC see chapter "Download of Configuration Files" on page 105.

80

DIOLINE PLC ▪

11.4.5.2 MVB Function BlocksThe embedding of following function blocks from the MVB-IKS library is necessary, to monitor and control the MVB interface.

Additional to the main function block MVBInfo there are several function blocks for the sink and source data, depending on which kind of variable types should be received and transmitted.

MVBInfoThe function block displays the state of the bus


Red Controls the red Bus LED (FB1ERR) BOOL

Green Controls the green Bus LED (FB1ST) BOOL

Device Disturbance If TRUE the bit Some Device Disturbance (SDD) of the device status word will be set.

BOOL

System Reserved If TRUE the bit System Reserved (SER) of the device status word will be set.

BOOL

GlobalSetDefault If TRUE the default value of the output variable will be written on every function block Source.

BOOL

GlobalValid If TRUE the input Valid is enabled on every function block Source.

BOOL


Address Displays the actual address of the PLC on the MVB.

UINT

LAT If TRUE LINE A is trusted. INT

RLD If TRUE the redundant LINE is disturbed. UINT

Error Displays an error number. For an explanation of the error numbers see chapter "Error Treatment" on page 133.

UINT

SinkTimeError Is TRUE if an STS time violation occurred. BOOL

MVBCFGVersion Displays the version of the configuration file. UINT

DEVICENumber Displays the chosen MVB configuration. UINT

81

DIOLINE PLC ▪

Behavior of the LAT and RLD Bit

The table below shows the behaviour of the LAT and RLD Bits at the interruption and reconnecting of the single MVB channel connection.

MVB Port

The variables are combined in groups and they are related to certain ports. The port defines the characteristics of the variable groups. The characteristics can be displayed with this function block.

Sink Function blockThere are several function blocks for the sink variables of the MVB. A function block for every type of variable is available. Every function block is set up after the following principal:

STEP WIRE A WIRE B LAT RLD

1 OK OK 1 0

2 Broken OK 0 1

3 OK OK 0 0

4 OK Broken 1 1

5 OK OK 1 0

6 Broken Broken 1/0 toggle 1


Port Defines the port number. UINT


Source If TRUE, the port is a sourceport. BOOL

Sink If TRUE, the port is a sinkport. BOOL

SinkTime This Output is just valid for the sink ports. Displays the defined sink time supervision for the chosen port.

Error Displays an error number. For an explanation of the error numbers see chapter "Error Treatment" on page 133

INT


Name Defines the name of the variable. The signal name in the MVB configuration and the variable name of this input have to be the same.

STRING


Out Displays the bus data of the chosen variable. UINT

82

DIOLINE PLC ▪

Source Function BlockThere are several function blocks for the source variables of the MVB. A function block for every type of variable is available. Every function block is set up after the following principal:

If the check variable is defined for a signal and received as invalid the received data is not adjusted to zero.

If the STS is defined for a port and STS time violation occurs the received data is adjusted to zero.

Valid Is TRUE if the check variable of the signal is valid. BOOL

Error Displays an error number. For an explanation of the error numbers see chapter "Error Treatment" on page 133.

INT

Port Displays the port number of the variable. UINT


Name Defines the name of the variable. The signal name in the MVB configuration and the variable name of this input have to be the same.

STRING

In Input for the transmission data. Different data types for every function block have to be used.

UINT

Default In every configuration a default value has to be defined.

BOOL

SetDefault If TRUE the default value will be sent on the MVB bus.

BOOL

Valid If TRUE the check variable of an signal will be valid.

BOOL


Error Displays an error number.For an explanation of the error numbers see chapter "Error Treatment" on page 133.

INT

Port Displays the port number of the variable. UINT

83

DIOLINE PLC ▪

11.4.6 CANopen Master Configuration

11.4.6.1 SYCON.NETThe Configuration of the CANopen network must be set in the SYCON configurator.The Tool is implemented in a seperate workspace in MULTIPROG.

EDS FileAn EDS File (Electronic Datasheet) is needed for every device on the CANopen Bus. The file contains the object index and the possible configurations of the devices. If such a file does not exist for a device it can be generated and imported in the SYCON configurator. The EDS files for the CANopen Master and Lütze devices are available and can be used directly in the configurator.

To import an EDS file follow those steps:

1. Copy or save the generated EDS under following path:\Documents and Settings\All Users\Appdata\SYCONnet\CANopen\EDS

2. Open MULTIPROG.

3. Open SYCON by clicking in the toolbar.

4. Click in the netDevice window.

5. Click Network in the menubar.

6. Choose Device Catalog.


7. Click Reload.After a successfull loading process the EDS file is in the device catalog.

84

DIOLINE PLC ▪

Configuration

The Configuration is partly based on an example with a buscoupler and a 8 DI/DO module.1. Open MULTIPROG.

2. Open a project or generate a new one.Generate a cyclic task with 50 ms.The processing time of the drivers is 20 ms. It is recommended to set the cycle time to min. 30 ms.

3. Open SYCON by clicking in the toolbar.


▪ On the right side of the netDevice window the menu tree is displayed. Choose the master and slave devices from there.

▪ In the netDevice window the connection from the Master to the Slave is shown. The connection is marked by a violet line. It is only active if a master is insert.

▪ The green line in the netDevice window marks the connection between the system and the CANopen Master.

Adding a Master

The DIOLINE PLC is the Master.

1. In the menu tree click on the + infront of the folder Hilscher.

2. Click on the + of the subfolder Master.

3. Click on the master NetX500COM.

4. Drag the master on the green connection line in the netDevice window.The CANopen Master NetX500COM is inserted. The violet line is the CANopen Bus. Connect the slaves to that bus.

85

DIOLINE PLC ▪

For further Information read the operating instructions of the CANopen buscoupler.

Adding a Slave

In this example the buscoupler DIOLINE 20 CANopen is the slave.

Before adding the slave to the system, set the node ID and the baudrate on the device. Turn the rotary switches with a screwdriver to make the settings. For exampe:

1. Set the node ID to 2:Set the first rotary switch to 0.Set the second rotary switch to 2.

2. Set the baudrate to 4 (125 Kbits/s).

3. Restart the buscoupler that the settings can be applied.

The node ID has to be unique. The node ID can just occur once in the CANopen network.

Make following settings in SYCON:

4. Click in the menu tree on the + infront of the Lütze folder.

5. Click on the + infront of the subfolder Slave.

6. Click on the Slave DIORAIL(Diorail108mod.eds).

7. Drag the slave on the violet connection line in the netDevice window.

Master Configuration

1. Make a right click on the draged master.

2. Choose Configuration.

86

DIOLINE PLC ▪


Driver

The driver has to be configured to connect the SYCON configurator and the CANopen Master of the PLC.

1. In the navigation click Driver.

2. Choose the driver TCP/IP for netX from the list.

3. In the navigation area click TCP/IP Driver for netX.Type in the IP address of the DIOLINE PLC in the IP Start Adress column. If the adress is not known, type in a range where the master could be.The IP address will be searched automatically.

Device Assignment

For a function system allocate the right physical device to SYCON.net. In this case it is the NETX CHIP of the PLC.

1. In the menu click on Device Assignment.

2. Click Scan.Some physical devices will be listed.

3. Choose the right device by clicking the checkbox infront of the device.

4. Click OK to confirm.

87

DIOLINE PLC ▪

Master Settings

1. Choose Automatically by device for the start of the bus communication.

2. Choose 1000 ms for the application monitoring time.

3. Choose Big Endian for the storage format.

4. Choose 2 byte boundaries for the module alignment. Every slave node will be on an even memory address. Important for the word adressing of the L-Bus.

5. Choose buffered host controlled for the Process data handshake. For further information read also the CANopen Master netXDTM documentation from company Hilscher.

Bus Parameters

1. The device description can be changed at any time.

2. For the node ID and baudrate type in the same values as set on the device. For example for the node ID 1 and 125 kBits/s for the baudrate.The COB-ID and the cycle period for the SYNC telegram can be set to the standard values.

COB-IDs with 29 Bit are not tested and not supported at the moment.

88

DIOLINE PLC ▪

3. If the master should be stopped in case of an error, choose the checkbox stop in case of monitoring errors.Monitoring errors are: Nodeguard and heartbeat errors.The communication will be stopped of all active nodes.If the checkbox is not choosen in case of an error the master tries to continue the communication with the nodes. The bus will not be stopped.

4. Choose the checkbox Send Global Start Node. After the master starts all nodes, a global start node will be send for synchronization.

Address Table

1. Click Address Table in the navigation area. The table shows all slaves of the master which are added to SYCON configurator. For every slave the mapped PDOs are listed.

To export the list as a CVS file, follow these steps:

a) Click CSV Export.

b) Choose a directory.

c) Type in a file name.

d) Click Save.

The file can be opened in a spread sheet program like excel.

89

DIOLINE PLC ▪

Node ID Table

1. Click Node ID Table in the navigation area.

▪ All availables nodes in the master are listed.

2. Click the checkbox to activate or deactivate the nodes. In the column Node ID the Node ID for every single slave can be configured.

SDO Table

1. Click SDO in the navigation area.

▪ All Service Data Objects of the nodes which are transmitted during the boot up phase are listed with content.

COB ID Table

1. Click COB ID Table in the navigation area.

▪ The table shows the configuration of the SYNC telegram and the active PDO configuration for all slvave nodes.

▪ Following telegram types are listed:

SYNC Synchronization Telegram

RXPDO[x] Received processData Object (Receive)

TXPDO[x] Transmitted Process Data Objects (Transmit)

2. Choose in the column Auto Alloc if an allocation should be done automatically.If choosen:

▪ The allocation of the standard paramter for the COB-ID is done automatically.

If the standard values will not be accepted The addressing of the PDOs has to be done manually by the user. Remove the checkmark from thecolumn Auto Alloc.

90

DIOLINE PLC ▪

Node Boot Up

1. Click Node Boot Up in the navigation area.

▪ It is the Node Boot Up start performance of the master.

▪ If no slaves are available or configured all options under this menu item are deactivated.

▪ Make the settings for all slaves: Choose the slave from the drop down list selected node.

▪ In the presetting all options are choosen.

▪ To deactivate an option: click in the checkbox of the option to remove the checkmark . Or click on the rectangle with the particular option.

▪ If changing the options the illustration with the rectangles will change.

Monitoring

It is possible to set the monitoring for the nodes among each other. You can choose between two monitoring methods:

▪ Heartbeat Protocol

▪ Node Guard Protocol

Heartbeat Protocol

1. Click Monitoring in the navigation area.

2. Choose a node from the drop down menu (NETX-COM <1>) which should be monitored by another device.

▪ Define the time the master should send the heartbeat. If no monitoring should be done, type in “0“.

3. Under Consumer all slaves are listed. Check the checkbox active to choose a slave.

▪ Click in the column Consumer Time. Set the time. The time has to be bigger than the producer time of the master.

91

DIOLINE PLC ▪

4. If all datas are parameterized click Apply.A green square with a checkmark and Save operation succeeded appears in the left lower corner of the window.

5. Click OK to close the window.

Node Guard Protocol

1. Choose a Slave DIORAIL (Diorail108mod.eds)<2> from the drop down list which should be monitored by the master.

2. Set the Guard Time.

▪ The guard time sets the time for sending the guardframe of the master.

3. Set the Life Time Factor.

▪ The Life Time Factor is the factor the guard time is multiplied by. The sum is the expecting time of the master for the answer of a slave.

4. If all datas are parameterized click Apply.

5. Click OK to close the window.

Slave Configuration

To configure a slave follow these steps:

1. Click right on the slave icon in the netDevice window.

2. Choose Configuration.


General Settings

The ID of the slave which set in the master and the device profile from the eds file are displayed.

92

DIOLINE PLC ▪

The profiledata cannot changed.

Special Function Objects

▪ Information of the different telegrams are displayed. The settings/changes has to be made in the master DTM.

▪ The slave can be configured for generating SYNC messages.

▪ The time stamp is no supported at the moment.

▪ The EMCY Telegram of the slave can be switched on and off.

▪ The SYNC ID and the EMCY ID of the slave can only be configured in the CANopen master.

Object Directory

All objects which are read out of the participant are listed.

▪ You can choose from the drop down list which object configuration should be displayed.The selection can be changed with Area and Status or Object.

▪ In the column Configure objects can be disabled or enabled.

▪ In the column Index Subindex the object index numbers with the subindex are listed.

▪ In the column Name the symbolic name of the object are listed.

▪ The column Access shows the access authorization of the objects:

RO Read Only

RW Read Write

WO Write Only

93

DIOLINE PLC ▪

This values are defined in the EDS file.

▪ If clicking any cell of the table the values are shown in the text fields:

▪Display mode (decimal or hexadecimal).

▪The current configured value.

▪The default value.

▪The data type which displays the minimum and maximum values.

If it is a descriable object the current value can be changed.

Properties (Processdata Objects)

In the list all receiving and transmitting PDOs are listed.

1. Choose RPDO or TPDO from the drop down list to display

▪ TPDO are sended by the node.

▪ RPDO are received by the node.

1. In this window PDOs can be choosen and configured:

By setting or removing a checkmark in the checkbox PDOs exists PDOs can be actived or deactivated.

To request PDOs by a remoteframe: Set a checkmark to enable RTR.

The master does not support 29 bit identifier.

94

DIOLINE PLC ▪

Transmission Mode

▪ synchron acyclicThe PDO is transmitted synchron, but acyclic. The transmission mode combines process-controlled and synchron.

▪ synchron cyclic (1-240)The PDO is transmitted with the SYNC telegram. The cyclic time is defined by the set SYNC cycletime multiplied by the parameter of the field Transmission Rate.

▪ Event-DrivenThe PDO is send at a change of data.

▪ Profile SpecificThe PDO is send at a change of data.

Addiotionally the option inhibit time and event timer are available:

▪ The inhibit time defines the event trigerred mode. This mode sets the time how long a TXPDO should not be send though a data change was a made.

▪ The event timer defines the time a PDO should be send though data were not changed.

For this example all settings for the first RX/TXPDO are the standard settings.Remove the checkmark from the checkbox PDO exists at all other RX/TX PDOs. Only the first RX/TX PDO is available for the CANopen buscoupler.

The activated PDOs are used for the communication. The corresponding parameter are added in the master configuration. The master is sending the parameter to the nodes during the initialization via the SDOs.

▪ The column Index displays the object index of the PDOs.

▪ The column PDO-Name displays the name of the PDO.

95

DIOLINE PLC ▪

Mapping (Process Data Objects)

1. Choose from the drop-down list Filter PDO Type the mappable objects which should be displayed in the list.

▪ From the drop-down list Object-Directory Array the object array, which should be displayed can be choosen.

▪ In the upper list all available objects which can be mapped to an RX or TX PDO are listed.

▪ In the lower list the mapped objects are listed.

2. To map an object, double click on the PDO in the list Mappable Objects.

3. Click Apply to save the settings.

Do a pseudo setting and click Apply two times, to save the configuration. The configuration is not active after the first try because of a bug. Do following steps:

96

DIOLINE PLC ▪

4. Change the settings again by attaching a new PDO and deleting it.

5. Click Apply.

▪ By clicking the arrow buttons the attached objects can be scrolled up or down. By clicking the scissors an attachement can be deleted.

Device Description

1. Choose Device from the folder Device Despriction.The device information are displayed.

The settings cannot be changed.

EDS

Choose the menu item EDS.To display the EDS file of the choosen slave follow these steps:

1. Type in any text to sought a text passage from the esd file in the search field.In the option it is possible to choose Match case or Match whole word.

2. Click Find Next.

Closing the Configuration

1. Click Apply to save the settings.

2. Click OK, to shut down the window.

97

DIOLINE PLC ▪

Processdata Mapping

To attach the processdata of the PDOs to the project specific (global) MULTIPROG variables follow these steps:

1. Click Processdata Allocation in the tool bar.


2. Click on the + infront of the master in the right menu tree.

3. Click on the + infront of DIORAIL (Diorail108mod.eds)[DIORAIL(Diorail108mod.eds)]<2>.

4. Click Receive PDO1 Communication Parameter or Transmit PDO1 Communication Parameter to allocate the global variables of the project to the PDO. The object is displayed in the list.

5. Click in the left menu tree on + infront of Ressource <--> NETX-COM[NETX 500 COM] <1>(#1).Because of a user defined configuration the name can be different.

6. Click on the folder Global_Variables. The global variables which were generated in the project appear in the lower part of the window.

7. Drag the variables for the in and/or output in the column Name of connection of the table on the right.

8. Choose the master from the menu tree by clicking the right mousebutton: NETX-COM [NETX 500 COM] <1>(#1)<-->Configuration/Ressource

9. Choose Select task. Choose the task which was created first and in which the CANopen driver should run.

Do not choose the default-task. Data inconsistency can appear during the processing of the CANopen data.

98

DIOLINE PLC ▪

11.4.6.2 Downloading the CANopen Configuration

10.Make a right click on the master again.

11.Choose Driver Parameters.


Make following settings:

12.For the Cardnumber type in “0“. PLC specific there is no card in the device. The CANopen Bus is realized by the CPU directly.

13.Type in the channelnumber of the Master. The channelnumber is conform to the BoardNo on the Input of the functional block CIFNetXInfo.Channelnumber 0: If a second Canopen fieldbus exists and has to be configured, type in 1.

14.Type in the timeout in milliseconds. The standard value is 100 ms.

15.Type in a standard address of the input and output data. Handle the start adresses like the offset of the I/O configuration.

The offset adresses can not be set twice.

16.Click Accept.

1. Open Sycon by clicking in the toolbar.

2. The PLC must be in Stop mode.

3. Make a right click on the master.

4. Choose Download.

5. A message that the download was successfull appears.

99

DIOLINE PLC ▪

11.4.6.3 Function BlocksEmbed the following function blocks of the firmware library CIFNetX.

CIFNetXInfo

Monitores the CANopen Bus status.

This functional block has to be insert in the same task as the driver in SYCON.Net.

Inputs Description Type

BoardNo Demand of the Channelnumber. INT


CardType Displays if the PLC is Master or Slave STRING

Slave/Master Displays if PLC is Master or Slave.0=Slave, 1=Master

BOOL

Run Displays if all configured subscribers on the bus are communicating.

BOOL

Partly Displays that not all configured subscrivers on the bus communicating.

BOOL

Stop Displays that the bus is in the stop mode BOOL

SystemError If a system error occurs a error number will be displayed.

INT

ReadError If a read error occurs a error number will be displayed.

INT

WriteError If a write error occurs a error number will be displayed.

INT

WDTime Time in which the watch dog has to be triggered again by the userprogram. If the time is 0 the watchdog is disabled.Allowed values are 20 to 65535 ms. The standard value is 1000 ms.

INT

Firmware Displays the current version of the firmware. INT

Version Displays the current version of the CANopen Network.

INT

100

DIOLINE PLC ▪

CIFNetXDevice

This function block monitores one slave. For every slave such a function block has to be insert.

Message BOX

With the Message BOX NMT and SDO messages can be send or received out of the application (on the master side). For example: Diagnosis messages, which are stored in the object index of a slave can be queried or setting parameters can be changed during the runtime. It is also possible to change the NMT status of a slave during the runtime (on the master side).

In the download area an example project can be found. The project contains all necessary datatypes, functional blocks and programs for the handling of the NMT and SDO messages.

CIFNetXAsync

The function block controls the access of the Message BOX.


BoardNo Demand of the Channelnumber. INT

DeviceNo Demand of the COB ID of the monitored CAN subscriber.

INT


Configured Displays if the subscriber is paramterized in the current configuration.

BOOL

Exchange Displays if data are exchanged with the subscriber.

BOOL

Diagnose Displays if diagnosis data are available for the subscriber.

BOOL


SendData Handling of the sending data. ANY

RecData Handling of the receiving data. ANY

SendLength The length of the sending data. INT

Destination Handler of the CANopen message queue. BYTE

Command Command for different message box functions.(Can be read in the CANopen Master API from Hilscher)

BYTE

Extension Reserved and always 0. BYTE

101

DIOLINE PLC ▪

CO_Zuweisung_SDO

Function block for the clear assignment of the necessary data for the SDO transmission and receiving.

Route Only for internal use of the NETX firmware. Has to be 0.

BoardNo Input for the channel number. INT

Start Trigger for starting the functional block. BOOL


SendData Handling of the sending data. ANY

RecData Handling of the receiving data. ANY

RecLength Display the length of receiving data in Byte. INT

Busy Is true as long a functional block is processed. BOOL

Done Is true if the processing of functional block is completed.

BOOL

Error If an error occurs a error number is displayed. INT

State Displays error numbers which can be found in the Hilscher API.

INT


NodeOD Commands the COB ID to which CAN subscriber the SDO has to be send.

INT

ObjektIndex Displays the object index. INT

SubIndex Displays the sub index. INT

DataLength Displays the length of the service data objects INT

Byte0 Contains the first byte of the slave object index which has to be written.

BYTE

Byte1 Contains the second byte of the slave object index which has to be written.

BYTE

Byte2 Contains the third byte of the slave object index which has to be written.

BYTE

Byte3 Contains the fourth byte of the slave object index which has to be written.

BYTE

Byte4 Not used

Byte5 Not used

Byte6 Not used

Byte7 Not used

102

DIOLINE PLC ▪

CO_Zuweisung_NMT

The functional block is for the assignment of the COB ID and NMT commands. The master can change the status of the slave in a network, following status are possible:

▪ InitializationAfter switching on the node has this status. The software and the device communication will be initilized. After that the node will be in the pre-operational status.

▪ Pre-OperationalIn this status the PDOs are not active. The status is used for configuring the CANopen devices. By transmitting SDOS the object directory of the single devices can be changed. Additionally emergency, synchronization, time stamps and (of course) NMT controll messages can be transmitted or received. While transmitting a start remote node, the node will change to the operational status.

▪ OperationalIn this status input and output data can be exchanged via PDOs. It is possible to change the configuration by the transmitting SDOs.

▪ StoppedThe module interrupts the data communication, except the guarding and heartbeat (if active).With an NMT message the status can be changed to pre-operational or operational.


msg Output of the compiled sending data for the CIFnetXAsync functional block.

Nr. Status Description

(1) Initialization finished Automatical changeover to pre-operational

(2) Start Remote Node[cs=01H]

Starts the module. Starts the transmitting of PDOs.

(3) Enter Pre-Operational Mode [cs=80H]

Stopps the PDO transmission. SDO is further active.

(4) Reset Node[cs=81H]

Modul reset by the application.

103

DIOLINE PLC ▪

(5) Reset Communication[cs=82H]

Reset of the communication.

(6) Stop Remote Node[cs=02H]

Stopps the communication, except nodeguarding and heartbeat.


NodeID Defines the COB ID of the subscriber. Broadcast if COB ID=0.

INT

NMT_Befehl Sets the command for every node.


msg Output of the compiled sending data for the CIFnetXAsync functional block.

104

DIOLINE PLC ▪

11.5 Compiling and Loading

11.5.1 Download of Configuration FilesFollowing files can be downloaded on the PLC:

▪ ProConOs.INI

▪ TCPIP.CFG

▪ MVBCFG.BIN

Follow the steps to download a configuration file:

1. Start MULTIPROG.

2. Create or open a project which can establish a connection to the PLC

3. Click in the toolbar.

The Ressource window appears:

4. Click Stop.

5. Click Download.

The Download window appears:

6. Click Download File.

7. Choose the configuration file to download.

8. Click Download.

9. Restart the PLC.

In the message window can be seen, if the loading was successful.

The configuration files are only active after a restart of the PLC. The commands flashdr and flashrem are active after the download.

105

DIOLINE PLC ▪

11.5.2 Downloading a MULTIPROG Project

After finishing the programming it is necessary to compile and download the project.

Before downloading the project make sure to download the necessary configuration files and restarting the PLC. In some cases errors can occur.

1. Click Code in the MULTIPROG menu bar.

2. Choose Make.

3. The compiling process starts. The state of the compiling is written in the Message Window.

4. In case of an error:

a) In the Message Window, click on the line with the error.

b) It forwards to the part of the SPS program which causes the error.

If the compiling is done without errors:

3. Send the project over the ethernet interface on the PLC.

4. Click in the menu bar.

5. The window Ressource appears:

6. Click Stop to stop the operation of the PLC, if the PLC is in the Run mode.

7. Click Download.

106

DIOLINE PLC ▪

The window Download appears.

For the downloading process following options can be set:

▪ Include BootprojectBy checking that option the project on the PLC will start automatically after booting. The project is stored in the flash memory. By not checking that option the project is stored in the RAM.

▪ Include SourcesBy checking that option the source code will be loaded on the PLC.

▪ Include OPC dataBy checking that option the information of the chosen OPC variables for the visualization will be loaded on the PLC.

8. Click Download under Project.

9. The current project on the PLC will be transcribed. An alert window appears to ask if the transcription should be done.

10.The PLC is compiling the project code for the system architecture on the PLC. If no error occurs the project is downloaded.

11.Click Cold in the window Ressource.

The PLC starts cold and is in the RUN mode.

12.The PLC LED is permanently on.

107

DIOLINE PLC ▪

11.5.3 Deleting the FlashdiskThe flashdisk must be reset manually, if using firmware version 1.72 or higher. Please proceed as follows:

1. Deleting the flashdisk without a configuration fileDownload the file flashrem.upd on the PLC. Proceed as described in chapter “Download of configuration Files“.

2. Deleting the flashdisk with a configuration file and the flashdisk formattingDownload the file flashclr.upd on the PLC. Proceed as described in chapter “Download of configuration Files“.

108

DIOLINE PLC ▪

109

11.6 Visualization – ProVisITThe program is implemented in MULTIPROG. It is for machine visualizing. It can communicate with every controller and devices which are configured in the OPC Server.

For visualizing with ProVisIt read the MULTIPROG Quick Start Manual.

DIOLINE PLC ▪ Operation

12 Operation12.1 Hardware Architecture

PFDThe Parallel Flash Disk has a size of 2 MB. Saves diagnosis data permanent, for example errors.

WatchdogThe watchdog monitors the PLC and is controlled over the function block IKSDigitalMonitor. If the watchdog does not receive a request or a signal from the PLC after 2 seconds it will restart the PLC.

CryptoIt contains the license of the CANopen Master. For the CANopen Slave a license is not necessary.

FRAMThe Ferroelectric Random Access Memory is a non persistent memory with a size of 4 kB. It saves the retain variables.

RTCReal time clock.

JTAGProgramming interface.

UART1Extended Interface RSBUS or RS485 BUS.

SDRAM (Synchronous Dynamik Random Access Memory)The Memory of the PLC with a size of 32 MB. For the project software <1MB can be used, because of the PLC performance.

Serial FlashThe serial flash stores the rcXOperating System, the ProConOS runtime environment, the PLC firmware, the boot project and the configuration files. The

110


data are read from the flash memory and be written in the SDRAM at the startup of the PLC.

UART0Connection of the serial interface RS232.

XM2 and XM3Connection of the fieldbusses.

PHY0 and PHY1Connection of the Ethernet.

111


12.2 Software ArchitectureBelow the modular structure of the operating system and its gateways are described.

rcxOperation SystemThe operating system of the PLC.

ProConOSPLC runtime environment.

Dual Ported MemoryThis layer is the communication between firmware drivers and functions and the ProConOs runtime enviroment.

FirmwareIn this layer all driver specific processes for the PLC, fieldbuses and other functionalities are done.

HardwareCPU and peripheral interfaces.

112


12.3 Memory Architecture (non volatile memory)

SD CardFor saving project sepcific user files.

FRAMFor saving retain data. Because of data mirroring 4 kB are effective available. The smallest unit of the FRAM are 4 byte. The FRAM can be triggerd by a function block or by setting a time value in the PROCONOS.INI.

Parallel FlashSaves diagnosis data. It is devided in two sections. The borders of sections are defined in the PROCONOS.INI. Please see Seite 66.

Serial FlashThe serial flash is devided in two sections. One section is reserved for the Firmware, the other is provided as FAT12 flashdisk. In this section all boot projects and all project specific configuration data are saved.The memory cannot be written additive.

113


12.3.1 RAM Architecture (volatile memory)The RAM is the main memory of the PLC. Every PLC has a memory of 32 MB.The RAM is devided in 5 different sizes and functionalities:

PROCONOS RAMFor processing the program code 1 MB is provided. The amount of free memory can be seen in the control dialog>program memory. This memory area stores the code of all POUs of the multiprog project. The full amount of the actual used program code can be seen in the control dialog > POU in the column “Code“.

Additional the Non-Retain and Retain Data are saved in the PROCONOS RAM. The size of the memory area depends on the used ressource. The data area always starts at byte 2000, because of that 2 kB have to be sustracted from the reserved ressource sizes:

See also Configuration of the PLC Memory Ranges on page 115.

RAM-DISKThe size of the RAM-DISK is 1 MB and it is organized as a FAT 12 System. In the RAM-DISK a part of the Bootproject is unziped and some Hilscher specific control data (TASK Configuration/ I/O Driver etc.) are saved. Also the fieldbusconfiguration (max. per FB 100 kB) can be saved here. Because of the big amount of data, the bootfile should be not bigger than 820 kB (80% of the RAM-DISK).

BufferThe checksum.upd and flash.upd is saved here during a firmware update via MULTIPROG or SD Card. After the data are saved a CRC and size check is done. The size is limited to 3 MB. After a successful check the data are automatically copied in the serial Flash.

OS-RAMIs used for different Operating System Tasks.

2. BufferThe second Buffer is reserved for further operation.

Ressource Reserved Size Effective usable size

PCOS_ARM_IKS 128 kB 126 kB

PCOS_ARM_IKS_M 256 kB 254 kB

PCOS_ARM_IKS_L 512 kB 510 kB

114


12.3.1.1 Configuration of the PLC Memory RangesTo confiigure the memory ranges start MULTIPROG and proceed as follows:

1. In the projecttree make a right click on Ressource.

2. Choose Settings.

The ressource setting dialog appears.

3. Click the button Data area...

The data area dialog appears.

Non retain data

▪ Start userThe value of the startadress wich starts at byte 2000. The startadress cannot be changed.

▪ End user / Start systemDefine a start value for a lower memory range where user data can be saved. The effective amount of memory can be set in the I/O configuration (VAR_CONF). The stored data can be accessed via the operation pointer.

▪ End system (max 131071)Define the end value of the memory range.

115


▪ Reserve per POUIt is possible to allocate an defined memory reserve to an POU. For further information read the MULTIPROG online help.

Retain Data

The described settings for the non retain data are also valid for the retain data.

4. Activate the checkbox Declare user memory at I/O configuration automatically. An automatic entry (VAR_CONF) with the set values is done in the I/O configuration.Only deactivate the checkbox if using old projects or special I/O configuration.

116


12.3.1.2 Checking the Program Size and FRAM dataWhen compiling a project in MULTIPROG in the message window all used bytes for the POUs (non retain data) and the permanent saved variables (retain data) are listed in the Infos tab.

1. To see how much memory of the RAMDISK is still available click in the toolbar.

The ressource window appears.

2. Click Info.

117


The free program memory space for the programm code (POUs) and the free memory space for the Retaindata is shown.Systemdata shows the free amount of memory for systemdata. This memory is not changeable by the user and used for PLC diagnostics.

Click the POU tab to the code size in bytes of every POU which is used in the program memory of the ressource. Also the sizes of the retain and non retain data which are used by the POU are listed. The last row shows the summery of used memory of every column. All size specifications are in bytes.

118


12.3.2 Monitoring the PLC tasks and CPU Capacity

We recommend that the processing time for the PLC tasks should never be higher than 50 % of the cycle time. It assures that the other 50 % of the CPU capacity can be used for the lower priority tasks.

It is possible to monitor the CPU capacity and the task time in MULTIPROG by using special system variables and memory mapping. The description is written in the following section.

1. Open MULTIPROG.

2. Generate a data type sheet or download the data type file in the Lütze Download Area.

Importing a file

3. Click on Datatype in the project tree window.

4. Click File in the menu.

5. Choose Import.


6. Choose Extended IEC 61131-3 Import

7. Click OK.

119


8. The window Object typesappears.

9. The option Datatypes is chosen.

10.Click OK.

11.Choose the path of the data type file.

12.Click on the filename in the right window.

13.Click OK.

The file will appear under Datatypes in the project tree window.

14.Double click on Global Variables in the project tree window.

15.Generate and map the following variables:

It is also possible to download an excel file with those predefined variables in the Download area.

a) Copy the variables of the excel file.

b) Open the global variables sheet in MULTIPROG.

c) Click in the last row of the sheet.

d) Paste the variables of the excel file.

120


16.Click Logical POU in the project tree window.

17.Import the predefined PLC_Diagnostic POU from the Lütze download area. Follow the steps under importing a file.

The new POU appears in the project tree window.

18.Implement the new POU in the task.

▪ In the debug mode the task information and the CPU load can be monitored in the POU PLC_Diagnostic.

▪ To start the mode the project has to be compiled and downloaded on the PLC.

▪ The PLC has to be in the run mode.

19.Click to start the debug mode.

20.Open the PLC_Diagnostic sheet in the project tree window.

The online values will be shown in the sheet.

121


12.3.3 L-Bus PerformanceThe PLC tasks have a higher priority than the communication tasks. The communication tasks cannot be processed until the PLC tasks are done.

The two diagrams are showing the data update of the PLC tasks in two different task configurations.

Priority – Time - Diagram Example 1

In the PLC Task 1, the data handling and the l-bus driver are actualized in every cycle.

In contrast to the first diagram the processing time of the second task has been increased. The result is that not every L-Bus cycle gets new data.

If working with the L-Bus in a time critical environment it is important to know these performance issues.

▪ Red lines: cycle time of the tasks

▪ Black bars: processing time of the tasks

▪ Arrows: task change regarding the priority

122

DIOLINE PLC ▪ Maintenance Software

13 Maintenance Software

13.1 Update Firmware (ProConOs)The update of the firmware can be done by MULTIPROG or the SD card.

13.1.1 Update via MULTIPROGThe firmware is saved on the serial flash.

To update the firmware, the serial flash has to be transcribed by the new version. Follow those steps:

1. Open MULTIPROG.

2. Open the current project.

3. Click on in the tool bar.

The Ressource window appears.

4. Click Stop to stop the PLC if running.

5. Click Reset to reset the running project.

6. Click Download.


7. Click Delete on target to delete the boot project.

8. Click Download File.

123



9. Choose the file CHECKSUM.upd.

10.Click Download.

11.Click again Download.

12.Choose the file flash.upd.

13.Click Download.

If the download is successful the flash process starts. The APP and USER LED are flashing alternatively. The process takes 1.5 minutes.

Do not switch off the PLC while the flash process is running. If such a case occurs it is possible that the PLC is not accessable anymore. The PLC has to be sent to Lütze Transportation GmbH.

Close all MULTIPROG ressource control dialogs before running the flash process. If a dialog is still open errors during the flashing can occure.

14.Click Info in the Ressource window to check the firmware version.

124


13.1.2 Updating the PLC via the SD CardTo update the PLC with configuration files, program files or firmware files.

For all updating processes a autoexec.bat must be created.

In the following chapters you can find examples of updating the PLC via the SD card.

It is possible to combine different updating process commands in one autoexec.bat file.

125


13.1.2.1 Updating the Firmware by the SD Card

While copying the files the APP and USER LEDs are permanently on. The process takes 15 seconds. If the copying is successful the flash process starts. The APP and USER LED are flashing alternatively. The whole process takes 1.5 minutes.

Do not switch off the PLC while the flash process is running. If such a case occurs it is possible that the PLC is not accessable anymore. The PLC has to be sent to Lütze Transportation GmbH.

If an error occurs the LEDs are flashing 5 times (50 ms on, 50 ms off). For example a file to copy does not exist on the PLC or SD card.

1. Copy the files checksum.upd and flash.upd in the root directory of the SD card.

2. Open the texteditor.

3. Enter following command:fwupdate flash.upd checksum.upd

4. Save the file in the root directory of the SD under following name:autoexec.bat.

5. Put the SD Card in the PLC.

6. When powering on the PLC, push the J1User Button till the LEDs flashing 20 times fast (100 ms on, 100 ms off).

The autoexec.bat is found.

The commands fwupdate flash.upd checksum.upd are processed.

126


13.1.2.2 Updating the software via the SD Card

The Bootfile.pro cannot be directly created out of MULTIPROG. To get a valid bootfile.pro file it necessary to copy it once from a already updated PLC. This must be done because of a internal code compilation which is proceeded after each download of a bootprojekt via Mulitprog. To copy a valid bootfile.pro file from the PLC see Seite 144.

If an error occurs the LEDs are flashing 5 times (50 ms on, 50 ms off). For example a file to copy does not exist on the PLC or SD card.

1. Copy the Bootfile.pro in the root directory of the SD card.


3. Enter following command:copy2plc FILENAMEresetExample: copy2plc Bootfile.pro reset





The command copy2plc FILENAME is processed.

The PLC will be restarted.

It is possible to load all configuration files, the boot project and the firmware update in one step. In the autoexec.bat the commands for the configuration files and the boot project have to be infront of the commands for the firmware update. The commands can be found on Seite 144.

127


13.1.2.3 Updating the PLC configuration filesWith this process following files can be updated, if needed:

▪ MVBcfg.bin

▪ config.dbm

▪ PROCONOS.ini

▪ TCPIP.cfg

The config.dbm cannot be directly created out of MULTIPROG. The config.dbm must always be read out of the PLC.

The files are only updated if a restart is done, after the copy procedure.

1. Copy the configuration file in the root directory of the SD card.

▪CANopen fieldbus – config.dbmCreate an underfolder with the name port_0 for the first CANopen fieldbus. If a second CANopen fieldbus is exsisting on the PLC, create a folder with the name port_1.The directory has to be on the SD card as well as on the PLC.


3. Enter the particular command. For the commands see Seite 144.

▪CANopen fieldbus – config.dbmTo create the CANopen directory on the PLC, use the command Mkdir port_x before copy2plc in the autoexec.bat.





The commands are processed.

The PLC will be restarted.

128


▪ If an error occurs the LEDs are flashing 5 times (50 ms on, 50 ms off). For example a file to copy does not exist on the PLC or SD card.

▪ It is possible to load all configuration files, the boot project and the firmware update in one step. In the autoexec.bat the commands for the configuration files and the boot project have to be infront of the commands for the firmware update. The commands can be found on Seite 144.

129

DIOLINE PLC ▪ Demounting

130

14 Demounting

1. Push the PLC up.

2. Pull the PLC from the top hat rail.

3. Push the PLC down and take the PLC off the rail.

DIOLINE PLC ▪ Final Shutdown and Disposal

131

15 Final Shutdown and DisposalMind the valid environmental standard of your country for the final shutdown and disposal.

For the final shutdown the device has to be disassembled. Electric Parts must be disposed after the national electronic scrap regulation. You take the responsibility for the shipped article. You have to dispose the article after the terms of use and legal liability on your own costs and exempt the LützeTransportation GmbH from the responsibilities of §10 passage 2 ElektroG (Take-back obligation of the manufacturer) and any third party in this content.

If you have handled the device to a commercial third party without any contractual acceptance of the disposal, you have to take back the device after the final shutdown on your own cost and the legal liability.

The entitlement of indemnity from Lütze Transportation GmbH by the customer does not prescribe before two years after the final shut down of the device. The two year deadline of the suspension of statue forlimitations can start with a written message about the terms from you to Lütze Transportation GmbH.

DIOLINE PLC ▪ Service

132

16 ServiceIf you have any further questions regarding the product or our repairing service please contact us:

Lütze Transportation GmbHBruckwiesenstraße17-1971384 WeinstadtTel.: +49 7151 6053-545Fax: +49 7171 [email protected]

DIOLINE PLC ▪ Error Treatment

17 Error Treatment17.1 Error Messages of the Function blocks

17.1.1 L-BusInfo

17.1.2 MVBInfo, Sink and Source

No. Error

0 No error

1 No L-Bus component connected

2 Error at the reading of the initialization process

3 Error at the reading if the type coding

4 Error at the number of data for the process image.

5 Number of the components to high.

6 Error at the reading of the state of the L-Bus

7 Error at the writing of the first output cycle

8 Error at the reading of the first output cycle

9 Error at the writing and reading of the second output cycle

10 Error at the reading of the end of the telegram after the second cycle.

11 Timeout at the import of the quitting signal.

No. Error

0 No error

1 Error at the opening of the MVBCFG file

2 No memory for the MVBCFG file

3 Error at the reading of the MVBCFG file

4 Error at the initialization of the MVB HAL

5 Error at the start of the MVB HNF

10 Error at the creating of the semaphores

11 Error at the setting of the MVB timer

12 Error at the initialization of the MVB timer

13 Error at the setting of the MVB interrupt

14 Error at the initialization of the MVB interrupt

15 Error at switching on the MVB interrupt.

20 Error at the start of the MVB firmware task

21 Error at the Start of the MVB timer

30 MWT error at the creating of the functions.

31 MWT error at the parameter “Name”

133


17.1.3 CoRec and CoSend

32 The parameter “Name” has no valid character order.

33 The name of the signal is not in the MVBCFG file.

34 The type of the signal is not supported.

35 The port for the signals is not available.

36 The memory for this port in not available.

37 The type of the signal does not match with the definition in the MVBCFG file.

38 The value of the signal could not be set.

39 Sink- or Sourcevariables interchanged

40 STS Timeviolation

41 Variable Data invalid (CHECK BITs)

50 Invalid DEVICEnummer-Entry (0) in ProConOS.INI

51 Invalid digital local IN value for MVB configuration (0)

52 No DEVICEnummer-Entry in ProConOS.INI

53 No ProConOS.INI exists

No. Error

No. Error

1 The Interface has no entry in the ProConOS.ini.

2 The Interface cannot be opened.

3 The setting of the interface parameters are not possible.

4 The setting of the baud rate is not possible.

5 The driver is unknown.

6 The number of data bits cannot be set.

7 The number of stop bits cannot be set.

8 The chosen parity cannot be set.

10 The wrong number of the interface was chosen.

11 The interface is not set for text formats (ProConOS.INI)

12 The interface is not initialized.

13 An error at the initializing appeared.

21 The address of the send data is invalid.

22 The address of the receiving data is invalid.

23 Not enough memory for sending the data (only valid for the function block “WriteCOM”).

30 No characters were received during the telegram effective dead time.

31 No characters were received during the effective dead time.

32 The number of the received data is too small.

134


17.1.4 SetDateTime

17.1.5 FILE_OPEN

17.1.6 FILE_READ

40 The position of number of the sending data is outside the use data.

41 The length of the use data is bigger than the total number of data.

42 The value and structure of the sending data cannot be evaluate.

53 The telegram ends without a stop character (only valid for the function block “ReadCOM”).

54 The checksum of the receiving data is wrong.

No. Error

No. Error

0 No error.

20 Range of the input “Seconds” is exceeded or below.

21 Range of the input “Minutes” is exceeded or below.

22 Range of the input “Hours” is exceeded or below.

23 Range of the input “Days” is exceeded or below.

24 Range of the input “Months” is exceeded or below.

25 Range of the input “Years” is exceeded or below.

26 System error during the setting of the function block clock, depending on the operating system.

No. Error

0 No error information available.

2 The max number of files is already open.

4 The file is already open.

5 The file is write protected or the access is denied.

6 The filename is not given.

No. Error


1 Invalid file handle.

10 End of File.

12 The number of the reading characters is bigger than the file buffer.

22 No data could be read.

135


17.1.7 FILE_WRITE

17.1.8 FILE_CLOSE

No. Error



11 There is not enough memory to write data.

12 The number of characters is bigger than the data buffer.

23 No data could be write.

No. Error



20 File could not be closed.

136

DIOLINE PLC ▪ Appendix

18 Appendix18.1 Content of the Firmware Libraries

18.1.1 MVB-IKS Firmware Library

Function Block Description

MVBInfo Displays the state of the bus and controls the global bus states.

MVBPort Displays the characteristics of the port.

SinkANTIVALENT Receives an antivalent value from the bus.

SinkBCD Receives a BCD number from the MVB bus.

SinkBITSET16 Can receive a word of 16 bit from the MVB bus.

SinkBITSET32 Can receive a double word of 32 bit from the MVB bus.

SinkBITSET8 Can receive a byte with 8 bits from the MVB bus.

SinkBOOL Can receive a boolean variable from the MVB bus.

SinkCHAR Can receive a character from the MVB bus.

SinkDateTime48 Can receive an information about the time from the MVB bus.

SinkENUM4 Can receive a number from the MVB bus with a range of 3.

SinkENUM8 Can receive a number with a range of 15 from the MVB bus.

SinkINT16 Can receive a 16 bit integer variable from the MVB bus.



SinkUNSIGNED16 Can receive a 16 bit integer variable without an operational sign from the MVB bus.



SourceANTIVALENT Can send an antivalent value on the MVB bus.

SourceBCD Can send a BCD variable on the MVB bus.

SourceBITSET16 Can send a word variable of 16 bit on the MVB bus.


137


18.1.2 ProConOS Firmware Library


SourceBOOL Can send a boolean variable on the MVB bus.

SourceCHAR Can send a character on the MVB bus.

SourceENUM4 Can send a variable with a max value of 3 on the MVB bus.

SourceENUM8 Can send a variable with a max value of 15 on the MVB bus.

SourceINT16 Can send a 16 bit integer variable on the MVB bus.

SourceINT32 Can send a 32 bit ineger variable on the MVB bus.

SourceINT8 Can send a 8 bit integer variable on the MVB bus.

SourceUNSIGNED16 Can send a 16 bit variable without an operational sign on the MVB bus.





BUF_TO_BYTE Copies element data types from a byte stream in a variable, field or in another element. Supports the data type: BYTE

BUF_TO_DINT Copies element data types from a byte stream in a variable, field or in another element. Supports the data type: DINT

BUF_TO_DWORD Copies element data types from a byte stream in a variable, field or in another element. Supports the data type: DWORD

BUF_TO_INT Copies element data types from a byte stream in a variable, field or in another element. Supports the data type: INT

BUF_TO_REAL Copies element data types from a byte stream in a variable, field or in another element. Supports the data type: REAL

BUF¬_TO_SINT Copies element data types from a byte stream in a variable, field or in another element. Supports the data type: SINT

BUF_TO_STRING Copies element data types from a byte stream in a variable, field or in another element. Supports the data type: STRING

138


BUF_TO_TIME Copies element data types from a byte stream in a variable, field or in another element. Supports the data type: TIME

BUF_TO_UDINT Copies element data types from a byte stream in a variable, field or in another element. Supports the data type: UDINT

BUF_TO_UINT Copies element data types from a byte stream in a variable, field or in another element. Supports the data type: UINT

BUF_TO_USINT Copies element data types from a byte stream in a variable, field or in another element. Supports the data type: USINT

BUF_TO_WORD Copies element data types from a byte stream in a variable, field or in another element. Supports the data type: WORD

BYTE_TO_BUF Copies element data types from a byte stream in a variable, field or in another element. Supports the data type: BUF

CLR_ERROR_CATALOG Deletes the failure catalog.

CLR_OUT Sets all outputs of the process image memory to 0.

COLD_RESTART Causes a restart.

CONTINUE If the input is true, the function block continues a program.

DERIVAT Implements a time differentiation. ENABLE=TRUE

DINT_TO_BUF Element data types of variables, fields or other Elements can by copied in a byte stream. Supports the data type: DINT

DWORD_TO_BUF Element data types of variables, fields or other Elements can by copied in a byte stream. Supports the data type: DWORD

EVENT_TASK Creates an event with a number.

FILE_REMOVE Deletes a file.

FILE_SEEK Puts the data pointer at an optional position.

FILE_TELL Shows the actual position of the data pointer.

FPID The function block does the second rate proportional, integral and differential regulation.

GET_ERROR Displays detailed information about an error which is saved in the failure catalog.

GET_ERROR_CATALOG Displays current information about the actual state of the failure catalog.

GET_SYM Seeks in the PDD for a symbolic name of the variable.


139


HOT_RESTART Does a hot start. At a hot start the data will not be initialize.

MEMCPY Copies data from the data filed in the running system (source data field) in another data field running system (target data field).

INT_TO_BUF Element data types of variables, fields or other Elements can by copied in a byte stream. Supports the data type: INT

INTEGRAL Implements an integration over the time.

MEMCPY Copies data from the data filed in the running system (source data field) in another data field running system (target data field)

MEMSET Sets a part of the memory on the value of the VAL operand.

PID The function block does the second rate proportional, integral and differential regulation.

PLC_STOP Stops the PLC at an increasing slope.

RD_BOOL_BY_SYM Reads the value of the symbolic variables in PDD. The name of the variable is dedicated to a character sequence. Read the value type: BOOL

RD_BYTE_BY_SYM Reads the value of the symbolic variables in PDD. The name of the variable is dedicated to a character sequence. Read the value type: BYTE

RD_DINT_BY_SYM Reads the value of the symbolic variables in PDD. The name of the variable is dedicated to a character sequence. Read the value type: DINT

RD_DWORD_BY_SYM Reads the value of the symbolic variables in PDD. The name of the variable is dedicated to a character sequence. Read the value type: DWORD

RD_INPUT_GROUP Reads the values of the process image memory for the input group.

RD_INT_BY_SYM Reads the value of the symbolic variables in PDD. The name of the variable is dedicated to a character sequence. Read the value type: INT

RD_REAL_BY_SYM Reads the value of the symbolic variables in PDD. The name of the variable is dedicated to a character sequence. Read the value type: REAL

RD_SINT_BY_SYM Reads the value of the symbolic variables in PDD. The name of the variable is dedicated to a character sequence. Read the value type: SINT

RD_STRING_BY_SYM Reads the value of the symbolic variables in PDD. The name of the variable is dedicated to a character sequence. Read the value type: STRING


140


RD_TIME_BY_SYM Reads the value of the symbolic variables in PDD. The name of the variable is dedicated to a character sequence. Read the value type: TIME

RD_UDINT_BY_SYM Reads the value of the symbolic variables in PDD. The name of the variable is dedicated to a character sequence. Read the value type: UDINT

RD_UINT_BY_SYM Reads the value of the symbolic variables in PDD. The name of the variable is dedicated to a character sequence. Read the value type: UINT

RD_USINT_BY_SYM Reads the value of the symbolic variables in PDD. The name of the variable is dedicated to a character sequence. Read the value type: USINT

RD_WORD_BY_SYM Reads the value of the symbolic variables in PDD. The name of the variable is dedicated to a character sequence. Read the value type: WORD

REAL_TO_BUF Elementary data types from variables, fields and other elements can be copied in the byte stream. Supports the data type: REAL

RTC_S Writes the date and the time in the character sequence.

SINT_TO_BUF Element data types of variables, fields or other element can be copied in a data stream. Supports the data type: SINT

STRING_TO_BUF Element data types of variables, fields or other element can be copied in a data stream. Supports the data type: STRINGS

TIME_TO_BUF Element data types of variables, fields or other element can be copied in a data stream. Supports the data type: TIME

UDINT_TO_BUF Element data types of variables, fields or other element can be copied in a data stream. Supports the data type: UDINT

USINT_TO_BUF Element data types of variables, fields or other element can be copied in a data stream. Supports the data type: USINT

WARM_RESTART Does a warm start. At a warm start just buffered data are initialized.

WORD_TO_BUF Element data types of variables, fields or other element can be copied in a data stream. Supports the data type: WORD

WR_BOOL_BY_SYM Writes a Boolean in a variable, which is insert in the PDD.

WR_BYTE _BY_SYM Writes a byte in a variable, which is insert in the PDD.

WR_DINT _BY_SYM Writes a double integer in a variable, which is insert in the PDD.


141


WR_DWORD_BY_SYM Writes a double word in a variable, which is insert in the PDD.

WR_INT_BY_SYM Writes an integer in a variable, which is insert in the PDD.

WR_OUTPUT_GROUP Writes a value of the type output in a variable, which is insert in the PDD.

WR_REAL_BY_SYM Writes a value of the type real in a variable, which is insert in the PDD.

WR_SINT_BY_SYM Writes a value of the type SINT in a variable, which is insert in the PDD.

WR_TIME_BY_SYM Writes a value of the type TIME in a variable, which is insert in the PDD.

WR_UDINT_BY_SYM Writes a value of the type UDINT in a variable, which is insert in the PDD.

WR_UINT_BY_SYM Writes a value of the type UINT in a variable, which is insert in the PDD.

WR_USINT_BY_SYM Writes a value of the type USINT in a variable, which is insert in the PDD.

WR_WORD_BY_SYM Writes a value of the type WORD in a variable, which is insert in the PDD.

WRITE_RETAIN Writes the remanent data in the memory.


142


18.2 DIOLINE 20 Module Types

Module Type Item Number

Bytes Input

Bytes Output

Current Consumption L-Bus

ID(hex)

8 Bit digital output 746415 0 1 90 mA F1

8 Bit digital output, 16 input diagnosis

746419746420746414746424

2 1 10 mA

125 mA125 mA

E3

16 Bit digital output 746401746412

0 2 10 mA E1

16 Bit digital input 746400746408746413746417746425

2 0 10 mA E0

8 Bit digital output and 8 Bit dgital input

746402 1 1 10 mA E2

Spacer 746418 1 0 10 mA F0

4 channel 16 Bit analog input

746403746404746410746411746421

8 0 50 mA 70

4 channel 16 Bit analog output

746405746406746422

0 8 150 mA 71

2 channel 16 Bit temperature output

746407 4 4 200 mA 76

143


18.3 Autoexec.bat Commands

Command Description

copy2sd filename The entered file is copied from the PLC to the SD card.

copy2plc filename The entered file is copied from the SD card to the PLC.

fwupdate flash.updchecksum.upd

The firmware is used for the flashing.

reset The PLC will be restarted after processing the entered commands.

Mkdirplc port_0 Creating a folder on the PLC.

copy2sd port_0\config.dbm Copying the the CANopen configuration file to the SD Card.

copy2plc port_0\config.dbm Copying the CANopen configuration to the PLC.

144

DIOLINE PLC ▪ Revision of the Document

145

19 Revision of the Document

Version Revision Date

1.00 Release of the Document 06/14/2012

02 ▪ Change of version numbering

▪ Update chapter Software Maintenance

12/17/2012

03 Correction of LED color for the function block IKS Monitor Digital

05/17/2016

DIOLINE PLC ▪ Glossar

GlossarAdd-onA module which supplements Hardware or Software. in contrast to Plug-in, existing libraries are used and functions are programmed.

ARM short form for Advanced risk machine. A micro processor.

API short form for Application Programming Interface. Programming Interface part of a program which is provided by the software system for the connection to the system.

ARP short form for Address Resolution Protocol.A network protocol. Determines the physical address (Hardware address) of the net entry layer.

ASCIIAmerican Standard Code for Information Interchange A 7 bit character code. The code defines 128 characters. 33 not printable and 95 printable characters. The printable characters consist of the Latin alphabet with big and small letters, 10 Arabic numbers, punctuation marks and control characters.

Baudrate, BaudUnit for the line digit rate for communication engineering. One baud is the speed of the transfer of one symbol per second. Every symbol equates a measurable signal change in the physical transmitting medium. The baudrate has to be the same on the transmitting and receiving end.The transmission speed of the data is number of bits per second (for example:10 KBits/s).

Big-EndianThe Byte with the highest bit is saved first. Data with the highest value are

named first. For example: hour:minute:second

CAN short form for Controller Area

Network.A asynchrony serial bus system which works according the CSMAICR (Carriers Sense Multiple Access/Collision Resolution) system.

CFG short form for Configuration. The setting of program and hardware parts for the system.

COB-ID short form for Object ldentifier. The ID consist of 32 Bit values. The first two bits are object specific.

CPU short form for Central Processing Unit.The CPU is the main processor.

CV short form for Check Variable.

DeviceNetLayer -7-Communicationprotocol based on CAN.

DriverA computer program or module which control the communication of the connected devices. The drivers uses a communication bus which is connected to the device. lt can transmit or receiving control data to the device or from the device. A communication between the operating system and the devices is possible.

EPROM short form for Erasable Programmable Read-Only-Memory. Memory which only allows the reading of data. The memory will be programmed before using in the device. The memory can be deleted by UV-Light After it is possible to rewrite the memory again. The lifetime cycle of the EPROM is 100 till 200 deletes.

146


Flash Memory see EPROM

FW short form for Firmware.An integrated software in electronic devices. Most of the time the software is saved on a flash memory. The firmware is connected to the hardware. The firmware is in-between the soft-and hardware. The operation software of a device or component is also called firmware.

Hot Plugging or Hot Swapping. Change of a system component or module during the runtime. The tem "hot swapping" is used according to components which are not working with software.

lnstantiationCreating of an object in a class of the object orientated programming.

IRQ short form for interrupt.A interception of the program to process something.

Little-EndianThe byte with the lowest bits is saved first the smallest value is named first. For example: Day.Month.Year

MVB short form for Multifunctional Vehicle Bus. A fieldbus which is used in railway vehicles. lt is part of the TCN (Train communication Network).

Network protocolAgreement after which data are exchanged between computers and processes which are in the same net.

Node-IDTo address the devices on the bus. Has to be distinct. The number cannot be assigned twice.

OPC short form for OLE for Process Control (Object Linking and

Embedding).Originally the name of a standardized software interface. Data exchange between applications in the field of automation engineering.

OSI-Layer Model short form for Open System lnterconnection Reference Model.ls used as a design basic forcommunication protocols in networks.

ParityNumber of Bits with a one in the information word. A parity control notices wrong transmitted information words ( a sequence of Bits). A parity bit is a control bit with a data ward.

PDO short form for Process Data Object Object of the CAN-Communication. With this objects process data using data are sent.

PingA diagnosis tool. Proofs the availability of a hast in the IP-Network. Same implements can also show the time between the receiving and transmitting data package.

PLC short form for Programmable Logic Controller.

POU short form for Program Organisation Unit. Element of a IEC61131-3 PLC-Program. Independent software unit which contains programming code. The name of the POU has to be distinct.lt can just be used one in a project.

Remanent MarksThe contain of the marks will still exists after interrupting the voltage, for example.

SAEJ1939Networkprotocolfor transmitting diagnosis data (for example temperature, rotational frequencyetc.)

147


and control information.

SDO short form for Service Data Object. Objects of the CAN communication. Protocol data are sent with this objects. STS short form for Sink Time Supervision

SYCON.NetA field device Tool (FOT) or device type manager (DTM).

TCN short form for Train Communication Network.A system of two field busses which are special developed for railway vehicles to replace the analog remote control and to collect the single operation states of the single vehicles.

TCP/IP short form for Transmission Control Protocol/lnternet Protocol. A family of network protocols. The identifiying of the PLCs which are in the network is done over the IP address.

Watchdog also called WDC (Watch Dog Counter).A component of a system which monitors other components. ls usually used in micro controller to avoid a breakdown causes by a software failure.

WTB short form for Wire Train Bus.The WTB is a fieldbus. The WTB and the MVB are the TCN. The fieldbus is used for the communication between the single railway vehicles.

148

DIOLINE PLC 746033 · 2018-04-03 · DIOLINE PLC Safety 8 3Safety 3.1 Content of the Manual Read...

Documents

Transcript of DIOLINE PLC 746033 · 2018-04-03 · DIOLINE PLC Safety 8 3Safety 3.1 Content of the Manual Read...