If you have a new account but are having problems posting or verifying your account, please email us on [email protected] 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 [email protected]

RTPI Dublinbus report issue

  • 14-02-2023 7:55am
    Registered Users Posts: 152 ✭✭

    Where can I report an issue for bus not showing on rtpi?

    Bus disappeared from rtpi (both on the sign and in DB app) 5 mins before the bus came. Driver shrugged when I pointed it out. "It happens".


  • Registered Users Posts: 1,158 ✭✭✭Citrus_8

    Leave drivers alone, they don't manage RTPI. They currently have more issues. Don't need to make one more to leave. This would make you wait for a bus even longer having driver shortages. There's another thread about the RTPI coming improvements and the reasons why buses disappear off the screens.

  • Registered Users Posts: 269 ✭✭newirishman

    Public transport providers do not care enough to be bothered by something like this.

    Saw the same reported to Dublinbus (via Twitter) recently - the response was essentially ‘driver shortage hence the bus didn’t run as per schedule’, just wait for the next one. And apologies for not taking the bus off the real time system.

  • Registered Users Posts: 899 ✭✭✭Burt Renaults

    You need to report this to the NTA, not Dublin Bus. It's their equipment. And I don't understand why you'd waste a driver's time with something that has absolutely nothing to do with them.

  • Registered Users Posts: 152 ✭✭prosaic

    I wasn't getting at the driver. I just asked him about it. I wondered could it be faulty equipment on bus.

    This was not a missing bus. It was a missing entry on the system.

    It would be in dublinbus system since it was missing from their app. Not NTA system.

    Is there somewhere in DB to send reports of issues?

  • Registered Users Posts: 15,184 ✭✭✭✭stephenjmcd

    It's not a DB issue, it's an NTA issue.

    If it disappeared off the RTI on street as you mentioned then it goes to NTA

    As others have said there's a full thread on this. Not long ago the NTA went before a Dail committee to explain what RTPI issues there was and what was being done to address them

  • Advertisement
  • Registered Users Posts: 152 ✭✭prosaic

    The DB app runs off DB data. It was missing from DB app so it is DB data that is incorrect.

    They don't have way to log issues it would seem.

  • Registered Users Posts: 15,184 ✭✭✭✭stephenjmcd

    You stated it disappeared from the RTPI on street, again an NTA issue.

    It's NTA equipment on board buses, not DB as others have already said.

    You can submit to DB using the customer comment form from the customer contact page on db website.

    However it's still the NTA that you need to submit to so it's pretty pointless going to DB

  • Registered Users Posts: 52 ✭✭halfpastneverr

    NTA only seems to take complaints about taxis. The only avenue for complaints for bus providers seems to be via twitter or email to the provider. So they're essentially policing themselves. Always a great idea.

  • Registered Users Posts: 152 ✭✭prosaic

    Based on an article in the paper about rtpi, the equipment on buses and the data is DB. What appears in DB app is their own data. What appears on signs is NTA.

    I was saying that the invisible bus was not showing on DB app (as well as not showing on signs)

    You would wish that DB would take some degree of responsibility and take reports of errors.

  • Registered Users Posts: 1,861 ✭✭✭Cushie Butterfield

    Contact them in the About option in main menu of app

  • Advertisement
  • Registered Users Posts: 4,784 ✭✭✭thomasj

    This was on the Dublin bus app today , the 2nd on the list in question was on the TFi app as UCD

  • Registered Users Posts: 17,322 ✭✭✭✭LXFlyer

    If this was near the terminus or shortly after a driver changeover point, there is an issue where buses can vanish from the apps/signs temporarily.

    The AVLC and RTPI system relies on the driver being signed into the ticket machine and the specific journey the bus is making, so that the RTPI system can apply the correct predictive schedule to the GPS location of the bus.

    It can happen that, where a driver has just signed onto the ticket machine, the AVLC system can take longer than normal to recognise the bus on the system and the bus may not appear on the apps/signs until maybe 5-10 minutes further along the route. It's not a particularly common occurrence, but it does happen from time to time - it's a system glitch, or something could be wrong with the GPS transmitter on the bus.

    Hence a bus can physically appear on street that doesn't appear on the apps.

  • Registered Users Posts: 17,322 ✭✭✭✭LXFlyer

    Actually in the case of Dublin Bus, the equipment on the bus is Dublin Bus equipment and that sends the GPS location data to the Dublin Bus AVLC system.

    That in turn feeds into three RTPI systems, which uses the predictive stop-by-stop schedules drawn up for every individual departure by Dublin Bus schedulers.

    The problem alluded to above is most likely to be a defective GPS transmitter on the bus, which is a Dublin Bus issue. It didn't appear on the Dublin Bus app which is coming directly from the GPS data.

    The three systems are

    1) Dublin Bus' own RTPI

    2) The NTA RTPI app

    3) The on-street signs, for which Dublin City Council hold the server

    Each of the three systems independently applies the predictive schedules to the GPS of the bus to come up with predictive times, which is why even in normal times (before all of the ongoing system issues) you could get different predictive times from each of the systems.

    We are in this multiple system mess due to historical political nonsense back in the day when the system was launched first.

    However, the NTA are planning a completely new AVLC and RTPI system which will sit across all PSO operators and there will then be one single system. But that hasn't happened yet.

    We still have individual operator control systems feeding the data, and we still have issues particularly with the NTA apps with buses not always showing live data, but rather the scheduled times, and in the case of GAI buses often displaying predictive times that are in no way relevant to where the bus physically is.

    It still needs working on.

  • Registered Users Posts: 17,322 ✭✭✭✭LXFlyer

    That's another glitch that I've noticed.

    The DB app is now displaying curtailed departures once again, but the stop listed isn't always correct - it seems to pick the Abbey Street one a fair bit!

    Strange that it didn't show as curtailed on the TFI app at the same time. The manual controller intervention should feed through.