User:Vitus - Revision history

Vitus: That's all for now I think :)

2010-08-24T12:34:11Z

That's all for now I think :)

Vitus: Fail-safe overflow

2010-08-24T12:29:19Z

Fail-safe overflow

Vitus: Tri-level designs

2010-08-24T12:00:39Z

Tri-level designs

Vitus: Keep the naming consistent

2010-08-23T21:22:36Z

Keep the naming consistent

Vitus: broken link

2010-08-23T21:13:48Z

broken link

Vitus: LED calculator

2010-08-23T21:13:17Z

LED calculator

Vitus: Converter

2010-08-23T20:51:59Z

Converter

Vitus: broken link

2010-08-13T20:20:05Z

broken link

Vitus: Fail-safe NOT/OR gate

2010-08-13T20:19:19Z

Fail-safe NOT/OR gate

Vitus at 19:32, 13 August 2010

2010-08-13T19:32:56Z

← Older revision		Revision as of 12:34, 24 August 2010
Line 116:		Line 116:
	*[[Media:Pf_problem_v5.sav\|Savegame]] (r20279; fixed PBS overflows to work with >r19896)		*[[Media:Pf_problem_v5.sav\|Savegame]] (r20279; fixed PBS overflows to work with >r19896)

−
−	~~To be continued...~~

	[[Category:Usual Suspects]]		[[Category:Usual Suspects]]

← Older revision		Revision as of 12:29, 24 August 2010
Line 81:		Line 81:
	Resources:		Resources:
	*[[Media:Tri_level_4.sav\|Savegame]] (r20594)		*[[Media:Tri_level_4.sav\|Savegame]] (r20594)
		+
		+
		+	==Simple fail-safe conditional overflow & injection==
		+
		+	Conditional overflows with conditional injection (unlike classic timer-based injection) are relatively new design, invented by [[User:V453000\|V453000]] and used for the first time in larger scale in [[PublicServer:Archive_-_Games_181_-_190#gameid_188\|PSG#188]]. Typical RoRo overflows (with one entry track) are fail-safe by design and don't need any further improvements to keep them working. On the other side, terminus overflows aren't fail-safe by design and need special approach: they require either waiting space (overflow with trains in waiting space) or waiting space alongside with fail-safe construction (trains do not use waiting space unless they would get stuck at entry signal). The second approach is better, because we want trains to wait either in station or in overflow depot (that's the main point of overflow, after all), however, this approach also involves tons of fail-safe tracks (which can get very confusing with large stations) and few flaws (waiting space is not prioritized, which can result in unwanted release of train in overflow).
		+
		+	This new design makes sure we do not need fail-safe tracks (because the overflow is fail-safe by design), waiting spaces are completly prioritized and (like in the fail-safe approach mentioned above) only used if the entering train would get stuck.
		+
		+	Resources:
		+	*[[Media:Simple_failsafe_overflow.sav\|Savegame]] (r20279)

← Older revision		Revision as of 12:00, 24 August 2010
Line 71:		Line 71:
	Resources:		Resources:
	*[[Media:Calc2.sav\|Savegame]] (r19523)		*[[Media:Calc2.sav\|Savegame]] (r19523)
		+
		+
		+	==Tri-level designs==
		+
		+	The aim of this savegame is to provide some examples of tri-level designs, so they are easily accessable without having to go through many other savegames. The collection isn't currently complete, though.
		+
		+	The first two termini stations aren't new designs and you can already find them in many PSGs (e.g. [[PublicServer:Archive_-_Games_171_-_180#gameid_180\|PSG#180]] or [[PublicServer:Archive_-_Games_181_-_190#gameid_182\|PSG#182]]). The next two are however new designs. Tri-level balancer reduces width of full (everything-to-everything) n->3 balancer by third and tri-level train reverser has enough capacity to keep ML flow undisrupted, while saving valuable space (for TL14, full turn might take as much as 46x42 tiles, while train reverser for such TL takes ''just'' 33x8).
		+
		+	Resources:
		+	*[[Media:Tri_level_4.sav\|Savegame]] (r20594)

@@ Line 55: / Line 55: @@
-==Green burst convertor==
+==Green burst converter==
-This tool is supposed to convert red signal of any length into few ticks of green signal. It is based on Fail-safe NOT/OR gate (mentioned above), but the distribution of prioritized lines is changed to provide green output only if the train is moving (i.e. when we can be sure the train isn't going to say in signal block for longer period). There are two possibilities on when to trigger burst of green signal - either at the beginning or at the end (of red state of input presignal). Convertor which provides green burst at the end (of duration) is much easier to build, however, in some cases we need green burst at the beginning (and it is also more logical). This layout then becomes pretty complicated, because we either have to use some tricks with priority or use a logic gate. See savegame for examples.
+This tool is supposed to convert red signal of any length into few ticks of green signal. It is based on Fail-safe NOT/OR gate (mentioned above), but the distribution of prioritized lines is changed to provide green output only if the train is moving (i.e. when we can be sure the train isn't going to say in signal block for longer period). There are two possibilities on when to trigger burst of green signal - either at the beginning or at the end (of red state of input presignal). Converter which provides green burst at the end (of duration) is much easier to build, however, in some cases we need green burst at the beginning (and it is also more logical). This layout then becomes pretty complicated, because we either have to use some tricks with priority or use a logic gate. See savegame for examples.
 This tool can be used for precise train counters and possibly some advanced logic systems.

← Older revision		Revision as of 21:13, 23 August 2010
Line 70:		Line 70:

	Resources:		Resources:
−	*[[Media:~~Calc~~.sav\|Savegame]] (r19523)	+	*[[Media:Calc2.sav\|Savegame]] (r19523)

← Older revision		Revision as of 21:13, 23 August 2010
Line 63:		Line 63:
	Resources:		Resources:
	*[[Media:Green_burst_counter.sav\|Savegame]] (r20594)		*[[Media:Green_burst_counter.sav\|Savegame]] (r20594)
		+
		+
		+	==LED calculator==
		+
		+	Long time ago, I got an idea to combine [http://www.tt-forums.net/viewtopic.php?t=42480&p=774856\| my previous calculator] (simple adder) with [http://www.tt-forums.net/viewtopic.php?f=29&t=37902\| LED counter]. The main point was to see, if such calculator would be possible to build and because of that, the calculator itself is fairly ''simple'' - it can add numbers up to 9 + 9. However, it is fully working and totally fail-safe (i.e. all logic gates are fail-safe). Most of the calculator is LED -> binary and binary -> LED converter, the adder is just small array of half bit adders at the bottom. Just note that the savegame isn't commented.
		+
		+	Resources:
		+	*[[Media:Calc.sav\|Savegame]] (r19523)

← Older revision		Revision as of 20:51, 23 August 2010
Line 53:		Line 53:
	Resources:		Resources:
	*[[Media:Failsafe_gate.sav\|Savegame]] (r20279)		*[[Media:Failsafe_gate.sav\|Savegame]] (r20279)
		+
		+
		+	==Green burst convertor==
		+
		+	This tool is supposed to convert red signal of any length into few ticks of green signal. It is based on Fail-safe NOT/OR gate (mentioned above), but the distribution of prioritized lines is changed to provide green output only if the train is moving (i.e. when we can be sure the train isn't going to say in signal block for longer period). There are two possibilities on when to trigger burst of green signal - either at the beginning or at the end (of red state of input presignal). Convertor which provides green burst at the end (of duration) is much easier to build, however, in some cases we need green burst at the beginning (and it is also more logical). This layout then becomes pretty complicated, because we either have to use some tricks with priority or use a logic gate. See savegame for examples.
		+
		+	This tool can be used for precise train counters and possibly some advanced logic systems.
		+
		+	Resources:
		+	*[[Media:Green_burst_counter.sav\|Savegame]] (r20594)

← Older revision		Revision as of 20:20, 13 August 2010
Line 52:		Line 52:

	Resources:		Resources:
−	*[[Failsafe_gate.sav\|Savegame]] (r20279)	+	*[[Media:Failsafe_gate.sav\|Savegame]] (r20279)

@@ Line 39: / Line 39: @@
 *[[Media:Train_stopper.sav|Savegame]] (r20279)
 *[[User:Vitus/Train_Stopper|Detailed description]]
@@ Line 48: / Line 62: @@
-Some examples of how to deal with very high train speeds are included in savegame. The "speedproof" concept isn't very useful, because normally used parameter (3500) is usually enough to keep reaction time very low and higher values rarely improve this time. High parameter however greatly reduces reaction time of single-train based logic gates (up to some speed, of course). On the other side, the need for unnecessarily more complicated NOT gates likely outweighs the actualy gain.
+Some examples of how to deal with very high train speeds are included in savegame. The speedproof concept isn't very useful, because normally used parameter (3500) is usually enough to keep reaction time very low and higher values rarely improve this time. High parameter however greatly reduces reaction time of single-train based logic gates (up to some speed, of course). On the other side, the need for unnecessarily more complicated NOT gates likely outweighs the actualy gain.
 Resources:

← Older revision		Revision as of 19:32, 13 August 2010
Line 46:		Line 46:
	*'''at TL1''' stop working with parameter 3816 or higher		*'''at TL1''' stop working with parameter 3816 or higher
	*'''at TL0.5''' do not work, due to insane train acceleration		*'''at TL0.5''' do not work, due to insane train acceleration
		+
		+
		+	Some examples of how to deal with very high train speeds are included in savegame. The "speedproof" concept isn't very useful, because normally used parameter (3500) is usually enough to keep reaction time very low and higher values rarely improve this time. High parameter however greatly reduces reaction time of single-train based logic gates (up to some speed, of course). On the other side, the need for unnecessarily more complicated NOT gates likely outweighs the actualy gain.
		+
		+	Resources:
		+	*[[Media:Speedproof.sav\|Savegame]] (r20279)