Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Impulses of fast insertion of coins are accumulated #45

Open
21it opened this issue Aug 18, 2021 · 6 comments
Open

Impulses of fast insertion of coins are accumulated #45

21it opened this issue Aug 18, 2021 · 6 comments

Comments

@21it
Copy link

21it commented Aug 18, 2021

Seems like if I'm able to insert coins fast enough in sequence, impulses for coins are accumulating. For example let's say I do have 3 similar coins, which are mapped to impulse number 2 on coins acceptor. I do insert them very fast in sequence. Then ATM will detect 3 coins corresponding to impulses 2, 4 and 6.

@lightisfaster
Copy link
Collaborator

Thanks for create this issue. Unfortunately we haven't found a solution for this yet. Maybe someone has an idea?

@AxelHamburch
Copy link
Contributor

I was able to reproduce the problem. I have a possible solution that requires a small relay, since the coin validator does not have a inhibit input. Whenever coins were inserted, I would deactivate the release coil for the passage of the coins, so that the coins that are thrown in immediately after being thrown in are ejected again. I need a place in the program where we can set an output that will switch a relay for a certain amount of time or until we can say for sure it's safe to add the second coin now. But I'm still at the beginning and the hardware ist just arrived. I will give an update as soon as I know more.

@AxelHamburch
Copy link
Contributor

This issue will be solved with the PR #64
#64
See details here:
https://github.com/AxelHamburch/LightningATM/blob/update_gpio/docs/guide/relay.md

@AxelHamburch
Copy link
Contributor

It's no in the current version. Use the ralay an the the problem is solved.
@lightisfaster can we close this topic?

@danielcharrua
Copy link
Contributor

@lightisfaster @AxelHamburch I think this issue is solved and can be closed.

@AxelHamburch
Copy link
Contributor

@lightisfaster
Pls close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants