Trigger standby through watchnet

[SFluster]

Is there a way to trigger standby mode in watchnet?

 

I couldn't find anything in the script section.

 

I've also tried setting my main display server as an external device to send the network commands but had no luck.

[joakim]

Hi SFluster.

 

It is indeed possible to trigger the standby mode of WATCHOUT through WATCHNET.

Set up your WATCHOUT main display server as an external device communicating using UDP, port 3039, and send the appropriate command.

A list of available commands can be found in the WATCHOUT manual in the "Control Protocol" section.

 

I've also attached an exported device from WATCHNET (in txt format) that you can import and start using. It contains the command you want, both hardcoded and by using parameters.

Watchout.txt

[jfk]

Hi SFluster.

 

It is indeed possible to trigger the standby mode of WATCHOUT through WATCHNET.

Set up your WATCHOUT main display server as an external device communicating using UDP, port 3039, and send the appropriate command.

A list of available commands can be found in the WATCHOUT manual in the "Control Protocol" section.

 

I've also attached an exported device from WATCHNET (in txt format) that you can import and start using. It contains the command you want, both hardcoded and by using parameters.

 

 

Have you verified this function? 

When I tried it with earlier versions of WATCHNET and watchpoint, it would not work.

Is this a recent change to allow other watchpoint control connections

to execute commands when WATCHNET is in control?

 

I assume the WATCHNET device talking to watchpoint is the same as any other Telnet connection.

When I tried it a while back, watchpoint would not allow a telnet session

to execute commands when WATCHNET is in control,

but I tried this with an earlier version of watchnet / watchpoint.

[joakim]

Hi Jim,

 

Yes this is verified and does work, but only when sending the commands over UDP.

When WATCHNET is controlling watchpoint the TCP connection is blocked.

[jfk]

Hi Jim,

 

Yes this is verified and does work, but only when sending the commands over UDP. ...

 

Ooops - missed the UDP part 

 

Did not expect the two connection types to behave differently beyond the connection itself.

I intrinsically avoid UDP due to the indeterminate nature of the connection.

In this case, beats a blank.

Thanks!

 

When WATCHNET is controlling watchpoint the TCP connection is blocked.

 

From a watchpoint perspective, should we call that WATCHNET mode?

or is is the same behavuor as production mode?

 

I believe the connection is permitted, so no connection error - commands are blocked  - same result