Continue to Site

Welcome to our site!

Electro Tech is an online community (with over 170,000 members) who enjoy talking about and building electronic circuits, projects and gadgets. To participate you need to register. Registration is free. Click here to register now.

  • Welcome to our site! Electro Tech is an online community (with over 170,000 members) who enjoy talking about and building electronic circuits, projects and gadgets. To participate you need to register. Registration is free. Click here to register now.

A counter that starts and stops with a negative going pulse

PurnenduD

New Member
I am looking for suggestions to build a counter that will start with a negative going pulse and stop with the next negative going pulse. The interval is going to be between many seconds to many minutes. The interval is to be read out, arbitrary units fine, does not have to be seconds or minutes. It can then be manually reset to start anew.
Thank you
 
How many bits ? And clock rate (resolution, is it 1 sec resolution) ?

What is counter output used for, a display of the interval value ?

After counter completes does it stop until a trigger starts it again or does
it just run continuously ?

Generally speaking one does that with a reciprocal counter approach.

At the counting rate you suggest an 8 pin micro would do the job.
 
Last edited:
Here is basic micro coded using block language. mBlock takes your block configuration
and converts to Arduino code so you can program the micro.

1744065481591.png



Is your start and stop pulse on the same signal line or two separate inputs ? Is pulse input from
mechanical switch ? If so we would add blocks to debounce the switch.

Rough circuit -
1744066364843.png
 
Last edited:
How many bits ? And clock rate (resolution, is it 1 sec resolution) ? 1 s resolution is enough. !2 bits will give me 1 h+, thats enough

What is counter output used for, a display of the interval value ? Yes

After counter completes does it stop until a trigger starts it again or does
it just run continuously ? The next low going pulse should start it.

Generally speaking one does that with a reciprocal counter approach. Seems like getting 1/x is always a pain but I am a neophyte.

Let me state the actual problem. Am trying to make a polymer layer on the walls in side a 20 micrometer id capillary. The polymerization is photoinitiated. So we pump pneumatically the polymerization mixture through a tube coil while blasting it with 10 W 365 nm light. The difference between forming any layer on the wall and the capillary getting totally blocked is very small! But because at constant pressure the flow rate is inversely proportional to the fourth power of the diameter, the flow rate is very sensitive to the id ofthe tube and hence the polymer layerr thickness. We have flow meters that can work in this extremely small flow regime: nL/min to uL/min but polymer deposition in that flow meter is equivalent to throwing a $2K flowmeter into the toilet. So we are simply letting the solution drop out of the capillary exit and counting the time between the drops. This I am next going to do w a LED and a photodiode, as the drop falls through that light path, it will generate a momentary pulse. So we count time between the pulses. Soon as that time drops perceptibly, we will stop the 365 nm irradiation light and wash out the capillary with alcohol, which dissolves the unreacted mixture but not the polymer already formed on the wall.
So it is basically a long interval drop counter and I want to sense an increase in the interval. I wish I could think of an analog solution (as my electronics mostly belongs to that age!) but does not seem easy. Perhaps the drop pulse can be used to pulse an LED coupled to a PD and I integrate the current over time which spans at least two drops. But the needed integration time constantis likely to be too long to be practical.
 
You can do long integrations times with todays OpAmps and caps.
But board leakage, contamination, humidity, dust enemies but not
impossible to conquer. But digital approach mitigates all of that.

1/x trivial in todays coding tools, mBlock no exception.

The ATTINY85 or the Nano board can do I2C to an OLED or character display.

Key issue with 555 is accuracy over T and V due to electrolytic drift. Eg. timing accuracy
poor.

Block languages come in many flavors, here is example to do talking volt/freq/pulse
idth....meter. And this language has blocks for I2C and display

 
Last edited:

Latest threads

New Articles From Microcontroller Tips

Back
Top