moa999 wrote:Without more information from mudb difficult to know what caused this.
Potentially a driver change midroute with someone entering the wrong thing - Opal generally handles changes OK (so long as the power stays on)
I've had a similar thing happen 'transfer when I was intending to tap off'.
What I'd done is placed my card next to the reader when it was saying 'please wait'. I'd done this several times previously with no issue - when the reader activates, my card scans and I pocket my card and wait for the bus to actually stop.
What I think happened, is the controller sent the signal to enable the readers, which start to turn on, THEN it sends the new location information. All I can think of is I tripped a race condition, the reader was enabled it found my card and started it's transaction. Then the location update arrived, so it aborted the transaction. No sound or indication on the screen, but it had already updated by card.
Nothing happens so I remove my card and re-present it to the reader to be told 'transfer'.. I try to reverse it but get 'already tapped on'.
My Opal transactions show I had 'tapped off' at the previous bus stop and tapped on at the stop I was getting off at. I was not where near the reader and sitting down when the bus was at the previous stop.