q_dubz
Full Member
Karma: +3/-0
 Offline
Posts: 154
|
 |
« on: September 25, 2015, 12:19:08 PM »
|
|
|
Cable: ROSS-TECH HEX+CAN (Dual-K&CAN<->USB) Drivers: FTDI v.2.12.06 -VCP Enabled -Set as COM2 OS: Windows10 **VCDS Boot Intelligent Mode: UNCHECKED** Tested, Saved NEFMOTO Flasher/Logger Recognizes Cable bu fails to connect via Fast Init or Slow Init: 25/Sep/2015 02:22:37.202: LOG: Opened FTDI device.
25/Sep/2015 02:22:37.207: LOG: FTDI device info - Description: Ross-Tech HEX-USB Serial Number: RT000001 Device Type: FT_DEVICE_232R ID: 0x403FA24 Device Flags: 0x0
25/Sep/2015 02:22:37.207: LOG: FTDI ChipID DLL is loaded, checking chip ID...
25/Sep/2015 02:22:37.214: LOG: FTDI device chip ID: 0x531F2ED9
25/Sep/2015 02:22:37.245: LOG: Starting send receive thread.
25/Sep/2015 02:22:37.247: LOG: Send receive thread now started.
25/Sep/2015 02:22:37.248: USER: Disconnected
25/Sep/2015 02:22:37.296: LOG: Setting communication timings to defaults.
25/Sep/2015 02:22:37.297: USER: Connecting...
25/Sep/2015 02:22:37.342: LOG: Setting communication timings to defaults.
25/Sep/2015 02:22:37.352: USER: Starting slow init connection.
25/Sep/2015 02:22:39.954: USER: Connecting to address 0x02.
25/Sep/2015 02:22:42.783: LOG: Failed to read sync byte, guessing baud rate is actually 9600.
25/Sep/2015 02:22:42.825: LOG: Not enough key bytes, read: 0
25/Sep/2015 02:22:42.841: USER: Slow init failed.
25/Sep/2015 02:22:42.842: USER: Disconnected ME7Logger also fails to connect though i'm unsure if it's seeing the cable or not: -> Reading log config file C:\Users\Quintin R. Callahan\Documents\ME7Logger\logs\stock2.cfg .... done
-> Reading ecu characteristics file C:\Users\Quintin R. Callahan\Documents\ME7Logger\ecus\Stock.ecu .... done
Used Ecu definition is:
[Communication]
Connect = SLOW-0x11
Communicate = HM0
LogSpeed = 56000
[Identification]
HWNumber = "0261208443"
SWNumber = "1037374043"
PartNumber = "8E0910560K"
SWVersion = "0010"
EngineId = "4.2L V8/5V"
Logged variables are:
#no.: name , alias , addr ,sz, bitm, S, I, A , B, unit
#------------------------------------------------------------------------------------------------------------
#001: lamsoni_w , AirFuelRatioCurrent , 00CDC0, 2, 0000, 0, 0, 0.000244141, 0, '-'
#002: mdverl_w , EngineLossTorque , 00CCB8, 2, 0000, 0, 0, 0.00152588, 0, '%'
#003: mrfa_w , DriverRequestedRelTorque , 00CC52, 2, 0000, 0, 0, 0.00305176, 0, '%'
#004: nmot , EngineSpeed , 00F370, 1, 0000, 0, 0, 40, 0, 'rpm'
#005: pus_w , BaroPressure , 385248, 2, 0000, 0, 0, 0.0390625, 0, 'mbar'
#006: pvdkds_w , BoostPressureActual , 00C7D0, 2, 0000, 0, 0, 0.0390625, 0, 'mbar'
Logged data size is 11 bytes.
Really logged are 6 entries with 11 bytes.
Start connecting to ECU at 25.09.2015 14:30:06.300
try connect slow(11)
try connect slow(11)
Could not connect
try connect slow(11)
14:30:11.851-810,8 os_setspeed(speed=10400)
14:30:11.862-540,0 os_receiver_off()
14:30:12.163-449,2 os_setbreak()
14:30:12.363-451,2 os_clrbreak()
14:30:12.563-450,3 os_setbreak()
14:30:12.763-450,4 os_setbreak()
14:30:12.968-403,9 os_setbreak()
14:30:13.163-450,5 os_clrbreak()
14:30:13.363-721,9 os_setbreak()
14:30:13.563-450,7 os_setbreak()
14:30:13.763-450,7 os_setbreak()
14:30:13.963-451,3 os_clrbreak()
14:30:13.966-486,8 os_receiver_on()
14:30:14.488-159,2 os_rcvbyte(timeout=500) -> TIMEOUT
try connect slow(11)
14:30:14.489-475,3 os_setspeed(speed=10400)
14:30:14.500-425,4 os_receiver_off()
14:30:14.801-213,8 os_setbreak()
14:30:15.001-215,9 os_clrbreak()
14:30:15.201-215,0 os_setbreak()
14:30:15.401-216,0 os_setbreak()
14:30:15.601-215,6 os_setbreak()
14:30:15.801-216,6 os_clrbreak()
14:30:16.001-377,1 os_setbreak()
14:30:16.201-215,8 os_setbreak()
14:30:16.401-215,4 os_setbreak()
14:30:16.601-215,4 os_clrbreak()
14:30:16.604-433,8 os_receiver_on()
14:30:17.118-696,6 os_rcvbyte(timeout=500) -> TIMEOUT
Could not connect
=> Could not connect to ECU, exiting ...
=> Logging failed
exiting (cause=0x4)... I don't think i've missed anything or if i need to do anything else as a last resort? Ideas? |
|
|
|
« Last Edit: September 25, 2015, 03:15:11 PM by q_dubz »
|
Logged
|
|
|
|
A4Rich
Full Member
Karma: +10/-0
Offline
Posts: 116
|
|
« Reply #1 on: September 25, 2015, 12:33:03 PM »
|
|
|
Cable: ROSS-TECH HEX+CAN (Dual-K&CAN<->USB) Drivers: FTDI v.2.12.06 -VCP Enabled -Set as COM2 OS: Windows10 **VCDS Boot Intelligent Mode: UNCHECKED** Tested, Saved NEFMOTO Flasher/Logger Recognizes Cable bu fails to connect via Fast Init or Slow Init: 25/Sep/2015 02:22:37.202: LOG: Opened FTDI device.
25/Sep/2015 02:22:37.207: LOG: FTDI device info - Description: Ross-Tech HEX-USB Serial Number: RT000001 Device Type: FT_DEVICE_232R ID: 0x403FA24 Device Flags: 0x0
25/Sep/2015 02:22:37.207: LOG: FTDI ChipID DLL is loaded, checking chip ID...
25/Sep/2015 02:22:37.214: LOG: FTDI device chip ID: 0x531F2ED9
25/Sep/2015 02:22:37.245: LOG: Starting send receive thread.
25/Sep/2015 02:22:37.247: LOG: Send receive thread now started.
25/Sep/2015 02:22:37.248: USER: Disconnected
25/Sep/2015 02:22:37.296: LOG: Setting communication timings to defaults.
25/Sep/2015 02:22:37.297: USER: Connecting...
25/Sep/2015 02:22:37.342: LOG: Setting communication timings to defaults.
25/Sep/2015 02:22:37.352: USER: Starting slow init connection.
25/Sep/2015 02:22:39.954: USER: Connecting to address 0x02.
25/Sep/2015 02:22:42.783: LOG: Failed to read sync byte, guessing baud rate is actually 9600.
25/Sep/2015 02:22:42.825: LOG: Not enough key bytes, read: 0
25/Sep/2015 02:22:42.841: USER: Slow init failed.
25/Sep/2015 02:22:42.842: USER: Disconnected ME7Logger also fails to connect though i'm unsure if it's seeing the cable or not: -> Reading log config file C:\Users\Quintin R. Callahan\Documents\ME7Logger\logs\stock2.cfg .... done
-> Reading ecu characteristics file C:\Users\Quintin R. Callahan\Documents\ME7Logger\ecus\Stock.ecu .... done
Used Ecu definition is:
[Communication]
Connect = SLOW-0x11
Communicate = HM0
LogSpeed = 56000
[Identification]
HWNumber = "0261208443"
SWNumber = "1037374043"
PartNumber = "8E0910560K"
SWVersion = "0010"
EngineId = "4.2L V8/5V"
Logged variables are:
#no.: name , alias , addr ,sz, bitm, S, I, A , B, unit
#------------------------------------------------------------------------------------------------------------
#001: lamsoni_w , AirFuelRatioCurrent , 00CDC0, 2, 0000, 0, 0, 0.000244141, 0, '-'
#002: mdverl_w , EngineLossTorque , 00CCB8, 2, 0000, 0, 0, 0.00152588, 0, '%'
#003: mrfa_w , DriverRequestedRelTorque , 00CC52, 2, 0000, 0, 0, 0.00305176, 0, '%'
#004: nmot , EngineSpeed , 00F370, 1, 0000, 0, 0, 40, 0, 'rpm'
#005: pus_w , BaroPressure , 385248, 2, 0000, 0, 0, 0.0390625, 0, 'mbar'
#006: pvdkds_w , BoostPressureActual , 00C7D0, 2, 0000, 0, 0, 0.0390625, 0, 'mbar'
Logged data size is 11 bytes.
Really logged are 6 entries with 11 bytes.
Start connecting to ECU at 25.09.2015 14:30:06.300
try connect slow(11)
try connect slow(11)
Could not connect
try connect slow(11)
14:30:11.851-810,8 os_setspeed(speed=10400)
14:30:11.862-540,0 os_receiver_off()
14:30:12.163-449,2 os_setbreak()
14:30:12.363-451,2 os_clrbreak()
14:30:12.563-450,3 os_setbreak()
14:30:12.763-450,4 os_setbreak()
14:30:12.968-403,9 os_setbreak()
14:30:13.163-450,5 os_clrbreak()
14:30:13.363-721,9 os_setbreak()
14:30:13.563-450,7 os_setbreak()
14:30:13.763-450,7 os_setbreak()
14:30:13.963-451,3 os_clrbreak()
14:30:13.966-486,8 os_receiver_on()
14:30:14.488-159,2 os_rcvbyte(timeout=500) -> TIMEOUT
try connect slow(11)
14:30:14.489-475,3 os_setspeed(speed=10400)
14:30:14.500-425,4 os_receiver_off()
14:30:14.801-213,8 os_setbreak()
14:30:15.001-215,9 os_clrbreak()
14:30:15.201-215,0 os_setbreak()
14:30:15.401-216,0 os_setbreak()
14:30:15.601-215,6 os_setbreak()
14:30:15.801-216,6 os_clrbreak()
14:30:16.001-377,1 os_setbreak()
14:30:16.201-215,8 os_setbreak()
14:30:16.401-215,4 os_setbreak()
14:30:16.601-215,4 os_clrbreak()
14:30:16.604-433,8 os_receiver_on()
14:30:17.118-696,6 os_rcvbyte(timeout=500) -> TIMEOUT
Could not connect
=> Could not connect to ECU, exiting ...
=> Logging failed
exiting (cause=0x4)... I don't think i've missed anything or if i need to do anything else as a last resort? Ideas? I could never get the FTDI drivers to work with my VCDS cable had to install the Ross-Tech drivers, see here. |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #2 on: September 25, 2015, 12:58:59 PM »
|
|
|
I could never get the FTDI drivers to work with my VCDS cable had to install the Ross-Tech drivers, see here. AGREED! Use the Ross-tech VCP driver! |
|
|
|
|
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
|
|
|
q_dubz
Full Member
Karma: +3/-0
Offline
Posts: 154
|
|
« Reply #3 on: September 25, 2015, 01:00:14 PM »
|
|
|
Yep, i tried the ROSS-TECH VCP Driver as well. Gonna restart the computer here and try again
|
|
|
|
|
Logged
|
|
|
|
q_dubz
Full Member
Karma: +3/-0
Offline
Posts: 154
|
|
« Reply #4 on: September 25, 2015, 01:09:47 PM »
|
|
|
no dice  |
|
|
|
|
Logged
|
|
|
|
A4Rich
Full Member
Karma: +10/-0
Offline
Posts: 116
|
|
« Reply #5 on: September 25, 2015, 01:51:54 PM »
|
|
|
IIRC I had to mess around with the driver after installation. If you didn't follow the instruction here with the Ross Tech driver, try again. |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #6 on: September 25, 2015, 01:54:52 PM »
|
|
|
BTW, from experience, ME7L works better through the virtual com port than directly to the RossTech USB interface api.
In any case, get VCDS working first, then nef, then ME7l thru com (vcp)
|
|
|
|
|
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
|
|
|
q_dubz
Full Member
Karma: +3/-0
Offline
Posts: 154
|
|
« Reply #7 on: September 25, 2015, 02:17:36 PM »
|
|
|
Yep, i installed the drivers properly. VCDS Works. Nef sees and can read the cable, but i cant establish a connection. ME7L doesn't even let me know if it can see the cable  |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #8 on: September 25, 2015, 02:58:42 PM »
|
|
|
Could be nef and me7 are not compatible with that ecu. Anyway, its just the v8.. Almost no tuning does much on that motor
|
|
|
|
|
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
|
|
|
q_dubz
Full Member
Karma: +3/-0
Offline
Posts: 154
|
|
« Reply #9 on: September 25, 2015, 03:17:32 PM »
|
|
|
Could be nef and me7 are not compatible with that ecu. Anyway, its just the v8.. Almost no tuning does much on that motor
mine's not just a v8 lol Anyway I FIGURED IT OUT. Went back into the CMD and did the whole -c connection parameters bit and found out it was the address/speed. ME7L GUI doesnt offer a way to change the address, unless i just dont know how. Visual ME7L and Nef Flash/Log do! So i was able to establish a connection. *wipes brow* Thanks for all the input in this thread.  |
|
|
|
|
Logged
|
|
|
|
|
