bwhinch

MrPLC Member
  • Content count

    31
  • Joined

  • Last visited

Everything posted by bwhinch

  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. Yea I would like to customize PlantPAx but I don't think I have the time to read. I'm not sure how it works and I don't want to break anything. I just need to get information on the screen for the electricians.
  3. I'm trying to figure out how to make an overlay visible if a button on the HMI is held down, I'm hoping there is a way without modifying the PLC. We have a plant with hundred of motors, I'm wanting to make a simple overlay that displays text over a motor to say what MCC and section the drive is located. We are using PlantPAx objects, however they don't really have a spot to enter MCC locations. I'm guessing I'll need to use VBA, however I'm hoping to only modify the HMI.
  4. I'm new to PlantPAx, and trying to make sense of some new equipment at my plant. There is a P_AOut AOI that will stop passing an input PSet_CV through it to Out_CV (to a 4/20mA Fisher Valve). There is no indication on the HMI of a fault. I've found toggling OCmd_Reset clears the fault and the valve resumes controlling again for a short while. In the P_AOut AOI I noticed the fault shows up under Val_Fault as 32 indicating a I/O Fault. If I trace PSet_CV back to the previous function block diagram, it's from a flow control P_PIDE AOI. That seems to be where the faceplate is linked to. It seems to be a cascade setup. The flow control PID sends the setpoint to the analog output AOI. I just don't understand how the faceplate is linked...  
  5. 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,
  6. 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,
  7. 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. http://www.plctalk.net/qanda/showthread.php?t=105902 I am wondering if I should be able to use the rs-232 serial port DF1 full duplex.  
  8. 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.
  9. 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?
  10. 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.
  11. 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.
  12. 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..
  13. 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.
  14. 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.
  15. 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.
  16. 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?  
  17. I'm attempting to make a backup of a program, complete with comments. I go connect to the PLC over Ethernet, and select Use Upload File to merge the comments from an original copy of the program. After that, I go file-saveas to backup the program. However the new saved file, complete with comments is only 134 KB, and the very original copy of the program is 230 KB, from 2003. Is there a reason for this, the program hasn't shrunk in size, only minor tweaking of some span calibration numbers.
  18. So I am following this procedure,  https://literature.rockwellautomation.com/idc/groups/literature/documents/ap/2711p-ap001_-en-p.pdf and I am stuck on page 53 of 102. Step 3/4, I can't see my controller under the ethernet driver. If I close FactoryTalk View Studio, and open RSLinx I can see the controller and existing field HMI fine. It seems like I am missing a step that I can't find in the guide. We have 4 pieces of equipment with their own controller and HMI. I am able to see the controllers for equipment 1 and 2, but not 3 or 4. And 4 is what I am trying to connect to, in order to test out the converted hmi program.
  19. 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!
  20. Does the device shortcut name matter, I'm not clear its purpose? I have right-clicked on the Ethernet driver and added a device with IP in both the local and runtime tabs. And clicked apply to the previously mentioned device shortcut. I just noticed that if I make a 2nd Ethernet driver, it auto-populates with a lot of our equipment IPs. Except for the SLC that I am looking for, which I have verified again is active. As a side note, what version of windows is your virtual machine with FT View Studio. I have a laptop running Windows 7 64-bit which only lets me import a PanelBuilder 32 into FT View if I remote desktop into the W7 64-bit machine via my main W10 machine. I think it is because FT View maybe running in 32-bit mode over a remote desktop connection...
  21. Is there anything that I need to configure seperately in RSLinx Classic then? I have added the ethernet drive with the correct IP address to the PLC but I am still not able to connect when testing the converted HMI. I don't have something configured properly, but I can't figure out what. I can ping the IP, it is valid. I have RSLinx Enterprise drivers setup in both the Design (Local) and Runtime (Target) tabs.
  22. Ok thanks, I had seen configurations for equipment 1 and 2 and thought it auto-sensed it.
  23. The issue is I can not see the plc or hmi in RSLinx Enterprise, however I can see them in RSLinx Classic.