flaattire
Full Member
Karma: +2/-0
 Offline
Posts: 68
|
 |
« Reply #510 on: November 06, 2014, 04:04:49 PM »
|
|
|
Great, I look forward to trying it out.
|
|
|
|
|
Logged
|
|
|
|
Nottingham
Full Member
Karma: +13/-1
Offline
Posts: 204
|
|
« Reply #511 on: January 08, 2015, 02:37:02 AM »
|
|
|
Any idea why it is still impossible to read over 2550mbar actual boost with 3 bar map sensor?
DSVDRGRAD & DSVDROFS are set to correct values, yet VCDS still reads 2550mbar max during spikes.
Any other maps besides those two?
|
|
|
|
|
Logged
|
|
|
|
|
dream3R
|
|
« Reply #512 on: January 08, 2015, 03:21:35 AM »
|
|
|
you need to look at the assembly and FR. pvdr_w should give you what you need  |
|
|
|
|
Logged
|
|
|
|
Nottingham
Full Member
Karma: +13/-1
Offline
Posts: 204
|
|
« Reply #513 on: January 08, 2015, 05:38:13 AM »
|
|
|
So is the variable VCDS is reading still 8-bit (i.e 255 factor 10)?
That would mean the 3 bar map is only needed for ECUs internal calculations and useless for logging without tampering with the RAM variables.
|
|
|
|
|
Logged
|
|
|
|
|
dream3R
|
|
« Reply #514 on: January 08, 2015, 06:26:11 AM »
|
|
|
That's why you need ASM. VCDS is probably still reading pvdkds_w or something.
In ME9 pvdr_w get converted to pvd_w then onwards (doubled) to the 2550 limited vars.
There's notes on here to get the blocks to measure what you want I think.
Another idea is can you log the sensor voltage? If so you can work out the boost value fairly easily.
|
|
|
|
|
Logged
|
|
|
|
|
RaraK
|
|
« Reply #515 on: January 08, 2015, 06:42:45 AM »
|
|
|
Just edit your VCDS measuring block lookup for reference pvdr_w.
GolfR will have this setup stock, so use that to reference.
This is only for ACTUAL boost in vcds. ASM required to make REQUEST read higher.
|
|
|
|
|
Logged
|
|
|
|
|
|
|
RaraK
|
|
« Reply #517 on: January 13, 2015, 08:04:54 PM »
|
|
|
worded that wrong, asm required to request higher than 2550 and also display higher than 2550 in vcds  MED9 does have the same limits as ME7 in that respect. |
|
|
|
|
Logged
|
|
|
|
P0nder
Newbie
Karma: +0/-0
Offline
Posts: 4
|
|
« Reply #518 on: January 15, 2015, 11:54:48 AM »
|
|
|
This forum is extremely helpful and full of great guidance. I'm stuck with a few MED9 queries which I'll post up shortly as I am trying to understand it over ME7  Would reading an ori/mod file from one MED9 ECU via OBD and flashing to another have any immo/vin conflict? The version in discussion is 1K0907115H with HW and SW numbers being exactly the same. Reason for this is to compare two vehicles to eachother, with 65 000km difference on the engines |
|
|
|
|
Logged
|
|
|
|
|
ddillenger
|
|
« Reply #519 on: January 15, 2015, 12:29:33 PM »
|
|
|
No OBD writing modifies the boot sector of the file, which is where the immobilizer data is stored, so as long as you are doing it via OBD, you're good to go!
|
|
|
|
|
Logged
|
Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!
Email/Google chat:
DDillenger84(at)gmail(dot)com
Email>PM
|
|
|
P0nder
Newbie
Karma: +0/-0
Offline
Posts: 4
|
|
« Reply #520 on: January 15, 2015, 12:34:40 PM »
|
|
|
Thanks for that
1. So I simply read the mod file from my car and flash it onto the other? You say it modifies the boot sector where immo data is stored, how would this work on another car then?
2. Manual or DSG makes no difference?
|
|
|
|
|
Logged
|
|
|
|
|
ddillenger
|
|
« Reply #521 on: January 15, 2015, 03:50:56 PM »
|
|
|
Thanks for that
1. So I simply read the mod file from my car and flash it onto the other? You say it modifies the boot sector where immo data is stored, how would this work on another car then?
2. Manual or DSG makes no difference?
I said OBD does NOT modify the boot sector. No OBD writing modifies... Not No, OBD writing modifies |
|
|
|
|
Logged
|
Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!
Email/Google chat:
DDillenger84(at)gmail(dot)com
Email>PM
|
|
|
P0nder
Newbie
Karma: +0/-0
Offline
Posts: 4
|
|
« Reply #522 on: January 16, 2015, 12:22:08 PM »
|
|
|
Ah Thank you Any difference between manual and DSG on the ECU file? |
|
|
|
|
Logged
|
|
|
|
|
ddillenger
|
|
« Reply #523 on: January 16, 2015, 01:12:11 PM »
|
|
|
Ah Thank you Any difference between manual and DSG on the ECU file? Depends on the file. |
|
|
|
|
Logged
|
Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!
Email/Google chat:
DDillenger84(at)gmail(dot)com
Email>PM
|
|
|
flaattire
Full Member
Karma: +2/-0
Offline
Posts: 68
|
|
« Reply #524 on: January 16, 2015, 09:25:14 PM »
|
|
|
With KFFDLBTS set 0 and KFLBTS set 1 across the board, is ALL protective fueling and related intervention disabled? TABGTS / TAVVKBTS are not defined or obvious in my binary so are unavailable for modification until I can disassemble and analyze the file.
I'm fueling through LAMFA and have good EGT at idle / cruise / WOT with manual probe, but unable to boost over 18 max / 12 redline--the ECU never requests more than these levels even though KFLDHBN, LDRXN, IOP, IRL allow it and timing is adjusted for no pull at WOT. The hardware / N79 is leak-free. The downpipe is 3" catless. My PID / WG maps are dialed in well with stock-like actual / specified boost behavior.
From what I've read this boost restriction could be due to (BTS?) intervening for high calculated EGT. Does this sound like it could be the case?
|
|
|
|
|
Logged
|
|
|
|
|
