Tyneside Q&A and issues

had a fright train doing a crew change in Newcastle i pulled the signal because i had a anouther fright going though and he was not booked to stop.

the crew was not there the call came in at 01:15 dep time 01:43

But it more than 10 most mints so why did it call up

... i pulled the signal because i had a anouther fright going though ...

Track section TYDM (UM south of Low Fell Jn) seems to have speed limit of 15 mph. Can't see this mentioned elsewhere.

Yes, the expected departure time is the relevant one, not the scheduled time.

the crew was not there the call came in at 01:15 dep time 01:43

Track section TYDM (UM south of Low Fell Jn) seems to have speed limit of 15 mph. Can't see this mentioned elsewhere.

I've got 6E99 in Newcastle at the moment for a crew change now I'm confused...

If you click on the train itself which brings up the stopping pattern, it clearly states Platform 8 for the crew change to take place however the Train List states the same train is in Platform 7 doing the crew change.

So as the train is stopped at signal 486, surely that means it's in Platform 8?

Just wondered if the platforms were done in such a way that Platform 8 was southbound and Platform 7 was northbound, just want to check why I see this.

Apart from that, It's a simulation I never thought would see the light of day so many many many many many thanks to the team for making this possible.

" said:

But it more than 10 most mints so why did it call up

" said:

... i pulled the signal because i had a anouther fright going though ...

:whistle:

Hi

There appears to be a 15mph speed limit on track circuit TYDM on the approach to signal 192 at Low fell junction

Many thanks
Mark

…Thanks, it's already been fixed, will be in the update on Monday or Tuesday. Somehow the leading (or middle) digit 1 fell off the sign.

When chained to York, up trains transferring from Tyneside don't appear to pick up their Current/Next location - trains due to stop at Northallerton are whizzing through non-stop as the York sim thinks the train is still at "Up Main (Darlington)". If the train gets as far as York it sits at a red signal and then calls in to say it's waiting. Down trains transferring from York to Tyneside are fine.

Not sure whether this is a send (Tyneside) or receive (York) problem or a combination of both, so have reported it here. I've got both sims open on the same PC with server enabled, Tyneside using the preset primary port and York using the preset secondary port.

When chained to York, up trains transferring from Tyneside don't appear to pick up their Current/Next location - trains due to stop at Northallerton are whizzing through non-stop as the York sim thinks the train is still at "Up Main (Darlington)". If the train gets as far as York it sits at a red signal and then calls in to say it's waiting. Down trains transferring from York to Tyneside are fine.

Not sure whether this is a send (Tyneside) or receive (York) problem or a combination of both, so have reported it here. I've got both sims open on the same PC with server enabled, Tyneside using the preset primary port and York using the preset secondary port.

I've worked around this by manually updating the Current/Next location via Edit Timetable. On one occasion I was late editing a TPX due to stop at Northallerton and the edit was accepted on approach to Northallerton - the train managed to go from 100mph to 88mph within five seconds and then dropped to 0mph in less than a second! Seems the brakes are decent on 185's but I wouldn't have wanted to be on board.... ;)

" said:

When chained to York, up trains transferring from Tyneside don't appear to pick up their Current/Next location - trains due to stop at Northallerton are whizzing through non-stop as the York sim thinks the train is still at "Up Main (Darlington)". If the train gets as far as York it sits at a red signal and then calls in to say it's waiting. Down trains transferring from York to Tyneside are fine.

Not sure whether this is a send (Tyneside) or receive (York) problem or a combination of both, so have reported it here. I've got both sims open on the same PC with server enabled, Tyneside using the preset primary port and York using the preset secondary port.

I've worked around this by manually updating the Current/Next location via Edit Timetable. On one occasion I was late editing a TPX due to stop at Northallerton and the edit was accepted on approach to Northallerton - the train managed to go from 100mph to 88mph within five seconds and then dropped to 0mph in less than a second! Seems the brakes are decent on 185's but I wouldn't have wanted to be on board.... ;)

could this be related to the issue I reported At post No 5 and post No 7

" said:

When chained to York, up trains transferring from Tyneside don't appear to pick up their Current/Next location - trains due to stop at Northallerton are whizzing through non-stop as the York sim thinks the train is still at "Up Main (Darlington)". If the train gets as far as York it sits at a red signal and then calls in to say it's waiting. Down trains transferring from York to Tyneside are fine.

Not sure whether this is a send (Tyneside) or receive (York) problem or a combination of both, so have reported it here. I've got both sims open on the same PC with server enabled, Tyneside using the preset primary port and York using the preset secondary port.

I've worked around this by manually updating the Current/Next location via Edit Timetable. On one occasion I was late editing a TPX due to stop at Northallerton and the edit was accepted on approach to Northallerton - the train managed to go from 100mph to 88mph within five seconds and then dropped to 0mph in less than a second! Seems the brakes are decent on 185's but I wouldn't have wanted to be on board.... ;)

could this be related to the issue I reported At post No 5 and post No 7

When requesting slot for Bedlington branch, resultant message states "Norton slot has been given." Confused the Bejeezus out of me first time ARS set the route trying to figure out what was trying to go down the Norton branch and why it needed a slot. :woohoo:

I agree, timetable rules and Google suggest that platform should be much longer than 188m (the current length of the two TCs). Mantis 15667 applies.