MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About bwhinch

  • Rank

Profile Information

  • Country Canada
  1. I'm trying to understand if I can use the ADC feature in my powerflex 525 drives. We have a large plant with vlans setup for different areas. If we have a drive fail and ADC is enabled, my understanding is we can take a brand new drive and it's plug and play. The part I don't quite understand is, we must first set the ip address in order for the PLC to push out the parameters using ADC? I was reading that some switches can automatically assign an IP to a new drive, because it's plugged into a specific port on the switch it knows what the IP address should be. Does that feature only work with certain switches, I know we use n-tron switches, but I don't know if those can auto assign IP addresses..
  2. Yes it is in the I/O tree but I do not fully understand how the parameters are backed up. If I were to install a new drive, would it automatically "push" parameters? I'll have to look into Drive Executive, I don't know if we have the software/license. Thanks,
  3. I'm new to this generation of PLCs, CompactLogix. I'm trying to figure out how I can backup the parameters for Powerflex 525 inverters. So far I've found out that if I am online and try to open one of the inverters (ethernet) it says Path Splicing - Failed to splice the path. However if I go offline I can see the parameters. I'm just wondering in the even that we need to replace an inverter, is there a way to "push" the parameter information to the newly installed inverter? I don't see any obvious buttons for it, and I haven't had much luck Googling. I'm likely not phrasing my question well enough.. Ideas? Thanks,
  4. Communication: PV +600 to SLC 5/03

    Thanks, that gives me information to look into for when the time comes. Unfortunately I don't have the luxury of being in charge of the budget. I can, and do make suggestions.
  5. Communication: PV +600 to SLC 5/03

    Interesting... So that means if I have another Panelview 550 die and have to upgrade to a 7 then my SLC 5/03 can't talk to it? My only option is to upgrade the PLC also?
  6. Communication: PV +600 to SLC 5/03

    That is good to know Ken, I do know we use those 1761-NET-AIC converters in several other areas of the plant.. I will eventually learn about those whenever it eventually fails.
  7. Communication: PV +600 to SLC 5/03

    Thanks for insight Joe, I was able to get it working this morning. You are right about the View Studio shortcut being tricky. I had some confusion for a moment because I had copied the design (local) communication to the runtime (target) and the COM Ports were different.
  8. Communication: PV +600 to SLC 5/03

    Yea I haven't made it that far, been a busy day with other break downs. I'm running into another issue now with the converted file, I notice the resolution is messed up for the diagnostics screen so it's not readable. It's very small, when I was going though the migration procedure I selected to scale the graphics and the correct resolution of 320x240 for the PV+600..
  9. Communication: PV +600 to SLC 5/03

    The PV 550 is 2711-K5A2x. The CH 0 is DF1, 19.2 k, etc on the SLC 5/03. It seems like it should work. I'm just running into scaling issues with the converted application it seems, trying that again. So I haven't had a chance to try the comms.
  10. I'm upgrading from a Panelview 550 to a Panelview Plus 600, I already have the HMI files converted. The PLC is a SLC 5/03. I found this post, I am wonder if there is other options besides using a 2711P-RN3. A quick Google seems like it's obsolete, but I am waiting to hear back from a sales guy. I am wondering if I should be able to use the rs-232 serial port DF1 full duplex.  
  11. Unclear on OTE OTU instructions used together

    It's been running for 16 years, however I don't think it uses that logic. According to the people who use the equipment regularly that belt always runs, only the main disconnect stops it. If I'm understanding everything, rung 68 doesn't have a purpose? Maybe it is an unfinished feature. The reason I am worried about it is because I'm tasked with adding a condition that would stop the belt.. So the OTU not really doing anything would make my life easier. The N15:101 integer of 3 is some sort of recipe value, it doesn't change for our usage.
  12. Unclear on OTE OTU instructions used together

    Yea Michael, the OTU and OTE are both enabled by the same N file. If I can import this picture correctly. Joe, in the image there is only two references to the output bit. My confusion is why the OTU instruction is even necessary, if there is no OTL instruction to latch in the first place. My understanding is if the value in the N file isn't equal to 3/4 it would disable the bit?  
  13. RSLogix 500/ SLC-500 I have this program where an OTU instruction unlatches a bit that's addressed to a VFD's emergency shutdown over devicenet. The next rung uses a OTE instruction to energize that same bit. I'm having trouble understanding if those are suppose to work together, and I can't seem to Google the right words. My background is DeltaV, I'm new to PLCs. Unfortunately I'm not able to test the program, I just expected to see a latching and unlatching pair.
  14. Thanks for the added tips Joe.
  15. I'm not clear on this step, I don't see those options in FTView or RSLogix 500. This sounds like my issue then... edit: Oh, I see my mistake now. Thank you so much for both your help. The device shortcut had to be named cpu4 because the diagnostics/error log at the bottom of FTView was spitting out some message about not being able to find [cpu4]::N7. This is all new to me, I won't be forgetting this!