Alert

Alert #1: Windows users: If you have suddenly started getting an error message: "Requested address is a broadcast address but flag is not set", try setting a different port by editing the port number in RemoteSign.ini Try something between 50603 and 65000 instead of 50601. See the Troubleshooting page for details.

Alert #2: If you were trying order a RemoteSign ESP, please try again, the Paypal forms have been updated.

Triggering screen changes

There are a number of ways to trigger screen updates remotely:

Method 1: Using two RemoteSign Windows



  1. Connect the two RemoteSigns
  2. On either machine press the ‘1’ key on the keyboard on the horizontal row of numbers (not on the number pad)
Pressing key ‘1’ should load Sensor1On.rsf on the other computer.
Pressing key ‘2’ should load Sensor2On.rsf on the other computer.
Pressing key ‘3’ should load Sensor3On.rsf on the other computer.
etc.

Advantages
  • Easy to set up
  • Works in both directions
  • 10 scripts file pairs possible

Disadvantage
  • Cannot be triggered by train layout software

Method 2: Using RemoteSign Sequencer to send sensor commands



RemoteSign Sequencer is installed with RemoteSign, and uses the same Registration.

  1. One can create scripts in RemoteSign Sequencer to send a sensor command {S} when desired
  2. The scripts can be set up to trigger at specific times, or after a specific delay 

Advantages
  • Up to 999 file pairs possible
  • Extremely flexible scheduling of screen loading, using time of day, delays, loops, etc.
  • Same files can be activated using method 1 when Sequencer is not being used

Disadvantages
  • Cannot be triggered by train layout (yet)
  • Needs some scripting work

Method 3: Using RemoteSign Sequencer to send {LOAD} commands



RemoteSign Sequencer is installed with RemoteSign and uses the same Registration.
  1. One can create scripts in RemoteSign Sequencer to send a {LOAD} command when desired. The load command can specify the file name to be loaded on the remote machine. You can tell it to load the same files that the sensor commands use, Eg {LOAD}Sensor2on.rsf or any other file you like, Eg {LOAD}ICE3424.rsf
  2. The scripts can be set up to trigger at specific times, or after a specific delay 
Advantages
  • No limit to files that can be loaded
  • Extremely flexible scheduling of screen loading, using time of day, delays, loops, etc.
Disadvantages
  • Cannot be triggered by train layout (yet)
  • Needs some scripting effort

Method 4: Using RemoteSign ESP module trigger pins to drive RemoteSign Windows



RemoteSign ESP modules are small hardware devices that have four pins that can be grounded, thus sending 4 different sensors to a RemoteSign

  1. If these sensor commands are sent to a RemoteSign Windows, then it will load the respective file as in method 1.

Advantages
  • Can be triggered by train layout software via an accessory decoder. (Such as Märklin k84 / m84, Viessmann 5213, etc.)

Disadvantage
  • Only 4 sensors per RemoteSign ESP at present. (An 8 sensor version without a screen is under development)

Method 5: Using RemoteSign ESP module trigger pins to drive RemoteSign Sequencer



RemoteSign ESP modules are small hardware devices that have four pins that can be grounded, thus sending 4 different sensor triggers to RemoteSign Sequencer

  1. If these sensor commands are sent to a RemoteSign Sequencer, then it will trigger any script that has that sensor set as its trigger. Those scripts can inform multiple other RemoteSigns to load new screens in a similar fashion to method 3. The scripts could also create custom screens using current time of day etc., instead of only loading a predefined rsf file.

Advantages
  • Can be triggered by train layout software via an accessory decoder. (Such as Märklin k84 / m84, Viessmann 5213, etc.)
  • Multiple RemoteSign ESP modules can be used to increase the scripts triggered.
  • Complete flexibility on what gets displayed and when.
  • Can drive multiple RemoteSign displays

Disadvantages
  • Only 4 sensors per RemoteSign ESP at present. (An 8 sensor version without a screen is under development.) Note however, that 4 sensors can be combined to generate 16 different events.
  • Needs some scripting effort

Method 6: Create a sequence of screens that have delays between them


  1. A single copy of RemoteSign Windows can automatically load another file after certain period. This allow you to create a long chain of screen that will cycle through and can loop back to any point in the cycle when complete. See auto loading
See sample files Gleis1-1.rsf through Gleis1-6.rsf

Note this technique can also be combined with the other methods. For example a sensor may trigger a file to be loaded which announces an arriving train, and after some minutes, that file loads a second one automatically that brings the screen back to its default state.

Advantages

  • Requires only a single copy of RemotesSign windows on one PC
  • Time before loading the next screen can be defined for every screen
Disadvantages

  • Cannot be triggered by train layout (yet)
  • Sequence is fixed

Method 7: Encourage you train software supplier to add direct support for RemoteSign

Send them to https://remotesign.mixmox.com/p/sdk.html