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

Did you consider writing an EEPROM emulator? #3

Open
daantimmer opened this issue Apr 30, 2021 · 4 comments
Open

Did you consider writing an EEPROM emulator? #3

daantimmer opened this issue Apr 30, 2021 · 4 comments

Comments

@daantimmer
Copy link

Instead of creating a PCB to reset the EEPROM have you considered using a very small MCU which emulates the EEPROM read/writes while basically always returning the maximum number? That would reduce the number of connector inserts/removals by 50% because those PCB connectors aren't too wear resistant.

@dekuNukem
Copy link
Owner

That would be a good idea, and not too difficult. However, it would involve destructively modifying the cassette, and the cassette still needs to be removed for refilling anyway.

One option is to design such a board, and use an external tank like those continuous inkjet printer modifications, but it would require a lot of work :)

@ncw
Copy link

ncw commented May 2, 2021

Or maybe modify the board so it enables write protect on the EEPROM?

@jangrewe
Copy link

The one big reason why i would not use any read-only/autoreset feature: you wouldn't know when to refill the casette. I think the current solution is actually the best way.

@dekuNukem
Copy link
Owner

Or maybe modify the board so it enables write protect on the EEPROM?

Well, if you do want to enable Write Protect on the EEPROM, I have tested it out and written a guide about it:

https://github.com/dekuNukem/bob_cassette_rewinder/blob/master/user_manual.md#can-i-enable-write-protect-wp-to-lock-out-wash-count

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