User Manual
Network Designer LIN
Design of LIN Network Architecture
Version 2.2
English
Imprint
Vector Informatik GmbH
Ingersheimer 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 in
any form or by any means without the written permission of the publisher, regardless of which method or which instruments, electronic
or 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
User Manual Network Designer LIN
Table of contents
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
About this user manual
1.4.1
Certification
1.4.2
Warranty
1.4.3
Support
1.4.4
Registered trademarks
7
8
8
8
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
4.5.1
The Project Explorer
4.5.2
The Library Browser
4.5.3
The Network Explorer
4.5.4
Object List window
4.5.5
Gateway Routing window
4.5.6
Attribute Definition window
4.5.7
Consistency Check window
27
27
28
29
31
31
32
32
5
Concepts
35
5.1
Network Designer LIN object model
5.1.1
Hardware topology and communication objects
5.1.2
Relations between objects
36
37
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
© Vector Informatik GmbH
Version 2.2
-I-
Table of contents
User Manual Network Designer LIN
6.1
Overview
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
6.5.1
Defining the publishers of signals
6.5.2
Creating LIN frames and placing the signals
6.5.3
Defining the subscribers of signals
6.5.4
Defining the response error signals of slave nodes
51
51
52
54
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
- II -
42
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Introduction
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
Certification
Warranty
Support
Registered trademarks
page 7
© Vector Informatik GmbH
Version 2.2
-3-
Introduction
1.1
User Manual Network Designer LIN
Network Designer LIN at a glance
Application areas
Network Designer LIN is a tool for designing the network architecture and
communication 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 the
data
Data for multiple networks and vehicle projects are saved in one Network Designer
workspace.
The communication descriptions of individual LIN networks can be exported to and
imported from LDF files. The exported LDF files can then be used in subsequent
development 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 Designer as central development tool for distributed ECU networks
User interface
-4-
The user interface is designed for efficiency. The hardware topology and network
communication are shown hierarchically. Data can be entered either directly into
object lists or via dialogs. Communication relations can be created using drag & drop
or via the menu.
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
© Vector Informatik GmbH
Introduction
Version 2.2
-5-
Introduction
1.2
User Manual Network Designer LIN
The Network Designer product family
Product family
components
The Network Designer product family consists of the following products:
> Network Designer CAN
> Network Designer LIN
> Network Designer FlexRay
Integrated use of
programs
Individual members of the product family can be used on a standalone or an
integrated basis. For integrated use, the individual Network Designer components
must 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 Designer version in an existing program
folder.
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. Routed
signals are recognized automatically on several buses because an identical signal
is used.
1.3
Integration into Vector LIN tool chain
Interaction between
the programs
Network Designer LIN is the central tool in Vector LIN tool chains such as CANoe.LIN
as well as in CANbedded LIN software components.
Communication data is defined, modified and managed in Network Designer LIN, and
the Vector LIN tools have read-only access to that data. Communication data is
exchanged between tools in the form of LDF / NCF files (*.ldf / *.ncf) for this purpose.
Data export
-6-
Network Designer LIN provides several functions to export the LIN data contained in
a workspace. The data of a whole LIN network is exported to an LDF file while the
data of a single slave node is exported to an NCF file.
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
1.4
Introduction
About this user manual
The user manual provides you the following access helps:
To find information
quickly
> 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 will
quickly find information.
In the two following charts you will find the conventions used in the user manual
regarding utilized spellings and symbols.
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.
<STRG>+<S>
Notation for shortcuts.
Symbol
Utilization
Conventions
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.
© Vector Informatik GmbH
Version 2.2
-7-
Introduction
User Manual Network Designer LIN
1.4.1 Certification
Certified Quality
Vector Informatik GmbH has ISO 9001:2008 certification. The ISO standard is a
Management System globally recognized quality standard.
1.4.2 Warranty
Restriction of
warranty
We reserve the right to change the contents of the documentation and the software
without notice. Vector Informatik GmbH assumes no liability for correct contents or
damages which are resulted from the usage of the user manual. We are grateful for
references to mistakes or for suggestions for improvement to be able to offer you
even 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
Registered
trademarks
All trademarks mentioned in this user manual and if necessary third party registered
are absolutely subject to the conditions of each valid label right and the rights of
particular registered proprietor. All trademarks, trade names or company names are
or can be trademarks or registered trademarks of their particular proprietors. All rights
which are not expressly allowed are reserved. If an explicit label of trademarks, which
are used in this user manual, fails, should not mean that a name is free of third party
rights.
> Outlook, Windows, Windows XP, Windows 2000, Windows NT are trademarks of
the Microsoft Corporation.
> Network Designer is a trademarks of Vector Informatik GmbH.
> eclipse is subject to the Copyright of the Eclipse contributors and others.
-8-
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Installation
2 Installation
In this chapter you find the following information:
2.1
General
page 10
2.2
Additional program documentation
page 11
2.3
Suggestions, comments, criticism, and troubleshooting
page 11
© Vector Informatik GmbH
Version 2.2
-9-
Installation
2.1
User Manual Network Designer LIN
General
Info: The software installation requires administrator rights!
Network Designer has a product activation feature that links the software license to
specific computer hardware. Unless activated Network Designer can't be started.
Please see documentation "NetworkDesigner_ProductActivation.pdf" available on the
installation CD.
System requirements > Pentium II processor, 300 MHz (minimum)
> 128 MB RAM (minimum)
> About 130 MB hard disk space
> Windows 2000, Windows XP, Windows Vista or Windows 7 as operating system.
The installation procedure is identical for all Windows versions.
Take the following steps to install Network Designer LIN on your computer:
1. Insert the installation CD into your computer’s CD drive.
The Network Designer LIN setup program will appear.
2. If the setup program does not appear automatically, open Windows Explorer and
switch to the CD drive.
3. Open the NetworkDesigner folder and start Setup.exe by double-clicking the
corresponding 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 program’s installation folder contains the files and folders shown in the table
below:
Info: In order for users other than the user who initially installed the program to work
with Network Designer LIN, those users must have rights that enable them to modify
the “NetworkDesigner.ini” file. You can administer the user rights in the property
dialog of that file. The user who installs the program should do this immediately after
the installation.
- 10 -
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
2.2
Installation
Additional program documentation
Network Designer LIN includes a comprehensive online help that can be accessed
via the Help menu, the [Help] button or the <F1> key.
Online help
The following supplemental information is available via the Network Designer
Documentation Browser and in the Docs folder:
Documentation
browser
> Application Notes
> Release Notes
> User Documentation
You can open the Documentation Browser by selecting Vector Network Designer|
Documentation Browser from the Windows Start menu or via the main menu item
Help| Documentation Browser.
2.3
Suggestions, comments, criticism, and troubleshooting
Vector is dedicated to making its products as user-friendly and robust as possible. To
help us achieve this goal, please send us your comments, suggestions, and
criticisms.
Please contact us
Should you experience problems or errors when running the program, please send us
a description of the problem or error in as much detail as possible.
Please send an email with the following information to [email protected]:
>
Program version including build number
(e.g. Network Designer LIN 1.0.44).
>
Detailed description of the error, including, if possible, the information shown in
the Assertion dialog, 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 description
of the desired functionality along with relevant use cases.
We welcome all suggestions for improving our programs.
© Vector Informatik GmbH
Email contact
Please provide the
following information
Version 2.2
- 11 -
User Manual Network Designer LIN
Basics
3 Basics
In this chapter you find the following information:
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
© Vector Informatik GmbH
Version 2.2
- 13 -
Basics
3.1
User Manual Network Designer LIN
Functionality
Range of functions
Network Designer LIN has the following functions:
> Creation of Network Designer workspaces
> Display of the vehicle topology and network communication in hierarchical views
as 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 and
via 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 ECU
on a particular network
> Mapping of signals to messages and modification of message layouts via a
graphical interface
> Specification of timing requirements of LIN frames
> Use of signal types to create uniform descriptions of signal parameters for multiple
signals as well as to define value codes
> Definition of user-defined (custom) attributes that enable targeted extension of the
data model
> Comprehensive consistency checks of relations across networks and bus systemspecific 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 a
distributed ECU and the data communication on individual networks.
Vehicle projects
Work in Network Designer LIN is based on vehicle projects.
In a vehicle project, you define the vehicle topology, which consists of ECUs and
networks, as well as communication descriptions and their relations for the individual
networks.
Vehicle hardware
topology
- 14 -
ECUs realize specific behaviors via their software, and can exchange data on the
networks they are connected to. Such a connection is called a network node.
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Basics
An ECU can be connected to several networks via one network node respectively.
Such ECUs constitute gateways between networks.
Signals are routed from one network (source network) to another network (destination
network) 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 of
global signals.
Signals
These global signals can be used (referenced) in multiple vehicle projects and
networks. The global nature of these signals makes it possible to create a signal pool
for use across several projects.
In a vehicle, signals are sent from one ECU on a network and received by other
ECUs 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 frame
layout
In a vehicle, signals are sent from one ECU on a network and received by other
ECUs on that network. These transmission and reception relations are called publish
and subscribe relations.
Transmission and
reception relations
The exchange of data between ECUs is defined as follows: the ECU that makes the
data available sends it to the network in the form of signals. The ECU that requires
the 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 the
communication relations.
In a LIN network the following communication relations exist:
Published signal
The network node of the transmitting ECU sends the signal
to the network.
Subscribed signal
The network node of the receiving ECU receives the signal
on a given frame from the network. The signal can also be
transmitted as part a different frame on the network, in which
case 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.
© Vector Informatik GmbH
Version 2.2
- 15 -
Basics
User Manual Network Designer LIN
The subscribed frame communication relation that is theoretically possible is not
specified because it can be derived from other communication relations. The
subscribed frame relation can be derived from the fact that a signal that is mapped
on a frame is received by the receiving ECU. The frame is then automatically
recognized as a subscribed frame.
Timing
Workflow
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 CAN network, the messages can be transmitted cyclically with a specific
cycle time, or sporadically.
>
In a FlexRay or LIN network, the transmission behavior of the individual frames is
defined in schedule tables or in a schedule that is global to the cluster.
Because it is a complex task, Network Designer LIN divides designing a distributed
ECU network into smaller steps that are more easily controlled. Specific functions and
editing modes are available for each of the steps described above.
Because of this division, you always concentrate on just one portion of the entire task
at any given point in time. The results obtained from one partial step are
supplemented by additional data in a subsequent step. You are not, however, forced
into a rigid edit or work mode, because you can switch between individual steps at
any time.
The Network Designer LIN user interface is split into sections that correspond to the
main 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 LIN and
save them in a Network Designer workspace. This data is then re-used in subsequent
development steps, such as the generation of software components for an ECU's
data communications, definition of ECU tests and network analyses. This way of
working has the advantage that you specify the data for all of the networks
consistently and simultaneously when you begin developing the distributed ECU
network, and then re-use it in subsequent development steps.
- 16 -
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Basics
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.
Network Designer LIN is a system for describing external ECU communications on
the logical layer. Internal ECU parameters, internal states and ECU behaviors are not
described. Physical network property aspects, e.g., circuit lengths and cross-sections,
are also not taken into consideration.
3.3
Export
Communication
description
Example of a design for a networked ECU system
Example: A simple vehicle architecture using a LIN network in a vehicle door
consists e.g. of a door control unit (DriverDoorModule) and an intelligent actuator for
controlling the window lifter motor (WindowLifter). The two ECUs are connected to
one another by a LIN bus (DriverDoor_LIN), and the door control unit is also
connected to the vehicle’s body CAN (Body_CAN). Both ECUs exchange data about
which direction the window is supposed to move in, the current window position and a
flag that displays anti-trap protection activity.
© Vector Informatik GmbH
Version 2.2
- 17 -
Basics
Designing the
hardware topology
User Manual Network Designer LIN
The vehicle’s hardware topology thus has the following schematic structure:
In Network Designer LIN, the hardware topology for a vehicle project is defined in the
Project Explorer. It would look like this in our example:
Defining global
signals
- 18 -
The signals exchanged between the ECUs, along with the signal properties, are
defined in the table below:
Signal
Value type
Length
[bit]
Resolution
WindowMotion
unsigned
2
WindowPosition
unsigned
CrushGuardActivity
unsigned
Version 2.2
Value range
Unit
1
0…3
0: no motion
1: up
2: down
3: reserved
—
8
0.4
0…100
%
1
1
0…1
0: inactive
1: active
—
© Vector Informatik GmbH
User Manual Network Designer LIN
Basics
In Network Designer LIN, the signals are defined either in the Library Browser or in
the signal list:
When the window lift button in a car is pressed, the door ECU transmits the desired
Designing signaldirection of motion to the WindowLifter ECU using the WindowMotion signal. This
oriented transmission
and reception
request is initially transmitted on the CAN bus and is received by the door ECU via
relations
this bus. The WindowLifter ECU transmits the current position of the window
(WindowPosition) and the anti-trap protection activity (CrushGuardActivity) to the door
ECU via the LIN bus.
The transmission and reception relations between the ECUs and signals are defined
in the Network Explorer:
In order to be transmitted on the LIN bus, signals must be placed (mapped) on LIN
frames.
Frames, along with their characteristic properties such as the LIN ID and minimum
and maximum cycle times, are therefore defined, and the signals mapped to the data
fields of the respective frames.
Defining the frames
and their properties
Mapping signals to
frames
The list below shows the messages to be defined, along with their LIN ID, the length
of the respective data fields and the signals that are to be transmitted on the frames:
© Vector Informatik GmbH
Version 2.2
- 19 -
Basics
User Manual Network Designer LIN
Cycle
time
min..max
[ms]
Publisher
LIN frame
LIN ID
Length
[byte]
Mapped
signals
WindowSlave
0x1D
1
30…120
DriverDoorModule WindowMotion
WindowMaster
0x1E
2
10…50
WindowLifter
CrushGuardActivity
WindowPosition
In addition to the application signals, each LIN slave sends a so-called Response
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 by the slave.
In the Network Designer LIN, the definition of messages and message properties as
well as the mapping of signals to messages is carried out in the Network Explorer.
In the screenshot, the LIN frames are shown under Unconditional Frames in the
object hierarchy on the right. The list on the right shows the messages mapped to the
selected frame. The frame properties can be defined in the opened dialog.
The Layout tab of the message properties dialog provides a visual representation of
the data field layout of the frames. The position of individual signals can be modified
interactively here.
- 20 -
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Basics
The last step in designing the communication is to define the scheduled transmission
behavior of the LIN network. With LIN buses, this is done using Schedule Tables.
Designing scheduled
transmission
behavior
The sequence in which the individual frames are to be sent on the LIN bus and the
respective pause before the next scheduled frame are specified in a Schedule Table.
Defining Schedule
Tables
Several Schedule Tables - one per network operating mode - are usually defined in a
LIN network.
In Network Designer LIN, you can create Schedule Tables in the Schedule Editor
interactively, or you can use the Schedule Table wizard to create them automatically
using specified minimum and maximum intervals.
Exporting the communication descriptions from a LIN network to an LDF file enables
them to be used in a different tool.
Export to LDF files
The LDF format is the communication data exchange standard defined by the LIN
Consortium, and is supported by practically all LIN tools.
The export is based on a single network and contains descriptions of the network
properties and the connected network nodes. The LDF file also contains all of the
frames along with the signals mapped to them, their properties and the network’s
Schedule Table.
This data then becomes the basis for subsequent steps in the development of a
networked ECU system, e.g., code generation, configuration of embedded software
components, testing of individual ECUs, network analyses, etc.
© Vector Informatik GmbH
Version 2.2
- 21 -
Basics
Export to NCF files
User Manual Network Designer LIN
Exporting the communication descriptions of a LIN 2.x slave node to an NCF file
enables them to be used in subsequent development steps e.g. creating an LDF file
based 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 LIN
tools.
The export is based on a single slave node and contains the node's properties as well
as all of the frames published and subscribed by the node along with the signals
mapped to them.
Designing gateways
As illustrated above, Network Designer LIN supports not only the design of a single
network, but also creation of the hardware topology of a gateway to other networks,
e.g. to a CAN network.
Network Designer CAN is required for defining communication relations on the CAN
bus. The WindowMotion signal is received by the door ECU on the CAN bus and is
then routed to the LIN bus. The Network Designer CAN Network Explorer is used to
define this reception relation on the CAN bus as well as the CAN message on which
the signal is transmitted via the CAN bus.
The signals routed from the CAN bus to the LIN bus, and vice versa, are listed in the
Gateway Signals list.
>
The Network Explorer for the CAN network is in the upper window. The
communication relations and the CAN network messages are defined here.
>
The lower window shows the list of gateway signals. Here, you can see that the
CrushGuardActivity and WindowPosition signals are routed from the LIN to
the CAN network, and that the WindowMotion signal is routed from the CAN to
the LIN network.
The messages on which the signals are transmitted on the respective networks are
also shown here.
- 22 -
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Usage
4 Usage
In this chapter you find the following information:
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
The Project Explorer
The Library Browser
The Network Explorer
Object List window
Gateway Routing window
Attribute Definition window
Consistency Check window
page 27
© Vector Informatik GmbH
Version 2.2
- 23 -
Usage
4.1
User Manual Network Designer LIN
Starting and ending the program
Accessing Network
Designer
Once the program is installed, the Network Designer icon will appear on your
desktop.
You can now start the program via this icon or via the Windows Start menu.
Starting Network
Designer LIN
>
Double-click the
icon on your desktop.
The program will start up with an empty workspace.
>
Click [Start] in the Windows taskbar.
Select Programs|Network Designer|Network Designer from the Start menu.
The program will start up with an empty workspace.
>
Open Windows Explorer.
Switch to the folder you saved your workspaces (NDW files) to.
Double-click the NDW file you wish to open.
The program will start up using the selected workspace.
Ending Network
Designer LIN
4.2
>
Select File|Exit from the main menu.
>
Click on
in the program’s title bar.
Structure of the main window
Structure/
Areas
The main window is divided into several areas. The uppermost area contains a menu
and toolbars for accessing various program functions, as is usual in Windows
programs. The status bar at the lower edge displays short notes and status
messages.
Workspace,
Project Explorer,
Library Browser
When a workspace is open, a Project Explorer, a Library Browser, and an Output
window are visible. Although these windows are normally aligned in a default
configuration, 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 windows
from docking to the edge of the main window, press the <Ctrl> key while dragging
them.
- 24 -
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Usage
Network Designer
main window
The remaining surface of the main window is reserved for the various editors. The
following editors are available in Network Designer:
>
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 one
network to another via a gateway.
>
Attribute Definition window for adding user-defined attributes to customize the
data model.
>
Consistency Check window to display the results of a consistency check.
Consistency checks can be carried out for individual networks or for entire vehicle
projects.
>
Schedule Editors to display and create schedule tables in LIN networks and static
and dynamic schedules in FlexRay clusters.
Editors
You can open the individual editors via the main menu, the toolbar icons or the
object-specific shortcut menus.
4.3
Working with Network Designer
You can perform various operations either in Network Designer’s main menu or via
object-specific shortcut menus. The shortcut menus are menus that contain a
number of operations that can be performed specifically with the selected object. The
shortcut menus can also contain special commands that are not available via the
main menu. To activate a shortcut menu, select an object in a tree or list view and
then press your right mouse key.
Main menu,
shortcut menus
Dialogs are used to modify object properties or to select options for an operation that
is 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
© Vector Informatik GmbH
Version 2.2
- 25 -
Usage
User Manual Network Designer LIN
Toolbars
The standard toolbar provides quick access to Network Designer standard
operations.
Usage of drag & drop You can drag individual objects from one window to another using drag & drop.
Keyboard operations
4.4
You can call up many of the Network Designer operations with your mouse as well as
your keyboard.
Opening and saving a workspace
Opening a Network
Designer workspace
1. Select File|Open Workspace… from 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 name
of the file into the File name field. The default file extension is NDW (“Network
Designer Workspace”).
3. Click the [Open] button.
Once the workspace is opened successfully, the Project Explorer and the Library
Browser are displayed along with any vehicle projects, signals, and signal types
contained in the workspace.
toolbar icon, via the
You can also open a Network Designer workspace via the
<Ctrl-O> keyboard shortcut or by using drag & drop to drag a NDW file onto the main
window. The file list in the File menu shows the most recently opened workspaces.
Saving a Network
Designer workspace
1. Select File|Save Workspace… from the main menu.
If you are saving the document for the first time, a file dialog will now appear.
2. Enter the new name in the File name field.
3. Click the [Save] button.
You can also save a Network Designer workspace via the
<Ctrl-S> keyboard shortcut.
- 26 -
Version 2.2
toolbar icon or with the
© Vector Informatik GmbH
User Manual Network Designer LIN
4.5
Usage
Windows / editors
Network Designer contains the following windows:
Window / Editor
Description
Project Explorer window
Hierarchical representation of vehicle projects and
associated 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 a
network.
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 userdefined attributes can be added and already existing
attributes edited.
Consistency Check window
Presents the results of the consistency check of a
workspace object and the associated relations.
Output window
Lists system messages.
Windows
4.5.1 The Project Explorer
This window represents the vehicle projects and their hardware topology
hierarchically. Various operations to define a vehicle’s hardware topology can be
executed from the object-specific shortcut menu or via drag & drop.
Overview
Screenshot
© Vector Informatik GmbH
Version 2.2
- 27 -
Usage
Description of the
Project Explorer
User Manual Network Designer LIN
The vehicle projects of the currently loaded workspace are displayed in the Project
Explorer, as well as the respective electronic control units (ECUs), networks, and
network 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 can
be 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 selected
network by double-clicking on a network or from the toolbar icon.
>
Execute object-specific operations on vehicle projects, ECUs, networks, and
network nodes.
The various operations can be executed from the object-specific shortcut menus
or via drag & drop.
4.5.2 The Library Browser
Overview
The Library Browser displays the global network independent objects of the
workspace.
Workspace page
The Workspace page displays all objects currently available in the local workspace.
These objects can be used to design the network architectures.
- 28 -
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Usage
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 linked
with the object.
Overview
Screenshot
© Vector Informatik GmbH
Version 2.2
- 29 -
Usage
Description of the
Network Explorer
User Manual Network Designer LIN
Depending on the object or object type selected in the left window, the following is
displayed:
>
A list of objects with their names and attributes
>
A list of links between the objects.
The names of the linked base objects, the attributes of the link and also the
attributes of the linked base objects are displayed.
If a concrete message is selected in the hierarchical view, for example, the
signals 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 position
of the signal in the data field of the message (startbit) and the attributes of the
linked signals (length, value type, etc.) are displayed in the columns.
Various attributes may be defined for objects of different object types or for links
between 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, the
reception and transmission signals are displayed in the object list as mapped or
unmapped 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 following
meanings:
>
Black
Value 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.
>
Gray
The value cannot be modified.
The values of the user-defined attributes are also displayed on the right side of the
Network 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 attribute
values 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 attribute
value has been edited. An attribute value is also considered edited if it has been
assigned the concrete value that corresponds to the default value of the attribute.
> Use the Reset to Default function in the shortcut menu of the list or click on the
[Reset] button on the Attributes register of the respective object dialog to reset the
attribute 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.
- 30 -
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Usage
Additional information about the object or object type selected in the hierarchical view
is displayed in the status bar at the bottom of the Network Explorer.
>
The Network Explorer can be opened from the shortcut menu of a network by
double-clicking on a network in the Project Explorer or from the toolbar icon
>
Press <F2> to launch the editing mode for individual object properties of the
selected cell.
>
The lists can be sorted by the entries of a specific column by clicking on the
column title.
>
Individual columns can be hidden or shown by functions in the shortcut menu of
the header row.
Operations in the
Network Explorer
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 a
message).
Overview
The information displayed corresponds to the information of the object list in the
Network Explorer.
The objects displayed can also be edited and new objects can be created in the list
window similar to the procedure in the Network Explorer.
If a list window is open, it is automatically updated when any modification is made to
the object type or object displayed.
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 Gateway
Routing window.
© Vector Informatik GmbH
Version 2.2
Overview
- 31 -
Usage
User Manual Network Designer LIN
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 Attribute
Definitions window from the View menu of the main menu or the toolbar icon .
Screenshot
Tips & tricks
If 0 has been entered for the Minimum and Maximum values, no range check of the
attribute values of this attribute is performed. In this case, any value (of the selected
value 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 Check window.
The symbol at the start of the line represents the object status.
The consistency check can be performed for all workspace objects, individual vehicle
projects or networks. Vehicle projects and networks are checked for consistency from
the object's shortcut menu.
Screenshot
- 32 -
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Usage
>
The object for which a result is displayed in the Consistency Check window can
be edited directly using the Edit function from the shortcut menu.
>
Detailed information about the status of the object is available in the Note and
Explanation columns of the table in the Consistency Check window or the
Object Status dialog.
>
The Configure Display... shortcut menu item opens the Settings dialog to
configure the list. This dialog is used to specify what information should be
displayed in the Consistency Check window.
>
The number of messages in the Consistency Check window is displayed in the
window title for your information, e.g. '4 of 6 displayed'.
>
If the Consistency Check window is open, it is automatically updated when any
data is modified.
© Vector Informatik GmbH
Version 2.2
Usage
Tips & tricks
- 33 -
User Manual Network Designer LIN
Concepts
5 Concepts
This chapter contains the following information:
5.1
Network Designer LIN object model
Hardware topology and communication objects
Relations between objects
page 36
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
© Vector Informatik GmbH
Version 2.2
- 35 -
Concepts
5.1
User Manual Network Designer LIN
Network Designer LIN object model
Overview
Network Designer LIN is based on an object model designed specifically for network
architecture 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 a
separate documentation that comes with the respective Network Designer LIN
version. You can open these documents with the Documentation Browser.
- 36 -
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Concepts
5.1.1 Hardware topology and communication objects
A vehicle project serves as a model of the distributed ECU network. A vehicle project
contains ECUs and networks. A vehicle project can be saved as a global object that is
independent of other objects.
Vehicle project
An ECU realizes a specific behavior via its software. The ECU is always a part of a
vehicle project in Network Designer and is defined there locally.
ECU
Data (signals) is transmitted via a network. The data transmission takes place with
the help of frames. A network is always a part of a vehicle project in Network
Designer and is defined there locally.
Network
Network Designer supports 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 other
ECUs to perform a specific function. Signals are saved as global objects in Network
Designer, and are independent of other objects like vehicle projects or networks. This
permits the creation of a signal pool that can be used across several vehicles.
Frames transmit data in the form of signals on a network. Bus system-specific
messages and frames are transmitted on the different bus system networks.
Global signal
Frame
Network Designer supports the following message types for the respective bus
systems:
>
CAN messages in standard and extended format
>
LIN unconditional frames, LIN diagnostic frames, LIN event-triggered frames, and
LIN sporadic frames
>
FlexRay frames for transmission in the static and dynamic FlexRay schedule
segments.
A signal that is transmitted on a network is called a network signal. A network signal
is automatically created when a signal is transmitted from an ECU to a specific
network or received from a network (Rx signal and Tx signal), or when a signal is
placed on (mapped to) a message (mapped signal). A network signal thus always
exists locally in a given network when the corresponding global signal is transmitted
on this network.
Network signal
5.1.2 Relations between objects
Network nodes represent the connection between an ECU and a network. When the
connection is made, a network node is created automatically. Every network node
has bus system-specific properties, e.g., the role of the ECU in a LIN network (LIN
master or LIN slave).
A gateway ECU or a LIN multi master node is connected to several networks and
thus has several network nodes.
An ECU’s data communication on a particular network is described via the network
nodes. This is effected by the creation of the published signal and the subscribed
signal relations.
© Vector Informatik GmbH
Version 2.2
Network node
- 37 -
Concepts
Published signal/
Subscribed signal
Published frame/
Subscribed frame
User Manual Network Designer LIN
These relations determine which values are exchanged between individual ECUs on
a concrete LIN bus.
>
The published signal relation describes a signal that is sent from an ECU on a
LIN bus. This relation can be defined by the user by creating of a link between a
global signal and a network node.
>
The subscribed signal relation describes a signal received by an ECU form a
LIN bus. This relation can be defined by the user by creating a link between a
mapped signal and a network node.
A published frame represents the relation between the transmitting node and a
frame.
A subscribed frame represents the relation between the receiving node and a frame.
This relation is derived of a mapped signal to a node automatically and can’t be
defined manually. A frame is subscribed by a node as soon as one of the signals
mapped on the frame is received by the node. A frame cannot be defined as an
subscribed 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 signal
must be placed in a frame, either on its own or in most cases together with other
signals. 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 of
the frame. To prevent signal values from being misinterpreted, signals cannot be
placed on the same positions and cannot overlap one another.
5.2
User-defined attributes
Saving additional
information
Network Designer LIN is based on the object model described above, as well as on
the properties of the individual object types. However, it is often necessary to add
additional properties to the pre-defined properties, e.g. if in a vehicle project, you want
to specify when the vehicle series began, or which editor is responsible for a given
ECU. The Network Designer object model can be customized using user-defined
attributes. You can use these to save any amount of additional information for objects
and object relations.
Objects/
Object types
User-defined attributes are available for
>
Vehicle,
>
Signal,
>
ECU
object types.
- 38 -
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Concepts
Every user-defined attribute is described by means of an attribute definition. This
describes the
>
value type as well as the
>
default value of the attribute
Attribute definitions
and independently of the value type, other attribute properties such as
>
minimum,
>
maximum,
>
valid enumeration values (“enum” values) and
>
maximum string length.
A specific attribute value can be defined for every object for whose object type a userdefined attribute exists. This can be done either in the object’s properties dialog or in
an object list. If an explicit value is not assigned to the object, the attribute default
value is used as the value for that object. This is indicated by an asterisk “*” in the
user interface.
5.3
Default values
Workspace
Network Designer LIN saves data in a Network Designer workspace. Such a
workspace consists of a Network Designer workspace file (.NDW file) and a series of
files in which the individual objects are saved.
The object files are saved to a data folder that has the same name as the NDW file in
a pre-defined structure. All of the files in this pre-defined folder structure are always
required in order to forward a Network Designer workspace or create a copy of it. The
workspace 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 the
NDW file and the associated data folder.
What is a
workspace?
Folder structure
Because a Network Designer workspace can contain an unlimited number of objects,
it is possible to save several vehicle projects in one workspace.
Note: All tools of the Network Designer product family can be used with Network
Designer workspaces. It is possible to work on a workspace with several tools. When
doing so, it is important to save the workspace before switching tools and to refresh
the workspace in the newly activated tool.
Use the <Ctrl-F5> 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.
The Schedule Tables are used to specify in which order and at which intervals the
frames are transmitted on the network.
© Vector Informatik GmbH
Version 2.2
LIN timing
LIN Schedule Tables
- 39 -
Concepts
5.5
User Manual Network Designer LIN
Exchanging data with other applications
Data format
Applications exchange LIN network communication data using the LDF or NCF
format. The LDF and NCF formats are standardized by the LIN Consortium and are
supported by all LIN development systems.
Network Designer LIN offers functions for importing and exporting data in the LDF
and NCF format.
Network-oriented
data exchange
> Since LDF is a network-oriented format and the communication data describe
exactly one network in one file, exports to and imports from LDF files are
performed on the basis of one individual network. When data for several networks
is exported, a separate LDF file is created for each network.
Node-oriented
exchange
> Network Designer LIN offers functions for importing and exporting data in the NCF
format. Since NCF is a node-oriented format, exports to and imports from NCF
files are performed on the basis of one individual slave node.
FIBEX exchange
format
Network Designer LIN offers 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) are
supported."
- 40 -
Version 2.2
© Vector Informatik GmbH
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
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
page 51
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
© Vector Informatik GmbH
Version 2.2
- 41 -
Tutorial
6.1
User Manual Network Designer LIN
Overview
Purpose
The purpose of this tutorial is to familiarize you with the user interface concept and
the most important of the Network Designer LIN functions.
At the beginning of each chapter are tasks that you can solve with the help of the
explanations that follow.
The sign on the left identifies the tasks.
Setup of this tutorial
6.2
>
In this tutorial you’ll first create a workspace and a vehicle project with its network
topology.
>
Then you’ll define global signals.
>
After that you’ll design the network communication of the LIN network. There you
define which ECU publishes the signal and you create the LIN frames and place
the signals on them.
>
To complete the network description you will then define the transmission
behavior of the frames and design the LIN schedule.
>
Finally this tutorial describes further steps for checking the network design and
exporting the communication data.
Creating a new workspace
Task: Create a new Network Designer workspace with the name “Tutorial.ndw” in the
LIN Data directory of your Network Designer LIN installation.
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 Workspace dialog opens.
- 42 -
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Tutorial
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 and
several 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 may
also be used to represent vehicle model series.
1. Right Click on Vehicle Projects in the Project Explorer.
© Vector Informatik GmbH
Version 2.2
- 43 -
Tutorial
User Manual Network Designer LIN
2. Select the New Vehicle Project… command.
The Vehicle Project dialog 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_Car in the Project Explorer.
The vehicles shortcut menu opens.
- 44 -
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Tutorial
2. Select the New LIN Network… command.
The Network dialog 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.
© Vector Informatik GmbH
Version 2.2
- 45 -
Tutorial
User Manual Network Designer LIN
7. Press [OK] to save the new LIN network.
The new network appears in the Project Explorer:
Creating three ECUs
1. Right click on ECUs in the Project Explorer.
The ECUs shortcut menu opens.
2. Select the New ECU… command.
The ECU dialog 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: WindowLifter and DoorLock.
The three ECUs appear in the Project Explorer:
Adding the ECUs to the LIN bus
Method 1 (focus on ECU)
1. Select Edit ECU… in the shortcut menu of the DriverDoorModule ECU in the
Project Explorer.
The ECU dialog opens.
2. Click on the Networks page.
3. Press the [Add…] button to select a network to which the ECU should be
connected.
The Choose Object dialog opens.
4. Click on the DriverDoor_LIN network in the list field.
5. Press [OK] to connect the DriverDoorModule ECU to the DriverDoor_LIN
network.
You’re back in the ECU dialog. The list now contains the CAN_Comfort network.
6. Press [OK] to close the ECU dialog.
- 46 -
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Tutorial
Method 2 (focus on network)
1. Select Edit LIN Network… in the shortcut menu of the DriverDoor_LIN network
in the Project Explorer.
The Network dialog opens.
2. Click on the ECUs page.
The list field shows the WindowLifter ECU which has already been connected.
3. Press the [Add…] button to select the WindowLifter ECU to which the
DriverDoor_LIN network should be connected.
The Choose Object dialog opens.
4. Click on the WindowLifter ECU in the list field.
5. Press [OK] to connect the DriverDoor_LIN network to the WindowLifter ECU.
You’re back in the Network dialog. The list now contains the following ECUs:
DriverDoorModule and WindowLifter.
6. Press [OK] to close the Network dialog.
Method 3 (drag & drop)
1. Left click on the DoorLock ECU in the Project Explorer.
2. Keep the left mouse button pressed and drag the DoorLock ECU on the
DriverDoor_LIN network in the Project Explorer.
Finally all 3 ECUs are connected to the DriverDoor_LIN network.
Setting up a second CAN bus
1. Select the New CAN Network… command in the shortcut menu of the
Vector_Car vehicle 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.
© Vector Informatik GmbH
Version 2.2
- 47 -
Tutorial
User Manual Network Designer LIN
Connecting the DriverDoorModule ECU with the CAN bus
1. Left click on the Body_CAN network in the Project Explorer.
2. Keep the left mouse button pressed and drag the Body_CAN network on the
DriverDoorModule ECU in the Project Explorer.
A Gateway is a special type of ECU, used to connect two or more networks with each
other. 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 Signal… command from the shortcut menu of the Signals folder
in the Library Browser.
The Signal dialog opens.
2. Enter the Name of the signal: WindowPosition.
3. Enter the Length of the signal: 8 [bits].
Info: LIN signals larger than 16 bits are automatically exported as byte array signals.
4. Enter the Unit of the signal: %.
5. Select the Value Type of the signal: Unsigned.
6. Set the Not Valid field to: 0.
7. Set the Use scaling option to: checked.
8. Set the Factor field to: 0.4.
9. Set the Offset field to: 0.
10. Set the Minimum field to: 0.
- 48 -
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Tutorial
11. Set the Maximum field to: 100.
12. Set the Automatic min-max calculation option to: unchecked.
13. Set the Signal Type selector to: <none>.
14. Press [OK] to save the new signal.
The new signal appears in the Signals folder in the Library Browser.
Copying the existing signal, renaming the signal and changing parameters
1. Select the Copy command from the shortcut menu of the WindowPosition signal
in the Library Browser.
2. Select the Paste command from the shortcut menu of the Signals folder in the
Library Browser.
The copied signal appears as WindowPosition_Copy_1 in the Signals folder of
the Library Browser.
3. Select the Edit Signal... command from the shortcut menu of the
WindowPosition_Copy_1 signal in the Library Browser.
The Signal dialog opens.
4. Change the Name of the signal to: DoorLockStatus.
5. Change the Signal properties:
> Signal Type: <none>
> Length: 1
> Unit: > Value Type: Unsigned
> Set the Use scaling option to unchecked.
© Vector Informatik GmbH
Version 2.2
- 49 -
Tutorial
User Manual Network Designer LIN
6. Press [OK] to save the changes.
The changed signal appears as DoorLockStatus in the Signals folder of the
Library Browser.
Copy the new DoorLockStatus signal 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 the
same length, value type, calculation rule, unit, minimum and maximum have to be
defined, these common properties can be defined by a signal type. The signals
themselves then reference the common signal type.
1. Select New Signal Type... in the shortcut menu of the Signal Types folder in the
Library Browser.
The Signal Type dialog opens.
Properties page
2. Enter the Name for the new signal type: MoveWindow_SigType.
3. Enter the length of the signal type: 2.
4. Enter the unit of the signal type: <empty>.
5. Select the value type of the signal type: Unsigned.
6. Set the Not Valid field to: 0.
7. Set the Use scaling option to: <checked>.
8. Set the Factor field to: 1.
9. Set the Offset field to: 0.
10. Set the Minimum field to: 0.
11. Set the Automatic min-max calculation option to: <checked>.
Value descriptions
page
12. Switch to the Value Descriptions page.
13. Press [Add] to add a new value description.
14. Click in the description field of value 0x0 and enter Not Active.
15. Create all four entries as shown in the following screenshot:
16. Press [OK] to save the changes.
The new signal type appears in the Signal Types folder in the Library Browser.
- 50 -
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Tutorial
Creating a signal that references the new signal type
1. Select the New Signal… command from the shortcut menu of the Signals folder
in the Library Browser.
The Signal dialog opens.
2. Select the MoveWindow_SigType signal type from the Signal Type drop-down
list.
The new signal automatically adopts the default settings of the selected signal
type.
3. Rename the new Signal to WindowPosition_Rear.
4. Press [OK] to save the changes.
The new signal appears in the Signals folder 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 Explorer of the
network. The Open Network Explorer function from the shortcut menu of a network
or double-clicking on a network in the Project Explorer opens the Network
Explorer.
Overview
6.5.1 Defining the publishers of signals
Task: Define a Tx relation between a signal and a node.
The WindowPosition signal is defined by one of the following methods as being
published by the DriverDoorModule node:
>
Drag & drop the WindowPosition signal from the Library Browser, list of
global signals or the list of network signals to the Published Signals folder of
the DriverDoorModule node in the Network Explorer.
>
To add the WindowPosition signal, use the [Add…] function on the Published
Signals page of the Property dialog of the DriverDoorModule node.
>
Copy the WindowPosition signal to the clipboard and execute the Insert Link
function from the shortcut menu of the Published Signals folder of the
DriverDoorModule node.
Info: After a signal has been defined as a published signal of a certain node it can
also be defined a subscribed signal of another node.
© Vector Informatik GmbH
Version 2.2
- 51 -
Tutorial
User Manual Network Designer LIN
6.5.2 Creating LIN frames and placing the signals
Task: Create a LIN frame.
Frames can be created in the Network Explorer or Object List window.
1. Use the New Unconditional Frame… function in the shortcut menu of the
Published Frames folder of the DriverDoorModule node create a new frame.
After creating the frame, the frame's Properties dialog is immediately displayed,
in which the frame is given a unique name. If no unique name is entered, the
system automatically adds a sequential number.
2. Enter the name of the message: DriverDoor_Window.
3. Enter the Frame ID: 0x0.
4. Set the Dynamic option to: <unchecked>.
5. Enter the Length of the frame in bytes: 4.
6. Enter the Min. Period of the frame in ms: <leave empty>.
7. Enter the Max. Period of the frame in ms: <leave empty>.
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 first
must be defined as a published signal then it has to be mapped to a frame. The data
is transmitted by means of the frame. A signal that is mapped to a frame is called a
mapped signal. A mapped signal is always mapped to a specific, unique position in
the data field of the frame (see Step 2).
The WindowPosition signal can be mapped to the DriverDoor_Window frame by
one of the following methods:
>
Within the Network Explorer: Drag & drop the WindowPosition signal from the
Published Signals list of the DriverDoorModule node to the
DriverDoor_Window frame in the Published Frames list of the
DriverDoorModule.
>
To add the WindowPosition signal, use the [Add…] function on the Signals
page of the Property dialog of the DriverDoor_Window frame.
>
Copy the WindowPosition signal to the clipboard and execute the Insert Link
function 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:
- 52 -
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
>
Tutorial
Enter the numeric position in the Properties dialog of the mapped
WindowPosition signal.
See Online Help for information on Intel and Motorola formats.
>
Graphical formatting of the Data field on the Layout page in the Properties
dialog of the DriverDoor_Window frame.
The byte order (Intel/Motorola) and the display format of the start position is
automatically 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 with
a 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.
Arrangement criteria
The mapping rules are selected in such a way to ensure the most efficient access
of the embedded software to the signals.
Graphical signal
layout
© Vector Informatik GmbH
Version 2.2
- 53 -
Tutorial
User Manual Network Designer LIN
6.5.3 Defining the subscribers of signals
Task: Define the DoorLock node as a subscriber of the DoorLockStatus signal.
The DoorLockStatus signal is defined by one of the following methods as being
subscribed by the DoorLock node:
>
Open the Network Explorer, then drag & drop the DoorLockStatus signal from
the Library Browser, list of global signals or the list of network signals to the
Subscribed Signals folder of the DoorLock node.
>
To add the DoorLockStatus signal, use the [Add…] function on the Subscribed
Signals page of the Property dialog of the DoorLock node.
>
Copy the DoorLockStatus signal to the clipboard and execute the Insert Link
function from the shortcut menu of the Subscribed Signals folder of the
DoorLock node.
Info: Before a signal can be defined as a subscribed signal of a certain node it has to
be 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 slave sends a so-called
Response 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 by
the slave.
1. Define the DoorLockStatus signal as published signal of the DoorLock node
(see chapter 6.5.1)
2. Open the DoorLock dialog with the Edit… shortcut menu of the DoorLock node
in the Network Explorer.
3. On the Properties page and select the category Status Management and select
via […] DoorLockStatus as Response Error signal.
- 54 -
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Tutorial
4. Create the DoorLock_Status frame in the Published Frames folder of the
DoorLock node (see chapter 6.5.2).
Settings:
> Frame Id: 0x1
> Length: 8
> Min and Max: > Message Id: 0x1
5. Map the DoorLockStatus signal to the DoorLock_Status frame (see chapter
6.5.2).
6. Define the DoorLock_Status frame as subscribed frame of the
DriverDoorModule node via drag & drop the DoorLock_Status frame to the
Subscribed Frames folder of the DriverDoorModule node.
Repeat these steps for the new signal WindowLifterStatus on the new
WindowLifter_Status frame of the WindoLifter node.
The settings are identical to DoorLockStatus signal and DoorLock_Status frame.
6.6
Designing the LIN Schedule
Task: Based on the created vehicle project and the designed network communication
of the DriverDoor_LIN network you will design the LIN schedule.
Set up a table with the NEW Table command:
1. Open the Network Explorer of the DriverDoor_LIN network.
2. Select the Edit schedule(s)… command in the shortcut menu of the
DriverDoor_LIN network.
The LIN Schedule Designer window opens.
3. Select the New Table command in the shortcut menu of the empty Schedule
Tables section of the window.
A table with the name Table0 is created and appears in the Schedule Tables
section of the window.
4. Select the Rename… command in the shortcut menu of the table.
5. Change the name to ApplicationTable.
6. Drag & drop the DoorLock_Status frame to the ApplicationTable.
7. Drag & drop the DriverDoor_Window frame to the ApplicationTable.
8. Click in the Delay column of the DriverDoor_Window slot and change the value
to 10.
© Vector Informatik GmbH
Version 2.2
- 55 -
Tutorial
User Manual Network Designer LIN
Set up a new table using the Table Wizard:
1. Select the New Table using Wizard… command in the shortcut menu of the
empty Schedule Tables section of the window.
The Schedule Table Wizard opens.
2. Select the Master Req diagnostic frame and press the [>>] button to add it to the
Selected frames list.
3. Select the SlaveResp diagnostic frame and press the [>>] button to add it to the
Selected frames list.
4. Click in the Req. Min. cell of the frames and change the Req. Min. time for both
frames to 10.
5. Change the Req. Max. time for both frames to 30.
6. Press [Next >].
The settings on the following page needn’t be changed.
7. Press [Next >].
The resulting schedule table is shown.
8. Press [Finish] to close the wizard.
The new table appears as Table1 in the list of schedule tables.
9. Select the Rename… command in the shortcut menu of Table1 and rename it to
DiagnosticTable.
10. Press [OK] to close the LIN Schedule Designer window.
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 are
mutually consistent, a consistency check can be performed with the Network
Designer.
1. Select the network on which to perform the consistency check.
- 56 -
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Tutorial
2. Select the Consistency Check command from the network's shortcut menu.
The result of the consistency check is displayed in a Consistency Check
window.
Task: Perform a consistency check for a vehicle project.
In order to determine whether the objects of a network and their relations are mutually
consistent, a consistency check can be performed with the Network Designer.
1. Select the vehicle project on which to perform the consistency check.
2. Select the Consistency Check command from the network's shortcut menu.
The result of the consistency check is displayed in a Consistency Check
window.
Info: The consistency check for a vehicle project only extends to the networks of the
vehicle project, whose type is supported by the Network Designer variants.
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 LIN
Description File
dialog
© Vector Informatik GmbH
Version 2.2
- 57 -
Tutorial
User Manual Network Designer LIN
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 execute
the Export to|LIN Description Files… shortcut 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 NCF
file.
2. From the node’s 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).
- 58 -
Version 2.2
© Vector Informatik GmbH
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 definitions
specify for which object type the attribute is defined and which
default value the attributes have.
communication
relations
Set and structure of data exchanged between the ECUs of a
distributed control system. This includes the messages,
message layout (mapping of signals to the messages), as well
as the transmission and reception relations between the
signals 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 a
user-defined
attribute
Value used for a user-defined attribute, if no explicit value has
been defined for an object.
destination message Message transmitted by a gateway ECU and on which a routed
signal 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.
ECU
electronic control
unit
Processing unit in a distributed vehicle network.
gateway
ECU linked with at least two networks. A gateway can transmit
signals 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 a
gateway 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 different
versions. In Network Designer, these are the vehicle projects
and 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 and
signal groups of the workspace.
local object
Object that is defined in the context of another object. In
Network Designer, for example, networks are always defined
within a vehicle project and messages within a network. Local
objects are always versioned as part of the global object to
which they belong.
© Vector Informatik GmbH
Version 2.2
- 59 -
Appendix A: Glossary
- 60 -
User Manual Network Designer LIN
Term
Description
mapped Rx signal
Network signal that is received by an ECU on a specific
message 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 signal
values. The exchanged signals are mapped in the data field of
the message. In addition, messages carry bus system-specific
protocol information (e.g. message header, identifier,
checksums, etc.).
network
Transmission medium used to exchange data between
distributed ECUs. Data is transmitted on a network by means
of a defined protocol (CAN, FlexRay, LIN).
Network Explorer
Window for defining the communication data of a network.
Defines the transmission and reception relations between
signals and nodes, as well as the messages of a network.
network node
Object that represents an ECU connection to a network. A
network node can have its own properties that specifically
describe the connection.
network signal
A signal transmitted on a concrete network. A network signal
references a global signal. A network signal has routingspecific 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 connections
between them.
object name or
symbolic identifier
Unique identifier of an object. This identifier is subject to certain
rules, 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 to
describe the hardware topology and communication relations,
e.g. networks, ECUs, messages or signals. The user has the
option of creating, editing and relating objects of these object
types.
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 the
PDU. Moreover a PDU describes a timing behaviour in the
context of a sender node. PDUs can be assigned to FlexRay
frames and network nodes as transmitted or received PDUs.
Project Explorer
Window for displaying vehicle projects loaded in the workspace
and its networks and ECUs. The hardware topology of a
vehicle is edited in this window.
relation between
objects
There are certain relationships between objects for describing
the hardware topology and communication. For example, a
message is transmitted by an ECU to a network. These
relationships are described by relations between the objects,
e.g. the node – Tx message) relation.
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Appendix A: Glossary
Term
Description
Rx message or Rx
frame
Message or frame received by an ECU on a network.
Rx signal
Network signal received by an ECU on a network.
schedule
Specified timetable in which messages or frames are
transmitted on a network. In FlexRay clusters and LIN
networks, schedules are used to define the transmission
properties of the ECUs. In contrast to the event-controlled and
arbitrage CAN protocol, the transmission time for FlexRay and
LIN is defined at the time the network is designed.
Transmission protocols in which the transmission properties
are defined by means of schedules are called TDMA
procedures (time division multiple access).
signal
Global signal that describes a value (a date) that is exchanged
between distributed control units. In contrast to a network
signal, a global signal is not assigned to a concrete network. A
global signal has properties such as data type and length.
Global signals can be versioned.
signal group
A signal group is a set of signals that is assigned to a
message, frame or PDU in common.
signal placement or
signal mapping
The fact that a signal is positioned in the data field of a
message and is transmitted on a network by means of the
message. A signal is always mapped to a certain position in the
data field of a message.
signal type
A signal type defines the properties, e.g. length and data type,
of one or more signals. Signals can reference the same signal
type, if they have identical properties.
source message
Message received by a gateway ECU and on which a routed
signal is transmitted.
source network
Network on which a gateway ECU receives a routed signal.
Tx message or Tx
frame
Message or frame transmitted by an ECU to a bus.
Tx signal
Network signal that is transmitted by the ECU on a network.
user-defined
attribute
User-defined attributes expand the set of object properties or
object relations specified in Network Designer. They allow the
user to customize the data model to the user's requirements. A
user-defined attribute is always defined for a specific object
type and has a default value. Each object of this type has either
an explicitly defined value or refers to the default value.
vehicle project
All data for describing the hardware topology and
communication relations of a distributed control system.
Different vehicle projects can be edited in the Network
Designer by multiple editors simultaneously. Vehicle projects
can be versioned.
workspace
Set of data with which a user currently works.
© Vector Informatik GmbH
Version 2.2
- 61 -
Appendix A: Glossary
7.2
7.3
7.4
- 62 -
User Manual Network Designer LIN
Network Designer CAN
Term
Description
CAN bus
A network that uses the CAN protocol to route data.
CAN message
Signals or signal values are transmitted on a CAN network by
means of CAN messages. CAN messages have a unique CAN
identifier for signal identification and prioritization (arbitration).
CAN network
A network that uses the CAN protocol to route data.
Network Designer LIN
Term
Description
LIN frame
Description of transmitted communication objects in LIN
systems.
LIN master node
Unit that connects an ECU with a LIN bus. In this LIN bus the
ECU takes over the function of the master node.
LIN network
Description for LIN bus system.
LIN slave node
Unit that connects an ECU with a LIN bus. In this LIN bus the
ECU takes over the function of the slave node.
Network Designer FlexRay
Term
Description
FlexRay channel
A transmission channel of a FlexRay cluster. Two channels can
be used within a FlexRay cluster for redundant data
transmission or for increasing bus bandwidth.
FlexRay cluster
A cluster makes data transmission between ECUs by means of
the FlexRay protocol possible. A cluster can have one or two
FlexRay channels.
FlexRay frame
Signals or signal values are transmitted on a FlexRay cluster
by means of FlexRay frames. FlexRay frames can be
transmitted in the static or dynamic segment of the FlexRay
schedule.
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Appendix B: File name extensions
8 Appendix B: File name extensions
A file name extension consists of three characters preceded by a period (full stop).
These are placed directly after the file name itself. The file name extension indicates
the file type.
File Extension
File Type
CHM
Help file
DBC
CANdb network file, used to describe CAN
communication data (Data Base for CAN)
DLL
Dynamic Link Library
EXE
Executable program
FIBEX (XML)
File that describes message-oriented communication
systems (Field Bus Exchange Format)
INI
File with configuration settings
LDF
LIN Description File, used to describe LIN
communication data
NDW
Network Designer Workspace file
XML
Extendable Markup Language
© Vector Informatik GmbH
Version 2.2
What is a file name
extension?
- 63 -
Appendix C: Keyboard operation
User Manual Network Designer LIN
9 Appendix C: Keyboard operation
- 64 -
Key(s)
Description
<Ctrl>+<O>
Opens a workspace.
<Ctrl>+<N>
Creates a new workspace.
<Ctrl>+<S>
Saves the currently open workspace.
<Ctrl>+<C>
Copies the selected object to the clipboard.
The Paste menu item or <Ctrl>+<V> can then be used
to make a copy of an object, and the Insert Link menu
item can be used to link the object with another object.
<Ctrl>+<V>
Pastes the contents of the clipboard.
<Ctrl>+<A>
Selects all lines of the active list view.
<Return>
Opens the properties dialog of the selected object.
Saves the changes made in a dialog and closes the
dialog.
Saves the changes made in the In-Place-Edit mode of
an object list.
<Esc>
Closes the active dialog without accepting the changes.
Rejects the changes made in the In-Place-Edit mode of
an object list.
Corresponds to activation of the [Cancel] or [Close]
button.
<Del>
Deletes the selected object.
<Ins>
Creates a new object.
<Tab>
Activates the next entry or button in a dialog.
<Shift>+<Tab>
Activates the previous entry or button in a dialog.
<Ctrl>+<Tab>
Activates the next dialog tab in a dialog that has several
tabs.
<Alt>+<Spacebar>
Opens the System menu of the Network Designer
program window.
Alternately, the System menu may also be opened by
double clicking the System Icon.
<F1>
Calls Network Designer help for the active dialog or the
selected command.
When the Network Designer help is already active it
calls a help text containing information on the use and
adaptation of help.
<F2>
Activates editing mode for the activated cell in a table.
<Ctrl>+<F4>
Closes the active window.
<Alt>+<F4>
Closes the active workspace and exits Network
Designer.
<F5>
Refreshes the current view.
<Ctrl>+<F5>
Reloads the active workspace.
This updates the data after a different Network Designer
tool has been used to edit the workspace.
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Appendix C: Keyboard operation
Key(s)
Description
<Ctrl>+<F6>
Activates the next open window in the main editing area.
<F10>
Activates the main menu bar.
<Cursor up>
Navigates one line up in tree and list views.
<Cursor down>
Navigates one line down in tree and list views.
<Cursor left>
In tree views: Opens the currently selected hierarchy
level or navigates up one level.
In list views: Activates the cell to the left of the currently
active cell.
<Cursor right>
In tree views: Opens the currently selected hierarchy
level or navigates down one level.
In list views: Activates the cell to the right of the currently
active cell.
<Shift>+<Cursor up>
<Shift>+<Cursor down>
Selects several adjacent lines in an object list.
<Ctrl>+<Cursor up> +
<Ctrl>+<Space>
<Ctrl>+<Cursor down> +
<Ctrl>+<Space>
Selects several non-adjacent lines in an object list.
<Page up>
Scrolls up one page.
<Page down>
Scrolls down one page.
<Pos 1>
Navigates to the first line in a tree or list view.
<End>
Navigates to the last line in a tree or list view.
<+> in NUM mode
Opens one hierarchy level for the selected line in tree
views.
<-> in NUM mode
Closes the hierarchy for the selected line in tree views.
<*> in NUM mode
Opens all nested hierarchy levels for the selected line in
tree views.
© Vector Informatik GmbH
Version 2.2
- 65 -
Appendix D: NetworkDesigner.ini configuration file
User Manual Network Designer LIN
10 Appendix D: NetworkDesigner.ini configuration file
NetworkDesigner.ini
Program-specific settings are saved in the configuration file.
You can edit the [AttributeCategoryN] sections to modify and extend the
attribute categories that are available in the list views during configuration.
N is a sequential index for numbering attribute categories. The individual categories
contain category names (e.g., Name=System Attributes) as well as the names of
the attributes belonging to the category. The attributes are also numbered
sequentially, e.g. Attribute1=Byte Order.
When editing attribute categories, please make sure that the categories and the
attributes belonging to the categories are numbered sequentially without any gaps in
ascending order, and that the attributes are spelled correctly.
- 66 -
Version 2.2
© Vector Informatik GmbH
User Manual Network Designer LIN
Appendix A: Addresses
11 Appendix A: Addresses
Vector Informatik GmbH
Vector Informatik
GmbH
Ingersheimer Str. 24
D-70499 Stuttgart
Phone: +49 (711) 80670-0
Fax: +49 (711) 80670-111
mailto:[email protected]
http://www.vector.com
Vector CANtech, Inc.
Vector CANtech, Inc.
Suite 550
39500 Orchard Hill Place
USA-Novi, Mi 48375
Phone: +1 (248) 449 9290
Fax: +1 (248) 449 9704
mailto:[email protected]
http://www.vector.com
Vector France SAS
Vector France SAS
168, Boulevard Camélinat
F-92240 Malakoff
Phone: +33 (1) 4231 4000
Fax: +33 (1) 4231 4009
mailto:[email protected]
http://www.vector.com
Vector GB Ltd.
Vector GB Ltd.
Rhodium
Central Boulevard
Blythe Valley Park
Solihull, Birmingham
West Midlands B90 8AS
United Kingdom
mailto:[email protected]
http://www.vector.com
© Vector Informatik GmbH
Version 2.2
- 67 -
Appendix A: Addresses
Vector Japan Co.,
Ltd.
User Manual Network Designer LIN
Vector Japan Co., Ltd.
Seafort Square Center Bld. 18F
2-3-12, Higashi-shinagawa, Shinagawa-ku
J-140-0002 Tokyo
Phone: +81 3 (5769) 7800
Fax: +81 3 (5769) 6975
mailto:[email protected]
http://www.vector.com
Vector Korea IT Inc.
Vector Korea IT Inc.
#1406 Mario Tower
222-12 Guro-dong, Guro-gu
Seoul, 152-848
Republic of Korea
Phone: +82 2 8070600
Fax: +82 2 8070601
mailto:[email protected]
http://www.vector.com
VecScan AB
VecScan AB
Theres Svenssons Gata 9
SE-417 55 Göteborg
Phone: +46 (31) 76476-00
Fax: +46 (31) 76476-19
mailto:[email protected]
http://www.vector.com
- 68 -
Version 2.2
© Vector Informatik GmbH
Get more Information!
Visit our Website for:
> News
> Products
> Demo Software
> Support
> Training Classes
> Addresses
www.vector.com