semilogical

MrPLC Member
  • Content count

    103
  • Joined

  • Last visited

Community Reputation

0 Neutral

About semilogical

  • Rank
    Sparky

Profile Information

  • Gender Male
  • Country United States
  1. RSLogix 5000 Source Protection

    Hello, I'm a former member when with another company.  My new company has a load of programs with source protection.  To date I have not found a listing of the contractors that set-up the programs.  I cannot open the files to trouble shoot them, I'm kind of lost. If I follow what I read online and here indicates to me that I'm out of luck. Is there any way to recover programming that  has been locked?  I have found one sk.dat file, but it does nothing.  In the dialog box I'm told that no file can be found and I see the file and it's contents.  Not real exotic, nor cryptic. Help in any manner would be appreciated.
  2. Not exactly, I think I was aware of the digit difference/or non difference. The customer's EPC seems to think I can transfer my Control Logix I/O to Modbus addressing that is designated for direct inputs, i.e. if I wire ZSC-123 to Input 1 in a Modbus platform (PLC) the address is 10001 or 100001. They expect me to transfer Local:1:I.Data.0 to 100001 for their use in the DCS Control equipment. I've never heard of that even being an option. When you use the ProSoft Technologies MNET module you get to transfer the data via preset blocks that are received in the Master starting at 40001 or 400001 (as the case may be). I was just looking for someone that has experience with any alternative addressing that can be sent from the Control Logix via ProSoft.
  3. I have been using the MNET modules for a few years and have been successful in sending information to various Distributed Control Systems. I have a current set of projects, one being managed by EPC/Fluor and the second EPC/JGC. Both have the very same set of specifications from the end user. The first is a large system and I will use about 600 Modbus addresses in the data transfer, the EPC/Fluor group has no issues with the format: MNET_15.Data.WriteData[0] - [599], we actually have a dual setup for redundancy so the second set of info is the same only using MNET_16 as the slot designator. The second EPC/JGC expects the Control Logix to send I/O data to the 000001-099999 for Outputs and 100001-199999 for Inputs and 300001-3xxxxx for the analogs. My experience tells me the data addresses they are using would be from a PLC with a database created around a Modbus format. In the time I've been transferring information with the Control Logix I have seen no other manner of transfer using the ProSoft Technology modules. Is there anyone out there that has used a different manner of transfer format? I'm about to send a message to the EPC/JGC regarding their shortsighted desire for the transfer, I just want to be sure that I'm not being the one shortsighted.
  4. My first response should be that I mistyped the standard, it's ISA-F3A.I may have misunderstood the initial post. I'm talking about determining what alarm shut down the process. I get the feeling that you are working with a process that has to be systematically shut down, thus the need for a fault routine to safely back down a process. In my world when there is an alarm/fault we trip the whole system back to an immediate failsafe position. We don't need to sequence the stop. Regarding ISA-(F)3A, it's a standard written by the Instrument Society of America. There are acutally quite a few different annunciators mapped out in their "Annunciator Sequences and Specifications standard ISA-S18.1 (1979). I have not been able to find a newer book with the Standards and Practices for Instrumentation, the one I have is the sixth edition printed in 1980. I'm sure there are more recent copies, but the basics most likely have not changed. My biggest task is converting the ladder into a function block that can be used when the customers request all function block programming. I have not been able to find a pre-engineered add-on for control logix in cyber space. Anyone else ever have a need for one of these?
  5. I've not used the Safety PLC's much, can yu program in Ladder in GuardLogix? If so can you indirectly address bits and words? I use an ISA-3A First Out Tracker that is very useful for tracking the event that stops the process. If you can indirectly address I'd be happy to share the program files with you. I've used it in Control Logix as well as SLC-500's.
  6. 1756-RM

    The primary and secondary chassis should be identical based on the Safety Reference Manual - Using Control Logix in SIL2 Applications. Publication 1756-RM001F-EN-P - June 2009. My point of reference is Chapter 1 page 20. I have two on tap to program, I have been advised this is the way to go if you are SIL2 rated or not. I'm no expert, but you get what I've experienced so far! I do believe the RM module does all of the configuration for the secondary CLX. good luck
  7. I have developed a first out annunciator based on the ISA 3A model, it works fine in ladder but the manner in which I wrote it tends to confuse some of my fellow programmers. I use indirect addressing so the basic 8 rungs of programming does not have to be repeated, rather re-referenced as the indirect index is incrimented. My goal is to have a first out annunciator for the control logix platforms, we are moving more towards them as they are SIL 2 rated. In using the CLX we are also trying to move to function block as our main code. Before I go all hog wild writing the program in function block I was wondering if anyone knows of existing add-ons that are available for exchange? I consider re-engineering the wheel to be a great waste of time. Our programs are typically repeatable with the exception of the number of system shutdowns that have to be alarmed in a first out manner. All but the first out annunciator is being transformed from ladder to Function Block, our style is easy and quick with the excepton of the dreded First Out Annunciation. Any help, pointers or pre-developed add-ons that are not copyrighted would be greatly appreciated.
  8. The Comms for Enterprise is configured and only holds the Ethernet for program transfer. I also blew out all comms and tried loading with the compact flash. Still no luck.
  9. The PVP is a Modbus Slave. I reloaded all software and firmware. KepServer = V4.500.462 Firmware = V5.10.01.09 (CPR 9 SP2) FT View Studio ME = V5.10.00 (CPR 9 SP2) I do get an unexpected diagnostic when I start the PVP. Opening project \Storage Card\KEPServerEnterprise\default.pfe The comms name in the KEPServer is Channel1.TEG.Integer I only have one tag loaded for testing. Following the opening project que I get [Factory Talk]: The item is no loner available: Channel1.TEG.Integer. I've gone back and forth with the softwares and firmware. Nothing seems to work.
  10. I am working with a panel view plus for a project. I have to ship this unit pre-setup for Modbus communications via the serial port. I have been using KepServer v4.5, FT Studio ME V5.10 and Firmware Release 5.10.01. According to all I know (which isn't much) I have configured the system correctly. HOWEVER; the PVP will not communicate with the KepServer and Modscan32. I have a spare SLC-504 I can use as a Modbus Master, but I've never setup the Channel for anything but normal comms. There is a place in the help that says Create Modbus data table, but I can't find anywhere in the software that points me in that direction. In the ML1100 you have some choices that are very apparent. Any help form anyone would be greatly appreciated.
  11. I've created a BMS program in ladder logic, so far it's pretty solid in it's operation. I need to create add-on function blocks to make programming easier for my counterparts at work. I do most of the programming but on occasion one of the other guys needs to do the same type of program. I figure that I can create a few add-on's that will take away some of the more advanced aspects of my program. Not that my program is out there, but some of the other guys do not understand indirect addressing and some of the other techniques I use well enough to follow my lead when developing a program. When they do a system checkout on my programs they all comment on how easy it is to follow. With FB they won't be needing to understand the inner workings of the Add-on's, just how to populate the pins. Any pointers to literature or a library of add-ons that are already out there and available would be helpful. IT'S FRIDAY - Ya all have a great weekend.
  12. Ethernet Addressing Question

    Bob, I was going to tell you that I tried using x.y.z.0 and it didn't work. Typically I set up any ethernet TCP/IP's using the industrial standard 192.168.x.x. When I deliver the project to the customer we adjust the IP's to fit with their plant standard. It's typically as varied as the number of hairs on your head at any given moment. Our old company architechture(probably spelled wrong) was 10.10.x.y. When we were bought out the new corporation added us in to thier structure. They have over 100,000 users on their intranet. Now we are up in the 1xx.1xx.100.xxx range. The good news is that we were able to get connected directly to our PLC's on the plant floor some 35 miles from the office. Saves driving time like you wouldn't believe. Is there someone here that can define the subnet to me? I normally get a default of 255.255.255.0 for my projects. Lately I've seen some different iterations of the number, i.e. 255.255.248.0 or 255.255.0.0 It doesn't make sense to me and I've not been real successful in finding anyone willing to give me an answer. Have fun all, TCP/IP is either the greatest thing in the world or it's a monsterous trap to drive us all crazy!
  13. Wonderware 9.0 Alarm page

    I am working with Intouch 9.0 Wonderware. I have an alarm banner across the top of the page, I can acknowledge all alarms but when I try to acknowledge the selected alarm I fail. I'm sure I'm missing the syntax for the alarm. I looked for a selection that would read the alarm selected and insert it into the equation / expression (or whatever the proper name is) but have not been able to achieve my goal. Any help would be greatly appreciated.
  14. PLC-5 Retrofit

    I'm currently still not having any luck getting the communications to work with my laptop, the desktop computers I had the "pre-checkout" software running on was working great before we shipped it to the customer. I will be shipping the PLC components back this week and will wait to reinstall the RSView32 program into those computers so I can reverify the RSLinx settings I had, the topic setup and the IP addressing for the rest of the system. When you have all of the equipment in one place it's easier to get things moving in a direction needed, all of the interactions are in place. Tha plus I'll have a couple of guys with me that are very familiar with the communications situations. Worst case we have 24/7 support from Rockwell so I can call/chat my way to success when the time comes. I will update this thread after I get the solutions wired in my head and in the equipment.
  15. I'm working on a retrofit system for a project from 1993. The programming is somewhat a mess and I've got to resurect the system in August. It's been sometime since I used a PLC-5 so my questions might seem as if they come from an inexperienced user. The topics of question is communication to an RSView32 on two table top units as well as some 1771-IXE questions. #1 - The last time I used RSView32 I went directly to a SLC-5/05 and didnt have any problems. Now it seems like I can't get the communication configured to talk. Right now I'm testing on my laptop connected live to a PLC-5/30B Revision U with an ethernet sidecar. I can program over the ethernet as well as the Serial port on my laptop. I cannot; however, get the RSView32 to talk to the PLC. I've tried several things. I even called tech support and the guy worked me through the way he felt it needed to be done and I'm still with a dead link. When I started working on the project I setup the IP addresses in the PLC and the two desktops. I did not have to create an OPC topic name as I was using a direct hookup to the PLC. I set up the IP's and it just worked. The desktop computers are now at the jobsite, the processor is on my desk sans the Remote I/O chassis's. I have 4 1771-IXE thermocouple modules in the system. Mostly type J thermocouples. I haven't used Block Transfers for almost 12 years now so the concept is a little foreign to me. If the data coming in is raw at 0-4095 I can handle the data, but if it is scaled to the standard ranges for the thermocouples I have a problem. The original programmer looked as if he used all raw data. My customer claimed they had to run the system in manual from day one. After reviewing the program I'm seeing why. Any pointers of how to get the communication and IXE configuratons out of the basement of my mind would be greatly appreciated.