RomRaider

Im using USB KKL VAG 409.1. As i wrote Nissan datascan 2 is working with this cable in com09.

to see a list of ports and make sure COM9 appears in there and you're writing it the same way. Also, can you translate the "open failed" error message.

Start any multimedia application in order to set applicable system timer period.

I connected successfully, worked with COM9 and with media player in the background.



Dumped a very small bin file, with only a few lines inside. Is it good? Should i use another kernel? When I open the .bin file with wols its still a very few curves.

When im trying with another kernel this is what i get:



Thank you for the help guys

Hello, newbie here.
I searched for "VAG-COM KKL 409.1 Cable" but there are different models has different chips. I'm a bit confused
Then I searched for chip based cable and check some comments about it. Some says CH340 is better, other says FTDI (FT232RL) better.
Whichone should I buy?

I have 2012 D22 NP300.

The one I bought was described as "FTDI FT232RL Vag com Kkl 409.1 OBD2 K-Line KWP2000 Iso9141 USB for Vw/Audi" but came with ch340 drivers... They're all chinese knock-offs so you'll just have to roll the dice. I've had no issues with mine.

Your 2012 still has K-line?

You need set actual for your rom AU360
setkeys 0x90FD3C82 0x277D374C
and try again runkernel npk_sh7055_18.bin or _35.bin

So they doesn't have any difference between FTDI & CH340x chip.
And I really dont know the answer of this question Do I have K-line on my D22?

Solved my problem, the dump was limited into 1kbyte.. Now i can download the full dump from my ecu, but it is very very slow. It takes one and a half hour, i had to stop it after 10 minutes.

Is there any way to dump faster?

How much time are you going to spend for ecu tuning in total if an hour and a half is an obstacle ?

CarlosGambino, you already use kernel?

I have the message:
"kernel not initialized - try runkernel..."

But it still downloading the dump.

This is my nisprog.ini :

set
interface dumb
port \\.\COM9
dumbopts 0x48

#sorry, you still need these
l2protocol iso14230
initmode fast
testerid 0xfc
destaddr 0x10
addrtype phys
up

#connect to ECU
nc

#optional, if your ECUID needs special keys (let me know if this happens !)
#setkeys 0x90FD3C82 0x277D374C

#try "setdev ?" to see choices, i.e. 7055 / 7058
setdev 0

#some extra parameters if you're having timing issues (frequent read timeouts etc)
#try "npconf ?" to see list.
#Setting P3 to 0 usually works well and makes comms faster.
npconf p3 0

#if you're having read/write errors and playing with some npconf parameters doesn't help:
#try changing the kernel comms speed. By default this is 62500bps.
kspeed 31250

runkernel npk_SH7055_35.bin

#dump command, uses regular fastdump or npkern fastdump if available. Syntax is "dumpmem <file> <start> <len>"
dumpmem asdf.bin 0 1048576
#shorthand , same thing:
dm asdf.bin 0 1048576

- why have you commented the "setkeys" line that pirelli2006 gave you ? of course runkernel isn't going to work.
- why do you have two dumpmem lines ?
- why are you setting kspeed, if you haven't even been able to get the kernel running ? start with te default settings. Don't touch kspeed.

When I enabled setkeys i got a bunch of error codes, but i will give it a try now.
Deleted the two dumpmem lines and speed set back to default. I didnt noticed this before.

Thank you

Yesterday successfully dumped my rom thank you guys.