Posted 27 Jun 2019 I have heard "Don't use SET or duplicate coils". I kind of agree, so how do you handle it? Do you use logic to control coil A1 and other logic to control coil A2. Then coil A is controlled by either A1 or A2. Do you use logic to SET or RST A and other logic to SET or RST A. Please realize the logic is not as simple as stated above. not simply condition 1 or condition 2 then out A. 1 person likes this Share this post Link to post Share on other sites
Posted 27 Jun 2019 @Russ McKenna Yes, You should not use duplicate coils for my program I have to use memory bit to buffer data for input/output example I need to use X0 to On Y0 normal program are -|X0|--------(Y0) If you need to create other program to control Y0 you need to parallel sequence before Y0 such as -|X0|-------(Y0) -X1|---| Then I have use Memory bit to solve this -|X0|--------(M10) -|M0|---| -|X1|--------(M11) -|M1|---| -|M0|--------(Y0) -|M1|---| That you can use any condition to control Y0 by use output at M data then parallel at output sequence and you can use M0 M1 for HMI control too. 1 person likes this Share this post Link to post Share on other sites
Posted 27 Jun 2019 it is not JUST "coils".... "do not duplicate" mantra applies to ANY instruction that modifies state of an output. the more instructions write to an output, the harder is to troubleshoot. two is the minimum number of instructions that would cause duplication. and that is already considered too much and frawned upon. some products have built in check for duplicates and in some cases will force you to prevent use of dupplicates. typically this would only look for bit-level instructions and word level instructions for exaample would still get free pass... 1 person likes this Share this post Link to post Share on other sites