??? 02/23/12 13:48 Read: times |
#186159 - Engine too fast Responding to: ???'s previous message |
Kai Klaas said:
A simple digital solution would measure the time between two succeeding edges of input clock and then output ten pulses in the next period of input clock. But if the input clock speeds up, there might not be enough time for all the ten pulses. A remedy could be to output the ten pulses in a period of time which is a bit shorter then the input clock period, to have some headroom for changes of input clock period.
The same happens when the input clock periode becomes wider. Then there are ten pulses at the beginning followed by a pause. Mahmood, can you experiment with such a tacho your customer has? Try to find out, how the tacho behaves with unsymmetrical pulse trains. Another methode is to estimate the trend of change of input clock periode by analyzing two succeeding periods of input clock. This methode is plausible if the diesel engine is big and rather slow-acting. Kai Klaas Good thinking Kai, the MCU method will not be simple, I will keep outputing the previos speed untill the new speed gets measured, then updates the output frequency accordingly so that I don't have blank periods in between speed change. However mechanical systems can never be as fast as electrical systems so the change of speed will always be slower than the multiplied output change. However I will have 180 degrees phase shift between the 2 frequencies which my client did accept. It turned out that the engine is for aeroplane and it goes up to 16,600 rpm. They want the change to be instant, they are capturing the speed to a Data Aquisition Card which accepts min of 15 Hz, while they want to monitor it from down to 1 Hz, thats why they want the multiplier 15x or 20x. Averaging will be done on PC. I will experiment with both solutions then report back. Mahmood |