Paylink working with libusb-1.0.25 ?OS linux 64bits

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
aurelien
Posts: 9
Joined: Tue Mar 23, 2021 4:13 pm

Paylink working with libusb-1.0.25 ?OS linux 64bits

Post by aurelien »

Hello

I am testing Paylink with OS linux 64bits kernel 4.19.204

Paylink with FW version 4.1.12.14
Paylink linux driver 4.1.12.12
Changer CPI Gryphon MDB FW 1.6.0


Sometimes the Gryphon MDB put the coin into the cashbox instead of the tube. The tube is not full
what can cause this issue ?

is AESdriver work with libusb-1.0.25 ?

Code: Select all

file /usr/bin/AESCDriver
/usr/bin/AESCDriver: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 4.19.0, stripped
Paylink log:

Code: Select all

15 November 2023 Linux Driver:4.1.12.12a
15:27:42.560 PC: AESCDriver Driver startup
15:27:42.577 PC: Driver start up
15:27:42.580 FTDI Open        : Genoa
15:27:42.580 FTDI VID PID     : 0403 de50
15:27:42.580 FTDI chip type   : 3
15:27:42.580 Timeout: read 5000, write 5000
15:27:42.706 Config: Start of download
15:27:42.706 Config: Checked, OK
15:27:42.706 Config: Paylink Checked OK against file "/etc/AES/Standard.cfg"
15:27:42.727 PC: Memory Reset - new protocol
15:27:43.035 API: MDB acceptor 2080000 at ba0 and 5 coins setup
15:27:43.351 API: Level 2 Tube Hopper S/N 2810, Address 13, Value 200 at d34 setup
15:27:43.454 API: Level 2 Tube Hopper S/N 2810, Address 12, Value 100 at d80 setup
15:27:43.559 API: Level 2 Tube Hopper S/N 2810, Address 11, Value 50 at dcc setup
15:27:43.663 API: Level 2 Tube Hopper S/N 2810, Address 10, Value 20 at e18 setup
15:27:43.771 API: Level 2 Tube Hopper S/N 2810, Address 9, Value 10 at e64 setup
15:27:43.936 API: Level 3 Payout System Hopper S/N 2810, Address 8, Value 10 at eb0 setup
15:27:44.375 APIPC: USB unit reset complete
15:27:44.375 : Interface memory set up
15:27:44.375 Exec: API task took 1609 msec
15:27:57.328 04:26
15:28:08.749 
15:28:08.749 Ver 004.001.012.014-526 Sep  7 2022 12:08:04
15:28:08.749 DP: Application active
15:28:08.749 Int: 00 03 5a 76 de bf 63 dc 38 13 40 f1 17 67 f3 ee 94 90 22 64 d5 6f 75 f3 40 09 40 51 bc 1d 2a 17
15:28:08.749 API: Payout recovery
15:28:08.749 MDB: Enable
15:28:08.749 API: MDB Status to 0
15:28:08.749 MDB: inhibits to 001f
15:28:08.749 API: Event 0003
15:28:08.749 API: Turn off barcodes
15:28:08.749 MDB: Disable
15:28:08.749 API: MDB Status to 4
15:28:08.749 MDB: Inhibit all
15:28:09.147 API: Event 0001
15:28:09.385 API: Event 0002
15:28:57.132 04:27
15:29:56.956 04:28
15:30:56.764 04:29
15:31:56.571 04:30
15:32:56.379 04:31
15:33:56.041 04:32
15:34:55.808 04:33
15:35:55.607 04:34
15:36:55.388 04:35
15:37:55.171 04:36
15:38:54.953 04:37
15:39:54.735 04:38
15:40:42.463 MDB: Selftest OK
15:40:42.464 API: Event 0000e0 for Acceptor 0
15:40:54.535 04:39
15:41:54.318 04:40
15:42:54.101 04:41
15:43:53.884 04:42
15:44:53.666 04:43
15:45:53.464 04:44
15:46:53.246 04:45
15:47:53.028 04:46
15:48:52.810 04:47
15:49:52.592 04:48
15:50:52.390 04:49
15:51:52.173 04:50
15:52:51.955 04:51
15:53:51.738 04:52
15:54:51.536 04:53
15:55:51.322 04:54
15:56:51.120 04:55
15:57:50.915 04:56
15:58:50.707 04:57
15:59:50.515 04:58
15 November 2023 Linux Driver:4.1.12.12a
16:00:50.304 04:59
16:01:19.926 MDB: Enable
16:01:19.926 API: MDB Status to 0
16:01:19.926 MDB: inhibits to 001f
16:01:27.492 MDB: Read coin 3 to tube 3 - 18 in tube
16:01:27.492 API:     Coin 3: saved
16:01:28.925 MDB: Read coin 3 to tube 3 - 19 in tube
16:01:28.925 API:     Coin 3: saved
16:01:29.890 MDB: Read coin 3 to tube 3 - 20 in tube
16:01:29.890 API:     Coin 3: saved
16:01:31.132 MDB: Read coin 3 to tube 3 - 21 in tube
16:01:31.132 API:     Coin 3: saved
16:01:31.264 MDB: Disable
16:01:31.264 API: MDB Status to 4
16:01:31.264 MDB: Inhibit all
16:01:50.087 05:00
16:02:49.891 05:01
16:03:49.678 05:02
16:04:49.465 05:03
16:05:49.253 05:04
16:06:49.057 05:05
16:07:48.844 05:06
16:08:29.185 MDB: Selftest OK
16:08:29.185 API: Event 0000e0 for Acceptor 0
16:08:45.928 MDB: Enable
16:08:45.928 API: MDB Status to 0
16:08:45.928 MDB: inhibits to 001f
16:08:48.638 05:07
16:08:51.781 MDB: Read coin 3 to tube 3 - 22 in tube
16:08:51.781 API:     Coin 3: saved
16:08:53.817 MDB: Read coin 4 to tube 4 - 9 in tube
16:08:53.817 API:     Coin 4: saved
16:08:54.014 MDB: Disable
16:08:54.014 API: MDB Status to 4
16:08:54.014 MDB: Inhibit all
16:09:48.431 05:08
16:10:31.308 MDB: Enable
16:10:31.308 API: MDB Status to 0
16:10:31.308 MDB: inhibits to 001f
16:10:36.887 MDB: Read coin 3 to tube 3 - 23 in tube
16:10:36.887 API:     Coin 3: saved
[b][u]16:10:37.572 MDB: Read coin 5 to cashbox[/u][/b]
16:10:37.687 MDB: Disable
16:10:37.687 API: MDB Status to 4
16:10:37.687 MDB: Inhibit all
16:10:48.220 05:09
16:11:48.005 05:10
16:12:47.790 05:11
16:13:47.591 05:12
16:14:47.375 05:13
16:15:47.153 05:14
16:16:46.949 05:15
16:17:46.729 05:16
Best regards
davebush
Posts: 482
Joined: Fri Oct 22, 2004 12:20 pm

Re: Paylink working with libusb-1.0.25 ?OS linux 64bits

Post by davebush »

Hi,

With MDB changers Paylink has no control over the routing of coins; it is entirely down to the changer itself. You will have to take this up with CPI or your supplier.

Sorry

Dave
Aardvark software developer. Please put all communication on the problem through the board for the benefit of others.
aurelien
Posts: 9
Joined: Tue Mar 23, 2021 4:13 pm

Re: Paylink working with libusb-1.0.25 ?OS linux 64bits

Post by aurelien »

Thank you Dave for the Gryphon,

Did you test AESDRIVE with libusb-1.0.25 with OS linux 64bits
davebush
Posts: 482
Joined: Fri Oct 22, 2004 12:20 pm

Re: Paylink working with libusb-1.0.25 ?OS linux 64bits

Post by davebush »

Hi,

I've not specifically tried Paylink with libusb-1.0.25, but the Paylink system uses very basic facilitites. If AESCDriver initialises correclty then you can be reasonably certain that you won't get problems while it is running.

If you do get any problems, come back to me with the details of the problem and I'll check it out.

Regards

Dave
Aardvark software developer. Please put all communication on the problem through the board for the benefit of others.
Post Reply