|
|
Post by stuckonthe486 on Aug 3, 2018 14:36:58 GMT
Having just had 15 minutes of my day wasted by this, I thought I’d ask here...
When a bus departure is cancelled, or the bus is told to run light for the first bit of a route, why does it still show on iBus as “due” for ages, and whose responsibility is it to switch it off?
I ask this after wasting a small chunk of the afternoon at Blackheath Royal Standard for a 202 which eventually rolled up its blinds and sailed off into the sunshine empty.
|
|
|
|
Post by joefrombow on Aug 5, 2018 14:56:09 GMT
Having just had 15 minutes of my day wasted by this, I thought I’d ask here... When a bus departure is cancelled, or the bus is told to run light for the first bit of a route, why does it still show on iBus as “due” for ages, and whose responsibility is it to switch it off? I ask this after wasting a small chunk of the afternoon at Blackheath Royal Standard for a 202 which eventually rolled up its blinds and sailed off into the sunshine empty. I think but I could be wrong open to correction but when the bus runs "ghost" along the route so still showing up on ibus however showing Not in Service on the blinds and not stopping at a fair few stops they are effectively cheating the system as to make up time but not to lose mileage . |
|
|
|
Post by ibus246 on Aug 5, 2018 17:35:07 GMT
Having just had 15 minutes of my day wasted by this, I thought I’d ask here... When a bus departure is cancelled, or the bus is told to run light for the first bit of a route, why does it still show on iBus as “due” for ages, and whose responsibility is it to switch it off? I ask this after wasting a small chunk of the afternoon at Blackheath Royal Standard for a 202 which eventually rolled up its blinds and sailed off into the sunshine empty. I think but I could be wrong open to correction but when the bus runs "ghost" along the route so still showing up on ibus however showing Not in Service on the blinds and not stopping at a fair few stops they are effectively cheating the system as to make up time but not to lose mileage . Yes you are correct, as it will technically be shown In service. In years gone by when there were roadside QSI inspectors, some companies used to take a bus from another terminating route and then run it past the inspector spot on time. I.e if a bus from a same company was terminating at Bromley North, it would be blinded up with no Pax on and then ran past the inspector on time |
|
|
|
Post by busaholic on Aug 5, 2018 17:49:14 GMT
I think but I could be wrong open to correction but when the bus runs "ghost" along the route so still showing up on ibus however showing Not in Service on the blinds and not stopping at a fair few stops they are effectively cheating the system as to make up time but not to lose mileage . Yes you are correct, as it will technically be shown In service. In years gone by when there were roadside QSI inspectors, some companies used to take a bus from another terminating route and then run it past the inspector spot on time. I.e if a bus from a same company was terminating at Bromley North, it would be blinded up with no Pax on and then ran past the inspector on time I remember when LT introduced white Ford Anglia vans, with a very prominent raised roundel on top, in the 1960s, manned by two roadside inspectors and drove them to strategic areas and then parked up for a while. Just as a schoolkid, but a bus-obsessed one, I could see an immediate change in how certain crews operated, and if the van started to follow their bus the panic that induced! It was great fun and led to an improvement in service while it lasted. 'On the Buses' may have exaggerated the tricks and foibles but it was undoubtedly a reflection on bus operation of the time. |
|
|
|
Post by snoggle on Aug 5, 2018 18:56:11 GMT
Having just had 15 minutes of my day wasted by this, I thought I’d ask here... When a bus departure is cancelled, or the bus is told to run light for the first bit of a route, why does it still show on iBus as “due” for ages, and whose responsibility is it to switch it off? I ask this after wasting a small chunk of the afternoon at Blackheath Royal Standard for a 202 which eventually rolled up its blinds and sailed off into the sunshine empty. I'm not an expert on I-Bus. I am sure one of the posters on here has said there is a code that a driver can enter to make the bus "disappear" from next bus departure lists. Obviously if drivers don't do this the bus may still appear. I understand that the system prevents the last scheduled bus of the day from being "cancelled". I don't know how often the TfL displays poll for data but other apps can get vehicles "stuck" in the system even if they are moving elsewhere. |
|
|
|
Post by londonbuses2018 on Aug 8, 2018 22:36:35 GMT
This is very interesting I suppose TFL never thought of the idea to tell you that the bus has been cancelled unlike the current Train Operators. London Underground I think tell you if a train has been cancelled.
|
|
|
|
Post by snoggle on Aug 9, 2018 10:49:46 GMT
This is very interesting I suppose TFL never thought of the idea to tell you that the bus has been cancelled unlike the current Train Operators. London Underground I think tell you if a train has been cancelled. I can't recall a time when any train on London Underground was announced as "cancelled". Given LU don't really advertise the existence of timetables or timetabled departures it's hard for the average passenger to have a clue what time a specific train is due. The only exception to this is the top end of the Met Line where frequencies are low to Amersham and Chesham. Only saddos like me used to know the train running numbers and times of certain trains on the Vic Line.  Similarly on the buses TfL don't place much emphasis on "timetables" for most of the network as it's deemed to be high frequency. If a bus was taken out of service due to defect or to catch up time and re-enter service later then TfL only say there is a gap in the service (via Countdown or app based info). The only times I have seen a reference to a "cancellation" was of the last bus of the night and some departures on Arriva London South operated night buses (this was on Twitter). All of TfL's real time departure info is based around "times to the next bus / tube / train" departure rather than a specific instance of a timed departure being cancelled - this even applies on the Overground where service headways are regularly only every 30 mins (Enfield / Cheshunt / Romford - Upminster). There is sometimes departure based info for the TfL Rail service to Heathrow if TfL are tweeting that the service has gone wrong (again!) but this is very much the exception and usually only by one specific person on the TfL Rail Twitter desk. |
|
|
|
Post by 6HP502C on Aug 9, 2018 12:14:08 GMT
Having just had 15 minutes of my day wasted by this, I thought I’d ask here... When a bus departure is cancelled, or the bus is told to run light for the first bit of a route, why does it still show on iBus as “due” for ages, and whose responsibility is it to switch it off? I ask this after wasting a small chunk of the afternoon at Blackheath Royal Standard for a 202 which eventually rolled up its blinds and sailed off into the sunshine empty. It's the bus driver's responsibility. The iBus module has the curtailments programmed in and the driver should manually select either when the trip starts or as soon as the controller issues the instruction. This then reflects in the Countdown system. |
|
|
|
Post by stuckonthe486 on Aug 9, 2018 16:03:41 GMT
Thank you all - interesting to know.
|
|
|
|
Post by RandomBusesGirl on Aug 10, 2018 21:40:08 GMT
On the subject of ghost buses, I've once waited for a morning 412 out of West Croydon, and the bus started tracking and "moving" on LVF, whilst physically it was still on the stand - as I was there  Now how did that happen? It was halfway down the route online when I took an alternative path away (a 64), and the very E400 still hasn't budged 🤔 |
|
|
|
Post by YY13VKP on Aug 10, 2018 23:35:24 GMT
On the subject of ghost buses, I've once waited for a morning 412 out of West Croydon, and the bus started tracking and "moving" on LVF, whilst physically it was still on the stand - as I was there Now how did that happen? It was halfway down the route online when I took an alternative path away (a 64), and the very E400 still hasn't budged 🤔 I think the same thing has happened to me with 8522 after it went mechanical once on the 433, and LVF claimed it was still moving but it was awaiting an engineer. In July whilst waiting for DWL56 on the 288, LVF said it had missed Queensbury Morrisons and was heading to the next one. Having been wanting to travel on this bus, I went to the other side of the Morrisons car park where the stand is, and it was still there. |
|
|
|
Post by someone on Jun 17, 2021 16:15:06 GMT
Having just had 15 minutes of my day wasted by this, I thought I’d ask here... When a bus departure is cancelled, or the bus is told to run light for the first bit of a route, why does it still show on iBus as “due” for ages, and whose responsibility is it to switch it off? I ask this after wasting a small chunk of the afternoon at Blackheath Royal Standard for a 202 which eventually rolled up its blinds and sailed off into the sunshine empty. I know! I was once waiting for a 178 at Annesley Road (K) that had the TfL website saying "due" for around 2 mins, before switching to "4 mins" at the end. |
|
