new $EE tuning thing!

[Xnke]

ZEB!

Creator of the .510 Deming Destroyer?

Been wondering what happened to the guys of that forum.

Steve, have you had any time to see if this will do the P66 V6 ECM's too?

[steveo]

Steve, have you had any time to see if this will do the P66 V6 ECM's too?

not yet.

i'd started making it work with the V6 ecms using pre-processor #define's. it logged and analyzed, and flash read worked (kinda, it read the bin but in a non-standard format).

that was several versions ago, new versions don't compile for V6 anymore, although the #define's are still there so it COULD be made to work.

the reason it's a bit difficult is i didn't write this project from the ground up to support different datastreams, mode4 commands, or flash routines, as i didn't plan on it being anything but an lt1 datalogger and mode4 controller.

[steveo]

had a error after flashing. attached a log. it'll need unzip Attachment 10093
using 4.0 release

the ECM did survive, right?

error messages from that routine are vague since i've never actually seen what byte is transmitted for a failed checksum or whatever. will improve that in the next release.

[jthompson122183]

the ECM did survive, right?

error messages from that routine are vague since i've never actually seen what byte is transmitted for a failed checksum or whatever. will improve that in the next release.

Yes the pcm survived and works as intended. I figured when I hooked up scan9495 that there would be error 50 prom checksum but no.

[jthompson122183]

Here is the list of ALDL mode 1 msg 0 to 6.

You can label it mode1 msg ?? command
and mode1 msg ?? memory location.

In your case:
The most used mode is mode1 msg0 [It is the main mode for most known dataloggers]
If you want to add other known memory byte to the stream, pick one of the existing that you don`t need in the data stream and change the memory location value to the to 011e.
When the PCM is flashed with new data You need to add the corresponding information to the logger programm so that it knows that at that byte now is 011e memory byte.

I have this working now. I patched byte 36 in the datastream as it was not used

[steveo]

Yes the pcm survived and works as intended. I figured when I hooked up scan9495 that there would be error 50 prom checksum but no.

weird. i think this might be a timing issue; that routine takes a HELL of a long time to execute, and i think the new version of qt deals with timers differently. the flash erase routine is another one that has a hell of a long response time (in whole seconds)

[kur4o]

Finally figured mode 4 cylinder deactivation.

mode 4 byte 7 $80=1[eside byte_30 $08]
ENABLE INJ CUT
mode 4 byte 10 $04 $02 $01 [eside byte_30 $04 $02 $01]
MATRIX LOOKUP FOR CYL CUT
1=000
2=001
3=010
4=011
5=100
6=101
7=110
8=111

Single cylinder deactivation only.
It is not possible to deactivate two or more cylinders at once.
Most likely spark will be set to 0 degree.
When engaged other mode4 commands will suffer, be disabled and behave strange.
Most important are spark and afr.
So use with special routine only for cylinder deactivation.

[steveo]

you realize your entire binary 'matrix' is just the cyl number minus one, as the values start from zero.

thing is these don't happen in numerical order they happen in firing order; im pretty sure it's actually:

(commanded_number=cylinder_number)

0=1
7=2
3=3
2=4
5=5
4=6
6=7
1=8

[steveo]

When engaged other mode4 commands will suffer, be disabled and behave strange.

haven't really noticed much, i've tested locking BLMs and closed loop enable/disable etc while disabling cylinders

[kur4o]

I noticed it is 0 to 7 in hex.
What happens is zeroing one of these hardware addresses which are responsible for individual inj bpw.
Likely they are tied to firing order.

RESERVED:1420 word_1420: fdb 0 ; DATA XREF: __RESET-46F8w
RESERVED:1420 ; __RESET-4696w ...
RESERVED:1420 ; INJ 1 TPU ADDRESS
RESERVED:1420 ; bpw loaded from STARTUP bpw
RESERVED:1420 ; if threshlod not reach use 0
RESERVED:1422 word_1422: fdb 0 ; DATA XREF: __RESET-46F4w
RESERVED:1422 ; __RESET-4692w ...
RESERVED:1422 ; INJ 2 TPU
RESERVED:1422 ; bpw
RESERVED:1424 word_1424: fdb 0 ; DATA XREF: __RESET-46F0w
RESERVED:1424 ; __RESET-468Ew ...
RESERVED:1424 ; INJ 3 TPU
RESERVED:1424 ; bpw
RESERVED:1426 word_1426: fdb 0 ; DATA XREF: __RESET-46ECw
RESERVED:1426 ; __RESET-468Aw ...
RESERVED:1426 ; INJ 4 TPU
RESERVED:1426 ; bpw
RESERVED:1428 word_1428: fdb 0 ; DATA XREF: __RESET-46E8w
RESERVED:1428 ; __RESET-4686w ...
RESERVED:1428 ; INJ 5 TPU
RESERVED:1428 ; bpw
RESERVED:142A word_142A: fdb 0 ; DATA XREF: __RESET-46E4w
RESERVED:142A ; __RESET-4682w ...
RESERVED:142A ; INJ 6 TPU
RESERVED:142A ; bpw
RESERVED:142C word_142C: fdb 0 ; DATA XREF: __RESET-46E0w
RESERVED:142C ; __RESET-467Ew ...
RESERVED:142C ; INJ 7 TPU
RESERVED:142C ; bpw
RESERVED:142E word_142E: fdb 0 ; DATA XREF: __RESET-46DCw
RESERVED:142E ; __RESET-467Aw ...
RESERVED:142E ; INJ 8 TPU
RESERVED:142E ; bpw


When applied AFR mode 4 requests are disabled. And absolute 0 degree spark is requested through mode 4.
So AFR and Spark won`t work.
Other things may not be affected. I didn`t have the time to investigate deeper.

[kur4o]

If my cylinder numbering is correct the order will be

Actual_cyl_nub = M4 command
4 =000
3 =001
6 =010
5 =011
7 =100
2 =101
1 =110
8 =111

[steveo]

AFR by nature can't work at the same time, since they use the same mode4 byte to select cylinders and afr

And absolute 0 degree spark is requested through mode 4

can you post the disassembly for that? my test logs show otherwise. disabling and enabling cylinders shows no more than 1 degree of spark variance, also i don't have any other evidence of absolute spark advance being zero (for example, zero spark advance at idle should cause a huge increase in MAP and i'm not seeing it)

[steveo]

If my cylinder numbering is correct the order will be

Actual_cyl_nub = M4 command
4 =000
3 =001
6 =010
5 =011
7 =100
2 =101
1 =110
8 =111

i think we need to confirm with a noid light who is correct

my car is down right now but i'll try to check soon

my theory:

0=1
1=8
2=4
3=3
4=6
5=5
6=7
7=2

your theory:

0=4
1=3
2=6
3=5
4=7
5=2
6=1
7=8

[kur4o]

I overlooked it again.
You get absolute zero degree spark if option Tside byte_2026 $04 =1 [It is also used for mode4 timer settings]
Default for all the bins I checked is zero. So I guess it shouldn`t be a problem.

[kur4o]

In the dissasembly they are transferred that way with some small offset.
If I have numbered the cylinders correctly[ I think i used one of the tc tables for ind cyl bpw corr] It will be that way.
It will be great if you can confirm the order.