Hello, im testing banknote acceptor JCM EBA 40 with escrow system but there is problem. There is an inconsistency between acceptor and paylink. When an acceptor rejects a banknote, it does not pass this information to the paylink that is waiting for the banknote to be stacked. The acceptor no longer receives any notes and cannot be turned on again. I attach the log. Please help.
So from the log, I assume we're talking about this point:
14:26:25.874 ccNote: Stack Escrow Note
At this point, Paylink has sent a command to the acceptor and is now waiting for anything at all to happen at the acceptor. All activity by an acceptor is reported to Paylink (and hence the application) as events in a message such as:
14:26:24.858 ccNote: New event 104, Old 103, note 5 in escrow
At present I regard this as proof that the acceptor is malfunctioning as it is not reporting anything (no New event messages are output). What happens if you actually try to do things to the acceptor? e.g. Remove the banknote, open the top etc., insert a new banknote, turn it off and on again?
If I remove the banknote nothing happens. When I read the acceptor status, it reports OK. It will only help end the original instance and start a new one. I attach a detailed log of the event.
Thanks for that. From the detail in the log I can see that the acceptor reports a banknote in escrow at 16:36:29.380, but at 16:36:30.146 it returns a "no note in escrow" error to the stack command!
I've updated the code to deal with this error code (as an Escrow note returned event) and this: https://d.pr/f/Sn0wY4 version implements the changes.
Please post a reply if this fixes your problem.
Regards
Dave
Aardvark software developer. Please put all communication on the problem through the board for the benefit of others.
Many thanks for the fix. Would it be possible to incorporate the modification into a stable version? I use an acceptor in production and if the problem goes away, it will run on another 15 machines.
This fix will be in the next full release, 4-1-12-10 - which is due this summer.
The change required here were very minor and are now permanent - in every release of Paylink from now on. Any release that ends 1-12-10 will have the fix in.
Aardvark software developer. Please put all communication on the problem through the board for the benefit of others.
Hi. The problem still persists.
I attach the log. After nine minutes, the unit was turned on again, so the machine had already recovered from the problem itself.
I'm not sure what you actually did here. Just looking at the log it appears that what actually made the acceptor start working again was disabling it and then enabling it again?
Can you try the test on that basis - as soon as the fault happens, disable and enable the acceptor?
Aardvark software developer. Please put all communication on the problem through the board for the benefit of others.
After a few seconds the problem occurs, so I turn the acceptor off(disable) and on(enable) again in the cycle. Only after nine minutes does the acceptor really turn on.
At 18:07:23.351 the Acceptor notifies Paylink that a Note into Escrow event has occurred. (sequence number 70)
At 18:07:24.039 Paylink issues a Stack command, and
at 18:07:24.054 the acceptor returns an error code 254 to that command, stating there is not a note in the acceptor escrow !!!
Paylink therefore notifies you of this by removing the "Note in escrow" condition.
At 18:17:03.581 the acceptor return the next event, sequence 71, which is note in escrow. During these 10 minutes, according to the acceptor, nothing interesting has happened!
Looking at this, between 18:07:23.351 and 18:07:24.039 the acceptor disabled itself and returned the note, without generating any event to mark this.
Ideally JCM would fix the firmware in their acceptor, but it looks as though you can do a "work around" in your code by disabling the acceptor if a note in escrow just disappears.
Aardvark software developer. Please put all communication on the problem through the board for the benefit of others.