We have a machine with a setup which consists of a SR5 acceptor and 2 MCL MK3 Compact hoppers. One hopper is address 3 and the other is address 10 BUT both hoppers have the value of 100 as we update the value field of the Dispenser Block as we need the extra capacity.
We get a problem where the SR5 will continually reject coins if they are put in one after each other, directly after/during an acceptor coin path update. However if we wait for a second or two, the acceptor will accept the coin with no problem. We know it has something to do with updating the acceptors coin path BUT we need to do this as the PathSwitchLevel is no use as that can only use 2 paths. This is no good if you have 2 hoppers of the same value as we need to manualy update the coin path so we can topup both hoppers as needed.
Can you suggest anything to fix / workaround this problem ?
Regards.
Coin acceptor reject during coin path update.
Moderators: aardvark, davebush, Admin
Here is a copy of the log from when hopper 1 required 2 x 100 coins to be full and thus requiring to update the coin path to divert to the other hopper which was low.
18:17:08.468 Coin: New event 54, Old 53, coin 1 to 4
18:17:09.140 Coin: New event 55, Old 54, coin 1 to 4
18:17:09.687 Coin: Path enables 7c ==> 7c
18:17:09.703 Coin: Modify paths for coin 1 to 2 / 3
18:17:10.156 Coin: New event 57, Old 55, event 19=>5, event 254=>8
18:17:10.156 DP: ccTalk coin Status to 40
18:17:10.171 DP: Event 1300c5 for Acceptor 1
18:17:10.218 Coin: Selftest OK
18:17:10.234 DP: ccTalk coin Status to 0
18:17:10.296 DP: Event fe00c8 for Acceptor 1
18:17:10.312 Acc: cc Note Disable
18:17:10.312 DP: cc Note Status to 4
18:17:10.312 Acc: ccTalk coin Disable
18:17:10.312 DP: ccTalk coin Status to 4
18:17:10.328 DP: Hopper for 100 Inhibited
18:17:10.328 DP: Hopper for 1 Inhibited
18:17:10.328 Coin: Inhibit all coins
18:17:10.468 Note: Disable acceptance
18:17:10.968 DP: Event 0000e0 for Acceptor 1
18:17:11.125 Coin: New event 58, Old 57, event 254=>8
18:17:11.140 DP: ccTalk coin Status to 44
18:17:11.187 Coin: Selftest OK
18:17:11.203 DP: ccTalk coin Status to 4
18:17:11.468 DP: Event fe00c8 for Acceptor 1
18:17:11.968 DP: Event 0000e0 for Acceptor 1
18:17:12.281 Coin: New event 59, Old 58, event 254=>8
18:17:12.281 DP: ccTalk coin Status to 44
18:17:12.343 Coin: Selftest OK
18:17:12.343 DP: ccTalk coin Status to 4
18:17:12.468 DP: Event fe00c8 for Acceptor 1
18:17:12.968 DP: Event 0000e0 for Acceptor 1
18:17:13.109 Coin: New event 60, Old 59, event 254=>8
18:17:13.109 DP: ccTalk coin Status to 44
18:17:13.171 Coin: Selftest OK
18:17:13.171 DP: ccTalk coin Status to 4
18:17:13.468 DP: Event fe00c8 for Acceptor 1
18:17:13.968 DP: Event 0000e0 for Acceptor 1
18:17:14.171 Coin: New event 61, Old 60, event 254=>8
18:17:14.171 DP: ccTalk coin Status to 44
18:17:14.234 Coin: Selftest OK
18:17:14.234 DP: ccTalk coin Status to 4
18:17:14.468 DP: Event fe00c8 for Acceptor 1
18:17:14.953 DP: Event 0000e0 for Acceptor 1
18:17:15.296 Coin: New event 62, Old 61, event 254=>8
18:17:15.296 DP: ccTalk coin Status to 44
18:17:15.359 Coin: Selftest OK
18:17:15.359 DP: ccTalk coin Status to 4
18:17:15.468 DP: Event fe00c8 for Acceptor 1
18:17:15.968 DP: Event 0000e0 for Acceptor 1
18:17:16.046 Coin: New event 63, Old 62, event 254=>8
18:17:16.046 DP: ccTalk coin Status to 44
18:17:16.109 Coin: Selftest OK
18:17:16.109 DP: ccTalk coin Status to 4
18:17:16.468 DP: Event fe00c8 for Acceptor 1
18:17:16.968 DP: Event 0000e0 for Acceptor 1
18:17:08.468 Coin: New event 54, Old 53, coin 1 to 4
18:17:09.140 Coin: New event 55, Old 54, coin 1 to 4
18:17:09.687 Coin: Path enables 7c ==> 7c
18:17:09.703 Coin: Modify paths for coin 1 to 2 / 3
18:17:10.156 Coin: New event 57, Old 55, event 19=>5, event 254=>8
18:17:10.156 DP: ccTalk coin Status to 40
18:17:10.171 DP: Event 1300c5 for Acceptor 1
18:17:10.218 Coin: Selftest OK
18:17:10.234 DP: ccTalk coin Status to 0
18:17:10.296 DP: Event fe00c8 for Acceptor 1
18:17:10.312 Acc: cc Note Disable
18:17:10.312 DP: cc Note Status to 4
18:17:10.312 Acc: ccTalk coin Disable
18:17:10.312 DP: ccTalk coin Status to 4
18:17:10.328 DP: Hopper for 100 Inhibited
18:17:10.328 DP: Hopper for 1 Inhibited
18:17:10.328 Coin: Inhibit all coins
18:17:10.468 Note: Disable acceptance
18:17:10.968 DP: Event 0000e0 for Acceptor 1
18:17:11.125 Coin: New event 58, Old 57, event 254=>8
18:17:11.140 DP: ccTalk coin Status to 44
18:17:11.187 Coin: Selftest OK
18:17:11.203 DP: ccTalk coin Status to 4
18:17:11.468 DP: Event fe00c8 for Acceptor 1
18:17:11.968 DP: Event 0000e0 for Acceptor 1
18:17:12.281 Coin: New event 59, Old 58, event 254=>8
18:17:12.281 DP: ccTalk coin Status to 44
18:17:12.343 Coin: Selftest OK
18:17:12.343 DP: ccTalk coin Status to 4
18:17:12.468 DP: Event fe00c8 for Acceptor 1
18:17:12.968 DP: Event 0000e0 for Acceptor 1
18:17:13.109 Coin: New event 60, Old 59, event 254=>8
18:17:13.109 DP: ccTalk coin Status to 44
18:17:13.171 Coin: Selftest OK
18:17:13.171 DP: ccTalk coin Status to 4
18:17:13.468 DP: Event fe00c8 for Acceptor 1
18:17:13.968 DP: Event 0000e0 for Acceptor 1
18:17:14.171 Coin: New event 61, Old 60, event 254=>8
18:17:14.171 DP: ccTalk coin Status to 44
18:17:14.234 Coin: Selftest OK
18:17:14.234 DP: ccTalk coin Status to 4
18:17:14.468 DP: Event fe00c8 for Acceptor 1
18:17:14.953 DP: Event 0000e0 for Acceptor 1
18:17:15.296 Coin: New event 62, Old 61, event 254=>8
18:17:15.296 DP: ccTalk coin Status to 44
18:17:15.359 Coin: Selftest OK
18:17:15.359 DP: ccTalk coin Status to 4
18:17:15.468 DP: Event fe00c8 for Acceptor 1
18:17:15.968 DP: Event 0000e0 for Acceptor 1
18:17:16.046 Coin: New event 63, Old 62, event 254=>8
18:17:16.046 DP: ccTalk coin Status to 44
18:17:16.109 Coin: Selftest OK
18:17:16.109 DP: ccTalk coin Status to 4
18:17:16.468 DP: Event fe00c8 for Acceptor 1
18:17:16.968 DP: Event 0000e0 for Acceptor 1
Hi,
The event 19=>5 immediately after you change routing, is generated by the SR5 (nothing to do with Paylink) and inidcates a problem with the passage of the coin through the mech. All the remaining events are pressimng the reject level.
Can you re-post a new trace, making it clearer where the reject coin problem occurs?
The event 19=>5 immediately after you change routing, is generated by the SR5 (nothing to do with Paylink) and inidcates a problem with the passage of the coin through the mech. All the remaining events are pressimng the reject level.
Can you re-post a new trace, making it clearer where the reject coin problem occurs?
Aardvark software developer. Please put all communication on the problem through the board for the benefit of others.
The problem occurs when a coin is inserted when the path is changed (Line 4). At no point was the reject lever pressed... several £1 coins were inserted and rejected.
We have since spoken to MC and they say it is NOT possible for the SR5 to accept a coin during a path change as the mech is in the process of updating the E2 memory. They have advised that the SR5i should be used instead of the SR5 as the updating time is far less.
We have since spoken to MC and they say it is NOT possible for the SR5 to accept a coin during a path change as the mech is in the process of updating the E2 memory. They have advised that the SR5i should be used instead of the SR5 as the updating time is far less.
No problem... the strange thing is that the coin acceptor will continue to reject coins if the are continually put in one after each other after a path update. The get an accept you must wait for 1-2 sec after the last coin insert and try again.
Is this somehting that can be changed in the paylink or is it just because the SR5 is slow ?
Is this somehting that can be changed in the paylink or is it just because the SR5 is slow ?