Requirements Fee Computer version 2.1.4.5 and above IOSY chip version 2.0 and above
Connection This is the specification of the I/O Connector for single track: Molex 6 pin 22-01-2061 0.100 inch Contact Spacing Mates to Molex 22-05-2061 Pins assignment:
Color Signal 1 Yellow Data 2 Orange Card present 3 Green Strobe 4— Key 5 Red Vcc 6 Brown GND The signal pins Datapark uses are Data, Strobe, Vcc and GND. Connect the reader to reader port 1 or 2 on DP 350: D1 = Data D0 = Strobe Reader Ports power on the DP 350 is 12V, so do not connect the reader to it, it will get burnt! Use 5V from another pin, for example the MAG output There is a hardware setting to enable ABA cards. it is a jumper on DP6010, JP5, it has to be ON to enable ABA cards i've circled it on the picture (attached)
Configuration Steps Reader port=the one you connected the reader to (i.e. [ReaderPorts] ReaderPort2=EXIT) Reader format=ABA These ticktes are not validated (erased) when they are exited. So we can’t know if the ticket was paid or exited and so on. This way it can be used for exiting again.. In order to prevent this, all used tickets are kept in a table in the NVRAM structure. The data stored in the table for a single ticket is: exit time; tkt number When a ticket wants to exit the FC first checks if it is in that table, if it is – PASSBACK ERROR. If not – the ticket is allowed exiting and is inserted in the table. The table can
contain 3000 tickets and they are cleared after they have been outlot for a certain period of time. This period is defined in the config.ini [FeeComp] MagStripeTktsClearPeriod = 24 ; default 24 in hours When a ticket exits its exit time is written into the table together with its number so 24 hours after its exit time it is deleted from the table. The info from the payment is added ini the revenue reports diDo, Datapark QA Team