|
RomRaider
Documentation
Community
Developers
|
|
Page 1 of 1
|
[ 13 posts ] |
|
| Author |
Message |
|
mickeyd2005
|
Post subject: Does CEL on CANBUS ecu's affect cable connectivity Posted: Fri Dec 12, 2008 8:17 pm |
|
 |
| Administrator |
 |
Joined: Wed Oct 25, 2006 4:32 am Posts: 3040
|
|
A friend overboosted while datalogging. He hit fuel cut and triggered a CEL.
The cable seems to have trouble connecting now. He tried to do a learning view and he also tried to read the existing rom in his ecu. Both attempts failed.
His car is a 2008 WRX.
I've never heard of this problem before. It's definitely not a problem on the previous cars. Is this just a coincidence? One off? Or have other people had this problem?
|
|
| Top |
|
 |
|
merchgod
|
Post subject: Re: Does CEL on CANBUS ecu's affect cable connectivity Posted: Fri Dec 12, 2008 10:07 pm |
|
 |
| RomRaider Donator |
 |
Joined: Thu Mar 30, 2006 2:38 am Posts: 5336
|
|
see if he can post the learning view log
|
|
| Top |
|
 |
|
mickeyd2005
|
Post subject: Re: Does CEL on CANBUS ecu's affect cable connectivity Posted: Sat Dec 13, 2008 3:53 pm |
|
 |
| Administrator |
 |
Joined: Wed Oct 25, 2006 4:32 am Posts: 3040
|
After a couple of drive cycles, the CEL turned off but the P0244 code was still in the ecu. He read it and cleared it and then did a learning view. Unfortunately, the log he sent me appears to be the one after it read correctly. Code: [07:19:50.8825000] Learning View version 0.4a [07:19:54.4137500] PassThruOpen returned 7 and DeviceID 0 [07:19:54.4137500] PassThruGetLastError returned 7, Message: device not responding [07:19:54.5543750] COM3 open [07:19:54.6012500] ECU Init [07:19:54.6012500] WRITE 6 bytes: 80 10 F0 01 BF 40 [07:19:54.6793750] READ 0 bytes: [07:20:02.7262500] No response to ECU Init [07:20:02.7575000] COM3 closed
[07:20:05.7887500] PassThruOpen returned 0 and DeviceID 2 [07:20:05.7887500] PassThruReadVersion returned 0 [07:20:05.7887500] Device firmware version: 1.01.2145 [07:20:05.8043750] DLL version: 0.50.2176 Oct 20 2008 17:50:12 [07:20:05.8043750] API version: 04.04 [07:20:05.8356250] PassThruConnect returned 0 and ChannelID 3 [07:20:05.8668750] PassThruStartMsgFilter returned 0 [07:20:05.8668750] ECU Init [07:20:05.9293750] PassThruWriteMsgs returned 0 [07:20:05.9450000] WRITE 6 bytes: 80 10 F0 01 BF 40 [07:20:05.9918750] PassThruReadMsgs returned 0 [07:20:05.9918750] READ 0 bytes [07:20:06.1950000] PassThruReadMsgs returned 0 [07:20:06.1950000] READ 116 bytes: 80 10 F0 01 BF 40 80 F0 10 69 FF A2 10 11 51 12 58 41 07 F3 FA C9 8E 0B 81 FE AC 00 00 00 66 CE 54 F9 B1 E4 00 1F 20 00 00 00 00 00 DC 00 00 5D 1F 30 80 F0 E6 00 00 43 FB 00 F5 C1 86 00 00 00 01 FD F1 80 00 81 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 45 [07:20:06.7106250] ECU supported (ECUID:5112584107 CALID:AZ1E401A DESC:08 USDM Impreza WRX MT) [07:20:06.7106250] FLKC load [07:20:06.7887500] PassThruWriteMsgs returned 0 [07:20:06.7887500] WRITE 11 bytes: 80 10 F0 06 A0 00 0C EC 0C 0F 39 [07:20:06.8356250] PassThruReadMsgs returned 0 [07:20:06.8356250] READ 0 bytes [07:20:06.8668750] PassThruReadMsgs returned 0 [07:20:06.8668750] READ 33 bytes: 80 10 F0 06 A0 00 0C EC 0C 0F 39 80 F0 10 11 E0 3F A6 66 66 3F D1 EB 85 40 00 00 00 40 13 33 33 9B [07:20:06.8668750] FLKC RPM [07:20:06.9450000] PassThruWriteMsgs returned 0 [07:20:06.9606250] WRITE 11 bytes: 80 10 F0 06 A0 00 0C EB F0 17 24 [07:20:06.9918750] PassThruReadMsgs returned 0 [07:20:07.0075000] READ 0 bytes [07:20:07.0387500] PassThruReadMsgs returned 0 [07:20:07.0387500] READ 41 bytes: 80 10 F0 06 A0 00 0C EB F0 17 24 80 F0 10 19 E0 45 16 00 00 45 3B 80 00 45 61 00 00 45 83 40 00 45 96 00 00 45 A2 80 00 C4 [07:20:07.0387500] IAM [07:20:07.1325000] PassThruWriteMsgs returned 0 [07:20:07.1325000] WRITE 11 bytes: 80 10 F0 06 A0 00 FF 2F DC 03 33 [07:20:07.1637500] PassThruReadMsgs returned 0 [07:20:07.1637500] READ 0 bytes [07:20:07.1637500] PassThruReadMsgs returned 0 [07:20:07.1637500] READ 21 bytes: 80 10 F0 06 A0 00 FF 2F DC 03 33 80 F0 10 05 E0 3F 80 00 00 24 [07:20:07.1637500] A/F Learning airflow [07:20:07.2575000] PassThruWriteMsgs returned 0 [07:20:07.2575000] WRITE 11 bytes: 80 10 F0 06 A0 00 0C 85 C0 0B 82 [07:20:07.3200000] PassThruReadMsgs returned 0 [07:20:07.3200000] READ 0 bytes [07:20:07.3356250] PassThruReadMsgs returned 0 [07:20:07.3356250] READ 29 bytes: 80 10 F0 06 A0 00 0C 85 C0 0B 82 80 F0 10 0D E0 40 B3 33 33 41 20 00 00 42 20 00 00 89 [07:20:07.3356250] A/F Learning #1 [07:20:07.4137500] PassThruWriteMsgs returned 0 [07:20:07.4293750] WRITE 11 bytes: 80 10 F0 06 A0 00 FF 2F 48 1F BB [07:20:07.4762500] PassThruReadMsgs returned 0 [07:20:07.4762500] READ 0 bytes [07:20:07.5231250] PassThruReadMsgs returned 0 [07:20:07.5231250] READ 49 bytes: 80 10 F0 06 A0 00 FF 2F 48 1F BB 80 F0 10 21 E0 BC 13 73 79 D0 73 D0 73 BC E5 60 32 E2 E8 E2 E8 BC AC 08 1F 3B 34 3B 34 3A 83 12 6E B3 0E B3 0E B5 [07:20:07.5387500] FLKC data [07:20:07.6168750] PassThruWriteMsgs returned 0 [07:20:07.6168750] WRITE 11 bytes: 80 10 F0 06 A0 00 FF 2F F0 1F 63 [07:20:07.6950000] PassThruReadMsgs returned 0 [07:20:07.6950000] READ 0 bytes [07:20:07.7106250] PassThruReadMsgs returned 0 [07:20:07.7106250] READ 49 bytes: 80 10 F0 06 A0 00 FF 2F F0 1F 63 80 F0 10 21 E0 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 71 [07:20:07.7262500] FLKC data [07:20:07.8043750] PassThruWriteMsgs returned 0 [07:20:07.8043750] WRITE 11 bytes: 80 10 F0 06 A0 00 FF 30 10 1F 84 [07:20:07.8512500] PassThruReadMsgs returned 0 [07:20:07.8668750] READ 0 bytes [07:20:07.9137500] PassThruReadMsgs returned 0 [07:20:07.9137500] READ 49 bytes: 80 10 F0 06 A0 00 FF 30 10 1F 84 80 F0 10 21 E0 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 71 [07:20:07.9137500] FLKC data [07:20:07.9918750] PassThruWriteMsgs returned 0 [07:20:07.9918750] WRITE 11 bytes: 80 10 F0 06 A0 00 FF 30 30 1F A4 [07:20:08.0543750] PassThruReadMsgs returned 0 [07:20:08.0543750] READ 0 bytes [07:20:08.1012500] PassThruReadMsgs returned 0 [07:20:08.1012500] READ 49 bytes: 80 10 F0 06 A0 00 FF 30 30 1F A4 80 F0 10 21 E0 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 71 [07:20:08.1168750] FLKC data [07:20:08.1950000] PassThruWriteMsgs returned 0 [07:20:08.1950000] WRITE 11 bytes: 80 10 F0 06 A0 00 FF 30 50 1F C4 [07:20:08.2418750] PassThruReadMsgs returned 0 [07:20:08.2418750] READ 0 bytes [07:20:08.2887500] PassThruReadMsgs returned 0 [07:20:08.3043750] READ 49 bytes: 80 10 F0 06 A0 00 FF 30 50 1F C4 80 F0 10 21 E0 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 71 [07:20:08.3043750] FLKC data [07:20:08.3825000] PassThruWriteMsgs returned 0 [07:20:08.3981250] WRITE 11 bytes: 80 10 F0 06 A0 00 FF 30 70 1F E4 [07:20:08.4450000] PassThruReadMsgs returned 0 [07:20:08.4450000] READ 0 bytes [07:20:08.4918750] PassThruReadMsgs returned 0 [07:20:08.4918750] READ 49 bytes: 80 10 F0 06 A0 00 FF 30 70 1F E4 80 F0 10 21 E0 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 71 [07:20:08.5075000] FLKC data [07:20:08.5856250] PassThruWriteMsgs returned 0 [07:20:08.5856250] WRITE 11 bytes: 80 10 F0 06 A0 00 FF 30 90 1F 04 [07:20:08.6168750] PassThruReadMsgs returned 0 [07:20:08.6325000] READ 0 bytes [07:20:08.6950000] PassThruReadMsgs returned 0 [07:20:08.6950000] READ 49 bytes: 80 10 F0 06 A0 00 FF 30 90 1F 04 80 F0 10 21 E0 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 71 [07:20:08.7106250] FLKC data [07:20:08.7887500] PassThruWriteMsgs returned 0 [07:20:08.7887500] WRITE 11 bytes: 80 10 F0 06 A0 00 FF 30 B0 1F 24 [07:20:08.8356250] PassThruReadMsgs returned 0 [07:20:08.8356250] READ 0 bytes [07:20:08.8981250] PassThruReadMsgs returned 0 [07:20:08.9137500] READ 49 bytes: 80 10 F0 06 A0 00 FF 30 B0 1F 24 80 F0 10 21 E0 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 71 [07:20:08.9137500] FLKC data [07:20:08.9918750] PassThruWriteMsgs returned 0 [07:20:08.9918750] WRITE 11 bytes: 80 10 F0 06 A0 00 FF 30 D0 1F 44 [07:20:09.0387500] PassThruReadMsgs returned 0 [07:20:09.0387500] READ 0 bytes [07:20:09.1012500] PassThruReadMsgs returned 0 [07:20:09.1012500] READ 49 bytes: 80 10 F0 06 A0 00 FF 30 D0 1F 44 80 F0 10 21 E0 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 71 [07:20:09.1012500] FLKC data [07:20:09.1950000] PassThruWriteMsgs returned 0 [07:20:09.1950000] WRITE 11 bytes: 80 10 F0 06 A0 00 FF 30 F0 17 5C [07:20:09.2262500] PassThruReadMsgs returned 0 [07:20:09.2418750] READ 0 bytes [07:20:09.2731250] PassThruReadMsgs returned 0 [07:20:09.2731250] READ 41 bytes: 80 10 F0 06 A0 00 FF 30 F0 17 5C 80 F0 10 19 E0 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 00 00 00 00 FF FF FF FF 6D [07:20:09.3512500] PassThruDisconnect returned 0 [07:20:09.3981250] PassThruClose returned 0
|
|
| Top |
|
 |
|
merchgod
|
Post subject: Re: Does CEL on CANBUS ecu's affect cable connectivity Posted: Sat Dec 13, 2008 11:25 pm |
|
 |
| RomRaider Donator |
 |
Joined: Thu Mar 30, 2006 2:38 am Posts: 5336
|
|
| Top |
|
 |
|
mickeyd2005
|
Post subject: Re: Does CEL on CANBUS ecu's affect cable connectivity Posted: Sun Dec 14, 2008 2:07 am |
|
 |
| Administrator |
 |
Joined: Wed Oct 25, 2006 4:32 am Posts: 3040
|
|
I think it was just coincidence. It turns out the connectivity is spotty. Sometimes, he can't connect with learning viewer. I asked him to get a log after it doesn't connect next time.
|
|
| Top |
|
 |
|
merchgod
|
Post subject: Re: Does CEL on CANBUS ecu's affect cable connectivity Posted: Sun Dec 14, 2008 12:29 pm |
|
 |
| RomRaider Donator |
 |
Joined: Thu Mar 30, 2006 2:38 am Posts: 5336
|
|
The first portion of the log is failed read, but I'm assuming that was just a prior attempt where he didn't have the ignition on or something.
|
|
| Top |
|
 |
|
mickeyd2005
|
Post subject: Re: Does CEL on CANBUS ecu's affect cable connectivity Posted: Sun Dec 14, 2008 4:50 pm |
|
 |
| Administrator |
 |
Joined: Wed Oct 25, 2006 4:32 am Posts: 3040
|
|
Yeah, the failed attempt was the night before.
|
|
| Top |
|
 |
|
merchgod
|
Post subject: Re: Does CEL on CANBUS ecu's affect cable connectivity Posted: Sun Dec 14, 2008 4:56 pm |
|
 |
| RomRaider Donator |
 |
Joined: Thu Mar 30, 2006 2:38 am Posts: 5336
|
|
It can't be - you can see the time in the log. It was right before the 2nd attempt. Plus the log is cleared everytime you run LV.
|
|
| Top |
|
 |
|
mickeyd2005
|
Post subject: Re: Does CEL on CANBUS ecu's affect cable connectivity Posted: Sun Dec 14, 2008 7:11 pm |
|
 |
| Administrator |
 |
Joined: Wed Oct 25, 2006 4:32 am Posts: 3040
|
|
I wrote that poorly. I meant, the log that I asked him to get was for the log the night before. He didn't do it. Instead, he immediately went to connection.
The current log that I posted is the good read like you stated.
|
|
| Top |
|
 |
|
mickeyd2005
|
Post subject: Re: Does CEL on CANBUS ecu's affect cable connectivity Posted: Sat Dec 20, 2008 7:02 am |
|
 |
| Administrator |
 |
Joined: Wed Oct 25, 2006 4:32 am Posts: 3040
|
Here's a log where he couldn't connect. Code: [21:51:40.0748750] Learning View version 0.4a [21:51:42.6373750] PassThruOpen returned 7 and DeviceID 0 [21:51:42.6373750] PassThruGetLastError returned 7, Message: device not responding [21:51:42.7936250] COM3 open [21:51:42.8248750] ECU Init [21:51:42.8561250] WRITE 6 bytes: 80 10 F0 01 BF 40 [21:51:42.9498750] READ 0 bytes: [21:51:51.5123750] No response to ECU Init [21:51:51.5436250] COM3 closed [22:25:37.1998750] Learning View version 0.4a [22:25:39.5905000] PassThruOpen returned 8 and DeviceID 0 [22:25:39.6061250] PassThruGetLastError returned 8, Message: unable to opsen device [22:25:39.7311250] COM3 open [22:25:39.7623750] ECU Init [22:25:39.7780000] WRITE 6 bytes: 80 10 F0 01 BF 40 [22:25:39.8561250] READ 0 bytes: [22:25:43.6998750] No response to ECU Init [22:25:43.7311250] COM3 closed
[22:26:02.7623750] PassThruOpen returned 8 and DeviceID 0 [22:26:02.7780000] PassThruGetLastError returned 8, Message: unable to opsen device [22:26:02.8873750] COM3 open [22:26:02.8873750] ECU Init [22:26:02.9030000] WRITE 6 bytes: 80 10 F0 01 BF 40 [22:26:02.9498750] READ 0 bytes: [22:26:05.4186250] No response to ECU Init [22:26:05.6061250] COM3 closed
It seems like the OP 2.0 cable can sometimes be flaky.
|
|
| Top |
|
 |
|
merchgod
|
Post subject: Re: Does CEL on CANBUS ecu's affect cable connectivity Posted: Sat Dec 20, 2008 9:59 am |
|
 |
| RomRaider Donator |
 |
Joined: Thu Mar 30, 2006 2:38 am Posts: 5336
|
|
I don't think I've seen that particular error message before. If it is Vista, try having him run LV as admin.
|
|
| Top |
|
 |
|
tmarcel
|
Post subject: Re: Does CEL on CANBUS ecu's affect cable connectivity Posted: Thu Dec 25, 2008 11:22 pm |
|
 |
| RomRaider Donator |
Joined: Thu Apr 27, 2006 12:35 pm Posts: 227 Location: Charlotte, NC
|
|
mickey,
The OP2 is a bit flaky still, generally speaking. For pre-CAN cars I have a back up 1.3 cable when the 2.0 doesn't want to cooperate. I've sent a ton of logs to Colby and originally he thought it was my computer. Mostly I was having issues with the early model 16 bit ECUs but the 32 bit ones would still give me problems from time to time. The EvoX seems rock solid so far and I haven't touched a new CAN bus Subaru yet but I can imagine it's got a hiccup or two per your post.
|
|
| Top |
|
 |
|
mickeyd2005
|
Post subject: Re: Does CEL on CANBUS ecu's affect cable connectivity Posted: Fri Dec 26, 2008 2:04 am |
|
 |
| Administrator |
 |
Joined: Wed Oct 25, 2006 4:32 am Posts: 3040
|
|
Yeah, someone sent me logs with gaps in it. It was from a OP 2.0 cable. I've never seen that before with the 1.3 cable. However, all later logs didn't have gaps in it.
|
|
| Top |
|
 |
|
Page 1 of 1
|
[ 13 posts ] |
|
Who is online |
Users browsing this forum: No registered users and 12 guests |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum
|
|