xHP DCT Flashing
- Thread starter doublespaces
- Start date
i never timed the full flash in WINKFP but 10 mins sounds familiar so you could be right about flashing back to stock
My experience was that the shift points were slightly higher across the board, less hesitation when taking off from a roll (before it would disengage clutches when rolling up to a junction and get confused) and less delay with selecting reverse. Shifts were crisper too.
Another user (Asbjorn) who did the same change also had the same feeling. He would get flywheel chatter in higher gears with the standard 35i flash because of installing an aftermarket flywheel, he said this was greatly reduced with the 35is flash because he felt it held gears longer.
Agree, there are better things to spend that much money on unless you want it for a very specific purpose and have no swaps....at least until maybe custom flashes get dug into.
Thank you for that path. I had to search about 3 different keywords from it, but finally found it and does look like the stock/initial install file judging by timestamp. I flashed a flash change and re-downloaded, but it's still time stamped from the original setup.
If there's no way to readout what's actually flashed, we may want to start a repository of the stock bins somewhere. I haven't looked at the file yet, but if complete, at least they're something to reference/start from. The swap/non-stock ZB people need to get those files read out somehow and probably custom flash back instead of using their OTS/stock flash options...if it even accepts that. If they can do a full write, they should be able to a full dump, but yeah, they don't make it easy. Someone needs to talk them into reads, not downloads.
My flash only change took a little over 1 minute, but I was on the stock ZB. If you have something that isn't for your exact car flashed to start, it surely does a full write to get rid of it.
I was thinking the same thing about the stock map repo. I verified the stock map with the files from WinKFP and the generated stock bin contains the correct binary data from the 0pa and 0da files for the latest stock ZB of my car.
It should be fairly easy to record the xHP flash process using a CAN sniffer, saves the hassle of buying expensive hardware to upload from the TCU. An XDF for the TCU would be a lot smaller than the DME one and I think we would only be looking at three hardware variants that cover the majority of cars (F980G (E9x and E8x), F991G(Z4 35is), F111G (M3)). My theory is that those 3 variations are due to those models having different flywheel as the Z4 35is has a slightly heavier one I think. It would be a bit of an asshole move to steal their OTS maps but at the same time I'd like the ability to truly customise things.
The stock map generated by xHP is only 1.5MB and a full program/data bin should be 4MB so it's certainly only a partial data map. Could fill the gaps in from the WinKFP files though.
Can you even read their maps? I didn't buy a map pack and never will, but I'd assume they would be encrypted. Only a matter of time before XDF gets sorted and we can do everything ourselves though.
0-01FFFF are FF on the backup/stock ZB download, but there is data from 20000+. That is a huge diff in file size, but repository may still be worthwhile for the data that is available.
0-01FFFF are FF on the backup/stock ZB download, but there is data from 20000+. That is a huge diff in file size, but repository may still be worthwhile for the data that is available.
I thought you meant their actual OTS maps, sorry.
Check DME codes after. Had to run out, so flashed TCU back to stock to get some base line DME and DKG logs on current DME map. No light/issues, but all these were sitting there.
++++7/8/2020 2:26:57 PM
- DME active codes -
2E7F - DME: EGS via PT-CAN2 and PT-CAN.
2F81 - DME: Engine switch-off time, instrument cluster timer - DME timer, comparison.
2F83 - DME: Engine switch-off time, instrument cluster timer - DME timer, comparison.
CD9D - Message (transmission data, 0xBA) faulty, receiver DME, transmitter EGS/HIM/SMG/DKG.
CD9E - Message (transmission data 2, 0x1A2) faulty, receiver DME, transmitter EGS/SMG/DKG.
CDB0 - Message error (display, transmission data, 0x1D2), DME receiver, ETC / HIM / SMG / DKG transmitter.
CDB4 - Message (transmission data , 0x3B1) faulty, receiver DME, transmitter EGS/SMG/DKG.
CDC3 - Message (status, DKG, 0x37D) faulty, receiver DME, transmitter DSC/DKG.
- DME shadow (inactive) codes -
CDB8 - Message (torque request, DKG, 0xB8) faulty, receiver DDE, transmitter EGS/SGM/DKG.
but i see in a data it has e-brake option enabled. does brake - handbrake detection status working well in standart 335?
also, ZB is 8606066 its pre-latest PROGRAM code, but what is data file? i guess 8606076 Z4 35I roadster non china/korea or 8606082 Z4 S35I roadster non china/korea?
so it does not backup your current changes? any way to get modified file by Xhp?
so say me your stock data file version and attach that backup, please, did they compressed or masked it?
i have stock bins and can modify something for you, then you can try to replace bin and reflash, maybe it sign it on the fly, or signature protection already removed.
data file size from 0DA should be about 130kb - from offset 0x20000 to 0x3FEFF. and pure code from 0PA about 1.5 mb
Last edited:
Seems like you would have to look into some custom programming to get rid of the error checks. I'm guessing that it's just an error for the illumination? The selection is a different part of the harness if I'm not mistaken. Maybe you could look into pulling the wires and adding a little resistor set so it thinks it's lighting up. May be easier than the coding.
Or hang the knob down in the trans tunnel above the guibo
Seems like you would have to look into some custom programming to get rid of the error checks. I'm guessing that it's just an error for the illumination? The selection is a different part of the harness if I'm not mistaken. Maybe you could look into pulling the wires and adding a little resistor set so it thinks it's lighting up. May be easier than the coding.
Or hang the knob down in the trans tunnel above the guibo
I thought about hiding it in the dash, it throws a display code, unlock button malfunction and park button malfunction
Oooh those should be for the stock GWS I think. Are you reverting or did you never get your trans to flash back to GTS?
Fitted my stock GWS back to try the custom setting, but I'm waiting on another GWS with a Park cable and shifter knob.
So - im confused. Can one of the XHP users explain to me... The flasher module has sliders and you can tweak various parameters to suit your car. The OTS maps you pay extra for are these same sliders set different ways or do you get further functionality ? That is the flasher gives you shift points up to 7k but the stage 3 map gives 7500 for example I mean whats the use case for the maps other than its set and forget ?
It's weird, everywhere xHP states, even when asked directly, that the flashing wont work with other than OEM DCT cars. I can anyways identify my Z4 35is DCT in my old E36. I just don't dare to try flashing, because everyone says it doesn't work.
Someone who has flashed the xHP, does this look correct to you (VIN is hidden on purpose)? Next step would be to buy a license and flash away?
@doublespaces, here's one interested in the development (specially for aftermarket things), two projects going on at the moment, both E and F-series DCT:s going into old BMWs with a decent amount of power...
Someone who has flashed the xHP, does this look correct to you (VIN is hidden on purpose)? Next step would be to buy a license and flash away?
@doublespaces, here's one interested in the development (specially for aftermarket things), two projects going on at the moment, both E and F-series DCT:s going into old BMWs with a decent amount of power...
Similar threads
