Designing a system for controlling the lights at a private airfield

Looking at post #28, with standard timing relays you can't do, stuff like 3-5 seconds before something ends. Timing needs to be from the beginning.

You also have 1 second resolution. Knob turning isn't going to work.

The timing diagram all has to be relative to the initiate, so tweaking a single variable in that diagram means tweaking multiple values.

So, you need a new timing diagram with times from the initiate.

With some sort of "smart relay" the "directly adjustable" times in that diagram can be entered and then the times from t=0 can be computed.

You did mention surges or in-rush which I think means multiple lights, so maybe that block can be fixed.

So, you need times from t=0 for starters.

You wont find a timer that say turns off 1-10 seconds before 15 minutes (900 s) is up. It would be a timer where that timer turns off at
899, 898....890 seconds after initiate.

So, you could have a spreadsheet that inputs the values desired and outputs the values to set the timing relays for mostly based on T=0.
 

Thread Starter

Rabbit H

Joined Aug 5, 2016
153
KISS,

Addressing your points...

"Timing needs to be from the beginning."

There is no reason why everything can't be referenced from T0:00 (the closing of L-854(R3) with one exception: the opening of L-854(R3) at T15:00 (the end of R3's 15 minute enable gate) is readily available for ending the obstacle light activation period.

"(the avoidance of) surges or in-rush (of) multiple lights..."

That's just part of the reason for sequencing the activation and deactivation of three lighting functions (beacon, windsock & obstacle ). The other (main? :) ) reason is that the sequential ramping up and down of the tower's lights would add a bit of flair to what would otherwise appear to be the simple flipping of one big light switch on and off.
 
Last edited:

Thread Starter

Rabbit H

Joined Aug 5, 2016
153
Guys,

It's been about half a year since I started this thread and it's run its course. To be honest with you, I blame myself because I wasn't exactly sure of what I wanted to accomplish when I posted it. And if I can't clearly tell you what I'm trying to do, it's a sure bet that you won't be able to tell me! Frankly, I feel bad for wasting your time.

However, half a year later I've ironed out what I need and since it's hardly the same today as it was 6 months ago, I've elected to close this thread and start a new, CLEARER one.

The major change is that the original thread started out with a very difficult goal; which required designing and constructing an RF receiver/decoder. In the six months since, I've located and purchased a professionally-built unit that will do just what I need. Woo Hoo!!!

However, I still need to design and build the control circuits that will be downstream of the receiver/decoder. While probably a simple thing, I can't seem to come up with an easy (uncomplicated!!!) circuit. Soooo... In order to start clean-sheet, I've started a new thread at:

https://forum.allaboutcircuits.com/threads/designing-a-lights-controller.151275/

Thanks in advance for any input you can offer!,

Harvey
 
Top