NefMoto > Technical > Flashing and Chipping > New ECU - still no Joy
Pages: [1]
« previous next »
Author Topic: New ECU - still no Joy  (Read 9679 times)
Rick
Hero Member
*****

Karma: +63/-4
Offline Offline

Posts: 704
« on: October 27, 2010, 11:15:20 AM »
Well after giving up with my oddball UK C box, i've just received an H box.  Tune is std as far as i know.  My car runs 660cc injectors etc so I knew it wouldn't run it with the std tune.  Howerver, i did try and start it and it ran for a few seconds albeit very rich, so far so good.

Next, VCDS connected no problem.  Finally time to try the Nefmoto flashing software. 

Nothing Sad  Exactly the same a my C box.  Slow innit fails. Tried 1.6 with the fast innit and still nothing.  Tried with a battery charger attached and no change.  Tried in a virtual box Vista session too.

Really at a loss.  If VCDS didn't work i would start blaming cables/drivers etc but it works perfectly Sad

Rick
Logged
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +132/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3
« Reply #1 on: October 27, 2010, 11:23:38 AM »
Lets double check everything.

Are you trying this in the car or on the bench?
Which cable are you using?
What OS and computer specs are you using?
Did you try pulling the instrument cluster fuse?

1.6 fixed a lot of communication protocol edge cases, so this really should work.
Logged
Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
Rick
Hero Member
*****

Karma: +63/-4
Offline Offline

Posts: 704
« Reply #2 on: October 27, 2010, 12:04:34 PM »
Tony,

So far all attempts in car.  I am shortly going to try on the bench which means I can use my Windows 7 32 bit desktop machine.

Cable is the blue ebay china dumb version.

Not tried pulling any fuses - i don't believe anyone is doing this with your software?

So far i have been using a 1.3 GHz 64 bit Celeron Netbook, GB memory running windows 7 64 bit.

Rick
Logged
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +132/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3
« Reply #3 on: October 27, 2010, 12:07:32 PM »
If VCDS can connect it probably doesn't require pulling the instrument cluster fuse.

Do you have a log file showing how slow init is failing?
Logged
Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
Rick
Hero Member
*****

Karma: +63/-4
Offline Offline

Posts: 704
« Reply #4 on: October 27, 2010, 12:22:43 PM »
Log file from tonight:


27/Oct/2010 06:35:22.641: LOG: Opened FTDI device.
27/Oct/2010 06:35:22.644: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM Device ID: 0x4036001 Device Flags: 0x0
27/Oct/2010 06:35:22.645: LOG: FTDI ChipID DLL is loaded, checking chip ID...
27/Oct/2010 06:35:22.645: LOG: Unable to read FTDI device chip ID
27/Oct/2010 06:35:22.696: LOG: Starting send receive thread.
27/Oct/2010 06:35:22.698: LOG: Send receive thread now started.
27/Oct/2010 06:35:22.704: USER: Disconnected
27/Oct/2010 06:35:22.759: USER: Connection attempt number 1.
27/Oct/2010 06:35:22.771: USER: Connecting...
27/Oct/2010 06:35:23.087: USER: Connecting to address 0x01.
27/Oct/2010 06:35:25.418: LOG: Failed to read sync byte. Read 0 bytes.
27/Oct/2010 06:35:25.437: USER: Slow init failed.
27/Oct/2010 06:35:25.443: USER: Disconnected
27/Oct/2010 06:35:25.472: USER: Connection attempt number 2.
27/Oct/2010 06:35:25.487: USER: Connecting...
27/Oct/2010 06:35:25.807: USER: Connecting to address 0x01.
27/Oct/2010 06:35:28.140: LOG: Failed to read sync byte. Read 0 bytes.
27/Oct/2010 06:35:28.163: USER: Slow init failed.
27/Oct/2010 06:35:28.170: USER: Disconnected
27/Oct/2010 06:35:28.201: USER: Connection attempt number 3.
27/Oct/2010 06:35:28.214: USER: Connecting...
27/Oct/2010 06:35:28.540: USER: Connecting to address 0x01.
27/Oct/2010 06:35:30.880: LOG: Failed to read sync byte. Read 0 bytes.
27/Oct/2010 06:35:30.899: USER: Slow init failed.
27/Oct/2010 06:35:30.919: USER: Disconnected
27/Oct/2010 06:35:30.952: LOG: Closing FTDI device.
27/Oct/2010 06:35:30.971: LOG: Send receive thread now terminated.
27/Oct/2010 06:35:34.544: LOG: Opened FTDI device.
27/Oct/2010 06:35:34.545: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM Device ID: 0x4036001 Device Flags: 0x0
27/Oct/2010 06:35:34.545: LOG: FTDI ChipID DLL is loaded, checking chip ID...
27/Oct/2010 06:35:34.546: LOG: Unable to read FTDI device chip ID
27/Oct/2010 06:35:34.592: LOG: Starting send receive thread.
27/Oct/2010 06:35:34.594: LOG: Send receive thread now started.
27/Oct/2010 06:35:34.600: USER: Disconnected
27/Oct/2010 06:35:34.624: USER: Connection attempt number 1.
27/Oct/2010 06:35:34.637: USER: Connecting...
27/Oct/2010 06:35:34.642: USER: Connecting to address 0x01.
27/Oct/2010 06:35:35.060: LOG: Sent message with service ID StartCommunication
27/Oct/2010 06:35:35.063: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
27/Oct/2010 06:35:35.066: USER: Fast init succeeded.
27/Oct/2010 06:35:35.117: LOG: Failed to send message 1 times, message send failed.
27/Oct/2010 06:35:35.119: USER: Disconnected
27/Oct/2010 06:35:35.156: USER: Connection attempt number 2.
27/Oct/2010 06:35:35.168: USER: Connecting...
27/Oct/2010 06:35:35.174: USER: Connecting to address 0x01.
27/Oct/2010 06:35:35.599: LOG: Sent message with service ID StartCommunication
27/Oct/2010 06:35:35.602: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
27/Oct/2010 06:35:35.607: USER: Fast init succeeded.
27/Oct/2010 06:35:35.655: LOG: Failed to send message 1 times, message send failed.
27/Oct/2010 06:35:35.657: USER: Disconnected
27/Oct/2010 06:35:35.698: USER: Connection attempt number 3.
27/Oct/2010 06:35:35.705: USER: Connecting...
27/Oct/2010 06:35:35.739: USER: Connecting to address 0x01.
27/Oct/2010 06:35:36.154: LOG: Sent message with service ID StartCommunication
27/Oct/2010 06:35:36.157: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
27/Oct/2010 06:35:36.160: USER: Fast init succeeded.
27/Oct/2010 06:35:36.209: LOG: Failed to send message 1 times, message send failed.
27/Oct/2010 06:35:36.212: USER: Disconnected
27/Oct/2010 06:35:36.245: LOG: Closing FTDI device.
27/Oct/2010 06:35:36.261: LOG: Send receive thread now terminated.
27/Oct/2010 06:35:43.164: LOG: Opened FTDI device.
27/Oct/2010 06:35:43.165: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM Device ID: 0x4036001 Device Flags: 0x0
27/Oct/2010 06:35:43.165: LOG: FTDI ChipID DLL is loaded, checking chip ID...
27/Oct/2010 06:35:43.166: LOG: Unable to read FTDI device chip ID
27/Oct/2010 06:35:43.212: LOG: Starting send receive thread.
27/Oct/2010 06:35:43.214: LOG: Send receive thread now started.
27/Oct/2010 06:35:43.219: USER: Disconnected
27/Oct/2010 06:35:43.249: USER: Connection attempt number 1.
27/Oct/2010 06:35:43.264: USER: Connecting...
27/Oct/2010 06:35:43.268: USER: Connecting to address 0x01.
27/Oct/2010 06:35:43.687: LOG: Sent message with service ID StartCommunication
27/Oct/2010 06:35:43.691: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
27/Oct/2010 06:35:43.693: USER: Fast init succeeded.
27/Oct/2010 06:35:43.743: LOG: Failed to send message 1 times, message send failed.
27/Oct/2010 06:35:43.746: USER: Disconnected
27/Oct/2010 06:35:43.772: USER: Connection attempt number 2.
27/Oct/2010 06:35:43.841: USER: Connecting...
27/Oct/2010 06:35:43.861: USER: Connecting to address 0x01.
27/Oct/2010 06:35:44.273: LOG: Sent message with service ID StartCommunication
27/Oct/2010 06:35:44.276: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
27/Oct/2010 06:35:44.281: USER: Fast init succeeded.
27/Oct/2010 06:35:44.329: LOG: Failed to send message 1 times, message send failed.
27/Oct/2010 06:35:44.331: USER: Disconnected
27/Oct/2010 06:35:44.368: USER: Connection attempt number 3.
27/Oct/2010 06:35:44.381: USER: Connecting...
27/Oct/2010 06:35:44.416: USER: Connecting to address 0x01.
27/Oct/2010 06:35:44.832: LOG: Sent message with service ID StartCommunication
27/Oct/2010 06:35:44.837: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
27/Oct/2010 06:35:44.839: USER: Fast init succeeded.
27/Oct/2010 06:35:44.887: LOG: Failed to send message 1 times, message send failed.
27/Oct/2010 06:35:44.890: USER: Disconnected
27/Oct/2010 06:35:44.928: LOG: Closing FTDI device.
27/Oct/2010 06:35:44.957: LOG: Send receive thread now terminated.
27/Oct/2010 06:36:34.394: LOG: Opened FTDI device.
27/Oct/2010 06:36:34.395: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM Device ID: 0x4036001 Device Flags: 0x0
27/Oct/2010 06:36:34.395: LOG: FTDI ChipID DLL is loaded, checking chip ID...
27/Oct/2010 06:36:34.396: LOG: Unable to read FTDI device chip ID
27/Oct/2010 06:36:34.446: LOG: Starting send receive thread.
27/Oct/2010 06:36:34.448: LOG: Send receive thread now started.
27/Oct/2010 06:36:34.454: USER: Disconnected
27/Oct/2010 06:36:34.488: USER: Connection attempt number 1.
27/Oct/2010 06:36:34.508: USER: Connecting...
27/Oct/2010 06:36:34.517: USER: Connecting to address 0x01.
27/Oct/2010 06:36:34.930: LOG: Sent message with service ID StartCommunication
27/Oct/2010 06:36:34.933: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
27/Oct/2010 06:36:34.935: USER: Fast init succeeded.
27/Oct/2010 06:36:34.985: LOG: Failed to send message 1 times, message send failed.
27/Oct/2010 06:36:35.006: USER: Disconnected
27/Oct/2010 06:36:35.046: USER: Connection attempt number 2.
27/Oct/2010 06:36:35.053: USER: Connecting...
27/Oct/2010 06:36:35.085: USER: Connecting to address 0x01.
27/Oct/2010 06:36:35.495: LOG: Sent message with service ID StartCommunication
27/Oct/2010 06:36:35.500: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
27/Oct/2010 06:36:35.504: USER: Fast init succeeded.
27/Oct/2010 06:36:35.552: LOG: Failed to send message 1 times, message send failed.
27/Oct/2010 06:36:35.555: USER: Disconnected
27/Oct/2010 06:36:35.586: USER: Connection attempt number 3.
27/Oct/2010 06:36:35.637: USER: Connecting...
27/Oct/2010 06:36:35.656: USER: Connecting to address 0x01.
27/Oct/2010 06:36:36.096: LOG: Sent message with service ID StartCommunication
27/Oct/2010 06:36:36.099: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
27/Oct/2010 06:36:36.101: USER: Fast init succeeded.
27/Oct/2010 06:36:36.151: LOG: Failed to send message 1 times, message send failed.
27/Oct/2010 06:36:36.154: USER: Disconnected
27/Oct/2010 06:36:36.189: LOG: Closing FTDI device.
27/Oct/2010 06:36:36.206: LOG: Send receive thread now terminated.
27/Oct/2010 06:36:52.594: LOG: Closing NefMoto ME7 ECU Flasher BETA 1.6.0.0
27/Oct/2010 06:49:45.758: LOG: Opened NefMoto ME7 ECU Flasher BETA 1.6.0.0
27/Oct/2010 06:49:50.444: LOG: Opened FTDI device.
27/Oct/2010 06:49:50.446: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM Device ID: 0x4036001 Device Flags: 0x0
27/Oct/2010 06:49:50.447: LOG: FTDI ChipID DLL is loaded, checking chip ID...
27/Oct/2010 06:49:50.449: LOG: Unable to read FTDI device chip ID
27/Oct/2010 06:49:50.514: LOG: Starting send receive thread.
27/Oct/2010 06:49:50.523: LOG: Send receive thread now started.
27/Oct/2010 06:49:50.528: USER: Disconnected
27/Oct/2010 06:49:50.557: USER: Connection attempt number 1.
27/Oct/2010 06:49:50.569: USER: Connecting...
27/Oct/2010 06:49:50.594: USER: Connecting to address 0x01.
27/Oct/2010 06:49:51.012: LOG: Sent message with service ID StartCommunication
27/Oct/2010 06:49:51.018: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
27/Oct/2010 06:49:51.020: USER: Fast init succeeded.
27/Oct/2010 06:49:51.068: LOG: Failed to send message 1 times, message send failed.
27/Oct/2010 06:49:51.072: USER: Disconnected
27/Oct/2010 06:49:51.098: USER: Connection attempt number 2.
27/Oct/2010 06:49:51.106: USER: Connecting...
27/Oct/2010 06:49:51.114: USER: Connecting to address 0x01.
27/Oct/2010 06:49:51.531: LOG: Sent message with service ID StartCommunication
27/Oct/2010 06:49:51.535: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
27/Oct/2010 06:49:51.546: USER: Fast init succeeded.
27/Oct/2010 06:49:51.588: LOG: Failed to send message 1 times, message send failed.
27/Oct/2010 06:49:51.590: USER: Disconnected
27/Oct/2010 06:49:51.624: USER: Connection attempt number 3.
27/Oct/2010 06:49:51.670: USER: Connecting...
27/Oct/2010 06:49:51.703: USER: Connecting to address 0x01.
27/Oct/2010 06:49:52.115: LOG: Sent message with service ID StartCommunication
27/Oct/2010 06:49:52.118: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
27/Oct/2010 06:49:52.121: USER: Fast init succeeded.
27/Oct/2010 06:49:52.171: LOG: Failed to send message 1 times, message send failed.
27/Oct/2010 06:49:52.174: USER: Disconnected
27/Oct/2010 06:49:52.215: LOG: Closing FTDI device.
27/Oct/2010 06:49:52.226: LOG: Send receive thread now terminated.
27/Oct/2010 06:49:54.621: LOG: Opened FTDI device.
27/Oct/2010 06:49:54.622: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM Device ID: 0x4036001 Device Flags: 0x0
27/Oct/2010 06:49:54.623: LOG: FTDI ChipID DLL is loaded, checking chip ID...
27/Oct/2010 06:49:54.623: LOG: Unable to read FTDI device chip ID
27/Oct/2010 06:49:54.673: LOG: Starting send receive thread.
27/Oct/2010 06:49:54.676: LOG: Send receive thread now started.
27/Oct/2010 06:49:54.708: USER: Disconnected
27/Oct/2010 06:49:54.762: USER: Connection attempt number 1.
27/Oct/2010 06:49:54.770: USER: Connecting...
27/Oct/2010 06:49:55.086: USER: Connecting to address 0x01.
27/Oct/2010 06:49:57.437: LOG: Failed to read sync byte. Read 0 bytes.
27/Oct/2010 06:49:57.458: USER: Slow init failed.
27/Oct/2010 06:49:57.461: USER: Disconnected
27/Oct/2010 06:49:57.486: USER: Connection attempt number 2.
27/Oct/2010 06:49:57.512: USER: Connecting...
27/Oct/2010 06:49:57.823: USER: Connecting to address 0x01.
27/Oct/2010 06:50:00.158: LOG: Failed to read sync byte. Read 0 bytes.
27/Oct/2010 06:50:00.178: USER: Slow init failed.
27/Oct/2010 06:50:00.184: USER: Disconnected
27/Oct/2010 06:50:00.217: USER: Connection attempt number 3.
27/Oct/2010 06:50:00.231: USER: Connecting...
27/Oct/2010 06:50:00.537: USER: Connecting to address 0x01.
27/Oct/2010 06:50:02.874: LOG: Failed to read sync byte. Read 0 bytes.
27/Oct/2010 06:50:02.895: USER: Slow init failed.
27/Oct/2010 06:50:02.900: USER: Disconnected
27/Oct/2010 06:50:02.936: LOG: Closing FTDI device.
27/Oct/2010 06:50:02.950: LOG: Send receive thread now terminated.
27/Oct/2010 06:50:31.714: LOG: Closing NefMoto ME7 ECU Flasher BETA 1.6.0.0
27/Oct/2010 06:52:50.609: LOG: Opened NefMoto ME7 ECU Flasher BETA 1.6.0.0
27/Oct/2010 06:53:04.167: LOG: Opened FTDI device.
27/Oct/2010 06:53:04.168: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM Device ID: 0x4036001 Device Flags: 0x0
27/Oct/2010 06:53:04.169: LOG: FTDI ChipID DLL is loaded, checking chip ID...
27/Oct/2010 06:53:04.170: LOG: Unable to read FTDI device chip ID
27/Oct/2010 06:53:04.233: LOG: Starting send receive thread.
27/Oct/2010 06:53:04.241: LOG: Send receive thread now started.
27/Oct/2010 06:53:04.246: USER: Disconnected
27/Oct/2010 06:53:04.275: USER: Connection attempt number 1.
27/Oct/2010 06:53:04.297: USER: Connecting...
27/Oct/2010 06:53:04.617: USER: Connecting to address 0x01.
27/Oct/2010 06:53:06.972: LOG: Failed to read sync byte. Read 0 bytes.
27/Oct/2010 06:53:06.993: USER: Slow init failed.
27/Oct/2010 06:53:06.997: USER: Disconnected
27/Oct/2010 06:53:07.024: USER: Connection attempt number 2.
27/Oct/2010 06:53:07.046: USER: Connecting...
27/Oct/2010 06:53:07.360: USER: Connecting to address 0x01.
27/Oct/2010 06:53:09.695: LOG: Failed to read sync byte. Read 0 bytes.
27/Oct/2010 06:53:09.722: USER: Slow init failed.
27/Oct/2010 06:53:09.729: USER: Disconnected
27/Oct/2010 06:53:09.763: USER: Connection attempt number 3.
27/Oct/2010 06:53:09.776: USER: Connecting...
27/Oct/2010 06:53:10.084: USER: Connecting to address 0x01.
27/Oct/2010 06:53:12.427: LOG: Failed to read sync byte. Read 0 bytes.
27/Oct/2010 06:53:12.446: USER: Slow init failed.
27/Oct/2010 06:53:12.451: USER: Disconnected
27/Oct/2010 06:53:12.481: LOG: Closing FTDI device.
27/Oct/2010 06:53:12.499: LOG: Send receive thread now terminated.
27/Oct/2010 06:53:22.636: LOG: Opened FTDI device.
27/Oct/2010 06:53:22.637: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM Device ID: 0x4036001 Device Flags: 0x0
27/Oct/2010 06:53:22.638: LOG: FTDI ChipID DLL is loaded, checking chip ID...
27/Oct/2010 06:53:22.638: LOG: Unable to read FTDI device chip ID
27/Oct/2010 06:53:22.686: LOG: Starting send receive thread.
27/Oct/2010 06:53:22.688: LOG: Send receive thread now started.
27/Oct/2010 06:53:22.695: USER: Disconnected
27/Oct/2010 06:53:22.720: USER: Connection attempt number 1.
27/Oct/2010 06:53:22.738: USER: Connecting...
27/Oct/2010 06:53:23.049: USER: Connecting to address 0x01.
27/Oct/2010 06:53:25.381: LOG: Failed to read sync byte. Read 0 bytes.
27/Oct/2010 06:53:25.398: USER: Slow init failed.
27/Oct/2010 06:53:25.402: USER: Disconnected
27/Oct/2010 06:53:25.427: USER: Connection attempt number 2.
27/Oct/2010 06:53:25.440: USER: Connecting...
27/Oct/2010 06:53:25.747: USER: Connecting to address 0x01.
27/Oct/2010 06:53:28.085: LOG: Failed to read sync byte. Read 0 bytes.
27/Oct/2010 06:53:28.107: USER: Slow init failed.
27/Oct/2010 06:53:28.113: USER: Disconnected
27/Oct/2010 06:53:28.145: USER: Connection attempt number 3.
27/Oct/2010 06:53:28.171: USER: Connecting...
27/Oct/2010 06:53:28.476: USER: Connecting to address 0x01.
27/Oct/2010 06:53:30.817: LOG: Failed to read sync byte. Read 0 bytes.
27/Oct/2010 06:53:30.836: USER: Slow init failed.
27/Oct/2010 06:53:30.841: USER: Disconnected
27/Oct/2010 06:53:30.865: LOG: Closing FTDI device.
27/Oct/2010 06:53:30.886: LOG: Send receive thread now terminated.
27/Oct/2010 06:53:42.251: LOG: Opened FTDI device.
27/Oct/2010 06:53:42.252: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM Device ID: 0x4036001 Device Flags: 0x0
27/Oct/2010 06:53:42.252: LOG: FTDI ChipID DLL is loaded, checking chip ID...
27/Oct/2010 06:53:42.253: LOG: Unable to read FTDI device chip ID
27/Oct/2010 06:53:45.303: USER: Failed to read test echo from FTDI device. Make sure the cable is in dumb mode and connected to the OBD port.
27/Oct/2010 06:54:00.023: LOG: Closing NefMoto ME7 ECU Flasher BETA 1.6.0.0
27/Oct/2010 08:24:21.049: LOG: Opened NefMoto ME7 ECU Flasher BETA 1.6.0.0
Logged
Rick
Hero Member
*****

Karma: +63/-4
Offline Offline

Posts: 704
« Reply #5 on: October 27, 2010, 01:07:54 PM »
Tony, Success!!!!  Cheesy Cheesy Cheesy

Bench read using my desktop.

Now going to try bench read using my laptop...

Rick
Logged
Rick
Hero Member
*****

Karma: +63/-4
Offline Offline

Posts: 704
« Reply #6 on: October 27, 2010, 01:54:16 PM »
Ok, the H box works on my laptop on the bench, so it is the car that is stopping coms somehow.  Next test is to pull the fuse for the cluster I guess!

Rick
Logged
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +132/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3
« Reply #7 on: October 27, 2010, 02:09:57 PM »
That is really weird. But I am glad you found it works on the bench.

The logs indicate that there is absolutely no response from the ECU. So it isn't something in the protocol that is failing. The ECU doesn't appear to respond to the wake up at all.

I have no idea why VCDS would work, and my software wouldn't though. Unless it is doing something tricky, like determining that the instrument cluster needs to be connected to first or something.

Can you take a multimeter and verify that the K-line on your OBD port is connected to the K-line on your ECU plug in the engine bay?
Logged
Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
Rick
Hero Member
*****

Karma: +63/-4
Offline Offline

Posts: 704
« Reply #8 on: October 27, 2010, 02:38:34 PM »
Yes I will do that, but doesn't VCDS use Kline?

I tested the C box on the bench, and this time it connected Smiley  However, I can't validate or read the flash, an error message says that the ECU needs to be connected to the vehicle? 

Log file:


27/Oct/2010 09:32:21.681: LOG: Opened NefMoto ME7 ECU Flasher BETA 1.6.0.0
27/Oct/2010 09:32:24.663: LOG: Opened FTDI device.
27/Oct/2010 09:32:24.664: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM Device ID: 0x4036001 Device Flags: 0x0
27/Oct/2010 09:32:24.665: LOG: FTDI ChipID DLL is loaded, checking chip ID...
27/Oct/2010 09:32:24.666: LOG: Unable to read FTDI device chip ID
27/Oct/2010 09:32:24.725: LOG: Starting send receive thread.
27/Oct/2010 09:32:24.730: LOG: Send receive thread now started.
27/Oct/2010 09:32:24.734: USER: Disconnected
27/Oct/2010 09:32:24.759: USER: Connection attempt number 1.
27/Oct/2010 09:32:24.764: USER: Connecting...
27/Oct/2010 09:32:25.070: USER: Connecting to address 0x01.
27/Oct/2010 09:32:27.247: USER: Slow init succeeded.
27/Oct/2010 09:32:27.249: USER: Switching to KWP1281 session.
27/Oct/2010 09:32:27.425: LOG: KWP1281 read block
27/Oct/2010 09:32:27.490: LOG: KWP1281 sent block
27/Oct/2010 09:32:27.748: LOG: KWP1281 read block
27/Oct/2010 09:32:27.812: LOG: KWP1281 sent block
27/Oct/2010 09:32:27.990: LOG: KWP1281 read block
27/Oct/2010 09:32:28.053: LOG: KWP1281 sent block
27/Oct/2010 09:32:28.202: LOG: KWP1281 read block
27/Oct/2010 09:32:28.265: LOG: KWP1281 sent block
27/Oct/2010 09:32:28.301: LOG: KWP1281 read block
27/Oct/2010 09:32:28.366: LOG: KWP1281 sent block
27/Oct/2010 09:32:28.371: USER: KWP1281 connect info: 8D0907551C  2.7l V6/MRC         0002 +? ?
27/Oct/2010 09:32:29.871: USER: Connecting to address 0x01.
27/Oct/2010 09:32:32.041: USER: Slow init succeeded.
27/Oct/2010 09:32:32.049: USER: Switching to KWP2000 session.
27/Oct/2010 09:32:32.364: LOG: Sent message with service ID StartCommunication
27/Oct/2010 09:32:32.413: LOG: Received message with service ID NegativeResponse
27/Oct/2010 09:32:32.414: LOG: Received negative response for service ID: StartCommunication, with response code: ServiceNotSupported
27/Oct/2010 09:32:32.418: USER: Connected
27/Oct/2010 09:32:34.923: LOG: Sent message with service ID TesterPresent
27/Oct/2010 09:32:34.962: LOG: Received message with service ID TesterPresentPositiveReponse
27/Oct/2010 09:32:37.478: LOG: Sent message with service ID TesterPresent
27/Oct/2010 09:32:37.517: LOG: Received message with service ID TesterPresentPositiveReponse
27/Oct/2010 09:32:39.488: USER: Reading ECU flash memory.
27/Oct/2010 09:32:39.490: USER: Disabling Windows sleep mode.
27/Oct/2010 09:32:39.503: USER: Reading ECU identification option: calibrationEquipmentSoftwareNumber
27/Oct/2010 09:32:39.524: LOG: Sent message with service ID ReadECUIdentification
27/Oct/2010 09:32:39.575: LOG: Received message with service ID ReadECUIdentificationPositiveResponse
27/Oct/2010 09:32:39.580: USER: Read ECU identification option with unknown scaling record.
27/Oct/2010 09:32:39.581: USER: Successfully read ECU identification information
27/Oct/2010 09:32:39.585: USER: ECU reports programming session preconditions have not been met.
27/Oct/2010 09:32:39.586: USER: Reasons preconditions failed:
27/Oct/2010 09:32:39.588: USER: -ECU must be connected to the vehicle
27/Oct/2010 09:32:42.088: LOG: Sent message with service ID TesterPresent
27/Oct/2010 09:32:42.133: LOG: Received message with service ID TesterPresentPositiveReponse
27/Oct/2010 09:32:43.759: LOG: User Prompt - Title: Programming Session Preconditions Not Met Message: ECU reports programming session preconditions have not been met..
Reasons preconditions failed:
-ECU must be connected to the vehicle

 Do you want to attempt to continue? Result: True
27/Oct/2010 09:32:43.762: USER: Continuing despite programming session preconditions not being met
27/Oct/2010 09:32:43.765: LOG: Starting diagnostic session type: ProgrammingSession
27/Oct/2010 09:32:43.777: USER: Starting diagnostic session.
27/Oct/2010 09:32:43.804: LOG: Sent message with service ID StartDiagnosticSession
27/Oct/2010 09:32:43.864: LOG: Received message with service ID NegativeResponse
27/Oct/2010 09:32:43.864: LOG: Ignoring message with service ID NegativeResponse because it was unsolicited
27/Oct/2010 09:32:43.865: LOG: Unsolicited negative response, request ID: StartDiagnosticSession response code: ConditionsNotCorrectOrRequestSequenceError
27/Oct/2010 09:32:43.921: LOG: Resending message. Send attempts: 2
27/Oct/2010 09:32:43.949: LOG: Sent message with service ID StartDiagnosticSession
27/Oct/2010 09:32:44.004: LOG: Resending message. Send attempts: 3
27/Oct/2010 09:32:44.031: LOG: Sent message with service ID StartDiagnosticSession
27/Oct/2010 09:32:44.063: LOG: Received message with service ID NegativeResponse
27/Oct/2010 09:32:44.063: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: ConditionsNotCorrectOrRequestSequenceError
27/Oct/2010 09:32:44.068: USER: Start diagnostic session failed, ECU reports conditions not correct or sequence error. Please turn off the ignition and retry.
27/Oct/2010 09:32:44.074: USER: Restoring Windows sleep mode.
27/Oct/2010 09:32:44.078: USER: Reading ECU flash memory failed.
27/Oct/2010 09:32:46.579: LOG: Sent message with service ID TesterPresent
27/Oct/2010 09:32:46.618: LOG: Received message with service ID TesterPresentPositiveReponse
27/Oct/2010 09:32:49.133: LOG: Sent message with service ID TesterPresent
27/Oct/2010 09:32:49.172: LOG: Received message with service ID TesterPresentPositiveReponse
27/Oct/2010 09:32:51.689: LOG: Sent message with service ID TesterPresent
27/Oct/2010 09:32:51.728: LOG: Received message with service ID TesterPresentPositiveReponse
27/Oct/2010 09:32:54.242: LOG: Sent message with service ID TesterPresent
27/Oct/2010 09:32:54.281: LOG: Received message with service ID TesterPresentPositiveReponse
27/Oct/2010 09:32:54.755: LOG: Closing NefMoto ME7 ECU Flasher BETA 1.6.0.0
Logged
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +132/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3
« Reply #9 on: October 27, 2010, 02:54:42 PM »
I don't actually know what precondition that one is. I believe it means the ECU must be in the car, but I am not 100% sure.
Logged
Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
Pages: [1]
  Print  
« previous next »
 
Jump to:  

Navigation
Personal Tools
  • November 27, 2024, 08:16:27 PM
  • Welcome, Guest. Please login or register.
    Did you miss your activation email?

    Login with username, password and session length
Search
 
Advanced Search
About Disclaimer
All Rights Reserved 2010 Nefarious Motosports
Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.035 seconds with 18 queries. (Pretty URLs adds 0s, 0q)