BobLfoot

MrPLC Admin
  • Content count

    3172
  • Joined

  • Last visited

Community Reputation

32 Excellent

About BobLfoot

  • Rank
    The Wizard
  • Birthday 05/30/63

Contact Methods

  • Website URL http://www.generalmills.com

Profile Information

  • Gender Male
  • Location Southern Indiana
  • Country United States

Recent Profile Visitors

5039 profile views
  1. Question on PowerFlex4 Drives

    It has been some years since I put single phase on a three phase drive but the older Yaskawa, Toshiba, TB Woods and some AB drives would run a load just fine if Single Phase was on Phases A & C, leaving the B Open.  The only issue was you needed to derate the unit.  If you put 480 on L1/L3 you'll either get a missing phase error or a testable drive.
  2. Macro Burned by the Micro 850

    I'll try and keep this neutral and not degenerate into a rant, but my recent experiences with the AB Micro 850 have been less than heart-warming and encouraging.  We recently purchased a production line for my place of employment from a trio of OEM Equipment builders.  All were supposed to use AB ControlLogix or CompactLogix PLCs.  However, two of the vendors called purchasing and said "let us save you some money, by using the Micro-850 PLC Rockwell's latest and greatest offering".  And our purchasing bought it.  So this week we brought in a Rockwell Premier System Integrator to add 9300-ENA units to these machine so we could collect SCADA Data from them. Now in full disclosure these were CCW version 6 not the latest and greatest 9.1,  So we came to machine 1 a micro 850 and uploaded, saved a copy for safety, then changed the Gateway  from blank to the NAT device IP and downloaded.  Machines on our SCADA Net could now see the Micro 850, but the machine it was in wouldn't start or communicate with the Component Panelview.  Turns out that thing was in remote and came up in program.  Chose run and all appears well.  Go on and do machine 2 another Micro - 850 and it went equally flawlessly.  Our downtime window was up so we started making product.  Only one problem the previous maximum speed was unattainable.  As a matter of fact several configured variables were at their Initial Factory State rather than the state they were when we shut down.  SO HERE COMES BURN NUMBER ONE.  Upload and Save only gets the logic not the variables or the values.  You must export the Controller and each programs variables to a separate excel file to have them around to restore.  That means 1 upload and 15 exports per machine backup and no word of this "FEATURE" in the tech database.  Now today we got a window to do the third machine also a Micro-850. This time we went to program and changed the Gateway without downloading.  Went back to run and all was well in CCW, except the NAT couldn't find the Micro-850.  Blowing the project totally away and doing an upload we learned that the Gateway was not there.  So we did the 1 upload, 15 exports, 1 download and 15 imports and this time all worked fine.  SO HERE COMES BURN NUMBER TWO.  So now we try and place message instructions from Machine 1 to Machine 2 in place and nothing will communicate.  Now before you think we're total fools we had to Micro-850's talking to a Compact Logix on the shop bench just fine when they were all in the same subnet.  But when we placed NATs between them nothing works.  Hopefully our SI will sort this out over the weekend and I'll post that answer later.  SO HERE COMES BURN NUMBER THREE.  We've decided it is in our best interest to flash our Micro-850's to version 9.1, but given the Micro's track record we decided to flash a spare first and swap it in.  Only one problem, the Micro-850 is either such a hot commodity or poor unit that you can't get one for at least 2-3 weeks.  ANd FINALLY BURN NUMBER FOUR.  Trying to troubleshoot this week I wanted to force an INPUT on; only there is no right click and force option.  It is called variable monitoring and you must lock and un-lock.  It has been FORCE for two decades, why change what we call it.  Really did we need to make this more complicated.   OK I am done.  I will not knowingly spec or buy another 850 in my Plant.  Enough said.  Control and Compact Logix only.
  3. ANSI / OSHA Standards Search

    Turns out NFPA 54 - National Fuel Gas Code is the most applicable.
  4. PLC Law

    It is out and in the downloads sections.  The "official 2016 - 10 year anniversary edition" of the PLC Laws.  Enjoy and chuckle.    
  5. PLC LAWS 2016 Edition

    Version 1.0.0

    220 downloads

    The 10 Year Anniversary Edition of a community guide on what to do and what not to do in the world of Automation.  Thanks to the members of MRPLC for submitting such humorous anecdotes.
  6. PLC LAWS 2016 Edition View File The 10 Year Anniversary Edition of a community guide on what to do and what not to do in the world of Automation.  Thanks to the members of MRPLC for submitting such humorous anecdotes. Submitter BobLfoot Submitted 01/11/16 Category Tutorials and Guides
  7. PLC Law

    Ok -- I bit the bullet and edited a new edition finally [2016 Edition].  It is with the proof readers now and hopefully will be available in the downloads section in a week or so.  thanks gleblanc, RussB and JordanCClark for your assist.
  8. I am looking at a project which will use an Open Natural Gas Flame to modify the product passing the automated cell.  My question is what OSHA / ANSI standard is there for Piped natural gas to an open flame?  I can find Bottle Gas and Oxy?Acet standards but nothing that seems to directly apply.  Thoughts anyone?
  9. KF2 and Rslinx enterprise

    First I am pretty sure your PLC is an SLC 504 not 405.  Second have you confirmed that your PSV1500 is using Dh+ and not RS232 to talk to the SLC?  If so it should be a matter of configuring the Linx Classic driver to see the PSV. Or configuring Linx enterprise on your laptop/PC so FTView can see the PSV.
  10. I am relatively new to Modicon PLC and trying to find a memory map that will help me out.  I understand the 0xxxx are output and 1xxxx are digital inputs, but in the Ab world I had S registers which contained the system clock and fault/status stuff.  Is there a document with the full register/memory map of the 434 or 534 CPUs explained.  Mr. Google and I haven't had any luck finding it yet.
  11. Well we updated from 434 to 534-14B and the Traffic Cop was an issue.  Turns out previous tech setup traffic cop for the 200 series I/o online and even though you read from the controller both standard and extended memory the traffic cop configuration is not uploaded.  This meant we had to reconfigure traffic cop in the 200 series I/O for the Model 534 cpu.  And of course Columns and Row don't translate to Racks and Slots as a sane individual would do it.  We had Rack 2 Slot 8 above Rack 3 Slot 6 whcih was above Rack 2 Slot 1 and Rack 2 Slot 2 in column 1.  Turns out there is a knurled pin with 8 slots and this determines the slot number.  And Inputs get placed on rack 2 and outputs on Rack 3 and there is no Rack 1.  Bottom Line it was learning curve but it was successful.  And yes We know the 434/534 are obselete but they are still working.
  12. Using Proworx with our Modicon PLC over ethernet occaisionally the connection drops and we encounter a situation where the programming mode bit is set and no one can gain programming mode. I've heard rumor that a block write from a neighboring modicon can reset that bit, but can't find the proof that this idea is anything more than "wish ware". Anyone know?
  13. Should I be concerned that traffic cop on the 434 is missing some racks which still work and has others defined which are "vapor ware" ?
  14. I am working in a "vintage" facility using ProworxNxt and need to migrate a CPU434 system to a CPU534. Can any proivde a referemnce or the broad strokes for doing this. I have changed the CPU in traffic cop using ProworxNxt offline, but not sure if there is anything else I need to do or how to "stuff" this new program into the CPU534?
  15. Connected Component Workbench

    I have not used CCW for PLC Programming, but every other RA Product I'm familiar adds the END invisibly even if you don't see it in the GUI/HMI. Best I can suggest is give it a try.