RSLogix 5000 - PART 3 Controls Explorer LLC Updating the Firmware: Mostly for Brand New Processor (CPU) How to change the IP Address, On-Line with the Processor Re-Establish connection with the New IP Address / Processor Disclaimer: This is not a Rockwell Website. This website is an attempt to educate the viewers to develop an understanding of controls engineering.

The value changes instantly from the HMI, but not a state change at the rung.It's difficult to understand what you mean by this statement.Are you setting the bit (value:= 1) by some means on the HMI, the HMI shows that the value is '1', but the PLC still reads '0'?If so, it's likely that you're link from the HMI tag database to the PLC is not correct, so that the value in the HMI tag database changes, but with no accurate link, the PLC never gets the message. I don't know C-More, so can't give you troubleshooting tips.

On most HMI's this error is usually in how the 'Access' name (or 'Topic' or whatever reference is given to the link connection is called.)Another possibility is that you are writing to a PLC address that is being overwritten by PLC logic - OTE, OTL MOV, etc. Do a cross-reference in the PLC on the tag to see if there are any destructive bits. It's possible that the HMI is getting out-of-sync with the PLC, writing the value, and therefore assuming that the value is '1', and the PLC is even receiving the '1', but then logic is setting it back to '0' before anything interesting happens.If my assumption about what you mean by 'on the HMI' is not right, please try to use many more words to describe what you are seeing.

You aren't charged by the letter for posting. Hello Aardwizz, by the value changing I am referring to the value in the PLC tags, I see them change when monitoring the tags.The HMI is a C-more HMI, its changing the value in the PLC, I can see the value change from a 0 to a 1, in the PLC. Its not a comms. The HMI is working, the PLC is just not changing the state (to green) to make the rung true to energize an output on the same rung.This is as simple a circuit as it gets,Its a side project at home so, tonight I will recreate the instructions and start over. But, I really cannot understand why the circuit isn't working. Truly a mind bender for me. It should be simple, therefore I must have made a simple mistake somewhere just haven't found it.I will update.

So what you're saying is that, when you monitor the value of the bit in the PLC, the value is '1'. Yet the following logic:TAG OUTPUT- -( )does not show the TAG contact as being green?And you are sure that:there is no other instruction changing the value of TAG;that the routine that rung is in has a JSR to it;that the rung is in a program that is scheduled and is inhibited;that there is not an AFI TND, MCR, JMP or other 'don't scan' instructions that are preventing the rung or JSR from being scanned;that the PLC is in Run or Remote Run mode? PLC is in 'run mode' the logic is tag and output, Aardwizz. There is no other instruction changing the value, I put the instruction on the Main Program routine just to eliminate the JSR issue to test the input.No there is no other AFI, AFB, MCR, JMP or don't scan instructions either. And, that's why I'm curious, I've never seen this issue. I will update you when I try a few things tonight.The PLC logic seems to work, the tag value changes but not the tag state (doesn't turn green).

Hachi the dog's hindi dubbed watch online. 70+ channels, more of your favorite shows, & unlimited DVR storage space all in one great price. Hachi: A Dog’s Tale (2009) Watch in HD Download in HD Starring: Richard Gere, Joan Allen, Cary Hiroyuki Tagawa, Sarah Roemer, Jason Alexander, Erick Avari, Davenia McFadden.

No forces are applied, the program works in all other respects, I will try another input, and some other things tonight.But curious to me.Thanks for the input. I put the instruction on the Main Program routine just to eliminate the JSR issue to test the input.I'm tempted to ask, 'But is your 'MainRoutine' actually the main routine, as configured in the Program (see below for the difference: the one with the underscore is the 'real' mail, as indicated by the icon).But the fact remains that you claim the value of the tag when monitored in the PLC is a '1', but the - - is not green.Frankly, that's impossible. And it's independent of whether the ladder is being scanned.The only way it can happen is if you have the wrong tag somewhere, and your HMI is linked to one tag, while another is linked to a similar tag. You could be offline with the program and a '1' will still change a contact green.Click on the tag in the PLC logic.

Right click and select Monitor '.What's the value?Which instruction are you using: - - or - / -?Note that I'm leaving the HMI out of the equation. That's a red herring for now. I want to confirm that the value as monitored in the PLC is what should drive the output.

The next step will be to see if you can change the value wholly using Logix. And that it if you do, it drives the output. THEN we'll bring the HMI back into things to see if it can change your bit.One step at a time.

This is how you troubleshoot.

We have a system made up of a PowerFlex 70, a Panelview Plus 1000 and a 1768-L43 Compactlogix Plc. IT would like to have this machine monitored on our local ethernet and this would require changing the IP address' on all 3 components. I don't believe it is as simple as just changing them individually. IE: the panelview tag search locations?

I know how to change them but I'm worried about the communications between the PLC and the Panelview after I do. This is going to be done during production as we need this unit running 24/7.

( Of Course) Any help would be great. You will need t o change the IP on the PV+ at the terminal itself. I believe you might be able to edit the shortcuts to devices (PLC IP address) from the screen too, but if not, you will need to do so in Factory Talk Studio and make a new runtime file for that PV+ (be sure to make the new file for the correct firmware running on the PV+). I think you can change the Compactlogix on the fly, not sure if any of your devices require power cycle after changing. I don't think so, but it wouldn't hurt to make sure the changes are all properly saved and that lost connections to the old IP addresses are flushed out of buffers. MAKE sure that your IT department understands Ethernet IP I/O traffic and what it WILL do to an office network if not properly connected to the business LAN.

The use of a managed switch between the two systems with IGMP snooping enabled and a querier working is highly recommended if not required.Edited 6 Mar 2013 by OkiePC. This can't be done 'on the fly', obviously. But it can be done quickly. For the PowerFlex 70, the easiest thing to do is to use the HIM module on the front to connect to the 20-COMM-E and set the new IP address there.

Cycle the power to the drive, or just perform a reset of the 20-COMM-E to make the new address take effect. For the PanelView Plus, the IP address of the terminal itself is part of the Windows CE operating system, rather than part of the FactoryTalk View application. You set this address using the Configuration screen of the PV+ terminal.

Start at the main menu, then select Terminal Settings - Networks and Communications - Network Adapters (I'm going from memory, here). You must cycle power or perform a 'Reset' of the terminal for the new IP address to take effect. The PanelView Plus uses RSLinx Enterprise onboard to communicate with the controller, and the IP address of the controller is part of the RSLinx Enterprise 'Shortcut'.

If you change the address associated with that Shortcut, all of the references to that PLC in the application will get pointed to the new address. This is most easily done using FactoryTalk View Studio and the RSLinx Enterprise Runtime (Target) communication tab, but can also be done onboard the terminal. Terminal Settings - Networks and Communications - RSLinx Enterprise Communication. Select the controller's Ethernet interface under the Ethernet driver, and select 'Edit Device' to change the IP address for that Shortcut. The IP configuration for the CompactLogix is stored in the 1768-ENBT module's onboard flash memory. It is not part of the CompactLogix user program. It works just like all other ControlLogix family Ethernet modules; the easiest way to modify its IP address is by using RSLinx Classic, browsing to the module, and selecting 'Module Configuration'.

I don't recall if the module (and therefore the controller) needs to cycle power before it can use that IP address, but it is likely. You will have to change the IP address of the PowerFlex object in the ControlLogix user program using RSLogix 5000.

That's really the only thing that can't be done with your fingertips or a free tool. The good news is that all three of the devices you are working on have a configuration mode or an onboard display that will show you their IP address.