pcmccartney1

MrPLC Member
  • Content count

    582
  • Joined

  • Last visited

Community Reputation

81 Excellent

About pcmccartney1

  • Rank
    Expert

Profile Information

  • Gender Male
  • Location Colorado
  • Country United States
  • Interests Family, Golf, Lacrosse
  1. simatic-op is on a write-protected medium

    Pretty sure it's telling you that the memory cards in each device have their respective write-protection switches turned on.  Just turn them off, then when done, turn them back on.
  2. Replacing a motor for powerflex 755

    Nothing to do in the PF755 or PLC, if and only if the replacement motor is identical in all it's characteristics and nameplate data.
  3. Unconfigured I/O Address Used

    I which ladder instruction are you typing this into?  Some do require word level and will not accept bit level addressing.  If you need the status of that specific bit, you might have to move (MOV) to another integer valve, something like N7:x and use that in the ladder instruction. Quite often as you type in the address and dropdown window will show you the next available address.  If you don't see it indicating the next available bit, then the instruction is looking for a word level address. Post you program and we'll know how to better answer your question. By the same token, the instruction help will tell you the acceptable addressing and format for each element in the instruction.
  4. Dan, You make me think back to my days in the power generation field.  I remember working with many Bentley-Nevada systems and then having to go with their IO to a third party Sequence of Events Recorder before getting any data or signaling into the PLC or DCS.  Hopefully, that's a much easier task these days.
  5. PanelView plus 1250 slow response on the HMI screen

    To add to Mel and Mav's comments.  What type of processor are you communicating with? In the case of a SLC or MLX, you'll want to include a service interrupt in the PLC program.  This allows for the program scan to be interrupted to allow for "other" devices to communicate with the PLC. In the case of Compact or ControlLogix, you'll want to look at the settings for program scan versus overhead (communication with other devices). 
  6. RFIDeas RFID reader with micro850 plc

    Yes
  7. RFIDeas RFID reader with micro850 plc

    Went to their website and searched their Knowledge Base for E/IP and found complete details for configuring both the reader and the PLC.
  8. Unexpected file format file translate help

    Not sure what ProSet200 means.  Additionally, no idea what an ACH.  If it's a RSLogix500 compatible program, it will be something like programname.RSS.
  9. Allen Bradley CNC or PNC

    I don't think they have any CNC Controllers.  While they have plenty of servos, drives and PLCs, the PLCs are not programmed in anything like G or M Code.  Additionally, I don't think they are capable of taking a Solidworks or equivalent and downloading or converting it into CNC code.  Rather, their Motion Analyzer can and would be capable of defining the various motions, speeds, etc, but again in a PLC or Ladder like coding format. Seems to me that CNC is more the domain of Siemens or Fanuc.
  10. Fork terminals for Mitsu PLS's

    Why not "bend" the fork in relation to the crimp portion at a 45 Deg angle or even 90 Deg and move on.
  11. HMI G3 not working using Crimson 2.0

    Within the Crimson software, the displays are configured.  Each object with have a reference to a tag within the tag database.  Those tags are contained within one of those configured protocols, ex. ML1500, Raw TCP/IP, etc... Maybe you could post the Crimson file.
  12. HMI G3 not working using Crimson 2.0

    I would have thought that changing the IP of the G3 should not affect the data exchange with the MicroLogix 1500, as that is a serial connection with a protocol called DF1. Are you sure that the information on those displays is coming from the ML1500? Your picture of the crimson shows a couple of connections to raw TCP/IP.  Those are ethernet devices and they would probably need to be updated with new IPs and updated driver information within the Crimson software and the G3.  
  13. Fx5ucpu, FX5u cclink ms using link with ifm io link

    The IO Link Master you selected, AL1342, is a Modbus TCP Interface.  Can your FX5U PLC talk Modbus TCP?  I see no issues with CC-Link module talking to the SMC if SS5Y3-10SVAN-16BS-C4 is CC-Link.   If the SMC valve bank truly has a CC-Link version of EX600, you are better off adding a couple of 4 point output modules to the SMC valve bank.  Just make sure the loads you are driving are within the capability of the SMC Output modules.
  14. Fx5ucpu, FX5u cclink ms using link with ifm io link

    Not to confuse the issue, but.. You stated originally that you have a FX5u with CCLink and plan to attach an ifmEfector IO Link device for 8 outputs. Please understand that CC Link is not IO Link.  Meaning you will need a protocol converter.  Normally this is done by using an IO Link Master block with the specific protocol you are trying to communicate with on the PLC.  A quick look at ifmEfector's various Master blocks, they have nothing that talks CC Link.  Rather they have many varietyies that talk AS-I, EtherNet/IP, EtherCAT, Profinet, etc... Probably need to have a conversation with your ifmEfector rep to get a better understanding.
  15. Safety Door Locks

    Wow, that is some box and pricey. We use Euchner with E-Stop and three other buttons (Cycle Start, Cycle Stop and Reset).  It is not CIP Safety capable.  Rather we've defined which inputs and outputs are safety and standard IO.  A 19 pin cable comes back to the panel for termination.  We then developed our own AOI for control of the door switch (also for other platforms like Siemens, Omron, etc...).  What I fear is that it's about break even on the pricing after the cost of the unit, the connection cable, the Point IO (both safety and standard).  When I say it's our standard, I mean that we use it across any PLC platform.  As in integrator, we supply systems for darn near any PLC Vendor. The documentation makes it look pretty easy to integrate, as long as it's a GuardLogix controller.  Not sure how to handle it for other platforms, unless, by some wild change the have other models with different protocols like ProfiSafe.