1 second pulser

Nigasai

Member
Join Date
Nov 2006
Location
Singapore
Posts
88
Hi,
What is the correct done preset Value for timers if I wanted to have a one second pulser in the following AB PLC:
- ControlLogix: 999 Preset value or 1000
- SLC : 99 Pre(.01) or 100
-PLC5 : 99 Pre(.01) or 100

so my done bit is the 1 second.. been using this quite often but have some confussion, specially when doing totallizer(SLC and PLC5)..

Cheers,
 
Last edited:
If you are talking about an accurate 1 second pulse, then you will have to include the overhead of the PLC (and thus reduce your preset) into your preset.

I did a timekeeping application for the Wentzville GM plant ages ago, and based on that PLC's load, I ended up with around a 970 millisecond preset.

The way that I did it was to call a STI (Selectable Timed Interrupt) when the timer timed out that added a one second count to the current time and reset the timer before jumping back to the main program.

It was accurate enough that all I really needed to correct the drift was the midnight pulse from the Simplex clock (rather than the hourly correction pulse).
 
Thanks rootboy, so every 970miliseconds you call for an STI and trigger 1 second bit before jumping back to the next scan... right?
 
Thanks rootboy, so every 970miliseconds you call for an STI and trigger 1 second bit before jumping back to the next scan... right?

Anytime! :)

For that program, I would add 1 to a register, compare it to 60, and if it was equal to 60, then add 1 to the "minutes" register and zero out the "seconds" register. And so on for hours, days, weeks, etc...

I'm pretty sure that I just used ADDs and Compares to avoid having any problems with resetting counters in a routine that was only going to be called for just one scan per second.

I came up with the ~ 970 milliseconds by way of observation. Basically I started it in the morning and waited until the next day to see how far I had gotten off (this was before the plant had wired up the input from the Simplex clock so I didn't have to worry about it getting corrected at midnight). But if I recall correctly, it was accurate to a second or so per day.

And all that this program did was to start the Paint shop in Wentzville so it had a very deterministic scantime.

So 970 probably won't work for you. And 970 justs sticks in my mind, and it probably isn't correct. But it was in the upper 900's anyways. Since I wrote this program in 1994, a few of the details might be a bit fuzzy. :)

But it's easy to figure out what it needs to be, just let it run for as long as you can stand it and then do the math (actual versus calculated e.g. PLC logic). But be advised that in any case you will have to correct it occasionally.

The Simplex system would give me an eight second "on" pulse on the hour, and a twelve second "on" pulse at midnight. It was a simple matter to create two timers that would look for an eight second and a twelve second pulse (the Simplex system had just one input).
 

Similar Topics

Hello all I have the opportunity to buy some second hand unused components, they are Siemens motor modules, a CPU, inputs and outputs. I have...
Replies
16
Views
2,145
Hello all. I have a 1769-L16 that I inserted a 1769-L35E into. I was expecting it to create module defined tags automatically in my controller...
Replies
10
Views
1,814
Hey guys, I'm not super familiar with Cnet, so I'd like some insight from people with more ControlNet experience than I. We have a controllogix...
Replies
4
Views
893
Hey All, i took a bit of a gamble today. I bought a second hand version of Studio5000, FTView Studio, FTView Studio ME. I have been using...
Replies
8
Views
2,245
I am controlling an EZMarquee display (EZMR-2L10C-E) by EZAutomation with a L82 AB PLC over ethernet. According to their installing/setup guide...
Replies
2
Views
2,050
Back
Top Bottom