networkdesigner22 lin manual en

7/21/2019 NetworkDesigner22 LIN Manual En

1/72

User Manual

Network Designer LIN

Design of LIN Network Architecture

Version 2.2

English


2/72

Imprint

Vector Informatik GmbHIngersheimer Str. 24

D-70499 Stuttgart

The information and data given in this user manual can be changed without prior notice. No part of this manual may be reproduced inany form or by any means without the written permission of the publisher, regardless of which method or which instruments, electronicor mechanical, are used. All technical information, drafts, etc. are liable to law of copyright protection.

Copyright 2010, Vector Informatik GmbH. Printed in Germany.All rights reserved.80410


3/72

User Manual Network Designer LIN Table of contents

Vector Informatik GmbH Version 2.2 - I -

Table of contents

1 Introduction 3

1.1 Network Designer LIN at a glance 4

1.2 The Network Designer product family 6

1.3 Integration into Vector LIN tool chain 6

1.4 Aboutthis user manual 71.4.1 Certification 81.4.2 Warranty 81.4.3 Support 81.4.4 Registered trademarks 8

2 Installation 9

2.1

General 10

2.2 Additional program documentation 11

2.3 Suggestions, comments, criticism, and troubleshooting 11

3 Basics 13

3.1 Functionality 14

3.2 Designing networked ECU systems 14

3.3 Example of a design for a networked ECU system 17

4 Usage 23

4.1

Starting and ending the program 24

4.2 Structure of the main window 24

4.3 Working with Network Designer 25

4.4 Opening and saving a workspace 26

4.5 Windows / editors 274.5.1 The Project Explorer 274.5.2 The Library Browser 284.5.3 The Network Explorer 294.5.4 Object List window 314.5.5 Gateway Routing window 314.5.6 Attribute Definition window 324.5.7 Consistency Check window 32

5 Concepts 35

5.1 Network Designer LIN object model 365.1.1 Hardware topology and communication objects 375.1.2 Relations between objects 37

5.2 User-defined attributes 38

5.3 Workspace 39

5.4 Defining the LIN timing 39

5.5 Exchanging data with other applications 40

6

Tutorial 41


4/72

Table of contents User Manual Network Designer LIN

- II - Version 2.2 Vector Informatik GmbH

6.1 Overview 42

6.2 Creating a new workspace 42

6.3 Creating vehicle projects and hardware topologies 43

6.4 Definition of global signals 48

6.5

Designing the network communication on a LIN bus 516.5.1 Defining the publishers of signals 51

6.5.2 Creating LIN frames and placing the signals 526.5.3 Defining the subscribers of signals 546.5.4 Defining the response error signals of slave nodes 54

6.6 Designing the LIN Schedule 55

6.7 Consistency Check 56

6.8 Exporting Data to an LDF File 57

6.9 Exporting Data to an NCF File 58

7 Appendix A: Glossary 59

7.1

Network Designer 59

7.2 Network Designer CAN 62

7.3 Network Designer LIN 62

7.4 Network Designer FlexRay 62

8 Appendix B: File name extensions 63

9 Appendix C: Keyboard operation 64

10 Appendix D: NetworkDesigner.ini configuration file 66

11

Appendix A: Addresses 67


5/72

User Manual Network Designer LIN Introduction

Vector Informatik GmbH Version 2.2 - 3 -

1 Introduction

In this chapter you find the following information:

1.1 Network Designer LIN at a glance page 4

1.2 The Network Designer product family page 6

1.3 Integration into Vector LIN tool chain page 6

1.4 About this user manual page 7

Certification

Warranty

Support

Registered trademarks


6/72

Introduction User Manual Network Designer LIN

- 4 - Version 2.2 Vector Informatik GmbH

1.1 Network Designer LIN at a glance

Application areas Network Designer LIN is a tool for designing the network architecture andcommunication data for distributed ECU systems. This includes

> design of hardware topologies based on ECUs and networks> definition of signals and messages along with their transmitters and recipients, as

well as

> specification of message timings.

Organization of thedata

Data for multiple networks and vehicle projects are saved in one Network Designerworkspace.

The communication descriptions of individual LIN networks can be exported to andimported from LDF files. The exported LDF files can then be used in subsequentdevelopment steps, e.g., simulation, ECU software configuration and ECU testing.

The communication descriptions of individual LIN 2.x slave nodes can be exported to

and imported from NCF files.

Tool chain

Network Designeras central development tool for distributed ECU networks

User interface The user interface is designed for efficiency. The hardware topology and network

communication are shown hierarchically. Data can be entered either directly intoobject lists or via dialogs. Communication relations can be created using drag & dropor via the menu.


7/72




8/72



1.2 The Network Designer product family

Product familycomponents

The Network Designerproduct family consists of the following products:

> Network Designer CAN

> Network Designer LIN

> Network Designer FlexRay

Integrated use ofprograms

Individual members of the product family can be used on a standalone or anintegrated basis. For integrated use, the individual Network Designercomponentsmust be installed in the same program folder (e.g. C:\Program Files\Network

Designer). The installation program will show a warning message if an attempt is

made to install an incompatible Network Designerversion in an existing programfolder.

Advantages of

integrated use

Integrated use of compatible Network Designer versions confers the following

advantages:

> Management of all supported bus systems using one unified interface

> Simultaneous management of networks on all supported bus systems

> Ability to define and visualize signals, which can be routed via gateways. Routedsignals are recognized automatically on several buses because an identical signalis used.

1.3 Integration into Vector LIN tool chain

Interaction betweenthe programs Network Designer LINis the central tool in Vector LIN tool chains such as CANoe.LINas well as in CANbedded LIN software components.

Communication data is defined, modified and managed in Network Designer LIN, andthe Vector LIN tools have read-only access to that data.Communication data isexchanged between tools in the form of LDF / NCF files (*.ldf / *.ncf) for this purpose.

Data export Network Designer LINprovides several functions to export the LIN data contained ina workspace. The data of a whole LIN network is exported to an LDF file while thedata of a single slave node is exported to an NCF file.


9/72



1.4 About this user manual

The user manual provides you the following access helps: To find informationquickly

> At the beginning of each chapter you will find a summary of the contents,> In the header you can see in which chapter and paragraph you are ((situated)),

> In the footer you can see to which version the user manual replies,

> At the end of the user manual you will find an index, with whose help you willquickly find information.

In the two following charts you will find the conventions used in the user manualregarding utilized spellings and symbols.

Conventions

Style Utilization

bold Blocks, surface elements, window- and dialog names of the

software. Accentuation of warnings and advices.[OK] Push buttons in brackets

File|Save Notation for menus and menu entries

Network Designer Legally protected proper names and side notes.

Source code File name and source code.

Hyperlink Hyperlinks and references.

+ Notation for shortcuts.

Symbol Utilization

Here you can obtain supplemental information.

This symbol calls your attention to warnings.

Here you can find additional information.

Here is an example that has been prepared for you.

Step-by-step instructions provide assistance at these points.

Instructions on editing files are found at these points.

This symbol warns you not to edit the specified file.


10/72



1.4.1 Certification

Certified QualityManagement System

Vector Informatik GmbH has ISO 9001:2008 certification. The ISO standard is aglobally recognized quality standard.

1.4.2 Warranty

Restriction ofwarranty

We reserve the right to change the contents of the documentation and the softwarewithout notice. Vector Informatik GmbH assumes no liability for correct contents ordamages which are resulted from the usage of the user manual. We are grateful forreferences to mistakes or for suggestions for improvement to be able to offer youeven more efficient products in the future.

1.4.3 Support

You need support? You can get through to our hotline at the phone number

+49 (711) 80670-200

or you send a problem report to the CANoe Support.

1.4.4 Registered trademarks

Registeredtrademarks

All trademarks mentioned in this user manual and if necessary third party registeredare absolutely subject to the conditions of each valid label right and the rights ofparticular registered proprietor. All trademarks, trade names or company names areor can be trademarks or registered trademarks of their particular proprietors. All rightswhich are not expressly allowed are reserved. If an explicit label of trademarks, whichare used in this user manual, fails, should not mean that a name is free of third partyrights.

> Outlook, Windows, Windows XP, Windows 2000, Windows NTare trademarks ofthe Microsoft Corporation.

> Network Designeris a trademarks of Vector Informatik GmbH.

> eclipseis subject to the Copyright of the Eclipse contributors and others.
http://www.vector-informatik.de/english/support/report.phphttp://www.vector-informatik.de/english/support/report.php


11/72

User Manual Network Designer LIN Installation


2 Installation


2.1 General page 10

2.2 Additional program documentation page 11

2.3 Suggestions, comments, criticism, and troubleshooting page 11


12/72

Installation User Manual Network Designer LIN


2.1 General

Info:The software installation requires administrator rights!

Network Designer has a product activation feature that links the software license tospecific computer hardware. Unless activated Network Designercan't be started.

Please see documentation "NetworkDesigner_ProductActivation.pdf" available on theinstallation CD.

System requirements > Pentium II processor, 300 MHz (minimum)

> 128 MB RAM (minimum)

> About 130 MB hard disk space

> Windows 2000, Windows XP, Windows Vistaor Windows 7as operating system.The installation procedure is identical for all Windowsversions.

Take the following steps to install Network Designer LINon your computer:

1. Insert the installation CD into your computers CD drive.

The Network DesignerLINsetup program will appear.

2. If the setup program does not appear automatically, open Windows Explorer andswitch to the CD drive.

3. Open the NetworkDesignerfolder and start Setup.exeby double-clicking thecorresponding icon.

4. Follow the setup program instructions.

Once the installation is complete, use the new icon that appears on your desktop

to start the program.The programs installation folder contains the files and folders shown in the tablebelow:

Info:In order for users other than the user who initially installed the program to workwith Network Designer LIN, those users must have rights that enable them to modifythe NetworkDesigner.ini file. You can administer the user rights in the propertydialog of that file. The user who installs the program should do this immediately afterthe installation.


13/72

User Manual Network Designer LIN Installation


2.2 Additional program documentation

Network Designer LINincludes a comprehensive online help that can be accessedvia the Helpmenu, the [Help]button or the key.

Online help

The following supplemental information is available via the Network DesignerDocumentation Browser and in the Docs folder:

Documentationbrowser

> Application Notes

> Release Notes

> User Documentation

You can open the Documentation Browser by selecting Vector Network Designer|Documentation Browserfrom the Windows Startmenu or via the main menu itemHelp| Documentation Browser.

2.3 Suggestions, comments, criticism, and troubleshooting

Vector is dedicated to making its products as user-friendly and robust as possible. Tohelp us achieve this goal, please send us your comments, suggestions, andcriticisms.

Please contact us

Should you experience problems or errors when running the program, please send usa description of the problem or error in as much detail as possible.

Please send an email with the following information to [email protected]: Email contact

> Program version including build number(e.g. Network Designer LIN1.0.44).

> Detailed description of the error, including, if possible, the information shown inthe Assertiondialog, such as file name, line, and expression.

> The operating system used with the program.

> If you have a suggestion for improvements, please send us a detailed descriptionof the desired functionality along with relevant use cases.We welcome all suggestions for improving our programs.

Please provide thefollowing information
mailto:[email protected]?subject=DaVinci%20Network%20Designer%20|%20Support%20Requestmailto:[email protected]?subject=DaVinci%20Network%20Designer%20|%20Support%20Request


14/72


15/72

User Manual Network Designer LIN Basics


3 Basics


3.1 Functionality page 14

3.2 Designing networked ECU systems page 14

3.3 Example of a design for a networked ECU system page 17


16/72

Basics User Manual Network Designer LIN


3.1 Functionality

Range of functions Network Designer LINhas the following functions:

> Creation of Network Designerworkspaces

> Display of the vehicle topology and network communication in hierarchical viewsas well as in object lists

> Creation and modification of objects that describe the topology (ECU, network)and the network communication (messages, frames and signals) in object lists andvia property dialogs

> Definition of global signals for use in different network and vehicle projects

> Copying of objects, including between vehicle projects in a workspace

> Entry of object parameters directly into object lists or via dialogs

> Specification of the messages, frames and signals sent and received by an ECUon a particular network

> Mapping of signals to messages and modification of message layouts via agraphical interface

> Specification of timing requirements of LIN frames

> Use of signal types to create uniform descriptions of signal parameters for multiplesignals as well as to define value codes

> Definition of user-defined (custom) attributes that enable targeted extension of thedata model

> Comprehensive consistency checks of relations across networks and bus system-specific properties

> Import of LIN communication descriptions from LDF files

> Export of communication data from a given LIN network to an LDF file

> Import of LIN slave node communication descriptions from NCF files

> Export communication data from a given LIN 2.x slave node to an NCF file

> Interactive creation of LIN Schedule Tables

> Initial generation of a LIN schedule using the LIN frame timing requirements

> Comprehensive online help

> Simultaneous working on design data by several users (multi-user support)

3.2 Designing networked ECU systems

Overview This chapter contains a brief introduction to designing a network architecture for adistributed ECU and the data communication on individual networks.

Vehicle projects Work inNetwork Designer LIN is based on vehicle projects.

In a vehicle project, you define the vehicle topology, which consists of ECUs andnetworks, as well as communication descriptions and their relations for the individualnetworks.

Vehicle hardwaretopology

ECUs realize specific behaviors via their software, and can exchange data on thenetworks they are connected to. Such a connection is called a network node.


17/72



An ECU can be connected to several networks via one network node respectively.Such ECUs constitute gatewaysbetween networks.

Signals are routed from one network (source network) to another network (destinationnetwork) via gateways.

Vehicle topology with 2 CAN buses, one LIN bus and one FlexRay bus.

The data exchanged between individual ECUs on networks is described by means ofglobal signals.

Signals

These global signals can be used (referenced) in multiple vehicle projects andnetworks. The global nature of these signals makes it possible to create a signal poolfor use across several projects.

In a vehicle, signals are sent from one ECU on a network and received by otherECUs on that network. These transmission and reception relations are called Tx(transmit) and Rx (receive) relations.

In order to be transmitted on a network, signals must be placed (mapped) on frames.In a physical network, the frames are then transmitted using the network protocol.

Frames and framelayout

In a vehicle, signals are sent from one ECU on a network and received by otherECUs on that network. These transmission and reception relations are called publishand subscriberelations.

Transmission andreception relations

The exchange of data between ECUs is defined as follows: the ECU that makes thedata available sends it to the network in the form of signals. The ECU that requiresthe data receives the signals from the network.

Because signals on a real network are always transmitted using frames, frames must

also be taken into consideration when creating a comprehensive description of thecommunication relations.

In a LIN network the following communication relations exist:

Published signal The network node of the transmitting ECU sends the signalto the network.

Subscribed signal The network node of the receiving ECU receives the signalon a given frame from the network. The signal can also betransmitted as part a different frame on the network, in whichcase the ECU does not receive it.

Published frame The network node of the transmitting ECU sends the frame,including all of its mapped signals, to the network.


18/72



The subscribed framecommunication relation that is theoretically possible is notspecified because it can be derived from other communication relations. Thesubscribed framerelation can be derived from the fact that a signal that is mappedon a frame is received by the receiving ECU. The frame is then automaticallyrecognized as a subscribed frame.

Timing The messages and frames are transmitted on the bus according to a defined timing.The way this timing is defined depends on the bus system.

> In a CANnetwork, the messages can be transmitted cyclically with a specificcycle time, or sporadically.

> In a FlexRayor LINnetwork, the transmission behavior of the individual frames isdefined in schedule tables or in a schedule that is global to the cluster.

Workflow Because it is a complex task,Network Designer LINdivides designing a distributedECU network into smaller steps that are more easily controlled. Specific functions andediting modes are available for each of the steps described above.

Because of this division, you always concentrate on just one portion of the entire taskat any given point in time. The results obtained from one partial step aresupplemented by additional data in a subsequent step. You are not, however, forcedinto a rigid edit or work mode, because you can switch between individual steps atany time.

The Network Designer LINuser interface is split into sections that correspond to themain workflow steps: hardware topology, signal definition and network design.

Design workflow Development steps for designing a network architecture and the data communication:

Advantages You can define all communication-related objects with Network Designer LINandsave them in a Network Designerworkspace. This data is then re-used in subsequentdevelopment steps, such as the generation of software components for an ECU'sdata communications, definition of ECU tests and network analyses. This way ofworking has the advantage that you specify the data for all of the networksconsistently and simultaneously when you begin developing the distributed ECUnetwork, and then re-use it in subsequent development steps.


19/72



Development process for a distributed ECU system: V model

Network data is exported to widely-used, network-specific exchange formats (DBC,LDF and FIBEX) and can be used in many development tools.

Export

Network Designer LINis a system for describing external ECU communications onthe logical layer. Internal ECU parameters, internal states and ECU behaviors are notdescribed. Physical network property aspects, e.g., circuit lengths and cross-sections,are also not taken into consideration.

Communicationdescription

3.3 Example of a design for a networked ECU system

Example:A simple vehicle architecture using a LIN network in a vehicle doorconsists e.g. of a door control unit (DriverDoorModule) and an intelligent actuator forcontrolling the window lifter motor (WindowLifter). The two ECUs are connected toone another by a LIN bus (DriverDoor_LIN), and the door control unit is alsoconnected to the vehicles body CAN (Body_CAN). Both ECUs exchange data aboutwhich direction the window is supposed to move in, the current window position and aflag that displays anti-trap protection activity.


20/72



The vehicles hardware topology thus has the following schematic structure:Designing thehardware topology

In Network Designer LIN, the hardware topology for a vehicle project is defined in theProject Explorer. It would look like this in our example:

Defining globalsignals

The signals exchanged between the ECUs, along with the signal properties, aredefined in the table below:

Signal Value typeLength[bit]

Reso-lution

Value range Unit

WindowMotion unsigned 2 1 030: no motion1: up2: down3: reserved

WindowPosition unsigned 8 0.4 0100 %

CrushGuardActivity unsigned 1 1 010: inactive1: active


21/72



In Network Designer LIN, the signals are defined either in the Library Browser or inthe signal list:

When the window lift button in a car is pressed, the door ECU transmits the desireddirection of motion to the WindowLifterECU using the WindowMotionsignal. Thisrequest is initially transmitted on the CAN busand is received by the door ECU viathis bus. The WindowLifterECU transmits the current position of the window(WindowPosition) and the anti-trap protection activity (CrushGuardActivity) to the doorECU via the LIN bus.

Designing signal-oriented transmission

and receptionrelations

The transmission and reception relations between the ECUs and signals are definedin the Network Explorer:

In order to be transmitted on the LIN bus, signals must be placed (mapped) on LINframes.

Defining the framesand their properties

Frames, along with their characteristic properties such as the LIN ID and minimumand maximum cycle times, are therefore defined, and the signals mapped to the datafields of the respective frames.

Mapping signals toframes

The list below shows the messages to be defined, along with their LIN ID, the lengthof the respective data fields and the signals that are to be transmitted on the frames:


22/72



LIN frame LIN IDLength[byte]

Cycletimemin..max[ms]

PublisherMappedsignals

WindowSlave 0x1D 1 30120 DriverDoorModule WindowMotion

WindowMaster 0x1E 2 1050 WindowLifter CrushGuardActivity

WindowPosition

In addition to the application signals, each LIN slave sends a so-called ResponseError Signal, which it uses to indicate whether a protocol error was identified. Likethe other signals, this signal is defined and mapped to a frame sent by the slave.

In the Network Designer LIN, the definition of messages and message properties aswell as the mapping of signals to messages is carried out in the Network Explorer.

In the screenshot, the LIN frames are shown under Unconditional Framesin theobject hierarchy on the right. The list on the right shows the messages mapped to theselected frame. The frame properties can be defined in the opened dialog.

The Layout tab of the message properties dialog provides a visual representation ofthe data field layout of the frames. The position of individual signals can be modifiedinteractively here.


23/72



The last step in designing the communication is to define the scheduled transmissionbehavior of the LIN network. With LIN buses, this is done using Schedule Tables.

Designing scheduledtransmission

behavior

The sequence in which the individual frames are to be sent on the LIN bus and therespective pause before the next scheduled frame are specified in a Schedule Table.

Defining ScheduleTables

Several Schedule Tables - one per network operating mode - are usually defined in aLIN network.

In Network Designer LIN,you can create Schedule Tables in the Schedule Editorinteractively, or you can use the Schedule Table wizard to create them automaticallyusing specified minimum and maximum intervals.

Exporting the communication descriptions from a LIN network to an LDF file enablesthem to be used in a different tool.

Export to LDF files

The LDF format is the communication data exchange standard defined by the LINConsortium, and is supported by practically all LIN tools.

The export is based on a single network and contains descriptions of the networkproperties and the connected network nodes. The LDF file also contains all of theframes along with the signals mapped to them, their properties and the networksSchedule Table.

This data then becomes the basis for subsequent steps in the development of anetworked ECU system, e.g., code generation, configuration of embedded softwarecomponents, testing of individual ECUs, network analyses, etc.


24/72



Export to NCF files Exporting the communication descriptions of a LIN 2.x slave node to an NCF fileenables them to be used in subsequent development steps e.g. creating an LDF filebased on several NCF files.

The NCF format is the communication data exchange format standard for LIN 2.x

slave nodes defined by the LIN Consortium, and is supported by practically all LINtools.

The export is based on a single slave node and contains the node's properties as wellas all of the frames published and subscribed by the node along with the signalsmapped to them.

Designing gateways As illustrated above, Network Designer LINsupports not only the design of a singlenetwork, but also creation of the hardware topology of a gateway to other networks,e.g. to a CAN network.

Network Designer CANis required for defining communication relations on the CANbus. The WindowMotionsignal is received by the door ECU on the CAN bus and isthen routed to the LIN bus. The Network Designer CANNetwork Explorer is used to

define this reception relation on the CAN bus as well as the CAN message on whichthe signal is transmitted via the CAN bus.

The signals routed from the CAN bus to the LIN bus, and vice versa, are listed in theGateway Signals list.

> The Network Explorer for the CAN network is in the upper window. Thecommunication relations and the CAN network messages are defined here.

> The lower windowshows the list of gateway signals. Here, you can see that theCrushGuardActivityand WindowPositionsignals are routed from the LIN tothe CAN network, and that the WindowMotionsignal is routed from the CAN tothe LIN network.

The messages on which the signals are transmitted on the respective networks arealso shown here.


25/72

User Manual Network Designer LIN Usage


4 Usage


4.1 Starting and ending the program page 24

4.2 Structure of the main window page 24

4.3 Working with Network Designer page 25

4.4 Opening and saving a workspace page 26

4.5 Windows / editors page 27

The Project Explorer

The Library Browser

The Network Explorer

Object List windowGateway Routing window

Attribute Definition window

Consistency Check window


26/72

Usage User Manual Network Designer LIN


4.1 Starting and ending the program

Accessing NetworkDesigner

Once the program is installed, the Network Designericon will appear on yourdesktop.

You can now start the program via this icon or via the WindowsStartmenu.

> Double-click the icon on your desktop.Starting NetworkDesigner LIN

The program will start up with an empty workspace.

> Click [Start]in the Windows taskbar.Select Programs|Network Designer|Network Designerfrom the Startmenu.

The program will start up with an empty workspace.

> Open WindowsExplorer.Switch to the folder you saved your workspaces (NDWfiles) to.Double-click the NDWfile you wish to open.

The program will start up using the selected workspace.

> Select File|Exitfrom the main menu.Ending NetworkDesigner LIN > Click on in the programs title bar.

4.2 Structure of the main window

Structure/Areas

The main window is divided into several areas. The uppermost area contains a menuand toolbars for accessing various program functions, as is usual in Windows

programs. The status bar at the lower edge displays short notes and statusmessages.

Workspace,Project Explorer,Library Browser

When a workspace is open, a Project Explorer, a Library Browser, and an Outputwindow are visible. Although these windows are normally aligned in a defaultconfiguration, they can be moved about freely.

Dockable windows The Project Explorer, Library Browser und Output window are dockable windows.Drag & drop the windows to any edge of the main window to dock them.

The windows can be positioned outside of the main window. To prevent the windowsfrom docking to the edge of the main window, press the key while draggingthem.


27/72



Network Designermain window

The remaining surface of the main window is reserved for the various editors. Thefollowing editors are available inNetwork Designer:

Editors

> Network Explorer for supported bus system networks.

> Object List window for listing objects of the same type.

> Gateway Routing window for visualization of the signals that are routed from onenetwork to another via a gateway.

> Attribute Definition window for adding user-defined attributes to customize thedata model.

> Consistency Check window to display the results of a consistency check.Consistency checks can be carried out for individual networks or for entire vehicleprojects.

> Schedule Editors to display and create schedule tables in LIN networks and staticand dynamic schedules in FlexRay clusters.

You can open the individual editors via the main menu, the toolbar icons or theobject-specific shortcut menus.

4.3 Working with Network Designer

You can perform various operations either in Network Designersmain menuor viaobject-specific shortcut menus. The shortcut menusare menus that contain anumber of operations that can be performed specifically with the selected object. Theshortcut menus can also contain special commands that are not available via themain menu. To activate a shortcut menu, select an object in a tree or list view andthen press your right mouse key.

Main menu,shortcut menus

Dialogs are used to modify object properties or to select options for an operation thatis to be performed. Some of the dialogs consist of several dialog tabs; you can switch

between these using the tabs at the upper edge of the dialog.

Dialogs


28/72



Toolbars The standard toolbar provides quick access to Network Designerstandardoperations.

Usage of drag & drop You can drag individual objects from one window to another using drag & drop.

Keyboard operations You can call up many of the Network Designeroperations with your mouse as well asyour keyboard.

4.4 Opening and saving a workspace

Opening a NetworkDesigner workspace

1. Select File|Open Workspacefrom the main menu.

The dialog for selecting the workspace (NDW file) to be opened appears:

2. Select the file name of the desired document from the file list, or enter the nameof the file into the File namefield. The default file extension is NDW (NetworkDesigner Workspace).

3. Click the [Open] button.

Once the workspace is opened successfully, the Project Explorer and the LibraryBrowser are displayed along with any vehicle projects, signals, and signal typescontained in the workspace.

You can also open a Network Designerworkspace via the toolbar icon, via thekeyboard shortcut or by using drag & drop to drag a NDW file onto the mainwindow. The file list in the Filemenu shows the most recently opened workspaces.

1. Select File|Save Workspacefrom the main menu.Saving a NetworkDesigner workspace

If you are saving the document for the first time, a file dialog will now appear.

2. Enter the new name in the File namefield.

3. Click the [Save] button.

You can also save a Network Designerworkspace via the toolbar icon or with thekeyboard shortcut.


29/72



4.5 Windows / editors

Network Designercontains the following windows: Windows

Window / Editor Description

Project Explorer window Hierarchical representation of vehicle projects andassociated electronic control units (ECUs), networks,and network nodes.

Library Browser The Library Browser displays the projects, signals,signal types and signal groups of the workspace.

Network Explorer window Representation of the communication data of anetwork.

Object List window Tabular overview of all objects of an object type.

Gateway Routing window Overview of automatically detected gateway signals.

Attribute Definition window Overview of user-defined attributes. New user-defined attributes can be added and already existingattributes edited.

Consistency Check window Presents the results of the consistency check of aworkspace object and the associated relations.

Output window Lists system messages.

4.5.1 The Project Explorer

This window represents the vehicle projects and their hardware topologyhierarchically. Various operations to define a vehicles hardware topology can beexecuted from the object-specific shortcut menu or via drag & drop.

Overview

Screenshot


30/72



Description of theProject Explorer

The vehicle projects of the currently loaded workspace are displayed in the ProjectExplorer, as well as the respective electronic control units (ECUs), networks, andnetwork nodes for each vehicle project.

A network node that represents the link between an ECU and a network is displayed

once under its network and once under its ECU. So for network nodes no name canbe defined, the connected ECU/network is shown as the network node's name.

The shown network node (Network 1 = ECU 1)is created with the connection between ECU 1 and network 1.

The following basic operations can be performed in the Project Explorer:

> Create and delete vehicle projects, ECUs, and networks

> Link ECUs to networks or delete an existing ECU link to a network.

> Open the Network Explorer for a network.

The Network Explorer can be opened from the shortcut menu of a selectednetwork by double-clicking on a network or from the toolbar icon.

> Execute object-specific operations on vehicle projects, ECUs, networks, andnetwork nodes.

The various operations can be executed from the object-specific shortcut menusor via drag & drop.

4.5.2 The Library Browser

Overview The Library Browser displays the global network independent objects of theworkspace.

Workspace page The Workspacepage displays all objects currently available in the local workspace.These objects can be used to design the network architectures.


31/72



Screenshot

4.5.3 The Network Explorer

This window displays the communication data of a network.The view is divided vertically into

> a hierarchical overview of available object types and objects.The hierarchies show the links (relations) between the objects.

> a list of objects that are assigned to the selected object type or that are linkedwith the object.

Overview

Screenshot


32/72



Description of theNetwork Explorer

Depending on the object or object type selected in the left window, the following isdisplayed:

> A list of objectswith their names and attributes

> A list of linksbetween the objects.

The names of the linked base objects, the attributes of the link and also theattributes of the linked base objects are displayed.

If a concrete message is selected in the hierarchical view, for example, thesignals in the object list linked to this message (signals mapped to the message)are listed. The name of the linked signal, the name of the message, the positionof the signal in the data field of the message (startbit) and the attributes of thelinked signals (length, value type, etc.) are displayed in the columns.

Various attributes may be defined for objects of different object types or for linksbetween different object types. In this case, the total number of attributes is displayed.If there are no attributes for certain objects or links, a minus sign () is displayed.

If a concrete network node is selected in the object hierarchy, for example, thereception and transmission signals are displayed in the object list as mapped orunmapped signals. Since no position is defined within a frame for unmapped signals,a minus sign () is displayed in this column.

The values are displayed in the list in different colors. The colors have the followingmeanings:

> BlackValue of a displayed object or link. The value can be modified.

> Blue(for links only)Value of a linked base object.The value can be modified and the modification also affects the base object.

> GrayThe value cannot be modified.

The values of the user-defined attributes are also displayed on the right side of theNetwork Explorer. If there is an asterisk '*' after the attribute value, then the attribute

still has the default value defined in the attribute definition.

Info:

> If a new default value is assigned to the user-defined attribute, all object attributevalues followed by an asterisk '*' are automatically assigned the new default value.

> The asterisk is removed as soon as an object's attribute value is edited,irrespective of the assigned concrete value. If there is no asterisk, the attributevalue has been edited. An attribute value is also considered edited if it has beenassigned the concrete value that corresponds to the default value of the attribute.

> Use the Reset to Defaultfunction in the shortcut menu of the list or click on the[Reset]button on the Attributes register of the respective object dialog to reset theattribute value to the default. If the default value is entered as an attribute value, a

prompt is displayed whether the attribute should be reset to the default.


33/72



Additional information about the object or object type selected in the hierarchical viewis displayed in the status bar at the bottom of the Network Explorer.

Operations in theNetwork Explorer

> The Network Explorer can be opened from the shortcut menu of a network by

double-clicking on a network in the Project Exploreror from the toolbar icon .

> Press to launch the editing mode for individual object properties of theselected cell.

> The lists can be sorted by the entries of a specific column by clicking on thecolumn title.

> Individual columns can be hidden or shown by functions in the shortcut menu ofthe header row.

Tips & tricks

4.5.4 Object List window

This list window provides a tabular overview of all objects of an object type or all

objects that are linked to the selected object (e.g. all signals that are mapped to amessage).

The information displayed corresponds to the information of the object list in theNetwork Explorer.

The objects displayed can also be edited and new objects can be created in the listwindow similar to the procedure in the Network Explorer.

If a list window is open, it is automatically updated when any modification is made tothe object type or object displayed.

Overview

Screenshot

4.5.5 Gateway Routing window

Signals that are routed from one network to another are called gateway signals.Gateway signals are automatically recognized and displayed in Network Designer.The shortcut menu of a vehicle project or gateway ECU is used to open the GatewayRoutingwindow.

Overview


34/72



Screenshot

4.5.6 Attribute Definition window

Overview This window contains the list of user-defined attributes. New user-defined attributes

can be added and existing attributes can be edited here. Open the AttributeDefinitionswindow from the Viewmenu of the main menu or the toolbar icon .

Screenshot

Tips & tricks If 0has been entered for the Minimumand Maximumvalues, no range check of theattribute values of this attribute is performed. In this case, any value (of the selectedvalue type) can be entered for the default value.

4.5.7 Consistency Check window

Overview The results of checking the objects and their relations to each other for consistency

are displayed in the Consistency Checkwindow.The symbol at the start of the line represents the object status.

The consistency check can be performed for all workspace objects, individual vehicleprojects or networks. Vehicle projects and networks are checked for consistency fromthe object's shortcut menu.

Screenshot


35/72



> The object for which a result is displayed in the Consistency Checkwindow canbe edited directly using the Edit function from the shortcut menu.

> Detailed information about the status of the object is available in the NoteandExplanationcolumns of the table in the Consistency Checkwindow or theObject Statusdialog.

> The Configure Display...shortcut menu item opens the Settingsdialog toconfigure the list. This dialog is used to specify what information should bedisplayed in the Consistency Checkwindow.

Usage

> The number of messages in the Consistency Checkwindow is displayed in thewindow title for your information, e.g. '4 of 6 displayed'.

> If the Consistency Checkwindow is open, it is automatically updated when anydata is modified.

Tips & tricks


36/72


37/72

User Manual Network Designer LIN Concepts


5 Concepts

This chapter contains the following information:

5.1 Network Designer LIN object model page 36

Hardware topology and communication objects

Relations between objects

5.2 User-defined attributes page 38

5.3 Workspace page 39

5.4 Defining the LIN timing page 39

5.5 Exchanging data with other applications page 40


38/72

Concepts User Manual Network Designer LIN


5.1 Network Designer LIN object model

Overview Network Designer LIN is based on an object model designed specifically for networkarchitecture design and data communication.

The figure below shows a user-oriented view of this object model:

The object types and object connections within the object model are described next.The properties of the individual object types and object relations are explained in aseparate documentation that comes with the respective Network Designer LIN

version. You can open these documents with the Documentation Browser.


39/72



5.1.1 Hardware topology and communication objects

A vehicle project serves as a model of the distributed ECU network. A vehicle projectcontains ECUs and networks. A vehicle project can be saved as a global object that isindependent of other objects.

Vehicle project

An ECU realizes a specific behavior via its software. The ECU is always a part of avehicle project in Network Designerand is defined there locally.

ECU

Data (signals) is transmitted via a network. The data transmission takes place withthe help of frames. A network is always a part of a vehicle project in NetworkDesignerand is defined there locally.

Network

Network Designersupports networks for the following bus systems:

> CAN

> LIN

> FlexRay

A global signal is a value that is made available by one ECU and is required by otherECUs to perform a specific function. Signals are saved as global objects in NetworkDesigner, and are independent of other objects like vehicle projects or networks. Thispermits the creation of a signal pool that can be used across several vehicles.

Global signal

Frames transmit data in the form of signals on a network. Bus system-specificmessages and frames are transmitted on the different bus system networks.

Frame

Network Designersupports the following message types for the respective bussystems:

> CAN messages in standard and extended format

> LIN unconditional frames, LIN diagnostic frames, LIN event-triggered frames, andLIN sporadic frames

> FlexRay frames for transmission in the static and dynamic FlexRay schedulesegments.

A signal that is transmitted on a network is called a network signal. A network signalis automatically created when a signal is transmitted from an ECU to a specificnetwork or received from a network (Rx signal and Tx signal), or when a signal isplaced on (mapped to) a message (mapped signal). A network signal thus alwaysexists locally in a given network when the corresponding global signal is transmittedon this network.

Network signal

5.1.2 Relations between objects

Network nodesrepresent the connection between an ECU and a network. When theconnection is made, a network node is created automatically. Every network nodehas bus system-specific properties, e.g., the role of the ECU in a LIN network (LINmaster or LIN slave).A gateway ECUor a LIN multi master nodeis connected to several networks andthus has several network nodes.An ECUs data communication on a particular network is described via the networknodes. This is effected by the creation of the published signal and the subscribedsignal relations.

Network node


40/72



Published signal/Subscribed signal

These relations determine which values are exchanged between individual ECUs ona concrete LIN bus.

> The published signalrelation describes a signal that is sent from an ECU on aLIN bus. This relation can be defined by the user by creating of a link between aglobal signal and a network node.

> The subscribed signalrelation describes a signal received by an ECU form aLIN bus. This relation can be defined by the user by creating a link between amapped signal and a network node.

Published frame/Subscribed frame

A published framerepresents the relation between the transmitting node and aframe.

A subscribed framerepresents the relation between the receiving node and a frame.This relation is derived of a mapped signal to a node automatically and cant bedefined manually. A frame is subscribed by a node as soon as one of the signalsmapped on the frame is received by the node. A frame cannot be defined as ansubscribed frame in its entirety because it is important to define which of the signals

transmitted on the frame are actually needed by the ECU to perform its tasks.

Frame signal In order for a value to be transmitted on a network in the form of a signal, the signalmust be placed in a frame, either on its own or in most cases together with othersignals. A signal that is placed on a frame is called a frame signal.

The most important property of such a frame signal is its position in the data field ofthe frame. To prevent signal values from being misinterpreted, signals cannot beplaced on the same positions and cannot overlap one another.

5.2 User-defined attributes

Saving additionalinformation

Network Designer LINis based on the object model described above, as well as onthe properties of the individual object types. However, it is often necessary to addadditional properties to the pre-defined properties, e.g. if in a vehicle project, you wantto specify when the vehicle series began, or which editor is responsible for a givenECU. The Network Designerobject model can be customized using user-definedattributes. You can use these to save any amount of additional information for objectsand object relations.

Objects/Object types

User-defined attributes are available for

> Vehicle,

> Signal,

> ECU

object types.


41/72



Every user-defined attribute is described by means of an attribute definition. Thisdescribes the

> value type as well as the

> default value of the attribute

and independently of the value type, other attribute properties such as

> minimum,

> maximum,

> valid enumeration values (enum values) and

> maximum string length.

Attribute definitions

A specific attribute value can be defined for every object for whose object type a user-defined attribute exists. This can be done either in the objects properties dialog or inan object list. If an explicit value is not assigned to the object, the attribute defaultvalue is used as the value for that object. This is indicated by an asterisk * in theuser interface.

Default values

5.3 Workspace

Network Designer LINsaves data in a Network Designerworkspace. Such aworkspace consists of a Network Designerworkspace file (.NDW file) and a series offiles in which the individual objects are saved.

What is aworkspace?

The object files are saved to a data folder that has the same name as the NDW file ina pre-defined structure. All of the files in this pre-defined folder structure are alwaysrequired in order to forward a Network Designerworkspace or create a copy of it. Theworkspace can no longer be read if any of these files is deleted, renamed or moved

manually. To rename the workspace manually, it is necessary to rename both theNDW file and the associated data folder.

Folder structure

Because a Network Designerworkspace can contain an unlimited number of objects,it is possible to save several vehicle projects in one workspace.

Note:All tools of the Network Designerproduct family can be used with NetworkDesignerworkspaces. It is possible to work on a workspace with several tools. Whendoing so, it is important to save the workspace before switching tools and to refreshthe workspace in the newly activated tool.Use the keyboard shortcut in Network Designer to do this.

5.4 Defining the LIN timing

An important part of designing a LIN network is the definition of LIN Schedule Tables. LIN timing

The Schedule Tables are used to specify in which order and at which intervals theframes are transmitted on the network.

LIN Schedule Tables


42/72



5.5 Exchanging data with other applications

Data format Applications exchange LIN network communication data using the LDF or NCFformat. The LDF and NCF formats are standardized by the LIN Consortium and are

supported by all LIN development systems.

Network Designer LINoffers functions for importing and exporting data in the LDFand NCF format.

Network-orienteddata exchange

> Since LDF is a network-oriented format and the communication data describeexactly one network in one file, exports to and imports from LDF files areperformed on the basis of one individual network. When data for several networksis exported, a separate LDF file is created for each network.

Node-orientedexchange

> Network Designer LIN offers functions for importing and exporting data in the NCFformat. Since NCF is a node-oriented format, exports to and imports from NCFfiles are performed on the basis of one individual slave node.

FIBEX exchange

format

Network Designer LINoffers functionality for importing and exporting data in the

FIBEX format. All FIBEX versions officially released by ASAM (1.1.5, 1.2.0, 2.0.0) aresupported."


43/72

User Manual Network Designer LIN Tutorial


6 Tutorial

This chapter contains the following information:

6.1 Overview page 42

6.2 Creating a new workspace page 42

6.3 Creating vehicle projects and hardware topologies page 43

6.4 Definition of global signals page 48

6.5 Designing the network communication on a LIN bus page 51

Defining the publishers of signals

Creating LIN frames and placing the signals

Defining the subscribers of signals

Defining the response error signals of slave nodes

6.6 Designing the LIN Schedule page 55

6.7 Consistency Check page 56

6.8 Exporting Data to an LDF File page 57

6.9 Exporting Data to an NCF File page 58


44/72

Tutorial User Manual Network Designer LIN


6.1 Overview

Purpose The purpose of this tutorial is to familiarize you with the user interface concept andthe most important of the Network Designer LINfunctions.

At the beginning of each chapter are tasks that you can solve with the help of theexplanations that follow.The sign on the left identifies the tasks.

Setup of this tutorial > In this tutorial youll first create a workspace and a vehicle project with its networktopology.

> Then youll define global signals.

> After that youll design the network communication of the LIN network. There youdefine which ECU publishes the signal and you create the LIN frames and placethe signals on them.

> To complete the network description you will then define the transmissionbehavior of the frames and design the LIN schedule.

> Finally this tutorial describes further steps for checking the network design andexporting the communication data.

6.2 Creating a new workspace

Task:Create a new Network Designerworkspace with the name Tutorial.ndw in theLIN Datadirectory of your Network Designer LINinstallation.

1. Double click the application symbol on your desktop.

The program starts with an empty working area.

2. Click the following symbol in the toolbar: .

The New Workspacedialog opens.


45/72



3. Now enter the name of the workspace to be created: Tutorial.ndw

4. Press the [Save]button.

The new workspace is created.

6.3 Creating vehicle projects and hardware topologies

Task:Create a new vehicle project and a hardware topology with two LIN buses andseveral ECUs, of which one ECU is a gateway between the two LIN buses.

Creating a vehicle project

A vehicle consists of a number of ECUs and one or more networks. Vehicles mayalso be used to represent vehicle model series.

1. Right Click on Vehicle Projectsin the Project Explorer.


46/72



2. Select the New Vehicle Projectcommand.

The Vehicle Projectdialog opens.

3. Enter the name of the new vehicle project: Vector_Car

4. Press [OK]to save the new vehicle project.

The new vehicle project appears in the Project Explorer

and in the Library Browser:

Setting up a LIN bus

1. Right click on Vector_Carin the Project Explorer.

The vehicles shortcut menu opens.


47/72



2. Select the New LIN Networkcommand.

The Networkdialog opens.

3. Enter the name for the new network: DriverDoor_LIN.

4. Enter the baud rate: 19.2.

5. Enter the manufacturer: Vector.

6. Enter the protocol version number: 2.0.


48/72



7. Press [OK]to save the new LIN network.

The new network appears in the Project Explorer:

Creating three ECUs

1. Right click on ECUsin the Project Explorer.

The ECUs shortcut menu opens.

2. Select the New ECUcommand.

The ECUdialog opens.

3. Enter the name for the new ECU: DriverDoorModule .

4. Press [OK]to create the new ECU.

5. Repeat steps 1 to 4 for the following 2 ECUs: WindowLifterand DoorLock.

The three ECUs appear in the Project Explorer:

Adding the ECUs to the LIN bus

Method 1(focus on ECU)

1. Select Edit ECUin the shortcut menu of the DriverDoorModule ECU in theProject Explorer.

The ECUdialog opens.

2. Click on the Networkspage.

3. Press the [Add]button to select a network to which the ECU should beconnected.

The Choose Objectdialog opens.

4. Click on the DriverDoor_LINnetwork in the list field.

5. Press [OK]to connect the DriverDoorModule ECU to the DriverDoor_LIN network.

Youre back in the ECUdialog. The list now contains the CAN_Comfortnetwork.

6. Press [OK]to close the ECUdialog.


49/72



Method 2(focus on network)

1. Select Edit LIN Networkin the shortcut menu of the DriverDoor_LINnetworkin the Project Explorer.

The Networkdialog opens.

2. Click on the ECUspage.

The list field shows the WindowLifterECU which has already been connected.

3. Press the [Add]button to select the WindowLifterECU to which theDriverDoor_LINnetwork should be connected.

The Choose Objectdialog opens.

4. Click on the WindowLifterECU in the list field.

5. Press [OK]to connect the DriverDoor_LINnetwork to the WindowLifterECU.

Youre back in the Networkdialog. The list now contains the following ECUs:DriverDoorModule and WindowLifter.

6. Press [OK]to close the Networkdialog.

Method 3(drag & drop)

1. Left click on the DoorLockECU in the Project Explorer.

2. Keep the left mouse button pressed and drag the DoorLockECU on theDriverDoor_LINnetwork in the Project Explorer.

Finally all 3 ECUs are connected to the DriverDoor_LINnetwork.

Setting up a second CAN bus

1. Select the New CAN Networkcommand in the shortcut menu of theVector_Carvehicle project.

2. Enter the name for the new Network: Body_CAN.

3. Enter the Baud Rate: 125.

4. Enter the manufacturer: Vector.

5. Enter the NM type: Vector.

6. Press [OK]to save the new CAN network.


50/72



Connecting the DriverDoorModule ECU with the CAN bus

1. Left click on the Body_CANnetwork in the Project Explorer.

2. Keep the left mouse button pressed and drag the Body_CANnetwork on theDriverDoorModule ECU in the Project Explorer.

A Gateway is a special type of ECU, used to connect two or more networks with eachother. Gateway ECUs have a special symbol:

6.4 Definition of global signals

Task:Create a global signal to exchange values between ECUs on the buses.

Creating a global signal

1. Select the New Signalcommand from the shortcut menu of the Signalsfolderin the Library Browser.

The Signaldialog opens.

2. Enter the Nameof the signal: WindowPosition.

3. Enter the Lengthof the signal: 8 [bits].

Info:LIN signals larger than 16 bits are automatically exported as byte array signals.

4. Enter the Unitof the signal: %.

5. Select the Value Typeof the signal: Unsigned.

6. Set the Not Validfield to: 0.

7. Set the Use scalingoption to: checked.

8. Set the Factorfield to: 0.4.

9. Set the Offsetfield to: 0.

10. Set the Minimumfield to: 0.


51/72



11. Set the Maximumfield to: 100.

12. Set the Automatic min-max calculationoption to: unchecked.

13. Set the Signal Typeselector to: .

14. Press [OK]to save the new signal.

The new signal appears in the Signalsfolder in the Library Browser.

Copying the existing signal, renaming the signal and changing parameters

1. Select the Copycommand from the shortcut menu of the WindowPositionsignalin the Library Browser.

2. Select the Pastecommand from the shortcut menu of the Signalsfolder in theLibrary Browser.

The copied signal appears as WindowPosition_Copy_1 in the Signalsfolder ofthe Library Browser.

3. Select the Edit Signal...command from the shortcut menu of theWindowPosition_Copy_1 signal in the Library Browser.


4. Change the Nameof the signal to: DoorLockStatus.

5. Change the Signal properties:

> Signal Type:

> Length: 1

> Unit: -

> Value Type: Unsigned

> Set the Use scalingoption to unchecked.


52/72



6. Press [OK]to save the changes.

The changed signal appears as DoorLockStatusin the Signalsfolder of theLibrary Browser.

Copy the new DoorLockStatussignal and rename it to WindowLifterStatus. The

settings are identical.

Creating a signal type

A signal type defines the base properties of similar signals. If several signals with thesame length, value type, calculation rule, unit, minimum and maximum have to bedefined, these common properties can be defined by a signal type. The signalsthemselves then reference the common signal type.

1. Select New Signal Type...in the shortcut menu of the Signal Typesfolder in theLibrary Browser.

The Signal Typedialog opens.

Properties page 2. Enter the Namefor the new signal type: MoveWindow_SigType.3. Enter the length of the signal type: 2.

4. Enter the unit of the signal type: .

5. Select the value type of the signal type: Unsigned.

6. Set the Not Validfield to: 0.

7. Set the Use scalingoption to: .

8. Set the Factorfield to: 1.

9. Set the Offsetfield to: 0.

10. Set the Minimumfield to: 0.

11. Set the Automatic min-max calculationoption to: .

Value descriptionspage

12. Switch to the Value Descriptionspage.

13. Press [Add]to add a new value description.

14. Click in the description field of value 0x0and enter Not Active.

15. Create all four entries as shown in the following screenshot:


The new signal type appears in the Signal Typesfolder in the Library Browser.


53/72



Creating a signal that references the new signal type

1. Select the New Signalcommand from the shortcut menu of the Signalsfolderin the Library Browser.


2. Select the MoveWindow_SigTypesignal type from the Signal Typedrop-downlist.

The new signal automatically adopts the default settings of the selected signaltype.

3. Rename the new Signal to WindowPosition_Rear.


The new signal appears in the Signalsfolder in the Library Browser.

6.5 Designing the network communication on a LIN bus

The communication relations of a network are defined in the Network Explorerof thenetwork. The Open Network Explorerfunction from the shortcut menu of a networkor double-clicking on a network in the Project Exploreropens the NetworkExplorer.

Overview

6.5.1 Defining the publishers of signals

Task:Define a Tx relation between a signal and a node.

The WindowPositionsignal is defined by one of the following methods as beingpublished by the DriverDoorModule node:

> Drag & drop the WindowPositionsignal from the Library Browser, list ofglobal signalsor the list of network signalsto the Published Signalsfolder ofthe DriverDoorModule node in the Network Explorer.

> To add the WindowPositionsignal, use the [Add]function on the PublishedSignalspage of the Propertydialog of the DriverDoorModule node.

> Copy the WindowPositionsignal to the clipboard and execute the Insert Linkfunction from the shortcut menu of the Published Signalsfolder of the

DriverDoorModule node.

Info:After a signal has been defined as a published signal of a certain node it canalso be defined a subscribed signal of another node.


54/72



6.5.2 Creating LIN frames and placing the signals

Task:Create a LIN frame.

Frames can be created in the Network Exploreror Object Listwindow.

1. Use the New Unconditional Framefunction in the shortcut menu of thePublished Framesfolder of the DriverDoorModule node create a new frame.

After creating the frame, the frame's Propertiesdialog is immediately displayed,in which the frame is given a unique name. If no unique name is entered, thesystem automatically adds a sequential number.

2. Enter the nameof the message: DriverDoor_Window .

3. Enter the Frame ID: 0x0.

4. Set the Dynamicoption to: .

5. Enter the Lengthof the frame in bytes: 4.

6. Enter the Min. Periodof the frame in ms: .

7. Enter the Max. Periodof the frame in ms: .

8. Enter the Message ID: 0x0.

9. Press [OK]to confirm the entries and close the dialog.

Task:Map a signal within the data field of a frame.

Step 1: Mapping the WindowPosition signal to the DriverDoor_Window frame

So that a signal can be transmitted on a network from an ECU to other ECUs, it f irstmust be defined as a published signal then it has to be mapped to a frame. The datais transmitted by means of the frame. A signal that is mapped to a frame is called amapped signal. A mapped signal is always mapped to a specific, unique position inthe data field of the frame (see Step 2).

The WindowPositionsignal can be mapped to the DriverDoor_Window frame byone of the following methods:

> Within the Network Explorer: Drag & drop the WindowPositionsignal from thePublished Signalslist of the DriverDoorModule node to theDriverDoor_Window frame in the Published Frameslist of the

DriverDoorModule .

> To add the WindowPositionsignal, use the [Add]function on the Signalspage of the Propertydialog of the DriverDoor_Window frame.

> Copy the WindowPositionsignal to the clipboard and execute the Insert Linkfunction from the shortcut menu of the DriverDoor_Window frame.

Step 2: Positioning the signals within the DoorControl_Left message

A signal is always mapped to a certain position in the data field of a frame.The position of a signal can be defined or changed as follows:


55/72



> Enter the numeric position in the Propertiesdialog of the mappedWindowPositionsignal.

See Online Help for information on Intel and Motorola formats.

> Graphical formatting of the Datafield on the Layoutpage in the Properties

dialog of the DriverDoor_Window frame.The byte order (Intel/Motorola) and the display format of the start position isautomatically taken into account in this dialog.

Use the [Arrange]function to automatically arrange the signals.

The following arrangement criteria are taken into account:

> Signals with a length of 8 bit or less do not exceed any byte limit; signals witha length of 16 bit do not exceed any Word (2-byte) limit.

> Signals with a length of 8 bit or more are mapped to a byte limit.

> Small signals are mapped at the start of the data field.

> Packeting takes place as closely as possible.The mapping rules are selected in such a way to ensure the most efficient accessof the embedded software to the signals.

Arrangement criteria

Graphical signallayout


56/72



6.5.3 Defining the subscribers of signals

Task:Define the DoorLocknode as a subscriber of the DoorLockStatussignal.

The DoorLockStatussignal is defined by one of the following methods as beingsubscribed by the DoorLocknode:

> Open the Network Explorer, then drag & drop the DoorLockStatussignal fromthe Library Browser, list of global signalsor the list of network signalsto theSubscribed Signalsfolder of the DoorLocknode.

> To add the DoorLockStatussignal, use the [Add]function on the SubscribedSignalspage of the Propertydialog of the DoorLocknode.

> Copy the DoorLockStatussignal to the clipboard and execute the Insert Linkfunction from the shortcut menu of the Subscribed Signalsfolder of theDoorLocknode.

Info:Before a signal can be defined as a subscribed signal of a certain node it has tobe defined as a published signal of another node.

6.5.4 Defining the response error signals of slave nodes

Task:In addition to the application signals, each LIN slavesends a so-calledResponse Error Signal, which it uses to indicate whether a protocol error was

identified. Like the other signals, this signal is defined and mapped to a frame sent bythe slave.

1. Define the DoorLockStatussignal as published signal of the DoorLocknode(see chapter 6.5.1)

2. Open the DoorLockdialog with the Editshortcut menu of the DoorLocknodein the Network Explorer.

3. On the Propertiespage and select the category Status Management and selectvia []DoorLockStatusas Response Error signal.


57/72



4. Create the DoorLock_Statusframe in the Published Framesfolder of theDoorLocknode (see chapter 6.5.2).

Settings:

> Frame Id: 0x1

> Length: 8

> Min and Max: -

> Message Id: 0x1

5. Map the DoorLockStatussignal to the DoorLock_Statusframe (see chapter6.5.2).

6. Define the DoorLock_Statusframe as subscribed frame of theDriverDoorModule node via drag & drop the DoorLock_Statusframe to theSubscribed Framesfolder of the DriverDoorModule node.

Repeat these steps for the new signal WindowLifterStatuson the newWindowLifter_Status frame of the WindoLifternode.

The settings are identical to DoorLockStatussignal and DoorLock_Statusframe.

6.6 Designing the LIN Schedule

Task:Based on the created vehicle project and the designed network communicationof the DriverDoor_LINnetwork you will design the LIN schedule.

Set up a table with the NEW Table command:

1. Open the Network Explorer of the DriverDoor_LINnetwork.

2. Select the Edit schedule(s)command in the shortcut menu of theDriverDoor_LINnetwork.

The LIN Schedule Designerwindow opens.

3. Select the New Tablecommand in the shortcut menu of the empty ScheduleTablessection of the window.

A table with the name Table0is created and appears in the Schedule Tablessection of the window.

4. Select the Renamecommand in the shortcut menu of the table.5. Change the name to ApplicationTable.

6. Drag & drop the DoorLock_Statusframe to the ApplicationTable.

7. Drag & drop the DriverDoor_Window frame to the ApplicationTable .

8. Click in the Delaycolumn of the DriverDoor_Windowslot and change the valueto 10.


58/72



Set up a new table using the Table Wizard:

1. Select the New Table using Wizardcommand in the shortcut menu of theempty Schedule Tablessection of the window.

The Schedule Table Wizardopens.

2. Select the Master Reqdiagnostic frame and press the [>>]button to add it to theSelected frameslist.

3. Select the SlaveRespdiagnostic frame and press the [>>]button to add it to theSelected frameslist.

4. Click in the Req. Min.cell of the frames and change the Req. Min.time for bothframes to 10.

5. Change the Req. Max.time for both frames to 30.

6. Press [Next >].

The settings on the following page neednt be changed.

7. Press [Next >].

The resulting schedule table is shown.

8. Press [Finish]to close the wizard.

The new table appears as Table1in the list of schedule tables.

9. Select the Renamecommand in the shortcut menu of Table1and rename it toDiagnosticTable .

10. Press [OK]to close the LIN Schedule Designerwindow.

6.7 Consistency Check

Task:Perform a consistency check for a network.

In order to determine whether the objects of a vehicle project and their relations aremutually consistent, a consistency check can be performed with the NetworkDesigner.

1. Select the network on which to perform the consistency check.


59/72



2. Select the Consistency Checkcommand from the network's shortcut menu.

The result of the consistency check is displayed in a Consistency Checkwindow.

Task:Perform a consistency check for a vehicle project.

In order to determine whether the objects of a network and their relations are mutuallyconsistent, a consistency check can be performed with theNetwork Designer.

1. Select the vehicle project on which to perform the consistency check.

2. Select the Consistency Checkcommand from the network's shortcut menu.

The result of the consistency check is displayed in a Consistency Checkwindow.

Info:The consistency check for a vehicle project only extends to the networks of thevehicle project, whose type is supported by the Network Designervariants.

6.8 Exporting Data to an LDF File

Task:Export the communication data of the current workspace to an LDF file.

1. Select the network that you want to export into an LDF file.

2. From the network's shortcut menu, select Export to|LIN Descrition File

3. Select the storage location and enter the file name.

4. Click [OK]to automatically export the network into a LIN Description file (*.ldf).

Export to LINDescription File

dialog


60/72



Info:You can also export all networks of a vehicle project in a single operation.Select the vehicle project that contains the network you want to export and executethe Export to|LIN Description Filesshortcut menu item.

6.9 Exporting Data to an NCF File

Task:Export the communication data of one slave node to an NCF file.

1. In the network explorer select the slave node that you want to export into an NCFfile.

2. From the nodes shortcut menu, select Export to|NCF File.

3. Select the storage location and enter the file name.

4. Via appearing dialog select desired option(s) for export.

5. Click [OK]to automatically export the node into a Node Capability File (*.ncf).


61/72

User Manual Network Designer LIN Appendix A: Glossary


7 Appendix A: Glossary

7.1 Network Designer

Term Description

attribute definition Description of a user-defined attribute. The attribute definitionsspecify for which object type the attribute is defined and whichdefault value the attributes have.

communicationrelations

Set and structure of data exchanged between the ECUs of adistributed control system. This includes the messages,message layout (mapping of signals to the messages), as wellas the transmission and reception relations between thesignals or messages and the ECUs of a network.

data field or payload The area of a message on which signals are transmitted.default value of auser-definedattribute

Value used for a user-defined attribute, if no explicit value hasbeen defined for an object.

destination message Message transmitted by a gateway ECU and on which a routedsignal is transmitted.

destination network Network on which a gateway ECU transmits a routed signal.

dockable window Windows that can be docked on an edge of the main window.These windows are always fully visible when open.

ECUelectronic control

unit

Processing unit in a distributed vehicle network.

gateway ECU linked with at least two networks. A gateway can transmitsignals from a source network to a destination network (route).

gateway routing Routing of a network signal from one network (source network)to another network (destination network) via a gateway ECU.

gateway signal Network signal that is routed from a source network via agateway ECU to a destination network.

global object Object that can be created independently of other objects.Global objects can be stored in the repository in differentversions. In Network Designer, these are the vehicle projectsand global signals. There are local objects in contrast to global

objects.global signal See "Signal"

hardware topology Description of the structure of a distributed control system.Defines via which networks the ECUs of a vehicle are linked.

Library Browser Window that displays the project, signals, signal types andsignal groups of the workspace.

local object Object that is defined in the context of another object. InNetwork Designer, for example, networks are always definedwithin a vehicle project and messages within a network. Localobjects are always versioned as part of the global object towhich they belong.


62/72

Appendix A: Glossary User Manual Network Designer LIN


Term Description

mapped Rx signal Network signal that is received by an ECU on a specificmessage on a network.

mapped signal Network signal that is routed to a specific position on a

message or frame on the network.mapped Tx signal Network signal that is transmitted by an ECU on a specific

message on a network.

message or frame Communication units required for the exchange of signalvalues. The exchanged signals are mapped in the data field ofthe message. In addition, messages carry bus system-specificprotocol information (e.g. message header, identifier,checksums, etc.).

network Transmission medium used to exchange data betweendistributed ECUs. Data is transmitted on a network by meansof a defined protocol (CAN, FlexRay, LIN).

Network Explorer Window for defining the communication data of a network.Defines the transmission and reception relations betweensignals and nodes, as well as the messages of a network.

network node Object that represents an ECU connection to a network. Anetwork node can have its own properties that specificallydescribe the connection.

network signal A signal transmitted on a concrete network. A network signalreferences a global signal. A network signal has routing-specific properties, e.g. transmission type and byte order.

object Elementary units for defining a distributed control system.Objects are placed in a relation to describe connectionsbetween them.

object name orsymbolic identifier

Unique identifier of an object. This identifier is subject to certainrules, since it is used when communication data is further used(e.g. generating control unit code, defining tests, etc.).

object type In Network Designer, objects of different types are used todescribe the hardware topology and communication relations,e.g. networks, ECUs, messages or signals. The user has theoption of creating, editing and relating objects of these objecttypes.

output window Window for the output of program messages.

PDU A PDU is a design element usually used in FlexRay networks.It contains a set of signals that have a defined layout within thePDU. Moreover a PDU describes a timing behaviour in the

context of a sender node. PDUs can be assigned to FlexRayframes and network nodes as transmitted or received PDUs.

Project Explorer Window for displaying vehicle projects loaded in the workspaceand its networks and ECUs. The hardware topology of avehicle is edited in this window.

relation betweenobjects

There are certain relationships between objects for describingthe hardware topology and communication. For example, amessage is transmitted by an ECU to a network. Theserelationships are described by relations between the objects,e.g. the node Tx message) relation.


63/72

User Manual Network Designer LIN Appendix A: Glossary


Term Description

Rx message or Rxframe

Message or frame received by an ECU on a network.

Rx signal Network signal received by an E

networkdesigner22 lin manual en

Documents