RSLinx lock up during Autoconfigure

rguimond · Dec 21, 2009

Version 2.51.00.21 (CPR7)
Running Windows XP 2002 SP3 on laptop with a real com port

Haven't had issues before.

If I connect to SLC 5/05 or ML1200 using RS-232 DF1 Devices driver and click on the Autoconfigure button, I get a message saying "Autoconfigure Initializing", but it won't go further than that. Used to work fine.

It doesn't appear that anything else has control of the COM port, and RSLinx works fine using Ethernet drivers.

Any suggestions?

Lancie1 · Dec 21, 2009

Your RS-232 cable could have a broken wire (internal break). Cables that are flexed many times eventually have a break in one of the wires. Most times you can't see it from the outside. Test the cable.

Ken Roach · Dec 21, 2009

Is the installation of SP3 recent ?

If the various baud rates, parity options, and error checking modes show up in sequence then it's probably a bad cable or bad port.

But if it just goes to "Autoconfigure Initializing", I would say that RSLinx is having trouble sending the port settings to Windows, which sounds like an XPSP3 problem.

There has been some discussion on this and other Forums about a trick to roll back the SP3 serial driver by replacing it with one from an SP2 computer.

The other option is to try out RSLinx 2.56 and see if it has the same trouble.

baref00t25 · Dec 21, 2009

Try testing your comm port with a loop back. I've had ports lock up before after they've been toasted for one reason or another.

http://zone.ni.com/devzone/cda/tut/p/id/3450

geniusintraining · Dec 21, 2009

Do you have any other drivers running? just a WAG

Ken Roach · Dec 21, 2009

GIT has a good point; conflicting drivers can cause similar problems.

When you have another driver running, like a DF1 driver in RSLinx Enterprise or the 1747-PIC driver still in residence, or even a Modbus or other driver in separate software, the error is usually different.

"Failed to open COMx for configuration" is the usual error messaage in those circumstances. It might be different if the conflicting driver is actually inside RSLinx.

The lack of an error message does not rule out a driver conflict, but does point to a software condition that RSLinx doesn't have an error check for.

My first step would be to install RSLinx 2.56, and my second step would be to hook up a serial sniffer or just a serial breakout box to see if any traffic actually hits the pins of the serial port, or if it gets hung up inside the operating system.

Gil47 · Dec 22, 2009

If the fault is still persisting I wonder if its time to delete the 2 Harmony files normally found at
C:\Program Files\Rockwell Software\RSCOMMON
as these are cache file that get rebuilt when RSLinx starts.

Well thats my wild guess for something to try.

rguimond · Dec 22, 2009

Ken Roach said:
GIT has a good point; conflicting drivers can cause similar problems.

When you have another driver running, like a DF1 driver in RSLinx Enterprise or the 1747-PIC driver still in residence, or even a Modbus or other driver in separate software, the error is usually different.

"Failed to open COMx for configuration" is the usual error messaage in those circumstances. It might be different if the conflicting driver is actually inside RSLinx.

The lack of an error message does not rule out a driver conflict, but does point to a software condition that RSLinx doesn't have an error check for.

My first step would be to install RSLinx 2.56, and my second step would be to hook up a serial sniffer or just a serial breakout box to see if any traffic actually hits the pins of the serial port, or if it gets hung up inside the operating system.

Tried sniffer first - didn't detect anything. Reinstalled RSLinx - didn't help.

I rolled-back the comm port driver - didn't help, either. Updating the comm port driver file did the trick!

Thanks for all your help.

geniusintraining · Dec 22, 2009

rguimond said:
Updating the comm port driver file did the trick!

Thanks for updating us

RSLinx lock up during Autoconfigure

rguimond

Lifetime Supporting Member

Lancie1

Lifetime Supporting Member

Ken Roach

Lifetime Supporting Member + Moderator

baref00t25

Member

geniusintraining

Lifetime Supporting Member + Moderator

Ken Roach

Lifetime Supporting Member + Moderator

Gil47

Member

rguimond

Lifetime Supporting Member

geniusintraining

Lifetime Supporting Member + Moderator

Similar Topics