CCM, HVAC, and ABS have mode 4 control, I can make a list of what data is displayed on oem but it will be undefined.
If we can find bin dumps of these modules it will get really funny.
F0 looks like broadcast with f4 id specified by cal data in the bin.
really?? i was assuming CCM was the master like a 'vette. that would explain why it's not working!Originally Posted by kur4o
so we might have three different connection routines, i was hoping that y-body and b-body would share one.
i might actually need to provide a selector on the settings page; y-body, f-body, and b/d-body. unless we can find a way to detect that by incoming serial data. that might be best. we could do like the OEM tools do, send a few 'resume' requests and wait for idle traffic, and look for specific signatures. lets search for those signatures. we need a 'vette guy and i think i can find that.
the only downside to that is what if guys have hacked cars with no CCM but still want corvette ABS codes or whatever. so maybe manual selection is the best way.
i think i might ask on first install what vehicle type (so the user doesn't have to worry about setting it) with a warning that if the vehicle type changes, go to settings.
vehicle type information may become necessary with ybody vs fbody ABS/TCS module queries anyways.
i have some thinking to do. can you confirm that the ecm is master on the b-body?
what if i get someone to donate you some modules, would you be interested?.... just for the hell of it
posted another one, bbody/ybody guys please test 'er out!
I make a decode list of the the db body idle scan messages.
The PCM is the masterbus for sure. If you can make it shut up it may be easier on the bus.
One part that you may miss is that each module can have multiple IDs assigned and it is defined in the bins.
For example PCM gets all data that is send on the bus. Id doesnt matter. If it is defined in bin it gets used, if it is not it is dumped.
I tested tside. It can get $91 id message send from abs module.
Also I found that corvette info is requested via $40 id but still couldn`t make it answer. I am still missing something. At least found in bin where this obd2 stuff is defined [f819-f9c7].
Played with mode7 but still can`t make the pcm answer my requests.
I am really interested to get some vette idle scan.
If you can source some modules will be great. Not sure will be needed but It will be fun to play with.
that's the thing, the only way i can think to do it is send a LOT of mode 0x08 messages really quickly for a few seconds until the ecm actually gets one.
the gaps are too small to 'search' for reliably.
so far it's not working. there has to be a way, otherwise how do the other tools work?
if the master (ecm) shuts up, it should kill the heartbeat frame and the other modules should be silent.
my last attempt sends 100x with 0-5ms random delay in between. that should saturate the bus and you'd figure the ecm would get at least one of them. it's unsuccessful.
Want to thank again everything you guys are doing. I can't say it enough!
i get that, but is it ever used anywhere interesting?One part that you may miss is that each module can have multiple IDs assigned and it is defined in the bins.
all i really care about now (now that all my goals have been reached), is just making it work properly for everyone, and trying to keep what's left of the lt1 tuning community together...
i don't even use the tool, i've given up trying to get my tune any better.
i think we'll gain a lot of users as people pull their cars out of storage, remember this thing only came out last fall... and that'll drive more traffic to the forum here, help keep things alive.
so thanks for your support (and donations... this program has bought me a TON of beer!)
I managed to cobble together a working windows laptop and have been using $EEHack for a week or 2 now to log my daily commutes (or at least the portion until the laptop battery gives out) and I am interested in getting a wideband, for 2 reasons. A) I'm starting to distrust the ~20 year old narrowband sensors, and B) I want to attempt programming the LT1 into a Lean Burn mode, of sorts, to see if it works for me since I'm doing so much light load/part throttle cruising and I am really trying to maximize my fuel economy. So I have a couple questions regarding WBO2's: Which would you recommend as working well with the LT1/$EEHack? I was leaning towards Innovate. I would be inclined to use 2, so I could read bank to bank instead of the aggregate, would it be possible to configure $EEHack in such a way that it could log both, using the A/C pressure pin and D27 (or whatever the other one is)? Do you have any idea of a more affordable way to do dual wideband logging than buying 2 separate kits? I seem to recall that one of the Innovate WB controllers can handle 2 inputs...And finally, I've read mixed opinions on using widebands as a permanent replacement for the narrowbands. I know they can do the narrowband spoofing, but I've heard some folks complain that a wideband sensor will not last nearly as long as a narrowband sensor in a daily driver. Do you think this claim has any merit?
dual widebands are total overkill.
FAST makes a dual one that's affordable though, that's what i have. it's not a great unit, but it works. the fact it's a 'dual' helped me quickly detect when I had a clogged injector, that's all. you don't have much per-bank balancing control above idle anyways, so seeing the banks independently is fairly useless.
eehack always logs both inputs no matter what, you can graph both together or display both in the dashboard no problem. but the analyzer only analyzes one at a time (whichever you have selected in settings). i will add something to 'average' them soon.
wideband spoofing sounds good but never works well. narrowbands work better for sticking around stoich, and the ECM wont get the response it wants from the nb simulator, it'll throw your afr all over the place. you'll want to install your wideband in a separate hole, have an o2 bung welded in.
if you're talking leaning it out at cruising speed or running AFRs different than 14.7:1 at anything but WOT, o2 spoofing and such is irrelevant, you'll need to run open loop. your narrowbands won't do anything. unless someone hacks it in, $EE doesn't really have the capability to run open loop just in certain zones of operation.
i run full time open loop myself and i've deleted my narrowbands and their wiring. closed loop is fine for emissions and self healing, but open loop is certainly more versatile, unless you think engines have optimal performance running stoich outside of wot, which isn't really true.
yep, comparing the wideband to the narrow band I came to realize quickly that the narrow band at anything other than stoich is worthless. I have a fairly lean cruise right now, but I'm running open loop full time. I have one narrow band still hooked up and I compare it sometimes to the wideband, but the computer doesn't use it.
It is my understanding that the whole reason that stoich is what it is and the reason the computer adjusts the way it does, bouncing between rich and lean around stoich is to keep the cats happy and working and make them last, not to make the engine happy. I have no cats so I don't see the point. My car runs great in open loop.
1994 LT1/4L60E Formula
it's more than that, it's trying to guarantee reasonable emissions in general. an engine burning at stoich has fairly clean emissions, and the o2 sensors allow the system to be self-healing to a point (if there's a vacuum leak or something, the o2s can still force it to burn cleanly)It is my understanding that the whole reason that stoich is what it is and the reason the computer adjusts the way it does, bouncing between rich and lean around stoich is to keep the cats happy and working and make them last, not to make the engine happy.
if emissions are a concern, keep it closed loop is a good idea
Awesome! This info helps me out a ton. I had wanted the dual bank WB for basically a similar reason, I'd like to know if there are any big differences in fueling from side to side to know if there's something like a clogged injector or etc. that needs fixing. The reason I asked about the NB spoofing was that my car does still need to pass emissions, visual and sniffer, and I wanted to make sure I kept the ability to do CL when necessary and was trying to figure out if I could just leave the WB in there the whole time, or if I would have to swap those, along with the tune, when it's time to get sniffed. And based on what you're saying, yeah, I should just plan on swapping the o2's when necessary. And yeah I understand about having to be in open loop to target a non-stoich AFR. Though I did read something about altering the NBo2 swing voltage to make it target a higher AFR in CL, but I'll need a WB to know if that works at all. Thanks again for all the awesome info and great tool!
Oh, and also this may seem like a really noob question, but how can I get $EEHack logs in csv instead of the native format?
Posting Permissions
Reply With Quote
Bookmarks