TunerPro User Forum

the pins themselves are physically different, so can't be done directly.

however, you could hook up a secondary port in parallel and have both available.

that is a very "chatty" application.... step 1 is to go to Mode 1 ALDL Dump Request Reply and change Body Size to Payload Offset + Payload Size + 1. that may fix some of the errors, but likely not all of them. after that, mode 8 commands will need to be inserted to get the ECM and BCM to q...

some of the early 4T60Es didn't have a trans temp sensor. the various modes are all fairly application specific. some ECMs don't support certain modes and those that do rarely have the same sequence of bytes to control their mode4 functions. would have to disassemble a BIN and find the commands to s...

you won't damage the ECM using mode 4 commands.... you also won't be able to get trans temp that way either. mode4 controls outputs. what you want is mode2 or mode3 to selectively dump data from RAM. you would need to know what byte in the RAM is being used for trans temp. however, i'm looking at th...

what kind of O2 sensor did you install? certain brands do not play well with GM ECMs/PCMs at all, Bosch seems to be a common one. idle instability can be caused by a few different factors with these since idling is done via a hybrid alpha-n method. any kind of problem with the MAP sensor/vacuum line...

at idle, that would be expected....

if you were cruising at a steady speed(say 55MPH) and it were swinging that slowly, i would consider it a problem.

a 1990 is MOST LIKELY to be $88, though there were still some $6D cars. would need to see what BCC is listed on the MEMCAL to be 100% certain.

i wouldn't think the A1 ADX would work with 88 code though.... send command is slightly different.

V5 allows long enough strings to do so. V4 didn't.

the IAC is a stepper motor used to control the amount of air going into the engine during low to no throttle. think of it as a computer controlled vacuum leak. more steps = more airflow. vacuum(as measured by the MAP sensor), it looks like you're at none if it is showing 4.92 volts. there should be ...

the amount of info being limited is normal... a lot of GM vehicles didn't really have ECMs in 1982, and the ones that did were pretty primative in what they could do.

i'm not used to a crossfire, but you seem to be idling with a LOT of IAC steps and little to no vacuum.

sure you're trying to load an ADX file when that happens? i think that message will happen when trying to load an ADS in addition to probably most other filetypes.

sounds like you're opening the XDF, not the XDL.

for guages, look for a red circular "guage" icon underneath the navigation bar. should see 4 icons there for the 4 different views.

what error message comes up when the ADX is loaded?

looks like you have the right ADX, logs are recorded as XDLs. did you already get one recorded?

you're on the right path.

i guess, what are you attempting to do? just datalogging(or watching a log?) or changing the calibration?

then what Six_Shooter stated is the problem you'll run into.

you would need to find a suitable and open A/D channel, patch the code to read it, store it in an open RAM location, then transmit it in place of another value in the ALDL stream.

referring to target AFR or read AFR?

carbon cannister = emissions item. captures gasoline vapors that form in the gas tank, get stored in the cannister until the ECM commands on a solenoid that allows those vapors to be drawn in by the engine and burned.

CCP = carbon cannister purge.

correct.

and you'll need to do that every time you launch tunerpro. the option does seem to persist if changing ADX files, so no worries there.

are you trying to use tunerpro V4 or V5? V5 is only officially supported on XP SP3 and later(though it has been made to work on XP SP2, that i know of).

narrowband O2 sensor. while i have generated a decent table for converting narrowband mV into AFR, there's no guarantee of how accurate it actually is. and that might be a bad O2 sensor. it is swinging a bit(which is good when operating in closed loop), but not at any kind of normal pattern. what's ...

XDF is not required for datalogging.

cable test only works if connected to the computer, but not the car. even then, it's not always an end-all test. correct ADS/ADX isn't required for this test either.

"low cylinder" means that at the very least, cylinder 4 has been detected to have a lot of significant misfires. i'd start by looking at the plugs, plug wires, maybe the ICM and the coilpack that control cylinder 4. if nothing is found by that point, then things are going to get a lot more...

A178?

http://tunerpro.net/gmOBDI.htm

try it out.

occasionally, when dealing with tables that have a bias/offset, when the bias value and the table value "cancel" each other out, the resulting data is -0.00, which is always an odd thing to see, especially if the equation required to create the value is identical. not sure if it bothers an...

my solution was to make a lookup table with all of the common and useful ASCII characters in it. worked for me.

EDIT: reading > me.

that works for the datastream side of things, but not in the BIN itself.

don't need a MAF to calculate airflow...

they do indeed do stuff, for closed loop fueling control.

what you're experiencing is completely normal.

assuming you have the correct ADX loaded and the right COM port selected, you should be able to scan it.

i think your ADS/ADX is wrong...

with the 5V portion of circuit directly connected to ground, that should register as 0 A/D counts, should come up as roughly 298.85*F. with the circuit open, that should be 255 A/D counts, should see near -40*F.

i believe this has happened to me before as well..

i think i usually either close/reopen the monitor window or close/reopen tunerpro itself and it fixes it?

to read the datastream, you need the correct ADS or ADX (depending on if you're running V4 or V5).

"hardware not found" is referring to emulation/burning hardware, not an ALDL cable, so that's normal.

file associations are largely used to "auto-launch" certain programs when the filetype is attempted to be opened. for instance, i have 3 BINs on my desktop since i use them often. if i double-click on one of them, tunerpro launches and automatically selects it as the current BIN. same proc...

is there a believable BPW being displayed in the datastream just before/when cranking?

how did you turn it off and what is happening?

you're on the right track.... but the +1 isn't +1 seconds.... it's +1 executions.

well.... think of it this way: if the RAM weren't incremented before checking against the scalar and the scalar was set to 0, then on the first pass: RAM: 0 scalar: 0 branch(and skip update) only if RAM is lower, do not branch if equal then on the first pass(and every pass actually), the BLM update ...

from John Pell's 8D disassembly: ;--------------------- ; UPDATE BLM ;--------------------- LCCE9: ldd *L0046 ; Air Fuel Ratio MODE WORD ; CRef: 0xCCE4 bitb #0x02 ; B1 1 = DECEL FUEL C/O ENABLED beq LCD5A ; BR IF NOT DECEL FUEL C/O ENABLED (Goes to LCD52 in ANHT) ; .....

that's a lot of info to go over....

couple of things i notice:

the RPM and PW when it starts cutting out looks like you're running into the park/neutral rev limiter, so i'd say that's normal.

at least one of your O2 sensors looks to be worn out.

some factory engines run pretty bad on factory tunes.... doesn't really surprise me. do some VE learns, get rid of knock if you see it, then see how well it's running. if you're not running into any knock and it's still running badly, next step would be to give it more advance and see if it helps out.

i'm surprised RBob himself doesn't have/supply a base BIN to run what appears to be a popular engine combo?

8184? kind of odd, but that would imply VERY close to 14-bit resolution... 14 bit being 8192. are you following the order of operations with that equation? i can't see a way to get negative numbers out of that equation without switching steps around. 30 - (X * 0.029296875) = in-hg (X * 0.029296875) ...

if it is 10 bit, then: X * 0.0048828125 = MAP Volts 30 - (X * 0.029296875) = in-hg examples: X = 1024 (5 volts, 0 vacuum) 30 - (1024 * 0.029296875 ) = 0 in-hg and for high vacuum... X = 0 30 - (0 * 0.029296875) = 30 in-hg that is, assuming 0 volts = 30 in-hg... i know with the GM 1BAR sensors i'm us...

with a 1BAR, 0 volts is 30 in-hg, 5 volts is 0 in-hg.

what kind of resolution are you dealing with? probably 8 or 10 bit?

there is a VE adder table at 39E for dealing with fuel at higher RPMs.

not sure which XDF you're using, but this is the one i generated, has some more stuff than the common one.

http://www.wikifortio.com/835826/my 4E.xdf.zip

moved to Other Makes.... was considering throwing it in the GM section, but it's not quite a GM model.

speaking of, what model is it? PCM part number? any info at all?

i would assume there is a VE adder table....

but as Mark pointed out, need to know what you're playing with first.

take original engine size, divide with new engine size.

ex:

383/350 = 1.094

multiply the BPC by that and it will get you more or less there.

like i said, did it with nAst1, which is my modified version of A1.

the way i have it setup, it won't rev up to whatever the limit is when the clutch is depressed, only cut fuel or spark if above the limit you want.

i've done this with nAst1, actually turned it into a 3-step limiter: step 1 = not moving, clutch disengaged, for launching at high throttle but not high RPM step 2 = moving, clutch disengaged, for shifting without lifting the throttle step 3 = max RPM to allow before cut regardless of MPH or clutch ...

TunerPro User Forum

Search found 962 matches

-0.00 in XDF display