Why do you think we have a crystal ball to get the basic values?
Much simpler to tell us up front.
Do I correctly infer you have no idea of what the RPM is? It is really simple 8th grade math to figure out the time for one revolution.
If you have no idea of what the two values are it seems to me you have no idea of what your process is and you are nowhere near ready to even tinker with a PLC.
Dan Bentler
the time values between the pulses are necessary to calculate the diameter of the wheel angry guy. if you do not have any technical comment please do not pollute this thread.
and may be you should hang out with friends more to learn how to speak like other people.
Just wait, tny asked a valid question. He stated that he needed to measure short time periods rather accurately and implied that the scan time variance would not be fine enough resolution. Maybe guidance in the high speed capabilities (if any) of the system he mentions would be in order. A long term timing of multiple occurances seems to be ruled out by his question. Homework or not, it appears he has give some thought to the matter.
By the way, his previous posts seem to indicate other than 'homework'.
it's nice to see right-minded people here
What is the minimum time the sensor pulses will be on for ?
Which CPU will you be using ?
Do you have to worry about the case where the wheel is stopped and is just on the edge of the sensor resulting in counts due to vibration ?
Will you consider adding a counter card ?
the pulses are 50 msec long. (on time)
the cpu is cpu314.
the stopping point is not important. i think there will not be any vibration problem but anyway i used a positive edge trigger after the input on my program.
and sure if necessary i may add a counter card.
the siemens 314 cpu and has counter inputs but they are already used to get data from encoders.
today i tried a way to calculate the time values between pulses by using normal timers, with no any hw interrupt, high speed counter etc. i simulated the pulses (50 msec pulse on - 250 to 1450 msec off) and i saw that the code works on an empty plc with 1 msec cycle times.
but with the cycle times of 30-40 msec with all codes, the code calculates the times with 20-30 msec excess.
step7 is not installed on this pc so i can not copy the code here, i'm sorry. i will add tomorrow.
regards