Here's a bit of code I've written to make a hp calculation formula I'm using in tunerpro a little more useful. This saves the current mph for app. 1 sec then outputs it to the datastream. Look functional? Now I have no idea where to insert this snippet, and I need an idea of how to send this to the datastream inplace of the engine run time. Can I hand it off to the subroutine at LFC89 and change how the engine run time gets it's data? I'm using the ARAPWB patch. At some point I think someone needs to go through and clean up $6E to clear out some room for new code. I'm learning... slowly. Maybe that'll be my project at some point.

bump

I'm not sure why you need to output the MPH each second to the data stream. The vehicle speed is already in the stream. Just use the engine run time counter at the PC end to know when to do the HP calculation. That too is in the data stream.

Should be able to get 11 frames of data a second from the ECM. This is at 8192 baud.

The easiest way to get more room in a BIN is to remove the factory test code. It is never used once the ECM is in a vehicle.

RBob.

At the pc end? You mean with excel or something? I want to see the value in tunerpro. Engine run time doesn't display correctly with the ARAPWB patch so I need to use the 1 sec flag.

The PC end is where to put the tough code. Why would the WB patch upset the engine run time variable? It shouldn't. Since it does fix that first. Then use whatever data analysis tool to extract the MPH gain over time for the HP calc.

RBob.

I'm barely familiar with motorola's code, much less writing stuff for tunerpro, LOL. How would I hold the MPH in memory with tunerpro? I'm going to contact the guy that made the ARAPWB patch so I can get info on his patch, then start fresh with a clean ARAP with mode 2 & some other stuff cut out.

OK, i have a better idea of what you want to do. The way to do this is to find two free bytes of RAM. Then place the address of each of these bytes in the ALDL stream data look up table. This table defines what data is sent via the ALDL stream. Can replace some thing that is rarely used, such as the rich/lean counter and cooling fan PWM.

In the IRQ1 routine there is a 1-second section of logic. This code can be found in there:

In this code location you want to shift the 'current' MPH byte to the 'old' MPH byte. Then save the current MPH reading in the 'current' MPH byte. Basically you are shifting the current to the 1-second old and saving the new current MPH reading.

This way TP will have both the 1-second old MPH reading and the current MPH reading. Each being updated once a second.

Like this:

The OldMph and CurrentMph are RAM locations that are used to store the data. Those are the locations that are placed into the ALDL stream table.

RBob.

Here's what was done to run time with ARAPWB.

CB1A: LDAA #$00
CB1C: JSR LF2F7
CB1F: STAA $0170
CB22: NOP
;---------------------------------------------

;---------------------------------------------
; If no Comm >= 5 Sec Force mode 0
; (TM'R VAL AT C70B)
;---------------------------------------------
CB23: LCB23 LDAA L0166 ; SERIAL DATA TIME TO FORCE MD 0

Yes, that will certainly wipe out the engine run time counter. Along with only doing a WB conversion once a second.

RBob.

It updates fairly quickly in the datalogs. I think he moved it to where the p.s. stuff was and didn't change the run time code back for some reason. If that's the case it can still be made to work. Is there a way lag the 2nd speed sample a sec behind rather than just outputting it once a second? Real time calc's would be nice... can it even hold on to a full sec of data without overrunning the memory with junk? Here's what was done to the p.s. section.

****FROM****

ldaa *L0066
cmpa LC576
bhi LCB7E
ldaa *L002F
coma
anda #0x08
oraa *L0038
staa *L0038

****TO******
ldaa *L0066
cmpa LC576
nop
nop
ldaa #0x00
jsr LF2F7
staa 0x0170

Well 400z28racer's not responding. So back to my other question, can I do this real time without overloading the memory?

Bumpity bump.

I am sorry, I've been busy writing VHDL code for the past 6 months. I'll be able to help you in the next few days.

Merry Christmas

Sweet. Happy New Year too.

Ok time to bring this back from the dead. I went another direction and used another formula to get VE then esimated power from that. All I need help with now is getting the mat to work properly on your wb patch.

Here's the formulas I'm working with. I'm obviously missing something because hp and torq are waaay off. VE looks accurate enough.

VE-
((X * .1323) / (491.67 / (459.67 + A) * .0808)) / ((B * R * 1) / 3456) * 100
Where A is MAT, B is engine displacement, R is RPM and X is MAF.

HP-
(A * C * (X * .01) * B * R) / 792001.6
Where A is atmospheric pressure, B is engine dispalcement, C is static compression ratio, R is RPM and X is VE.

Torq-
5252 * X / R
Where R is RPM and X is HP.

Edit- corrected formulas.

Any takers?

I was just wndering if "C" should be Dynamic Comp instead of Static.

That doesn't help, probably because the formula assumes 100% ve and adjusts based on actual. Unless my car's suddenly making 1600hp I didn't know about! I did find out that LV8 and VE are essentially the same thing though after comparing the 2 in my datalogs, all that's needed is to change it to % rather than 0-255. So that simplifies things a little, no need for the mat or a separate ve calculation. These calculations seem to work out perfect on paper but gets goofed up in tunerpro somehow...

Found it. Devil's in the decimal. Here's the correct hp formula. (A * C * (X * .01) * B * R) / 792001.6

It's alive!!!

Looks like this is still estimating a little low. Other problem is it can't be used for forced induction using LV8 as VE. I need to figure out how to get the mat reading correctly again.