On 12 Feb, 23:29, Fig wrote:
On Mon, 12 Feb 2007 20:34:12 -0000, Paul Scott





wrote:

"Mizter T" wrote in message
oups.com...

I'd suggest that what is happening is this - the card readers doesn't
initially communicate with the Oyster card (perhaps because the card
isn't held flat to the reader) which triggers the error message, but
split seconds later communication is established successfully, and the
Oyster card is accepted and the gate opens. The glitch (if there is
one) is that the "Seek Assistance" error message remains on the
display rather than being cleared off when there's no longer a
problem.

Perhaps the LU staff could be briefed to simply explain that code 94
means
that the Oyster validation wasn't as quick as designed because of user
error - the signs do say 'always touch in' not 'wave about'...

Except, IME, the complete opposite is true. I have noticed that a long
lingering touch, often accompanied by a bit of a 'slide' is likely to set
off the "seek assistance" message accompanied by an open gate.
This used to happen to me often when I first started using Oyster, but
very rarely now that I've been using it daily for a couple of years. I do
notice it happen to other people though. People in front of me and also
friends of mine from out of London who are using the system for the first
time. And it always happens with a prolonged 'touch' or 'slide'. What
appears to happen is that as the card touches the reader the gate gives
its normal 'beep' and opens the gate but a split second later it gives the
reject 'triple beep' and shows the 'seek assistance' message. The gate
remains open. It would appear that the gate is registering the card twice
and is therefore more likely to be showing a code 42 "pass-back" or
similar. With experience, you get to know what kind of touch will result
in success and I usually touch my Oyster very briefly and have lifted it
off before the acceptance 'beep' sounds. Occasionally, I am too hasty and
I get the 'triple beep' reject without an open gate and a 'seek
assistance' but it is obvious to me that I've been too quick. A second
touch will open the gate.
So, in summary, I think the gates are too sensitive and throw a fit if
your card lingers or slides. I agree with the O.P. that this behaviour is
rude and the gate should recognise the difference between a double read
and a pass-back.

--
Fig- Hide quoted text -

- Show quoted text -

This is a bit of a fuss about nothing. Code 94 simply means, as you
were told, card communication error. The reasons for this could be
many (card problems, reader problems, and most likely: interference
between the two radio tranceivers), but if you get a 94 then it is
very likely that a second touch of the card on the reader will resolve
all problems. Of course, if the card is actually damaged then you may
need a replacement.

I suppose you could put in a freedom of infomation request if you
really want more info, but you might be better spending your time
(cont. code 94.)