You are here: Wiki > start > simulations > brighton

Locked Page is locked

Table of Contents

SimSig Brighton
Sim Versions
Timetables
Scenario Description
Shortcut Keys
Train Describer
Slots and Yard Permissions
Unusual Signalling Arrangements
Multiplay and Chaining
Regulation Techniques
Timetables
Known Issues / Bugs
Reference Section
Signal Number Plan
Platform Lengths
Sidings Lengths
Reverse T.C. Lengths

SimSig Brighton

Sim Versions

Version Status Scroll/Views
Loader
Published Comments
V4.0 Donationware S L 05/11/13 Available from the Download section
V1.2b3 Donationware S 02/07/13 No longer available for download
V2.227.5 (Beta version) Donationware S 21/08/11 No longer available for download

Timetables

=

Scenario Description

Title Published Author Comments
Brighton September 2009 v1.03 11/11/10 TBC Bundled with v2.227.5
Brighton 15th October 2009 v1.4 02/07/13 TBC Bundled with v1.2b3
Brighton 15th October 2009 (0445) v1.4 02/07/13 TBC Bundled with v1.2b3
Brighton April 2012 V2.3 10/10/12 TimTamToe Available from Download section
Brighton 2014 V1.0 20/05/14 John Bessant Available from Download Section

The third in the series of Three Bridges simulations, Brighton covers panels five and six, from Balcombe to Patcham Tunnel for panel five, and onwards to Brighton for panel six.

The simulation includes the main line from London to Brighton, the lines towards Lewes from both Brighton and Keymer Junction, and the coast line towards Shoreham. In total approximately 35 route miles are included. There is just one CCTV level crossing , near Keymer Junction.

Shortcut Keys

Pressing and holding down the shift key then pressing one of the following letter keys will move the simulation screen to the designated area:

  • B - Brighton
  • H - Haywards Heath
  • K - Keymer Junction
  • L - Lovers Walk Depot
  • P - Preston Park
  • V - Hove

Train Describer

  • Dividing trains at Haywards Heath will need the headcode for their dividing portion interposed manually. Depending on the timetable, this is normally the rear portion. The headcode will usually remain with the divided portion after the rest of the train has departed
  • Joining trains at Haywards Heath can be ignored as the second train to arrive will lose its description after the conjoined train fully departs the platform. However, ensure the portions joined in the correct order and thus have their correct headcode upon departure.
  • When running trains "wrong line", the

    train descriptions will initially step to the first signal in the "right direction", followed by the intermediate station, if appropriate, followed by the signal at the far end of the reversible section. As an example, working from Preston Park to Keymer Junction will result in a step from Signals T420/T422 to T421, then T421 to Hassocks (T389), then Hassocks to T370.

  • Brighton station has two train describer berths per platform - most recent arrival (buffer-end berth) and first departure out (Signal-end berth). If a train divides, or double docking is performed, then you are advised to use sticky notes to remind you of what is where. Trains leaving will only pick up the TD from the departure berth; TDs in the arrival berth are ignored for these, and a

    Non-Described Special Description (NDSD) will be inserted for trains departing without a TD in the leftmost berth. Always interpose outbound trains in the left hand berth.

  • Please note that dividing or double docking trains will therefore need their headcode inserted into the departure berth after any trains in front have departed.
  • With the exception of Lovers Walk Depot (L2, L11, L21 and West Carriage Road), siding exit signals are not provided with TD berths. Therefore, the signaller must interpose the description at the first appropriate signal.
  • =

    Slots and Yard Permissions

  • Lovers Walk Depot can see which trains are approaching and thus you do not need permission for trains to enter - although you do still need the slot. To avoid delays as much as possible, it is a good idea to request the slot as the train gives TRTS at Brighton or Preston Park, this should usually be granted by the time the driver calls in from the signal.
  • You need to obtain permission from Hove Yard for trains to enter. Use the telephone facility to call the yard and offer the train, before signalling it in once accepted. It is a good idea to hold trains at Brighton or Preston Park until permission is given, otherwise you could potentially gridlock the area if permission is not given soon enough.

No other sidings or yards need permission.

=

Unusual Signalling Arrangements

All these features are true to life, unless otherwise stated.

  • Signal T335RR is fixed at double yellow.
  • Signals T331R and T335R are fixed at yellow.
  • Signals T337, T339 and T343 will not show a proceed aspect until a route is set towards them.
  • Signal T1279 (Brighton West Carriage road) must be manually cancelled, whereupon it will then time-out before the route releases.
  • There are no routes to Signal T349. Platform 3 at Haywards Heath can only be entered from the south end but trains can depart back to the south from any platform.
  • Signal T342 is a fixed red, therefore no routes are possible from this signal. As such, do not send trains continuing in the Up direction into Platform 2 at Haywards Heath.
  • The "platform" for Haywards Heath Platform 1 extends beyond signal T345, towards the spur. This allows for trains to pull past the signal to fit into the platform. This should only be used for any freight trains that need to run-round.
  • There are several alternative routes between the same signals at Brighton. The interlocking will automatically set the pre-programmed preferred route if it is available, otherwise it will try the programmed alternatives. To select a non-preferred route, manually key the points before setting the route. Not every logical possibility is available in the interlocking.
  • The

    Direction of Flow arrows are normally lit in the "normal" direction for each section of line. Setting a "wrong road" route will cause the "normal" direction arrow to extinguish and the "reverse" direction to light. When the route releases, the "reverse" direction will extinguish and the "normal" direction will light. In real life these take a few seconds to switch back to the "normal" direction.

  • Signals T665 and T667 at Brighton read over a staff crossing with white lights. Due to the proximity of this crossing to those signals, they will not

    clear for 20 seconds after setting the route to allow any users to clear the crossing. An exception to this is when a train is leaving platform 3 towards signal T667 whereupon the signal will clear immediately if the train has yet to pass signal T450.

  • Various sets of points in depot, yard and siding areas are not self-normalising and must be manually replaced to normal after the passage of a train. The track will flash white in the immediate area of that particular set of points, and as there is a message event for this on

    F3 Options - Messages tab you will see a message appear in the messages window too. You can also set a sound effect to go off when this occurs.

  • Hove Platforms 1 and 2 are

    permissive in the Up direction only (ie only trains from Portslade can be called on into the platform) from main signals. All platforms are permissive in both directions from shunt signals (see next note).

  • Hove has

    Track Circuit Overrides for each platform. These allow shunt signals with routes set into occupied platforms to clear. To operate, the platform track must be occupied and the shunt route (from T1400/T1398/T1391/T1393) set, and then the appropriate override must be pulled (right-click). The signal will then show a proceed aspect. The override is a one-shot feature and will reset once the route is cancelled by the passage of a train or by cancelling the route.

  • The Ardingly Branch is a non-electrified single track freight-only line leading to a run-round loop at Ardingly itself, and is only about a mile and a half long. Although an entry point has been provided here in SimSig, trains will not exit here and will thus need to be timetabled in and back out again as the train will not "fall off" when it reaches Ardingly. When the train is on the branch, the "train in section" indication will show in red until the train leaves the single line towards signal T337. The train description from Haywards Heath will step from signal T336 to T331 but will need cancelling manually from T331.
  • =

    Multiplay and Chaining

Brighton will be able to chain with the unreleased Gatwick. When chained, the following features become enabled:

  • The fast and slow line

    approach berths at Balcombe Tunnel Junction become active

  • Bi-directional working is possible, by Gatwick sending trains via the up line to Haywards Heath

This simulation can be handled by a single user although that user will be quite busy! A Sunday timetable may be easier.

The simulation can also chain with Lancing at Portslade

=

Regulation Techniques

  • Trains to/from the West Carriage Road can only use Platform 2, and thus can only then proceed towards Hove.
  • Non-stop trains at Haywards Heath may use any platform without penalty, so use that to your advantage if you have a delayed train ahead of it.
  • Make sure you get the level crossing barriers at Keymer LC down in time for trains to/from Lewes. As a general rule, start lowering the barriers for down trains after they leave Haywards Heath, and for up trains after they leave Plumpton.
  • Take care with trains that arrive at Brighton from Hove and proceed towards Preston Park, or vice versa. These trains can only use Platform 3, and as such require the buffer-stop end of the platform so as to be standing behind signal T450.
  • If a failure prevents use of the up or down main lines between Preston Park and Brighton then the carriage line may be used for passenger-carrying trains, provided the route is set and

    proved throughout. Set the routes in reverse order so that the last route you set is the one towards signal T1243 for a down train or the one towards signal T1262 or T1250 for an up train. Note: During this time, no other trains other than that one passenger-carrying train may occupy the Carriage Line.

  • =

    Timetables

Supplied with the simulation:

User-supplied timetables:

  • TBD

How to write timetables:

Known Issues/Bugs

  • In multiplay, calls from signals T699; T673; and T677 are sent to Workstation 5 instead of Workstation 6.
  • At Hove, no route can be set from 684 into platforms 1 or 2 if a warner route is set between 673 and 677. Vice versa, no route can be set from 673 to 677 if a warner route is set from 684 to 680.

    Forum thread .

See also: Known Loader bugs

Reference Section

Signal Number Plan

Signal Number Plan

This is an Adobe Acrobat PDF file. If you don't have Adobe Acrobat Reader installed on your computer you can get a free download of the latest version from the Adobe website . When checked during March 2013, it had reached v11 and the download size was just under 50MB.

TIPLOC Codes

Signal Box Prefix Codes

* Fringe box, signals not controlled by this sim.
Code Box
LG Lancing*
LW Lewes*

Non-prefixed signals are controlled by Three Bridges (T)

Platform Lengths

Aldrington

Platform Length (carriages) Length (metres)
1 4 85.1
2 4 85.2

Balcombe

Platform Length (carriages) Length (metres)
1 12 250.6
2 8 166.0

Brighton

Platform Length (carriages) Length (metres) Notes
1 12 234.7
2 12 278.3
3 12 250.5 from Preston Park direction
3 4 85.0 from Hove direction
4 12 250.5
5 12 248.4
6 12 250.2
7 12 240.5
8 12 240.0

Burgess Hill

Platform Length (carriages) Length (metres)
1 12 262.1
2 12 262.1

Cooksbridge

Platform Length (carriages) Length (metres)
1 6 137.8
2 6 132.8

Falmer

Platform Length (carriages) Length (metres)
1 7 157.9
1 7 156.1

Hassocks

Platform Length (carriages) Length (metres)
1 12 274.3
2 12 274.3

Haywards Heath

Platform Length (carriages) Length (metres)
1 12 241.4
2 12 241.4
3 12 241.4
4 12 241.4

Hove

Platform Length (carriages) Length (metres)
1 12 241.1
2 12 241.1
3 12 241.1

London Road (Brighton)

Platform Length (carriages) Length (metres)
1 7 138.2
2 7 143.7

Moulsecoomb

Platform Length (carriages) Length (metres)
1 4 85.0
2 4 86.0

Plumpton

Platform Length (carriages) Length (metres)
1 8 167.3
2 8 166.8

Portslade

Platform Length (carriages) Length (metres)
1 12 249.6
2 8 152.3

Preston Park

Platform Length (carriages) Length (metres)
1 12 246.9
2 12 246.9
3 12 246.9

Wivelsfield

Platform Length (carriages) Length (metres)
1 12 246.9
2 12 246.9

Sidings Lengths

Preston Park Up Sdgs

Siding Length (carriages) Length (metres) Power Supply (Type)
1 12 256 DC 3rd Rail
2 12 256 DC 3rd Rail

Hove Yard

Siding Length (carriages) Length (metres) Power Supply (Type)
1 12 256 DC 3rd Rail
2 12 256 DC 3rd Rail
3 12 256 DC 3rd Rail
4 12 256 DC 3rd Rail

Hove Up Sidings

Siding Length (carriages) Length (metres) Power Supply (Type)
1 10 220 DC 3rd Rail
2 12 256 DC 3rd Rail

Reverse T.C. Lengths

Hove East Reverse

Signal Type LOS Length (carriages) Length (metres) Power Supply (Type)
T1391 Shunt T672 12+ 300 DC 3rd Rail
T1393 Shunt T674 12+ 610 DC 3rd Rail

Hove West Reverse


=

Miscellanea

Signal Type LOS Length (carriages) Length (metres) Power Supply (Type)
T1398 Shunt Up Sdg 1 10 220 DC 3rd Rail
T1400 Shunt LG1 12+ 680 DC 3rd Rail

Hove is often jokingly referred to as "Hove Actually" since when residents are asked if they are from Brighton, they often answer "No, I'm from Hove, actually" - perceived locally to be of a higher social class than Brighton.


Last edited by Maxo11x on 18/12/2018 at 18:16