Home |
Search |
Today's Posts |
![]() |
|
London Transport (uk.transport.london) Discussion of all forms of transport in London. |
Reply |
|
|
LinkBack | Thread Tools | Display Modes |
|
#1
![]() |
|||
|
|||
![]()
Roland Perry wrote on 18 March 2014 20:47:53 ...
In message , at 20:03:09 on Tue, 18 Mar 2014, Mizter T remarked: On 18/03/2014 19:34, Roland Perry wrote: http://metro.co.uk/2014/03/16/thousa...for-bus-after- oyster-readers-charge-wrong-card-in-contactless-glitch-4610552/ "Just under one per cent of all Oyster and contactless journeys involve a card clash and we are seeing this number continue to drop each week." Sorry, but 1% seems very high. My experience of card clash is an error 94 & the gates don't open. I didn't think that gates were enabled for contactless cards yet. Given there's a not-insignificant trial running, I'd suggest they are. I'd forgotten about the trial. But it's very worrying that they are charging the credit cards of people not signed up to the trial. That seems to me to be completely wrong, on many levels (for example, it means anyone can join the 'trial' just by proffering their card). The Metro story you referenced in the original post refers to buses - CPC acceptance is not a trial on buses, it's been accepted as a fare payment method since December 2012. I know, but someone mentioned "gates" (error 94 etc), which I don't recall ever seeing on a bus. FWIW, trying my contactless credit card on validators (both on gates and standalone) has resulted in an error message, can't remember which one. There are now posters and signs around the transport network warning against card clash, but I think the message should have been delivered earlier and more forcefully. That's another message from the newspaper article - the need for such warnings, which are quite frankly a desperate attempt to cover up a massive technology failure. I'm not sure I'd describe it as a *technology* failure. The passenger has presented a set of cards to the reader, two of which have validity for the journey. What do you expect to happen in those circumstances? If the card furthest away from the reader pad is on the edge of the acceptable range, it may or may not be read. So you might get a card clash (neither card accepted - try again) or you might have the nearest card used for the journey. The failure is the lack of communication for several YEARS, by both TfL and the banks. It took me some time to realise that the frequent mis-read of my Oyster (Freedom Pass) at Tube stations was caused by the RFID Barclaycard in the same wallet. That was long before RFID cards had any validity on TfL services. Neither Barclaycard nor TfL had bothered to warn me. -- Richard J. (to email me, swap 'uk' and 'yon' in address) |
#2
![]() |
|||
|
|||
![]() "Richard J." wrote in message news ![]() Roland Perry wrote on 18 March 2014 20:47:53 ... In message , at 20:03:09 on Tue, 18 Mar 2014, Mizter T remarked: On 18/03/2014 19:34, Roland Perry wrote: http://metro.co.uk/2014/03/16/thousa...for-bus-after- oyster-readers-charge-wrong-card-in-contactless-glitch-4610552/ "Just under one per cent of all Oyster and contactless journeys involve a card clash and we are seeing this number continue to drop each week." Sorry, but 1% seems very high. My experience of card clash is an error 94 & the gates don't open. I didn't think that gates were enabled for contactless cards yet. Given there's a not-insignificant trial running, I'd suggest they are. I'd forgotten about the trial. But it's very worrying that they are charging the credit cards of people not signed up to the trial. That seems to me to be completely wrong, on many levels (for example, it means anyone can join the 'trial' just by proffering their card). The Metro story you referenced in the original post refers to buses - CPC acceptance is not a trial on buses, it's been accepted as a fare payment method since December 2012. I know, but someone mentioned "gates" (error 94 etc), which I don't recall ever seeing on a bus. FWIW, trying my contactless credit card on validators (both on gates and standalone) has resulted in an error message, can't remember which one. There are now posters and signs around the transport network warning against card clash, but I think the message should have been delivered earlier and more forcefully. That's another message from the newspaper article - the need for such warnings, which are quite frankly a desperate attempt to cover up a massive technology failure. I'm not sure I'd describe it as a *technology* failure. The passenger has presented a set of cards to the reader, two of which have validity for the journey. What do you expect to happen in those circumstances? If the card furthest away from the reader pad is on the edge of the acceptable range, it may or may not be read. So you might get a card clash (neither card accepted - try again) or you might have the nearest card used for the journey. The failure is the lack of communication for several YEARS, by both TfL and the banks. It took me some time to realise that the frequent mis-read of my Oyster (Freedom Pass) at Tube stations was caused by the RFID Barclaycard in the same wallet. That was long before RFID cards had any validity on TfL services. Neither Barclaycard nor TfL had bothered to warn me. ------------------------------------------------------------------------------------------------------------------------ I think you contradicted your own claim here If both cards are valid for the journey then you are right that the technology may have difficulty deciding which one to charge (and certainly wont know it has made a mistake if only one tries to "connect") but cards that are not valid for the journey interfering with a card that is, is a failure of the technology and ought to have been designed out at the start tim |
#3
![]() |
|||
|
|||
![]()
tim..... wrote on 18 March 2014 21:57:24 ...
"Richard J." wrote in message news ![]() Roland Perry wrote on 18 March 2014 20:47:53 ... In message , at 20:03:09 on Tue, 18 Mar 2014, Mizter T remarked: On 18/03/2014 19:34, Roland Perry wrote: http://metro.co.uk/2014/03/16/thousa...for-bus-after- oyster-readers-charge-wrong-card-in-contactless-glitch-4610552/ "Just under one per cent of all Oyster and contactless journeys involve a card clash and we are seeing this number continue to drop each week." Sorry, but 1% seems very high. My experience of card clash is an error 94 & the gates don't open. I didn't think that gates were enabled for contactless cards yet. Given there's a not-insignificant trial running, I'd suggest they are. I'd forgotten about the trial. But it's very worrying that they are charging the credit cards of people not signed up to the trial. That seems to me to be completely wrong, on many levels (for example, it means anyone can join the 'trial' just by proffering their card). The Metro story you referenced in the original post refers to buses - CPC acceptance is not a trial on buses, it's been accepted as a fare payment method since December 2012. I know, but someone mentioned "gates" (error 94 etc), which I don't recall ever seeing on a bus. FWIW, trying my contactless credit card on validators (both on gates and standalone) has resulted in an error message, can't remember which one. There are now posters and signs around the transport network warning against card clash, but I think the message should have been delivered earlier and more forcefully. That's another message from the newspaper article - the need for such warnings, which are quite frankly a desperate attempt to cover up a massive technology failure. I'm not sure I'd describe it as a *technology* failure. The passenger has presented a set of cards to the reader, two of which have validity for the journey. What do you expect to happen in those circumstances? If the card furthest away from the reader pad is on the edge of the acceptable range, it may or may not be read. So you might get a card clash (neither card accepted - try again) or you might have the nearest card used for the journey. The failure is the lack of communication for several YEARS, by both TfL and the banks. It took me some time to realise that the frequent mis-read of my Oyster (Freedom Pass) at Tube stations was caused by the RFID Barclaycard in the same wallet. That was long before RFID cards had any validity on TfL services. Neither Barclaycard nor TfL had bothered to warn me. ------------------------------------------------------------------------------------------------------------------------ I think you contradicted your own claim here If both cards are valid for the journey then you are right that the technology may have difficulty deciding which one to charge (and certainly wont know it has made a mistake if only one tries to "connect") but cards that are not valid for the journey interfering with a card that is, is a failure of the technology and ought to have been designed out at the start Or perhaps a limitation of the technology? Are there in fact any examples of RFID systems which can handle and ignore any non-valid cards while processing a valid card? -- Richard J. (to email me, swap 'uk' and 'yon' in address) |
#4
![]() |
|||
|
|||
![]() "Richard J." wrote in message ... tim..... wrote on 18 March 2014 21:57:24 ... "Richard J." wrote in message news ![]() Roland Perry wrote on 18 March 2014 20:47:53 ... In message , at 20:03:09 on Tue, 18 Mar 2014, Mizter T remarked: On 18/03/2014 19:34, Roland Perry wrote: http://metro.co.uk/2014/03/16/thousa...for-bus-after- oyster-readers-charge-wrong-card-in-contactless-glitch-4610552/ "Just under one per cent of all Oyster and contactless journeys involve a card clash and we are seeing this number continue to drop each week." Sorry, but 1% seems very high. My experience of card clash is an error 94 & the gates don't open. I didn't think that gates were enabled for contactless cards yet. Given there's a not-insignificant trial running, I'd suggest they are. I'd forgotten about the trial. But it's very worrying that they are charging the credit cards of people not signed up to the trial. That seems to me to be completely wrong, on many levels (for example, it means anyone can join the 'trial' just by proffering their card). The Metro story you referenced in the original post refers to buses - CPC acceptance is not a trial on buses, it's been accepted as a fare payment method since December 2012. I know, but someone mentioned "gates" (error 94 etc), which I don't recall ever seeing on a bus. FWIW, trying my contactless credit card on validators (both on gates and standalone) has resulted in an error message, can't remember which one. There are now posters and signs around the transport network warning against card clash, but I think the message should have been delivered earlier and more forcefully. That's another message from the newspaper article - the need for such warnings, which are quite frankly a desperate attempt to cover up a massive technology failure. I'm not sure I'd describe it as a *technology* failure. The passenger has presented a set of cards to the reader, two of which have validity for the journey. What do you expect to happen in those circumstances? If the card furthest away from the reader pad is on the edge of the acceptable range, it may or may not be read. So you might get a card clash (neither card accepted - try again) or you might have the nearest card used for the journey. The failure is the lack of communication for several YEARS, by both TfL and the banks. It took me some time to realise that the frequent mis-read of my Oyster (Freedom Pass) at Tube stations was caused by the RFID Barclaycard in the same wallet. That was long before RFID cards had any validity on TfL services. Neither Barclaycard nor TfL had bothered to warn me. ------------------------------------------------------------------------------------------------------------------------ I think you contradicted your own claim here If both cards are valid for the journey then you are right that the technology may have difficulty deciding which one to charge (and certainly wont know it has made a mistake if only one tries to "connect") but cards that are not valid for the journey interfering with a card that is, is a failure of the technology and ought to have been designed out at the start Or perhaps a limitation of the technology? Are there in fact any examples of RFID systems which can handle and ignore any non-valid cards while processing a valid card? ------------------------------------------------------------------------------ This isn't really the point at which the technology has failed if an RFID can't cope with this then that's the technology that's been poorly implemented tim |
#5
![]() |
|||
|
|||
![]()
In message , at 21:32:05 on Tue, 18 Mar
2014, Richard J. remarked: There are now posters and signs around the transport network warning against card clash, but I think the message should have been delivered earlier and more forcefully. That's another message from the newspaper article - the need for such warnings, which are quite frankly a desperate attempt to cover up a massive technology failure. I'm not sure I'd describe it as a *technology* failure. The passenger has presented a set of cards to the reader, two of which have validity for the journey. What do you expect to happen in those circumstances? A properly designed system would instruct the cards to back-off for a pseudo random period, then interrogate again. At that point it's much more likely that only one would respond. Yes, I know it doesn't currently work like that. If the card furthest away from the reader pad is on the edge of the acceptable range, it may or may not be read. So you might get a card clash (neither card accepted - try again) or you might have the nearest card used for the journey. Another, lower-tech, option would be to have twin pads. One for Oyster and another for contactless credit cards. The failure is the lack of communication for several YEARS, by both TfL and the banks. It took me some time to realise that the frequent mis-read of my Oyster (Freedom Pass) at Tube stations was caused by the RFID Barclaycard in the same wallet. That can't be the case, because there's a combined Oyster/Contactless Barclaycard which has worked perfectly well for years as an Oyster on an Oyster-only pad. That was long before RFID cards had any validity on TfL services. Neither Barclaycard nor TfL had bothered to warn me. Clashes have been known about for years - I used to have a door-entry rfid card which I could not keep in my regular wallet as it interfered with the Oyster. -- Roland Perry |
#6
![]() |
|||
|
|||
![]()
I'm not sure I'd describe it as a *technology* failure. The passenger
has presented a set of cards to the reader, two of which have validity for the journey. What do you expect to happen in those circumstances? A properly designed system would instruct the cards to back-off for a pseudo random period, then interrogate again. I still don't understand how that tells it which of the two valid cards to use. On the theory that the fairly bad always triumphs over the good, I expect the solution will be tin foil hat wallete with an external pocket. My wallet has internal shielding on each card pocket so that none of the cards in it are visible to external readers. It would not be hard to make a modified version of such a wallet with one pocket deliberately left unshielded, so you can use it to touch in without removing the card from the wallet. I understand all the reasons such an approach stinks, e.g., for people who use the Oyster to get to work and a company ID to unlock the office door, but you heard it here first. -- Regards, John Levine, , Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. http://jl.ly |
#7
![]() |
|||
|
|||
![]()
In message , at 14:52:30 on Wed, 19 Mar
2014, John Levine remarked: I'm not sure I'd describe it as a *technology* failure. The passenger has presented a set of cards to the reader, two of which have validity for the journey. What do you expect to happen in those circumstances? A properly designed system would instruct the cards to back-off for a pseudo random period, then interrogate again. I still don't understand how that tells it which of the two valid cards to use. If it got an answer from both (with a suitable separation), it could decide to use the season ticket rather than the PAYG. Doesn't have to take just the first one, especially just after it had detected a clash. -- Roland Perry |
#8
![]() |
|||
|
|||
![]()
I still don't understand how that tells it which of the two valid
cards to use. If it got an answer from both (with a suitable separation), it could decide to use the season ticket rather than the PAYG. Doesn't have to take just the first one, especially just after it had detected a clash. I suppose, but that still doesn't help in the many cases where there is no clear reason to prefer one card over another. It seems a poor use of funds to redo the gates when it will only help sometimes. Like I said, people will get wallets that more or less solve the problem. -- Regards, John Levine, , Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. http://jl.ly |
#9
![]() |
|||
|
|||
![]() "John Levine" wrote in message ... I still don't understand how that tells it which of the two valid cards to use. If it got an answer from both (with a suitable separation), it could decide to use the season ticket rather than the PAYG. Doesn't have to take just the first one, especially just after it had detected a clash. I suppose, but that still doesn't help in the many cases where there is no clear reason to prefer one card over another. It seems a poor use of funds to redo the gates when it will only help sometimes. ------------------------------------------------------------------------- The gates get reprogrammed software frequently However ISTM that the time taken to wait for the delay between the cards re-transmitting is going to be a killer here - especially if you've three (or four) cards tim |
#10
![]() |
|||
|
|||
![]()
In message , at 18:24:08 on Wed, 19 Mar
2014, John Levine remarked: I still don't understand how that tells it which of the two valid cards to use. If it got an answer from both (with a suitable separation), it could decide to use the season ticket rather than the PAYG. Doesn't have to take just the first one, especially just after it had detected a clash. I suppose, but that still doesn't help in the many cases where there is no clear reason to prefer one card over another. If I have two+ contactless credit cards then I really don't care which of them TfL use, as long as they only use ones I've signed up to my "capped account" of course. It seems a poor use of funds to redo the gates when it will only help sometimes. I think they've vastly underestimated the number of people with more than one 'rfid' card. In the near future there are likely to be lots of people with at least one ITSO card, as well as one Credit Card, even if they have decided to give up on Oyster. Like I said, people will get wallets that more or less solve the problem. I've already had to do that (perhaps six years ago). How many different wallets do they want people to have? And remember that one of the USPs of Oyster was *not* needing to take it out of your wallet to use. -- Roland Perry |
Reply |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
TfL admits to card-clash | London Transport | |||
Travel Card vs. Oyster Card | London Transport | |||
Oyster Card And Travel Card Question | London Transport | |||
Travel card month card cheaper than Oyster ? | London Transport | |||
difference between Gold Record Card and Record Card | London Transport |