NefMoto

Noob issue I suppose
Trying to connect to a 8e0 909 518af that i had in the garage,,experimenting until I figure out what im doing with this.
Bench wired a battery with a trickle charger, power is ok
B+ connected to pins as described in the guides,3,21,62 and added + to pin121 as well
grounds to cable and pins 1&2 ecu
added - connection pins 4+5 on ross cable
Using Ross HEX-CAN cable, powered, and grounded on the proper pins,,works fine with ross software.
Tried connecting to my daily,,ross worked, This does not.
It does appear in the line on top right, and have set to dumb mode .
Maybe I need another cable?

More info on cable.. what does it look like in device manager?

Tried updating driver, said it already was up to date.
Connects fine in the same port I always use for Ross
Does not have a flag in device manager

I can't tell what you are saying works and what does not

The one ecu works but another doesn't? One cable works but another doesn't? One program works but another doesn't?

 Ross Tech works fine in the car
Nef software will not connect,,get could not open ftdi device, also in car, and on bench,,ross connected on bench and in car
Tried all different baud rates, fast and slow init, and boot mode

both ecus connected to ross software, one on bench, one in car

Device manager says its a ch340 or the likeness. I did read some threads on here stating that nefmoto does not support that chip which if this is the case I'm not going to be very happy that I purchased this off a reputable website in which I trusted would be selling a legit cable for my car. Which by the way is a 2000 usdm b5 s4 6mt. Or am I wrong? I just went at it again tonight for another hr or two trying to get this thing recognized and still to no avail? Not ony did I buy this off a legit performance website I also bought a $99 licence from ross-tech for the lite version. $175 bucks in and I'm still banging my head

I looked through the details in device manager and did not see anything like ch340, suppose its the ross interface.
KKl blue cable is $13 on amazon,,which a lot of users have success with,,,ordering today.

thanks for your input

"legit" or not means nothing. you have to ask before you buy it which chip it has.

Im not so good at forums but I'm adding my resolution to my issue.
There is so much information here its hard to find exactly what you need,,its ok,,Ill find it.
My Ross cable was the problem,,hex-can,,possibly boot leg,,but worked fine with my registered ross.
I bought a KKL cable from ebay,,came with a cd/dvd with a lot of crap on it,,just extracted the drivers.
Didnt work on my bench rig,,,still working on that,,will go to a salvage yard and cut out a DLC and harness,,re do it,,and see the results another day
I connected it with success to my daily and extracted the base files from that ECU.
Im on my way

Just have to find all the info I need , I am persistent

Thanks for the guidance

The cable appears ;
FT232R USB UART
Same as I have seen in some of the guide pages.

That cable should definitely work with Nef.

Any luck getting ME7Logger working with it?

I have not tried it with the logger.
Intention is to study and learn the system functions, editing, remove IMMO on a 01 TT225 I just got (bad cluster)
So far have pulled the .bin on my daily, 03tq,,think I found a xdf thats close,,,I also found your xdf on the wiki which has a lot more info than what I found.
Still playing with changes, and getting the checksums correct, will be a while before I am ready to try flashing..
Bench rig still not working with a spare I have,,might be a brick,,will try in boot mode and see if I can connect to it.

Thanks,,great project you have here.

My next step will be writing my own xdf for my daily,,cant find everything I need by searching the pages here for my ecu. Steep learning curve.
Goals are for SAI and downstream 02, I have a 3 inch down pipe and sensor spacer,,fooling it for now,,that stuff is easy to find..cmd prompt check sum corrector is challenging, ill figure it out.

make sure you install the oem FTDI drivers directly from ftdi, not the drivers that came with the cable.

I did install the drivers that came with it.
I went to the FTDI link and verified it was the most recent driver;
2.12.28.0
I replaced it with the driver from their pages, it works fine
working on my bench rig,,got it to read ecu info,,immo blocking the download
now I am working out cmd to delete the immo,,,its a spare ecu, if I brick it, oh well
I will figure it out, and will spend the time.