Options
Pulsing Simultaneous Relays
Jason Lowe
Posts: 1
I have a projector screen with a broken mechanical limiter to stop the screen when it lowers/raises. Replacing the screen is not an immediate option, so I need to figure out a way to send the up and down commands to the motor simultaneously. The wall control override has a "stop" button which simply crosses the two power leads, causing a momentary short which stalls the motor.
I'm going to try this code next (NI-3000 controller)
PULSE [dvSCRN1,2] //lower screen
wait 150 //give screen time to drop
PULSE {{dvSCRN1,1], [dvSCRN1.2]} //send lower and raise at same time
I've tried a few variations on this, and haven't had any success getting two relays to fire at the same time. I'm hoping I'm just making a dumb syntax error, and that firing two relays simultaneously isn't an option.
I'm going to try this code next (NI-3000 controller)
PULSE [dvSCRN1,2] //lower screen
wait 150 //give screen time to drop
PULSE {{dvSCRN1,1], [dvSCRN1.2]} //send lower and raise at same time
I've tried a few variations on this, and haven't had any success getting two relays to fire at the same time. I'm hoping I'm just making a dumb syntax error, and that firing two relays simultaneously isn't an option.
0
Comments
Should pulse both relays "simultaneously". They won't get triggered at exactly the same time, since one will execute a few milliseconds after the other but that shouldn't matter in your case. Netlinx being single threaded, there is no way to do things exactly simultaneously.
Paul
You seem to have a full stop in your second relay
PULSE [dvSCRN1,2] //lower screen
wait 150 //give screen time to drop
PULSE {{dvSCRN1,1], [dvSCRN1,2]} //send lower and raise at same time
You seem to have a curly brace where you should have a square bracket...LOL
PULSE [dvSCRN1,2] //lower screen
wait 150 //give screen time to drop
PULSE {[dvSCRN1,1], [dvSCRN1,2]} //send lower and raise at same time[/QUOTE]
Will this actually work?
Will Pulse take multiple DevChans?
Tested
PULSE will not take multiple DevChans.
This won't help with your code issue, but that be dangerous territory you're entering. Without knowing your exact situation, what will the result be if the motor controller doesn't get the stop command? Screen winding back up on itself and getting damaged? Screen canister falling from the sky (seen this before)? Motor bursting into flames?
There are multiple reasons why a motor controller wouldn't see a contact closure from a control system, or see the closure but not act on it, and though it may happen rarely this could create a hazardous situation. Hardware limiters are there for a reason...