Hi Chuck, had a look at your project. A neat idea. I assume the code refers to the spreadshet to select the correct data?
I did think about wi-fi onto the massive dev chart, (esp32 has wi-fi) so the user can import the development data, but then that becomes a faff, so might as well just use a laptop running a dev-timer app. All this takes one away from the idea of a dedicated timer.
I have the development timer sitting here, all working nicely. I'm just tinkering with it, changing things like 'Button 1' to say 'Yellow Button'
Nobody has asked for the code yet, so I'm assuming it will not be a popular project.
Parts list is already on Github & I have the schematic ready to upload.
I might do an enlarger timer next. The ones that work in stops are really expensive. Seem quite easy to input start time, e.g 4 seconds, then the timer will bang off 4 second exposures (or 2 second for half stops) to make a test strip. Then timer can work in stops (really good once one gets used to the idea) or old fashioned seconds. Output to a opto-coupled relay module to power the enlarger.
Easy, maybe 2 or more memory functions to toggle different settingsI have also been thinking about building an enlarging timer. In my case, I have these requirements:
- Two timer settings so I can set one for soft light exposure and the other for hard light for split vc printing.
Not sure what you mean here- 0-100% intensity adjust for each of the timers to handle dry down adjustment and other incremental tuning.
Yes, I agree. I use a rotary encoder, with acceleration, so easy to dial in big changes or small steps- Physical knobs to set time for each - I hate pushing buttons, it's slow and inefficient.
Yep, good old fashioned relay. Cheap opto-isolated modules available. These can be mounted in a separate unit, incorporating a socket for the enlarger & lead to plug into the mains- Relay based activation because cold light heads produce a real wallop of an inductive kick.
TFT screen has built in LED. Have never tried dimming it.- Ability to turn the display/LEDs waaaaaay down so they don't fog paper.
Easy, maybe 2 or more memory functions to toggle different settings
Not sure what you mean here
Yes, I agree. I use a rotary encoder, with acceleration, so easy to dial in big changes or small steps
Yep, good old fashioned relay. Cheap opto-isolated modules available. These can be mounted in a separate unit, incorporating a socket for the enlarger & lead to plug into the mains
TFT screen has built in LED. Have never tried dimming it.
Anyway, here is the link to my github for the film develop timer. Stlll early days, with just basic information there at the moment. I have not put the code there, as I am still tinkering with it, but if someone builds the hardware bofore the first release. I'm happy to send them the beta versions to play with.
GitHub - billbill100/Build-a-B-W-Film-Developer-Timer-Auto-Twiddler-Cheap-Easy-it-Works: Build a Black & White Film Developing Timer with optional motor driven twiddler for agitation
Build a Black & White Film Developing Timer with optional motor driven twiddler for agitation - billbill100/Build-a-B-W-Film-Developer-Timer-Auto-Twiddler-Cheap-Easy-it-Worksgithub.com
What language did you code this in?
I have also been thinking about building an enlarging timer. In my case, I have these requirements:
- Two timer settings so I can set one for soft light exposure and the other for hard light for split vc printing.
- 0-100% intensity adjust for each of the timers to handle dry down adjustment and other incremental tuning.
- Physical knobs to set time for each - I hate pushing buttons, it's slow and inefficient.
- Relay based activation because cold light heads produce a real wallop of an inductive kick.
- Ability to turn the display/LEDs waaaaaay down so they don't fog paper.
Did you include in your own experimentation the following experiment or equivalent:From my own experimentation, I have found twiddling every bit as good as inversion,
Be aware that even when the relay is OFF,there will be some AC on the output, flowing through the capacitor.Be sure to put an appropriate capacitor across the relay to absorb the inductive flyback.
So I reasoned, "gee, if I use a much larger capacitor for the snubber then lots more noise will be inhibited, right?" ... and yes, I was right ... but the large cap allowed for so much current to flow through the arrangement that the motor started spinning without the fets being active!
Mainly gibberish and C++)
When raw speed is needed, a bit of assembly.
I post the compiled Hex code, to flash directly to the processor.
As I use blocks of pre-written code (to save me having to write the same stuff over and over) and then call them as a library, it would end up too complex to publish the code directly.
I have the working code sitting here now, all working. Until somebody requests it, I will continue to a tinker and add functionality. It no auto-corrects input errors, so if the user dials down the dev time, for example, agitation time may longer than the dev time.
Also planning to add a memory function, so it remembers the settings at power off. Might also add multiple memories, so different setups can be saved & easily recalled.
Yeah, I use a Gra Lab timer. Or my wrist watch or my phone. Etc.
When I start loading developing the first thing is to leave my watch downstairs. Watches are dangerous things. Never happened to me but a friend was loading tanks with a watch…
Here is a photo of the (new) 3d printed Patterson Super 4 Tank Lid.
It incorporates mounting for the stepper motor & teeth on the underside, to engage with the serrations on the tank rim.
A new twiddling stick will be available soon (printing now) which will connect directly to the stepper motor drive shaft.
stl print files on Github & Instructables.
Without a 3d printer, it is quite simple to make something similar from a piece of ply or plastic.
View attachment 369231
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?