Controlling Light Factory

[ChuckPuckett]

I have used SCS for years to control Light Factory. And how have I done this? By always looking at an existing SCS file and copying the telnet syntax.
Unfortunately, I lost my laptop to severe h/w failure, and had to reload SCS and LF and now I have nothing from which to cut and paste.
I need to set up SCS (which now has much better support for LF apparently) and provide the correct telnet port number (don't know what that is).
Then I can probably find the correct telnet syntax. It's "SEND " something our another.
Can anyone help me out here? Port number for LF and send syntax?
Is there something I have to do on the LF side? I established all this years ago and haven't looked at the bare bones in a long time.

[BCGTech]

I need to set up SCS (which now has much better support for LF apparently) and provide the correct telnet port number (don't know what that is).

The default port number for LightFactory is 3100, although that can be changed on the LF end but going with the default is OK. If you wish to send commands to LF from SCS, then in Production Properties/Devices/Control Send Devices, select "Network Out" as a Device Type. In the lower part of the window will appear some new options to select. In the pulldown list for "Remote Device" is the entry "LightFactrory", which if selected will fill in the default port number of 3100. You then fill in the "Server Name or IP Address" box with the name or address of the PC running LF (localhost or 127.0.0.1 if LF is running on the same PC as SCS). Notice that you can also specify a network protocol of either "telnet" or "UDP". The latest version of LF (V2.17.0 Build 120) can deal with either protocol whereas earlier versions only supported telnet. In LF, go to System Properties and System Input/Output tab and you will see check boxes to enable telnet and/or UDP. Telnet requires a network session to be established at both ends of the connection whereas UDP is "connectionless" and the network traffic is one-way. Telnet is more robust, but incurs more overhead than UDP.

Then I can probably find the correct telnet syntax. It's "SEND " something our another.

I'm a little confused here because if you are sending commands to LF from SCS, then you would create "Control Send" cues or subcues in SCS where you would specify the LF command line strings you want LF to execute. The "SEND" you mention above is an LF command that would go the other way (i.e. out of LF to some other service like SCS). If you want to do that, then there's a whole different setup to the one I described above (which I can supply on request).

Hope that gets you going again.

Bruce