pcmhacking.net

Tre-Cool wrote:Can you add the T43 controller, even if experimental and I'll try a few reads. can do on bench and in car.

also does anyone have an e67 bin file from a LSA motor?

just tried to read an e38 with a hpt custom OS:

[03:53:50:538] Operating System: 1250232
[03:53:50:540] Unsupported Operating System currently on ECU or does not match loaded file ECU type. Write routine cancelled (No programming has occurred).


Can't write over it at all.

Cant really work out what to do for the T43 without knowing the memory thats in it. Ill need to pull the GM kernel and see what it does as thatll give some clues.

As for the OS, assuming they havent messed with seg structure, should be able to read and verify file fine after adding its OS ID to supported list. I can make a quick edit if your up for testing that custom os ECU?

I pulled the tune out with efilive to see if it was an auto/man cal then overwrote it with the factory os.

I did pull the file with efi, so can technically write it back.

Factory OS based off vin was 12639270

I thought you worked out the memory etc was the same as e38 ecu?

Tre-Cool wrote:I pulled the tune out with efilive to see if it was an auto/man cal then overwrote it with the factory os.

I did pull the file with efi, so can technically write it back.

Factory OS based off vin was 12639270

I thought you worked out the memory etc was the same as e38 ecu?

It has the same processor based on the T43 bin, and size is the same as the E38bins (2Mb).. but dont actually know what exactly the chip is, if that makes sense?

I've tried to read 2 ecus in cars over the last couple days. Both times it killed comms with the E38's. I had to disconnect the battery and both came back to life, phew!!!
This was with the Ford VCM2 that I've done the 3 bench recoverys with.

Downloading the new version now.

julespatch wrote:I've tried to read 2 ecus in cars over the last couple days. Both times it killed comms with the E38's. I had to disconnect the battery and both came back to life, phew!!!
This was with the Ford VCM2 that I've done the 3 bench recoverys with.

Downloading the new version now.

Does it finish the read or even start it? Or what happens?

The kernel uploaded will stay running until told to exit or power down/up.

It tries to start but doesn't get any further. There's no comms and no start until the battery is disconnected.
2012 SSV
2008 SS
I'll give it another go tomorrow and save the logs when there's no audience or pressure lol

julespatch wrote:It tries to start but doesn't get any further. There's no comms and no start until the battery is disconnected.
2012 SSV
2008 SS
I'll give it another go tomorrow and save the logs when there's no audience or pressure lol

Haha, no problem. Worked fine in my VE SS when I tried, Ill try again tomorrow.

Ok, It did struggle a couple times trying to start sending the bootloader in my ute. It did do it but not everytime.

Issue appears to be I didnt wait long enough for all modules in the car to respond to the setup commands and then begin. I have now added a 500ms delay between each setup command and that seems to have solved it. Was able to read/write without problems.

Will update to v1.0.4.x later tonight which will have that change.

Hi Tazzi,
I have seen some really long(relatively) response times here with the US cars. Maybe make a flag setting in software to allow a full 2 seconds, or longer, between modules for reply? I have seen ~10 seconds before the car was ready. The newer e92 stuff can take even longer with wifi, bluetooth and other stuff I don't know is going on in the background. Truly, waiting 30 seconds or longer for the car to "stabilize" doesn't bother me at all as it's still a lot shorter time than doing a hard boot of the car.
My dos centavos.

Tested quite a few times in car, seems the extra 500ms made the difference.
Also monitored and watched SPS in car, and seems it gives a good buffer time between commands as well to ensure everything has responded