Time Delay Board
Jon Levatte
Hi @melissav-monday.com thanks for your reply. I did play around with this but i decided against it as I only want to delay a minute or so max really before the lead moves over over to the closed board.
I need a delay option as well. Let us delay an automation step by seconds minutes hours or days. I created an update for an item and then it disappeared in front of me when the item moved to another board but I was not done taking action on the item. I had to go to the other board to continue updating the item. If it delayed by a minute or two It would have been less disruptive. Or at a minimum dont make it disappear when the item is open. Leave it open but move the item in the background via automationFireShot Capture 046 - real geeks - my new leads - John Clarke - upstream-residential-llc.monday.com28801396 225 KB
As a user, I want to create automation recipes with multiple steps that will run in the sequence in which they are defined on the recipe. I should be able to specify a delay (in seconds, minutes, hours, days) for each step in the automation.
+1 for a delay option. I have an automation that replicates the comments included in a text column into the conversation thread, so there is traceability of the comments modified each week. I would love to have a delay option, as sometimes the people making the updates want to go back correct something that was misspelled and the updates end up getting logged multiple times
Some automations do not process because the pulse moves to another board before it could run. Seen a lot of others have the same issue. Need to be able to add a small delay before this automation runs so everything else has run before it moves over to the next board.
In programming a show this pst week on the ION, I ran into a lack of ability I was used to on the Express boards. Previously I had been able to apply an wait time to the up fade of a cue. However when I tried doing this with delay on the ION, it would delay the whole cue. I was successful applying a wait to the down time only but never solely to the up time. Is there an easy work around for this other than creating multiple cues and linking them with follows?
ionCorrect me if I'm wrong, but hasn't most of the common Obsession / [Slash] syntax been replaced by multiple key strokes on the time and delay buttons due to the fact that we now have so many parameters that can have timings attributed too.
I've been assured by Anne that we will get the slash back for intensity time and delay. I don't know how everyone else feels, but the current behavior makes me absolutely crazy. When I'm doing simple programming, the current syntax is very fast. But once you want to change the downfade and the down delay of a cue in one commandline, it becomes awkward and cumbersome. And also, if a designer says "Time 5...Time3" I now have to figure out if he's changed his mind, or is giving me a split fade.
I think the loss of "Time/" is a good thing, because I think having too many ways to accomplish the same thing complicates the learning/teaching process, which I have to do often in my venue. I prefer a consistent and concise way to do things. ETC is good at being responsive to their customers but sometimes it leads to unnecessary complexity.
"Time/" makes sense for multi-scene preset boards with conventional lights, but EOS/Ion/Element is a tracking console that supports multiple lights. Every cue can have more than in/out time parameters. I would rather learn a new habit of pressing the [Time] key to cycle through the parameters than to have to explain the history of the Express to new users in order for them to understand the alternate syntax. I also like being able to hover over a single key rather than searching for the [ \ ] key to compose the command line.
But a couple corrections. That functionality never existed with the Express consoles, it was Obsession (and, while I'm not sure of other consoles, the Hog 2 as well. This is in no way a preset console legacy function.
As I mentioned before, the statement "Time 5 Time 3" is ambiguous, but the big problem is we don't have an efficient way of changing multiple timing parameters with one command line. Let's say that you have a cue with a Up time of 6, a Down time of 3, and no delay. The designer will say "Change the Up fade to 10, and put a delay of 5 on the Up.", or, more likely, "Cue 10 Time 5/ Delay 2/ Enter" because many designers speak time commands with slashes.
This is a whole lot more difficult with our current methodology. I appreciate the fact that time toggles through categories, but I don't find it all that useful, I will always type "FOCUS COLOR BEAM TIME" if I want all of them, and "COLOR TIME" if that's all I want. Hitting "TIME TIME TIME" to get to color time isn't really comfortable to me.
i find being able to press the time key repetedly to cycle through the different catagories handy if I'm changing a bunch of times on the one cue as i can do it in the one command line. That said, if I just want to change the colour time, I'll use the colour[time] syntax. I like having the option to do it either way depending on the circumstance and what will be faster.
In my experience, i generally find designers will say "make the cue 5 up, 10 down, and a delay of 2 on the down" as opposed to speaking syntax to me. Even if they do, speak syntax from another console eg: "make the time 5/10" does it really make a difference? Either way you need to interprate what they want and enter it into the console.
And just to complete Victor's sketch of the "speaking" designer, there are a small number of [older] designers who'll add, "Put a Wait on the Cue of 8", which requires one further step of translation by the programmer.
two pins that are un-marked are the control points. close the circuit and the relay energizes. open the circuit and the timing starts. a note is that there is no de-bounce. the unit requires a good signal before entering the timing.
The one drawback of buying from China is that the sellers never give enough information about the product. They may give the voltage but not the current, or where you need to know the size, that's omitted from the description. And there seems no easy way to ask a question about the product. Bloody annoying!
the photo of the part shows the relay. the relay is marked so you can find the coil voltage and contact ratings. the only way to find the power consumption of the control circuit is to put in on a bench and test.
I needed the schematic too so I reversed engineered it. Here it is a little late for you perhaps but hopefully it will help others. i don't know why they don't publish the schematic and actually go to the trouble of sanding off the numbers on the 4541 IC. No one is going to copy the board as you can't even buy the parts for what they sell the completed boards for with shipping!
I was hoping that someone had played with this more and had something more than the schematic, like the datasheet. I am trying to see if I can take a normally closed signal (alarm out), and apply it to a normally open circuit, to make a light turn on, with this board. I am using a Roiscok RK210PR PIR Sensor which has a normally closed 12vdc 100ma alarm circuit. I wanted to use this HC-31 relay with the Roiscok but now I am thinking I need to abandon one or both of them. Anyone have any ideas?
You could still use this circuit. You should be able to connect your NC alarm relay in series with 12v power and VCC on the 2 conductor terminal. Then connect your light and power source in series with the NC and Common contact on the 3 conductor terminal. I dont think it matters if you use S6 or S7 if you dont need the delay function.
This results in the board having power when your NC alarm relay is in normal mode. The relay board loses power when your alarm is triggered. The output relay has been open, and now shuts causing the light to turn on. Things get slightly more tricky if you want the delay functions.
It's hard to trace through that board. However that schematic for the FC-31 is incomplete with some obvious errors. Q output of the CD4541 shows connected to Vcc (shorting the output). The way Q2 transistor is connected to the collector of transistor Q3 is incomplete, as there is no path to bias Q2 ON ( it will always stay OFF). The base is always floating (not great either)
I spent hours reverse engineering the board and decided to post it to be nice. Out of all that work I only see one omission, The 10K pullup resistor for Q3 is missing. Any one with a brain could easily see what that part of the circuit is doing even with the resistor missing. I wasn't designing the board I was reverse engineering it to get an idea of it's capabilities as it obviously had more than the manufacturers "datasheet" suggests.
In the two problems you state you made an OBVIOUS ERROR (to use your words) on one. You stated "Q output of the CD4541 shows connected to Vcc (shorting the output)". Q/nQ select (pin 9) is an INPUT to select the default state of the output (Q) on pin 8. Connecting it to VCC makes Q high after reset.
So after 1300+ downloads not one person has said thanks. All I see are whiners who want everything handed to them so they don't have to think or learn and now an inconsiderate person who overstates a problem on the board and makes a real obvious error not even getting his criticism right.
I wish I could pull the schematic I posted off. I have a newer version of the schematic with the pullup resistor added and also directions on how all the inputs and outputs work. I don't think I will be posting it any time soon.
tpknet:
I needed the schematic too so I reversed engineered it. Here it is a little late for you perhaps but hopefully it will help others. i don't know why they don't publish the schematic and actually go to the trouble of sanding off the numbers on the 4541 IC. No one is going to copy the board as you can't even buy the parts for what they sell the completed boards for with shipping!