EFIDynoTuning Forum

That means the tune file is corrupted not the QH, most likely the datalogging patch got overwritten when you wrote it with BE.

Write the tune with tunerpro and then read it back out and post it in your thread i'll take a look.

decipha wrote: ↑2024 Jun 11, 06:42 That means the tune file is corrupted not the QH, most likely the datalogging patch got overwritten when you wrote it with BE.

Write the tune with tunerpro and then read it back out and post it in your thread i'll take a look.

//Attached files
This is how i did

1- Removed the qh from the car
2- plugged to my computer and opened binary editor
3- cleared ram
4- closed binary editor
5- opened tunerpro rt and loaded my .bin tune
6- wrote to chip and closed bin in tunerpro rt
7- clicked download bin from emulator to file and saved as "luis save to.bin"
8 - loaded the tune again and verified ram
9- closed bin again
10- clicked download bin from emulator to tunerpro rt
11- verified ram
12- at the top left clicked "File" then "save bin as" and named it "luis save as"
13- Exit tuner pro rt and unplugged the qh
14- installed qh to the car
15- constant fan and fuel pump

update: still no success.

found on my garage two spare eec I had, one t4m0 and another u4p0.
Plugged the t4m0 eec and car started right of. Then I removed it and cleaned the j3 port to install the qh in.
Loaded a stock t4m0 bin and got the constant fan, tried with BE and worked fine.

Plugged the u4p0 eec and the car got constant fan (qh unplugged), then I removed it and opened to see the inside and the two SMD capacitors were fried so I replaced them with regular capacitors of the same value, car started right of.
Removed it again and cleaned the j3 port.
Reinstalled it with the qh in, loaded my u4p2 tune and got the constant fan.
Just to be sure I loaded it with BE and worked fine.

At this point I think its more like a QH issue where mode 4 (default) is corrupted or something. Wonder is there a procedure to fix this up

just a shot in the dark, but I would try writing a bin file full of FF from binary editor and then try writing the correct bin from tunerpro.

efloth wrote: ↑2024 Jun 18, 12:11 just a shot in the dark, but I would try writing a bin file full of FF from binary editor and then try writing the correct bin from tunerpro.

What do you mean with full of FF? thanks

Attached: These are not programs, just files filled with hex value FF. I'm not sure if BE uses 56k or 64k files so choose the appropriate option.

64kb file is wrong size

you need to read the qh file out not download from emulator, read from emulator to tunerpro

regardless, it sounds like you don't have the correct GUFX xdf loaded in tunerpro.

what are the 3 file revisions loaded in to the top of tunerpro?

Tried writing the 56k bin filled of FF with BE, of course as expected the car ran the fan continuously, then wrote with tunerpro a fresh download stock u4p0 bin from the downloads section with fresh download definition.
same issue.
then I did download from emulator to tuner-pro then save as. (Attached the file)

upper 3 files are: U4P0_Stock.bin | XDF File - CBAZA_210126.xdf | ADX File - DECIPHA_210225.adx

Next thing I'll try is buying another used gen 2 QH from facebook.