Route System

Overview

The Route System in Railux 6 Ultra provides a central reference for all train routes on the network. Each route entry includes:

• A route name and code

• The ordered list of stations served (matching station sensor API names)

• Suggested travel times between stops, supporting timetable adherence and passenger information

This library supports both manual driving and ATO with manual supervision, providing route and schedule data for display, monitoring, and manual operations—not for fully automated ATO.

---

File Location

Script Path: ReplicatedStorage.RouteLibrary

---

Data Structure

Each route is an entry in a Lua table (Library), indexed by a unique route ID.

Field	Type	Description
Name	String	The public-facing name of the route (e.g. “Eureka Line (Southbound)”).
Code	String	The unique route code (e.g. “E01”).
Stations	Table	Ordered list of station names (must match the StationName StringValue in each StationSensor’s API).
Schedule	Table	Suggested travel times (seconds) between each leg; used for timetables, supervision, and display.

---

Example Route Definition

Library[1] = {
    Name = "Eureka Line (Southbound)",
    Code = "E01",
    Stations = {"StationA", "StationB", "StationC"},
    Schedule = {10, 30, 30}, -- [1]=to A, [2]=A→B, [3]=B→C
}

---

Example Library Structure

local Library = {}

Library[1] = {
    Name = "Eureka Line (Southbound)",
    Code = "E01",
    Stations = {"StationA", "StationB", "StationC"},
    Schedule = {10, 30, 30},
}

Library[2] = {
    Name = "Eureka Line (Northbound)",
    Code = "E02",
    Stations = {"StationC", "StationB", "StationA"},
    Schedule = {10, 30, 30},
}

Library[3] = {
    Name = "Placeholder",
    Code = "XXX",
    Stations = {},
    Schedule = {},
}

return Library

---

Usage

• Manual Driving: Display the current route, next station, and expected travel times to the driver and passengers.

• ATO with Supervision: Supervisors can monitor adherence to the scheduled times or use the data for announcements and route displays.

• Passenger Information: Use the route and schedule data to show upcoming stops and estimated arrival times on in-train or station displays.

---

Best Practices

• Station names must match the StationName StringValue in each StationSensor’s API.

• Travel times are advisory, supporting timetables and announcements.

• Route codes should be unique and descriptive.

---

Example Use Case

A display script can look up the current route to show the sequence of stations and target times, helping both manual drivers and passengers stay informed about the journey ahead.

---

Note: This route system is not intended for fully automated ATO control, but provides essential reference data for manual and supervised operations.

---