Aardvark Embedded Solutions Ltd Support Forum

Hi, I'm sorry but I've not got anything to add. I would have suggested that the address may wrong, but you say it did respond once, so it's not going to be that. Given the tests you've done with a scope, it just looks to me like the MDB circuity on the Paytec is faulty. Sorry i can't be more help. R...

Hi,

I can't see any way that this could be software in the Paylink, and you already have the Paylink MDB hardware working with your other connections.

The only two things i can think of are problems the 24/36 V power to the Paytec, or the Paytec itself is faulty.

Sorry not to be more help,

Dave

Hi, Paylink can only go off what is reported by the changer. If the the changer doesn't send the information you want, then there is no way for Paylink to do anything about this. The MDB specification allows the changer to say whether a coin was routed to the cash box or to the tube. The Paylink han...

Hi,

To handle an MDB Bill peripheral, you need: Paylink discovers that it is a recycler and sets everything up accordingly, without anything in the config.

Note that you do need a recent release.

Dave

Hi, Nothing in the API was specifically designed to be thread safe. That said, all the API calls that are essentially reading values from the Paylink are safe. However those issuing commands or modifying peripheral behaviour are theoretically capable of triggering the Paylink unit into action part w...

Pleased to help.

Dave.

Hi, There is a fault in your hopper's firmware - you need to talk to the manufacturer / distributor. To explain: There are two principal ways of sending a pay request to a hopper, "Encrypted" and "Serial Number". From it's declared name it appears your hopper uses the "Seria...

Hi,

It's not obvious what can be wrong. You can get further diagnostics out of the system by following this guide: http://www.aesoffice.eu.com/HTTPSpace/P ... %20Log.pdf and send me the results.

Dave

I'm sorry, but we are only concerned with the firmware.

Everything about the hardware is handled by Crane PI. I'm pretty sure they won't send you anything, but you can always try asking your distributor / supplier.

Dave

I'm sorry but there's nothing in your post that appears to correspond to any particular fault. It doesn't look like software / firmware to me so I suspect there is a hardware fault, although it doesn't line up with any of the common ones. The best idea is probably to try a different unit, if that wo...

Hi, Are you using an acceptor or a note recycler? (You have specified a note recycler in the configuration file) For any model of acceptor you just need: Note Acceptor at 40 [CRC BNV 846627] This gives a standard acceptor. You can add the CRC and/or BNV nnnnnn options to match the device. If you are...

Hi, In general for RS232 you are better off using native Windows / Linux communications device handlers with a standard RS232 device. If you still think that this is the best way to go, Paylink does have a special purpose RawPort interface for low level access to the Paylink ports - it was intended ...

Hi Nathan, After some research, it appears that the driver we supply is not compatible with having Core Isolation Memory Integrity turned on. (This is apparently the default with new Windows 11 installations) The simple solution is to turn off Memory Integrity: It's a bit long winded, but if you run...

Hi, There is a problem to do with users, which I think is related to IIS. (It may be only on 64 bit) With IIS the application is not running as the normal user, while the driver program is. As these are running as different users, that means that shared memory has to be in the "global segment&q...

Hi Nathan, The Paylink driver and the DLL communicate using a shared memory segment, and error 31 means that for some reason the DLL is unable to open the segment correctly. This can be due to access permissions if you are running the application in an unusual way. Can you think of any way the faili...