Hi,
I'm using a Crane SCR recycler - how do I detect that the cashbox has been removed - I can't find a reference in the documentation.
Nathan
Detecting Cashbox Removed
Moderators: aardvark, davebush, Admin
Re: Detecting Cashbox Removed
Hi,
All information that is not about actual money acceptance is reported though the NextEvent() interface. For full details you should check page 69 of the applications manual and ImheiEvent.h.
Any problem involving a note accetpor / recycler cashbox will be flagged as an event type IMHEI_NOTE_STACKER_PROBLEM when it occurs and IMHEI_NOTE_STACKER_FIXED when it clears.
Also the exact event from the Acceptor will be reported in the RawEvent field. You will be able to see this is the field across the centre of the Demo program.
The RawEvent field will contain the exact problem / event that was reported by the acceptor, Appendix 1 of the API docuementation should detail these, but unfortunately the EBDS RawEvent codes have not yet made it into Appendix 1.
For EBDS it will be a bit number matching one of the error bits in the reply - this is the complete list:
Regards
Dave
All information that is not about actual money acceptance is reported though the NextEvent() interface. For full details you should check page 69 of the applications manual and ImheiEvent.h.
Any problem involving a note accetpor / recycler cashbox will be flagged as an event type IMHEI_NOTE_STACKER_PROBLEM when it occurs and IMHEI_NOTE_STACKER_FIXED when it clears.
Also the exact event from the Acceptor will be reported in the RawEvent field. You will be able to see this is the field across the centre of the Demo program.
The RawEvent field will contain the exact problem / event that was reported by the acceptor, Appendix 1 of the API docuementation should detail these, but unfortunately the EBDS RawEvent codes have not yet made it into Appendix 1.
For EBDS it will be a bit number matching one of the error bits in the reply - this is the complete list:
Code: Select all
EBDS_CHEATED = 0, // The device has detected conditions consistent with an attempt to fraud the system.
EBDS_REJECTED = 1, // The document presented to the device could not be validated and was returned to the customer.
EBDS_JAMMED = 2, // The path is blocked and the device has been unable to resolve the issue. Intervention is required.
EBDS_STACKER_FULL = 3, // The cash box is full of documents and no more may be accepted. The device will be out of service until the issue is corrected.
EBDS_CASSETTE_MISSING = 4, // The cash box has been removed. No documents may be accepted. The device is out of service until the issue is corrected.
EBDS_PAUSED = 5, // The customer is attempting to feed another note while the previous note is still being processed. The customer must remove the note to permit processing to continue.
EBDS_CALIBRATING = 6,
// Data Byte 2
EBDS_POWER_UP = 0+8, // The device has been powered up. It is performing its initialization routine and not yet ready to accept documents.
EBDS_INVALID_COMMAND = 1+8, // The device received an invalid command.
EBDS_FAILURE = 2+8, // The device has encountered a problem and is out of service. Intervention is required.
EBDS_TRANSPORT_OPEN = 6+8 // Note path access is opened (vault, door, or both).
Dave
Aardvark software developer. Please put all communication on the problem through the board for the benefit of others.