Help for connecting laptop to slc 5/05

[panic mode]

- get serial cable 1747-CP3 or 1756-CP3 (or any null modem cable)
- connect one end to CPU and other to your PC
- open RSLinx, load DF1 driver, select ControlLogix and hit
Autoconfigure. You might want to change
COM port to match address of your computer COM port.
- Once you get sucess, you should be able to browse in RS Linx and
find the connected PLC. This is REQUIRED before you can go
online with the RSLogix.
- If you don't have offline copy of the PLC program you should be able
to go inlone and upload program from PLC (note you will have to
create new project - just blank file that matches CPU you want to
upload from)
Having no offline copy of the running SLC will make it hell
of a job to do any work with the program. If you have at least
I/O list of the machine or electrical diagrams, you might be able
to figure out most of the internal bits and troubleshoot the
program. Otherwise - good luck...
- Once you have uploaded program from the SLC, you can go to
controller properties and check the IP address (if static!).
- this should let you work with the PLC but as you guessed
DF1 is not nececarily the screamer. If you want to get faster
connection you can get a single etherenet crossover cable
OR use ethernet hub (or switch) and pair of ethernet straight
cables to make phisical connection.
- You have to use proper subnet mask and IP address on both PLC and
laptop in order to communicate (typically you leave PLC settings
as they are if this is part of working machine and just change
your laptop eth. configuration).
- Once you have done this, you do the same thing as before:
open RS Linx, instal eth. driver, MANUALLY enter the IP address
of the PLC, and make sure you can see the PLC while browsing
in RSLinx. Once this works you can use it in RSLogix...



sure

 

[punder30]

I agree with 93lt and panic with there reply posts. The DF1 protocol is the prefered method of finding the IP address on a current application, or in a new application, put an IP address in the 5/05 to be able to communicate over AB's Ethernet/IP protocol. Notice I put AB's protocol. This is not a open protocol. Just be aware of that if you ever need to communicate over an ethernet other than AB equipment. The other equipment(if other than AB) needs to be compatiable with AB's protocol. Why did AB do that? Internet protocol has been around a long time...even before as what we know the internet is today. So why does AB want to cash in on user royalties if a widely used free open protocol being used for years that works well. Well thats a issue to itself.

Also, if you ever have problems of Rslinx seeing the PLC,Ethernet PV,etc. and get a "?" to show up in linx. This is a problem I had at first. Through my pain and tribulations, I figured it out finally. I will go in detail of how and why if anybody has that problem.