Skip to main content

New system from Rinas points way to continuous RFID ticket encoding

Magnetic stripe encoding and verification specialist Rinas has developed a continuous ticket personalisation system for RFID ticketing. The system accepts continuous pre- printed tickets either in fan-folded form or in batch rolls containing anything up to 3,000 individual tickets.
October 28, 2014 Read time: 2 mins
Rinas RFID Avatar
Magnetic stripe encoding and verification specialist Rinas has developed a continuous ticket personalisation system for RFID ticketing.

The system accepts continuous pre- printed tickets either in fan-folded form or in batch rolls containing anything up to 3,000 individual tickets. The length of each ticket is entered as a software parameter while the width is mechanically adjusted and then entered as a parameter in the software.

The number of RFID transponders that can be installed using the system is limited purely by mechanical restraints but is  currently limited to six for parallel ticket processing. Up to eight (four on each side) ‘ruggedised’ print units, each fitted with a dedicated print cartridge with an integrated print head, can be cascaded for print height variation at a 12.7mm pitch. The technology in use is based on trusted HP print technology and uses the same inkjet expertise in daily use by millions of office printers. The system also enables scanner units to be integrated for OCR tasks, barcode or 2D code recognition, database retrieval of personalisation information and quality inspection tasks after printing.

It is also capable of marking and logging tickets with defective transponders. Once personalised, the new drum or container of fan-folded individually personalised tickets can be lifted off the unit ready to be installed into a ticket vending machine. Rinas says that, with minimal intervention, the machine is capable of conversion for more ambitious tasks involving the encoding of both RFID and MagStripe continuous tickets. The MagStripe option has more variables, however, so this would require a more detailed customer specification. %$Linker: 2 External <?xml version="1.0" encoding="utf-16"?><dictionary /> 0 0 0 oLinkExternal <span class="mouselink">www.rinas.com</span> Visit www.rinas.com Website false http://www.rinas.com/ false false%>
boombox1
boombox2