From adc01a0bba29b40278e45c50caa954c435374f7b Mon Sep 17 00:00:00 2001 From: orwell Date: Tue, 6 May 2025 00:43:06 +0200 Subject: Multi-ARS (waiting for multiple routes simultaneously, load-balancing) --- advtrains_interlocking/database.lua | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'advtrains_interlocking/database.lua') diff --git a/advtrains_interlocking/database.lua b/advtrains_interlocking/database.lua index 844d350..5e35dba 100644 --- a/advtrains_interlocking/database.lua +++ b/advtrains_interlocking/database.lua @@ -214,10 +214,11 @@ TCB data structure -- aspect will be set accordingly. routeset = -- Route set from this signal. This is the entry that is cleared once -- train has passed the signal. (which will set the aspect to "danger" again) - route_committed = -- When setting/requesting a route, routetar will be set accordingly, + -- routeset may be a table (e.g. {1,2}) while the route is not committed yet, indicating a wait for multiple routes at once (Multi-ARS) + route_committed = -- When setting/requesting a route, routeset will be set accordingly, -- while the signal still displays danger and nothing is written to the TCs -- As soon as the route can actually be set, all relevant TCs and turnouts are set and this field - -- is set true, clearing the signal + -- is set true, clearing the signal (when this is true, routeset is never a table) aspect = -- The aspect the signal should show. If this is nil, should show the most restrictive aspect (red) signal_name = -- The human-readable name of the signal, only for documenting purposes routes = { } -- a collection of routes from this signal -- cgit v1.2.3