gromit

MrPLC Member
  • Content count

    231
  • Joined

  • Last visited

Community Reputation

3 Neutral

About gromit

  • Rank
    Sparky

Profile Information

  • Country United States

Recent Profile Visitors

2851 profile views
  1. SLC5/05 in unmatched chassis

    I added the s:5/4 unlatch instruction at the bottom of Ladder 2 and then disabled the referenced JMP and returned the S:5/8 & S:1/10 memory module bits back to 1, then transferred from RUN to PROGRAM to RUN, which created the following fault. "The required memory module is absent or S:1/10 or S:1/11 is not set as required by the program." So, I put the S:5/8 & S:1/10 memory module bits back to 0, cleared the fault, then transferred to RUN with no faults.
  2. SLC5/05 in unmatched chassis

    Ken, thanks for your reply...I was able to prevent the major error by doing the following: removed 2nd 10-slot chassis & disabled s11-12 & s27-28 to ignore modules in rack to prevent processor from faulting...also added n110:0-3 through n117:0-3 to replace I:10-14.0-3 and O:15-17.0-3 to prevent processor fault. Also added JMP & LBL to bypass lad3 & 4...which are input and output routines. Lastly, set S:5/8 & S:1/10 memory module bits from 1 to 0. I will load a prior version and then add the s:5/4 unlatch to see if that works.
  3. SLC5/05 in unmatched chassis

    The initial fault was cleared by setting s:11&12, s:27&18, and s:25&26 to all 0s. I then changed the rack size from 13 slots to 10 slots, and then replace many input and output assignments to integer files; which cleared the program errors. Unfortunately, I am still getting the following error..."A minor error bit is set at the end of the scan.  refer to S:5 minor error bits." as depicted in the attached pic. Do you have any other ideas on how to clear the fault?
  4. SLC5/05 in unmatched chassis

    Thanks Mickey, I will try this today.
  5. SLC5/05 in unmatched chassis

    Thanks for your reply. . . However, I don't see the "ignore configuration error" checkbox. See the attached pic for reference.
  6. I have a spare SLC5/05 chassis with I/O. I want to load a different SLC5/05 program into this processor, but the I/O configuration doesn't match the actual modules. So, how can I run the program without it faulting, so that I could test some of the subroutines? Thanks.
  7. Is version 12.038 CompactLogix L35E (ser A)  firmware compatible with 1769-L35E COMPACTLOGIX 5335E CONTROLLER. CONTROLLER VERSION = 12.22 ? If not, where can I get the appropriate firmware? Thanks.  
  8. ControlLogix Controller & Program tags

    Thanks Armadillo852 and jncontrols. Sounds like a plan...I will move (cut & paste) the tags to the controller tags area and download the program, while in PROGRAM mode. All efforts complete without incident. Thanks for the assist..
  9. ControlLogix Controller & Program tags

    Thanks, jncontrols. I understand your recommendation and its intent; however, I was hoping for a more efficient solution. So, if the tags can't be cut from the program tags area and then pasted in the controller tags area while in RUN mode, could the tags be copied from the program tags area, then pasted in the controller tags area, and finally deleted from the program tags area while in RUN mode? Thanks for your feedback.
  10. Can ControlLogix Program tags be moved to Controller tags area while in run mode, via cut & paste or some other means? Also, is it true that only tags in the controller tags area can be accessed via CiTect HMI and other HMIs? Thanks.
  11. SLC5/05 1747-L553 intermittent loss of communication Has anyone ever experience an intermittent loss of communication between the SLC5/05 1747-L553 PLC and a computer which can only be recovered by cycling power on the PLC? We are experiencing a communication loss sometimes once a week, sometimes more...and it is occurring on three different PLCs. A PLC specialist or contractor claims that the loss of communication can be caused by the PLC firmware. The specs from the PLC are as follows: PLC model: SLC5/05 1747-L553   CAT: 1747-L553 SER C PROC REV 5   OS# 1747-OS501 SER C FRN 9   Has anyone experienced this type of loss, and if so what would be the best course of action to take? Is there a sniffer that can be employed to determine if the comms loss is caused by the PLC, by the computer, or by something else. Please advise. Thanks!
  12. Can the following functions be achieved in the SLC5/05 processor? 1.Mean Value over time      a.determines the mean value of the input value X with a moving time window T. 2.Differentiator     a.used to generate a time derivation of an analog input 3.Running Average 4.Rate of Change monitor
  13. Can the following functions be achieved in the SLC5/05 processor? 1.Mean Value over time      a.determines the mean value of the input value X with a moving time window T. 2.Differentiator     a.used to generate a time derivation of an analog input 3.Running Average 4.Rate of Change monitor
  14. When communicating between SLC5/05 and a third party, we are receiving sporadic timeout alarms...by sporadic, I mean it could be hours to days apart. The program scan time is very short…only 20 msec maximum & 10 msec average. Do you have any suggestions for resolving this issue? Also, is there a way to determine communication rate or communication scan time? Thanks!
  15. SLC5/04 DF1 port

    Unable to communicate to SLC5/04 DF1 port using null modem cable, even after resetting processor to factory defaults by shorting the VBB & GND pins or by shorting the capacitor. I can connect to the processor and download a program via the 1784-U2DHP adapter, but still can't connect to the DF1 port. To prove my cable and USB to serial works, I move it to another SLC PLC and it communicates properly. I spoke with Rockwell support at length and they say that the port is bad and there is nothing else that can be done. Does anyone know of any other steps that I could take to get the DF1 port to work? Thanks.