NefMoto

I've tries with a generic vag-com cable and my HEX-USB:

1.6.0.0 on a acer netbook running windows 7 starter:

05/Jan/2011 09:33:28.546: USER: Switching to KWP2000 session.
05/Jan/2011 09:33:28.608: LOG: Opened FTDI device.
05/Jan/2011 09:33:28.670: LOG: FTDI device info - Description: Ross-Tech HEX-USB Serial Number: RT000001 Device Type: FT_DEVICE_BM Device ID: 0x403FA20 Device Flags: 0x0
05/Jan/2011 09:33:28.670: LOG: FTDI ChipID DLL is loaded, checking chip ID...
05/Jan/2011 09:33:28.702: LOG: Unable to read FTDI device chip ID
05/Jan/2011 09:33:28.748: LOG: Starting send receive thread.
05/Jan/2011 09:33:28.795: LOG: Send receive thread now started.
05/Jan/2011 09:33:28.795: USER: Disconnected
05/Jan/2011 09:33:28.904: USER: Connection attempt number 1.
05/Jan/2011 09:33:28.920: USER: Connecting...
05/Jan/2011 09:33:29.263: USER: Connecting to address 0x01.
05/Jan/2011 09:33:31.603: LOG: Failed to read sync byte. Read 0 bytes.
05/Jan/2011 09:33:31.681: USER: Slow init failed.
05/Jan/2011 09:33:31.681: USER: Disconnected
05/Jan/2011 09:33:31.728: USER: Connection attempt number 2.
05/Jan/2011 09:33:31.744: USER: Connecting...
05/Jan/2011 09:33:32.165: USER: Connecting to address 0x01.
05/Jan/2011 09:33:34.364: USER: Slow init succeeded.
05/Jan/2011 09:33:34.396: USER: Switching to KWP1281 session.
05/Jan/2011 09:33:34.552: LOG: KWP1281 read block
05/Jan/2011 09:33:34.645: LOG: KWP1281 sent block
05/Jan/2011 09:33:34.910: LOG: KWP1281 read block
05/Jan/2011 09:33:35.035: LOG: KWP1281 sent block
05/Jan/2011 09:33:35.144: LOG: KWP1281 read block
05/Jan/2011 09:33:35.238: LOG: KWP1281 sent block
05/Jan/2011 09:33:35.363: LOG: KWP1281 read block
05/Jan/2011 09:33:35.488: LOG: KWP1281 sent block
05/Jan/2011 09:33:35.519: LOG: KWP1281 read block
05/Jan/2011 09:33:35.675: LOG: KWP1281 sent block
05/Jan/2011 09:33:35.690: USER: KWP1281 connect info: ?6A906032KR 1.8l 5VT NB AG4 G04 4743   B
05/Jan/2011 09:33:37.235: USER: Connecting to address 0x01.
05/Jan/2011 09:33:39.450: USER: Slow init succeeded.
05/Jan/2011 09:33:39.637: LOG: KWP1281 read block
05/Jan/2011 09:33:39.700: LOG: KWP1281 sent block
05/Jan/2011 09:33:40.043: LOG: KWP1281 read block
05/Jan/2011 09:33:40.105: LOG: KWP1281 sent block
05/Jan/2011 09:33:40.277: LOG: KWP1281 read block
05/Jan/2011 09:33:40.339: LOG: KWP1281 sent block
05/Jan/2011 09:33:40.495: LOG: KWP1281 read block
05/Jan/2011 09:33:40.558: LOG: KWP1281 sent block
05/Jan/2011 09:33:40.682: LOG: Final byte of KWP1281 message was not block end byte.
05/Jan/2011 09:33:40.698: LOG: KWP1281 read block failed.
05/Jan/2011 09:33:40.729: USER: Failed to read KWP1281 connect info.
05/Jan/2011 09:33:42.227: USER: Connecting to address 0x11.
05/Jan/2011 09:33:44.426: USER: Slow init succeeded.
05/Jan/2011 09:33:44.442: USER: Switching to KWP2000 session.
05/Jan/2011 09:33:44.816: LOG: Sent message with service ID StartCommunication
05/Jan/2011 09:33:44.863: LOG: Received message with service ID StartCommunicationPositiveResponse
05/Jan/2011 09:33:44.879: USER: Connected
05/Jan/2011 09:33:47.390: LOG: Sent message with service ID TesterPresent
05/Jan/2011 09:33:47.453: LOG: Resending message. Send attempts: 2
05/Jan/2011 09:33:47.468: LOG: Sent message with service ID TesterPresent
05/Jan/2011 09:33:47.546: LOG: Resending message. Send attempts: 3
05/Jan/2011 09:33:47.562: LOG: Sent message with service ID TesterPresent
05/Jan/2011 09:33:47.624: LOG: Failed to send message 3 times, message send failed.
05/Jan/2011 09:33:47.640: USER: Disconnecting because no response was received for the Tester Present message.
05/Jan/2011 09:33:47.749: USER: Disconnected
05/Jan/2011 09:33:47.796: LOG: Closing FTDI device.
05/Jan/2011 09:33:47.827: LOG: Send receive thread now terminated.





05/Jan/2011 09:33:50.276: USER: Switching to KWP2000 session.
05/Jan/2011 09:33:50.401: LOG: Opened FTDI device.
05/Jan/2011 09:33:50.401: LOG: FTDI device info - Description: Ross-Tech HEX-USB Serial Number: RT000001 Device Type: FT_DEVICE_BM Device ID: 0x403FA20 Device Flags: 0x0
05/Jan/2011 09:33:50.448: LOG: FTDI ChipID DLL is loaded, checking chip ID...
05/Jan/2011 09:33:50.448: LOG: Unable to read FTDI device chip ID
05/Jan/2011 09:33:50.510: LOG: Starting send receive thread.
05/Jan/2011 09:33:50.510: LOG: Send receive thread now started.
05/Jan/2011 09:33:50.651: USER: Disconnected
05/Jan/2011 09:33:50.666: USER: Connection attempt number 1.
05/Jan/2011 09:33:50.713: USER: Connecting...
05/Jan/2011 09:33:50.713: USER: Connecting to address 0x01.
05/Jan/2011 09:33:51.150: LOG: Sent message with service ID StartCommunication
05/Jan/2011 09:33:51.150: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
05/Jan/2011 09:33:51.181: USER: Fast init succeeded.
05/Jan/2011 09:33:51.212: LOG: Failed to send message 1 times, message send failed.
05/Jan/2011 09:33:51.275: USER: Disconnected
05/Jan/2011 09:33:51.306: USER: Connection attempt number 2.
05/Jan/2011 09:33:51.337: USER: Connecting...
05/Jan/2011 09:33:51.353: USER: Connecting to address 0x01.
05/Jan/2011 09:33:51.774: LOG: Sent message with service ID StartCommunication
05/Jan/2011 09:33:51.774: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
05/Jan/2011 09:33:51.868: USER: Fast init succeeded.
05/Jan/2011 09:33:51.868: LOG: Failed to send message 1 times, message send failed.
05/Jan/2011 09:33:51.883: USER: Disconnected
05/Jan/2011 09:33:51.930: USER: Connection attempt number 3.
05/Jan/2011 09:33:51.946: USER: Connecting...
05/Jan/2011 09:33:51.961: USER: Connecting to address 0x01.
05/Jan/2011 09:33:52.460: LOG: Sent message with service ID StartCommunication
05/Jan/2011 09:33:52.460: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
05/Jan/2011 09:33:52.538: USER: Fast init succeeded.
05/Jan/2011 09:33:52.538: LOG: Failed to send message 1 times, message send failed.
05/Jan/2011 09:33:52.601: USER: Disconnected
05/Jan/2011 09:33:52.632: LOG: Closing FTDI device.
05/Jan/2011 09:33:52.679: LOG: Send receive thread now terminated.

Version 1.6.1.0 should hopefully fix this issue, but I'm not positive.

I will be releasing a new version of 1.6.1.0 tonight that should work for more people if you have already tried it.