Joe E.

MrPLC Member
  • Content count

    488
  • Joined

  • Last visited

Everything posted by Joe E.

  1. I remember one being pretty quick, another took much longer.
  2. From what our vendor told us, the license for v14 will activate v13 as well. You do have to install the software, though.
  3. SLC 5/03 AND EZ3 TOUCHSCREEN

    Counters are usually retentive, I'm not sure why they're resetting on you. What controls the B:3 bit that you're using to reset the counters? Is it just the HMI? If so, does the HMI have a setting that has it write that tag on power-up (I remember something about that with some HMIs but it's been a long time since I worked with an EZ Automation one)?
  4. Copy INT into second half of a DINT

    Also look at the COP instruction. If you set up your INT as one INT in an array of 2 INTs with the other INT being whatever needs to be in the lower word of the DINT.  You then COP the array into the DINT using a length of 1. Alternatively, you can MUL the INT by 2^16 (to shift the bits 16 places to the left) into a holding DINT tag and then MVM (masked move) the holding DINT into the destination DINT. It looks like the BTD instruction will be the cleanest option, though.
  5. We had a problem on an old Phase I DriveLogix processor where it would lose its memory sometimes when the power was turned off. The electricians would replace the battery every time even though the battery light wasn't on. It turned out that the battery wasn't the issue at all but it was a problem with the hardware that went away when we replaced it for another problem. I can't find the knowledge base article on it. I don't know if the L61 had a similar bug or not.
  6. Communications Issue

    If you're connecting to a CompactLogix PLC through its serial  port, you will almost certainly need a null modem serial cable. I would think that the standard SLC cable would work, but I just use a regular 9-pin serial cable with a generic null modem adapter to connect to these.
  7. How To: Panel View Plus

    You will need Factory Talk View Studio for Machine Edition to configure your HMI. It comes with RSLinx Enterprise which sets up drivers to allow the HMI to communicate with PLCs. If you don't have the software, you will need to contact your local Rockwell distributor. If you have all of that.... If it's a brand new HMI, it should boot to the configuration screen. You can navigate through the options (I don't remember the sequence since I don't do this often) to find the Network adapters and set the IP address. After a power cycle, you should be able to connect to it with your PC as long as both are on the same (or routable) subnet.
  8. Allen Bradley fail safe IO module ??

    It sounds like you're looking for a safety PLC or a programmable safety relay. Depending on how much safety I/O you need, their CR30 safety relay: http://ab.rockwellautomation.com/relays-and-timers/safety-relays/guardmaster-440c-cr30 Programming is done with their free CCW (connected components workbench) [ugh] or it can be integrated into a ControlLogix/CompactLogix project file if you add an Ethernet module to it.  
  9. RSLogix500 Ladder Problem

    Not sure exactly what you're looking for... So you have a bunch of bits. Do you simply want to know the elapsed time since any bit changed state? Either going on-off or off-on? It will be simple if they're in one word, which is easy to do if it's 5000 platform. First copy the bits into a DINT address: XIC Bit0 OTE Word.0 XIC Bit1 OTE Word.1 etc. Then simply do a compare. If the word is not equal to its predecessor, reset the timer and move the word into its predecessor.
  10. Logix5000 Problem

    The first time I started using 5000, we had versions 10-15 installed and the compare tool was definitely present.
  11. Logix5000 Problem

    The compare tool is still there; I used it just a couple of days ago. I think it's an option you have to select when installing the software. Once it's there, it shows up in: Windows Start Menu -> All Programs -> Rockwell Software -> Logix Designer Tools There is also an option when installing it for it to end up in the "Tools" menu inside the software, but I've found that to be hit or miss. Sometimes it works, sometimes it doesn't. I don't bother with that any more; I just leave it in the Start menu. I think it's normal for a cancelled online edit to trigger this. If you compare and find that there really is no difference, just go online and save it.
  12. Packing two USint into an INT

      In the Siemens world, words and doubles are divided up into bytes. Here's a little cheat-sheet I made up a while ago to keep it straight in my head (Least significant bits/bytes are to the right): So, if your information in integer X needs to be stored inside the higher-order bytes of DB10.DBD8, you would simply move it into DB10.DBW8. If the information in integer Y needs to be in the lower-order bytes of DB10.DBD8, you would move Y into DB10.DBW10. If you're using "M" memory instead of DBs, you can just substitute "M" for "DB10.DB" above. IOW, if your destination is MD100, you would move X into MB100 and Y into MB102. Disclaimer: I've only just gotten TIA Portal, so I can't post an example for you, but the data structure should be the same.  As with everything "weird" like this, you will want to use a test PLC to make sure this works the way you expect it to. If you don't have a test PLC, you can test it out with unused memory in your main PLC.    
  13. Etherhet problem compactlogix 1769-L32E

    Their BOOTP program is really...flaky. Make sure that all other network adapters on your PC are disabled, enabling ONLY the adapter that's connected to the PLC. I don't think that's strictly a requirement from Rockwell, but that's the only way we've been reliably able to get it to work. Sometimes it takes a power cycle of the PLC or a reboot of the PC. In the BOOTP utility, go to Tools -> Settings and make sure that's set up. If that PLC has a USB port, I would just connect to it with that instead and use RSLinx to configure the Ethernet port. You might also try another BOOTP program. I've used the one from Phoenix Contact. It seems to work better than Rockwell's: http://select.phoenixcontact.com/phoenix/dwl/dwl03c.jsp?from=eshop&lang=en&UID=2701094&param1=JrCDnVW3q4k%3D%2F0dDxMIlHrxc%3D&tstamp=1438567205534    
  14. Newby mistakes

    RSLogix 500 is still a current product marked as "Active Mature", which means "Product is fully supported, but a newer product or family exists. Gain value by migrating." List price for the standard edition of the software is about $2700 per seat. You will have to contact a local distributor to get your actual price. For comparison, the standard version of studio 5000 (for the latest series of their controllers) lists for about $3700 per seat.  RSLogix 5, which is also marked as "Active Mature" but is definitely on the way out lists for about $10,000 per seat. They do that to get people to migrate off of the old stuff, which I understand, but it's still REALLY annoying.  
  15. software information

    I know that standard (what we have) will not let you do anything with macros or VB.
  16. software information

    I found that too, but it doesn't show the difference between starter/standard/professional.
  17. software information

    RSLinx is included. Your local distributor should be able to give you a good description of the different levels of the software. The difference isn't license duration but what each package lets you do. I know that there's a place on their website that provides that comparison but I can never find it when I need it and bookmarks never seem to last for long.
  18. software information

    No worries. Missed the sarcasm font...  ;)
  19. software information

    Portal doesn't support anything Allen-Bradley. Unless something has changed, it also doesn't support all Siemens hardware (MicroMaster, Multi-panels, etc.).  Only the latest and "greatest".
  20. PLC 2 files?

    We have a bunch of PLC2s running, but we use a different software package from a 3rd party that won't import your files.  Hopefully someone will stumble into this who can help you out.
  21. You make good points about damaging spare parts. It's not my preference at all, but we don't have a good system in place for securely storing them elsewhere.  Every time we set up shelves with parts, the shop gets rearranged and unqualified people decide what to keep without qualified people even being aware that the sorting is underway.  Protests land on deaf ears as tens of thousands of dollars of parts vanish overnight.  If they're in the cabinets, at least they're out of sight/out of mind until needed.  The same is true for drawings that electricians will need.  It's hard enough to keep track of them in the cabinets; anywhere else is impossible. I wish our situation was different, but 6 years of trying to adjust the culture have been fruitless. I was actually kind of hoping that it was an NEC violation so I could at least push for doing something else, but I may not have that "ammo". 
  22. It's a common practice in our plant to store electrical spare parts in the bottom of control cabinet enclosures.  They're not in the way and don't interfere with troubleshooting the cabinet.  I've been told that this practice is a violation of NEC, but I can't find it anywhere in NEC or in NFPA 79.  Or on Mike Holt's site (I'm not a member there). Is this a code violation?  If so, what section?  
  23. Function Blocks and Data logging to CSV

    Basically, when you finish an FB, the declaration area at the top becomes the structure of a data block.  When you call the FB, you assign a DB to it.  If you're calling it from within another FB, you can create a variable in the declaration area of the calling FB that's the same type as the called FB, essentially embedding the DB inside another DB.  This is essential if you're going to be calling the FB more than a couple of times.  If you call it from FCs or if you don't want to muck with the declaration area of an FB in a working machine (which I TOTALLY understand), you'll need a separate DB for each call of the FB.   Example.  Let's say you create FB100 to do something.  In most of our machines, FBs are only used once so what they would do is create DB100 as an instance DB of FB100 and use them together.  It's definitely not necessary to match the FB and DB numbers, it's just a convention that the particular OEMs who built our machines use.  It gets more complicated with multiple calls to the same FB.  Let's say you want to call FB100 5 times from within FCs (or from other FBs without modifying their DBs).  You would create 5 DBs, each an instance DB of FB100.  You can number them anything you want, let's say DB75, DB109, DB115, DB209, and DB1056 (totally random numbers....).  Each time you called FB100, you would use a different instance DB. If you call FB100 from only within other FBs, you can create variables in the declaration areas of the calling FBs.  You would assign the variable's Data Type to match the symbolic name of the FB you want to call. Here's a screenshot showing an example in Simatic Manager.  Portal will look different, but the principle should be the same (we just ordered a license to upgrade Simatic Manager to Portal but it hasn't arrived yet so I can't see what the differences are yet): The window in the back is the blocks folder of Simatic Manager with FB11 selected.  Note that its Symbolic name is "PosStatus". The window on top is the block editor with FB10 opened and its interface (declaration area) opened to the STAT area.  The programmer has declared a number variables of Data Type "PosStatus".  In the ladder window (Network 12), you can see a function call to FB11 that's using one of the embedded data structures. If you right-click on the call instruction and open the called block, it takes you to FB11, even thought that's not at all clear from looking at the call instruction.  
  24. How to Select suitable FactoryTalk Licence

    I would also reach out to your local Rockwell Distributor for guidance.  They should be able to help you select the right package.
  25. What do you think of Lenze?

    Another thumbs-down from the US.  We have about 15 or so identical machines with EVS9325 drives that were built by our internal machine-builder group.  Their failure rate is WAY too high, in my opinion.  We've had 6 failures in the last year and a half or so.  To be fair, there may be an issue with the OEM's application of the drives.  We've been unable to get the Lenze software installed and working on any of our laptops, even though our machine builder group just says, "Install this program and it just works every time for us".  So, basically, we hand the repaired drives back to the builders to program for us so they can sit on the shelf waiting for the next failure.  Just last week, we had one fail before our spare was back to us so we had to buy a new one, which was VERY expensive. We've also had an inordinate number of failures of motor/gearbox assemblies where the holding brake fails (may also be an application error, but the builder insists that it's working properly). There is no way to repair just the brake; we have to send the whole motor/gearbox assembly back to them for repair, which is very expensive.  I don't have numbers on the brake failures since one of the mechanical guys handles those.