Eurotech COM-1240 Owner's manual

Brand: Eurotech

Model: COM-1240

Category: Gateways/controllers

Type: Owner's manual

EmbeddedDNA

Library Tool Reference Manual

(To be used with Library Tool Ver.1.00)

Rev. 1.0 - Sep. 2006

124

2 PC/104 – COM-1240 Tools Manual

Introduction

Eurotech Spa would like to point out that, although all the information contained herein has been

carefully verified, Eurotech Spa does not assume any responsibility for errors that might appear in this

document, or for damage to property or persons resulting from an improper use of this manual and of the

related software.

Eurotech Spa reserves the right to change the contents and form of this document, as well as the features

and specifications of its products at any time, without notice

, particularly because of continuous

upgrades.

Eurotech Spa informs you that the information contained in this manual is continuously being updated in line

with the technical alterations and improvements made by Eurotech Spa to the products and thus this manual

only reflects the technical status of the products at the time of printing.

Updated versions will become available on the Eurotech website: www.eurotech.it

For further information, please contact:

Eurotech Spa.

Phone: +39 0433 485 411

Fax: +39 0433 485 499

E-mail: sales@eurotech.it

This manual is protected by copyright.

Trademarks and registered trademarks appearing in this document are the property of their respective

owners. Copies of all or part of this manual or translations into a different language may only be made with

the prior written consent of Eurotech Spa.

Reproduction for distribution purposes is only permissible with the express approval from:

Eurotech Spa

Via Solari, 3

33020 - AMARO (UD)

ITALY

PC/104 – COM-1240 Tools Manual 3

Conventions

The following table lists the conventions that are used throughout this manual.

Icon Notice Type Description

Information note

Important features or instructions

Warning

Information to alert you to potential

damage to a program, system or device

or potential personal injury

The “Mode” of the register:

R/W Read and write register

RO Read only register

W Meaning of the register when written

R Meaning of the register when read

Hexadecimal numbers:

Hexadecimal numbers are indicated with an “h” suffix (for example: 11Ch)

Other:

NC Not internally connected

Reserved Use reserved to Eurotech

Environmental safety

When disposing of the equipment, we suggest separating all of its components when possible, and disposing

of them in accordance with local waste disposal legislations.

Be sure to dispose of used batteries as required by local waste disposal legislation. Never throw batteries

into a fire (risk of explosion) or household garbage can.

The symbol on the product or on its packaging indicates that this product may not be treated

as household waste. Instead it should be handed over to the applicable collection point for the recycling of

electrical and electronic equipment. By ensuring this product is disposed of correctly, you will help prevent

potential negative consequences for the environment and human health, which could otherwise be caused

by inappropriate waste handling of this product. For more detailed information about recycling of this product,

please contact your local civic office, your household waste disposal service or the shop where you

purchased the product.

Antistatic precautions

Always use appropriate antistatic precautions when handing any board

This is to avoid damage caused by ESD (Electro Static Discharge)

Table of contents

Introduction..................................................................................................................................................2

Conventions...................................................................................................................................................3

Environmental safety .....................................................................................................................................3

Antistatic precautions.....................................................................................................................................3

Table of contents .........................................................................................................................................4

System Requirements ...................................................................................................................................5

Installation......................................................................................................................................................5

Export project to Microsoft Access MDB database .......................................................................................5

Import project from Microsoft Access MDB database ...................................................................................5

Creating a new project...................................................................................................................................6

Data Tables ...................................................................................................................................................6

Project.......................................................................................................................................................7

MvbDevices ..............................................................................................................................................8

MvbDevice................................................................................................................................................9

RtpConfigFunDir.....................................................................................................................................10

RtpConfigParam .....................................................................................................................................11

TrafficStore .............................................................................................................................................12

MvbBusAdmin ........................................................................................................................................13

Variables.................................................................................................................................................14

DefaultValues .........................................................................................................................................15

PdmConfig..............................................................................................................................................16

PdmProgram ..........................................................................................................................................17

System Requirements

MVBDSCfg.exe is a Windows based application; the minimum system requirements are:

•

Windows XP or Windows 2000

Microsoft.NET Framework 1.1

The Microsoft Windows Update service can be used to upgrade th

e basic software of the PC.

Installation

No installation is required. Double clicking MVBDBCfg.exe will immediately start the program.

Export project to Microsoft Access MDB database

This feature is useful for translating and exporting project files to a Microsoft Access database format.

The first step requires the creation of an empty MDB database using Microsoft Access program, this is

necessa

ry because MVBDSCfg does not create the database file it simply creates tables and populates

them with data. Be sure the required tables are not present on the database file, because MVBDSCfg will

create them.

Import project from Microsoft Access MDB database

It is possible to import a project directly from a Microsoft Access MDB database. MVBDSCfg requires that

the source database is compliant with relationship rules embedded in MVBDSCfg projects.

6 PC/104 – COM-1240 Tools Manual

Creating a new project

To create a new empty project simply select ‘File’ & ‘New’ in the menu, then input the required data into the

tables.

Data Tables

The project consists of a set of tables like a generic database application. MVBDSCfg can distinguish two

types of tables:

Constant tables •

•

Application project tables

The constant tables are identifiable by name: if the name starts with the underscore (“_”) ASCII character the

table is a “Constant table”. These tables are read only and are used by the tool as constant values. The user

can open these tables and view the contents for help when editing “Application project tables”.

All other tables are application project tables. Users can edit them to create a project.

The current version of MVBDSCfg has the following limitations:

15 constant tables

28 application project tables

The following section describes all the tables in detail. The order is the natural order in project building for all

kind of applications: TCN, WTB, MVB gateway, MVB device and WTB device.

PC/104 – COM-1240 Tools Manual 7

Project

Project identification table used to sign the database. The defined values are available during normal

operation for version control. If this table is not filled the MVBDSCfg will automatically insert default values

with current built date and zero’s for all other fields.

Field Usage Range Notes

Name

Project name Not yet implemented in database generation

Application Id

Application identification 0~65535 Null = 0

Vehicle

Application Id

Vehicle application

identification

0~65535 Null = 0

Database

Version

Database version number 0~65535 Null = 0

Database Date

Creation date Null = Actual date

Compatibility

Level

Code for previous version

compatibility

0~65535 Null = No constraint

Codes can be used to force compatibility level

in binary database generation

See the “Evolution” number in ‘Help’ & ‘About’

dialog box

Note:

The values in this section are not used by the application, so it is recommended to fill the table to identify a

configuration database once uploaded to device.

8 PC/104 – COM-1240 Tools Manual

MvbDevices

This table is required for devices that include an MVB bus and RTP. A minimum of one physical device is

required to configure the hardware device; more entries are required to properly build the RTP Function

Directory (see IEC) and to configure the MVB bus administrator known device list.

More records are allowed for this table.

Field Description

Name

Internal name used to identify the record

It is recommended to use the name of the physical device. This is the primary key of the

table, therefore no duplication is allowed.

Address

MVB physical device address

It is recommended to limit the 4096 range to 8 significant bits, with a low value for

message data capability (class 2 MVB device) and high values for process data only

capability (class 1). The low values are 1~254, and high values are 256, 272 to 4080. The

value “0” is a logical address for itself and is often used to fill some entries in RTP function

direction table. The value 255 is also reserved for RTP using.

KnowDevice

The checked device will be put on MVB BA known device list. It is recommended to check

all the MVB devices on the network; the other poll mechanism is the polling for all possible

devices for network discovery.

BusAdmin

The MVB BA mastership transfer will be performed on the selected devices.

ScanOrder

This value is used to define a fixed scan order for the known devices and also for bus

administrators.

Note:

The fields “KnowDevice”, “BusAdmin” and “ScanOrder” are used to create the MVB bus administrator

configuration database.

PC/104 – COM-1240 Tools Manual 9

MvbDevice

This table is required for devices that include an MVB bus. A single entry is required on this table.

Field Description

AttachType

This field defines the physical medium attachment for the MVB bus. The valid values

are stored on the constant table “_MvbAttach”.

LineUsed

This field defines the redundancy option. The valid values are stored on the constant

table “_MvbLineMode”.

TimeMaxReply

Maximum Reply Time

This value is used to setup the reply time according to IEC 61375 clause 3.4.2.2 for

reply delay definition. The default value is 42.7(microseconds); other valid values are:

22.0, 64.0 and 86.0. The value will be rounded according to IEC defined values.

Device

MVB device name

This field contains the MVB device name from “MvbDevices” table.

DSWSet

Device Status Word set mask

This value is used to set one/more bits on MVB device status word. See IEC 61375

clause 3.6.4 for Device Scan. In this clause the device status word is defined for MVB

device classes. This field is present for special applications that directly drive the device

status word and for testing. For normal operation and application projects this value

should be reset to zero because it is directly driven by TCN software.

DSWClear

Device Status Word clear mask

This value is used to reset one or more bits on MVB device status word. See the

previous (DSWSet) field description.

10 PC/104 – COM-1240 Tools Manual

RtpConfigFunDir

This table is required if RTP software is included in TCN software stack. An entry for each function is

required.

Field Description

RtpFct

RTP function number. Range: 0~255. See IEC 61375 clause 2.3.10.2.3 Address constants for

the embedded / reserved RTP values. The function 251 (RTP router) shall be present for TCN

gateway. The functions 253/254 for TCN network management are also defined. See the

UIC556 2

edition for RTP function definitions. For example function 15 is reserved for

Mapping Server; function 9 for diagnostic, function 14 for passenger information system and

so on. See UIC556 2

edition Annex 1 for the whole WTB traffic; look at the source and

target function for type of telegram “E”.

Device

MVB device name. This field contains the MVB device name to allow for correct routing of the

TCN gateway. The MVB device address is also called station. Zero “0” is an alias for itself.

Example:

On a TCN Gateway the RTP function 251 (RTP routing) refers to MVB address “0”: this is

why the MvbDevices table contains an entry for logical device with MVB address “0”.

Description

Available for commenting.

PC/104 – COM-1240 Tools Manual 11

RtpConfigParam

This table is required if RTP software is included in TCN software stack. A single entry is required.

Field Description

MaxCalls

Maximum number of simultaneous RTP call messages.

If the device tries to force this limit the AM_NR_OF_CALLS_OVF RTP error is generated:

see IEC 61375 for reference about call instances. On a TCN gateway a high value shall

be set in order to let the Multicast Mapping Server to perform multiple calls (for example

“turn-on light” see UIC556 2nd edition Annex 1 telegram 2.1E.

MaxRepliers

Maximum replier instances allowed in device.

If the device tries to force this limit the AM_NR_OF_INST_OVF RTP error is generated:

see IEC 61375 for reference about replier instances. Like for MaxCalls, the correct value

shall evaluated according the RTP messaged data traffic of the device

MaxCredit

The connection credit is an RTP parameter used to setup the transport layer.

The value 7 is the recommended maximum performance on high quality network; reduced

values should be used for disturbed physical layer. See IEC61375 clause 2.3.6 for more

detail about this setup.

CallTimeout

Predefined RTP message data connection timeout.

The time unit is 64 milliseconds.

12 PC/104 – COM-1240 Tools Manual

TrafficStore

This table is required to define the datasets involved in RTP process data traffic. The table contains up to

one WTB dataset, zero or more MVB datasets and zero or more EXT datasets. The EXT dataset is a custom

definition with bus_id=2 referring to embedded shared memory or dual port memory to interface custom bus.

This table is also used to create the MVB bus administrator configuration database (if applied).

Field Description

Name

Dataset name

TsName

Traffic store identifier. Refer to “_TrafficStores” constant table for the valid values.

According with IEC 61376: MVB bus id value is “0”, WTB bus id value is “1” and EXT bus is

a custom value used for additional custom bus; the decimal value is 2. For the WTB bus, a

single entry is allowed to define a full WTB traffic store; the MVBDBCfg will use the

MaxNodes field of the WtbDevice table to create the WTB traffic store.

Port

Port number as defined in IEC 61375 document. For the WTB bus the value “0” shall be

used because the entry is expanded by MVBDSCfg to create a full WTB traffic store

definition. For MVB bus the range 0~4095 can be used, normally high values are used for

class 1 devices that do not implement the PIT (process data index table); for these class 1

devices the process data port number(s) correspond to the MVB physical address. For EXT

bus, different port values are defined depending of the case: (CAN bus, Shared memory,

TC57 protocol, other UART custom protocols).

DsSize

Dataset size. The WTB bus the value 128 is used, MVB bus the values 2,4,8,16 and 32 are

used, and for the EXT bus the dataset size depends on the specific hardware / Software

project.

Direction

Dataset data flow. The values are defined in the “_DataSetDirections” constant table. The

direction is the device point of view. For the WTB bus the SOURCE value shall be used, for

MVB device the proper value shall be used (according with MVB network definition). EXT is

used for PDM variables.

PollPeriod

Polling period for the dataset. For WTB bus, the value is not applied because it is defined

by WTB NodePeriod in the WtbDevice table; do not set any value putting the word “(null)”.

For the MVB dataset the value is a number of basic periods: valid values are

1,2,4,8,16…512,1024. For most applications the MVB basic period is exactly 1ms, so the

value (powers of “2”) is the number of milliseconds. This value is used to create the MVB

bus administrator configuration database.

ScanOrder

Set value “(null)” for WTB bus. For the MVB bus, this value defines the poll order of

datasets, it is used to create the MVB bus administrator configuration database. Valid

values have a range 1 <= ScanOrder < (PollPeriod+1). Fractional numbers are allowed to

force an order for datasets polled on the same basic period. The full poll list table is

graphically displayed with the command ‘View’ & ‘MvbPollList’ (if the MVB bus

administrator configuration table is correctly compiled). For EXT bus, set value “(null)” if no

different specified on specific hardware and software project.

Hide

This flag is used to define phantom entries required for internal reference (for example for

variable definition), but not inserted to traffic store configuration database. In some

application dataset referring to EXT bus are phantom entries because the EXT traffic store

is an embedded hardware and/or software definition on the target. A special usage is also

available for MVB dataset with non standard polls: in this case phantom entries with

different “PollPeriod” and “ScanOrder” can be defined to create complex interleaving in

MVB bus administrator configuration.

Description

User Comments

PC/104 – COM-1240 Tools Manual 13

MvbBusAdmin

This table defines the MVB bus administrator configuration. The complete configuration requires the

MvbDevices table to build the “know device list” and the “bus administrator list”. The TrafficStore table is

required to create the scan lists using the “PollPeriod” and “ScanOrder” fields.

Field Description

NotUsed

Set this value to “(null)” for compatibility.

Version

The configuration version is used in Bus Administrator to check the consistence

in case of multiple class 4 devices.

TimeReplyMax

t_reply max is used to adjust the network speed according to MVB physical layer

(medium type, repeaters, active star coupler, etc..). The default value is 42.

PeriodsPerMacro

The number of basic periods in a macro period. The default is 1024, used with

1ms of basic period to define about 1second

EpsHigh

Flag for event poll strategy for high priority.

EpsLow

Flag for event poll strategy for low priority.

TimeBasicPeriod

Basic period duration in microseconds. Set value 1000 for 1msec.

MacroCyclesPerTurn

Number of macro cycles per turn.

DeviceScanStrategy

This flag is used to setup the device scan. If checked, all devices will be polled,

otherwise the devices listed in “MvbDevices” table with the “KnowDevice” flag

checked will be polled. In this case the order is defined in “ScanOrder” field.

ScanList

For old compatibility only. Set the string “112=0 16=1”.

Hide

This option will prevent the MVB bus administrator section generation on output

binary database. Use is for testing purpose only.

14 PC/104 – COM-1240 Tools Manual

Variables

This table defines the RTP variables according the IEC61375 process variable definition.

Field Description

A numeric identifier that represents the order on the output database. The values are

generated automatically by the ‘Project’ & ‘Check’ procedure. The value is for user

reference only.

Name

Variable name. No duplication is allowed because this is the primary table key.

Type

This value defines the variable type. Refer to “_VarTypes” constant table for valid

values. The prefix of the variable type defines the “type”, the number define the variable

size in bits.

Examples:

“B1” is a Boolean variable, size = 1-bit.

“T48” is a time-date variable, size = 48-bits

ArraySize

This value defines the number of items for array variables. According to IEC61375, only

integer variables of 8, 16 or 32-bit size are supported array types. The value “(null)”

should be used for scalar type variables.

DataSet

This field is a reference to the “TrafficStore” record.

DataAddress

Address of the variable on the dataset. The value is defined in bits. The value range in

0~1023. The ‘Project’ & ‘check’ procedure evaluates the overflow according the dataset

size and the variable size.

CheckAddress

Check variable address. Even values in the range 0~1023 are applicable to define a

check variable. The values 1023 and “(null)” are used if not check variable is defined.

The ‘Project’ & ‘check’ procedure evaluates the overflow according the dataset size.

Timeout

Timeout of the variable in milliseconds. The value “(null)” should be used if no timeout is

defined. The application uses the timeout value to evaluate the freshness of the single

variable. Different values can be defined for variables on the same dataset.

Description

A text field for the users description.

Notes:

The PDM (Process Data Marshalling) defines a special complex variable for import from more vehicles / TCN

nodes. Refer to PDM user manual for this variable definition.

PC/104 – COM-1240 Tools Manual 15

DefaultValues

This is very simple table supplying constant values for the PDM application program.

Field Description

Name

This value identifies the entry on the table. No duplication is allowed because this is the

primary database key.

ValByte

This is a numeric value. The valid range is 0~255 for a single byte constant value.

Description

A text field for user description.

Note:

The PDM can be programmed to refer to this table for constant values. If a value size exceeds the single

byte, the successive byte will also be used. For this reason the value order is mandatory. The creation order

is used to identify the successive byte(s). The creation order is displayed when the window is open.

16 PC/104 – COM-1240 Tools Manual

PdmConfig

This table defines some configuration parameters for PDM.

Field Description

AllowSingleNode

This flag allows the PDM to work regardless the WTB network. Check this value for

UIC556 compatibility.

DefaultFTF

This value refers to the “PdmFTFCodes” table and is used to allow the PDM to work

alone for applications where no mapping server is used. Use the value “(null)” for

UIC556 application.

MarshTime

The marshalling time is a value, in milliseconds, is used to define the PDM

marshalling time poll. A very short time (for example 10ms) can be used for very

simple PDM programs; in case of huge PDM programs higher values should be used.

The suggested starting value is 200ms.

MaxUicVeh

The maximum UIC vehicles value is used to limit the traffic store usage for import

with multiple results for UIC sort mode: refer to PDM user manual for detail.

OnErrorValue

This value is used by PDM as an embedded default statement where no explicit

definition is supplied in the PDM program. Valid values are defined in

“_PdmCfgErrValue” constant table.

OnErrorCheck

This value is used like “OnErrorValue”. Valid values are define in “_CheckVariable”

constant table.

Description

A text field for users description

Note:

Refer to PDM user manual for details about PDM functionality and configuration.

PC/104 – COM-1240 Tools Manual 17

PdmProgram

This table defines the PDM program.

Field Description

This value is a numeric identifier that represents the order on the output database. The

values are generated automatically by the ‘Project’ & ‘Check’ procedure. The values

are for user reference only.

ExecOrder

This value can be supplied to force a different execution order. If no value is supplied

“(null)”, the default execution order (according to “ID” field value) will be applied.

MarshMode

Three marshalling modes are defined on the “_PdmMarshMode” constant table. The

“IMP” (import) and “EXP” (export) are reserved for TCN gateway to import variables

from WTB and to export variables to WTB. For all other data paths the “INT” (internal)

marshalling mode is used.

FTFrequired

This statement is applicable for UIC556 gateways. If the value is specified from

“PdmFTFCodes”, the statement will be executed, if and only if the node FTF

corresponds to a specified value. If the “(null)” value is specified the statement is

always executed (regardless of FTF code of the node).

Result

This field is a reference to “Variables” table. The result variable should be a WTB

variable for export marshalling.

PdmFct

PDM functions are defined in “_PdmFunction”. The default function is a special code to

overwrite the embedded result values defined in “PdmConfig” table: if this code is

specified, the “Argument” field (described below) is not applied.

Argument

This field refers to the argument variable from “Variables” table. The argument variable

refers to WTB dataset for import marshalling on TCN node.

FTFimport

This field is used for import marshalling mode only. If a valid value from

“PdmFTFCodes” is specified, the import is performed from dataset marked with the

FTF code only. If “(null)” is specified the import is performed from all FTF codes (no

check on FTF is performed).

SDFMode

Only applicable to import from WTB. When checked the import will generate a complex

variable to separately store more source variables from different TCN nodes. The

PdmFct will be a “COPY” function. The “Result” variable definition is used to create the

SDF variable: The “DataAddress” value specifies the directory size. The

“CheckAddress” is zero, if the check variable is required and “(null)” if not required.

Refer to the PDM user manual for a full description of import with SDF.

SDFUicSort

A sub code for import SDF mode: The UIC sort will generate data according to the UIC

vehicle number. The non-UIC sort will select the TCN sort by using the WTB node

address instead of UIC addresses. The TCN sort will require a 64-bit directory size in

order to represent WTB address 1~63. The UIC sort supports directory sizes of 8, 16,

32 and 48-bits.

BitCastValue

If not “(null)” the “Argument” variable is converted to BITSET type and the selected bit

is used. The absolute valid range is 0~63, but the high limit is defined by the

“Argument” variable size (in bits). The ‘Project’ & ‘check’ procedure evaluate the

selected value.

BitCastNot

This flag works is “BitCastValue” is not “(null)” to negate the selected bit.

18 PC/104 – COM-1240 Tools Manual

ChkArgValue

Applicable values are defined in “_PdmCheckArg”. This field defines the check on

“Argument” variable. If the check variable is defined, the check variable is used;

otherwise the values “all zeros” and “all ones” (except for B1 variable type) will be used

for Error and Undefine attribute to invalidate the argument. This check can be disabled

selecting the value “NONE”. The value “ERROR” is used for mandatory argument that

require invalidating of result. The value “IGNORE” is used for optional argument that

can be skipped if not okay. This statement is not applicable with “DEFAULT” “PdmFct”.

ChkArgTimeout

This field will check the timeout of the “Argument” variable comparing the dataset

freshness counter with the “Timeout” value defined in “Variables” table. The values, the

actions and the applicability are the same of “ChkArgValue”.

OnErrorCheck

This field is used to define the check variable value for error handling. The values are

defined in “_CheckVariable” table. This field is applicable only with “DEFAULT”

“PdmFct”. If this statement is not defined the general default statement is used (see

“PdmConfig” table).

OnErrorValue

This field is used to define the value for error handling. The values are defined in

“_PdmOnErrValue” table. The value “NO_WRITE” is used to keep previous result; the

value; the value “UNDEF” is used for undefined value (all ones); the value “ERROR” is

used for error value (all zeros). The value “DEFAULT” is used to use a specific value

from “DefaultValues” table.

DefValue

This value is a reference to “DefaultValues” table applicable to “DEFAULT” “PdmFct”

and “DEFAULT” “OnErrorValue”. ). The “Project->check” procedure evaluate the data

alignment and overflow according to “Result” variable type and size.

Description

A text field for the users description

Note:

Refer to PDM user manual for detail about PDM functi

onality and configuration.

Eurotech COM-1240 Owner's manual

Brand: Eurotech

Model: COM-1240

Category: Gateways/controllers

Type: Owner's manual

Download PDF

report

Eurotech COM-1240 Owner's manual

Eurotech COM-1240 Owner's manual

Related papers

Other documents