MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

69 Excellent


About ElectronGuru

  • Rank

Profile Information

  • Gender
  • Location Missouri
  • Country United States
  • Interests ones and zeros.

Recent Profile Visitors

3609 profile views
  1. Anyone have experience with the 1756-5580 controllers? I'm specifically curious about the role-based access control that Rockwell is boasting about. The following bullet point is from the associated link: Includes controller-based change detection and logging, digitally-signed controller firmware, and role-based access control for extra security https://www.rockwellautomation.com/en-us/products/hardware/allen-bradley/programmable-controllers/large-controllers/controllogix/1756controllogix5580.html The L7 controllers also have controller-based change detection and logging. It's just been expanded in the L8 from logging 100 to 500 events in the controller's memory. But they're making it sound like it's a brand new thing. The above bullet point also makes it sound as though the role-based access control feature is embedded in the controller, and therefore would not be dependent upon the FactroyTalk Admin Directory. Is this true and if so, how do you use this feature? Would you apply the FactoryTalk security when creating the project and it just remembers the permissions? Or is this advertising blurb a bit misleading, like making the change detection and logging sound like a whole new thing? Anyone?
  2. Emulate 5069-L310ERS2

    @BobLfoot that's spot-on; you must download the individual version(s). Currently you can get RSLogix Emulate 5000 in versions 20.4, 21.3, and 24.1. Studio 5000 Logix Emulate is available in versions 24.1, 28, 30, 31, 32, 33, 34, and 35.  You should be able to look those up, compare, and download from here:  https://compatibility.rockwellautomation.com/Pages/MultiProductSelector.aspx?crumb=111
  3. Open .RSP file

    @mhi are you needing to go online with a PLC-5, or just open the file and read the code? If you truly need to get online with a working PLC-5 processor, you'll want to check through RSLinx to see what the controller is flashed to, as only versions 8, 9, and 10 (out of 10) are still available. In the Search box, type "RSLogix 5" and get the exact version to match your processor(s) here: https://compatibility.rockwellautomation.com/Pages/MultiProductSelector.aspx?crumb=111 If you only need to open the file to read the code, post the .rsp file here and someone who has RS5 will be able to open it, print as a .pdf and re-post for you. 
  4. Most of the components of a .med are individually exportable and saved with their own file extensions. A couple of examples would be; displays are .gfx, global object displays are .ggfx, recipes are .rcp, etc. I think maybe one of the SQL's jobs is just keeping the whole thing grouped together in one database, hence the Tech Note stating you'd have to import the components and create a whole new application. When editing HMI code in a .med the save button is always greyed out until you make a change on whatever component (such as a display) you have open and has focus. As you know, an L5K is an exported project and we accomplish that export by doing a "Save As", which doesn't exist in FTME or FTSE. We can only save individual components as we edit them, and import/export them using the import/export tool.  Just for grins, I just tried to open a .med in Notepad and it looked like a lot of gibberish, with more than half the character being symbols I've never seen anywhere.  All that to say, unless someone pulls a rabbit out of a hat, I don't know any way to make a deliberate and meaningful change to a .med with a text editor. But I sure would be willing to learn about it if it exists.
  5. We've known forever that once a .med is opened in a newer version of Studio than the one it was created in, it's now locked to that version or higher. But yes, in versions 9 through 12 we were able to restore a .mer or .apa to a .med and edit it, regardless of which version of FTView Studio created the original file. To make sure I'm not remembering this wrong, this morning I created a .mer on a laptop with FTView Studio V12 and downloaded it to a PanelView Plus 7 Pro with FW 8.2. I then uploaded that .mer to a different laptop with FTView Studio V10 and successfully restored it to a .med. I only got the usual warning that I'm converting an V8.2 .mer to a V10 .med, and that I won't be able to go backwards with that specific .med.  I haven't downloaded FTView Studio V13 yet but I'm willing to take you at your word, @BobLfoot, that once V13 gets hold of a project file, that file is locked to V13. I'm wondering what surprises await us in V14, scheduled for release sometime early next year.  
  6. @BobLfoot got it, thanks. @pturmel my experience is that you can't have more than one version of FactoryTalk installed at a time. I screwed myself a couple of years a while back by updating to V12 when the rest of the outfit was using V10. That created some work-related issues that are neither here nor there for this thread but suffice to say, there is no "go back" button. I had to completely un-install FTView Studio and do a clean install to get back to V10. If you or anyone knows a way to have more than one version of FTME or SE on a single machine (without using a VM) I'd love to know about it. 
  7. Maybe I'm not reading this right but I'm confused. The project was built in V12, modified by an integrator in V12, and then you wanted to add another display in V12. When did V13 come into play?
  8. Can not open projects in FactoryTalk

    Something else just occurred to me; In your laptop's search box type the words "FactoryTalk  Directory Configuration Wizard" and open it. You might try checking both the local and network boxes and going through the setup process again (it's short and painless) before running the resdir utility.  Hope this helps.
  9. Read IO Config

    Unfortunately, Rockwell removed the Read IO feature when they went from 500 to 5000. There are several module status values that can be obtained with a GSV instruction, but the retrieving model/catalog number is not on the list.  The best way to see what's in any given slot is RSLinx when offline. When online, of course, you just look a the properties dialog box. 
  10. Can not open projects in FactoryTalk

    Though this article doesn't reference your specific issue, I've found that the resdir tool linked at the end solves a lot of FT directory issues.  https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/577717
  11. RSLinx Classic Lite

    @Ron_Smith I'm currently having an issue where from within the Studio 5000 Task Monitor the RSLinx Ehternet driver sees the nodes but won't let me connect to them. The Knowledgebase solution was to upgrade to 4.3, so I'll be trying that in the coming week. RSLinx seems to have some quirks here lately.
  12. RSLinx Classic Lite

    I've seen this before but more often with the yellow question marks. If you have a backup of the driver, restore it. Otherwise, note the driver settings, delete and re-create the driver offline and next time you plug in everything should be normal. Then use the RSLinx Classic Backup Restore Utility to create a backup for the next time something like this happens.  Would be nice if someone else could jump in with a magic one-click solution, besides don't plug into the wrong network, lol.
  13. Produced-Consumed tags exchange

    There is a hurdle between RS5000 (V20 and below) and Studio5000 (V21 and above). All L6 controllers hard stopped at V20, but there are a handful of L7s that will go down to V19. Your workaround of "lying" to one controller and telling it that it's consuming a tag from an L6 instead of the actual L7 is pretty clever. I think that most or all data on the backplane is multi-cast, not unicast. I tend to switch everything in the local chassis to multi-cast, as I believe most of the default card settings are unicast.
  14. Produced-Consumed tags exchange

    IT and controls people are the bane of each other's existence, lol.  My experience has been that when the generations of PLC get too far apart, it's better just to use the message instruction. This can be frustrating when all you need is something as simple as line speed to get from one controller to another, but it's reliable.
  15. Produced-Consumed tags exchange

    Whether you in the same chassis is not as important as being on the same network. The Design Considerations manual says; "You cannot bridge produced and consumed tags over different networks. For two controllers to share produced or consumed tags, both controllers must be attached to the same network. You can produce and consume tags over ControlNet or EtherNet/IP networks". It stops short of saying whether you can share data this way across different subnets, which is the situation you're in and is something I've never tried. Like @Joe E., I'd be surprised if it didn't work but if if doesn't, you'll have to use a MESSAGE instruction.