|
Post by kmkcheng on Oct 11, 2019 1:17:31 GMT
It's not great but mistakes occur, it's life and it's too short Not sure about you but when I receive a response from TfL or any other companies for that matter I would expect them to double check it before sending. There's nothing wrong with making a mistake, being dyslexic myself I can vouch for that but making 4 mistakes in one email shows a lack of care and attention to the response in my opinion. I can forgive the 492/493 mistake but if they completely got the time of day wrong, that means they may have botched the complaint and investigation as they looked into 9pm when services may have been running fine and not at 7:30am which was when the original complaint occurred.
|
|
|
Post by bn12cny on Oct 11, 2019 22:47:12 GMT
|
|
|
Post by riverside on Oct 12, 2019 12:05:22 GMT
If only somebody had been able to video the rows and rows of withdrawn RT/RTL/RTW buses stored at the side of Poplar(PR) Garage in the late 1960s. Thanks for posting a very intriguing clip.
|
|
|
Post by cl54 on Oct 12, 2019 17:26:32 GMT
It was good to buses on the 11 and 133 back in Liverpool Street bus station this morning.
The temporary stop signs for the stands and staff facilities are still in Finsbury Circus but the 3 storey Crossrail construction buildings have gone.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Oct 12, 2019 18:06:00 GMT
Do unscheduled curtailments have to be inputted by the driver into iBus or can the iBus controller do this remotely?
There have been far too many 240s this week terminating at Mill Hill East and Mill Hill Broadway but with the iBus still stating the normal Edgware or Golders Green destination. Annoying for countdown; confusing when the blinds are set differently to the iBus.
|
|
|
Post by Paul on Oct 12, 2019 21:47:17 GMT
Do unscheduled curtailments have to be inputted by the driver into iBus or can the iBus controller do this remotely? When given an unscheduled curtailment the first thing a driver should be doing is inputting it into the MDT (the data terminal we have in the cab). Incredibly, there are drivers who claim not to know how to do this but are too proud to ask to be shown. It’s amazing really since it’s in the basic training I know that iBus controllers can cancel curtailments remotely (had it happen to me) so it’s logical to assume they can input a curtailment. It’s been so long since I was in an iBus room that I genuinely can’t remember! It’s a shame iBus isn’t used properly by some drivers - they give those of us who bother to do the job properly a bad name 🙄
|
|
|
Post by rif153 on Oct 12, 2019 21:50:14 GMT
Do unscheduled curtailments have to be inputted by the driver into iBus or can the iBus controller do this remotely? There have been far too many 240s this week terminating at Mill Hill East and Mill Hill Broadway but with the iBus still stating the normal Edgware or Golders Green destination. Annoying for countdown; confusing when the blinds are set differently to the iBus. I’ve previously read on here that sometimes curtailments can only be authorised by controllers, to prevent the driver doing self curtailments. When the bus doesn’t change it’s pretty unhelpful, for example I was on a 94 curtailed at Shepherds Bush, the blonds changed by Ibus continued saying Acton Green. The poor driver was shouted at by several passengers when they were turfed off the bus.
|
|
|
Post by capitalomnibus on Oct 12, 2019 23:04:21 GMT
It was good to buses on the 11 and 133 back in Liverpool Street bus station this morning. The temporary stop signs for the stands and staff facilities are still in Finsbury Circus but the 3 storey Crossrail construction buildings have gone. It opened mid morning and not from first buses as many thought.
|
|
|
Post by capitalomnibus on Oct 12, 2019 23:07:23 GMT
Do unscheduled curtailments have to be inputted by the driver into iBus or can the iBus controller do this remotely? When given an unscheduled curtailment the first thing a driver should be doing is inputting it into the MDT (the data terminal we have in the cab). Incredibly, there are drivers who claim not to know how to do this but are too proud to ask to be shown. It’s amazing really since it’s in the basic training I know that iBus controllers can cancel curtailments remotely (had it happen to me) so it’s logical to assume they can input a curtailment. It’s been so long since I was in an iBus room that I genuinely can’t remember! It’s a shame iBus isn’t used properly by some drivers - they give those of us who bother to do the job properly a bad name 🙄 Some of the basics as you mention some driver still do not know how to do it, or cant be bothered, which is shameful as it is very basic. Curtailments can be entered onto an individual bus or a multiple of buses, or deleted from an ibus controller. They can also play pre-recorder announcements. If a planned curtailment is in place, then all buses on route could automatically have the ibus set to curtail.
|
|
|
Post by Alexis on Oct 12, 2019 23:58:21 GMT
Was just looking at the 55's new timetable and noticed that a fair number of journeys are scheduled to take just over 2 hours, do any other routes apart from the X26 break the 2-hour mark?
|
|
|
Post by 6HP502C on Oct 13, 2019 0:11:48 GMT
Do unscheduled curtailments have to be inputted by the driver into iBus or can the iBus controller do this remotely? There have been far too many 240s this week terminating at Mill Hill East and Mill Hill Broadway but with the iBus still stating the normal Edgware or Golders Green destination. Annoying for countdown; confusing when the blinds are set differently to the iBus. I’ve previously read on here that sometimes curtailments can only be authorised by controllers, to prevent the driver doing self curtailments. When the bus doesn’t change it’s pretty unhelpful, for example I was on a 94 curtailed at Shepherds Bush, the blonds changed by Ibus continued saying Acton Green. The poor driver was shouted at by several passengers when they were turfed off the bus. Yes, a driver needs authority from the controller to curtail. But not to select a curtailment from the MDT. Drivers should be doing it really but I find it's 50/50. One thing that really annoys me is when a driver puts one in when they're not supposed to - I got off a 427 at Hayes By Pass once because that's what the iBus was showing, only for the driver to shut the doors and continue in service.
|
|
|
Post by thesquirrels on Oct 13, 2019 14:00:36 GMT
Was just looking at the 55's new timetable and noticed that a fair number of journeys are scheduled to take just over 2 hours, do any other routes apart from the X26 break the 2-hour mark? I had a look on Robert Munster's londonbusroutes.net site to find out the answer to this - as far as I can see, only the 53 at high peak now hits 121 minutes. The 25 did too, prior to that route's curtailment to Holborn Viaduct. A little context is always fun, I note that sixteen years ago the only two TfL* routes to break the 100 minute runtime mark were the 25 (103 mins) and the 53 (101 minutes, but for the much longer old route from Plumstead to Oxford Circus! The current run to Lambeth is timed to take 20 minutes longer) (source: web.archive.org/web/20020204152557/http://www.londonbusroutes.net/details.htm)* The X26's predecessor, the non-TfL but travelcard-passed 726, had a run time of between 113 and 143 minutes between Heathrow and deepest Dartford, and it is this route which captures the overall crown. In theory, if not in practice, as reliability was pretty appalling)
|
|
|
Post by 6HP502C on Oct 13, 2019 17:11:06 GMT
* The X26's predecessor, the non-TfL but travelcard-passed 726, had a run time of between 113 and 143 minutes between Heathrow and deepest Dartford, and it is this route which captures the overall crown. In theory, if not in practice, as reliability was pretty appalling) If we're counting historic routes, the 25 had up to 146 minutes running time for two or three trips in the peak until the recent cutback!
|
|
|
Post by ronnie on Oct 13, 2019 19:54:30 GMT
* The X26's predecessor, the non-TfL but travelcard-passed 726, had a run time of between 113 and 143 minutes between Heathrow and deepest Dartford, and it is this route which captures the overall crown. In theory, if not in practice, as reliability was pretty appalling) If we're counting historic routes, the 25 had up to 146 minutes running time for two or three trips in the peak until the recent cutback! I personally did 140+ minutes on the 25 during the peak in its last week!
|
|
|
Post by busaholic on Oct 13, 2019 20:54:53 GMT
* The X26's predecessor, the non-TfL but travelcard-passed 726, had a run time of between 113 and 143 minutes between Heathrow and deepest Dartford, and it is this route which captures the overall crown. In theory, if not in practice, as reliability was pretty appalling) If we're counting historic routes, the 25 had up to 146 minutes running time for two or three trips in the peak until the recent cutback! Sunday 133 South Croydon to Hendon Central was 126 minutes, mostly at 10 mph max. Put me off long bus journeys for life!
|
|