|
Post by M1104 on Jan 15, 2018 21:42:25 GMT
Absolutely. During my CA days I would only yell "hold tight please" at Victoria Station or whenever a large group boarded. Perhaps rather than iBus announcing it, the announcement would be tied into the doors. "Doors closing, hold on tight" - IIRC First tried something with the rear doors I think it was something like, “Stand clear, doors opening” from memory. We also had the “Bus stopping at next bus stop, please stand well clear of doors” announcement on London Central & General buses between 51 & 03 reg which activated not long after the bell was pressed. Firstbus also had "stand clear doors closing." With them and the London General announcement not all the speakers were utilised, which the "hold tight..." announcement would need to have access to.
|
|
|
Post by danorak on Jan 15, 2018 22:37:09 GMT
There have been a few stats buzzing around today about slips and falls on buses, but how many of these are caused by the bus pulling away from the stop as opposed to the driver having to slam on the brakes? And what about when the bus is pulling away from traffic lights, or pulling out to turn right - no warning that the bus is about to move then.
|
|
|
Post by snoggle on Jan 15, 2018 23:46:58 GMT
There have been a few stats buzzing around today about slips and falls on buses, but how many of these are caused by the bus pulling away from the stop as opposed to the driver having to slam on the brakes? And what about when the bus is pulling away from traffic lights, or pulling out to turn right - no warning that the bus is about to move then. TfL publish all bus incident data every quarter. While not in excrutiating detail it gives reasonable details about the nature of the injury and treatment. tfl.gov.uk/corporate/publications-and-reports/bus-safety-data
|
|
|
Post by rj131 on Jan 16, 2018 16:42:45 GMT
Don’t know if this has been mentioned yet but this ‘please hold on blah blah blah’ announcement is only a trial for a month and it will ‘only continue if it’s been linked with a reduction in the number of injuries’ (shame it’s not linked with the amount of annoyed people it’s caused ), so I’m praying to god that the number of injuries won’t ‘reduce’, though TfL will probably make up a reason that it has and will continue to use the announcement knowing how unbelievably crazy health and safety has gone these days. I will actually probably stop using the London Buses if they continue it because of how ridiculously annoying it is. The trick is to get people to deliberately injure themselves so that the number will increase if anything so that they’ll remove it
|
|
|
Post by londonbusexplorer on Jan 16, 2018 20:02:22 GMT
After a long time, it has got very irritating. I made a video which is in a joke kind of format and all I got is dislikes...
Do people actually like this new system? It is the worst thing to happen on the iBus!
|
|
|
Post by 6HP502C on Jan 17, 2018 23:55:50 GMT
The lovely E266 of NX has gone up in my estimations. To date it doesn't have this new announcement and still says "Richards Avenue" instead of "to" when announcing the route.
|
|
|
Post by RandomBusesGirl on Jan 18, 2018 1:48:13 GMT
The lovely E266 of NX has gone up in my estimations. To date it doesn't have this new announcement and still says "Richards Avenue" instead of "to" when announcing the route. Yes the fun thing I've discovered with friends is that ALL buses with derpy/faulty iBus do NOT make the torture messages \ /
|
|
|
Post by gloriouswater on Jan 18, 2018 22:25:59 GMT
The lovely E266 of NX has gone up in my estimations. To date it doesn't have this new announcement and still says "Richards Avenue" instead of "to" when announcing the route. Yes the fun thing I've discovered with friends is that ALL buses with derpy/faulty iBus do NOT make the torture messages \ / Unless it's one of those buses that announces the route a million times every time it stops at a traffic light. Then it's double the torture
|
|
|
Post by snoggle on Jan 18, 2018 23:27:23 GMT
It seems the announcement is only triggered at stops formally recognised by I-Bus. Didn't activate at all on the Hail and Ride section of the W11 today which means I only got to hear it about 3 times as there were not many people about so stops at fixed stops were few and far between.
|
|
|
Post by ibus246 on Jan 19, 2018 12:06:45 GMT
It seems the announcement is only triggered at stops formally recognised by I-Bus. Didn't activate at all on the Hail and Ride section of the W11 today which means I only got to hear it about 3 times as there were not many people about so stops at fixed stops were few and far between. It was activating on the 434 hail and ride virtual stops the other day.
|
|
|
Post by snoggle on Jan 19, 2018 12:22:35 GMT
It seems the announcement is only triggered at stops formally recognised by I-Bus. Didn't activate at all on the Hail and Ride section of the W11 today which means I only got to hear it about 3 times as there were not many people about so stops at fixed stops were few and far between. It was activating on the 434 hail and ride virtual stops the other day. It would do as the stops are recognised / formalised within I-Bus. The W11 has not had any virtual stops added to the I-Bus script hence the difference.
|
|
|
Post by Paul on Jan 19, 2018 18:53:36 GMT
It seems the announcement is only triggered at stops formally recognised by I-Bus. Didn't activate at all on the Hail and Ride section of the W11 today which means I only got to hear it about 3 times as there were not many people about so stops at fixed stops were few and far between. It was activating whenever and wherever I stopped on the R10 today and yesterday. We do have iBus recognised points but even between these stops the announcement was playing Also found another problem with it today. I let someone off at the Cheltenham Road stop on the R7. For those who know the area, you’ll know the next stop (Haileybury Road) is just a few hundred yards along the road. After leaving the first stop, the route number and destination was announced and then the ‘Hold on’ announcement but it played so late that I had passed the second stop before iBus announced ‘Haileybury Road.’
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jan 20, 2018 9:02:58 GMT
It's now been updated to play directly after the destination info. Still too late on some routes and probably too early on others. The screen now only shows one dot on updated buses.
|
|
|
Post by M1104 on Jan 20, 2018 11:49:46 GMT
It's now been updated to play directly after the destination info. Still too late on some routes and probably too early on others. The screen now only shows one dot on updated buses. I can't see that being any more beneficial than the way it was up to yesterday. As many has pointed out the best way for the message to work effectively is for it to be triggered by the closing of the front doors (not quite sure how it would work on LTs). Alternatively have it as a preset message to be played only when necessary.
|
|
|
Post by Eastlondoner62 on Jan 20, 2018 17:13:29 GMT
It's now been updated to play directly after the destination info. Still too late on some routes and probably too early on others. The screen now only shows one dot on updated buses. I can't see that being any more beneficial than the way it was up to yesterday. As many has pointed out the best way for the message to work effectively is for it to be triggered by the closing of the front doors (not quite sure how it would work on LTs). Alternatively have it as a preset message to be played only when necessary. Tfl seem to have mucked up on some routes implementing this. For whatever reason the 422 announcement now doesn't announce the number while on the B16 we had the weird scenario where it went "B16 to Please Hold on the Bus is about to Move" However it was fine on the 96, 401 and 62 that I rode.
|
|