Problems issuing Extended Escrow commands

[Nathan]

Can you help.

The Extended Escrow part of Paylink is working strangely.

- At 11:48:54 we have started the acceptance. Escrow status is EXT_ESCROW_WAITING
- at time 11:49:06.1228 we detected the inserted note using EscrowThroughput.
- At time 11:49:06.1288 we call EscrowCommand [EXT_ESCROW_PAUSE].
- At time 11:49:07.3896, after about 1 second we repeat the call, the escrow state is still EXT_ESCROW_WAITING. This is repeated 3 more times. The status does not change.

We are unable to process this correctly.

Can I go over the correct processing procedure with you?
1. We enable the acceptor ( acceptor.Status &= ~Paylink.AcceptorStatus.Inhibit; ) and WriteAcceptorDetail
2. AESImhei.EnableInterface() command;
3. AESImhei.EscrowCommand( EXT_ESCROW_START)
4. AESImhei.EscrowCommand( EXT_ESCROW_ACCEPT)

Now the acceptor is started and is in bill acceptance mode. After inserting a banknote ( we want to accept the banknote and store it in the reccylator):
5. AESImhei.EscrowCommand( EXT_ESCROW_PAUSE)
6. AESImhei.EscrowCommand( EXT_ESCROW_STACK)

Our log for this shows:

Code: Select all

2022-02-14 07:47:35.3345 | DEBUG | Paylink Driver | EscrowCommand [0, EXT_ESCROW_ACCEPT] 
2022-02-14 07:47:44.5633 | TRACE |            Paylink Driver | Read Event [device: Banknote acceptor]: EventCode: '0', RawEvent: '0', IsDispenser: '0', Source 'Banknote acceptor'=>'0x258' 
2022-02-14 07:47:51.1401 | DEBUG | Paylink Driver | EscrowCommand [1, EXT_ESCROW_PAUSE] 
2022-02-14 07:47:52.2080 | DEBUG | Paylink Driver | EscrowCommand [2, EXT_ESCROW_PAUSE] 
2022-02-14 07:47:53.2203 | DEBUG | Paylink Driver | EscrowCommand [3, EXT_ESCROW_PAUSE] 
2022-02-14 07:47:54.2328 | DEBUG | Paylink Driver | EscrowCommand [4, EXT_ESCROW_PAUSE] 
2022-02-14 07:47:55.2458 | DEBUG | Paylink Driver | EscrowCommand [5, EXT_ESCROW_PAUSE] 

[davebush]

Hi,

I might have found the problem.

Looking at your log, I think the manual has confused you. The 1st parameter to EscrowCommand is "Number". This is not the sequence number of your commands, it specifies which one of the extended escrow recyclers you are talking to.

In your system this will always be zero, as you only have the single acceptor.

In the API design you could have multiple extended escrow acceptors and this would then specify which one of them is to receive the command.

Regards

Dave

[Nathan]

Hi,

Thank you - yes that was the problem.

Nathan