Ticket gate error 134

[Ed92uk]

Can anybody confirm what this code means?

Just had ticket rejected at BHM. No issue from staff with myself but it was escalated to 3 different people to let me through the gate. They said ticket has been used before however I am 100% certain that’s impossible. Return portion of an anytime which was checked on train and stamped with date etc so can prove I had just got off the train. They confiscated it (again no issue personally) and let me through but when they shouted theb3rd member of staff over I was getting a little worried!

 

[philthetube]

Did they take your details?

 

[Starmill]

Was Birmingham New Street where your journey ended?

 

[TEW]

Error code 134 is 'previously used'.

 

[Cantab26]

Error code 134 is 'previously used'.

I have had this error code at Birmingham New Street with the unused return portion of an Anytime Return on several occasions in the recent past. I wonder if there may be an error in the programming?

 

[Wallsendmag]

Were you both returning on the same day as you outward trip?


Sent from my iPhone using Tapatalk Pro

 

[Cantab26]

Were you both returning on the same day as you outward trip?


Sent from my iPhone using Tapatalk Pro

In my case, I was returning on a later day on each occasion.

 

[Wallsendmag]

That’s probably the problem , we’ve found some tickets are encoded with the start date and a period of validity but some gatelines just read the start date


Sent from my iPhone using Tapatalk Pro

 

[CyrusWuff]

This generally seems to be an issue with tickets issued on Tribute, as it strictly adheres to the RSP spec when initially writing the magstripe by encoding the date and time of issue to the "last used" portion of the data block.

Unfortunately, most ticket barriers don't adhere to the spec and throw an erroneous "used already" error. It's possible to verify the non-use by reading the ticket on a Desktop TIS, however.

 

[Haywain]

That’s probably the problem , we’ve found some tickets are encoded with the start date and a period of validity but some gatelines just read the start date

In which case the ticket should be rejected as out of date rather than previously used.

This generally seems to be an issue with tickets issued on Tribute, as it strictly adheres to the RSP spec when initially writing the magstripe by encoding the date and time of issue to the "last used" portion of the data block.

Unfortunately, most ticket barriers don't adhere to the spec and throw an erroneous "used already" error. It's possible to verify the non-use by reading the ticket on a Desktop TIS, however.

Having worked on a route where Tribute was used and barriers are in place I have not seen this problem. Certainly the largest supplier of gateline hardware, Cubic, would have long since ironed out any problems caused by allegedly not adhering to the RSP spec.

 

[Wallsendmag]

At a recent test the same error code showed for several different reject reasons


Sent from my iPhone using Tapatalk Pro

 

[CyrusWuff]

Having worked on a route where Tribute was used and barriers are in place I have not seen this problem. Certainly the largest supplier of gateline hardware, Cubic, would have long since ironed out any problems caused by allegedly not adhering to the RSP spec.

Well it's what the evidence is pointing to in my experience at work. I'd say that 99% (if not 100%) of the tickets incorrectly flagged as already used have been issued on Tribute, and we've got Cubic gates. That's got to be more than mere coincidence.

 

[Ed92uk]

My return was used the day after outward. No details were taken they just took the ticket which was fine by me.

 

[AY1975]

The magnetic strip on the back of tickets is perfectly good 1980s/90s technology, but it has its limitations and presumably can't cope with the sheer complexity of different ticket types that there are these days. I suppose it was only designed to have to go through London Underground ticket gates.

Some tickets, such as those issued by Virgin East Coast, now have barcodes on them - I presume these will eventually completely replace the magnetic strip, as I think barcode readers use more sophisticated technology. The sooner this happens, the better. So far I haven't managed to get the barcode on a normal credit card-sized ticket to work the ticket gates, though.

 

[Wallsendmag]

Unfortunately the VTEC gatelines cant read the barcodes on CCST stock.


Sent from my iPad using Tapatalk Pro

 

[boxy321]

The magnetic strip on the back of tickets is perfectly good 1980s/90s technology, but it has its limitations and presumably can't cope with the sheer complexity of different ticket types that there are these days. I suppose it was only designed to have to go through London Underground ticket gates.

Some tickets, such as those issued by Virgin East Coast, now have barcodes on them - I presume these will eventually completely replace the magnetic strip, as I think barcode readers use more sophisticated technology. The sooner this happens, the better. So far I haven't managed to get the barcode on a normal credit card-sized ticket to work the ticket gates, though.

Tell me that when I have to queue up to get my faulty season ticket reprinted every month. Yes I know not to put it near a phone. Yes I know not to to put it near other cards. Yes it probably is the X-ray machine or whetever at the Post Office.

 

[swt_passenger]

I'm interested in how the gates will mark barcode tickets to prevent repeated reuse, pass back etc etc. Not necessarily the panacea people hope for...

 

[AlterEgo]

I'm interested in how the gates will mark barcode tickets to prevent repeated reuse, pass back etc etc. Not necessarily the panacea people hope for...

Surely the ticket isn't marked, but the database updated to say where a barcode has been scanned? Are all barcode scanners linked like this?

 

[swt_passenger]

Surely the ticket isn't marked, but the database updated to say where a barcode has been scanned? Are all barcode scanners linked like this?

No idea if they are linked - wouldn't that require an unlikely level of cooperation between all the TOCs back office systems? The same TOCs who can't or won't make ITSO work across TOC boundaries?

If you want all transactions to be fed to a back office via bar-codes won't you also need a 100% barriered network?

 

[AlterEgo]

No idea if they are linked - wouldn't that require an unlikely level of cooperation between all the TOCs back office systems? The same TOCs who can't or won't make ITSO work across TOC boundaries?

If you want all transactions to be fed to a back office via bar-codes won't you also need a 100% barriered network?

Wouldn't require a 100% barriered network, no. There are lots of paper tickets which never get marked and I don't see why that would be any different for a barcode?

 

[Wallsendmag]

I'm interested in how the gates will mark barcode tickets to prevent repeated reuse, pass back etc etc. Not necessarily the panacea people hope for...

That’s called an e-TVD already in use every time a ticket is scanned a record is added to its history very very useful . There are four different suppliers I believe and the systems can all talk to each other. Gates and onboard TIS can all add records almost instantly.


Sent from my iPhone using Tapatalk Pro