Search the Community

Hello all, first post here, and thanks in advance for the help. I'm a fairly green SCADA and controls designer and although I worked fairly extensively with these systems in the past, I followed a sightly different career path for the last several years and haven't had my hands on a PLC that whole time. Started a new job and am rebuilding my knowledge with it. Fortunately my company afforded me a PLC to take home and mess around with for this purpose. I feel pretty dumb as I am struggling to even connect with it, haha. Here are the stats: Backplane: TSXRKY4EX (end caps are securely in place) Power supply: TSX PSY2600 Processor: TSX P57 6634 First I attempted to connect via ethernet, using the IP address sticky-noted to the front of the processor: 10.1.1.80. No luck, "PLC address is incorrect, or PLC is busy, yadda yadda". As I understand, the default IP address can be converted from the MAC address. The last two MAC address numbers were: CF.87, which gave me the address 85.16.207.135. Same result with this. I tried pinging both address from the command console and had no luck there either. I happened to have a USB to unitelway adapter (Telemecanique brand) and attempted using that as well, Address:SYS.. Media:Unitelway. No luck, same answer. After a lot of frustration and hours spent scouring the internet for answers, I took the nuclear option and pulled the battery (while unplugged) and replaced after 30 or so seconds. I was assuming this would clear the memory and reset the IP to default (85.16.207.135), afterwhich I could reconfigure and start fresh. Unity still can't connect nor can I ping it. It should be noted that I am using Unity Pro XL Version 8.0, on a VMware image. I did attempt pinging from both the VM and the host machine, both can ping other known devices so connection by the VM through the host shouldn't be the problem. Neither the VM or the host recieved a ping reply from the PLC. Any help would be GREATLY appreciated. I feel I have exhausted all options and I hope I didn't shoot myself in the foot by pulling the battery. As far as whatever program was on it before is irrelevant, the PLC was given to me to do with whatever I wish, so memory loss wasn't a danger. I just need to connect to it. Thanks!!

Hello, would like to change some ideas with you. I´m working in a new project and need convert an SLC500 to Controllogix, with a 1747-AENTR is possible create a SLC500 Eth remote.... but in my case i have two 1746-A13 (conected by expansor) and can´t add all the modules in a rslogix5000 aplication. In the 1747-AENTR manual say that is possible in the v21.00 of the rslogix5000... I really need install this new version? Don´t have other way? Thank you! Vitor Prado

I am working on Remote IO panel and plan to use the following components: 1734-AENT 1734-OW4 - qty 2 1734-IE4C I wonder if I need to separate the bus between the relay output module and analog input module? Or anywhere else in this setup? Thanks.

Hello, I'm working with some old Allen-Bradley SLC5/04 systems with 1747-SN modules. The module is located in Slot1. One system is only using the RIO module for a PV1000. How do you know where the "M-Files" for Analog I/O modules and/or Panelviews are located? I see programming using locations such as: M1:1.810 where 60 words are being copied from a Remote I/O PV1000 to some words for the SLC to utilize, but I don't understand why "M1:1.810" was used instead of, for example, "M1:1.800"? I looked and so far cannot find information pertaining to the words other than what is in the User's manual, and it doesn't address this issue. The panelview in my example uses all of Logical Rack 0, Full Rack addressing. Any help would be most appreciated. I have very little experience with the RIO stuff because almost everything I've worked with in the past has been Devicenet.

I need to change the IP address of an existing PLC. Only access I have is remote (VPN). Is there any issue with downloading the same program - with the IP address changed - to the existing processor? Then change the local network range to match, etc...