how to get all (error) messages from between B2B banknote and paylink

[flyelephantw]

Hi Dave,

We also try "demo.exe" to observe the status when paper jammed.
However,it is strange, and we can't see the status to be updated.
The status stays "dumping".
We think this is not right, and it should return and update to error status.
Please kindly share your idea about this.

https://drive.google.com/file/d/1kWinWp ... sp=sharing

the below is showing "Unit Fault e4" in the log.
https://drive.google.com/file/d/1uegacH ... sp=sharing

You also can find the log file via the below link:
https://drive.google.com/file/d/1hG8hj_ ... sp=sharing

David

[davebush]

Hi,

The Paper Jammed" status is not shown against the dispenser. On Demo.exe, error reports such as this are reported in the "Event List" - you can see this outlined in the images here: https://d.pr/i/VNAWUP

The status of dumping remains because Paylink is waiting for the B2B to report that it is no longer dumping - the error status does not terminate the dump.

[davebush]

1/ The poll of NextEvent takes almost no time - only about 3 statements are executed, all just accessing shared memory. All Paylink interaction is designed in this same way. There is no other way to tell an event is waiting.

2/ If the acceptor as whole reports an error, that is not associated with the dispenser itself. The Payout terminates when the B2B sends a status of validly idle, until that point Paylink can't guarantee that the B2B will nor dispense any more bills.

3/ There is no problem, but you will be unable to tell what is happening as the events are discarded.

[flyelephantw]

hi Dave,

I thought Paylink should also feedback the real-time/ immediate error message via "LastPayStatus" after calling "Payout".
The current mechanism seems to take use of NextEvent, however NextEvent like a container to store all kinds of event message.
On the other hand, the feedback of error message to Payout status is more intuitive and effective way to control the process once exception occurs during payout, no matter what banknote validators is connected to Paylink.

Before you decide to implement the above method. If possible, please kindly share demo code to decipher CCNet error from "NextEvent". We can quickly proceed to done this by current method.

David

[davebush]

Hi David,

I have to admit the Paylink API is outdated, it was designed when the only payout was from coin hoppers. We may update at some future point, but for now we're stuck with it.

LastPayStatus is only updated at the end of Payout processing, and will notify you that that the payout failed at high, device independent level, most people do not need any more detail than this.

I cannot supply you with code to process the B2B events, as they depend on actually running a B2B. You should implement the demo code from before to output extensive diagnostic on each event read, recreate the problem on the B2B with that running and then use the output to create a function that selects those that are relevant to your problem.

Dave