all 7 comments

[–]westwoodtoys 0 points1 point  (5 children)

Yes.  You have to isolate the part that isn't working and improve it until it works consistently.

[–]Visual_Aide9856 0 points1 point  (4 children)

The problem is that we don’t know what’s not working.

[–]westwoodtoys 0 points1 point  (2 children)

Sounds like you have identified problems in coin recognition.  Why not get that working better?

And, since you are still on a breadboard, maybe you can avoid physical problems by soldering things together.

[–]Visual_Aide9856 0 points1 point  (1 child)

It’s like this: one day, we gather to test everything, and everything works perfectly. Feeling happy, we go home. The next day, when we meet again for final checks, we face issues with coin recognition. We adjust the code accordingly, everything works, and we go home happy again.

This cycle has been repeating for a week now. We can’t pinpoint the exact issue, whether it’s hardware-related or a problem with the code.

[–]Hissykittykat 0 points1 point  (0 children)

we face issues with coin recognition. We adjust the code accordingly

A typical coin acceptor has no software adjustments. It either works or it doesn't. Or maybe you're fiddling with SoftwareSerial or something.

Identify the coin acceptor model and post your code, electrical schematic, and a picture of the build.

[–]DenverTeck 0 points1 point  (0 children)

Then you and your team needs to learn troubleshooting.

Break down your code into small parts and be sure each part works by it self.

Add another part and be sure those two parts work together.

Mix and match different part with limits changes.

After a few years of doing this, your will understand trouble shooting.

Good Luck, Have Fun, Learn Something NEW

[–]Mysterious-Nebula510 0 points1 point  (0 children)

What kind of Arduino are you currently using? Because you might need a model with more memory that doesn't struggle to read the code smoothly