Background:
If you're familiar with the '747 ECM, the data rate is very low (~1Hz
output). This makes things like monitoring the O2 sensor voltage to look for sluggishness jsut about useless.
I wanted to pull the O2 sensor crosscounts and simply divide by time interval in order to get a crosscount rate. In that manner, I can take a relative look at O2 sensor health. I'd like to see ~3Hz crossing rate.
I'm datalogging via a Red Devil River Bluetooth adapter into ALDLdroid. I'm using the Tunerpro V5.2 bitstream definition file found HERE. Everything else seems to work alright, but the O2 crosscount value never changes from zero. I'm thinking that either the bitstream definition is wrong or the Bluetooth adapter is goofing up somehow (although I don't know how all the other values would be good).
I can see the O2 sensor voltage crossing over/under the 450mV midpoint as I look at it, but still the crosscounts remain zero in closed loop.
How can I check the .adx against the actual bitstream?
If you're familiar with the '747 ECM, the data rate is very low (~1Hz
output). This makes things like monitoring the O2 sensor voltage to look for sluggishness jsut about useless.
I wanted to pull the O2 sensor crosscounts and simply divide by time interval in order to get a crosscount rate. In that manner, I can take a relative look at O2 sensor health. I'd like to see ~3Hz crossing rate.
I'm datalogging via a Red Devil River Bluetooth adapter into ALDLdroid. I'm using the Tunerpro V5.2 bitstream definition file found HERE. Everything else seems to work alright, but the O2 crosscount value never changes from zero. I'm thinking that either the bitstream definition is wrong or the Bluetooth adapter is goofing up somehow (although I don't know how all the other values would be good).
I can see the O2 sensor voltage crossing over/under the 450mV midpoint as I look at it, but still the crosscounts remain zero in closed loop.
How can I check the .adx against the actual bitstream?
