new $EE tuning thing!

[jthompson122183]

Well I found out what the 21cd table is on t-side. I asked about the table in a tuning group on Facebook and this is what was postedAttachment 10395

[kur4o]

Well I found out what the 21cd table is on t-side. I asked about the table in a tuning group on Facebook and this is what was postedAttachment 10395

There are four tables like this for each sensor two front and two rear.
I see no evidence in the disassembly that this table is used for something like that. I guess it is used only for corvette obd-2 diagnostics for sensor health when engine is not warm enough.
Still need to see if it is related with blm update enable routine. It is really complicated and unclear.

[steveo]

It looks like it is common for eside to answer 05 aa on the first mode 06 request. I have no idea why maybe PCM dependant or some deliberate glitch left from GM.
So you can try to add e-side exception on mode 06 request to accept 05 as valid answer. That may resolve the issue.

i'll check it out.

Those extra modules on y and some b really load the bus and can get you as fast as 2 frames per second

some of the more deluxe b-bodies are having similar problems, pulling fuses is solving it.

i can make a special routine to bombard and query the related modules to see what answers to mode 8 requests.

[steveo]

posted a new beta with possible fix for b-body and f-body cars. for 0xF1, 0xF0, 0x81, 0x0A, 0xA6, and 0x40, i repeat 10 mode 0x08 requests each. i modulate the timing of the requests themselves +0-5msec between each request and +75-80msec between each iteration. this brute force takes less than 1 second but might be enough to hammer the bus and make the devices listen. i've sent this beta to two users outside this forum that have had issues and i'll see how it works for them.

also possible fix for kur4o's e-side nonstardard aldl reply. it still produces an error in the debug log (as it's technically a breach of normal aldl comms due to its mode mismatch), but if 0xAA is the response, and it's the first mode 6 packet for the e-side, it flushes the read buffer and continues on. i think that'll effectively go past it. let me know how it works.

[kur4o]

Tried the new beta, so far the mode 05 issue is gone. It still shows the error mismatch but loads fine the bin afterthat. I am very happy with that.

Sniff some module commands for data request.

Y-body
abs [f9 57 01 00 af]
sir [fa 57 01 00 ae]
ccm [f1 57 01 00 b7]

B-body
HVAC [ea 57 01 01 bd]
ccm [f1 57 01 01 b6]
SIR and ABS as y-body

[steveo]

thanks that's a BIG help. eehack has a lot of users emailing me, i can use them to do some raw commands and figure out what we can get.

glad mode 5 is working for you.

[steveo]

digging around i found the ABS data sheets for the y-body, also just noticed the common ADX file for tunerpro has SIR labeled as ABS, so now we have at least some of the SIR data. i'll start with the SIR module definition, and look into ABS more.

not sure what the vette CCM or bbody hvac spits out and not sure anyone will care, but might be cool to look into too.