Paylink - returning escrow notes issue

[mzdunek]

Hello,

We have project that is using iPRO-RC with Paylink and Combo-T from Azkoyen. We have connected it all through paylink to windows PC and launched your testing app. Accepting note escrow and routing it into recyclers of iPRO-RC works fine. But when we are pressing Payout button with amount same as accepted note, Combo-T keeps paying out change in coins, not in note that should be processed by iPRO-RC and counted in paylink.

Firmware is newest possible.

Please help us resolve this issue.

Thanks,
Marcin

[davebush]

Hi,

Paylink keeps a reasonably detailed log of what it is attempting to do and why. The default is a file called Paylink.log located in the default folder when the driver is run. Or you can run the program MilanDiag which shows you the log as it is generated.

If you have a look at the log yourself, ignoring everything that isn't clear, you might be able to see messages that you can understand. If not, then post the log here and I'll tell you what's going on.

Dave

[mzdunek]

Hello, could you check these logs?

https://pastebin.com/raw/JbfRDgYE

Thanks,
Marcin

[davebush]

Hi,

I don't know how it has happened, but the Paylink driver is trying to set a strange value in the recycler, which fails, and is not processing anything else.

Unfortunately your log doesn't go back far enough, so I can't see the start of the problem.

Can you reset everything - unplug Paylink (to power cycle it), unplug the iPro from Paylink and exit all Payulink related PC programs. Then turn things on in the sequence:

• PC Driver program
• Plug in Paylink
• Plug in iPro
• Try payout

and then send all that log.

Regards

Dave

[mzdunek]

Hello,

iPRO-RC vendor told us to update its firmware. After update we can successfully get notes back from upper recycler (10 PLN in our case), unfortunately problem still exists for lower recycler (20 PLN in our case) - iPRO didnt even make any sound or movement.

Could you read something from these logs? Or have any other advice for us?
https://pastebin.com/raw/PCuLRT7z

Thanks,
Marcin

[davebush]

Hi,

Sorry, but you still have the same problem. The log you included doesn't go back far enough.

Can you try the test I outlined, or is there a problem doing that?

Also, are you sure you are not accidentally setting a count of 12376 within your application? (It is dificult to do accidentally as you have to use WriteDispenserDetails() after setting DispenserBlock.Status to DISPENSER_UPDATE_COUNT)

Regards

Dave

[mzdunek]

Hello,

We have made everything like you said, here are logs from start of Paylink:

https://pastebin.com/raw/4xs2A22i

[davebush]

From the log,
Until 17:26:03.768 Paylink is essentially idle.

At 17:26:03.768 an application registers with the API. Between then and 17:26:05.254 a large number of set up updates are done by the application, not all of which are sensible.
The application atempts to set the coin counts of all 4 hoppers to 792 - this is rejected as hoppers do not maintain coin counts
The application sets a set of coin paths into the coin acceptor
The application atempts to set the note recycler to reycle notes 1 and 7 and 8 to box 1 - Paylink takes the last, tells the unit the send note 8 to box 1 and the unit rejects the attempt
Finally the application (probably) atempts to set the coin count of Box 1 to -8024 - the unit rejects this, but Paylink doesn't accept the rejection and gets stuck continually retrying the update.

I strongly suspect that all your problems are due the this failed attempt to set up the system.

Dave

[mzdunek]

Hello,

We have checked that even when starting device with paylink without our application it produces these logs:

Code: Select all

11:00:13.316 ID-003: Cmd Reject
11:00:13.460 ID-003: Status 4b=>1a
11:00:13.632 ID-003: Update Box 1 from 53 to -4248
11:00:13.632 ID-003: Status 1a=>4b
11:00:13.632 ID-003: Cmd Reject
11:00:13.775 ID-003: Status 4b=>1a
11:00:13.947 ID-003: Update Box 1 from 53 to -4248
11:00:13.947 ID-003: Status 1a=>4b
11:00:13.947 ID-003: Cmd Reject
11:00:14.091 ID-003: Status 4b=>1a
11:00:14.262 ID-003: Update Box 1 from 53 to -4248
11:00:14.262 ID-003: Status 1a=>4b
11:00:14.262 ID-003: Cmd Reject
11:00:14.406 ID-003: Status 4b=>1a
11:00:14.577 ID-003: Update Box 1 from 53 to -4248
11:00:14.578 ID-003: Status 1a=>4b
11:00:14.578 ID-003: Cmd Reject
11:00:14.721 ID-003: Status 4b=>1a
11:00:14.893 ID-003: Update Box 1 from 53 to -4248
11:00:14.893 ID-003: Status 1a=>4b
11:00:14.893 ID-003: Cmd Reject
11:00:15.037 ID-003: Status 4b=>1a

Could it be connected to our issue?

[davebush]

I'm reasonably sure that you have not power cycled the Paylink unit after your application last ran.

It's important to understand that restarting the Paylink.exe driver program has no effect on the running code, only power cycling the Paylink will reset to code.

Dave

[mzdunek]

Hello,

Thanks for reply. Unfortunately problem still exists. We have noticed that after power-cycling when we execute EnableInterface command, these "Update Box 1 from 53 to -4248" starts producing.

Here are newest log with Java Code that produces it:

https://pastebin.com/3KdRUdpH

[davebush]

The log still shows something triggering a change to CoinCount - are you absolutely sure you ran the listed code? As well as the ID-003 updates there is also these:

09:09:44.636 ccHopper@5: Coincount update to -19128 not implemented
09:09:44.636 ccHopper@6: Coincount update to -19128 not implemented
09:09:44.636 ccHopper@3: Coincount update to -19128 not implemented
09:09:44.636 ccHopper@18: Coincount update to -19128 not implemented

Regardless of your situation, it's not satisfactory for Paylink to hang just becasue of an invalid parameter so we have updated the ID-003 driver to "sanity check" the supplied parameter. You can download the new firmware from: http://aesoffice.eu.com/HTTPSpace/Payli ... 15-526.zip or from http://aesoffice.eu.com/HTTPSpace/Payli ... -15.tar.gz if you need a Linux updater.

Once you have loaded the firmware from that, you should be able make progress on your application development.

Dave