On 12 Jan, 10:24, Matthew Dickinson
wrote:

On 12 Jan, 00:27, Mizter T wrote:

On 11 Jan, 16:47, Mr Thant
wrote:

(snip)

I think what it means is that the NR station's ticket barrier isn't
programmed to do PAYG and rejected Abigail's Z1-3 Travelcard. Since
the DLR has its own ticket barrier and exit in the vicinity of the
station, there's no need to go through the NR station to get out from
the DLR. This seems as good a way as any of reminding people PAYG
isn't usable on NR.

That's a very interesting interpretation, one that hadn't crossed my
mind - I simply though it was the result of sloppy programming.

I have to say that *if* this is the case then it actually sounds like
a fairly good way of avoiding problems, particularly of people trying
to get in to the station whilst attempting to use Oyster PAYG for
travelling on the NR trains.

The SET gateline hasn't been reprogrammed, and did return error code
57 (PAYG not accepted) when i tried my PAYG Oyster on it.


Thanks for the report from the field - so Mr Thant's hypothesis
appears to be correct. A slightly strange arrangement, but I think
it's for the best - and of course one can bear in mind that it is just
a relatively temporary arrangement as the NR network should be
accepting Oyster PAYG by the end of the year.


On a slightly related note, the TfL fare finder appears to return no
fares for Richmond - Clapham Junction journeys.
I wonder what would be charged for an actual PAYG journey (via
Willesden Junction or Earls Court and West Brompton.)


The TfL Fare finder also returns no fares for Kew Gardens - CJ and
Gunnersbury - CJ.

I guess this is either a mistake, or a purposeful omission from the
public Fare finder to try and dissuade people from thinking Oyster
PAYG is valid on the SWT.

Actually I've just checked the Fare finder for a Wimbledon - CJ fare
(via District line and West Brompton) and it does return fares for
that journey, so I dare say the missing fares from Richmond/ Kew
Garden/ Gunnersbury is more likely to be in error.

So yeah, I also wonder how a real journey would be charged.
Essentially depends on whether or not the public Fare finder database
reflects the 'real' Oyster database.