Several coins in TAcceptorBlock structure

[andreIsGold]

Hello Dave,

I'm sending you an image where you can see my problem.

When I call to the ReadAcceptorDetails function, it returns via parameter the data that you can see in the image.
Below, I write a piece of MilanDiag diagnostic that shows something similar than the image.

{ Acceptor 0: MCL SR5, Default Path 5,
Event count 0, Currency <MX>, 16 coins:
Coin 0, Value 5,
Coin 1, Value 10,
Coin 2, Value 20,
Coin 3, Value 50,
Coin 4, Value 100,
Coin 5, Value 200,
Coin 6, Value 500,
Coin 7, Value 1000,
Coin 8, Value 1000,
Coin 9, Value 2000,
Coin 10, Value 2000

Acceptor 1: ccTalk Note, Default Path 0,
Event count 0, Currency <MX>, 16 coins:
Coin 0, Value 2000,
Coin 1, Value 2000,
Coin 2, Value 2000,
Coin 3, Value 5000,
Coin 4, Value 5000,
Coin 5, Value 5000,
Coin 6, Value 10000,
Coin 7, Value 10000,
Coin 8, Value 10000,
Coin 9, Value 20000,
Coin 10, Value 20000,
Coin 11, Value 50000,
Coin 12, Value 50000,
Coin 13, Value 100000 }

Well, I know in Mexico (our Client) there are different types of one note (for instance, there are three types of $20 notes, two types of $200 notes).

What I want is, when I call to ReadAcceptorDetails function, I need to receive the same list but without repeated values. I want this:

{ Acceptor 0: MCL SR5, Default Path 5,
Event count 0, Currency <MX>, 16 coins:
Coin 0, Value 5,
Coin 1, Value 10,
Coin 2, Value 20,
Coin 3, Value 50,
Coin 4, Value 100,
Coin 5, Value 200,
Coin 6, Value 500,
Coin 7, Value 1000,
Coin 8, Value 2000

Acceptor 1: ccTalk Note, Default Path 0,
Event count 0, Currency <MX>, 16 coins:
Coin 0, Value 2000,
Coin 1, Value 5000,
Coin 2, Value 10000,
Coin 3, Value 20000,
Coin 4, Value 50000,
Coin 5, Value 100000 }

That should solve my problem. Obviously, the acceptors should accept all the legal tenders. That is, all the different types of notes and coins in Mexico.

I hope you understand my problem so you can give me a solution...

Sorry about my poor english...

Thank you very much in advance!

Best Regards

[davebush]

I understand what you're after, but I'm afraid there are no facilities in Paylink itself to achieve what you're after. the reason the manufactures of acceptors set these up as different coins with the same value is because, under some circumstances, it may be desirable to disable one but not the others ( - things like obsolete coins being withdrawn.) Paylink therefore exposes these different coins to give you the chance to disable one but not the others.

I'm afraid you're just going to have to either adapt your application to handle the different coins, or get the acceptor manufacturers to give you different firmware.