Use the AHACB .cry strategy file. I have that strategy and HOG0.bin loaded right now, and it appears to be working fine, i.e. nothing to indicate it's the wrong definition/strategy for this binary.

You won't be able to save the binary or datalog until you get a registration code from its author, sailorbob, a.k.a. Derek. His information will pop up when you click Info --> Revision Info, or just press Ctrl+R.

I'm not too certain about AHACB and all of the binaries that fall under it, but I do know that VEX1 and WAY1 also work. It's very similar to the AHACA strategy I've been building for the past couple of years; the greatest difference is mostly the lack of knock sensing and relevant PIDs. Kinda sucks there's so much Mustang crap out there and so little for the trucks, IMO, but it has gotten considerably better, relatively recently.

 

Sig,

I got the AHACB strat from Derek and it won't datalog correctly. He is trying to fix it but as of now:

1. ECT is always 234
2. Vbat is always 5.875
3. RPMS are always in 6k range
4. TPS is off

Derek noticed that SAFTOT was off too and thinks he fixed that. He's been really good about responding via email.

Did you have any problems like this?

Do you think the AHACA strat would work on my EEC? I'm going to try the VEX1 and WAY1 .bins later with AHACB to see if anything helps.

 

Thanks Sig. I have AHACB on the laptop and really liked it. I thought it was Clint's file and have asked him twice for the Reg key. Thanks for the tip on figuring out who it belongs to.

I unplugged my knock sensor 6 months ago and won't be going back. I pull my plugs frequently to double check that I'm not getting detonation since my exhaust is kinda loud.

 

I've had all sorts of problems. :toothless

Those PIDs you listed are definitely wrong in the 'latest' AHACA (Rev. 7) listed on the eecanalyzer.net site. Anytime I've tried datalogging PIDs with addresses in the register file (0x00 to 0xFF), it REALLY takes a shit, sputtering, bucking, almost stalls, etc. ECT has been a problem, as has ACT, but I've found 'alternate' addresses for RPM, SPARK (which is SAFTOT), MAF, MAFV, LOAD, LOADX, EVP, TP, ACT (had to use a transfer function), and MPH (actually VSBAR). They're all above 0x0100, so no patches are required. The PW and INJDC parameters seem to work great as they are from Rev.7, but I'm on version 22 of my experimental definitions and STILL looking for things. :haha

I'm pretty sure it's the patch code that's the problem, but I haven't a clue as to how to generate new patch code or fix what's already there. There IS an AutoGeneratePatchCode tag you can put into the Profile sheet of the definition file, but I've tried it with absolutely NO success. It may have to do with my version of the QH. I've got v1.2, so it needs to be sent back for a re-flash to v1.6 soon as I'm able.

That's the other PITA I've had: sometimes, it's like it doesn't give a shit what I tell it to do. Changing some EGR stuff, like switches and multipliers, doesn't appear to do a damn thing...until I turn the truck off and come back some time later to try again. Then magically, the changes I've made start working. This kind of behavior can make tuning into an exercise in :banghead .

Oh well, it's made me into an expert of turning off my truck while going down the road and restarting it. :rofl:


EDIT: The ECT address and datalogging worked ONE TIME, now that I think about it. That was ONLY when I used Clint's Rev.7 definition file. It makes no damn sense to me, since I even tried copying EVERYTHING from my definition to his to try it out, and it still puked.

 

unfortunately the AHACB def file I'm using is encrypted so I'm SOL trying to edit anything, even if I could figure it out.

I loaded the VEX1.xls from eecanalyzer and Spark and TPS worked, but the others were still wrong.

I'm not sure what to do next. I've got $500 worth of software and hardware now and can't do much.

 

I'm not sure what to do next. I've got $500 worth of software and hardware now and can't do much.

This tuning stuff takes time, man. It does pay off, but you've got to stick with it, and drill through the problems, one at a time. What do you need to change in the tune that the AHACB strategy is lacking?

Like I've mentioned before, it's unfortunate the truck PCMs don't have nearly the support level of the Mustang PCMs. Owning a vehicle that's not really designed or intended to perform well is probably the biggest reason, but much like the Mustang tuners have muddled through and figured things out, we can do the same.

You should consider yourself lucky regarding the AHACB strategy. That sucker has many more scalars than mine (578 vs 341), Derek supports it well, and there are quite a few guys out there with VEX1/WAY1/HOG0 PCMs trying to modify their trucks. AFAIK, I am the only guy tuning a BIO0/AHACA PCM with a QH, and I've fleshed it out fairly well on my own; I'm up to 239 functions and 51 tables, with all the transmission control functions finally complete.

Here's a list of the working TAGs in my Payload sheet:

• LOAD
• LOADX
• MAF
• MAFV
• SPARK
• N
• MPH
• ISCDC
• IPSIBR
• IPSIBR_KGHR
• KAMRF1
• KAMRF2
• LAMBSE1
• LAMBSE2
• EVP
• PW1
• PW2
• VBAT
• TP
• BAP
• ACT
• HO2S1
• HO2S2

I have notes on many more, but it's just a matter of (not) having time to check every single one, let alone do it while driving.

 

this all sound complicated. maybe its just all the filenames and crap ive never heard of.:toothless

 

Que dijo?

 

Derek sent another AHACB to try where he thinks RPM and SPARK are fixed. I'll try it today, but then I still have problems with VBAT, TPS, and ECT.

I tried another DEF file (VEX1) and TPS and Spark worked but RPM, ECT and VBAT did not.

Here's what I don't understand - how do I create my own DEF files? I have Binary Editor and EEC Analyzer. I saw the DEF template. How do I read the .bin to figure out which addresses to input? If I knew how to do this I could use the info from the DEF where TPS worked and try to figure some stuff out on my own.

All I really know how to do at this point is load DEF and Calibration in BE and click buttons.

Oh and since Derek's AHACB is encrypted I can't see what he has done.

Also, I've read on eectuning.net that WAY1 follows a VEX1 strat. The guys at Moates said HOG0 was a VEX1 strat, and Clint from BE said VEX1, so natch I'm confused about which strat I should be pursuing.

 

whats with the different strategies? are they just different ways the computer reacts to certain changes. like how much advance at a certain rpm?

 

I'm not sure Pfun. I know several EEC catch codes can fall under the same strat. For example, WAY/VEX1/HOG0 fall under AHACB strategy.

Derek's AHACB revisions work great. Now I can start datalogging.

I have to hook up my wideband too. I'm on the quest for better mileage and more power at WOT.

 

personally i wouldnt go through all the trouble with that kind of stuff, id just do whats known to work then worry about stuff like that. then again i can just watch you struggle with it.:rofl:

cant you just make it stay in closed loop full time? wont that improve milage?

 

I will try to give you both some answers when I'm able, probably sometime tomorrow. Tonight, I'm goin' pimpin'. :imp

Short version: VEX1 isn't really a strategy. It's a PCM "catch code," or a binary file, just like mine is BIO0. But it is correct to say that VEX1 and WAY1 both fall under the same strategy.

A strategy is a "secret decoder ring" if you will, that allows programs like Binary Editor to 'know' what the structure of the binary looks like. They are the means to knowing exactly where things are, like spark and fuel tables, for example. The strategy tells the Binary Editor where to look for things (the address), the size of the PID (bytes, rows, columns), and any appropriate scaling that needs to be done (usually a divisor like 'X/65535' for a 2-byte entry, 'X/255' for 1-byte, then multiplication against another constant, e.g. 5.00, for most sensors).

You CAN stay in closed-loop all the time, but you wouldn't like driving a Bronco that never went open-loop when you punch the go-go pedal. I've tried it! :rofl:

Actually, BE has improved my mileage significantly. I can watch my load, spark, fuel, etc., but the more-important one for economy is the instant MPG. It tells you why having a light foot and coasting are very important for efficiency, and, immediately, the impacts of a heavy foot and high-speed driving.

I've been pulling down 22 mi/gal all this past week with the warm weather.

I want a wideband sooooo bad.....! :cry I know, I know, I said I'm gonna build a controller....yeah, yeah.... :rofl: