Could u help me with MDB connecting of changer to paylink ? I have mei CF7000 via MDB. I connected the MDB cabel to Paylink ( MDB master) and the aes driver reports me these errors.
14:22:22.051 MDB: Device Status reply < 7 bytes
14:22:22.051 MDB: 0 > 09
14:22:22.051 MDB: 1064 > 09
14:22:22.051 MDB: 1064 > 09
14:22:22.051 MDB: 1925 C 30
14:22:22.051 MDB: Bad message read
14:22:22.131 MDB: Device Status reply < 7 bytes
14:22:22.930 MDB: Timeout (60) for MDB @ 8
14:22:22.994 MDB: Timeout (60) for MDB @ 8
14:22:23.042 MDB: Timeout (60) for MDB @ 8
14:22:23.123 MDB: 0 > 09
14:22:23.123 MDB: 730 > 09
14:22:23.123 MDB: 61 > 09
14:22:23.123 MDB: 61 > 09
14:22:23.123 MDB: Missing response from MDB @ 8
14:22:23.123 DP: Lost fault 000000e2
14:22:24.183 MDB: 0 > 09
14:22:24.183 MDB: 61 > 09
14:22:24.183 MDB: 61 > 09
14:22:24.183 MDB: 61 > 09
14:22:24.183 MDB: Missing response from MDB @ 8
14:22:25.246 MDB: 0 > 09
14:22:25.246 MDB: 61 > 09
14:22:25.246 MDB: 61 > 09
14:22:25.247 MDB: 1066 > 09
14:22:25.247 MDB: Missing response from MDB @ 8
14:22:26.308 MDB: 0 > 09
14:22:26.308 MDB: 61 > 09
14:22:26.308 MDB: 1066 > 09
14:22:26.308 MDB: 1066 > 09
14:22:26.308 MDB: Missing response from MDB @ 8
14:22:27.315 MDB: Device Status reply < 7 bytes
14:22:27.363 MDB: Timeout (60) for MDB @ 8
14:22:27.427 MDB: Timeout (60) for MDB @ 8
14:22:27.474 MDB: Device Status reply < 7 bytes
14:22:27.538 MDB: Timeout (60) for MDB @ 8
14:22:27.602 MDB: Timeout (60) for MDB @ 8
14:22:27.666 MDB: Device Status reply < 7 bytes
14:22:27.698 MDB: Timeout (60) for MDB @ 8
14:22:27.762 MDB: Timeout (60) for MDB @ 8
14:22:27.826 MDB: Timeout (60) for MDB @ 8
14:22:27.900 MDB: 0 > 09
14:22:27.900 MDB: 1 > 09
14:22:27.900 MDB: 61 > 09
14:22:27.900 MDB: 61 > 09
14:22:27.900 MDB: Missing response from MDB @ 8
14:22:27.900 DP: Lost fault 000000e2
14:22:28.962 MDB: 0 > 09
14:22:28.962 MDB: 61 > 09
14:22:28.962 MDB: 61 > 09
14:22:28.962 MDB: 61 > 09
14:22:28.962 MDB: Missing response from MDB @ 8
14:22:30.024 MDB: 0 > 09
14:22:30.024 MDB: 61 > 09
14:22:30.024 MDB: 61 > 09
14:22:30.024 MDB: 1066 > 09
14:22:30.024 MDB: Missing response from MDB @ 8
14:22:31.087 MDB: 0 > 09
14:22:31.087 MDB: 61 > 09
14:22:31.087 MDB: 1066 > 09
14:22:31.087 MDB: 1066 > 09
14:22:31.087 MDB: Missing response from MDB @ 8
14:22:32.150 MDB: 0 > 09
14:22:32.150 MDB: 1066 > 09
14:22:32.150 MDB: 1066 > 09
14:22:32.150 MDB: 1066 > 09
14:22:32.150 MDB: Missing response from MDB @ 8
14:22:32.805 MDB: Device Status reply < 7 bytes
14:22:32.991 MDB: 0 > 09
14:22:32.991 MDB: 1066 > 09
14:22:32.991 MDB: 1066 > 09
14:22:32.991 MDB: 1965 C 30
14:22:32.991 MDB: Bad message read
14:22:33.135 MDB: Device Status reply < 7 bytes
14:22:33.199 MDB: Timeout (51) for MDB @ 8
14:22:33.247 MDB: Timeout (60) for MDB @ 8
14:22:33.310 MDB: Timeout (60) for MDB @ 8
14:22:33.390 MDB: 0 > 09
14:22:33.390 MDB: 0 > 09
14:22:33.390 MDB: 53 > 09
14:22:33.390 MDB: 61 > 09
14:22:33.390 MDB: Missing response from MDB @ 8
14:22:33.390 DP: Lost fault 000000e2
14:22:34.451 MDB: 0 > 09
14:22:34.451 MDB: 53 > 09
14:22:34.451 MDB: 61 > 09
14:22:34.451 MDB: 61 > 09
14:22:34.451 MDB: Missing response from MDB @ 8
14:22:35.513 MDB: 0 > 09
14:22:35.514 MDB: 61 > 09
14:22:35.514 MDB: 61 > 09
14:22:35.514 MDB: 1066 > 09
14:22:35.514 MDB: Missing response from MDB @ 8
14:22:36.576 MDB: 0 > 09
14:22:36.576 MDB: 61 > 09
14:22:36.576 MDB: 1066 > 09
14:22:36.576 MDB: 1066 > 09
14:22:36.576 MDB: Missing response from MDB @ 8
14:22:37.639 MDB: 0 > 09
14:22:37.639 MDB: 1066 > 09
14:22:37.639 MDB: 1066 > 09
14:22:37.639 MDB: 1066 > 09
14:22:37.639 MDB: Missing response from MDB @ 8
14:22:38.310 MDB: Device Status reply < 7 bytes
14:22:38.487 MDB: 0 > 09
14:22:38.487 MDB: 1066 > 09
14:22:38.487 MDB: 1066 > 09
14:22:38.487 MDB: 1973 C 30
14:22:38.487 MDB: Bad message read
14:22:38.631 MDB: Device Status reply < 7 bytes
14:22:38.695 MDB: Timeout (60) for MDB @ 8
14:22:38.759 MDB: Timeout (60) for MDB @ 8
14:22:38.823 MDB: Timeout (60) for MDB @ 8
14:22:38.896 MDB: 0 > 09
14:22:38.896 MDB: 1 > 09
14:22:38.896 MDB: 61 > 09
14:22:38.896 MDB: 61 > 09
14:22:38.896 MDB: Missing response from MDB @ 8
Do you know, where might be a problem ?
Regards
Getting MDB Working
Moderators: aardvark, davebush, Admin
Re: Getting MDB Working
It sounds as though you've used the wrong MDB connection.
The connector labelled Master is to connect to an MDB master. To connect to a changer, you need the 3 pin which connects to an MDB Slave.
I think we should have labelled these the other way around!
Regards
Dave
The connector labelled Master is to connect to an MDB master. To connect to a changer, you need the 3 pin which connects to an MDB Slave.
I think we should have labelled these the other way around!
Regards
Dave
Aardvark software developer. Please put all communication on the problem through the board for the benefit of others.
Re: Getting MDB Working
Now i restarted Paylink.
Connect to MDB Slave:
16:50:24.823 PC: AESCDriver Driver restart (after crash)
16:50:26.827 PC: Driver restarting
16:50:26.832 FTDI Open : Genoa
16:50:26.832 FTDI VID PID : 0403 de50
16:50:26.832 FTDI chip type : 3
16:50:26.832 Timeout: read 5000, write 5000
16:50:26.882 DP: Application has gone away
16:50:26.882 MDB: Disable
16:50:26.882 DP: MDB Status to 45
16:50:26.882
16:50:26.962 Config: Start of download
16:50:26.962 Config: Checked, OK
16:50:26.962 Config: Paylink Checked OK against file "Standard.cfg"
16:50:26.980 PC: Memory Resynch - new protocol
16:50:27.284 DP: MDB acceptor 2090000 at ba0 setup
16:50:27.708 DPPC: Input Update @47c, 1=>0
16:50:27.708 PC: Input Update PayValue 0, Old 0
16:50:27.708 PC: Update @bac, 41=>45
16:50:27.708 PC: USB unit re-synch complete
16:50:27.708 : Interface memory set up
16:50:27.708 Exec: DP task took 683 msec
16:50:27.791
16:50:27.791 Ver 004.001.012.071-526 Oct 25 2016 11:13:54
16:50:27.791 DP: Application active
16:50:27.791 MDB: Enable
16:50:27.791 DP: MDB Status to 41
16:50:27.791 DP: Event 0002
16:50:27.791 DP: Turn off barcodes
16:50:30.699 00:02
I start App CoinRead.
but on change is still Check Vendor Comms error. I tried with/without 12V in paylink. Is it necassary 12V in MDB Comm ?
I have no idea, where might be a problem. Any idea ?
Connect to MDB Slave:
16:50:24.823 PC: AESCDriver Driver restart (after crash)
16:50:26.827 PC: Driver restarting
16:50:26.832 FTDI Open : Genoa
16:50:26.832 FTDI VID PID : 0403 de50
16:50:26.832 FTDI chip type : 3
16:50:26.832 Timeout: read 5000, write 5000
16:50:26.882 DP: Application has gone away
16:50:26.882 MDB: Disable
16:50:26.882 DP: MDB Status to 45
16:50:26.882
16:50:26.962 Config: Start of download
16:50:26.962 Config: Checked, OK
16:50:26.962 Config: Paylink Checked OK against file "Standard.cfg"
16:50:26.980 PC: Memory Resynch - new protocol
16:50:27.284 DP: MDB acceptor 2090000 at ba0 setup
16:50:27.708 DPPC: Input Update @47c, 1=>0
16:50:27.708 PC: Input Update PayValue 0, Old 0
16:50:27.708 PC: Update @bac, 41=>45
16:50:27.708 PC: USB unit re-synch complete
16:50:27.708 : Interface memory set up
16:50:27.708 Exec: DP task took 683 msec
16:50:27.791
16:50:27.791 Ver 004.001.012.071-526 Oct 25 2016 11:13:54
16:50:27.791 DP: Application active
16:50:27.791 MDB: Enable
16:50:27.791 DP: MDB Status to 41
16:50:27.791 DP: Event 0002
16:50:27.791 DP: Turn off barcodes
16:50:30.699 00:02
I start App CoinRead.
but on change is still Check Vendor Comms error. I tried with/without 12V in paylink. Is it necassary 12V in MDB Comm ?
I have no idea, where might be a problem. Any idea ?
Re: Getting MDB Working
The MDB connector from the Paylink does not carry power, it's just communications to and from the Paylink.
The CF7000 will require at least 24V and that has to be connected directly from the PSU to the CF7000. Don't forget to connect 0V as the PSU may be isolated.
The CF7000 will require at least 24V and that has to be connected directly from the PSU to the CF7000. Don't forget to connect 0V as the PSU may be isolated.
Aardvark software developer. Please put all communication on the problem through the board for the benefit of others.
Re: Getting MDB Working
I have connect changer to 30V.
Changer to paylink is connect via rx tx a communicate ground from mdb cabel.
Regards
Changer to paylink is connect via rx tx a communicate ground from mdb cabel.
Regards
Re: Getting MDB Working
I'm glad te hear it's all working.
Please open another thread if you get any other problem.
Regards
Dave
Please open another thread if you get any other problem.
Regards
Dave
Aardvark software developer. Please put all communication on the problem through the board for the benefit of others.
Re: Getting MDB Working
Hello,
Its not working.
I tried new PSU and still not work.
AESCDriver, [v4.1.12.12a], Oct 26 2020 10:42:32, Configuration file: Standard.cfg
29 October 2020 Linux Driver:4.1.12.12a
10:20:26.206 PC: AESCDriver Driver restart (after crash)
10:20:28.210 PC: Driver restarting
10:20:28.215 FTDI Open : Genoa
10:20:28.215 FTDI VID PID : 0403 de50
10:20:28.215 FTDI chip type : 3
10:20:28.215 Timeout: read 5000, write 5000
10:20:28.266 DP: Application has gone away
10:20:28.266 MDB: Disable
10:20:28.266 DP: MDB Status to 45
10:20:28.266
10:20:28.346 Config: Start of download
10:20:28.346 Config: Checked, OK
10:20:28.346 Config: Paylink Checked OK against file "Standard.cfg"
10:20:28.364 PC: Memory Resynch - new protocol
10:20:28.668 DP: MDB acceptor 2090000 at ba0 setup
10:20:29.090 DPPC: Input Update @47c, 1=>0
10:20:29.090 PC: Input Update PayValue 0, Old 0
10:20:29.090 PC: Update @bac, 41=>45
10:20:29.090 PC: USB unit re-synch complete
10:20:29.090 : Interface memory set up
10:20:29.090 Exec: DP task took 680 msec
10:20:29.174
10:20:29.174 Ver 004.001.012.071-526 Oct 25 2016 11:13:54
10:20:29.174 DP: Application active
10:20:29.174 MDB: Enable
10:20:29.174 DP: MDB Status to 41
10:20:29.174 DP: Event 0002
10:20:29.174 DP: Turn off barcodes
10:20:32.577 00:02
Its some way to debug, if the paylink try to communicate with changer ?
In this log its look like, that all is working, but not.
Regards
Jan
Its not working.
I tried new PSU and still not work.
AESCDriver, [v4.1.12.12a], Oct 26 2020 10:42:32, Configuration file: Standard.cfg
29 October 2020 Linux Driver:4.1.12.12a
10:20:26.206 PC: AESCDriver Driver restart (after crash)
10:20:28.210 PC: Driver restarting
10:20:28.215 FTDI Open : Genoa
10:20:28.215 FTDI VID PID : 0403 de50
10:20:28.215 FTDI chip type : 3
10:20:28.215 Timeout: read 5000, write 5000
10:20:28.266 DP: Application has gone away
10:20:28.266 MDB: Disable
10:20:28.266 DP: MDB Status to 45
10:20:28.266
10:20:28.346 Config: Start of download
10:20:28.346 Config: Checked, OK
10:20:28.346 Config: Paylink Checked OK against file "Standard.cfg"
10:20:28.364 PC: Memory Resynch - new protocol
10:20:28.668 DP: MDB acceptor 2090000 at ba0 setup
10:20:29.090 DPPC: Input Update @47c, 1=>0
10:20:29.090 PC: Input Update PayValue 0, Old 0
10:20:29.090 PC: Update @bac, 41=>45
10:20:29.090 PC: USB unit re-synch complete
10:20:29.090 : Interface memory set up
10:20:29.090 Exec: DP task took 680 msec
10:20:29.174
10:20:29.174 Ver 004.001.012.071-526 Oct 25 2016 11:13:54
10:20:29.174 DP: Application active
10:20:29.174 MDB: Enable
10:20:29.174 DP: MDB Status to 41
10:20:29.174 DP: Event 0002
10:20:29.174 DP: Turn off barcodes
10:20:32.577 00:02
Its some way to debug, if the paylink try to communicate with changer ?
In this log its look like, that all is working, but not.
Regards
Jan
Re: Getting MDB Working
Hi,
I suspect that there's no communication at all. If you look in here http://aardvark.eu.com/downloads/docume ... inkLog.pdf at stage 5, you can turn on the MDB diagnostics (d mdb)
I suspect you will see something like the image, crucially the character after the : will be > which shows an outgoing message, none will show a < which shows a reply.
If I'm correct, then it is purely a question of working out why the transmit and receive pins on the MDB are not connected correctly!
Regards
Dave
I suspect that there's no communication at all. If you look in here http://aardvark.eu.com/downloads/docume ... inkLog.pdf at stage 5, you can turn on the MDB diagnostics (d mdb)
I suspect you will see something like the image, crucially the character after the : will be > which shows an outgoing message, none will show a < which shows a reply.
If I'm correct, then it is purely a question of working out why the transmit and receive pins on the MDB are not connected correctly!
Regards
Dave
Aardvark software developer. Please put all communication on the problem through the board for the benefit of others.
Re: Getting MDB Working
Hello,
I have next knowledge about the issue.
If i connect changer directly via EXEC to VM, on Paylink i see some communication, so connection to paylink is fine.
But I want to connect charger wihout VM. Do I understand correctly that paylink should act as VM for changer. If the connection is in paylink to MDB slave ?
Regards
Jan
I have next knowledge about the issue.
If i connect changer directly via EXEC to VM, on Paylink i see some communication, so connection to paylink is fine.
But I want to connect charger wihout VM. Do I understand correctly that paylink should act as VM for changer. If the connection is in paylink to MDB slave ?
Regards
Jan
Re: Getting MDB Working
I got this log now:
13:53:03.206 Task: MDB, debug on
13:53:03.206 $ MDB: 1066: > [09] [09]
13:53:04.083 MDB: 0 > 09
13:53:04.083 MDB: 61 > 09
13:53:04.083 MDB: 61 > 09
13:53:04.083 MDB: 1066 > 09
13:53:04.083 MDB: Missing response from MDB @ 8
13:53:05.075 MDB: 1066: > [09] [09]
13:53:05.139 MDB: 0 > 09
13:53:05.139 MDB: 61 > 09
13:53:05.139 MDB: 1066 > 09
13:53:05.139 MDB: 1067 > 09
13:53:05.139 MDB: Missing response from MDB @ 8
13:53:05.586 9656 bytes memory free
13:53:06.130 MDB: 1060: > [09] [09]
13:53:06.205 MDB: 0 > 09
13:53:06.205 MDB: 1066 > 09
13:53:06.205 MDB: 1067 > 09
13:53:06.205 MDB: 1067 > 09
13:53:06.205 MDB: Missing response from MDB @ 8
13:53:06.724 MDB: 584: < {31}
13:53:06.724 MDB: Device Status reply < 7 bytes
i can see both side commucation. Its possible, that changer is bad set up ?
13:53:03.206 Task: MDB, debug on
13:53:03.206 $ MDB: 1066: > [09] [09]
13:53:04.083 MDB: 0 > 09
13:53:04.083 MDB: 61 > 09
13:53:04.083 MDB: 61 > 09
13:53:04.083 MDB: 1066 > 09
13:53:04.083 MDB: Missing response from MDB @ 8
13:53:05.075 MDB: 1066: > [09] [09]
13:53:05.139 MDB: 0 > 09
13:53:05.139 MDB: 61 > 09
13:53:05.139 MDB: 1066 > 09
13:53:05.139 MDB: 1067 > 09
13:53:05.139 MDB: Missing response from MDB @ 8
13:53:05.586 9656 bytes memory free
13:53:06.130 MDB: 1060: > [09] [09]
13:53:06.205 MDB: 0 > 09
13:53:06.205 MDB: 1066 > 09
13:53:06.205 MDB: 1067 > 09
13:53:06.205 MDB: 1067 > 09
13:53:06.205 MDB: Missing response from MDB @ 8
13:53:06.724 MDB: 584: < {31}
13:53:06.724 MDB: Device Status reply < 7 bytes
i can see both side commucation. Its possible, that changer is bad set up ?
Re: Getting MDB Working
Hello,
i changed the paylink and its all working. Paylink, which i have, has broken MDB interface.
Thank u for your patience
Regards
i changed the paylink and its all working. Paylink, which i have, has broken MDB interface.
Thank u for your patience
Regards
Re: Getting MDB Working
That's good news.
It's possible that you broke something when you used the wrong plug. I'll remember that if anyone else has problems with MDB.
Regards
Dave
It's possible that you broke something when you used the wrong plug. I'll remember that if anyone else has problems with MDB.
Regards
Dave
Aardvark software developer. Please put all communication on the problem through the board for the benefit of others.