Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi all! We have been experiencing an issue on site where threads have been missing the latest postings. The platform host Vanilla are working on this issue. A workaround that has been used by some is to navigate back from 1 to 10+ pages to re-sync the thread and this will then show the latest posts. Thanks, Mike.
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Multiple bus RTPI systems?

  • 04-08-2022 1:57pm
    #1
    Registered Users, Registered Users 2 Posts: 3,228 ✭✭✭


    I’m standing at a bus stop in Dublin waiting for a Dublin Bus. The display at the stop says 1 minute. The TFI Real Time Ireland app on my phone says 3 minutes. The popular Dublin Bus Live iPhone app, which I’ve used for years and used to be very accurate, says 13 minutes. I didn’t check the Dublin Bus app. The bus came after 1 minute.

    Can somebody more knowledgeable please explain to me why this is happening? It’s a recurrent issue and happens on multiple routes at multiple stops. I can only assume they’re all pulling the info from different feeds. It makes it very difficult to plan a journey.

    I’m sorry, I’m sure this has been answered in one of the other bus threads, but I find those tend to be enthusiasts and public transport workers talking to each other, and a lot of it goes over my head. I just want to know which app to look at to know when the bus is coming. Apparently none of them, since on this occasion the display at the stop was correct, and the apps were wrong.



Comments

  • Registered Users, Registered Users 2 Posts: 1,245 ✭✭✭p_haugh


    With the current delays and cancellations due to covid and driver shortages etc., the TFI Realtime Ireland app is the most accurate, especially because it shows which services are curtailed or cancelled, and it has the ability to show the location of buses.

    The rtpi displays at the bus stop itself currently don't show if a service is cancelled.



  • Registered Users, Registered Users 2 Posts: 17,941 ✭✭✭✭LXFlyer


    I’d second that.

    Also, being able to go back along a bus route and click on the bus symbols to see the live position of Dublin Bus or Go Ahead vehicles on the map is very useful, especially if the connection between the GPS live position of the bus and the predictive times is broken for whatever reason.



  • Registered Users, Registered Users 2 Posts: 1,330 ✭✭✭bikeman1


    I have been having the exact same problem for the last month.

    Everything (including the DB app) was showing a different time to that at the stop, which was the most accurate. I was nearly running for a bus based on the TFI app and ended up having 7 minutes extra to wait. Presumably there is some "stepping up" of services with a shortage of drivers and everything is running all over the place?



  • Registered Users, Registered Users 2 Posts: 3,228 ✭✭✭Breezer


    Thanks folks. Yes, I’d started using the TFI Realtime app due to what I’d read on here about curtailments etc. But on this occasion, that was wrong too (albeit by 2 minutes).

    It really is nonsense. Whatever about curtailments, they should all be pulling info from the same source.



  • Registered Users, Registered Users 2 Posts: 3,057 ✭✭✭Vic_08


    The Source is the base AVL data which if working correctly gives a regularly updated location for each vehicle.

    The second layer is connecting each vehicle with a particular bus and or driver duty, this is done when the driver logs on to the ticket machine and should correctly match with a schedule allowing the software to correctly assign it to a route and current and future departures.

    The third layer is processing this factual data into a prediction of future events, namely the arrival time at particular stops, by reference to pre-programmed timing estimates, learned times from past performance and probably some manually altered entries.

    This is always going to have some inaccuracy as it is still a prediction. Were it changed to show how far away in distance each bus is it could be accurate but not terribly useful for most passengers.


    The first layer should be very accurate, the odd faulty equipment excepted.

    The second would also be accurate in normal circumstances, where the majority of duties are running as planned. I expect part of the problem at present is that a lot of changes are having to be made on the fly to adjust the duties to cope with staff absences. This will then lead to duties not operating their scheduled runs which then confuses the real-time system that hasn't been programmed for this level of disruption.

    Once there is a significant amount of bad data and buses not connected with recognisable schedules the real time predictions will start to output various anomalies.

    I suppose had the system been perfectly designed with the robustness to cope with any and all levels of disruption it may just about be able to still output mostly good information but what are the chances it was an expertly designed and debugged gold plated system and not a barely functional off the shelf system based on some other city bodged to work in Dublin.



  • Advertisement
  • Registered Users, Registered Users 2 Posts: 5,912 ✭✭✭Charles Babbage


    The point surely is that there should be as a good a system as possible and then the different modes of display should all access this, not come up with their own estimates.



  • Registered Users, Registered Users 2 Posts: 3,228 ✭✭✭Breezer


    Thanks @Vic_08. That’s a helpful explanation. But I agree with @Charles Babbage . Surely TFI should be making one set of data, incorporating all of the above, available to all app developers? As it is, the data displayed in TFI’s own app doesn’t match the data displayed on TFI’s on-street displays. It was a small discrepancy in this example, but it’s been a lot bigger at other times.



  • Registered Users, Registered Users 2 Posts: 17,941 ✭✭✭✭LXFlyer


    The NTA are looking to replace the different company systems with one system going forward. But it’s going to take time to implement I suspect.

    Why the on street displays and the TFI app wouldn’t agree on the times I can’t answer - that’s bizarre.

    One thing I will say is that I figured out that there will always be a difference between the countdown minutes on the DB app and the TFI app. The DB one uses “due” to denote now, while the TFI one uses “due” to denote 60 seconds or less away.

    As I’ve said already the live positions on the map on the TFI app are pretty accurate most of the time (apart from in the city centre), and if in doubt I find checking back along the route to see where the bus is a handy option. That app does show the curtailments and cancellations too.



  • Registered Users, Registered Users 2 Posts: 3,228 ✭✭✭Breezer


    I got the 155 today. The on-street displays said “Bray”, but the bus said “O’Connell St.” This caused great fun at several stops, particularly on O’Connell St, where a large number of people were waiting to get on, but the bus was going nowhere.

    I don’t know what the TFI app said, since the bus didn’t appear there at all (it was pulling into the stop just as I arrived at the stop, so I suspect it was showing as already gone).

    It’s absolutely crazy that a destination isn’t updated on the on-street displays. Surely it can be, since the last buses of the day tend to run to city centre only? So why isn’t it?



  • Registered Users, Registered Users 2 Posts: 1,245 ✭✭✭p_haugh


    Most of the last buses of the day are scheduled to run to CC only, so that's preprogrammed. The displays currently can't be updated in real-time, meaning cancelled/curtailed services don't reflect correctly. The only updates they can make to the displays is if a service is cancelled, and AFAIK, that is a manual process in that the controller on duty has to click a button to remove it from the feed. Hopefully once the NTA sort out the new bus tracking system, all these issues will be rectified.



  • Advertisement
  • Registered Users, Registered Users 2 Posts: 17,941 ✭✭✭✭LXFlyer


    The displays show the scheduled destinations, which in the case of the last bus where it is scheduled to operate to city centre will be the last scheduled stop in the city centre.

    Something has changed since prior to Covid and now neither the on-street displays and Dublin Bus app no longer show the curtailed destination when a service is curtailed to run only part of the route. It’s some sort of system glitch.

    In that case only the TFI app will show the controller’s curtailment.



  • Registered Users, Registered Users 2 Posts: 69,588 ✭✭✭✭L1011


    I'm now starting to find a substantial number of 41s that are marked as cancelled on the TFI app are actually running. Nearly misdirected a couple to take a 41C and walk in to the airport due to the app showing cancellations for 3/4 of an hour, but then one turned up.



  • Registered Users, Registered Users 2 Posts: 1,330 ✭✭✭bikeman1


    I can confirm this happens from time to time. I’ve had a random empty “41C” come along when neither one was scheduled or showing on the display or apps.

    I think the controller will have cancelled a bus, but then found a volunteer to run some or all of the route as a special to mop up some of the pax.

    That’s your lucky day when that happens!



  • Registered Users, Registered Users 2 Posts: 1,375 ✭✭✭Boulevardier


    On a related point, I have a Nokia phone and I regularly use the SMS text (53035) service when I am waiting at stops without RTPI displays. In the last few days the texts have included a notification that the "service" (presumably the SMS service, not the bus route) is due to cease at the end of September.

    I think this curtailment is unnecessary and unacceptable. Who do I contact to express my dissatisfaction? Possibly the NTA?



  • Registered Users, Registered Users 2 Posts: 69,588 ✭✭✭✭L1011


    I'd expect the service has stopped covering its costs - those shortcodes aren't cheap. Its not well publicised, which won't help; but the number of people willing to pay 30c a go for that info is still going to be tiny.

    The NTA would be who to the complain to, but its quite likely they just handed the service over to a commercial operator who are pulling out.



  • Registered Users, Registered Users 2 Posts: 1,375 ✭✭✭Boulevardier


    I am 67 and on free travel. This will leave a number of people like me without a service we need.



  • Moderators, Motoring & Transport Moderators, Technology & Internet Moderators Posts: 23,006 Mod ✭✭✭✭bk


    NTA would be the ones to complain too.

    If they do end it, I’d point out as an alternative, that smart phones and data plans have gotten ridiculously cheap and a smart phone plan would probably cost you less then constantly paying 30c for this service.



  • Registered Users, Registered Users 2 Posts: 1,165 ✭✭✭Citrus_8


    Why not to use the mobile internet connection?



  • Registered Users Posts: 189 ✭✭Fizzy Duck


    The 41's now pull into Summerhill at the end of each duty. So when we sign in at the garage the real time starts tracking at Mountjoy Square on the way to Abbey Street. This is why some of the services disappear for a while, in my opinion.



  • Registered Users Posts: 762 ✭✭✭Jayuu


    Perfect example of crazy waiting time differences.

    https://twitter.com/formyrantings/status/1562842807563603968



  • Advertisement
  • Registered Users, Registered Users 2 Posts: 3,228 ✭✭✭Breezer


    Thank you. I was trying to take a photo of the on-street display, but they’re actually very hard to photograph legibly.

    Dublin Bus’s reply to that tweet is to use the Dublin Bus app, because the Transport for Ireland app “does not appear to be our app.” Jesus wept.



  • Registered Users Posts: 12 transportrian


    Bus companies are not helpful at all when it comes to reporting issues about RTPI. It doesn't help when TFIs website just tells you to contact the operator even when it's about TFis infrastructure. For example, it is going into the second week of the real-time display at my bus stop not working, and the response from Go-Ahead was explaining what real-time is... (see below)

    what I said:


    GAIs Response:

    I have no clue from this email if the issue has been flagged to TFI/NTA at all?



Advertisement