TunerPro User Forum

so, I don't know how many other people are using tunerpro to write patches, but something that has come to mind while writing many-hundred byte patches that would speed things up a bit would be a button in the Patch Entry Editor that would grab a string of base data of the same length as the patch d...

i've more or less done this by having the text background and text color change when the bit flips.

EDIT: I am the dumb, "graphic" didn't register.

closed loop correction is a short term fuel trim and BLM is a long term fuel trim. a BPW can't be derived from them, only an indication of how much the BPW is being effected by O2 sensor readings. 160 baud datastreams are unidirectional: data can only go from the ECM to a scanner/laptop. 8192 baud s...

described shortly: adding BPW into the datastream, 2 other bytes would need to be removed to place the BPW value into the stream(PROM ID, if present, is what I would suggest). it's a bit more complicated than that, but you would essentially end up with a unique ADX for a BIN with a modified datastre...

you could roughly approximate the amount of fuel injected with either a TPS vs RPM or MAP vs RPM lookup table..... but at that point, you might be further ahead to modify the datastream to output the BPW value.

I've had something similar happen with tinytuner.... the issue is that tinytuner was inserting a lot more data into the clipboard than what it needed to. I found that you can just paste what you do have copied into a spreadsheet, then recopy only what you need to go into tunerpro and you're good to ...

it's entirely possible that your datastream doesn't output a BPW value, few if any 160 baud ECMs do.

Tunerpro/Scannerpro are the only software packages that should recognize an ADX.

from what I'm reading up on the MEFIBurn package, it should have the correct ADX with it?

a BIN isn't necessary to capture accurate data, only that you have the correct ADS/ADX for the BIN you are running. if you have a PROM burner, you could copy off the AULS BIN that is on your current PROM. that could be your basis for a custom tune, otherwise you would need to decide which of the ava...

well, if they've sent along anything related to the datastream, it could be compared against the MEFI3 ADX I have to see if anything changed there.

i have an ADX for a MEF3 unit, but I have no idea how similar they are.

something, something, internet is written in ink....

http://www.gearhead-efi.com/Fuel-Inject ... rmation-AO

that may help.

A263 for your PCM, A293 for your ABS module.

I haven't done either of those yet for my last run-through, but I've built them before.

https://www.dropbox.com/s/mysb9o58pdz8h ... I.zip?dl=0

that should have both.

those should be present in the TP definition downloads page.

http://tunerpro.net/downloadBinDefs.htm

what you have is a P66 V6 PCM, they ran from 1993-1995 on the 3.4 F-bodies and 93-95 on 3100 powered FWD cars(speed-density only, the 94-95 A-bodies with a 3100 use a modified version of the 94-95 W-body 3.4 PCM, which itself is a derivative of the pre-94 series 1 3800 PCM..... the rabbit hole goes ...

most P4 applications(8/16/32KB BINs), yes. there are exceptions though.

with the C3 applications, those varied a bit, but usually at 0004(I think).

with the P6/P66 applications, anything goes. some don't even have mask IDs.

i would be very surprised if that weren't an 8D calibration. take a look at the BIN in a hex editor(you can call up the one built into tunerpro by pressing Ctrl + H when the BIN is loaded), click over to position 0008, see what value is listed. I'm expecting 8D or possibly AA. if 8D, you have your a...

i'll have to reinstall IDA and find out... I still haven't gotten everything organized/dealt with since a fresh OS re-install.

yahoo started sending tunerpro notification emails into my spam folder... never realized when there were updates. :( My guess from looking at the logs is that you're seeing cross-talk on the ALDL line. that was my conclusion as well, but it's difficult to tell what exactly will get the line clear wi...

from what I remember, the 7429 was able to be used in place of the other ECMs used up until its introduction, it essentially had some hardware fixes and got a new part number because of it.

the turning over but not firing is odd... what happens if you plug it in while the engine is already running?

https://www.dropbox.com/s/g4h6gc2sjv9wwxj/A072.zip?dl=0 here is a ZIP containing 4 files, 2 are for TP V4, 2 for TP V5. the way these early 3800 PCMs communicate is certainly different. the document states the way they connect includes responding to a message sent out to an ALDL device, which will s...

the ECM portion of A072 is nearly identical to A094, so that file shouldn't take too long to get functional. it looks like there might be a typo or two that will need testing, like the A072 document claiming that the ECM's ID is 4F instead of F4.... I don't know if I've ever seen an application that...

I've had a LOT of personal stuff to deal with lately... lymphoma is a hell of a ride, and I'm not even the one that had it.

I'll try and get to it tonight, I've got a lot more free time on my hands now than I have had for the past couple months.

what XDF are you working with?

L and M seem to act as redundant circuits for each other, likely due to how dependant all of the modules in the car are with each other. it does need to be "activated" in that the always being transmitted datastream needs to be disabled via commands from a laptop(or tech1 or xxx), then sen...

A072 does look correct, post here tomorrow(bad memory) and i'll see if i can get it done. at first glance, it looks really similar to a few other i've made, possibly close enough to only need slight tweaking for an 89 reatta.

hmm..... hard to tell what exactly is going on there. anyways, here is what GM did for what looks like all possible options on the 93-95 northstars(except for the allante): http://imgur.com/3MAiMkB,d6wkJMW it would seem that you can have a broken wire anywhere in there and everything will still work...

do you happen to know the exact year/model of the car your harness was pulled from?

the L and M pins are used as kind of a ring network(i believe that's the correct term)... it varies a bit depending on the engine/year/model, even if it is a domestic market vs export car.

i don't have a 93-95 northstar car to play with..... i've built prototype definitions and had people test them. any ALDL cable that works with 8192 baud datastreams should work. i looked into the connector issue, the B pin only appears to be used on the 4.9 cars to force it into set-timing mode. gra...

with a northstar PCM, you should only need A and M.... i'm not aware of the B pin even being populated on them.

there is more than one problem you're going to run into.... what MAP sensor is being used now? what trans? i wouldn't want to try and get the northstar PCM to work in anything other than a cadillac, there is too much intermodule communication/dependancy that now has to be disabled or worked around i...

i'll gladly send them under the warning that they're very incomplete and only useful for a 95 calibration.

https://www.dropbox.com/s/8iv6n45gpcrzhyf/A210%20test.adx?dl=0 try that ADX, it isn't what i would call finished(reorganization and labeling needs done), but it should work well enough to see if things are going to play well together. any ALDL cable that works with other GM stuff that operates at 81...

tunerpro will do it, as long as you have an ADX that will work with it. i've built at least one for the northstar applications, but have no way of testing it.

Westers definitely has access to some stuff, couldn't say how much. i've poured through my own disassembly for many, many hours and while i've likely found all of the tables in both sides and given them rough labels, i've only put definitive labels on maybe 5-10% of them since the rest are rather un...

http://northstar.7p.com/ that is one 7730 route, though it is setup for a 5 speed fiero. i'm not necessarily a fan of where the calibration ended up at, but it can/does work. i don't know about the 96-99 northstar PCM.... i know it is a somewhat related version of the 93-95 version in that it still ...

it will need to be present for the second processor to function. without it, the primary processor won't be too happy when it doesn't receive any communications from the secondary. however..... that is a large jump in operation to go from a 4T80 to a 700R4.... the transmission side isn't going to be...

the northstar PCM is one of 3(i think) series of dual-processor PCMs, the other two are the 94-95(and slightly modified 96-97) LT1 and the 93-95 3100/3.4RWD PCMs. having two processors, they also have two PROMs. generally, everything is split more or less into an engine side and a transmission side....

i started making an XDF for the 95 applications(93, 94 and 95 all require different XDFs), but i've put a lot of time into it for not a lot of results. i don't know if i've ever specfically looked for the VATS option in the calibrations, it probably isn't difficult to find after knowing how it works...

i'm showing BCRL as being the E-body(eldorado), HO Northstar calibration. i don't have that exact one, but i do have a BBSX, which is superceded by BHMU. BCRL is also superceded by BHMU, so there is a good chance it will at least be close to what you need.

http://tunerpro.net/gmOBDI.htm you'll find the A269 ADS here, which can be converted to an ADX fairly easily. https://www.dropbox.com/s/xey9g7d83eerrui/A269.adx?dl=0 alternatively, i just converted it there. looks like the XDF isn't in the TP downloads section though.... isn't on gearhead-efi either...

A269 for the ADX.

the $36 XDF might be correct?

i'll need to look again, but i seem to remember pretty much none of the saturn stuff made it into the ALDLStuff.zip archive that has most of the OBD1 streams in it. without it, you have to reverse engineer every single byte in the datastream..... or have some inside knowledge of how a tech1 is acqui...

don't suppose you can upload the ADX used to grab that data as well?

how large are the XDL files that get created from a recorded log?

by trace, i assume this is in a monitor view.... i can see a few solutions, some working better than others. changing the min/max range, along with the equation to display negative numbers would do such a thing and leave good data, just with the wrong sign in front of it. creating an AFR "error...

that PCM has a couple of datastreams, some of which are basically specific to the transmission, so it was broken up into two sections. you seem to have the transmission ADX loaded.

you need to increase Body Size by 1, not Payload Size.

There are no XDF restrictions in the free version.

If you could post both XDFs somewhere, we may be able to figure out where the problem lies.

TunerPro User Forum

Search found 962 matches

Patch base data idea