Title: Cable issue?
Post by: armageddon on April 10, 2021, 08:36:15 AM
Hi all.
Was using the same ftdi based cable with nefmoto and me7logger since 2013 till mounth ago when it stop working/recognized
Prior to this, it was working flawless, both on car and on bench
I'm at the third cable (ft232rl) and can not get it to work, cable is recognized but can no get conection on nefmoto and with me7logger error 0x4.
On the bench it works fine though.
I am assuming that it's a cable fault , but who knows...
Title: Re: Cable issue?
Post by: armageddon on April 10, 2021, 03:11:29 PM
Additional info
Same cable, same car but different pc and it works fine in car.
What could cause this issue?
No modifications to car, same drivers as old cable, how can it not work on usual pc but works on other?
Title: Re: Cable issue?
Post by: vwaudiguy on April 10, 2021, 03:58:59 PM
Most likely a driver issue, or wrong com port specified.
Title: Re: Cable issue?
Post by: armageddon on April 10, 2021, 04:55:56 PM
Most likely a driver issue, or wrong com port specified.
I thought so, but then tested on bench and works fine.
Title: Re: Cable issue?
Post by: armageddon on April 12, 2021, 11:03:49 AM
Forgot to add the text Logged data size is 93 bytes.
Really logged are 50 entries with 93 bytes.
Start connecting to ECU at 10.04.2021 14:41:01.269
try connect slow(01)
KW1281: connect
kw1281_init: sync timeout waiting for 0x55
try connect slow(01)
KW1281: connect
kw1281_init: sync timeout waiting for 0x55
Could not connect
try connect slow(01)
14:41:09.016-641,8 os_setspeed(speed=10400)
KW1281: connect
14:41:09.031-516,1 os_receiver_off()
14:41:09.332-674,0 os_setbreak()
14:41:09.532-672,0 os_clrbreak()
14:41:09.732-672,0 os_setbreak()
14:41:09.932-674,5 os_setbreak()
14:41:10.132-672,5 os_setbreak()
14:41:10.332-672,5 os_setbreak()
14:41:10.532-671,5 os_setbreak()
14:41:10.732-672,5 os_setbreak()
14:41:10.932-673,0 os_setbreak()
14:41:11.132-671,5 os_clrbreak()
14:41:11.135-092,0 os_receiver_on()
14:41:11.738-708,4 os_rcvbyte(timeout=500) -> TIMEOUT
kw1281_init: sync timeout waiting for 0x55
try connect slow(01)
14:41:12.740-670,1 os_setspeed(speed=10400)
KW1281: connect
14:41:12.757-619,5 os_receiver_off()
14:41:13.058-879,5 os_setbreak()
14:41:13.258-881,1 os_clrbreak()
14:41:13.458-881,1 os_setbreak()
14:41:13.658-880,6 os_setbreak()
14:41:13.858-883,6 os_setbreak()
14:41:14.058-880,6 os_setbreak()
14:41:14.258-881,1 os_setbreak()
14:41:14.458-880,6 os_setbreak()
14:41:14.658-880,1 os_setbreak()
14:41:14.858-879,5 os_clrbreak()
14:41:14.862-092,5 os_receiver_on()
14:41:15.465-760,8 os_rcvbyte(timeout=500) -> TIMEOUT
kw1281_init: sync timeout waiting for 0x55
Could not connect
=> Could not connect to ECU, exiting ...
=> Logging failed
exiting (cause=0x4)...
Title: Re: Cable issue?
Post by: Blazius on April 12, 2021, 01:07:07 PM
Forgot to add the text Logged data size is 93 bytes.
Really logged are 50 entries with 93 bytes.
Start connecting to ECU at 10.04.2021 14:41:01.269
try connect slow(01)
KW1281: connect
kw1281_init: sync timeout waiting for 0x55
try connect slow(01)
KW1281: connect
kw1281_init: sync timeout waiting for 0x55
Could not connect
try connect slow(01)
14:41:09.016-641,8 os_setspeed(speed=10400)
KW1281: connect
14:41:09.031-516,1 os_receiver_off()
14:41:09.332-674,0 os_setbreak()
14:41:09.532-672,0 os_clrbreak()
14:41:09.732-672,0 os_setbreak()
14:41:09.932-674,5 os_setbreak()
14:41:10.132-672,5 os_setbreak()
14:41:10.332-672,5 os_setbreak()
14:41:10.532-671,5 os_setbreak()
14:41:10.732-672,5 os_setbreak()
14:41:10.932-673,0 os_setbreak()
14:41:11.132-671,5 os_clrbreak()
14:41:11.135-092,0 os_receiver_on()
14:41:11.738-708,4 os_rcvbyte(timeout=500) -> TIMEOUT
kw1281_init: sync timeout waiting for 0x55
try connect slow(01)
14:41:12.740-670,1 os_setspeed(speed=10400)
KW1281: connect
14:41:12.757-619,5 os_receiver_off()
14:41:13.058-879,5 os_setbreak()
14:41:13.258-881,1 os_clrbreak()
14:41:13.458-881,1 os_setbreak()
14:41:13.658-880,6 os_setbreak()
14:41:13.858-883,6 os_setbreak()
14:41:14.058-880,6 os_setbreak()
14:41:14.258-881,1 os_setbreak()
14:41:14.458-880,6 os_setbreak()
14:41:14.658-880,1 os_setbreak()
14:41:14.858-879,5 os_clrbreak()
14:41:14.862-092,5 os_receiver_on()
14:41:15.465-760,8 os_rcvbyte(timeout=500) -> TIMEOUT
kw1281_init: sync timeout waiting for 0x55
Could not connect
=> Could not connect to ECU, exiting ...
=> Logging failed
exiting (cause=0x4)... Try 0x00
Title: Re: Cable issue?
Post by: BlackT on April 12, 2021, 01:36:58 PM
Test cable latency with VCDS lite
Title: Re: Cable issue?
Post by: armageddon on April 13, 2021, 10:38:35 AM
Try 0x00
Already slow - 0x00 as has been since 2013 and with prj pach to be able to start log with engine running
Title: Re: Cable issue?
Post by: armageddon on April 13, 2021, 10:41:46 AM
Test cable latency with VCDS lite
Latency test is good at 4.5ms but cannot access to engine module, works fine on the other modules though. My other replica vcds works fine on all modules.
Title: Re: Cable issue?
Post by: BlackT on April 13, 2021, 12:31:57 PM
I was with same issue, bur my latency test was poor, than I buy BMW K+DCAN and since than no problems.
I think is best to make own cable
Title: Re: Cable issue?
Post by: armageddon on April 23, 2021, 11:45:24 AM
I was with same issue, bur my latency test was poor, than I buy BMW K+DCAN and since than no problems.
I think is best to make own cable
Good call on the bmw cable, mine arrived today and all works fine again. It was definitely the cables at fault, the 6 year old chinese kid was probably having a bad morning when made them Thanks
|