Joe E.

MrPLC Member
  • Content count

    883
  • Joined

  • Last visited

Community Reputation

89 Excellent

2 Followers

About Joe E.

  • Rank
    Guru

Contact Methods

  • Website URL http://

Profile Information

  • Gender Male
  • Location Blacksburg, VA
  • Country United States

Recent Profile Visitors

5469 profile views
  1. Reset in ControlLogix Processor

    If you get online (you really should be able to while it's faulted), there may be more information there.
  2. Reset in ControlLogix Processor

    In the programming manual, it doesn't say much: "For a controller with no memory card installed, the controller: Detected a non-recoverable fault Cleared the project from memory" The recovery method: 1) Clear the fault. 2) Download the project 3) Change to Remote Run or Run mode. If the fault persists: 1) Before cycling power to the controller, record the state of the OK and RS232 status indicators <-This is interesting since the -L72 doesn't have an RS232 port... 2) Contact Rockwell Automation support You should still be able to get online with it. How do you normally connect to the PLC?
  3. NFPA79 chapter 5 talks about the incoming power connection and disconnecting means. Section 5.3 covers the disconnecting means. I'm not 100% sure what you mean, but I don't see many exceptions to the requirement to provide a supply circuit disconnecting means within the enclosure except for panels that are smaller than 2HP and they need one close by and clearly identified. I didn't read the whole section, though.
  4. Anybus x Gateway assembly instances

    I googled "1794-aent generic module" and found this: https://www.hilscher.com/fileadmin/cms_upload/ko/Resources/pdf/EtherNetIP_Generic_Adapter_DTM_OI_08_EN.pdf It appears to have some of the parameters you're looking for, but they may not be useful to you. Realize that the configuration you're trying to do will be very dependent on which modules are attached to the -AENT and this may not work at all. Are you trying to control a Flex I/O chassis with a PLC that doesn't support it? If so, it may be a better investment of time/effort to use different I/O that the PLC supports or change to a PLC that supports that I/O chassis.
  5. generate pdf file

    That file is password protected. You need to provide the password so someone can open it to print it out. Be aware that breaking/bypassing passwords, and discussion of it, is not allowed on this forum.
  6. Oleg

    That file is password protected. You need to provide the password so someone can open it to print it out. Be aware that breaking/bypassing passwords, and discussion of it, is not allowed on this forum.
  7. Overlapping memory areas in TIA Portal

    Hmmm.... I searched the project and it turned up where the words are used. It would be really nice if the search results had a column showing whether it was used as a read or as a write. As it is, you have to open each result and look at it.
  8. I have a fair amount of experience with Simatic Manager, but I'm new to TIA Portal. This one has me stymied after a couple hours of hunting (this time). This is an issue we've encountered before with various machines programmed in Portal, but didn't have a chance to chase it down. Here's a simple and clear example. This machine is from France and was programmed with Portal v14. The alarm bits are all contained in a global data block DB2. The alarm bits are individually SET in FC2 when conditions are right for each alarm. Each bit has its own -(S)- coil, which (as far as we can tell) is the only place it's written...EXCEPT...the first network in FC2 uses MOVE instructions to write "0" to DB2.DBD0 and DB2.DBD4 any time a "reset" pushbutton is pushed (there are 2). The problem we have is that all of the ways we've tried accessing the cross-reference for the program only show the individual bits (DBX), not the double words (DBD). If the MOVE instructions had been placed in another FB/FC/OB somewhere, we would have had a major devil of a time finding them. They just happened to be at the top of the alarm FC. Here's a screenshot of the MOVE instructions with the x-ref information shown for DB2: In the Simatic Manager world, the Cross Reference will show where the different registers are used, whether as DBX, DBB, DBW, or DBD, but it seems to me that the Cross Reference in Portal only shows actual symbols, not addresses. Since there is no symbol defined for the DBD addresses (and I don't there CAN be, since they're defined as DBX bit addresses), they don't show in the x-ref. I opened the Cross-Reference window (which is different from the bottom-half cross-reference information tab above) and clicked on "Show overlapping access" on its toolbar, which opened another sub-window...which is blank and doesn't show the overlapping access to the DBD word (maybe because the MOVE instructions used absolute addresses instead of non-existent symbols?): I came across a blog post about issues in TIA portal v13. One of the entries mentions a global address overview, which is tantalizingly close to the "show usage" tab of the old Simatic Manager x-ref but I can't find any way to get to it. This probably wouldn't help us track down a DBx.DBDy overlap, but would be useful for finding unused "M" memory: Another "interesting" piece of information is how the HMI alarms are configured. They use trigger tags that are word-level, not double-level. In other words, alarm #1's trigger address is DB2.DBX1.0, which is part of Trigger tag Alarme_mot_0, which points to DB2.DBW0. The tag databases and x-refs for the PLC and HMI appear to be distinct and separate entities, contrary to the marketing presentation we attended for Portal which said that everything was in one place and easy to find. That's definitely not our experience so far. I found an article on Siemens' website about prepending "AT" to the beginning of a tag name to have overlapping tags but that only applies to the declaration areas of FBs and FCs. This is a global DB. And I'm not sure it would even work anyway, though I suspect it would IF the MOVE instructions used the tag names instead of the addresses. Can anyone help me figure out a way to x-ref the DBD usage and to find the global address overview?    
  9. Counter Malfunction

    Is the counter tag used in another place?
  10. Ultra 3000 Drive Follower not indexing

    I don't suppose you have a backup parameter file from before Maintenance Bob got to it? Or another identical machine to compare?
  11. You're welcome. I learned those tips the hard way. One of my first tasks here (over 8 years ago) was converting an old PanelView 1400 (a CRT HMI that was a predecessor to the Panelview Standard) to a PanelView Plus. It connected to a PLC-5 over DH+. It took me a while to figure it all out using just the manual we had for RSView 32 version 4 (which became FT View Studio at version 5, I think). Unfortunately, the glitches and gotchas I had to work around back then are still there at v8.2.
  12. Here's another tip. If you copy/paste a bunch of objects from one HMI project to another, and if the device shortcuts are named differently, you will have trouble. Also, if you change the name of the device shortcut in the communications setup, it will NOT change the name in your display objects! To remedy that, you can select all of the objects on a display screen by pushing ^A, then open the tag substitution dialog by pushing ^R. You can search for any text and replace it with any text: In this dialog, I can enter Ink_Detect in the "Search for:" field and enter Ink_Detect_D in the "Replace with:" field if I change my device shortcut name to Ink_Detect_D. This is also a handy dialog to use to see the tags and expressions that are used on that display. You can just scroll through the list looking for misspellings etc. There are other gotchas I learned the hard way. You can be doing everything perfectly correctly and it still won't work, until you reboot your PC. Then it "magically" starts working. If everything looks right, like, "...it should work, darn it!!!", try rebooting the PC. Especially, especially, especially if you're making changes to the device shortcut or communications settings. I've had countless annoyances working with these HMIs when I made a change to the communications and had to jump through otherwise pointless hoops to get it working again. I've even seen where I could run the project in test mode and it's fine but when I compile & download the runtime to the HMI, it doesn't work. Until I reboot the PC and re-compile the runtime file. Then it works, without changing anything else. As an example, I decided to test what I just outlined above by changing the device shortcut name to verify that it didn't change it in the object properties. Then I changed it right back and nothing would communicate in test mode. I shut down/restarted View Studio, same result: no comms to the PLC. Then I rebooted the virtual machine, opened View Studio, and tested it and it worked perfectly. If in doubt, and you think you have it right, first close and re-open View Studio. If that doesn't fix it, reboot your PC.
  13. Here are some screenshots of what I'm working on now: First, here's the Communications Setup dialog box: The device shortcut here is "Ink_Detect" and it points to the MicroLogix 1400 at 192.168.0.16 Next is the Connections tab of the properties of a multistate indicator that's tied to the address N7:70: Note the syntax with the colons and square/curly braces. Your device shortcut name is embedded in there. If you click the "..." button under "Tag", you'll get the tag browser: The project name is Ink_Detect_D, which is the top level of the browser window. Ink_Detect is the name of the device shortcut. This is not final and I'll end up changing the names once it's closer to being done and I know exactly which line it'll end up on. If your shortcut is configured correctly, and the PLC is ping-able at the IP address in the design (Local) tab of the shortcut, clicking "Refresh All Folders" will populate these folders. The address I need for the multistate indicator is inside the N7 file, expanded above. If you use the "..." button to open the tag browser, you can just double-click on the address you want and it will automatically add the punctuation and syntax it needs.
  14. Awesome, that's good to hear. We're all at v8.2 (2 laptops for the maintenance folks and 4 for engineers). Our firmware versions range from 5.x to 9.
  15. Cool. We have so much on our plates, we haven't been able to investigate that at all. Right now, we're avoiding anything that would make it more complicated to keep the machines running and make the upgrades we're being asked to make.