I just received my 4-car cable yesterday; I have a '99 Firehawk M6 with factory '99 programming. I've tried numerous times to get a read; the greatest amount of progress I've reached is 50% before it disconnected. I'll let it try to re-establish a connection, but all subsequent attempts to re-connect fail.

Is this a typical thing? Should I attempt to flash my PCM to an updated base code? Should I try to get a read from a friend's car? Are there any recommended settings for the COM port (9600, 8,N,1)? I certainly didn't expect to run into immediate problems with LS1_edit.

 

What operating system are you using? It seems using Edit with anything after Windows 98 is trouble. In my case, using XP, it worked for awhile then I couldn't connect at all. Edit was created using the old .dlls and other files used in Win98 and Win95. Win2000 and up are "smart" operating systems and will eventually reject programs not designed for them.

 

I'm using Win 2000 on a Toshiba Tecra notebook, connecting via COM1 at 9600,8,N,1. Edit runs and connects, but it doesn't remain connected for very long. I'm tired of resetting my PCM after every failed reconnect attmpt; there's no way in HELL this laptop will see a damn Win9x OS.

 

I got a dollar here that says your laptop has an infrared port on it, that needs to be disabled.

Check out my doc at http://www.akmcables.com/serial.doc - now, the testing of the box does not apply to the LS1Edit cable (it's only for my OBDI cable), but the disabling of the infrared port stuff does.

Hope that helps,

Andrew

 

Thanks a TON, Andrew! I wish I had met you earlier (before I graduated from Baylor).

 

Also, what do you recommend I set the COM port to? At what speed does data transfer via the LS1_edit cable? Currently it's set at 9600bps; would I benefit by changing it to 19200bps?

 

If you had a comm port problem you wouldn't be able to connect at all.

 

</font><blockquote><font size="1" face="Verdana, Helvetica, sans-serif">quote:</font><hr /><font size="2" face="Verdana, Helvetica, sans-serif">Originally posted by Camaroholic:
[QB]I got a dollar here that says your laptop has an infrared port on it, that needs to be disabled.
Hope that helps,[QB]</font><hr /></blockquote><font size="2" face="Verdana, Helvetica, sans-serif">Camaroholic:
That's a fix!!! Disabled IR port, she's working great! Thank you !

<small>[ November 08, 2002, 10:29 PM: Message edited by: Wt99C5 ]</small>

 

</font><blockquote><font size="1" face="Verdana, Helvetica, sans-serif">quote:</font><hr /><font size="2" face="Verdana, Helvetica, sans-serif">Originally posted by Predator:
<strong>If you had a comm port problem you wouldn't be able to connect at all.</strong></font><hr /></blockquote><font size="2" face="Verdana, Helvetica, sans-serif">Mmmmmm, no.

What happens is that most of the time, the infrared port goes to COM3, which shares the same interrupt request line as COM1. COM1 can fire up and start, but if for *any* reason the infrared port causes an interrupt on the PC, bye-bye communications.

Just like the 'old days' of serial mice and modems. I don't know how many PC's I had to fix that were purchased with the mouse on COM1 and the modem on COM3. Whenever you launched the modem, the mouse quit working... and vise-versa.

And Wt99C5, glad it worked for you.

I've had guys ship me their laptops and cables before (because they weren't working), just to find that this was exactly the problem. Trying to walk through this over the phone (since no two manufacturers make the disabling function exactly alike) is tough. But, it's quite common. Who uses those stupid infrared ports anyway? <img border="0" title="" alt="[Wink]" src="gr_images/icons/wink.gif" />

-Andrew

 

I just moved here about 6 months ago. Diggin' it so far. <img border="0" title="" alt="[Smile]" src="gr_stretch.gif" />

COM settings do not matter. LS1prog overrides the settings. FWIW, the laptop communicates with the cable at 56k, I believe.

I never mess with the COM settings on my laptop. Stuff just works like voodoo. <img border="0" title="" alt="[Wink]" src="gr_images/icons/wink.gif" />

-Andrew

 

Andrew,

I didn't want to get into this in Imperator's thread, but since his problem seems to be solved, let me run this by you. I wish my connection woes were as simple as disabling infrared devices. Edit connects fine with my desktop using Win98, but I can't get it to work any longer on my laptop with XP Professional. I even had a loopback test performed on my serial port, and the serial port is working fine. I've tried changing comm ports, changing flow rate to xon/xoff, etc. etc. No conflicts anywhere. Even having XP emulate Win98 for the Edit program offers no solution. I had my cable checked by Carputing, and no problem there. I know if I loaded my laptop with Win98, Edit would work, but I too, don't want to do that. I've pretty much given up on trying to make Edit work on XP, and plan on buying another older laptop to use with Edit and EASE unless I can somehow find a solution before next spring. Have you heard of a problem like mine using XP? Anything else I can try that you can think of? Sorry if I'm butting in here--forgive me. <img border="0" title="" alt="[Embarrassed]" src="gr_emb.gif" /> Thanks so much.