Strange Oyster error
On 6 June, 18:14, Paul Corfield wrote:
Eh? *Validators simply set your card to the opposite of its previous
state assuming other factors are also valid. In other words if the last
thing you did was enter then it will set exit assuming zones and PAYG
money and max journey time is all logical and valid.
Is there a difference between exit validators (at ungated stations)
and interchange validators (eg at Moorgate, Farringdon, Highbury). My
experience is mainly with the latter. The behaviour you describe would
only make sense for the former.
Surely it's you who made the error? *You were exiting from the NR "side"
of the OSI so needed to record an exit on the validator. You "entered"
at the Vic Line and a failure to record your exit from NR got you the £4
charge. *I don't see how there is an Oyster failing here no matter how
galling it is for you to have incurred a £4 charge.
But I didn't exit anything! I interchanged, indoors, without leaving
railway property. The thing that's incorrect is for the programmers to
have even considered treating it as an OSI. To the passenger, it's no
more of one than changing tube lines at Oxford Circus.
The JLE gateline at Stratford is a good comparison. It doesn't require
PAYG customers arriving from the DLR (etc) to have touched out. I
foolishly expected the gateline at Tottenham Hale to also have been
programmed properly.
(and I genuinely expected you to be outraged that the gateline is
misprogrammed, not making excuses)
U
|