kpizzolatto

MrPLC Member
  • Content count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About kpizzolatto

  • Rank
    Sparky

Profile Information

  • Country United States
  1. Controls Engineering Company is looking for PLC experts who “eat, sleep, and breathe” ControlLogix and are looking to expand their knowledge and capabilities with the product. Candadate needs to be willing to step out of his comfort zone and be willing to be challanged to learn while working with the best. Looking for someone willing to: • Work daily in a laboratory located in the Cleveland, Ohio area. • Willing to commit to a 12 month assignment. • Willing to accept $100,000.00 to $110,000.00 for his trouble. If interested, please send résumé in Word format to: jstroud@teamses.com
  2. Q12H and QD75M4 OPR Parameter help please

    Dropped Y40 for .5s whenever somebody applies one of the new OPR settings. Made it out to the Client's facility last week; it worked perfectly. THANKS!!! (I always dropped Y40 on estop, too, but maybe that doesn't count. Why the estop didn't do it, I don't know.)
  3. First, please accept my thanks for any help you can give. I've gotten good advice from the folks on this board in the past and do certainly appreciate it!! Briefly, I have successfully sent OPR parameters from the PLC to the QD75M4 for 4 axes, but the QD74M4 doesn't act upon the new values. I can see new values for Pr.43 and Pr.45 in the QD75M4, but they are ignored when I execute an OPR. To make the new values active I simply connect in "Test Mode" using GX-Configurator QP, then exit test mode. After that--viola! the modified parameters are active! How can I skip this GX-Configurator step and make them active by a command from the PLC? Here is a detailed description of what I've done and what I've observed so far: The QD75M4 is in "slot" 4 (address 0x40 by bit or 0x04 by word). The PLC is a Q12H. Other notes and references at the end. I've given them a "Seek Prox" and a "Set Pos" button, also, the ability to "ENTER Value". Example "Seek Prox" button for axis 1 (note set pos is similar, except P4.43 is set to 6): User goes to the Homing screen (so, this happens before they press any buttons) PLC tells the QD75M4 that the next move command will be an OPR (Cd.3): [MOV K9001 U4\G1500] User enters a value into D7828,D7829 which he wants applied once the OPR is complete PLC tells the QD75M4 the new OP Address to apply (Pr.45): [DMOV D7828 U4\G72] User presses the "Seek Prox" button PLC tells the QD75M4 this OPR will be type 0 "Near Point Dog" (Pr.43): [MOV K0 U4\G70] PLC reads the OPR type back from the QD75M4 (Pr.43): [MOV U4\G70 D7693] After confirming the QD75M4 got the new type of OPR, the PLC sets the "Go" command (): -()-Y50 Axis executes an OPR, according to some previous configuration of Pr.43 and Pr.45. So, here is the problem--now the configuration Pr.43 and Pr.45 are in the QD75M4 (see below). Once they are applied, the axis executes the OPR in exactly the expected manner. But--until then, the new configuration is ignored! To get the new configuration to become active, I've tried the following: In this case, a "new configuration" would be any change to Pr.43 or Pr.45 ESTOPping the machine (removes run permissives) Explicitly sending a HALT to the QD75M4 from the PLC -()- Y44 Doesn't work Power cycling the whole machine (OFF, wait 5 minutes, ON) Doesn't work Connect to the QD75M4 with GX Configurator QP, create new "untitled" project, enter "Test" mode, READ up the params from the QD75M4, exit "Test" mode. After this, the new parameters function. The selected positions and the new OPR method are now active. Note I know they're already IN the QD75M4 before I do this because the PLC confirms the OPR method, and I can use Buffer Memory Monitor to see the position setpoints. They could have only come from the user's entry into the module via PLC. What is it that GX Configurator QP sends to the QD75M4 to make it see the new parameters (which the QD75M4 it already has!) How can I tell the PLC to do that? I guess there is some Yxxx or Buffer Memory command I have to toggle in the PLC--but what?!! Note: The home dogs seem logically inverted, too. I don't expect this has anything to do with the question above, but it seems weird. Normally-Open home dogs are installed (that is, we see measure voltage at the input when the axis is on the prox and the prox LED is on). But GX Configurator QP reports "Off" when this condition is true (LED is on) and "On" otherwise (axis is off of the prox and LED is OFF). In section "Signal layout for external device connection connector"... The manual says the following re "Near-point dog signal" This signal is used for detecting the near-point dog during OPR. The near-point dog OFF ON is detected at the rising edge. The near-point dog ON OFF is detected at the falling edge. OK, so to me this says wire it normally open, but ??? References "Positioning Modules QD75M1, QD75M2, QD75M4", Art. no.: 149924 01 04 2004 IB (NA) 0300062-B Version B
  4. Help: GE Proficy ME 5.70 beats the HDD to death!

    So, the short answer is there is something on my laptop that Proficy can't handle. If anybody has some idea of an incompatibility I could look for that would help; otherwise, thanks for the advice you gave Blow-by-blow below Well, I uninstalled per the instructions, reinstalled 5.70 (w/ everything), rebooted, applied updates, rebooted, etc... Tried to use the PLC developer; hard drive spun for about 20 minutes, then I tried to close the app. No response. Tried to kill the app by process explorer--still no response. And the HDD spins... Finally gave up & rebooted the machine. Try to start the app again; nothing happens. I mean NOTHING--nothing in the event log, no process starts; nothing. Uninstall, reinstall (just Logic dev PLC, this time), etc. etc. Try to start the app; nothing still happens. This is a field service laptop with EVERYTHING installed on it--I'm surprised it worked this long. Rockwell, GE, Pilz, Siemens, Mitsu, Omron, Automation Direct, Eaton, etc. It did work once before, but that was many versions & updates of many other industrial softwares ago... I have an old "clean" windows VM--just XPSP2; nothing else. Install to the VM (just the PLC stuff). Create a new "empty" project called "DoesTheDamnedThingWork" Create new target VersaMax...YupItWorks... And...It works...
  5. Help: GE Proficy ME 5.70 beats the HDD to death!

    Thanks very much--what I'm hearing from you is this is NOT normal behaviour. Unfortunately, an upgrade costs money, so that will NOT be happening any time in the near future. So I got the cklist & the zip & chm for 2 updates . The uninstall checklist at KB12350 specifies "Instructions valid for all SIMs of PME version 6.00 and older..."; I have 5.70, but I'll take any help I can get at this point!
  6. I haven't used GE much lately, so all I'm looking for is some feedback from those who do: Briefly, it's acting as if there's very little memory and a giant swapfile. EVERY thing I touch causes massive HDD traffic. Before you ask, XP reports 3G of real memory, and all the other apps run just fine. Prior to starting up proficy, only 1G is in use. Details follow, and thanks to ANYONE who can help!!! Do you find that Proficy ME (we have an old version--5.70) tends to beat the hard drive? If I start Proficy ME and create a new empty project then a new target (VersaMax) it takes 5 or 10 minutes (really, I timed it; it's that bad...). During that period, proficy shows "Not Repsonding" in the title bar and the HDD almost solid ON. After just creating a couple modules, process explorer says proficy has transferred a total of 7.7G from/to the HDD!! Also, each time I click on anything in the project tree at the left (ex.: Right-click to create a VersaMax, then wait for it to appear, then right-click to create a new IO module under it), the hard drive lights up AGAIN, stays on for a minute or two, then I get the context menu and can create the module. I recall from working with it in the field on 90/70 PLCs that it's pretty frustrating and balky software, but never seemed this miserable. Can anyone tell me what might make Proficy beat the heck out of the HDD? Has anybody seen this before and solved it? Did a reinstall fix it? Did you find some database or cache that has become too huge and purge it? I cannot believe this software sucks so hard--I must be doing something wrong!
  7. If you really want sequential execution, maybe SFC would be a better language? This costs extra, so maybe you're stuck with ladder. You can get sample code from RA for step sequencer in ladder Sample code search "sequencer" There's AOIs that let you execute ladder one rung at a time, and transition to the next when you get past the current. You can see if a step faulted and which step you're on, too.
  8. A-B Power Flex 400 Radio Noise

    Something is definitely wrong; you should not be seeing this much interference. Have you installed just a PowerFlex 400, or do you have appropriate enclosure, grounding/bonding, and line filters? Have you called your distributor? Even if you don't have a tech support contract, for 12000, somebody should at least talk to you. I just got a PF4 in for a well pump in my house; here's what the AB folks told me before I spent the money. Here's the typical stuff they warn you about: Install in bonded shielded box Lower your chop frequency Watch out for reflected waves--cable length is an issue, though the manual says not at 230V. Filter the incoming power appropriately. Filter the power to the pump if reqired for reflected wave protection. Use a VFD rated motor & cables. Here's some links to AB manuals that may help you: PowerFlex 400 Manuals Some particular ones you might find useful: PowerFlex 400 Input RFI Filters PowerFlex 400 Adjustable Frequency AC Drive Quick Start Adjustable Frequency AC Drive for Fan & Pump Applications User Manual Here's some general references about EMC Earthing, Bonding and EMC System Design for Control of Electrical Noise Good luck, and please followup when you find a solution.
  9. Position Control with QD75M

    Yeah, during the initial design, but we decided not to use it because we wanted a "move complete" not a "close enough" condition. Of course, Pr.16 is at default (.00100 inch), so that's probably close enough. From the manual... "The command in-position flag is used as a frontloading signal indicating beforehand the completion of the position control." At this point, maybe that's as good as you'll get from Mitsubishi? I'll forward it to the engineer in the field. Any ideas on the position feedback? Md.20 and Md.21 don't seem to tell us where we really are. Thanks for your help!
  10. Position Control with QD75M

    Position Feedback with Mitsubishi Servos GoToPosition.zip Does anybody have experience with Mitsubishi servos and time to answer a question? Most parameters, except target positions, are set by GX-Configurator QP. All the equipment in question is from Mitsubishi. I've got a QD75M4 motion control module and four MR-J2S servo amplifiers. They are controlling four HC-KFS43K motors. The PLC involved is a Q12H, not a dedicated motion control PLC. I'm using simple single-step (end) or two step (continue, then end) motions to send servos to PLC-specified positions. I'm using a couple of bits to generate a "move complete" status in my PLC: X14 (positioning complete--the step is complete) NOT XC (busy--the servo is executing a move) And I'm monitoring position feedback using Md.20. The problem is that in certain moves when the servo is mechanically prevented from achieving its target position, I still see X14 AND NOT XC And my position feedback (via Md.20) shows that I have reached my target position. I have tried to find another method using this equipment to achieve the goal, but I'm having no luck. I want to send the servo to a position, get feedback indicating "at position" when it's there, and monitor the actual position whether the servo reachse setpoint or not. Has anybody successfully done this? How might this be done with the equipment above (using the general-purpose Q12H PLC, not a dedicated mitsubishi motion control PLC)? A more detailed version of the above question is restated below. Thanks for your help! The manual I reference below is QD75M Position Module Software Manual V2-D.pdf, identified as Type QD75M Positioning Module User's Manual IB(NA)-0300062-B(0404)MEE The servos drive ball screws with "sleds" mounted on the nut to carry workpieces That's not really important as the encoders are attached to the motors, not the ball nut. All axes are independant and all moves are simple "go-to-position" commands. The moves all use CTRL Method 1: ABS line 1 (Axis #1 Linear control (ABS)) move, which controls speed to a set position. Each move can consist of either a 0: END (End command) segment a 1: CONT (continue positioning control) segment followed by an 0: END (End command) segment. The second type of move is for high speed approach followed by creep speed final positioning. Two of the axes are pick-and-place, and reliably reach their commanded position every time. The other two axes bring two workpieces together, and due to lack of precision in prior measurement sometimes cannot reach their final position. For all axes, I create a "move complete" bit in the PLC using X14 (positioning complete) and NOT(XC) BUSY per p6.3 (Fig. 6.3 ON/OFF timing of each signal at start of positioning). Also, for all axes, I read current feed value via Md.20 For axes which do not achieve target position, we expect to see either the "move complete" (generated in the PLC as above), or an error. We also monitor the current feed value from Md.20 as above. This is so that we can adjust the position of the next equipment in the process. It seems that the QD75M4 reports move complete and current feed value Md.20 = target event though position has not been achieved. To test this, the Engineer onsite installed an oversized workpiece so that the ball screw could not achieve final position, then executed the move to go to that position. 1. We get "move complete" (X14 TRUE and XC FALSE with no faults, per sec. 6.3 above) even though the sled doesn't make it to the specified position. The command in-position width is .00100" We would expect the servo to fault on a following error if it never made position, but it just stops with no fault and maintains force against the workpiece. We monitor axis faults at Md.23 (Active Error Code). 2. The current feed value Md.20 shows that actual position = target position, even though we can see it has not occurred. Previously, the Engineer scribed a line on the ballscrew carrier while the sled was at the target position. During this test he observed the sled is around an inch short of the line, even though the current feed value Md.20 reported target position had been achieved. I would expect the feedback to report the actual position, not the target position. If not at Md.20, then I would expect some other parameter to report the actual position. To check this, the Engineer grabbed the sled and moved it back about 6" against the force of the motor. After releasing the sled, the motor returns it to the position against the workpiece where he grabbed it. Current Feed value at Md.20 and Machine Feed Value Md.21 never changes. If the Engineer drops 240V power, but not control power to the servos, (just opens the safety gate) current feed value from Md.20 abruptly changes without the sled observably moving. Reported value in Md.20 is roughly consistent with actual observed positon. At that point, moving the sled produces the expected change in current feed value Md.20. We have tried: Monitoring Md.21 instead of Md.20 Both behave similarly, except that Md.20 reflects the offset applied during setup via OPR. Changing Pr.21 (Current feed value during speed control) to 1 (The current feed value will be updated.) produces no change in the problem. Ref 5.34, Pr.21. I've read multiple Mitsubishi motor, PLC, servo, and motion controller manuals, reviewed the parameters the software GX-Configurator-QP, looking for some parameter I have set wrong, or the correct parameter I should be monitoring. I'm finding nothing. I want to send the servo to a position and get feedback to the PLC that tells me: 1. I've reached position within tolerance. 2. The actual position of the encoder at all times This seems like a fairly straightforward application of a servo (a very basic one, actually), but I just don't see how to do it with these products. Has anybody successfully done this? How did you do it? Thank you very much for your kind assistance! For reference, I've attached the configuration files from GX-Configurator QP. Note that we populate the target positions in the positioning data from the PLC (they're all zeroes in the GX configurator file).