TimeTable - Revision history

Charlie at 01:16, 26 January 2016

2016-01-26T01:16:24Z

← Older revision		Revision as of 01:16, 26 January 2016
Line 20:		Line 20:
	:(string)		:(string)
	:Identifier used to like with movement orders in the movement order table (Train_ID_SOFT). This allows for trains with the same train ID to have different movement orders.		:Identifier used to like with movement orders in the movement order table (Train_ID_SOFT). This allows for trains with the same train ID to have different movement orders.
	a
	;Train_ID		;Train_ID
	:(string)		:(string)

Charlie at 01:15, 26 January 2016

2016-01-26T01:15:58Z

← Older revision		Revision as of 01:15, 26 January 2016
Line 20:		Line 20:
	:(string)		:(string)
	:Identifier used to like with movement orders in the movement order table (Train_ID_SOFT). This allows for trains with the same train ID to have different movement orders.		:Identifier used to like with movement orders in the movement order table (Train_ID_SOFT). This allows for trains with the same train ID to have different movement orders.
			a
	;Train_ID		;Train_ID
	:(string)		:(string)
Line 218:		Line 218:
	;ActivityCode		;ActivityCode
	:(string)		:(string)
	:Semi-colon delimited list of "activity codes" or "traffic codes." Refer to the article on [[Traffic Codes\|Traffic Codes]] for more information.		:Semi-colon delimited list of "activity codes" or "traffic codes." When an activity code is made active, trains with an activity code in this column become '''active'''. Refer to the article on [[Traffic Codes\|Traffic Codes]] for more information.

	;InactivityCode		;InactivityCode
	:(string)		:(string)
	:Semi-colon delimited list of "activity codes" or "traffic codes." Refer to the article on [[Traffic Codes\|Traffic Codes]] for more information.		:Semi-colon delimited list of "activity codes" or "traffic codes." When an activity code is made active, trains with an activity code in this column become '''inactive'''. Refer to the article on [[Traffic Codes\|Traffic Codes]] for more information.

	;SpawnInfo		;SpawnInfo

Charlie: InactivityCode column

2016-01-26T01:10:11Z

InactivityCode column

← Older revision		Revision as of 01:10, 26 January 2016
Line 218:		Line 218:
	;ActivityCode		;ActivityCode
	:(string)		:(string)
	:~~Comma~~-~~separated~~ list of "activity codes" or "traffic codes." Refer to the article on [[Traffic Codes\|Traffic Codes]] for more information.		:Semi-colon delimited list of "activity codes" or "traffic codes." Refer to the article on [[Traffic Codes\|Traffic Codes]] for more information.

			;InactivityCode
			:(string)
			:Semi-colon delimited list of "activity codes" or "traffic codes." Refer to the article on [[Traffic Codes\|Traffic Codes]] for more information.

	;SpawnInfo		;SpawnInfo

ErwinL: RequiresTrain added

2015-02-01T13:42:41Z

RequiresTrain added

← Older revision		Revision as of 13:42, 1 February 2015
Line 36:		Line 36:
	:(int)		:(int)
	:Database ID of the train this train depends on - this means that the specified train must have already left the simulation for this train to spawn.		:Database ID of the train this train depends on - this means that the specified train must have already left the simulation for this train to spawn.
			:Groups for trains depending on each other are defined in the TrainUnits table

	;DependsOnDelay		;DependsOnDelay
	:(int)		:(int)
	:Defines the length of time between the first train despawning and this train spawning. Value is in minutes.		:Defines the length of time between the first train despawning and this train spawning. Value is in minutes.
			:No value is a default of 30 minutes.

			;RequiresTrain
			:(int)
			:Database ID of the train this train requires and depends on - this means that the specified train must have entered and have left the simulation for the next train belonging to the same group to spawn.
			:The train requiring and depending on a train must also have the same database ID filled in in DependsOnTrain
			:Groups for trains depending on each other are defined in the TrainUnits table

	;EntryPoint		;EntryPoint

Charlie at 18:53, 22 December 2014

2014-12-22T18:53:08Z

← Older revision		Revision as of 18:53, 22 December 2014
Line 233:		Line 233:
	*[...]_CTA		*[...]_CTA
	the roll number for the PID's		the roll number for the PID's

			;MaxSpeed
			:(int)
			:When present, defines the maximum speed (in km/h) that a train can move. When ''not'' present, the train's max speed is calculated from the individual vehicles. This value is useful when the train should move slowly than otherwise is normal.


	{{DeveloperNavBottom}}		{{DeveloperNavBottom}}

SignalAdmin at 13:34, 28 February 2013

2013-02-28T13:34:48Z

← Older revision		Revision as of 13:34, 28 February 2013
Line 63:		Line 63:
	:(int)		:(int)
	:Defines the direction of the train when being placed. 0 = left, 1 = right.		:Defines the direction of the train when being placed. 0 = left, 1 = right.

			;outOfGaugeType
			:defines the type of out-of-gauge train. Currently only A,B,C,D for Germany are implemented

			;outOfGaugeInstructions
			:defines various special instructions for this out-of-gauge train.
			:currently implemented: "TR:123AT_124AT_125AT" will create list in fax with "tracks train needs to follow to avoid collisions".

	;ConsistTemplateID		;ConsistTemplateID

Charlie at 16:32, 16 January 2013

2013-01-16T16:32:07Z

← Older revision		Revision as of 16:32, 16 January 2013
Line 75:		Line 75:
	:(int)		:(int)
	:''(optional)''		:''(optional)''
	:Used to indicate the path template to use for routing the train when it is going in a '''left-ward'' direction.		:Used to indicate the path template to use for routing the train when it is going in a '''left-ward''' direction. Useful for a train that requires a different path depending on which direction it's going.

	;PathTemplateIDRight		;PathTemplateIDRight
	:(int)		:(int)
	:''(optional)''		:''(optional)''
	:Used to indicate the path template to use for routing the train when it is going in a '''right-ward'' direction.		:Used to indicate the path template to use for routing the train when it is going in a '''right-ward''' direction. Useful for a train that requires a different path depending on which direction it's going.

	;Origin		;Origin

Charlie at 16:27, 16 January 2013

2013-01-16T16:27:01Z

@@ Line 71: / Line 71: @@
 :(int)
 :Used to indicate the path template to use for routing the train.
 ;Origin

Charlie at 20:53, 7 March 2012

2012-03-07T20:53:33Z

← Older revision		Revision as of 20:53, 7 March 2012
Line 194:		Line 194:
	:(string)		:(string)
	:Comma-separated list of "activity codes" or "traffic codes." Refer to the article on [[Traffic Codes\|Traffic Codes]] for more information.		:Comma-separated list of "activity codes" or "traffic codes." Refer to the article on [[Traffic Codes\|Traffic Codes]] for more information.

			;SpawnInfo
			:(string)
			:''optional''
			:Defines additional spawning behaviour. See [[SpawnInfo]].

	There may be other fields in this table. Some of these fields are used to automatically generate the values in other fields, such as the TimeTableStops field. This is done with external tools that are separate from the simulation. Other fields are used only for the purpose of generating a printed timetable and are used by either passengers or dispatchers only and are not used by the simulation. As a timetable developer, you are free to add any fields you like for your own purposes. These fields will be ignored by the simulation.		There may be other fields in this table. Some of these fields are used to automatically generate the values in other fields, such as the TimeTableStops field. This is done with external tools that are separate from the simulation. Other fields are used only for the purpose of generating a printed timetable and are used by either passengers or dispatchers only and are not used by the simulation. As a timetable developer, you are free to add any fields you like for your own purposes. These fields will be ignored by the simulation.

Charlie at 21:02, 3 December 2011

2011-12-03T21:02:00Z

← Older revision		Revision as of 21:02, 3 December 2011
Line 96:		Line 96:
	:Provides additional steering information for specific trains. This information is needed to assist the coworkers to give more accurate prompting. It also is used during the pre-simulation process to automatically route traffic more accurately.		:Provides additional steering information for specific trains. This information is needed to assist the coworkers to give more accurate prompting. It also is used during the pre-simulation process to automatically route traffic more accurately.

	The data is semi-colon delimited. Each item is composed of three things: the station code, a signal name, and a track name. The train is then routed from that signal to the given track. Example:		:The data is semi-colon delimited. Each item is composed of three things: the station code, a signal name, and a track name. The train is then routed from that signal to the given track. Example:

	KB;A902;207AT		KB;A902;207AT

	This specifies that in Bonn, the train should be routed from signal A902 to track 207AT.		:This specifies that in Bonn, the train should be routed from signal A902 to track 207AT.

	Multiple entries are separated by semicolons:		:Multiple entries are separated by semicolons:

	STATION;SIGNAL1;TRACK1;STATION;SIGNAL2;TRACK2;STATION;SIGNAL3;TRACK3		STATION;SIGNAL1;TRACK1;STATION;SIGNAL2;TRACK2;STATION;SIGNAL3;TRACK3

	The station entry may be left empty if the layout does not have a station code defined:		:The station entry may be left empty if the layout does not have a station code defined:

	;SIGNAL1;TRACK1;;SIGNAL2;TRACK2;;SIGNAL3;TRACK3		;SIGNAL1;TRACK1;;SIGNAL2;TRACK2;;SIGNAL3;TRACK3