new $EE tuning thing!

[steveo]

thanks, i'll fix that. i found the problem, i was reading this chart from the bottom up; and it's in a strange order. i'll assume that broke my shift selector since they use the same bits afaik

              SHIFT B  SHIFT A  GEAR
              ----------------------
                0        0       3RD
              ----------------------
                0        1       4TH
              ----------------------
                1        0       2ND
              ----------------------
                1        1       1ST
              ----------------------

[steveo]

i posted a fix: http://fbodytech.com/3-6-beta/

there are some other changes too, you'll have to download updated libraries to use this version.

[steveo]

yet another beta, major display performance increases as well as a facelift, bunch of other little stuff.

i actually bumped the version to 4.0 since there's a ton of changes.

it's looking good

please help test, will release soon

http://fbodytech.com/3-6-beta/

[kur4o]

I do some test today with the earlier version. All works fine. I tested the speed writing but when I read it it looks like regular version of the bin with no ff added. Is it normal behaviour or It`s my mistake(I am not quite sure what i did, and checked the bins later). I tried to flash the same bin but the write buttons are greyed out and couldn`t force patch only write with identical bins.

Also the last figure of the Vin is missing and can`t be written.

In the mode1 msg 0 there is one more free byte to add. I suggest you load there byte_011E which is the ad channel for pin d31 and that way you can have true dual wideband setup with pin d27. Both pins are configured the same on the board and will output identical ad result.

For the tcc there are different setups in 94 and 95 bins. 94 is only tcc lock, 95 adds tcc dc control.
I will check the commands and post them later.

What byte in the datastream is d31?

You need to patch it in the datastream to show up. It is at byte_11e
Can you add the aldl data in the modified xdf you are working on. I will really appreciate it.

[steveo]

I do some test today with the earlier version. All works fine. I tested the speed writing but when I read it it looks like regular version of the bin with no ff added. Is it normal behaviour or It`s my mistake(I am not quite sure what i did, and checked the bins later). I tried to flash the same bin but the write buttons are greyed out and couldn`t force patch only write with identical bins.

if you have an auto+maf bin, right now, it doesn't 0xFF anything out. i'm going to add more unused regions later. speed writing still helps a bit if it lands on a 0xFF it just skips ahead in the bin.

the way i chose to do patch insertion in $eehack is passive. it wants you to feed it an un-patched bin. it patches it in ram and flashes it. notice there's no 'save' button for patched bins. it will refuse to write bins that have already been patched, and expects the tuner to keep track of his own bins.

there's two reasons for this:

1. patching is 100% transparent to the tuner no matter what happens, any $ee tunerpro xdf or tunercat definition will work. eehack is not bin editing software, so it must not break compatibility, and i dont want users to have to worry about how my patches work.
2. i plan to do some table relocations in the future, which could further break existing XDFs if you read those bins and try to tune them..passive also seems the way to go here..

Also the last figure of the Vin is missing and can`t be written.

thanks i'll fix that!

[steveo]

i actually might remove the ability to read a patched bin from the ECM unless a debugging check box is set.

[kur4o]

00 00 00 00 02 00 00 00 00 00 00 00 enable tcc pwm valve control or rev inh load 00{94} or CA{95} for dc
00 00 00 00 02 02 00 00 00 00 00 00 enable tcc pwm valve control or rev inh load ff{94} or 63{95} for dc
00 00 00 00 01 00 00 00 00 00 00 00 enable tcc lock -tcc unlock
00 00 00 00 01 01 00 00 00 00 00 00 enable tcc lock -tcc lock

That should do it for the tcc control

[jthompson122183]

You need to patch it in the datastream to show up. It is at byte_11e
Can you add the aldl data in the modified xdf you are working on. I will really appreciate it.

Well I have no problem adding that in , but I'm not sure which values need changed and to what.

[kur4o]

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.

[fbody_Brian]

Congratulations Steveo

You have managed to make an app that flashes LT1 PCMs natively under linux.



Flashing worked for me, no errors, everything went perfectly. The app looked just like the win version during the flash, going full screen, etc.

all I can really say is HELL YEAH!!!

[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