MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

19 Good

1 Follower

About pcmccartney1

  • Rank

Profile Information

  • Gender Male
  • Location Colorado
  • Country United States
  • Interests Family, Golf, Lacrosse
  1. Find password from .mer or .apa

    The .mer has a communications shortcut that should be pointing to the PLC at a specific  address.  If you can get to the PVs communications setup and view the device shortcut, you might be able to determine the IP of the PLC and verify that the PV is in the same subnet.  Worst case, I think you edit the shortcut and possible get comms working again.
  2. Find password from .mer or .apa

    If you bought an OEM piece of equipment, you would think that there would be an O&M Manual and the passwords would be recorded there. Generally, most people use the Windows users. Have you called the OEM? Some of us get a fancier and go login/logout through the PLC.  Did they give you a backup of PLC (.ACD or RSS)?  Look at the login and logout macros for each user, it might point you back to some array tags in the PLC and you might see the passwords in there. Post the .ACD and one of us might figure it out.
  3. Flex I/O

    I belive that the only networked IO is possible through a DNet module and only for a couple of the MicroLogix processors.
  4. Flex I/O

    In the project tree, goto EtherNet, right click and add the AENT.  Then specify the addressing, stick length and then add the modules as children of the AENT..
  5. PowerFlex525 Drive Online parameters

    The 525 E/IP board is embedded, it should have been seen by RSL5K if the PC/PLC/PF525 are all in the same subnet.  Either check for the drive in RSLinx,, or use the BootP to set the IP, or Thru the keypad, set the IP, making sure to disable the BootP/DHCP parameter in the drive.  Then try going online with the 525 again.
  6. FTView ME 8.20 TagDB

    Thanks GSteel for posting back the solution
  7. FTView ME 8.20 TagDB

    Nevermind, turns out the FTView ME is not locking up, rather the Tag Browser was off the visible screen.  The technote descries using the Alt+Space method to gain access to the windows tile and then using arrow keys to eventually move it back into visible range of screen.
  8. FTView ME 8.20 TagDB

    Recent issue with my FTView ME Studio V8.20.  When on any object's Connections Tab and selecting on the ellipse for either Tag or Expression, FTView ME locks up.  Dead as a doornail.  Eventually have to open a Task Manager to kill the app, then reboot the PC (in this case, a VMImage of Win 7). Pretty sure it's a call to the MDF file in the project folder, but not sure how or what to look at to repair the lock condition. Any ideas or pointers?  Hoping the answer is not "Uninstall and re-Install". Thanks in advance, Rick   P.S. Interestingly, when using the task manager to kill the app, I occasionally get a new icon in the taskbar for "Tag Browser".
  9. Connect 2 PLC to 1 PVP HMI

    Yes,   Simply define two device shortcuts
  10. Upgrading from Panelbuilder32 to Panelview Plus Issues

    When you configured the shortcut, more than likely you were on the "Design" tab in the right hand pane.  Once you have a viable shortcut assignment, you must copy the "design" tab to the "Runtime" tab, with a convient button for doing so.  THen recreated your MER and download to the PV+.  After reboot, see if you get data and the errors in the various objects go away.
  11. SLC500 to Compactlogix Migration

    I might be wrong but.... The limitations on I/O Modules for the CompactLogix are with regards to the 1769 bus.  I think that because you are using an 1747-AENT, you would be more concerned with EtherNet connections and probably are fine. I suggest you test configure say a 1769-L30ER and see how many 1747-AENTs you can add and have the controller verify.  You next consideration will be memory for code.
  12. Interfacing of plc and vfd

    From Rockwell's Knowledge Base, ID 122258 has a link to "1766-RM001F-EN-E MicroLogix 1400 Programmable Controllers Instruction Set Reference Manual". Chapter 23 gives complete information regarding messaging via Modbus TCP with the MLX as Master. http://literature.rockwellautomation.com/idc/groups/literature/documents/rm/1766-rm001_-en-p.pdf
  13. Rsnetworx for devicenet

    From within the RSNetworkx for DeviceNet, goto fFile Menu and select "Generate Report".  You will then see a dialog to select either "selected devices" or "entire network".
  14. [newbie] help regarding modbus communication

    You'll need to be more specific, there are many different versions of Modbus communication protocols. RTU, TCP, etc...
  15. RXLinx network item UNKEYED

    Yes, if you want it too. You need to open your project and look at every comms module and IO module and determine what level of compatibility you want to force the module to comply to.  Read the help doc in RSL5K and choose carefully.  The results of your selection will affect how the system responds.