Pages: 1 [2] 3 4
Author Topic: proper noob start up help  (Read 36073 times)
adeyspec
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 131


« Reply #15 on: January 12, 2013, 06:21:03 AM »

i think i have a cable with the wrong chip in? i run an old 3.11 vagcom and it works great. thought id check with vcds and it wont work. could anyone confirm this?



update, opened it up and it has a ch340 chip in? guess i best get looking for a FT232R chipped one. Was really looking forward to doing my first pull on the ecu
« Last Edit: January 12, 2013, 06:44:27 AM by adeyspec » Logged
prj
Hero Member
*****

Karma: +915/-427
Offline Offline

Posts: 5840


« Reply #16 on: January 12, 2013, 07:06:28 AM »

Yeah wrong chip then.

VCDS will never work though, only VCDS Lite.
Logged

PM's will not be answered, so don't even try.
Log your car properly.
adeyspec
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 131


« Reply #17 on: January 12, 2013, 07:44:57 AM »

only loaded vcds to try it, i like my older fully working version. just got on ebay and ordered a cable with the fd232 chip in to get me started. a friend has a cable too so hes checking his so i might get on it sooner, cheers for the help
Logged
adeyspec
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 131


« Reply #18 on: January 18, 2013, 01:10:00 AM »

i have now got the cable that shows up in nefmoto  Grin time to try it all out. for just reading the map off the ecu do i need to go down the route of grounding the earth pin?

this is what im getting so far on my older 551 ecu

Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
KWP1281 connect info: 8D0907551   2,7l V6/5VT         D04

though im stuck on where to go to actually find the map to load into tuner pro.

if i click on read i get

Disabling Windows sleep mode.
Reading all ECU info.
Unable to validate programming session preconditions, attempting to continue.
Negotiating communication timings.
Successfully changed to new communication timings.
Starting diagnostic session.
Successfully started diagnostic session.
Negotiating communication timings.
Reading all ECU info failed.

please be gentle with me im still learning
Logged
adeyspec
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 131


« Reply #19 on: January 18, 2013, 02:38:06 AM »

looks like boot mode wont work with my new cable? wont connect atall if i put the ecu into boot?
Logged
aef
Hero Member
*****

Karma: +69/-46
Offline Offline

Posts: 1570


« Reply #20 on: January 18, 2013, 03:27:01 AM »

Try bootmode with argdubs tool.
Logged
adeyspec
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 131


« Reply #21 on: January 18, 2013, 12:09:09 PM »

FAIL error=0x09 ?
Logged
adeyspec
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 131


« Reply #22 on: January 19, 2013, 01:48:41 AM »

right with a few tweeks i managed to pull a file using argdubs tool. so im getting there slowly, cheers for the info peeps. so is this the same info i would have if i was pulling a file using nefmoto or something slightly different?
Logged
ddillenger
Hero Member
*****

Karma: +638/-21
Offline Offline

Posts: 5640


« Reply #23 on: January 19, 2013, 01:59:21 AM »

No. The file you pulled with me7_95040 is from the eeprom, not the flash chip. It is much smaller @ 512bytes and contains adaptation settings and immobilizer data. The flash chip is much larger @ 1024kb, and contains everything responsible for engine management.

The eeprom also contains the SKC, so now you have that as well, but you'll need to get nefmoto working to do any tuning.
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
adeyspec
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 131


« Reply #24 on: January 19, 2013, 02:41:57 AM »

mine has the smaller memory, think thats where i was confused. ok so if i can pull info in boot mode should it work in nefmoto?
Logged
adeyspec
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 131


« Reply #25 on: January 19, 2013, 02:59:24 AM »

this is what im getting from nefmoto boot mode

Connecting...
Starting bootstrap loader upload.
Sent bootstrap init zero byte.
Received device ID response for init zero byte.
Successfully uploaded bootstrap loader.
Received bootstrap loader started status message.
Starting upload of bootmode runtime.
Uploaded bootmode runtime data.
Sent baud rate detection byte.
Bootmode runtime upload failed. Failed to receive baud rate detection response message.
Disconnected
Connecting...
Starting bootstrap loader upload.
Sent bootstrap init zero byte.
Sent bootstrap init zero byte.
Sent bootstrap init zero byte.
Bootstrap loader upload failed. Failed to receive device ID response for init zero byte.
Disconnected
Logged
ddillenger
Hero Member
*****

Karma: +638/-21
Offline Offline

Posts: 5640


« Reply #26 on: January 19, 2013, 03:04:19 AM »

Nefmoto won't read the ecu in bootmode, it'll simply connect allowing you to confirm the ecu is actually in bootmode.

You need the galletto software to read the bin in bootmode. What you DON'T need is the galletto cable, as long as you have an ftdi based cable that contains a serial number (232bm/245bm devices do not, whereas 232r do), you can edit the galletto executable to work with your cable.

http://nefariousmotorsports.com/forum/index.php?topic=639.msg22346#msg22346

You can also change the serial number embedded in the cable to match the galletto executable, however this is not a viable option if you have a premium nefmoto license. Neither way is better than the other, both take less than a minute once you know what you're doing.
« Last Edit: January 19, 2013, 03:06:13 AM by ddillenger » 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
adeyspec
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 131


« Reply #27 on: January 19, 2013, 03:43:16 AM »

nice one looking through it now, got the program and it says unable to open com port or something close. just working through checking and changing the serial numbers
Logged
ddillenger
Hero Member
*****

Karma: +638/-21
Offline Offline

Posts: 5640


« Reply #28 on: January 19, 2013, 03:51:16 AM »

Yessir. Until you change the serial Galletto will display an error, something along the lines of "failed to open com port". Once the serials match it should work, if not, use the galletto 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
adeyspec
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 131


« Reply #29 on: January 19, 2013, 04:01:05 AM »

hmmm changed the serial in the .exe using a hex editor to match the one on my cable. galetto just comes up with opening port impossible. any other tips? there doesnt seem to be a setup screen anywhere to select ports or anything in the program
Logged
Pages: 1 [2] 3 4
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.041 seconds with 16 queries. (Pretty URLs adds 0.001s, 0q)