Defining a connection in Sequencer

RemoteSign Sequencer allows you to control one or more RemoteSigns.

Each RemoteSign that you wish to control needs accessible on your network, and you need to tell RemoteSign Sequencer where these RemoteSigns are on the network.  They use the Internet TCPIP protocol for communicating. This means that any two computers on a local area network (LAN) or even any two connected to the Internet will be able to communicate with each other. The computers could be a Windows machine running RemoteSign Sequencer and a second Windows machine running RemoteSign, or, the second computer can be a RemoteSign ESP module, or both.

Step 1

The first step is to find out either the network name (also called a host name) or the IP address of the RemoteSign that you wish to control. Both Windows RemoteSign and RemoteSign ESP let you know what their network address is, so that you can enter that address in RemoteSign Sequencer.

RemoteSign ESP

Once a RemoteSign ESP, gets onto the network via Wifi, it display its IP address and unique network name. In this example, the IP address is 192.168.86.172 and the network name is remotesignc6cf88


Windows RemoteSign

To find the Network name and IP address,
  1. On the remote Windows computer, start RemoteSign
  2. Press 'C' to display the Connection screen.
  3. Click the radio button Wait for remote connection
  4. Note the machine name and IP address
  5. Press Escape or click 'Close'

Step 2

In RemoteSign Sequencer, if you are trying a sample file that has a RemoteSign partially defined like this:

Click the Edit button and enter the network name address that you found in Step 1. You can also name the RemoteSign to something more meaningful...


Click OK

If you wish to add additional RemoteSigns, click the 'Add a RemoteSign' button:


Give it a name (whatever you like) and enter the network address you found in Step 1

One you have defined the RemoteSigns, you can manually connect using the 'Connect' button, or if the 'Auto connect' box is checked, Sequencer will connect automatically.

This shows a successful connection... it shows the name and IP address of the other machine and also what software is running there.

Once connected, the top status light on the RemoteSign on Windows will turn green and
RemoteSign ESP signs will switch to a blank screen.

Remember to save your changes by pressing Ctrl-S or using File  Save

Connection failures

If you get connection failures (red status light) press 'W' in the Windows RemoteSign to force it to wait for a connection.

If the signs won't connect, double check the network name. Sometimes the network router uses a slightly different name to the host name. If trying a network name fails, try adding .local or .lan to the end of the hostname. Failing that, from a command prompt,

enter the command:

nslookup 192.168.1.xx 

(where 192.168.1.xx is the IP address of the machine you are trying to reach)
and it should tell you the name of the host you should use. Enter the name exactly and with same casing.

You can also use IP addresses....

Note however, that the IP address may change next time the device is started. If you use IP addresses and have a modern router you may be able to configure that device to always be given the same IP address or you can assign a static IP address.

If you are running RemoteSign and RemoteSign Sequencer on the same computer, you can use 127.1.1.1 as the IP address in the next step. It is a special IP address that means "this machine".

Connecting to a computer that is behind a firewall or router

By default, RemoteSign uses TCPIP port 50601. When you try to connect or wait for a connection on a machine that is running firewall software you may get a pop-up asking permission for RemoteSign to access the network (connecting to another machine). RemoteSign will not work unless you allow these operations.

If your RemoteSign that is waiting for a connection is on a network that has a router between the network and the rest of the internet you may have to open port 50601 to allow traffic through. You may also have to forward incoming requests on that port to the machine that is waiting for a connection. For example, on a LinkSys router the forwarding screen looks like this:


Incoming requests on port 50601 will go to the machine on the local network with the IP address 192.168.1.23. Note that if you want outside machines to be able to connect to that same machine it is advisable to allocate a static IP address to that machine.














Back to User manual