Rejected notes

[quip3]

I’m having issues with multiple rejected notes but need some more details on why they are being rejected.

The paylink log file shows status and event codes, is there somewhere that explains what these mean? In particular ‘Note Status 20’ and ‘Event 000102’

11:43:39.652 16:15
11:43:46.903 DP: ID-003 Note Status to 20
11:43:52.939 ID-003: Note rejected
11:43:52.962 DP: ID-003 Note Status to 0
11:43:52.962 DP: Event 000102 for Acceptor 0
11:43:54.311 DP: ID-003 Note Status to 20
11:43:57.087 ID-003: Note rejected
11:43:57.087 DP: ID-003 Note Status to 0
11:43:57.087 DP: Event 000102 for Acceptor 0
11:43:58.439 DP: ID-003 Note Status to 20
11:44:02.234 ID-003: Note rejected
11:44:02.234 DP: ID-003 Note Status to 0
11:44:02.234 DP: Event 000102 for Acceptor 0
11:44:04.637 DP: ID-003 Note Status to 20
11:44:07.364 ID-003: Note rejected
11:44:07.364 DP: ID-003 Note Status to 0
11:44:07.364 DP: Event 000102 for Acceptor 0
11:44:07.664 DP: ID-003 Note Status to 20

Thanks

[davebush]

Hi,

You are running a relatively old version of Paylink, which doesn't include the JCM / ID003 error code in its reporting. If you load the latest firmware http://aardvark.eu.com/downloads/softwa ... -12-15.zip this includes the error byte in the rejected message, which should be one of these:

71H Insertion error
72H Magnetic pattern error
73H Return action due to residual bills, etc. (at the head part of ACCEPTOR)
74H Calibration error/ Magnification error
75H Conveying error
76H Discrimination error for bill denomination
77H Photo pattern error (1)
78H Photo level error
79H Return by INHIBIT: Error of insertion direction / Error of bill denomination
7BH Operation error
7CH Return action due to residual bills, etc. (at the stacker)
7DH Length error
7EH Photo pattern error (2)
7FH True bill feature error

To answer your other questions:

The Status reported is the Status field in the AcceptorBlock structure

The API Event is an encoded version of the data returned by the NextEvent call. The LS 16 bits are the event code, bits 17-24 are the raw error byte and the top 8 bits are an index to the unit causing the event.

Regards

Dave

[quip3]

Hi Dave,

Is there any way to get further information for the version that we're currently running? We're stuck on this firmware version at the moment so upgrading isn't an option.

Is there any sort of documentation that might explain what the status 20 is for this version?

Also is it possible to speculate if the issues are related to reading the notes/tickets or some kind of hardware issue like with the sensor?

Thanks

[davebush]

Hi,

Status 20 is just ACCEPTOR_BUSY - you get it whenever the acceptor does anything.

I'm sorry, but I have no idea what common reject reasons are - JCM might be able to help! (Or could you check CCT recordings?)

Regards

Dave

[quip3]

Thanks for your help Dave,

Just one other question, what version of the firmware was the error byte in the rejected message added? Can you confirm if it's in firmware version 4.1.12.6 as we'll be using that on some of our units?

Thanks

[davebush]

Sorry, but I'm afraid the diagnostic is only present in 4.1.12.8 onward.

I understand the principle of "if it isn't broke don't fix it" but in general later releases are a good idea.

Regards

Dave