FREMO Interlocking

Elekdra MR -> User documentation

31.01.2006

Elekdra

Elekdra has the responsibility, to control the entired station. This should be done in respect to all rules.

Installing Elekdra

Elekdra is delivered in on Zip file. For fast installation, just unpack the File at C: and start Elekdra.

To understand, what Elekdra needs to run, the following files are described.

Basically, all Files can be positiond at each place of the computer, except of one! The configuration file elekdra_config.xml has to be placed at C:/elekdra/elekdra_config.xml. All other Files are referenced in that file.

Configuring Elekdra

The configuration of Elekdra is done by editing elekdra_config.xml. For that, each standart editor may be used. Here, the different sections of the file shall be described.

The File is written in XML, and so some coding standarts have to be considered.

The file has to begin with the tag: <?xml version="1.0" encoding="UTF-8"?>

The next tag is <config>. It may not be closed, until the file is at the end! Within this tag, all the configuration is done.

The following sections describe the different tags. Each title stands for a tag. Subtitles for a tag within the tag above.

version

Here the version of the filetype is set. Currently it is 1

loglevel

The Loglevel configures the way of logging. It defines the lowest level of logging. A higher level means, that less information is logged.

0 ... All Messages, even Debug messages
1 ... Info
2 ... Notice
3 ... Failure
4 ... Error
5 ... Fatal
6 ... Emegency

languagefile

This tag gives the absolute path to the languagefile.

<languagefile>C:\elekdra\languagefile.xml</languagefile>

language

Here the selected Language is given. The language has to be defined in the languagefile.

deutsch ... German
english ... Englisch

<language>deutsch</language>

selstation

Here the shortcut of the station, which has to be loaded, is given. The stations are defined in a later section of the file. The name has to be identical to the shortcut, which is defined by the station.

<selstation>oberwart</selstation>

constants

Within this tag <constants></constants>, all constants have to be defined.

timeout_point_sim

This constant defines the time, the turnout is been simulated to switch into the selected position. This is needed, if ther is no feedback of the timeout. The value gives the number of seconds.

<timeout_point_sim>5</timeout_point_sim>

timeout_point

This constant defines the maximum time for the turnout to get into the selected position. If the position is not reached within that time, the turnout sends an error. The value gives the number of seconds.

<timeout_point>10</timeout_point>

turnoff_output

Here it is defined, if the power of the turnout motor has to be turned off, if the turnout has reached the selected position. Possible values are yes or no.

<turnoff_output>no</turnoff_output>

intervall_check_ekw

This constant defines the period for checking single diamond crossing with slips. If the two turnouts have positions, that are not possibe, an error is created. The value gives the number of seconds.

<intervall_check_ekw>5</intervall_check_ekw>

timeout_eksa_sim

This constant defines the time, the levelcrossing secure system is been simulated to switch into the selected position. This is needed, if ther is no feedback of the timeout. The value gives the number of seconds.

<timeout_eksa_sim>5</timeout_eksa_sim>

timeout_eksa

This constant defines the maximum time for the levelcrossing secure system to get into the selected position. If the position is not reached within that time, the levelcrossing secure system sends an error. The value gives the number of seconds.

<timeout_eksa>10</timeout_eksa>

intervall_ln_resend

Gives the period to resend safety related status information over the LotusNet, like the state of a signal. The value gives the number of milliseconds.

<intervall_ln_resend>10000</intervall_ln_resend>

turnout_ln_resend

Gives the period to resend turnout status information over the LotusNet. The value gives the number of periods of the safety related information.

<turnout_ln_resend>3</turnout_ln_resend>

connections

Here the connections are configured within the tag <connections></connections>

lbserver_ip

Configures the IP Adress of LbServer.

<lbserver_ip>127.0.0.1</lbserver_ip>

lbserver_port

Configures the Port of LbServer.

<lbserver_port>1234</lbserver_port>

elekdra_port

Configures the Port, Elekdra should open for connection to user interfaces..

<elekdra_port>2143</elekdra_port>

station

Here station is defined within the tag <station></station>

name

Defines the shortcut of the station. The shortcut has to be unique! It is used, to reference the station at selstation and in the different stationfiles.

objectfile

Gives the absolute path to the object file of the station.

<objectfile>C:/elekdra/stations/demo/objects.xml</objectfile>

hardwarefile

Gives the absolute path to the hardwarefile of the station.

<hardwarefile>C:/elekdra/stations/demo/hardware.xml</hardwarefile>

routefile

Gives the absolute path to the routefilee of the station.

<routefile>C:/elekdra/stations/demo/route.xml</routefile>

That was the configuration of Elekdra. The stations are defined in seperate files as configured above.