I've finally gotten around to programming an AD Click PLC that's been sitting in my office for close to two years. The main reason I'm using it is that the ML1100 I was planning on using for this project won't fit in the available space.
Converting rungs with inputs, outputs and internal bits has been a breeze, but I'm hung up on what the equivalent bits for timers status (.EN, .TT, .DN, etc.) are. I've gotten around TT by using a Greater-Than contact that I use to compare TD1's current value to "zero". If the contact is true and the conditions that started TD1 are true, the timer must be running.
For an equivalent to DN, I compare current value to SetPoint.
I'm sure the above work-arounds will work fine, but I'm guessing there's a much more elegant way to make it work.
BTW, the .RSS program I'm converting only has a dozen rungs and is for a floor scrubber. My intention is to broaden my experience by converting this on my own, but a little push in the right direction would go a long way!
Converting rungs with inputs, outputs and internal bits has been a breeze, but I'm hung up on what the equivalent bits for timers status (.EN, .TT, .DN, etc.) are. I've gotten around TT by using a Greater-Than contact that I use to compare TD1's current value to "zero". If the contact is true and the conditions that started TD1 are true, the timer must be running.
For an equivalent to DN, I compare current value to SetPoint.
I'm sure the above work-arounds will work fine, but I'm guessing there's a much more elegant way to make it work.
BTW, the .RSS program I'm converting only has a dozen rungs and is for a floor scrubber. My intention is to broaden my experience by converting this on my own, but a little push in the right direction would go a long way!