MrPLC Admin
  • Content count

  • Joined

  • Last visited

Community Reputation

58 Excellent

About BobLfoot

  • Rank
    The Wizard
  • Birthday 05/30/63

Profile Information

  • Gender Male
  • Location Southern Indiana
  • Country United States

Recent Profile Visitors

7767 profile views
  1. Part tracking - counting rejects

    If what you are looking for is a rolling count of defects in the last 100 the logic is relatively easy. You have a pair of FFL/FFU instructions and a Counter Register for defects. SO as you said , when you load the FIFO with the part if the first bit is 1 Increment or CTU the counter. When FFL is full as told by the .dn bit, perform and FFU and it the unloaded part has bit one true then decrement or CTD the counter. No need for a nasty for/next loop and cycling through the FIFO stack.
  2. EDS is not registered why?

    I may be reading your post all wrong, but have you added the Card EDS to RSLINX and seen them there?  If not you'll never see them in Studio.
  3. Excellent answer pcmccartney1 only one product I would add to the list OSISOFT Pi is worth considering.  It's what's under the hood of Rockwell Historian, but less expensive and cross-vendor friendly.
  4. Redundancy Processor Online Modifications

    Been over a decade Guy since I had to work with redundant processors, but if you followed the redundancy bible instructions and made your changes to the primary properly they should, emphasis on should replicate to the redundant partner.  Might want to plan a time to turn off the primary and confirm that though.
  5. converting rs232 data

    srsicard3 - I am guessing because you did noy uplaod a copy of your program that you're looking at the data ina tag and trying to figure out what to do with it.  Been a while since I've had to mess with Serial Data, but String Parsing Instructions will be your worst enemy of your best friend.
  6. product gaping on 3 conveyors

    Mattison, not to throw ice water on what you're doing, because it has been done, but it's not easy. First you will only change gap when more than 1/2 the dough piece is on the faster/slower conveyor. Second if you try to change the gap too much you'll stretch or bunch the dough, also not a good idea I would think. For what I discuss following I'm assuming Conveyor A feeds Conveyor B feeds Conveyor C. Conveyor A runs a constant speed and has two sensors.  Sensor 1 is in the middle of Conveyor A and measures Window Size {Lead Edge to Lead Edge},  Dough Piece Size {Lead Edge to Trail Edge} and Gap Size {Trail Edge to Lead  Edge}. I'd measure the sizes in mm and not seconds. Obviously you'll have an ideal condition where all three require no change.  You'll have a condition where the dough piece is fine, but the gap is too small or too large. This will be what you use to calculate your adjust. The second sensor at the outfeed of Conveyor A will determine when you want to ramp up or ramp down Conveyor B. If you've measure distance (mm) and not time, then you can run a confirming set of measurements on Conveyor B with it's sensor 1 and if needed repeat the process going onto C. You'll also need to handle the case where the Dough Piece is oversize or undersized.
  7. RSlinx micro 1000

    Two suggestions: 1. Please Post a Copy of the program you downloaded so we can see what it might have done. 2. Make this post in the AB Forum for more responses.
  8. The fear of FOR TO loops

    Andepand, please allow me to introduce you to a friend of mine.  His name is Joe Relay.  Joe still talks about changing the programming on the saw yard saws by rewiring the relays.  Joe reads Ladder Logic like it was his native language.  But don't try and confuse him with that New Fangled Flow Chart and Structured Text stuff / fluff.  Joe has worked the night shift for years now and one of the reasons I can sleep through the night.  Joe would take one look at your nice fancy loops and reach for the phone to ahve you come in and fix the system when it doesn't run.  Right it out in ladder logic and Joe will let you sleep like a baby with the missus beside you.  I exaggerate a little but you get he point I think.
  9. It will not be a cheap option, but I've used MDT Autosave for over a decade and can say it will do what you want. CHeck it out - .  
  10. CompactLogix Controllers

    You might Open Studio 5000 and create a new project for a 1769-L36ERM {CompactLogix 5370 Controller} and give it a name like test or trial. After Clicking next you'll be asked to choose the revision of the PLC. I have 24,26,27,28,29,30 & 31 installed on my PC so I am presented with all of them as options. I'm guessing 30 won't be presented to you as an option.    
  11. FactoryTalk View - Parameters on VBA

    Not super fluent in what you're trying to do, but does calling it List most every where and then calling it Lista when you assign it to msj1 not cause an issue?
  12. Controllogix/factory talk 15 minute logging

    Please allow me to interject some thoughts / additions to IO_Racks excellent suggestion.  If this is a state requirement and you must have a sample every 15 minutes then you may want to sample every 8 or every 5 in case something hiccups.  Also I would suggest having a watchdog handshake between the FTView and PLC.  Take the Data from your Sensor , place the reading into a FIFO.  If the handshake is alive then pull the data from the fifo and pass to the FTView.  Once that data has been there for 30 seconds and the FIFO isn't empty and the handshake is staill alive send the next data.  This approach will of course mean you'll need not just the reading but a timestamp buffer as well.  But this way when Joe Operator Extraordinaire  turns off the FTView so he can nap and not be woke by it's flashing lights.  You'll still have data.
  13. Clx to micro820 heartbeat

    When working with PLC5, SLC500 and CompactLogix, ControlLogix and GuardLogix I generally use only reads.  It is more efficient and clearer than doing writes.  Now the Micro 820/830/850 ABOMINATIONS are a departure from this.  I do all communications to Micro8XX from the COntrol or Compact logix by read and write.  My approach is simple.  I operate on a Master/Slave Hearbeat mentality as follows:   1) Slave Reads Master Register A  into Slave Register B. 2) Slave Copies Slave Register B to Slave Register C 3) Master Reads Slave Register C into Master Register D. 4. Master Adds One (1) to Master Register D and Places the Result in Master Register A. 5. An Not Equals Statement in the Master compares Master Register A to Master Register D.  If they remain different for more than the desired Fault Timeout then a fault bit is set in Master and COde Activated to act appropriately.. 6. An Equals Statement in the Master compares Slave Register B to Slave Register C.  If they remain the same for more than the desired Fault Timeout then a fault bit is set in the slave and action is taken. This method gives you not only a communications check, but a scanning program check as well..
  14. AB PLC and Zebra Printer/ Scannaer integration with RS232

    Prathamesh - Let me suggest you "eat this elephant a byte at a time". 1. Take a PC with Hypterminal/Putty/Terraterm/<insert favorite terminal program here> and ensure you can RS-232 communicate to printer, then to scanner and finally to 1734-232ASC from the PC. 2. With all pieces communicating to the PC now try and hook the ASc and Printer or ASC and Scanner up. 3. Once you're into step 1 if you ahve questions about programming the 232ASC post back.
  15. Identifying Known Ethernet IP connections

    macg - I have some thoughts on your situation but may be a little long winded in explaining,  It is one of my personal pet peeves that System Integrators and even Plant Support Personnel don't do a good job of handshake between networked plcs.  Were I solving your problem I would set up a network of compact and control logix processors using the produced/consumed data model.  Each Station would have an ethernet card/port connecting to the station IP network of 192.168.C.X and would also have an Ethernet Card?port connecting to the System IP network of 172.B.C.X.  The System network would use Produce consume tags and have logic that as long as the handshake bit was freshly passing between Control Central and Station that Stations Program was scanned.  A station which became unresponseive after being recognized would execute a fault block of logic.  A station not present after power up delay would be considered not attached.  Hope I was clear enough.