Title: Help Can't connect - log inside Post by: pedrosousa on January 11, 2016, 04:00:44 PM Hi, I'm having problems connecting on bench, haven't tried in car but I thinks it's going to be the same problem...
Here's the log 11-Jan-2016 10:33:08.125: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F 11-Jan-2016 10:33:08.125: USER: Switching to KWP2000 session. 11-Jan-2016 10:33:08.484: LOG: Opened FTDI device. 11-Jan-2016 10:33:08.484: LOG: FTDI device info - Description: USB <-> Serial Serial Number: Device Type: FT_DEVICE_BM ID: 0x4036001 Device Flags: 0x0 11-Jan-2016 10:33:08.484: LOG: FTDI ChipID DLL is loaded, checking chip ID... 11-Jan-2016 10:33:08.484: LOG: Unable to read FTDI device chip ID 11-Jan-2016 10:33:08.844: USER: Validated FTDI device is in dumb mode. 11-Jan-2016 10:33:08.859: LOG: Starting send receive thread. 11-Jan-2016 10:33:08.875: LOG: Send receive thread now started. 11-Jan-2016 10:33:08.875: USER: Disconnected 11-Jan-2016 10:33:09.078: LOG: Setting communication timings to defaults. 11-Jan-2016 10:33:09.078: USER: Connecting... 11-Jan-2016 10:33:09.281: LOG: Setting communication timings to defaults. 11-Jan-2016 10:33:09.281: USER: Starting slow init connection. 11-Jan-2016 10:33:11.891: USER: Connecting to address 0x01. 11-Jan-2016 10:33:14.297: USER: Slow init succeeded. 11-Jan-2016 10:33:14.312: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x0A 11-Jan-2016 10:33:14.312: USER: Switching to KWP1281 session. 11-Jan-2016 10:33:15.672: LOG: Failed to read KWP1281 block title byte. 11-Jan-2016 10:33:15.672: LOG: KWP1281 read block failed. 11-Jan-2016 10:33:15.672: USER: Failed to read KWP1281 connect info. 11-Jan-2016 10:33:17.172: USER: Connecting to address 0x01. 11-Jan-2016 10:33:19.609: USER: Slow init succeeded. 11-Jan-2016 10:33:19.609: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x0A 11-Jan-2016 10:33:20.969: LOG: Failed to read KWP1281 block title byte. 11-Jan-2016 10:33:20.969: LOG: KWP1281 read block failed. 11-Jan-2016 10:33:20.969: USER: Failed to read KWP1281 connect info. 11-Jan-2016 10:33:22.469: USER: Connecting to address 0x11. 11-Jan-2016 10:33:24.859: USER: Slow init succeeded. 11-Jan-2016 10:33:24.875: LOG: Setting Address: 0x11 KeyByte1: 0x6F KeyByte2: 0x0F 11-Jan-2016 10:33:24.875: USER: Switching to KWP2000 session. 11-Jan-2016 10:33:25.218: LOG: Sent message with service ID StartCommunication 11-Jan-2016 10:33:25.218: USER: Sending start communication request. 11-Jan-2016 10:33:25.234: LOG: Read incorrect echo from ECU while sending message bytes. Matched first 1 of 2 bytes. 11-Jan-2016 10:33:25.234: LOG: Expected: 01 81 82 11-Jan-2016 10:33:25.234: LOG: Read: 01 81 11-Jan-2016 10:33:25.234: LOG: Was ignoring first 1 bytes of the echo. 11-Jan-2016 10:33:25.234: LOG: Clearing remaining expected echo bytes. 11-Jan-2016 10:33:28.265: LOG: Double checking receive buffer for embedded messages before flushing receive buffer due to P1 ECU response inter byte time out. 11-Jan-2016 10:33:28.265: LOG: Flushing 2 bytes from receive buffer due to P1 ECU response inter byte time out. 11-Jan-2016 10:33:28.265: LOG: Message received no replies. 11-Jan-2016 10:33:28.265: LOG: Failed to send message 1 times, message send failed. 11-Jan-2016 10:33:28.265: USER: Start communication request did not receive any response. 11-Jan-2016 10:33:28.265: USER: Disconnected 11-Jan-2016 10:33:28.453: LOG: Setting communication timings to defaults. 11-Jan-2016 10:33:28.468: USER: Connecting... 11-Jan-2016 10:33:28.672: LOG: Setting communication timings to defaults. 11-Jan-2016 10:33:28.672: USER: Starting slow init connection. 11-Jan-2016 10:33:31.281: USER: Connecting to address 0x11. 11-Jan-2016 10:33:34.203: LOG: Failed to read sync byte, guessing baud rate is actually 9600. 11-Jan-2016 10:33:34.265: LOG: Not enough key bytes, read: 0 11-Jan-2016 10:33:34.375: USER: Slow init failed. 11-Jan-2016 10:33:34.390: USER: Disconnected 11-Jan-2016 10:33:34.546: LOG: Setting communication timings to defaults. 11-Jan-2016 10:33:34.546: USER: Connecting... 11-Jan-2016 10:33:34.703: LOG: Setting communication timings to defaults. 11-Jan-2016 10:33:34.703: USER: Starting slow init connection. 11-Jan-2016 10:33:37.312: USER: Connecting to address 0x11. 11-Jan-2016 10:33:40.234: LOG: Failed to read sync byte, guessing baud rate is actually 9600. 11-Jan-2016 10:33:40.296: LOG: Not enough key bytes, read: 0 11-Jan-2016 10:33:40.421: USER: Slow init failed. 11-Jan-2016 10:33:40.421: USER: Disconnected 11-Jan-2016 10:33:40.546: LOG: Setting communication timings to defaults. 11-Jan-2016 10:33:40.609: LOG: Closing FTDI device. 11-Jan-2016 10:33:40.624: LOG: Send receive thread now terminated. Cable problem? or other problem?? Vag-com works on bench Title: Re: Help Can't connect - log inside Post by: armageddon on January 11, 2016, 05:26:31 PM If you are around Barcelos you can try with my cable
Title: Re: Help Can't connect - log inside Post by: pedrosousa on January 12, 2016, 02:40:28 PM Tested with the last version of NefMoto and the log bench reading is this:
12-Jan-2016 09:10:44.037: LOG: Opening NefMoto VW Audi ME7 Flasher Logger 1.9.3.2 12-Jan-2016 09:10:45.225: LOG: Cannot load license file, file does not exist: C:\Documents and Settings\Administrador\Application Data\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat 12-Jan-2016 09:10:45.537: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2 12-Jan-2016 09:11:06.347: LOG: Closing NefMoto VW Audi ME7 Flasher Logger 1.9.3.2 12-Jan-2016 09:24:52.817: LOG: Opening NefMoto VW Audi ME7 Flasher Logger 1.9.3.2 12-Jan-2016 09:25:20.660: LOG: Opening NefMoto VW Audi ME7 Flasher Logger 1.9.3.2 12-Jan-2016 09:25:20.879: LOG: Cannot load license file, file does not exist: C:\Documents and Settings\Administrador\Application Data\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat 12-Jan-2016 09:25:20.957: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2 12-Jan-2016 09:25:53.643: LOG: Cannot load license file, file does not exist: C:\Documents and Settings\Administrador\Application Data\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat 12-Jan-2016 09:25:53.768: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2 12-Jan-2016 09:26:34.329: LOG: Closing NefMoto VW Audi ME7 Flasher Logger 1.9.3.2 12-Jan-2016 09:26:42.219: LOG: Closing NefMoto VW Audi ME7 Flasher Logger 1.9.3.2 12-Jan-2016 09:28:40.825: LOG: Opening NefMoto VW Audi ME7 Flasher Logger 1.9.3.2 12-Jan-2016 09:28:41.309: LOG: Cannot load license file, file does not exist: C:\Documents and Settings\Administrador\Application Data\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat 12-Jan-2016 09:28:41.387: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2 12-Jan-2016 09:28:48.825: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F 12-Jan-2016 09:28:48.934: LOG: Opened FTDI device. 12-Jan-2016 09:28:48.934: LOG: FTDI device info - Description: USB <-> Serial Serial Number: Device Type: FT_DEVICE_BM ID: 0x4036001 Device Flags: 0x0 12-Jan-2016 09:28:48.934: LOG: FTDI ChipID DLL is loaded, checking chip ID... 12-Jan-2016 09:28:48.934: LOG: Unable to read FTDI device chip ID 12-Jan-2016 09:28:49.075: USER: Validated FTDI device is in dumb mode. 12-Jan-2016 09:28:49.153: LOG: Starting send receive thread. 12-Jan-2016 09:28:49.200: LOG: Send receive thread now started. 12-Jan-2016 09:28:49.215: USER: Disconnected 12-Jan-2016 09:28:49.934: LOG: Setting communication timings to defaults. 12-Jan-2016 09:28:49.950: LOG: Set timing parameters to defaults. 12-Jan-2016 09:28:49.950: USER: Connecting... 12-Jan-2016 09:28:50.043: LOG: Setting communication timings to defaults. 12-Jan-2016 09:28:50.059: USER: Starting slow init connection. 12-Jan-2016 09:28:52.668: USER: Connecting to address 0x01. 12-Jan-2016 09:28:55.075: USER: Slow init succeeded. 12-Jan-2016 09:28:55.075: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x0A 12-Jan-2016 09:28:55.075: USER: Switching to KWP1281 session. 12-Jan-2016 09:28:56.434: LOG: Failed to read KWP1281 block title byte. 12-Jan-2016 09:28:56.434: LOG: KWP1281 read block failed. 12-Jan-2016 09:28:56.434: USER: Failed to read KWP1281 connect info. 12-Jan-2016 09:28:57.934: USER: Connecting to address 0x01. 12-Jan-2016 09:29:00.356: USER: Slow init succeeded. 12-Jan-2016 09:29:01.715: LOG: Failed to read KWP1281 block title byte. 12-Jan-2016 09:29:01.715: LOG: KWP1281 read block failed. 12-Jan-2016 09:29:01.715: USER: Failed to read KWP1281 connect info. 12-Jan-2016 09:29:03.215: USER: Connecting to address 0x11. 12-Jan-2016 09:29:06.606: LOG: Failed to read address complement. 12-Jan-2016 09:29:06.731: USER: Slow init failed. 12-Jan-2016 09:29:06.731: USER: Disconnected 12-Jan-2016 09:29:06.887: LOG: Setting communication timings to defaults. 12-Jan-2016 09:29:06.887: USER: Connecting... 12-Jan-2016 09:29:07.043: LOG: Setting communication timings to defaults. 12-Jan-2016 09:29:07.043: USER: Starting slow init connection. 12-Jan-2016 09:29:09.652: USER: Connecting to address 0x01. 12-Jan-2016 09:29:12.074: USER: Slow init succeeded. 12-Jan-2016 09:29:13.434: LOG: Failed to read KWP1281 block title byte. 12-Jan-2016 09:29:13.434: LOG: KWP1281 read block failed. 12-Jan-2016 09:29:13.434: USER: Failed to read KWP1281 connect info. 12-Jan-2016 09:29:14.934: USER: Connecting to address 0x01. 12-Jan-2016 09:29:17.324: USER: Slow init succeeded. 12-Jan-2016 09:29:18.699: LOG: Failed to read KWP1281 block title byte. 12-Jan-2016 09:29:18.699: LOG: KWP1281 read block failed. 12-Jan-2016 09:29:18.699: USER: Failed to read KWP1281 connect info. 12-Jan-2016 09:29:20.199: USER: Connecting to address 0x11. 12-Jan-2016 09:29:23.574: LOG: Failed to read address complement. 12-Jan-2016 09:29:23.699: USER: Slow init failed. 12-Jan-2016 09:29:23.699: USER: Disconnected 12-Jan-2016 09:29:23.871: LOG: Setting communication timings to defaults. 12-Jan-2016 09:29:23.871: USER: Connecting... armageddon We ca try one saturday or one sunday, with my car or with ecu on bench Title: Re: Post by: pedrosousa on January 16, 2016, 10:02:36 AM Solved....
Today in car I had problems but then it connected and I could read the ecu... It's not the cable or ecu... it's a car wiring problem... |