Status of Removed iPro-RC Toggling Between Empty and Non-Functional

[paulp]

I am using Paylink 4.1.12.14 with a JCM iPro-RC. This device has a stacker and 2 x recycling channels RC1 and RC2.
When I pull out the stacker, I get reports that both RC1 and RC2 are non-functional. But then the next poll via ReadDispenserDetails() tells us they are both empty.

Each poll seems to cycle between status values of non-functional (-3) and empty (1).
I would really expect it to report non-functional and stay at that until the stacker is reinserted.

I have confirm this is happening, and excluding our code, by using the Demo.exe that came with the latest SDK. I can the status of these 2 devices toggling like I describe.

[aardvark]

Hi Paul,

I strongly suspect this is Paylink accurately reporting the information from the device.

Can you get a log from Paylink while it is doing this?

Thanks

Dave

[paulp]

I have come back to this today and the same fault (iPro stacker removed) and now I find it is toggling between "Non-Functional" and "Dispenser Count Updated" (pay status 111)

[paulp]

I can't see a way to attach files to posts, so I have emailed you a log file

FYI, we are polling using ReadDispenserDetails() to determine the dispenser status which I am seeing toggling

[davebush]

Hi Paul,

There is a bug in the ID003 recycler handling. The fragment of code was inserted in release 4.1.12.9 from 2018 and is intended to mark the recycler units as out of service whenever theres a major problem with the acceptor.

Unfortunately what it does is toggle between "out of service" and "result of last pay operation" every 150 milliseconds - as you've seen.

Although the fix is easy, the next release 4.1.12.15 is already happening so it won't make it into the main line code until 4.1.12.16

Dave

[paulp]

Hi Dave,
That's good to know that you have identified the causs and that the fix would be easy.

Unfortunately now we have added reporting of realtime information based on data we are receiving via the GBG MDC protocol, this is causing an excessive amount of false information.

Do you have any ideas on possible release of 4.1.12.16?
If 4.1.12.15 is still "happening" and the fix is easy, is there no chance you could squeeze it into that one?

Paul

[paulp]

For other interested readers, Dave kindly implemented his fix in 4.1.12.15 and provided a pre-release of this Paylink firmware, which did resolve the problem for me