Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
it:wintertrainv4:design:configuration [2019/12/29 09:26]
jabe [Where]
it:wintertrainv4:design:configuration [2020/01/05 10:49] (current)
jabe
Line 1: Line 1:
 ====== Organization of Configuration data ====== ====== Organization of Configuration data ======
  
-Site specific configuration is all about specifying how the whole Winter Train is structured and how the supporting hardware and software is organized. This is the part, which will change each time a railway is build or rebuild. ​+Site specific configuration is all about specifying how the whole Winter Train is structured and how the supporting hardware and software is organized. This is the part of the system, which will change each time a railway is build or rebuild. ​
  
 ===== "​What"​ ===== ===== "​What"​ =====
  
   * Railway configuration   * Railway configuration
-    * Track topology (order of and distance between e.g. points and signals, length of track segments)+    * Track topology (sequence ​of and distance between e.g. points and signals, length of track segments)
     * Signaling data like routes, speed, shunting area etc.     * Signaling data like routes, speed, shunting area etc.
     * Position of balises     * Position of balises
Line 13: Line 13:
     * Identity and name     * Identity and name
     * Length and orientation     * Length and orientation
 +  * Operational data
 +    * Time Tables
   * System configuration   * System configuration
-    * Structure ​of track side elements and associated element controllers (I/O and wiring configuration)+    * HW structure ​of track side elements and the associated element controllers (I/O and wiring configuration)
     * Structure of the network interconnecting the various supporting hardware (network addressing)     * Structure of the network interconnecting the various supporting hardware (network addressing)
     * Radio network structure (radio addressing)     * Radio network structure (radio addressing)
     * Server configuration;​ TMS, RBC     * Server configuration;​ TMS, RBC
-    * Screen layout for signalers interface ​(HMI)+    * Screen layout for operator interfaces ​(HMI and MCe)
  
 ===== "​Where"​ ===== ===== "​Where"​ =====
-The implementation of the RBC and interlocking ​for the WinterTrain ​v4 will include several computers and Arduino-like modules, all of which has to be configured for the actual railway. One approach could be to configure and re-compile the software for each of these modules and computers depending on the actual ​configuration. However, this would require each element controller to have new software when ever e.g. the cabling or track layout was changed.+The implementation of the various features (OBU, RBC, TMS etc.) for the WinterTrain will include several computers and Arduino-like modules, all of which has to be configured for the actual railway. One approach could be to configure and re-compile the software for each of these modules and computers depending on the actual ​model railway. However, this would require each element controller to have new software when ever e.g. the cabling or track layout was changed.
  
-Instead an approach of having the majority of configuration data stored centralized in the computer running the RBC, will be used. The communication network then will be used by the RBC to distribute relevant configuration data to the various controllers. Site specific data will be organized and stored as follows. For each sub-system is listed, which configuration data will be included in that sub-system.+Instead an approach of having the majority of configuration data stored centralized in the computer running the RBC, will be used. The communication network then will be used by the RBC to distribute relevant configuration data to the various ​element ​controllers. ​The same apply to screen layout, which as well will be stored in the core system and distributed to each operator place. 
 + 
 +Site specific data will be organized and stored as follows. For each sub-system is listed, which configuration data will be included in that sub-system.
  
   * OBU   * OBU
     * Train identity     * Train identity
-    * Radio network address of the OBU it self and the associated DMI+    * Radio network address of the OBU 
 +    * Radio network address of the associated DMI
   * DMI   * DMI
     * Radio network address of DMI and associated OBU     * Radio network address of DMI and associated OBU
Line 33: Line 38:
     * Track topology     * Track topology
     * Balise position     * Balise position
-    ​* <​del>​Route specification</​del>​ +    * Configuration of HMI and MCe user interfaces ​including screen layout
-    ​* Configuration of HMI user interface ​including screen layout+
     * <​del>​HMI user data</​del>​     * <​del>​HMI user data</​del>​
     * Communication network structure     * Communication network structure
     * Configuration of element controllers like which signal is connected to which output driver     * Configuration of element controllers like which signal is connected to which output driver
     * Train properties (ID, length and position of balise reader antenna)     * Train properties (ID, length and position of balise reader antenna)
 +  * Element controller (EC)
 +    * Network address of the EC
 +    * Number and type of element drivers implemented by that EC
 +  * TMS
 +    * Time Tables
   * HMI User interface   * HMI User interface
     * IP address of RBC     * IP address of RBC
-  * Element controller +  * MCe User Interface for maintenance 
-    * Network ​address +    * IP address of RBC
-    * Number and type of element drivers ​+
  
  

it/wintertrainv4/design/configuration.txt · Last modified: 2020/01/05 10:49 by jabe