Br2300 recycler connection by cctalk

[xagduran]

Hi:
We have to connect by cctalk, a BR2300 recycler.
What is the line to put in the Standard.cfg file or which one should be uncommented?
By MDB it works perfectly, but not cctalk, we could not detect it by Paylink
We need to connect it by cctalk, because we are going to use the banknote recycler, by MDB it is not possible, so it would go to level 3, and we can use the recycler to return tickets.
Thank you.
Greetings.

[davebush]

You need Paylink version 4.1.12.10 or later.

The configuration line is:

Code: Select all

ICT Recycler at 40 CRC BNV 123456

[xagduran]

Hello:
We have put the line as you have indicated, the line accepts it perfectly, it is not an error, but it still does not detect the BR2300.
This is what comes out.
Thanks in advance.
23: 45: 40.935 d cctalk
23: 45: 40.935 Task: cctalk, debug on
23: 45: 40.935 $ Config: Unknown 1/16
23: 45: 42.748 Config: Unknown 1/16
23: 45: 43.748 Config: Unknown 1/16
23: 45: 44.217 7800 bytes memory free
23: 45: 44.748 Config: Unknown 1/16
23: 45: 45.748 Config: Unknown 1/16
23: 45: 46.733 Config: Unknown 1/16
23: 45: 47.733 Config: Unknown 1/16
23: 45: 48.733 Config: Unknown 1/16
23: 45: 49.718 Config: Unknown 1/16
23: 45: 50.733 Config: Unknown 1/16

[davebush]

Hi,

The error Config: Unknown is the slightly unclear diagnostic that you are running the wrong version of the firmware for the configuration.

For an ICT recycler, you need to load and run the InnovV4-1-12-11firmware. http://aardvark.eu.com/downloads/softwa ... -12-11.zip

Paylink is a relatively old design and now handles many more peripherals than were originally intended. This means that the space for the firmware is no long large enough to load every handler, so the slightly less common ones are handled in separate firmware builds.

Regards

dave

[xagduran]

Hello:
Thank you very much, with your instructions we have already made Paylink detect the BR2300 Recycler by Cctalk.
Acceptors on the system are:
Acceptor 0: Unknown code 12020602 - <~~ V1.15-BTBP00HVG050000EU405 ~ BTB>, Serial Number 9054464,
Default Path 0, Currency <EU>, 4 coins:
Coin 0: <EU0005A>, Value 500, Count 9, Path 0, Coins 0
Coin 1: <EU0010A>, Value 1000, Count 3, Path 0, Coins 0
Coin 2: <EU0020A>, Value 2000, Count 0, Path 0, Coins 0
Coin 3: <EU0050A>, Value 5000, Count 0, Path 0, Coins 0
Acceptor 1: MDB Level 3 Changer - <1978 ~ 2 ~ ICT ~ CCM6-EUR MDB ~ 0552>, Serial Number 211392708,
Default Path 0, Currency <978>, 6 coins:
Coin 0: <5 * 1>, Value 5, Count 0, Path 1, Coins 0, Default Path -1
Coin 1: <10 * 1>, Value 10, Count 0, Path 2, Coins 0, Default Path -1
Coin 2: <20 * 1>, Value 20, Count 0, Path 3, Coins 0, Default Path -1
Coin 3: <50 * 1>, Value 50, Count 2, Path 4, Coins 2, Default Path -1
Coin 4: <100 * 1>, Value 100, Count 4, Path 5, Coins 4, Default Path -1
Coin 5: <200 * 1>, Value 200, Count 2, Path 6, Coins 2, Default Path -1

Dispensers on the system are:
Dispenser 0: Unknown code 11020602 - <ICT Recyc>, Serial Number 9054464,
Coin Value 99999999, Number Paid 0, Current Count 0
Inhibit 0, Address 41
Dispenser 1: MDB Tube - <Level 2 Tube>, Serial Number 211392708,
Coin Value 200, Number Paid 3, Current Count 19
Inhibit 0, Address 14
Dispenser 2: MDB Tube - <Level 2 Tube>, Serial Number 211392708,
Coin Value 100, Number Paid 2, Current Count 31
Inhibit 0, Address 13
Dispenser 3: MDB Tube - <Level 2 Tube>, Serial Number 211392708,
Coin Value 50, Number Paid 2, Current Count 20
Inhibit 0, Address 12
Dispenser 4: MDB Tube - <Level 2 Tube>, Serial Number 211392708,
Coin Value 20, Number Paid 2, Current Count 0
Inhibit 0, Address 11
Dispenser 5: MDB Tube - <Level 2 Tube>, Serial Number 211392708,
Coin Value 10, Number Paid 0, Current Count 0
Inhibit 0, Address 10
Dispenser 6: MDB Tube - <Level 2 Tube>, Serial Number 211392708,
Coin Value 5, Number Paid 0, Current Count 0
Inhibit 0, Address 9
Dispenser 7: MDB Payout System - <Level 3 Payout System>, Serial Number 211392708,
Coin Value 1, Number Paid 0,
Inhibit 0, Address 8

Now, as we are new to this, we want to fill the reclador with 5 euro bills, up to an amount that we indicate, for example 10 bills.
How do we direct the 5 euro bills to the dispenser?
And then once we get them to be digested to the dispenser, when returning the change, by putting the number of the dispenser and the number of tickets, it is enough for the return, through AESImhei.SetDispenseQuantity (numberDispenser, numberCurrencies, valueAreturnForMoney. );

Thank you very much for all your attention, you have been very attentive and kind to us.
A greeting.
Angel

[davebush]

Hi,

To choose which note to recycle, you use the Path field in the AcceptorCoin object.

The AcceptorBlock has an array of these called Coin[] - you set the Path field for the Bill you want to recycle to 1, the others are all 0. You can test this with the Demo program as shown here: https://d.pr/i/IMmCOz

For Payout, you can just provide the total amount as the paramter to Payout(), and Paylink will automatically choose the coins / bills to use. If you need to override the automatic selection, that's where you would use SetDispenseQuantity and PaySpecific.

Regards

Dave

[xagduran]

Hello:
What does this message mean:
23: 58: 22.525 DP: ccNote acceptor 12020602 at ba0 updated after registration!
23: 58: 22.525 ccNote: Enable acceptance
23: 58: 22.525 ccNote: inhibits to ff ff
23: 58: 22.573 DP: Lost fault 00ff0120
23: 58: 22.616 ccNote: Selftest fail 39/21
23: 58: 22.616 DP: Lost fault 00270121
23: 58: 23.243 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 24.030 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 24.840 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 25.176 DP: ICT Recyc Hopper S / N 9054464, Address 41, Value 500 at fd0 updated
23: 58: 25.176 ICT Recyc: Recycler now has note 1, recycling 1
23: 58: 25.655 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 26.454 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 26.994 PC: Update Interlock Set. (32044! = 32043/32042)
23: 58: 26.995 PC: Interlock Now Clear. (After 1 tries.)
23: 58: 27.299 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 28.096 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 28.936 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 29.742 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 30.542 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 31.341 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 32.142 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 32.987 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 33.797 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 34.623 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 35.435 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 36.256 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 37.067 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 37.883 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 38.543 PC: Update Interlock Set. (32994! = 32992/32992)
23: 58: 38.544 PC: Interlock Now Clear. (After 1 tries.)
23: 58: 38.706 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 39.532 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 40.342 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 41.149 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 41.655 PC: Update Interlock Set. (33250! = 33248/33248)
23: 58: 41.656 PC: Interlock Now Clear. (After 1 tries.)
23: 58: 41.948 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 42.767 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 43.572 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 44.391 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 45.180 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 45.980 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 46.819 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 47.655 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 48.496 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 49.296 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 50.121 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 50.950 DP: Waiting for DLL - Latest 171920, Last 171420
23: 58: 51.759 DP: Waiting for DLL - Latest 171920, Last 171420

[davebush]

Hi,

The DLL needs to report a payout failure to the application, but the application has not called LastPayoutStatus().

In detail:
Most of the Paylink is completely decoupled, where the paylink and DLL look at shared memory and action any updates the are discovered.

A Payout is however a more complicated process, and the DLL has to complete a Payout sequence, started with Payout(), by returning to the Application the result as the return value of LastPayoutStatus().

This message is the Paylink warning that this has not happened, and that it will not action another Payout until the result of the last one has been given to the application.