Engineering Question about vehicle tachometer circuitry

  • Thread starter Thread starter berdan
  • Start date Start date
  • Tags Tags
    Circuitry Vehicle
Click For Summary
SUMMARY

The discussion centers on designing a tachometer circuit for a racing car using a motorcycle engine's ECU output. The ECU provides a square wave signal with a 30% duty cycle, where each pulse corresponds to one engine revolution. The team aims to create a circuit that utilizes 9 LEDs to display RPM ranges, specifically from 1200 RPM to 12000 RPM. The final decision was to implement the tachometer using an Arduino, which allows for flexibility and ease of programming.

PREREQUISITES
  • Understanding of square wave signals and duty cycles
  • Familiarity with Arduino programming and interfacing
  • Knowledge of frequency counters and decade counter ICs
  • Basic electronics principles related to LED circuits
NEXT STEPS
  • Research Arduino libraries for reading digital signals
  • Learn about frequency counter circuits and their applications
  • Explore decade counter ICs, specifically the 4017 series
  • Investigate methods for LED multiplexing to avoid flickering
USEFUL FOR

This discussion is beneficial for mechanical engineering students involved in electronics projects, hobbyists working with Arduino, and anyone interested in automotive electronics and tachometer design.

berdan
Messages
31
Reaction score
1
Hi,dear engineer fellas.

Here is my query :

We are team of students who compete in international FSAE competition-that is,we are making a racing car if you will.The engine is motorcycle engine.
Our team is responsible of the different circuitry . Funny stuff is,we are all mechanical engineers :) .
Anyways:
I have to design device ,that reads the data from onboard ECU (engine control unit) tachometer.The output from the drive circuit is a
square wave with a 30% “on” (Vbat) and 70% “off” (0v) duty cycle.Every pulse means one revolution (that is changable with ECU service program ,anyway,that's what we agreed on).

What circuit can I use to decifer the RPM?The circuit we agreed on will have 9 Leds,each led simbolizes range of 1000 RPM.

http://imageshack.us/f/7/vm4s.jpg/
Anyway,being in distant past practical electronics engineer,I will try my hardest to understand what you will throw at me :) .

Thanks in advance.
 
Last edited:
Physics news on Phys.org
berdan said:
Hi,dear engineer fellas.

Here is my query :

We are team of students who compete in international FSAE competition-that is,we are making a racing car if you will.The engine is motorcycle engine.
Our team is responsible of the different circuitry . Funny stuff is,we are all mechanical engineers :) .
Anyways:
I have to design device ,that reads the data from onboard ECU (engine control unit) tachometer.The output from the drive circuit is a
square wave with a 30% “on” (Vbat) and 70% “off” (0v) duty cycle.Every pulse means one revolution (that is changable with ECU service program ,anyway,that's what we agreed on).

What circuit can I use to decifer the RPM?The circuit we agreed on will have 9 Leds,each led simbolizes range of 1000 RPM.

http://imageshack.us/f/7/vm4s.jpg/



Anyway,being in distant past practical electronics engineer,I will try my hardest to understand what you will throw at me :) .

Thanks in advance.

Since this is your schoolwork project, it is not appropriate for us to tell you how to make this circuit. You must do the bulk of the work on it.

Try starting with reading about frequency counters: http://en.wikipedia.org/wiki/Frequency_counter

And also read about decade counter ICs: http://en.wikipedia.org/wiki/4000_series#4017_decade_counter

If you have specific questions after doing that reading, please post them here. You should be able to post a block diagram of your circuit after doing that reading, however...
 
There are a number of ways to go about this. Some much more crude (simple) than others. You haven't stated any accuracy specs. Counters is a decent way to go since they will be as accurate as your timebase. Other methods are simpler and of course less accurate, but probably quite acceptable.
 
Since this is your schoolwork project, it is not appropriate for us to tell you how to make this circuit. You must do the bulk of the work on it.

It's not my schoolwork project,we are team of students who make a car.I don't get any homework credit for solving this problem..More over,our academic teachers tell us to use any information source available.

Anyway,those links do not say much to me,specialy the first one which is very generic (about the frequency counters).I tried to look more detailed circuits overthe web but not much luck.

There are a number of ways to go about this. Some much more crude (simple) than others. You haven't stated any accuracy specs. Counters is a decent way to go since they will be as accurate as your timebase. Other methods are simpler and of course less accurate, but probably quite acceptable.

Well,the only constraints for this problem that I can give,we need to measure from let's say 20 Hz to around 200 Hz (which is from 1200 RPM to 12000 RPM,because ECU onboard tachometer gives one pulse for each revolution),and ,hmm,maybe "refresh rate" sort of speak of around 500 msec (I guess that's enough time not to drive driver insane with led flickering).
Again,I am mechanical eng. student,with only rudementary electronics training and practise.
 
berdan said:
It's not my schoolwork project,we are team of students who make a car.I don't get any homework credit for solving this problem..More over,our academic teachers tell us to use any information source available.

It's not a schoolwork project, but your teachers are guiding your work? If you do not complete this project, do you still graduate?

And there is a difference between "using information sources" and asking others to draw out a schematic for you. Can you sketch how you would use the counter ICs to give you a signal that you can use to drive the LEDs? If not, you should have an EE student helping you on this project, IMO.
 
It's settled ,we going to implement it in arduino.
Thanks guys.