Upcoming Games

(UTC times)


Full list
Add a game

Upcoming Events

No events to display

Manchester North issues

You are here: Home > Forum > Simulations > Released > Manchester North > Manchester North issues

Page 1 of 1

Manchester North issues 12/07/2021 at 01:10 #140528
Shwam3
Avatar
11 posts
Online
I have come across a handful of issues I've not seen on the forum so far:

- Missing TD step for MN576 (Salford Cent P2) to MN648.
- Trains entering from Newton Heath at MN902 while the route is set into the neck will take the route without question, the sim manual says you may leave this route set and cancel it when a train enters. (Save "210710-234014 sim time 044401.ssg" shows 5S51 just entered about to pass MN902).
- Cannot set any routes from MN904 (cursor moves to exit signal, no message), additionally the cursor position is incorrect.
- Drawings I have show that, since at least 2018, MN905 (GMC siding) is actually a position light numbered MN1655.
- No signalled route from MN903 or MN905 to MET1 stop board.
- TH7300 at Rochdale P3 requires track TECE clear when points PTH418 are normal causing an ACOA on TH7300 when a train arrives into P4 and PTH418 auto-normalises.
- The call-on route from CE27 to CE30 never seems to clear.
- CE50 signal appears to cover the Down Rochdale arrow label.
- Up trains calling at Littleborough will lose their headcode if another train enters quickly behind it, additionally the second train shows as "XXXX Train in front" rather than being stopped at a signal. (Save "210712-014056 sim time 000000.ssg" demonstrates this).

All issues were found while running sim as below (2017-2021 era):
OS: Windows 10 Enterprise 64bit
Loader: SimSig Loader version 5.16; Sim: Simulation Manchester North; data version 2.0
License: Dynamic license in use
TT: Manchester North 2019-01-09 SX v1.0.0
TT filename: Manchester North 2019-01-09 SX.WTT
TT merged: False
Sim upgrade: False
Loader upgrade: False
Save reloaded: False
NERA2017 active at start
NSIMERA active at start
NPROBLEMS active at start
NNONE active at start

Post has attachments. Log in to view them.
https://signalmaps.co.uk
Log in to reply
Manchester North issues 12/07/2021 at 08:25 #140530
Hap
Avatar
985 posts
Thanks for reporting.

I have also been able to replicate all of your reports.
I'll update this post with the relevant Mantis ticket numbers as I create them.

Craig

How to report an issue: www.SimSig.co.uk/Wiki/Show?page=usertrack:reportanissue
Log in to reply
Manchester North issues 12/07/2021 at 09:10 #140531
Hap
Avatar
985 posts
Quote:
- Missing TD step for MN576 (Salford Cent P2) to MN648.

Mantis 34415

Quote:
- Trains entering from Newton Heath at MN902 while the route is set into the neck will take the route without question, the sim manual says you may leave this route set and cancel it when a train enters. (Save "210710-234014 sim time 044401.ssg" shows 5S51 just entered about to pass MN902).

Mantis 34114 #18224

Quote:
- Cannot set any routes from MN904 (cursor moves to exit signal, no message), additionally the cursor position is incorrect.

Mantis 34113

Quote:
- Drawings I have show that, since at least 2018, MN905 (GMC siding) is actually a position light numbered MN1655.

Mantis 18326

Quote:
- No signalled route from MN903 or MN905 to MET1 stop board.

This line has been disconnected to the Mertolink and as far as I am aware in the 2017 onwards era.

Quote:
- TH7300 at Rochdale P3 requires track TECE clear when points PTH418 are normal causing an ACOA on TH7300 when a train arrives into P4 and PTH418 auto-normalises.

Mantis 34112

Quote:
- The call-on route from CE27 to CE30 never seems to clear.

Route needs set to the white arrow for the Shunt signal to clear.

Quote:
- CE50 signal appears to cover the Down Rochdale arrow label.

Mantis 33959
Quote:
- Up trains calling at Littleborough will lose their headcode if another train enters quickly behind it, additionally the second train shows as "XXXX Train in front" rather than being stopped at a signal. (Save "210712-014056 sim time 000000.ssg" demonstrates this).

Mantis 34111

All issues were found while running sim as below (2017-2021 era):
OS: Windows 10 Enterprise 64bit
Loader: SimSig Loader version 5.16; Sim: Simulation Manchester North; data version 2.0
License: Dynamic license in use
TT: Manchester North 2019-01-09 SX v1.0.0
TT filename: Manchester North 2019-01-09 SX.WTT
TT merged: False
Sim upgrade: False
Loader upgrade: False
Save reloaded: False
NERA2017 active at start
NSIMERA active at start
NPROBLEMS active at start
NNONE active at start

How to report an issue: www.SimSig.co.uk/Wiki/Show?page=usertrack:reportanissue
Last edited: 12/07/2021 at 09:23 by Hap
Reason: None given

Log in to reply
Manchester North issues 12/07/2021 at 11:02 #140533
jc92
Avatar
3629 posts
Hap in post 140531 said:
Quote:

No signalled route from MN903 or MN905 to MET1 stop board.

This line has been disconnected to the Mertolink and as far as I am aware in the 2017 onwards era.
Think this ones still a bug - the line beyond the stop board is disconnected but the line up to it remains so the GMC train loco can RR. 34116 now raised

"We don't stop camborne wednesdays"
Log in to reply
Manchester North issues 12/07/2021 at 13:51 #140534
Shwam3
Avatar
11 posts
Online
Quote:
Quote:
- No signalled route from MN903 or MN905 to MET1 stop board.

This line has been disconnected to the Mertolink and as far as I am aware in the 2017 onwards era.

The same drawing as my first post doesn't show either of these routes disconnected or out of use.

Quote:
Quote:
- The call-on route from CE27 to CE30 never seems to clear.

Route needs set to the white arrow for the Shunt signal to clear.

I was trying using the F11 menu to occupy tracks but I now see there's some treadle logic only worked by an actual train.

https://signalmaps.co.uk
Log in to reply
Manchester North issues 12/07/2021 at 13:56 #140535
9pN1SEAp
Avatar
1102 posts
Certainly looks like on Google Maps there's a stop block attached the line at MET1 (between the two road bridges).
Jamie S (JAMS)
Log in to reply
Manchester North issues 12/07/2021 at 14:37 #140536
Splodge
Avatar
701 posts
Online
When I worked on Metrolink there was a stop board; beyond that some sleepers chained across the track and a gate/barrier of some sort with a red 'stop' marker. The points and physical connection were there still (points clipped, scotched and unworked), and this appears to be the case still from a recent cab ride video: https://youtu.be/WxSf7OWJWuw?t=2829
There's the right way, the wrong way and the railway.
Log in to reply
The following user said thank you: Hap
Manchester North issues 12/07/2021 at 14:42 #140537
Hap
Avatar
985 posts
Disconnected probably isn't the best word. There is a sleeper with stop board on the railhead at the location of the gate and de-railer closer to the metrolink junction.

https://youtu.be/WxSf7OWJWuw?t=2835

The details have been left for the dev on the mantis ticket and hopefully he'll be able to shed some more light on that area.
There should be a route to the MET1 to allow the RR though, so JC as documented that. 905 signal should be a position light which hasn't carried forward from the 2009-2017 era.

Ta
Craig

How to report an issue: www.SimSig.co.uk/Wiki/Show?page=usertrack:reportanissue
Log in to reply
Manchester North issues 12/07/2021 at 16:54 #140539
y10g9
Avatar
895 posts
Shwam3 in post 140534 said:
Quote:
Quote:
- No signalled route from MN903 or MN905 to MET1 stop board.

This line has been disconnected to the Mertolink and as far as I am aware in the 2017 onwards era.

The same drawing as my first post doesn't show either of these routes disconnected or out of use.

Shwam, you mention about a drawing in your first post but haven't linked to anything

I've had a look at the controls and other signaling diagrams for that area.
Somehow at the GMC sidings the 2017 to 2021 era, the signals have been reverted to the 1998-2009 data rather than the data which is used in the 2009-2017 era
It is correct that MN905 has no route to MET1. This signal was removed when the Oldham Loop was taken out of Network Rails control.
MN905 was replaced by a Shunt signal MN1655. This signal is missing in this era (it is present in the 2009-2017 era) and has a route that goes to the stop board MET1
MN903 has 2 available routes.
The first is a shunt class route into the GMC Sidings. This was towards MN905 before 2009, and to MN1655 after 2009.
The second route in post 2009 eras is a shunt route to MET1. After the removal of the Oldham Loop, MN903 became a fixed red with PL.

This has been raised in Mantis 34118 which replaces 34116

Log in to reply
Manchester North issues 12/07/2021 at 23:03 #140542
Shwam3
Avatar
11 posts
Online
Attached are the relevant portions of the plan.




Post has attachments. Log in to view them.
https://signalmaps.co.uk
Log in to reply
The following user said thank you: y10g9
Manchester North issues 13/07/2021 at 04:07 #140543
y10g9
Avatar
895 posts
Thanks Shwam.
That tally’s with the plans I was working from.

Log in to reply
Manchester North issues 15/07/2021 at 12:58 #140590
9pN1SEAp
Avatar
1102 posts
With regards to #34111 I had a goods train right behind 1J11 showing "stopped at PN321", and its code (6M36) overwrote the approach berth before stepping into berth THJ7310 when 1J11 departed Littleborough. If that's of any help.

Thanks
Jamie

Jamie S (JAMS)
Log in to reply
Manchester North issues 15/07/2021 at 14:15 #140592
Hap
Avatar
985 posts
9pN1SEAp in post 140590 said:
With regards to #34111 I had a goods train right behind 1J11 showing "stopped at PN321", and its code (6M36) overwrote the approach berth before stepping into berth THJ7310 when 1J11 departed Littleborough. If that's of any help.

Thanks
Jamie
That's been fixed Cheers Jamie.

Craig

How to report an issue: www.SimSig.co.uk/Wiki/Show?page=usertrack:reportanissue
Log in to reply
The following user said thank you: 9pN1SEAp
Manchester North issues 17/07/2021 at 22:02 #140631
9pN1SEAp
Avatar
1102 posts
Just had a fun one on 2021 TT. 6H60 from Peakstone was routed 598 - 576 - 648 - 857 (opposite running via SFD P2 / MCV P3).

TD didn't step from 576 to 648 and caused alarm "Non-describe train in berth X857" as it headed towards the throat.

I also had a situation earlier in the game where route 595A (P6 down starter) was set, but didn't prove because of loss of normal detection on P6505 (USF-P5), and the TD didn't step from 595 to 583 when the train was talked through red signal with a lit stalk. I haven't yet tried to reproduce this one.

Thanks
Jamie

Post has attachments. Log in to view them.
Jamie S (JAMS)
Last edited: 17/07/2021 at 22:03 by 9pN1SEAp
Reason: None given

Log in to reply
Manchester North issues 18/07/2021 at 06:04 #140633
pedroathome
Avatar
887 posts
576 - 648 was picked up the other day, and is resolved pending an update (Please see first post in this thread)

Step 0595 -> 0583 is triggered by TMCAL, conditions being Route 595(A), and Signal 595 OFF. While I agree this is unusual, this is what the TD stepping table I have appears to state. TMCAL is former Track TAAP, which is what is referenced in sim.

Hope this helps

James

Log in to reply
The following user said thank you: 9pN1SEAp
Manchester North issues 18/07/2021 at 08:34 #140635
9pN1SEAp
Avatar
1102 posts
Thanks James, I suspected the step out of P6 might not happen even when I had managed to set the route
Jamie S (JAMS)
Log in to reply
Manchester North issues 18/07/2021 at 19:30 #140643
pedroathome
Avatar
887 posts
On a side note, I can think of another example where TD stepping is based on point positions, and doesn't consider what route, if any, is set.
Log in to reply
The following user said thank you: 9pN1SEAp