Forums.MrPLC.com > AB MicroLogix 1000 Communication problem

RobertL

Feb 1 2009, 09:10 PM

Hi folks,
I'm having communication problems with a AB MicroLogix 1000, I need to upload an application program but I'm getting the following message "Initial Driver failed-code:-1" Current driver (AB-DF1-1) may not be running, however, the driver configuration is successful and It's running (AB-DF1-2DH485). The only difference I could see is that the message says that AB-DF1-1 may not be running while my connection shows AB-DF1-2DH485 is running. Can anyone suggest me how to solve this problem? I would appreciate any help.

slcman

Feb 1 2009, 09:24 PM

QUOTE(RobertL @ Feb 1 2009, 09:10 PM) [snapback]78314[/snapback]

Hi folks,
I'm having communication problems with a AB MicroLogix 1000, I need to upload an application program but I'm getting the following message "Initial Driver failed-code:-1" Current driver (AB-DF1-1) may not be running, however, the driver configuration is successful and It's running (AB-DF1-2DH485). The only difference I could see is that the message says that AB-DF1-1 may not be running while my connection shows AB-DF1-2DH485 is running. Can anyone suggest me how to solve this problem? I would appreciate any help.

You must see the plc in RsLink. Maybe the driver in your project is not correct. You can change it in Controller properties -> controller communication.
Anyway you can also use Comms (in menu) -> Who active go online, you'll promt in RsWho, just select your plc. I think is the easy way...

good luck

IPSteve

Feb 5 2009, 12:13 PM

If the first answer doesn't help then the problem could be your operating system. I recently went to link up to a plc, that I had always been able connect to in the past, and found out I couldn't. After much searching and pounding my head I found out that my operating system, Windows XP with service pack 3(SP3) was the problem. I rolled it back to service pack 2 and had no problems. Hope this helps.

BobLfoot

Feb 5 2009, 07:29 PM

QUOTE(IPSteve @ Feb 5 2009, 12:13 PM) [snapback]78468[/snapback]

If the first answer doesn't help then the problem could be your operating system. I recently went to link up to a plc, that I had always been able connect to in the past, and found out I couldn't. After much searching and pounding my head I found out that my operating system, Windows XP with service pack 3(SP3) was the problem. I rolled it back to service pack 2 and had no problems. Hope this helps.

I am using Windows XP Professional SP3 with all of "uncle Bill's" latest security updates and have no issues with any Rockwell product I am using. This is not to say there might not be an issue somewhere, but I'd work with your Rockwell Support Tech and the fine folks of mrplc for ages before I left my PC vulnerable by rolling back the security to SP2 level.

TWControls

Feb 5 2009, 09:41 PM

I believe that there are some increased issues with the PIC driver with SP3...but mine usually takes about 30 tries to get it to work on SP2

IPSteve

Feb 6 2009, 07:17 AM

QUOTE(BobLfoot @ Feb 5 2009, 07:29 PM) [snapback]78500[/snapback]

QUOTE(IPSteve @ Feb 5 2009, 12:13 PM) [snapback]78468[/snapback]

If the first answer doesn't help then the problem could be your operating system. I recently went to link up to a plc, that I had always been able connect to in the past, and found out I couldn't. After much searching and pounding my head I found out that my operating system, Windows XP with service pack 3(SP3) was the problem. I rolled it back to service pack 2 and had no problems. Hope this helps.

I am using Windows XP Professional SP3 with all of "uncle Bill's" latest security updates and have no issues with any Rockwell product I am using. This is not to say there might not be an issue somewhere, but I'd work with your Rockwell Support Tech and the fine folks of mrplc for ages before I left my PC vulnerable by rolling back the security to SP2 level.

I can see your concerns, but the laptop that I use for programming is not used for surfing the web, so the extra security updates aren't a huge concern for me. I only go online if I have to download a driver or get updates for my PC. Besides it was Allen Bradley that said the drivers for the PIC unit were not compatable with SP3 and to roll back to SP2. This also allowed my RS-232 driver to work. Rolling back to SP2 can't hurt as a test to see if it solves the problem. You can always reinstall SP3.