PDA

View Full Version : No interface cable found



eboggs_jkvl
November 11th, 2005, 09:01 AM
Getting this error


Error code: ERR_NOCABLE/31

No interface cable found.



What is wrong? I used the interface cable with LS1edit and it worked but I try to scan and log and I get an error message


Elmer

eboggs_jkvl
November 11th, 2005, 09:04 AM
Error data


Error report generated by EFILive at 15:59:43 on Nov 11, 2005

Error code: ERR_NOCABLE/31
No interface cable found.

EFILive Version: 7.3.0 (Build 303)

Platform: Windows XP
Version: 5.1 (build 2600)
Processor type: Pentium 869MHz

Directories
Temporary Cache: C:\Documents and Settings\Elmer Boggs\My Documents\EFILive\V7\Temporary cache
Logged Data: \\Eboggs\My Documents\EFILive\V7\Logged data
Customers: C:\Documents and Settings\Elmer Boggs\My Documents\EFILive\V7\Customers
Configuration: C:\Program Files\EFILive\V7\Configuration
Exported Data: C:\Documents and Settings\Elmer Boggs\My Documents\EFILive\V7\Exported data
Images: C:\Documents and Settings\Elmer Boggs\My Documents\EFILive\V7\Images
Sounds: C:\Documents and Settings\Elmer Boggs\My Documents\EFILive\V7\Sounds
Maps: C:\Documents and Settings\Elmer Boggs\My Documents\EFILive\V7\Maps
Pids: C:\Documents and Settings\Elmer Boggs\My Documents\EFILive\V7\PIDs
Virtual Dash: C:\Documents and Settings\Elmer Boggs\My Documents\EFILive\V7\VDash
Print Reports: C:\Documents and Settings\Elmer Boggs\My Documents\EFILive\V7\Print reports
Bug Reports: C:\Documents and Settings\Elmer Boggs\My Documents\EFILive\V7\Bug reports

Connected: No
Com port: 0
Com setup:
Requested baud rate: 115200

Cable id: 0
Cable code:
Cable desc:
Cable version:
Cable Firmware date:
Cable model:
Cable Serial number:

Protocols: 0
Protocol list:

Auto connect: No
Scan OBDII info: No

Error retries: 1
Retry delay: 10
Message throttle: 0

Most recently used VIN: 2G1FP22G0W2xxxxxx (Note: 1)

PCM information
PCM HDW Number: Unknown
Calibration ID: Unknown
Serial Number: Unknown
Operating System: Unknown
Engine Calibration: Unknown
Engine Diagnostics: Unknown
Transmission Calibration: Unknown
Transmission Diagnostics: Unknown
Fuel System: Unknown
System: Unknown
Speedometer: Unknown
Operating System BCC: Unknown
5x24 scan mode: Unknown
10x24 scan mode: Unknown
Maximum dynamic packets: Unknown

Detected modules:
$10=Powertrain Control Module (PCM)

Selected parameters:

Most recent communication with vehicle:
15:51:56.468 Send: $01,$02,$23,$01,$00,$27
15:51:56.678 Send: $01,$01,$02,$00,$04
15:51:56.889 Send: $01,$02,$23,$01,$00,$27
15:51:57.099 Send: $01,$01,$02,$00,$04
15:51:57.620 Send: $01,$02,$23,$01,$00,$27
15:51:57.850 Send: $01,$01,$02,$00,$04
15:51:58.060 Send: $01,$02,$23,$01,$00,$27
15:51:58.271 Send: $01,$01,$02,$00,$04
15:51:58.641 Send: $01,$6C,$10,$F1,$2A,$00,$00,$00,$00,$00,$00,$05,$0 D,$00,$04
15:51:58.771 Send: $01,$68,$6A,$F1,$01,$00,$00,$00,$00,$00,$00,$05,$8 0,$00,$04
15:51:59.442 Send: $01,$6C,$10,$F1,$2A,$00,$00,$00,$00,$00,$00,$05,$0 D,$00,$04
15:51:59.572 Send: $01,$68,$6A,$F1,$01,$00,$00,$00,$00,$00,$00,$05,$8 0,$00,$04
15:59:40.435 Send: $01,$02,$23,$01,$00,$27
15:59:40.645 Send: $01,$01,$02,$00,$04
15:59:40.856 Send: $01,$02,$23,$01,$00,$27
15:59:41.066 Send: $01,$01,$02,$00,$04
15:59:41.487 Send: $01,$02,$23,$01,$00,$27
15:59:41.697 Send: $01,$01,$02,$00,$04
15:59:41.907 Send: $01,$02,$23,$01,$00,$27
15:59:42.118 Send: $01,$01,$02,$00,$04
15:59:42.448 Send: $01,$6C,$10,$F1,$2A,$00,$00,$00,$00,$00,$00,$05,$0 D,$00,$04
15:59:42.588 Send: $01,$68,$6A,$F1,$01,$00,$00,$00,$00,$00,$00,$05,$8 0,$00,$04
15:59:43.129 Send: $01,$6C,$10,$F1,$2A,$00,$00,$00,$00,$00,$00,$05,$0 D,$00,$04
15:59:43.259 Send: $01,$68,$6A,$F1,$01,$00,$00,$00,$00,$00,$00,$05,$8 0,$00,$04

Report ID: 248826 (Note: 2)

Notes:
(1) The VIN sequence number is not required for this report and for your privacy it is NOT included in this report.

(2)The report ID is a checksum of the report text and is used to verify the integrity of the report.

wait4me
November 11th, 2005, 10:27 AM
Are the drivers installed for the cable? When you go to control panel / system/ hardware, is anything showing not installed correctly?

Is the light on the unit itself flashing when you install it into the port?

eboggs_jkvl
November 11th, 2005, 10:57 AM
The cable worked perfectly when I fired up ls1edit and programmed my PCM today

After the programming, I was going to record while I drove home from the shop. I got the error.

The cable has a single flashing red light when the PC is running, the car is running and the cable is hooked up.

There are no error messages in the "System" Devices.

Blacky
November 11th, 2005, 11:00 AM
You may have the scan tool set to look for an AutoTap cable. Open the Properties window and make sure the [Connection] tab page is set up like the image.

eboggs_jkvl
November 11th, 2005, 11:09 AM
It was looking for Atap I changed it to what you requested and still get the error message.

Blacky
November 11th, 2005, 11:24 AM
A red LED flashing should only occur while data is being logged - it's the heartbeat signal that keeps the PCM sending data - it should flash about every 2 seconds. However, if you have not got a successful connection then the red LED should not be flashing.

The yellow OBD LED should flash all the time that it is connected to the vehicle with the ignition on. That yellow LED shows class-2 bus activity.

In the error report you posted:

Most recent communication with vehicle:
15:51:56.468 Send: $01,$02,$23,$01,$00,$27
15:51:56.678 Send: $01,$01,$02,$00,$04
15:51:56.889 Send: $01,$02,$23,$01,$00,$27
...
Those messages are exclusively trying to contact an AutoTap cable.

You should be seeing messages of the form:


Most recent communication with vehicle:
12:20:32.515 Send: $A1,$23,$00,$01,$00,$C5
12:20:32.515 Recv: $B1,$A3,$00,$00,$54
12:20:32.515 Send: $A1,$40,$00,$06,$0C,$6C,$10,$F1,$2A,$00,$8A
12:20:32.625 Send: $A1,$23,$00,$01,$00,$C5
12:20:32.625 Recv: $B1,$A3,$00,$00,$54
...
i.e. they should start with $A1 = transmit and $B1 = recieve. If you are not seeing any messages starting with $A1 then the Scan Tool software is not even attempting to contact the FlashScan cable. That points to a configuration issue with the Scan Tool software.

To see those messages, just press Ctrl+G after attempting to connect to the FlashScan cable.

You could always try checking the box "Scan all cable types" to see if EFILive can automatically figure out the FlashScan connection.

Regards
Paul

eboggs_jkvl
November 11th, 2005, 11:39 AM
Error report generated by EFILive at 18:38:05 on Nov 11, 2005

Error code: ERR_NOCABLE/31
No interface cable found.

EFILive Version: 7.3.0 (Build 303)

Platform: Windows XP
Version: 5.1 (build 2600)
Processor type: Pentium 879MHz

Directories
Temporary Cache: C:\Documents and Settings\Elmer Boggs\My Documents\EFILive\V7\Temporary cache
Logged Data: \\Eboggs\My Documents\EFILive\V7\Logged data
Customers: C:\Documents and Settings\Elmer Boggs\My Documents\EFILive\V7\Customers
Configuration: C:\Program Files\EFILive\V7\Configuration
Exported Data: C:\Documents and Settings\Elmer Boggs\My Documents\EFILive\V7\Exported data
Images: C:\Documents and Settings\Elmer Boggs\My Documents\EFILive\V7\Images
Sounds: C:\Documents and Settings\Elmer Boggs\My Documents\EFILive\V7\Sounds
Maps: C:\Documents and Settings\Elmer Boggs\My Documents\EFILive\V7\Maps
Pids: C:\Documents and Settings\Elmer Boggs\My Documents\EFILive\V7\PIDs
Virtual Dash: C:\Documents and Settings\Elmer Boggs\My Documents\EFILive\V7\VDash
Print Reports: C:\Documents and Settings\Elmer Boggs\My Documents\EFILive\V7\Print reports
Bug Reports: C:\Documents and Settings\Elmer Boggs\My Documents\EFILive\V7\Bug reports

Connected: No
Com port: 0
Com setup:
Requested baud rate: 115200

Cable id: 0
Cable code:
Cable desc:
Cable version:
Cable Firmware date:
Cable model:
Cable Serial number:

Protocols: 0
Protocol list:

Auto connect: Yes
Scan OBDII info: No

Error retries: 1
Retry delay: 10
Message throttle: 0

Most recently used VIN: 2G1FP22G0W2xxxxxx (Note: 1)

PCM information
PCM HDW Number: Unknown
Calibration ID: Unknown
Serial Number: Unknown
Operating System: Unknown
Engine Calibration: Unknown
Engine Diagnostics: Unknown
Transmission Calibration: Unknown
Transmission Diagnostics: Unknown
Fuel System: Unknown
System: Unknown
Speedometer: Unknown
Operating System BCC: Unknown
5x24 scan mode: Unknown
10x24 scan mode: Unknown
Maximum dynamic packets: Unknown

Detected modules:
$10=Powertrain Control Module (PCM)

Selected parameters:

Most recent communication with vehicle:
18:37:58.268 Send: $01,$02,$23,$01,$00,$27
18:37:58.478 Send: $01,$01,$02,$00,$04
18:37:58.689 Send: $01,$02,$23,$01,$00,$27
18:37:58.899 Send: $01,$01,$02,$00,$04
18:37:59.320 Send: $01,$02,$23,$01,$00,$27
18:37:59.530 Send: $01,$01,$02,$00,$04
18:37:59.740 Send: $01,$02,$23,$01,$00,$27
18:37:59.951 Send: $01,$01,$02,$00,$04
18:38:00.281 Send: $01,$6C,$10,$F1,$2A,$00,$00,$00,$00,$00,$00,$05,$0 D,$00,$04
18:38:00.391 Send: $01,$68,$6A,$F1,$01,$00,$00,$00,$00,$00,$00,$05,$8 0,$00,$04
18:38:00.812 Send: $01,$6C,$10,$F1,$2A,$00,$00,$00,$00,$00,$00,$05,$0 D,$00,$04
18:38:00.922 Send: $01,$68,$6A,$F1,$01,$00,$00,$00,$00,$00,$00,$05,$8 0,$00,$04
18:38:01.943 Send: $01,$02,$23,$01,$00,$27
18:38:01.943 Recv: $01,$02,$23,$01,$00,$27
18:38:02.044 Send: $01,$01,$02,$00,$04
18:38:02.044 Recv: $01,$01,$02,$00,$04
18:38:02.144 Send: $01,$02,$23,$01,$00,$27
18:38:02.144 Recv: $01,$02,$23,$01,$00,$27
18:38:02.244 Send: $01,$01,$02,$00,$04
18:38:02.244 Recv: $01,$01,$02,$00,$04
18:38:03.085 Send: $01,$02,$23,$01,$00,$27
18:38:03.085 Recv: $01,$02,$23,$01,$00,$27
18:38:03.185 Send: $01,$01,$02,$00,$04
18:38:03.185 Recv: $01,$01,$02,$00,$04
18:38:03.285 Send: $01,$02,$23,$01,$00,$27
18:38:03.285 Recv: $01,$02,$23,$01,$00,$27
18:38:03.386 Send: $01,$01,$02,$00,$04
18:38:03.386 Recv: $01,$01,$02,$00,$04
18:38:04.137 Send: $01,$6C,$10,$F1,$2A,$00,$00,$00,$00,$00,$00,$05,$0 D,$00,$04
18:38:04.137 Recv: $01,$6C,$10,$71,$2A,$00,$00,$00,$00,$00,$00,$05,$0 D,$00,$04
18:38:04.247 Send: $01,$68,$6A,$F1,$01,$00,$00,$00,$00,$00,$00,$05,$8 0,$00,$04
18:38:04.247 Recv: $01,$68,$6A,$71,$01,$00,$00,$00,$00,$00,$00,$05,$0 0,$00,$04
18:38:05.088 Send: $01,$6C,$10,$F1,$2A,$00,$00,$00,$00,$00,$00,$05,$0 D,$00,$04
18:38:05.088 Recv: $01,$6C,$10,$71,$2A,$00,$00,$00,$00,$00,$00,$05,$0 D,$00,$04
18:38:05.198 Send: $01,$68,$6A,$F1,$01,$00,$00,$00,$00,$00,$00,$05,$8 0,$00,$04
18:38:05.198 Recv: $01,$68,$6A,$71,$01,$00,$00,$00,$00,$00,$00,$05,$0 0,$00,$04

Report ID: 280920 (Note: 2)

Notes:
(1) The VIN sequence number is not required for this report and for your privacy it is NOT included in this report.

(2)The report ID is a checksum of the report text and is used to verify the integrity of the report.

eboggs_jkvl
November 11th, 2005, 11:40 AM
That's the error data AFTER I changed it to the setting that you wanted

Blacky
November 11th, 2005, 12:05 PM
What is wrong? I used the interface cable with LS1edit and it worked but I try to scan and log and I get an error message
Elmer

Ok, getting right back to the initial post, you said "I used the interface cable with LS1edit and it worked". I presume you mean you used the cable with EFILive's Tuning Tool software. There is no way that FlashScan will work with LS1Edit software.

If you meant that you were using LS1Edit's cable with LS1Edit's software then that has no bearing on whether EFILive/FlashScan will work or not work.

Download the attached USB program, plug in FlashScan and run the usbview.exe program. You should see the same information for FlashScan as the attached image. If you do not then you will probably need to re-install the FlashScan USB drivers.

Regards
Paul

eboggs_jkvl
November 11th, 2005, 12:59 PM
This is what I see

eboggs_jkvl
November 11th, 2005, 01:00 PM
I downloaded the USB drivers and unzipped them. Where are the placed?

eboggs_jkvl
November 11th, 2005, 01:57 PM
Feel free to delete this post. Geezer attack


Thanks for the responses


Elmer

Blacky
November 11th, 2005, 02:16 PM
Feel free to delete this post. Geezer attack


Thanks for the responses


Elmer

So is it working now? Should I ask what the problem was? Was it just a case of installing the USB drivers?

Paul

Black02SS
November 11th, 2005, 02:56 PM
To many metamucil martini's for you Elmer. :)

wait4me
November 11th, 2005, 05:41 PM
:) woo hoo :)

eboggs_jkvl
November 12th, 2005, 03:12 AM
To many metamucil martini's for you Elmer. :)


Ouch! Quit talking about my "vice". Actually, just a sheer case of stupidity. I grabbed the wrong cable out of the bag. I actually use the A-Tap serial cable and wasn't paying attention and grabbed the ls1edit cable.

On another note:

I want to record Injector Duty Cycle 1 & 2 and it's showing as invalid PID. I have recordings where I recorded that data but now it says I can't record it.

Injector Pulse width bank 1 & 2 are also showing invalid.

Now, I rebuilt the engine, (Same PCM) and basically I have an LS6 engine with 60 lb injectors.


Why have thos 4 PIDs gone away? I did a shift-f2 to "refresh them but they still show as invalid. I'd really like to use those on this car.


Elmer

Black02SS
November 12th, 2005, 03:17 AM
Hmm... Do you have the latest build E? There was a small lapse with Pre-Release 011 and it was updated again just shortly after.

eboggs_jkvl
November 12th, 2005, 03:25 AM
Hmm... Do you have the latest build E? There was a small lapse with Pre-Release 011 and it was updated again just shortly after.


Hey! I've been sick! You had releases coming out the wazoo and I haven't a CLUE where I'm at on this software! :p


I'll check, just a sec...

V7.3.0 (Build 303)
obdiiV7.dll 7.3.0 (Build 446)

is on the laptop.

Black02SS
November 12th, 2005, 03:42 AM
Yea need a update. :) Give that awhirl and see how it turns out for ya.

eboggs_jkvl
November 12th, 2005, 04:09 AM
Yea need a update. :) Give that awhirl and see how it turns out for ya.

I downloaded the ZIP for 011 unzipped and moved the files to the appropriate folder and still show the same version in the "about".

Do I need to go to the car and refresh? It looks like the same version to me?

Black02SS
November 12th, 2005, 04:23 AM
These are the current release builds that it should be Elmer.

Tuning Tool V7.3.0 (Build 317)
Scan Tool V7.3.0 (Build 303)
obdiiV7.dll: V7.3.0 (Build 446)

This is the latest update. You might want to uninstall your current build (Save any files you want to retain later. cal_pids.txt, scripts, PIDS, etc) reinstall 7.2 and update to 7.3 (Build 317).

eboggs_jkvl
November 12th, 2005, 04:27 AM
Ahso! Read the fine print!

I can use the Duty cycle BUT and ONLY if I select IBPW Bank1 & IBPW Bank2 ALSO!


Those 2 MUST be selected before I'm allowed to select Inj Duty Cycle 1 & 2

Black02SS
November 12th, 2005, 04:29 AM
Ahso! Read the fine print!

I can use the Duty cycle BUT and ONLY if I select IBPW Bank1 & IBPW Bank2 ALSO!


Those 2 MUST be selected before I'm allowed to select Inj Duty Cycle 1 & 2

Right, you said that the IBPW for Bank 1 and 2 were showing invalid which would mean you can't select the duty cycles.. So we need to get it so the IBPW is valid.

eboggs_jkvl
November 12th, 2005, 04:36 AM
Somewhere between the update, the refresh and two hook-ups to the car this morning, the IBPW 1&2 lost the cute red X on the PID field.

It appears that somewhere along the line I hit the combo to wake this thing up.

Black02SS
November 12th, 2005, 04:46 AM
That is great to hear.

Nothing more to see here ;)

Blacky
November 12th, 2005, 09:49 AM
One last thing to add...

From the Readme.rtf file in V7.3:

Validating PIDs:
After upgrading from EFILive V7.1.x or earlier, previously validated PIDs may be marked as "not supported", they will be displayed with a red cross through their icon on the [PIDs (F8)] tab page.
Once a connection has been made to each new vehicle, you should manually validate PIDs (if EFILive does not validate them automatically) by selecting the menu option: Info->Validate PIDs or pressing the hotkey Shift+F2.
If a connection will not be made with this computer, you may use FlashScan to validate the PIDs remotely, or copy the appropriate *.vpl and *.vml files from your laptop computer into the folder:
My Documents\EFILive\V7\PIDs.

Regards
Paul

Bruce Melton
November 21st, 2005, 05:34 AM
Mine does that every once in a while. Plug, unplug the USB or even reload driver. For me it comes back when I call it home.

eboggs_jkvl
November 21st, 2005, 07:01 AM
One last thing to add...

From the Readme.rtf file in V7.3:

Validating PIDs:
After upgrading from EFILive V7.1.x or earlier, previously validated PIDs may be marked as "not supported", they will be displayed with a red cross through their icon on the [PIDs (F8)] tab page.
Once a connection has been made to each new vehicle, you should manually validate PIDs (if EFILive does not validate them automatically) by selecting the menu option: Info->Validate PIDs or pressing the hotkey Shift+F2.
If a connection will not be made with this computer, you may use FlashScan to validate the PIDs remotely, or copy the appropriate *.vpl and *.vml files from your laptop computer into the folder:
My Documents\EFILive\V7\PIDs.

Regards
Paul


I did the manual validate and the fields STILL show as not valid PIDs. I've refreshed the PIDs at least twice and nothing changes.

Elmer

Blacky
November 21st, 2005, 04:09 PM
Do you mean the injector duty cycle PIDs? If so, right click on them and select "More info..." to see why they are not valid.

Regards
Paul