NefMoto

Hey gents. Need to share a story some may relate to.

So I bought a 2000 Audi A4 1.8t ATW 150 HP, and with the help from here was able to improve the bin, remove loads of unnecessary stuff and made the car perform better than it had in years.
Jump ahead two years, give the car to my son. He takes it in for the clean air test, due on my upcoming birthday, and it fails. Seems the cat monitor is disabled now and the clean air machine knows it.
So now, I need to relearn how to read my bin, re enable the cat monitor, or restore to a stock ATW bin, if they exist anywhere.
Still can open nefmoto, found my saved bin files but cannot remember which ME7 Mem layout to use.
Ideally I'd like to just retweak the existing bin to pass clean air, but am damned if I recall how I did it two years ago.
Anyway, write stuff down! That's the moral of my story gents.
Any help re the above would be appreciated.. ribbing for getting old, expected.  Lol..
Cheers.
Mike.

IIRC the memory layout is 29f400 :)

This might help:
http://nefariousmotorsports.com/forum/index.php?topic=615.0

Hey Kasper, thanks. That helps a lot.
Nice thing about re-learning things is it takes less time..
Connected nefmoto flasher with my ftdi cable to tha car, hit refresh, saw FT232R USB UART as my device, hit connect slow init,
Result "failed to read test echo from ftdi device. Make sure cable is in dumb mode and connected to the OBD port."
So, now to reread how to configure my obd cable again. Was hoping nothing changed but something must have.
Thanks again brother. Once I can copy my ecu file from the car I will check CDKAT and go from there.
Mike.

Well, reinstalled the ftdi driver to version 2.12.28 and it shows my cable as being serial port(com1)
I'm running Nefmoto 1.9.1.2, and have two cable choices, both of which says they supports premium features within nefmoto.
Still won't connect and get the echo error code and make sure you are in dumb mode.
I can read my obd from my alternate stand alone reader, but even though I get the light in the cable while connected, continues to get same connection error.
Same thing in vcds-lite, shows there on comm3 as pass through etc, but won't read or connect...
Reviewing the noob walk through again..
Sigh

Well, I was using the wrong laptop, hehe. I used an Xp laptop to flash the car and my win 7 rig to do my offline programming.

Ok, now I have read and saved my installed bin file using the 400bb mem lay out. A pop up appeared at the start saying the mem layout appeared invalid, but the file transfer was successful.
Can't remember if I saw that message two years ago... is that a worry?

Now I'm running a compare in tuner pro and see my cat monitor cdkat is, as expected, set to 0. Deleted sai and a bunch of other stuff back when, so now I'm hoping just to reenable cdkat and associated post cat sensors and pass clean air with minimum mods.
Cat monitoring is what the test failed for at the ministry, so that's where I am going to focus..
Cheers, and thanks.

Any idea what was wrong with the wrong laptop?

The win7 laptop didn't have the proper ftdi drivers, I presume.
Nor a copy of vcds, just vcds lite and I couldn't force the cable into dummy mode.
So happy I still had a connecting xp rig I didn't spend too much time trying to ascertain what was going wrong on the newer laptop. Think deleting and reinstalling all the latest versions will be in order over the holidays.

Checked the bin pulled out of the Audi and yes, I've disabled cat, post cat o2. No wonder it failed the clean air test.
I need to find a happy medium between stock and what I was running as there is no more sai, but there is still a cat and an o2 sensor etc installed in the car.
Want to ensure in two years my son won't be facing the same reflash issues.
BIN comparison is a great feature In tunerpro I am rediscovering this weekend.
:)

Here's my code status currently, post reflash.
Now to see if I start throwing codes again once the required number of restarts has been made.
Red means still testing, yellow means not supported on my app.

Bad news update.
Threw a code P0411 for the secondary air.
Tried to change CDSLS to 0 to disable secondary air monitor. Checked bin with me7corrector,  o errors found. Connected with nefmoto, reflashed, disconnected after success. Started and ran car once. Shut off, now won’t restart, just turns over. And nefmoto will not reconnect?
WTF? Have I bricked this thing somehow?
Everything seemed to look proper...
Please help with any suggestions from your 3xperience. My boys gonna be some mad at his dad as he works midnights this week..
thanks guys.

If I somehow checked the wrong bin with me7 and flashed a bin with checksum errors, would it still run through a rewrite without errors and allow the car to drive once before locking up?
While it was running that first time I was able to connect my wireless dongle and read the new diagnostics as I did in the above picture. It did show secondary air not supported. But then like I said. I shut the car off and now it will not restart or allow nefmoto to reconnect. Fails at address 0x01 three times repeated, then goes back to stand by.
Now that it won’t start, the WiFi dongle no longer connects either. Really believe I somehow installed a bin file with checksum errors by mistake. Too many versions open at the same time I guess. That would explain why nothing connects, or starts anymore.
Now to relearn how to flash in boot mode, or if it can be done while still in the car,etc. dang it.
Thanks in advance for some suggestions.
Mike.

My specs are:
2000 Audi A4 B5 1.8T ATW 150 hp 4B0906018P 0261206537 1037352750 .bin
I never had this one bricked so am not sure of which pin needs to be grounded to force boot mode, while still in car. Presume the ecu is under the windshield like on the Jetta at this point.
Then I will use nefmoto to reconnect I presume? as I start to relearn all this stuff in a hurry.
 
I’ve only flashed one ecu in boot mode on the bench so would really prefer to do this one in car I think. And that was over 4 years ago.
Cheers, and thanks.
Mike.

As far as i know, galletto 1260 cable/software can do boot mode while in car.
But i might be wrong?

The other option is to remove ECU and open it.
It should be pin 24 on the AMD 29f400 chip :)

Galetto 1260 and cable can boot in car? That may be the ticket.
Thank you Kasper.
This pc doesn’t have galetto on it it seems, but was the one I used when I boot flashed an 02 1.8t out of a Wolfsburg Jetta a few y3ars back.
Wondering out loud how I boot flashed 8t back then..
Is Galetto available like nefmoto?
Regards.
Mike

I’ve installed Galetto 1260 successfully and hesitate now to remove all my ftdi chip drivers.
From what I’m reading galetto may have a conflict with the ftdi chipset and require all existing drivers to be removed.
Think I will actually install galetto on my win7 laptop as it wasn’t working with the ftdi dongle anyway. That way, once unbricked I can reuse the space machine to further diagnose what went wrong on my last flash as after all this, I still need to get the car to pass clean air..
Will be reading lots more tonight I think..
Thanks again.

Galetto is premium software/cable.
But there is "cracked" software iirc.
And you can flash a kkl cable to work with it :)

I have installed 1260 and re serielized my ftdi cable to match via mprog. Thanks to ddillenger’s walk through for help with that.
Now when I start galetto, without being connected to the car and plug in the ftdi dongle it asks me to install drivers, which I do from galetto, I now see an ftdi ft8u2xx device in device manager. All good So Far?
Next I run galetto and get to the main screen.
It says connected at the top mid screen.
Manufacturer: Audi
ECU: Audi VW ME 7xx29f400bb (ground pin 24)

But there are other ecu choices. Under Benzina there is another Audi 29f400bb, but without saying ground eeprom.
My question is which one will allow rewriting without forcing boot mode?

And do I simple rewrite using galetto with the last known good bin file like I would with nefmoto?
Sorry for asking all this, but I have found only tertiary walk throughs for galetto so far tonight and am getting a little cross eyed..
Leary of plugging the laptop back in until I know a bit more about using galetto..
Thanks.

Is there a specific reason for not wanting to remove and open ECU?

Only that it’s untouched. I was able to flash this one with nefmoto originally and every time, right up until I flashed yesterday’s that failed.
I will try to reflash in place today with Galletto. Assuming the non boot mode ecu selection is the one to try first. Was reading and reviewing late last night.
Failing that, I will pull trim and try to gain access to it properly to ground the pin..
Need to get this thing running again..
Thanks.

Ok, galetto shows connected at the top of its window,  not device active as I see on some walk through videos.
I select read ecu it tells me to cycle ignition which I do, then galetto hangs. Get the hour glass, but no percentage of read occurs. Wait a few minutes, nothing changes. Have to power down the laptop to recover.
I’m going to pull my ecu covers off and try to boot flash it.
I was hoping to verify connection via the dongle, communication wise before committing to pulling the ecu covers but maybe it is hanging because of the corrupt bin file currently installed?
As mentioned, I have installed the drivers that came with galetto to my laptop, and changed the serial number of the dongle to match galetto.
When I start the galetto program I get the ‘connected’ message at the top, whether the dongle is connected or not, so I am still not sure I have an actual connection to the car..
Thanks.

Just thinking out loud still, but if I was to pull an ecu from a 2000 similar ATW car, would it be plug and play or did the 2000s have the IMMO and security features as well?
Once I have an accesssible ecu, I will be able to recover with nefmoto, it’s the boot mode issue that has me stymied at the moment.
Thanks gents.

Pulled my trim and popped the cover to access the ecu. Wasn’t as hard as I feared.
Now to pull the battery neg, get my jumper all set up and force boot mode.
From more reading I have seen some use nefmoto to check connection after getting into boot mode. Then they run either galetto or MPPS to perform the flash.
I have both installed but have not run either successfully before.
The dongle I use for nefmoto is a vag-kkl but the one I reserielaized is a different dongle so as to not spoil the settings on the one that worked wit nefmoto. It’s still an ft232r chipset, just a different cable.
How can I validate obd connection prior to committing to writing the bin once in boot mode?
Thanks gents.

To test my lead(s) I connected nefmoto to my converted Corrado and was able to read the ecu with both cables.
The Kkl cable showed as a ft232r  device and the one I reprogrammed with the galetto s.n. shows up as a usb<->serial cable within nefmoto.
Both were able to successfully connect in kwp1281 and kwp2000 sessions.
So I believe that I should be able to connect with galetto but am still not sure why it hung the first time I tried to connect it to the bricked ecu, unless due to the corrupted file it hangs unless I’m in boot mode..
Hope this ongoing relearning dialogue helps others. I am a big advocate of follow up on tech boards and try to share my failures and victories along the way.
Cheers, and thanks for any tips from those experienced with these self inflicted woes..
Mike.

You are correct. Galleto will hang if you aren't in bootmode. Its happened to me before. You are really close now, flash away once you get bootmode.

Audi runs once more..
Thanks gents. Back to a working bin file.
Now to hopefully remove the sai code that started this whole saga. One more day in November to get my clean air done
 Not sure if the 2000 has MSLUB (0x1A698), and MSLBAS (0x183CC) to rewrite to 0.
Think if I just force CDSLS to 0 it’ll show unsupported and that could still cause a failure.
Worst case, I time my inspection between cat passing and while sai still shows not ready.
Think you can have two not ready and still pass..

Thanks again for following along.
Cheers..