RidePlayer Fleet Deployment

In WinScript, we've now made it possible to deploy a script to multiple show controllers at once. This will come in handy if you are working with a fleet of RidePlayers, where each RidePlayer has the same script that is running. This functionality is achieved by using the Send Button: mceclip0.png


To start, we need to adjust our RidePlayer script into a script that can be deployed to multiple show controllers.

You probably already have a RidePlayer script built up. All you need to do to enable this functionality is double click on your local show controller in your script to open the Edit Device dialog, and check the Used on multiple controllers box. This will then allow you to select your fleet count, as well if you'd like your RidePlayer fleet names to be zero indexed. In my example, I have a fleet of three rideplayers, and I'd like them to be referenced as RV[1], RV[2], and RV[3], so I am not going to check the zero indexed box. Click "Finish", and now your script is ready to be deployed to a fleet!


To deploy your script, we'll now be moving to the Send Script window, accessed by clicking:  mceclip2.png

If you're on the same network as all of your RidePlayer, you'll see them appear in the Send Script box.

Before you are deploying your script, it's a good idea to make sure all the RidePlayer have the appropriate IP address already set up. To do that before you go any further, you can setup their IP Media and IP Control addresses via the front of the unit itself, or remotely through AMI Terminal.
All of the RidePlayer on my network are being shown correctly below.


Okay - now to start assigning each RidePlayer its unique device name (part of the array we set up earlier).

You'll notice, if you click on a RidePlayer in the list, it will become highlighted, and then you can see Firmware information for that specific unit below. As you have a unit highlighted, click the Properties button. A Configure Device dialog will appear. Here, you can select the Device Name from a drop-down list, as well as give it a Nickname. The nickname is just a human-readable name you can assign to help find units easier in your script - especially if you need to name your device something more technical. Click Apply and OK.


Do the same for all of your RidePlayer units. As you do this for each unit, you'll notice the Nickname updates, and a Gray Box appears under the Status column.

The Device Names will finish updating once the script is actually sent to the units, but until then, the Device Names will just appear as the "generic name" of your array.

The status indicators next to the controller name have three different colors.
Green: Controller script and firmware is up to date.
Red: Controller is not up to date or out of sync.
Gray: The controller has not been checked.

Because we haven't sent a script yet, or clicked the verify button, all our status indicators are gray.


If you highlight all the RidePlayer in the list (click the top unit, click shift, then click the bottom unit - all will be highlighted). Let's now click the Verify button.

Now, all the status boxes are red, because the three RidePlayers still don't have our script (we haven't sent it yet!)

Another important note, the red and green indicators DO NOT take into account media files. You can check "Verify" and it go green, but RidePlayer could be missing media files that are included in the script.


Now, let's actually send a script! The send button is in the lower right of this pop up window. Before you click send, read over the three options you have with the Send Button.

Send Files Even If Device Is Up To Date: This will send the script files even if the WinScript files match. This might be helpful as a troubleshooting technique if you think one of the WinScript Files on your RidePlayer might have gotten corrupted in file transfer, or something like that.

Include Media Files: This will send Media Files that are locally included in your script but are not yet on your RidePlayer. (For a file to be locally included, in the Media Files tab of WinScript, the audio file must have the "Include" checkbox checked. You must also have the audio file in your local folder on your computer as that's where it sends the media file from when the FTP connection is established.)

If both this checkbox and the "Send Files Even If Device Is Up To Date" checkbox is also checked, it will send all the media included in your script again - regardless if the RidePlayer has them already or not.

Include Firmware Updates if Needed: This will look at the RidePlayer Firmware (found in C:\Program Files\Alcorn McBride Inc\WinScript Live 5\Controller Firmware\RPlayer ) and check it against what your RidePlayer is currently running. If they are different, when you click "send" it will send and update the firmware. If they are the same, nothing will get sent (but you will see your RidePlayer get rebooted.) If the "Send Files Even If Device Is Up To Date" checkbox is checked along with this checkbox, it does NOT send and update the firmware again (contrary to how the Include Media Files checkbox does). If you really need to re-send/re-update an identical firmware, you can do so from the Help > Update Controller Firmware window.

In the image below, I have sent the script to Vehicle 1. It then reboots (could take up to 5-8 minutes), and may disappear from your list for awhile. Don't worry, it should return when complete :)


Here, it has returned, and is now green! Meaning the script and media files match the RidePlayer's script and media files.


Again, you can highlight all of them at the same time, and click the send button only once, and an entire fleet can be deployed! We're clear to rock!!

For a more comprehensive look at RidePlayer in general, including a video detailing what's been discussed here, check out the Alcorn McBride Academy RidePlayer Course - found in the training section of our website.


Have more questions? Submit a request