Reading a speed sensor best method?

[davewanna]

Cheers for that Dave, looks like it will help me out a lot. It's pouring rain here so haven't had a chance to jack the back wheels up and test the car out yet.
But no doubt I will have more questions soon.

Looking at my post history, I found I originally asked this question in 2009, but didn't really have the time to sort it out, so I programmed the car to change gear based on RPM, not on speed, and then pretty much forgot about it. There was helpful posts in that thread also. Surely I have enough to make some progress now, if only this rain would stop.

Cheers

[Art]

Did you put the sensor there yourself? or is it part of the vehicle?
There should be a logic signal at the ECU.

But, yeah, anyway, external interrupt on the rising edge of the signal.

((variable pulses counted in a second X 3600) / constant pulses per km) X 3600 = Kilometers per hour!

[davewanna]

It's a factory sensor in the gearbox, but there is more than one. There is also two ECU's, one for the engine, one for the gearbox, that I am replacing, as the engine has been replaced with something more powerful, and now changes gear too soon.

I haven't been able to work out interrupts yet, do I have to use the CCP1 pin? I haven't used interrupts at all, is there a "dummy's guide" anywhere? haha

I programmed it today to read with PULSIN. I am reading the tacho, and the speedo now with PULSIN, but the reults are average. There is some 'contact bounce' with the speed sensor, that gives me erratic readings. I have programmed it to take two readings, and only use them if they are similar which is working. But with the PULSIN_MAX @ 10000, reading the RPM, and the SPEEDO, and sometimes having to re-read the speedo, the whole program runs fairly slow until the car speed, and the RPM increase. I would still like to get the capture interrupts working.

Also, I have run out of program space. It's a project that has grown over time, and now it handles the auto gearbox, monitors engine specs, and does climate control. Also has a setup menu where sensors can be calibrated, and gearbox and air-con settings can be changed. Current pic is a 16F877A.

From what I can tell, the 18F452 is pin compatible, and has twice the program space. Would it be viable for me to port my code over to the 18F452? I have only used 16F devices before.

Thanks...

[Jumper]

Hi,

If you plan to change from the 877A to something else I recommend 18F4620 (which is also pin-compatible). That will give you 64K Flash and alot more RAM. The only reason the 452 would be an option is if you cant get the 4620.

Do not worry about changing from the 877A, the 4620 is still easy to handle and has multiple INT inputs that you will find really useful.

[Art]

I have had a 16F877A (@4MHz) working in a hot car cab for two months without a reset. That is a plug for the hardware.

Some of the goodies that come with basic block execution of your program (and PULSIN will be one of them) where interrupts will not.
All I can say is search for Darrel Taylor instant interrupts or study Microchip datasheets to do it yourself, (but you'll probably need an example anyway).
The effect a bit like multitasking, your program does not appear to be held up while pulses are being counted.

[davewanna]

Jumper: Thanks for the info on the 4620, looks like the 452 will do, but the 4620 will be better.

Art: I had a quick look at your projects, and you might be interested to know this auto controller is actually in a Surf. And I am doing a digital speedo type of arrangement for my hilux ute also, except instead of numbers, I am using the motors out of a motorcycle dash to move the factory needles.

I will look through your other projects later.

Thanks!

Dave