Paylink Coin Count Error

Support for the Milan Intelligent interface, sold by Money Controls as the Paylink USB unit and for the earlier PCI card version.

Moderators: aardvark, davebush, Admin

Post Reply
oupablo
Posts: 4
Joined: Tue Dec 03, 2013 8:35 pm

Paylink Coin Count Error

Post by oupablo »

I've emailed support but I will also put this here to see if anyone else has experienced this problem.

I'm having an issue with the paylink and a NRI Currenza C2 coin recycler.

The issue occurs as follows:

Connect C2 to paylink
Enable AESCDriver
Run AESCDemo program to monitor input
Insert Nickel (registers fine)
Disconnect C2 from paylink
Insert Two Nickels
Reconnect C2 to paylink
Paylink continuously reads as if nickels are being inserted

The issue does not seem to happen if only one nickel is inserted while the device is disconnected. Only when more than one coin is inserted. To fix the issue, the coin device must be power cycled. The display on the device shows change counts correctly.

Here is the output from the paylink when this happens:

Configuration file: Standard.cfg
05 August 2014 Driver:1.2.0.1
13:16:47.258 PC: Driver restart (after crash)

13:16:47.400 Timeout: read 5000, write 5000
13:16:47.400 FT2232C end points in 2 out 129
13:16:47.400 FTDI chip type : 3
13:16:47.400 Baudrate : 9600
13:16:47.400 Bitbang mode state : 0
13:16:47.400 FT2232C interface number : 0
13:16:47.400 FT2232C index number : 0
13:16:47.400 Bitbang mode : 1
13:16:47.400 EEPROM size : 128

13:16:47.448 USB: PC (re)started

13:16:47.512 Config: Paylink Checked OK against file "Standard.cfg"
13:16:47.514 PC: Memory Reset - new protocol

13:16:47.563 USB: PC Link Up

13:16:47.734 DP: CCNet acceptor 120b0e01 at ba0 and 7 coins
setup

13:16:48.002 DP: MDB acceptor 2080000 at da4 and 5 coins
setup

13:16:48.245 DP: Level 2 Tube Hopper S/N 10128051, Address 12, Value 100 at f38 setup

13:16:48.314 DP: Bill to bill Cassette Hopper S/N 999999, Address 1, Value 100 at f84 setup

13:16:48.386 DP: Level 2 Tube Hopper S/N 10128051, Address 11, Value 25 at fd8 setup

13:16:48.458 DP: Level 2 Tube Hopper S/N 10128051, Address 10, Value 10 at 1024 setup

13:16:48.530 DP: Level 2 Tube Hopper S/N 10128051, Address 9, Value 5 at 1070 setup

13:16:48.606 DP: Level 3 Payout System Hopper S/N 10128051, Address 8, Value 5 at 10bc setup

13:16:48.904 DP: Interface memory set up
13:16:48.904
13:16:48.904 PC: *** USB unit major memory reset ***
13:16:48.904
05 August 2014 Firmware: 4.1.12.6 from Aug 22 2013 at Aug 22 2013 Driver:1.2.0.1
13:16:48.904 Exec: DP App. task took 1341 msec

13:16:50.406 7376 bytes memory free

13:17:08.897
13:17:08.897
13:17:08.897 DP: Application active
13:17:08.897 DP: Interface memory recovery - payout recovered
13:17:08.897 CCNet: Enable
13:17:08.897 DP: CCNet Status to 0
13:17:08.897 MDB: Enable
13:17:08.897 DP: MDB Status to 0
13:17:08.897 MDB: inhibits to 001f
13:17:08.897 DP: Resending Events
13:17:08.897 DP: Event 0003
13:17:08.897 DP: Turn off barcodes
13:17:08.897 CCNet: inhibits to ff ff ff

13:17:08.961 CCNet: Status 14

13:17:09.343 DP: Event 0001

13:17:09.839 DP: Event 0002

13:17:10.349 DP: Event 000120 for Acceptor 0

13:17:10.893 DP: Event 0100c8 for Acceptor 1

13:17:11.369 DP: Event 0000a0 for Dispenser 5

13:17:16.389 00:02

13:17:20.626 MDB: 0 > 0b
13:17:20.626 MDB: 310 > 0b
13:17:20.626 MDB: 60 > 0b
13:17:20.626 MDB: 60 > 0a
13:17:20.626 MDB: Missing response from MDB @ 8
13:17:20.626 DP: MDB Status to 41
13:17:20.626 DP: Event 0000e2 for Acceptor 1

13:17:25.703 Exec: DP App. task took 68 msec
13:17:25.703 MDB Tube@9: for 5 - reported coins 39=>41

13:17:25.814 Exec: DP App. task took 100 msec
13:17:25.814 MDB: Selftest OK
13:17:25.814 MDB: Read coin 1 to tube 1 - 41 in tube

13:17:25.857 DP: MDB Status to 0
13:17:25.857 DP: Coin 1: sent to hopper, 3452 read, 0 limit
13:17:25.857 DP: Event 0000e0 for Acceptor 1
13:17:25.857 Exec: DP App. task took 41 msec

13:17:26.009 MDB: Read coin 1 to tube 1 - 41 in tube
13:17:26.009 DP: Coin 1: sent to hopper, 3453 read, 0 limit

13:17:26.152 MDB: Event 1=>8
13:17:26.152 DP: Event 0100c8 for Acceptor 1

13:17:26.259 MDB: Read coin 1 to tube 1 - 41 in tube
13:17:26.259 DP: Coin 1: sent to hopper, 3454 read, 0 limit

13:17:26.515 MDB: Read coin 1 to tube 1 - 41 in tube
13:17:26.515 DP: Coin 1: sent to hopper, 3455 read, 0 limit

13:17:26.769 MDB: Read coin 1 to tube 1 - 41 in tube
13:17:26.769 DP: Coin 1: sent to hopper, 3456 read, 0 limit

13:17:27.024 MDB: Read coin 1 to tube 1 - 41 in tube
13:17:27.024 DP: Coin 1: sent to hopper, 3457 read, 0 limit

13:17:27.279 MDB: Read coin 1 to tube 1 - 41 in tube
13:17:27.279 DP: Coin 1: sent to hopper, 3458 read, 0 limit

13:17:27.533 MDB: Read coin 1 to tube 1 - 41 in tube
13:17:27.533 DP: Coin 1: sent to hopper, 3459 read, 0 limit

13:17:27.777 MDB: Read coin 1 to tube 1 - 41 in tube
13:17:27.777 DP: Coin 1: sent to hopper, 3460 read, 0 limit

13:17:28.034 MDB: Read coin 1 to tube 1 - 41 in tube
13:17:28.034 DP: Coin 1: sent to hopper, 3461 read, 0 limit

13:17:28.279 MDB: Read coin 1 to tube 1 - 41 in tube
13:17:28.279 DP: Coin 1: sent to hopper, 3462 read, 0 limit

13:17:28.535 MDB: Read coin 1 to tube 1 - 41 in tube
13:17:28.535 DP: Coin 1: sent to hopper, 3463 read, 0 limit
davebush
Posts: 492
Joined: Fri Oct 22, 2004 12:20 pm

Re: Paylink Coin Count Error

Post by davebush »

Hi,

That is very strange - it's obviously a bug, either in the coin changer or in Paylink.

In order to see what's going on, I really need a completely clean log. If you follow these http://aesoffice.eu.com/HTTPSpace/Gener ... %20Log.pdf instructions (obviously you'll need "d mdb") to capture the relevant trace, and then attach / e-mail the resultant file, I'll check it out.

Dave
Aardvark software developer. Please put all communication on the problem through the board for the benefit of others.
oupablo
Posts: 4
Joined: Tue Dec 03, 2013 8:35 pm

Re: Paylink Coin Count Error

Post by oupablo »

Thanks Dave. At this point it sounds like a bug in the coin changer. The changer company has just sent me a firmware update. If that doesn't work, I'll send you the MDB output to help track down what's down.
Post Reply