We want to encode any RFID card (for example a transport card) or even Dual EMV cards, encode the magnetic stripe, print the name with UV DOD inkjet on the front, and print the 3 digit security code with a laser. As fast as possible.
How do we do that? This paper only handles the principle and the handshake.
We do this by feeding 10 or 20 cards into our Radio frequency Encoding Section & Transport (REST), holding the cards under the antennas until encoded via RFID, then we go into our RoadRunner III section where we first read the UID to make synchronization absolutely sure, encode the magnetic stripe, print with our DOD inkjet the front of the card, and print the security code with a laser on the back.
It is important to notice that REST Server can be made/implemented by any company, provided the handshake between the REST Server and the RoadRunner controller is clear. Last but not least, programming the cards is the bottleneck, the REST Server shall encode 10 cards in parallel as fast as it encodes 1 card !
The RoadRunner is a proven system with DOD inkjets used to personalize cards in the retail business, like gift cards, membership cards (AARP for example), medical cards, etc.
The Master is the roadrunner controller which:
- Will send the 10 account numbers (with track1 or track2 data) to the REST Server
- Directs the feeder to feed 10 (or 20 cards) onto REST
- Will tell the REST Server that the 10 products are mechanically under the antenna
- REST server will handshake with the 10 antennas and encode (EMV) data onto the cards
- REST server will tell Master that it finished encoding the 10 cards with UID and good/bad
- Master will take the 10 cards further to the Roadrunner and repeat steps 1) to 5) for the next 10
- Master will read the UID at the beginning of the RoadRunner to make sure synchronization is right
- Master will mag-encode (the mag-encoder can alternatively be installed in the feeder at the beginning: TotalMag option), inkjet, and laser the good cards. Bad cards are rejected, slated for remake
REST Server and RoadRunner controller handshake
Protocol: tcp/ip, non blocking
Endpoint: REST Server (The RoadRunner controller will connect to REST Server through tcp/ip at production start)