mikeb52
Full Member
Karma: +0/-2
 Offline
Posts: 102
|
 |
« on: July 01, 2014, 10:48:14 AM »
|
|
|
Hey gents. Trying to learn this stuff such that I can rework a 20011.8t AWW into a 90 Corrado. Engine is in, and wiring ruffed into locations and I turned my attention to the Bosch 7.5 ecu. Purchased this. http://www.ebay.com/itm/271304445606?_trksid=p2059210.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AITTo do the ecu work and was able to use it on another, intact jetta via the obd2 port and vagcom 409.1 to reset some auto trans issues but it never ran auto scan successfully, coming back with to many comm errors.. When I installed the USB dongle, I didn't install anything beyond the little set up disk it came with. So now I want to read, and save my bin file to do the immo, sai, and evap deletes, if I can figure out how. When I connected with argdubs software, I get a cable error, no echo, etc and no luck. So I read more and see that you are maybe supposed to load specific ftdi drivers and such, so I install m-prog and try to read my cable. No good, and I'm left scratching my head.. Ordered another dongle. http://www.ebay.com/itm/281288095104?_trksid=p2059210.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AITBut I thought I bought the right one first.. Anyway, any tips, or links to threads I missed,, gratefully appreciated.. I read the wiki, I am a mechanically inclined guy, and I mistakenly thought the actual, physical swap would be the hard part.... This binary stuff is just, intangible to my old hands..and I thought I was a pc savy guy.. Thanks again. |
|
|
|
|
Logged
|
|
|
|
|
ddillenger
|
|
« Reply #1 on: July 01, 2014, 10:54:54 AM »
|
|
|
In device manager, under ports, find your cable. What manufacturer is listed in properties?
|
|
|
|
|
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
|
|
|
mikeb52
Full Member
Karma: +0/-2
Offline
Posts: 102
|
|
« Reply #2 on: July 01, 2014, 12:29:35 PM »
|
|
|
mfgr is FTDI. Location USB high speed serial converter.
Driver provider FTDI, ver; 2.8.30.0
|
|
|
|
|
Logged
|
|
|
|
mikeb52
Full Member
Karma: +0/-2
Offline
Posts: 102
|
|
« Reply #3 on: July 02, 2014, 08:11:39 PM »
|
|
|
So based on the info in device mgr, do I have the correct cable? Should I maybe pull off the cover and check the board? Are you supposed to manually add drivers.
Thx gents.
|
|
|
|
|
Logged
|
|
|
|
|
ddillenger
|
|
« Reply #4 on: July 02, 2014, 09:08:38 PM »
|
|
|
The cable appears right as long as it's not a bundled galletto cable. As for the drivers, the newest FTDI drivers are fine. Does the cable show up in nefmoto at all?
|
|
|
|
|
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
|
|
|
mikeb52
Full Member
Karma: +0/-2
Offline
Posts: 102
|
|
« Reply #5 on: July 03, 2014, 05:26:25 PM »
|
|
|
I connected just the cable to my pc running the nefmoto me7 flasher logger 1.9.3.2
Se,ected both kwp2000 and boot mode, ran through all baud choices and refreshed device each time and it did not see the cable.
Do I need to be connected to a car to read/test the cable?
Thnks,
|
|
|
|
|
Logged
|
|
|
|
mikeb52
Full Member
Karma: +0/-2
Offline
Posts: 102
|
|
« Reply #6 on: July 04, 2014, 06:58:04 AM »
|
|
|
So I tried to use the program, and cable connected to my 2000 jetta 2.0 as well as stand alone and no luck. Doesn't seem to connect. With this cable I can use vag com 409.1 to read my tranny, it wont read engine and comes back 'to many communication errors to continue', but I thought that could be the car itself as it was a bit of a dog when I bought it. I set the dumb mode, and kwp-2000 on within vagcom and saved it before exiting, but nothing in either slow init, fast init, or bootmode. Wish someone was close enough to watch over their shoulder. I feel I'm missing something obvious. I've been a pc guy since windows 3.0 and predate the internet. This should be doable by me,,,, grrrrrrrrrrrrrr  Thanks all, rant is over. |
|
|
|
|
Logged
|
|
|
|
mikeb52
Full Member
Karma: +0/-2
Offline
Posts: 102
|
|
« Reply #7 on: July 05, 2014, 10:25:13 AM »
|
|
|
So I have to assume my cable is crap since it isn't seen in the nefmoto software, or m-prog, despite the advertising.
Or I'm an idiot that is doing something fundamentally incorrect.
Tried to read my other jetta, no good either, but as I said, I can connect via vag com 409.1 to some extent.
So when the new cable arrives I will try to read the cable via nefmoto, then try to read my jetta via the obd2 connection and nefmoto. Then I will be rady to actual work on the ecu that has started all this in the first place.
Now regarding that one, its an 01 Wolfsburg turbo going into a Corrado. My harness will allow for proper obd2 connection in the Corrado.
I have to disable the immo, sai, evap, and asr in the ecu to work in the Rado.
I would like to re identify the vin to match the 90 Corrado as well, but not a must.
Would it be better to put the ecu in the car, and try to pull the bin and such through the obd or just go right to opening the cover and doing boot mode, since it is out at the moment?
I did try once already on the bench, and that's when I realized I have cable issues.
Thanks for any advise.
Mike.
|
|
|
|
|
Logged
|
|
|
|
|
ddillenger
|
|
« Reply #8 on: July 05, 2014, 10:52:11 AM »
|
|
|
Uninstall the old drivers (and check the box to delete them) and then manually intall the newest FTDI drivers.
|
|
|
|
|
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
|
|
|
mikeb52
Full Member
Karma: +0/-2
Offline
Posts: 102
|
|
« Reply #9 on: July 05, 2014, 07:44:08 PM »
|
|
|
Well that was a key step DD for certain.
Uninstalling and manually upgrading to 2.10.0.0 has enabled my cable to be read by nefmoto and m-prog.
It now shows up as a ft232r usb uart in the device drop down menu at 38400 baud!
So now I'm going to try and copy my jetta 2.0 ecu program, just to test.
That works, I'm going to retry my bootflash set up and argdubs software.
Still unsure if those two programs copy the same file, a bin file I believe, just through different means.
First real positive step in this ecu adventure. Been a good day. Got my fmic kit, and now progress on the ecu work..
May still get this car project completed..
Thanks for the tips again!!
|
|
|
|
|
Logged
|
|
|
|
|
ddillenger
|
|
« Reply #10 on: July 05, 2014, 07:57:09 PM »
|
|
|
Glad to hear you're having luck.
There are two types of memory in your ecu.
One is the flash that nefmoto/galletto read
One is the eeprom that argdubs tool reads.
|
|
|
|
|
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
|
|
|
mikeb52
Full Member
Karma: +0/-2
Offline
Posts: 102
|
|
« Reply #11 on: July 05, 2014, 08:19:17 PM »
|
|
|
Just tried the nefmoto flasher in the 2.0. I tried to connect in both fast nd slow init sequences, but I have no memory layout for ec maps installed yet so presume it can't read the flash until then.
My goal being immo and sai and such I think I will focus on the eeprom for now as that's the bin I need to edit to fix all those I believe yes? The flash is for tuning and optimizing said tune once the car is running once more?
I'll get to the tuning later. The original jetta tune worked awesome, in the jetta..
Cheers..
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #12 on: July 05, 2014, 08:23:54 PM »
|
|
|
I think I will focus on the eeprom for now as that's the bin I need to edit to fix all those I believe yes?
IMMO yes, SAI no. |
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! 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 ex
|
|
|
mikeb52
Full Member
Karma: +0/-2
Offline
Posts: 102
|
|
« Reply #13 on: July 05, 2014, 08:58:20 PM »
|
|
|
Well, still get the " no echo from cable" error 0x07.
I selected dumb mode in vag com before closing it but no change.
I wonder, when this is hot wired up, should the blue light on the dongle come on when you flip the switch?
For my set up, I'm using a battery charger,connected to a battery and taking the juice and grounds from that set up, running the power for both dongle, and ecu switched from the same switch. Should only the ecu be switched? Grounds all bundled together back to the negative post, and therefore negative on the charger.
Pin 7 on dongle to 43 on the ecu for k line comm. power to 3 and 62, both switched on the ecu,
16 on the dongle, also switched.
Grounds are pins 1 on the ecu and 4,5 on the dongle, all connected, as well as the jumper ground for 24 on the chip.
Was hopeful I was there.
Thanks.
|
|
|
|
|
Logged
|
|
|
|
|
ddillenger
|
|
« Reply #14 on: July 05, 2014, 09:26:54 PM »
|
|
|
You must also power pin21 on the ME7.5 ecus  |
|
|
|
|
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
|
|
|
|
