Memory Requirement for Each Instruction, Counter, Instruction, Timer, etc.

Is there a list flying around that lists how much memory each instruction, counter, etc. takes up in the the Click's memory? This is very handy in several ways like looking to replace another PLC with a Click knowing the count for each instruction, or estimating a program size before going down the rabbit hole just to find out (the hard way) the needs of the program exceed the controller's capacity just to name a couple. I have seen this type of information listed with some other controllers so it does not hurt to ask.

 

Thank you in advance


kewakl and Sparkyinak like this.
  • ADC Community_02 (Automationdirect.com)

    The Click plc can have a program size of 8,000 steps. The amount of steps each instruction consumes is not documented. In addition, if you want to store program documentation (rung comments, nicknames, etc.) this would contribute to the overall project file size:

    imageAnother option is our P1000 Productivity CPU's that have a 50 MB memory:

    https://cdn.automationdirect.com/static/specs/P1-540.pdf

    Expand Post
    Selected as Best
  • ADC Community_02 (Automationdirect.com)

    The Click plc can have a program size of 8,000 steps. The amount of steps each instruction consumes is not documented. In addition, if you want to store program documentation (rung comments, nicknames, etc.) this would contribute to the overall project file size:

    imageAnother option is our P1000 Productivity CPU's that have a 50 MB memory:

    https://cdn.automationdirect.com/static/specs/P1-540.pdf

    Expand Post
    Selected as Best
  • Sparkyinak (Customer)

    Thanx. I did find this information but it didn't satisfy my "curiosity". So, as long as I limit the program to 8000 steps with no program documentation, there will be enough memory to cover the 8000 steps along with their interconnections?

     

    My apologies for such a question and I am not trying to be difficult. This is the first time I am working with the Click and AD product and I know I will have a lot of programming ahead of me. I am sure anyone taking on a big project, these would be (hopefully) a valid concern. I may not even put a dent into its capacity but imagine investing weeks into a program just to get 90% there and run out of memory or some other limiting capacity. I do not have the time to get the experience with the particular product that I will have by the time I am almost done with this project,

    Expand Post
    • Todd Dice (Customer)

      You can have an 8000 step project and have it fully documented (rung comments, instruction comments, etc.) Have hit that wall and know this. If your reasoning for going with the Click is the CPU on-board I/O, I'd go with a BRX: The BRX has more memory and its PLC scan is head and shoulders faster than the Click. The BRX programming via Do-more Designer is similar to Click with a more powerful instruction set.

  • Matt Pawlak (Customer)

    When I bumped up against the 8000 step limit, I made these notes. I cannot guarantee they are correct.

     

    • Contacts, OUT, and SET, are one step each.
    • Compares are two steps each.
    • Timers and counters are 3 steps.

    Note: rungs do not require any inputs, but if there are no inputs on a rung a step is still consumed by an implied "Always On" contact. 

    Expand Post
    • Todd Dice (Customer)

      Just did a check. A single math instruction, where the equation is: (DF100 * 0.95) + (DF1 * 0.05) result DF100, triggered by a one-shot rising uses 10 steps.

  • Sparkyinak (Customer)

    Thanx all for your input. Unfortunately, I will just have to play it by ear and see where it goes. I was finally able to figure out a workaround to a problem with its C-More Micro HMI so I should not have to have to write such a large program after all