|
Post by norbitonflyer on Jan 5, 2019 17:25:27 GMT
Odd sight at Richmond this evening, where the departures screen was showing the next half-dozen District Line trains as running to "Anerley, calling at Anerley only" The train in Platform 7 was an S7, which would be quite a surprise if it did manage to make it to the advertised destination.
Richmond is an SWR-managed station, and in my experience SWR (and its predecessors) have never taken much interest in what is going on at platforms 3-7.
|
|
|
Post by Dstock7080 on Jan 5, 2019 17:38:41 GMT
Odd sight at Richmond this evening, where the departures screen was showing the next half-dozen District Line trains as running to "Anerley, calling at Anerley only" The train in Platform 7 was an S7, which would be quite a surprise if it did manage to make it to the advertised destination. Richmond is an SWR-managed station, and in my experience SWR (and its predecessors) have never taken much interest in what is going on at platforms 3-7. Diversion to Anerleymy pic in these pages from 27 March 2011 !:
|
|
Antje
侵略! S系, でゲソ! The Tube comes from the bottom of London!
Posts: 603
|
Post by Antje on Jan 5, 2019 19:25:01 GMT
With a Class 378, it is sort of possible via the North London line, before switching the the East London line via a connection west of Highbury & Islington.
|
|
|
Post by norbitonflyer on Jan 5, 2019 19:47:41 GMT
With a Class 378, it is sort of possible via the North London line, before switching the the East London line via a connection west of Highbury & Islington. It would, but it would involve running "wrong line" through Caledonian Road & Barnsbury (although Carto Metro says the track is officially "reversible") and I don't know whether the "transfer" track at High & I is passed for passenger use. In any case, the train in platform 7 wasn't a 378 but an S7, which wouldn't have got further than Gunnersbury. The "non-stop" aspect was also intriguing. I assume the train was actually going to Aldgate East - the District Line beyond there is closed for maintenance today.
|
|
|
Post by goldenarrow on Jan 5, 2019 23:14:58 GMT
Could it be that the station systems haven't got the codes for Aldgate East Lt [ZAE] and have simply reverted to the closest one that is does which is Anerley [ANZ]?
I know that as a TOC, London Overground have the full tranche of stations uploaded onto their announcement systems regardless of route or even possibility of being a destination including stations that are not on the LO/LU/TfL Rail network.
|
|
|
Post by xplaistow on Jan 6, 2019 1:16:07 GMT
I can't be the only person who thought this was a FRIPAS thread when they saw the title...
|
|
|
Post by superteacher on Jan 6, 2019 8:52:18 GMT
I can't be the only person who thought this was a FRIPAS thread when they saw the title... I did too! So I’ve made a small alteration to the thread title.
|
|
|
Post by mattdickinson on Jan 6, 2019 9:15:54 GMT
Could it be that the station systems haven't got the codes for Aldgate East Lt [ZAE] and have simply reverted to the closest one that is does which is Anerley [ANZ]? I know that as a TOC, London Overground have the full tranche of stations uploaded onto their announcement systems regardless of route or even possibility of being a destination including stations that are not on the LO/LU/TfL Rail network. Another possibility is that the old CRS code for Anerley (ANY) has caused an issue.
|
|
|
Post by norbitonflyer on Jan 6, 2019 12:49:42 GMT
If the problem is peculiar to Richmond, I would suspect its a glitch in SWR's DMI software, as it is their station and their information system. Does anyone know what was showing on DMI screens further up the line?
|
|
|
Post by superteacher on Jan 6, 2019 13:04:58 GMT
If the problem is peculiar to Richmond, I would suspect its a glitch in SWR's DMI software, as it is their station and their information system. Does anyone know what was showing on DMI screens further up the line? Pretty sure the current system can’t cope with “Aldgate East” as a destination. Looking at the live departures boards for Embankment, they are showing “Wsst Ham.” No idea if that’s what is being shown on the actual boards though,
|
|
|
Post by t697 on Jan 6, 2019 14:13:31 GMT
After ATC, it won't be possible to reverse EB to WB terminating at Aldgate East so maybe systems lose that as they are updated.
|
|
|
Post by superteacher on Jan 6, 2019 15:00:31 GMT
After ATC, it won't be possible to reverse EB to WB terminating at Aldgate East so maybe systems lose that as they are updated. I don’t think they ever had the ability to show it.
|
|
|
Post by PiccNT on Jan 6, 2019 16:55:59 GMT
The DMI at Heathrow T5 also shows odd destinations. A couple of days ago it showed the first train (mine) as Oakwood but instead of 2 minutes, it showed 48 minutes and the second train according to that was Triangle Sidings!
|
|
|
Post by Dstock7080 on Jan 6, 2019 17:19:57 GMT
If the problem is peculiar to Richmond, I would suspect its a glitch in SWR's DMI software, as it is their station and their information system. Does anyone know what was showing on DMI screens further up the line? "West Ham" at most places, although Blackfriars did actually show "Aldgate East". Earl's Court 'heritage' boards were blank when an Aldgate East train went through.
|
|
|
Post by peterc on Jan 7, 2019 13:00:29 GMT
I can't be the only person who thought this was a FRIPAS thread when they saw the title... I did too! So I’ve made a small alteration to the thread title.
I still had to look twice to realise that it wasn't.
|
|
|
Post by t697 on Jan 7, 2019 19:33:40 GMT
The DMI at Heathrow T5 also shows odd destinations. A couple of days ago it showed the first train (mine) as Oakwood but instead of 2 minutes, it showed 48 minutes and the second train according to that was Triangle Sidings! Hope they don't use the Triangle Sidings one too often! The Picc line 73TS trains are banned from going there now since the SSR voltage went up to nominal 750V on most sections not shared with the Picc.
|
|
roythebus
Pleased to say the restoration of BEA coach MLL738 is as complete as it can be, now restoring MLL721
Posts: 1,254
|
Post by roythebus on Jan 7, 2019 19:52:05 GMT
With a Class 378, it is sort of possible via the North London line, before switching the the East London line via a connection west of Highbury & Islington. It would, but it would involve running "wrong line" through Caledonian Road & Barnsbury (although Carto Metro says the track is officially "reversible") and I don't know whether the "transfer" track at High & I is passed for passenger use. In any case, the train in platform 7 wasn't a 378 but an S7, which wouldn't have got further than Gunnersbury. The "non-stop" aspect was also intriguing. I assume the train was actually going to Aldgate East - the District Line beyond there is closed for maintenance today. If it is a signalled move, then it is passed for passenger use. If it is just with subsidiary signals, then possible not It also depends whether facing point locks are fitted which must be if it's reversible.
|
|
|
Post by PiccNT on Jan 7, 2019 23:56:37 GMT
The DMI at Heathrow T5 also shows odd destinations. A couple of days ago it showed the first train (mine) as Oakwood but instead of 2 minutes, it showed 48 minutes and the second train according to that was Triangle Sidings! Hope they don't use the Triangle Sidings one too often! The Picc line 73TS trains are banned from going there now since the SSR voltage went up to nominal 750V on most sections not shared with the Picc. Not exactly banned as there may be a signalling issue at say Hammersmith EB on the local where we can't get back onto the Picc and have to reverse at West Kensington. It does go to 750v past the Barons Court rail gap so we have to cut out all heating and ventilation and then, with authority, we can proceed.
|
|
|
Post by MoreToJack on Jan 8, 2019 0:58:30 GMT
Hope they don't use the Triangle Sidings one too often! The Picc line 73TS trains are banned from going there now since the SSR voltage went up to nominal 750V on most sections not shared with the Picc. Not exactly banned as there may be a signalling issue at say Hammersmith EB on the local where we can't get back onto the Picc and have to reverse at West Kensington. It does go to 750v past the Barons Court rail gap so we have to cut out all heating and ventilation and then, with authority, we can proceed. That does not disagree with the original statement, which is that they are banned from Triangle. As you clarify, 73TS can proceed as far as West Kensington and reverse east to west in the eastbound platform, but only with equipment cut out and only if there is no other option but to divert onto the District. In the event that West Kensington has issues there is a further emergency plan but that does not include the use of Triangle. Worth pointing out the issue is less the nominal 750V, it's the high regen spikes that could cause issues. The 73TS have not been assured for this level of voltage.
|
|
|
Post by norbitonflyer on Jan 8, 2019 8:28:55 GMT
|
|
|
Post by MoreToJack on Jan 8, 2019 9:23:07 GMT
This was prior to the SSR voltage uplift and at the time 73TS were permitted to run to High Street in the event of either signalling issues at Hammersmith or a wrong signal lowered and accepted. If my memory serves me correctly this particular trip was a planned move.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jan 8, 2019 10:04:56 GMT
It was planned to go to West Kensington but the route failed to send it back west so the next reversing point is High Street Kensington hence it ended up there.
Somewhere in my pictures I have a few of it at Earl’s Court going east
Going forward there is nothing stopping from a signalling point of view this happening again at Hammersmith perhaps Tom could earn a few quid
|
|
|
Post by norbitonflyer on Mar 25, 2019 22:25:37 GMT
Train rolled onto Richmond this morning claiming to be for Chalfont & Latimer fast. Not sure an S7 has ever been to C&L! Once the driver had changed ends, it proclaimed, more prosaically, but rather more plausibly, that it would only go to Tower Hill.
|
|
|
Post by t697 on Mar 25, 2019 23:01:27 GMT
Train rolled onto Richmond this morning claiming to be for Chalfont & Latimer fast. Not sure an S7 has ever been to C&L! Once the driver had changed ends, it proclaimed, more prosaically, but rather more plausibly, that it would only go to Tower Hill. Most S7s did a 'rattle run' from Neasden to Amersham and back when originally delivered a few years ago. But they were empty stock then. C&L Fast is code 008 or 009 on the selection screen while Tower Hill from Richmond is 891 and the trip to Richmond 744. Something odd there with fingers or software... Possibly only the first digit of the Next Trip got entered so it got taken as 008.
|
|
|
Post by norbitonflyer on Apr 4, 2019 9:56:33 GMT
More dodgy info at Richmond this morning - there really needs to be better communication between LUL and the poor SWR staff on the ground who have to deal with the fallout. "(Minor delays" on the rainbow board at 0855, but the departure screens showed the next train in 4 minutes, and another in 14, so all seemed well. However, down on the platform, the train on platform 7 left at 0856 with the display still saying it was due to leave at 0859 (catching several people out who could have caught it if they had realised the doors were closing for real!), and there was no sign of another. A couple of minutes later, the 0809 and 0819 both changed to "cancelled" meaning, (if true!) that there would be a gap of over 30 minutes until the 0829, shown as departing Platform 6. The only information the staff had was that there was a train at Gunnersbury. This is presumably the one that arrived in Platform 7 (not 6) at about 0908, proclaimed on the boards (rather alarmingly, given the layout of the station) as "Please stand back, this train is not scheduled to stop at this station". Fortunately 21444* did not reprise the attempt 7100 made 32 years ago to get to TwickenhamHaving decamped to the 0910 Overground departure, (a fifteen minute longer journey via West Hampstead trumps a thirty minute wait for a direct train) I noticed at Gunnersbury that the only information there about the District Line was that the first eastbound was cancelled - no information about when to expect a train - and the westbound train standing in the platform with passengers boarding and alighting was "passing through, please stand back" - slightly more plausible there than at Richmond, but in fact no more accurate. So, why is accurate information on the Richmond branch an optional extra? * (I don't usually notice numbers but "all the 4's" is distinctive anyway, and the background to the numerals on that unit appear to be in a different shade to the bodysides - has it been repainted at some time?)
|
|
|
Post by Dstock7080 on Apr 4, 2019 10:40:01 GMT
* (I don't usually notice numbers but "all the 4's" is distinctive anyway, and the background to the numerals on that unit appear to be in a different shade to the bodysides - has it been repainted at some time?) 21443/44 carried a special vinyl wrap during 2015, when the vinyl was removed the numbers came with it! so the numbers were reapplied using non-standard methods.
|
|
|
Post by norbitonflyer on Apr 4, 2019 17:04:45 GMT
21443/44 carried a special vinyl wrap during 2015, when the vinyl was removed the numbers came with it! so the numbers were reapplied using non-standard methods. Interesting! What was the wrap? Does anyone have any insights into why information is so unreliable on the Richmond branch, or indeed what caused the cancellations?
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Apr 4, 2019 17:21:27 GMT
Point failure at Tower Hill so no Tower Hill trains as the bay road is out of commission
|
|
|
Post by goldenarrow on Apr 4, 2019 17:50:10 GMT
|
|
|
Post by norbitonflyer on Apr 4, 2019 20:23:21 GMT
Point failure at Tower Hill so no Tower Hill trains as the bay road is out of commission ......and the misinformation on the Richmond branch? How much overview do the District Line controllers have of the trains ( or indeed station platforms) once they reach NR metals at Gunnersbury? As far as I am aware, the only LUL staff who ever go to Richmond are the drivers, and at the crucial moment they are seven car-lengths away from the information screens. Would it not be a good idea to have the screens repeated where the drivers can see them, so that if there is a discrepancy between what they say and what the drivers have been told to do (like leave before the advertised time as happened this morning, or in a different order, as happened one day last week) they at least know about it?
|
|