Stock MAF on "pressure" side?
Registered User
Joined: Jul 1999
Posts: 219
From: College Station, Tx, USA
Originally posted by y2khawk
Now that's how to do it
AVR have more than 8 bit resolution? Curious how the conversion granularity is.
either way, much better solution. My box from Pro-m was too sketchy for my taste, and when it crapped out i ditched their MAF for the current setup.
I've always run the MAF on the pressure side with great results.
Now that's how to do it
AVR have more than 8 bit resolution? Curious how the conversion granularity is.
either way, much better solution. My box from Pro-m was too sketchy for my taste, and when it crapped out i ditched their MAF for the current setup.
I've always run the MAF on the pressure side with great results.
. The built in ADC is 10-bit, at ~15 ksps. Even has a nice little "low noise" mode were you can shut off most of the uC while the ADC unit is doing a conversion for better accuracy. Spec without low noise mode is +- 2LSB's for absolute accuracy, and +-0.5lsb for linearity. But the main thing is there are some nice c compilers and it has more than enough horsepower for even my crappy code
. I think 10 bit's should be plenty, but if I see any aliasing I will just just add in an i2c compatible separate higher resolution ADC - since codevision C has nice support for i2c communications. But I think 10 bits should be fine.Chris
Registered User
Joined: Jan 1999
Posts: 884
From: I reached back like a pimp and smacked that LS1....
Originally posted by Chris B
Kinda overkill, but it works. The built in ADC is 10-bit, at ~15 ksps. Even has a nice little "low noise" mode were you can shut off most of the uC while the ADC unit is doing a conversion for better accuracy. Spec without low noise mode is +- 2LSB's for absolute accuracy, and +-0.5lsb for linearity.
But the main thing is there are some nice c compilers and it has more than enough horsepower for even my crappy code. I think 10 bit's should be plenty, but if I see any aliasing I will just just add in an i2c compatible separate higher resolution ADC - since codevision C has nice support for i2c communications. But I think 10 bits should be fine.
Chris
Kinda overkill, but it works
. The built in ADC is 10-bit, at ~15 ksps. Even has a nice little "low noise" mode were you can shut off most of the uC while the ADC unit is doing a conversion for better accuracy. Spec without low noise mode is +- 2LSB's for absolute accuracy, and +-0.5lsb for linearity. But the main thing is there are some nice c compilers and it has more than enough horsepower for even my crappy code
. I think 10 bit's should be plenty, but if I see any aliasing I will just just add in an i2c compatible separate higher resolution ADC - since codevision C has nice support for i2c communications. But I think 10 bits should be fine.Chris
I could have got as much out of that if it was written in arabic
Registered User
Joined: Feb 2000
Posts: 22
From: Waterford, MI USA
Originally posted by Chris B
Kinda overkill, but it works. The built in ADC is 10-bit, at ~15 ksps. Even has a nice little "low noise" mode were you can shut off most of the uC while the ADC unit is doing a conversion for better accuracy. Spec without low noise mode is +- 2LSB's for absolute accuracy, and +-0.5lsb for linearity.
But the main thing is there are some nice c compilers and it has more than enough horsepower for even my crappy code. I think 10 bit's should be plenty, but if I see any aliasing I will just just add in an i2c compatible separate higher resolution ADC - since codevision C has nice support for i2c communications. But I think 10 bits should be fine.
Chris
Kinda overkill, but it works
. The built in ADC is 10-bit, at ~15 ksps. Even has a nice little "low noise" mode were you can shut off most of the uC while the ADC unit is doing a conversion for better accuracy. Spec without low noise mode is +- 2LSB's for absolute accuracy, and +-0.5lsb for linearity. But the main thing is there are some nice c compilers and it has more than enough horsepower for even my crappy code
. I think 10 bit's should be plenty, but if I see any aliasing I will just just add in an i2c compatible separate higher resolution ADC - since codevision C has nice support for i2c communications. But I think 10 bits should be fine.Chris
I'm a motorola guy myself, currently hacking together as little thermocouple and A/D box with a CAN transceiver. String a couple together w/ a CAN card and maybe Labview and i got me a nice datalogger for all 8 EGT's, some intercooler temps, maybe a collector back pressure or 2, etc etc
keeps me busy But i'll agree, a CPU is the better way to go
Thread
Thread Starter
Forum
Replies
Last Post
