Best method for automatic shutdown

[Sydney]

I have a standalone, unattended WO6 server in a show.

 

Does anyone have tried and tested recommendations for automated daily shutdown?

 

Windows Task Scheduler?

Or a third-party app such as Wise Auto Shutdown perhaps?

[jfk]

Neither.

Depends on other factors as well.

Once it is shutdown, how will it be started the next day?

[zackboyd]

External control is always the best option. You don't want additional services running on your display server.

[Sydney]

The WO server will be powered on manually each day and a script will start the show running after startup.

The show then runs on repeat for around six hours.

 

Were installing in a listed historic building therefore the mains power supply has to be shut-off overnight, so no scope for control the server over a network connection. We can't send commands such as powerDown (I can't find any information about this command in the user manual by the way).

 

The invigilators could just switch the server off at the power supply each night but for obvious reasons I'd prefer to run a controlled shutdown.

[jfk]

The WO server will be powered on manually each day and a script will start the show running after startup.

The show then runs on repeat for around six hours.

 

You might consider setting the watchpoint computer BIOS to startup after a power failure. (WATCHPAX always do this)

When mains power is restored, they would all start themselves.

 

 

Were installing in a listed historic building therefore the mains power supply has to be shut-off overnight, so no scope for control the server over a network connection. We can't send commands such as powerDown

 

Maybe you can, you do not need a network to do this ...

If the daily power restoration is on a consistent schedule,

then you can run an aux timeline on startup that runs for as many hours as you need,

and then sends two Output string cues to execute a controlled power down of the computer.

Set up a WATCHOUT Output for the localhost IP address (127.0.0.1) at port 3039.

see below reference for the strings to send in the cues

Those cues will only work when in cluster mode (started by a script is cluster mode)

Anytime watchmaker is in use they will error (and that is maybe not a bad thing ;-)

 

If there are multiple watchpoint comptuers in a single show group,

they have to be connected to at least a network of their own to function,

and you can add additional WATCHOUT Outputs and cues to power them down first.

 

(I can't find any information about this command in the user manual by the way).

 

The User Guide only documents cluster commands, which are sent to one watchpoint computer

which then acts as a master and it relays the commands to all other watchpoint computers in the clsuter,

resulting in a net result of communication from one to many.

 

Advanced commands like collecting the network adaptors MAC address (for later use in Wake On Lan)

and powering down watchpoint computers are 

administrative commands (strictly one to one).

Those are pretty much documented in various places in this forum.

IP power down

[Sydney]

Many thanks for the ideas and detailed instructions.

 

We're using a single standalone WO server/display PC for the show here, would that change your recommendations for a controlled shutdown?

 

Our timeline is 50 minutes duration which repeats continuously over a six hour day.

[jfk]

Many thanks for the ideas and detailed instructions.

 

We're using a single standalone WO server/display PC for the show here, would that change your recommendations for a controlled shutdown?

 

No.

 

Our timeline is 50 minutes duration which repeats continuously over a six hour day.

 

Independent of the timeline you are using now,

add a new auxiliary timeline (call it shutdown for example)

that is six hours long (or whatever) and at the

end of that aux timeline place the powerDown commands.

When your main timeline starts, send a simple run to the shutdown aux timeline.

granted each time that 50 minute show loops, it will resend the command,

but that will not interrupt or change the time position of the already running shutdown aux timeline.

[Sydney]

 

 

 

 

end of that aux timeline place the powerDown commands.

 

Could you explain how to accomplish this placement of the powerDown command?

[jfk]

Not knowing were to start with you, here is the complete process

for a clean power down 6 hours after the show has started ...

 

Create an Output in WATCHOUT

(go to Windows - Output, in the Output window, create a new Output,

name it something like WO_loopBack, set to type: TCP/IP, address: 127.0.0.1 port: 3039)

 

Go to the task window (Windows Tasks), Create a new aux timeline, open it.

With the new aux timeline as the current active window,

Go to Timeline Settings (Ctrl-J)

set the duration to 6:00:00.000 or whatever delay time you need.

Rename the timeline, something like delay_6hr-pwrDwn

Close the timeline settings dialog,

Go to just before the end of the new aux timeline, so cursor at 5:59:59.500

 

Make an Output String cue on the delay_6hrs-powerDown aux  timeline at 5:59:59.500 -

to make a string cue, drag the output listing from the output window to the aux timeline

 

In the first string cue, name it as you wish, in the string entry section, enter

authenticate 2$0D

Make another string cue at 6:00:00.000 (0.5 second later),

name it as you wish, in the string entry section type 

powerDown$0D

 

A few tenths of a second after the beginning of the main timeline (something like 0:00:00.200),

add a control cue, name it as you wish,

set the popup menu in the control cue to

Timeline named: and enter  delay_6hrs-powerDown

set to Run

done!