Mission Space Simulator

https://mcpeshare.com

Overview

This is a mission space simulator. The simulator is running on a server in a datacenter in Dallas, TX. The backend simulator is written in PHP and makes a good attempt to simulate running an Orange Bay. You can power up / down, home the bay and dispatch the ride just like you would do in real life. You can also hit ride stop, E-Stop, dispatch inhibit etc. and they act like you would expect. If the ride was running and you click Ride Stop the ride will return to the home position and raise the floors. If you hit E-Stop while the ride is running it will come to a fairly quick stop and the floors will be left down. If you hit power disconnect while the ride is running is will coast to a stop and the floors will be left down.

Naturally after an E-Stop or Power Down you will have to power up and re-home the bay. There is one capsule control panel to open and close all 10 capsules, of course in real life you have to do this 10 times... When the ride is finished the capsule doors and exit doors will automatically open, and after a brief time the entrance doors will open and then eventually automatically close just like in real life.

There is a random chance that you will get one or more door obstructions which will cause the entrance door LED to blink yellow, you must then manually close the entrance doors. In real life you would walk the perimeter inside the bay when this happens. After closing the capsules and all entrance, ADA, and exit doors and if there are no dispatch inhibits, ride stops, or e-stops you should get the flashing green dispatch button.

Once you press the dispatch button there is a random chance that you may get one or more intelli-video or motion sensor alarms. You will need to open your exit doors to investigate the issue and then ask mission control to clear your dispatch inhibit. Once cleared you should be able to dispatch the ride. In the simulator it will not give you an alarm twice in a row (so no need to retrain!).

The web portion of the simulator is a combination of html, css, and a lot of javascript. Every attempt was made to make this simulator as accurate as possible but is not meant to be a replacement for live instructor training. Also it is a shared web page, if you are interacting with it and you suddenly see a ride stop it may be that another person has logged in and clicked ride stop! When you open the web page it will ask you for a 4 digit code to proceed. It's the same code we use on our devices. I hope you enjoy the simulator. From time to time I host Bay 5 pizza parties at my house where you can play around with the physical Bay 5 simulator panels and even use the intercom!

Physical Bay 5 Simulator Panel showing Launch Physical Bay 5 Simulator Panel showing Mission Control

Hardware Construction

The physical Bay 5 was about a 6 month effort in sourcing the physical buttons, switches, indicators etc to match the actual panels for the real ride as well as assembling, soldering, and crimping everything together. I went through several revisions along the way especially with the wiring between the two panels and how I drive the 24V LEDs.

Wiring inside the metal enclosure Exposed circuit boards, relays, mixing board, and power supplies

Most of the hardware switches and indicators were purchased used on E-Bay but some I had to purchase new from the suppliers. The panels were cutout and manufactured by a company called Front Panel Express. I used their free design tool to design each panel specifying the exact size and location of any cutouts and any printed graphics or engraved lettering.

The panel itself is run by a Rasberry Pi linux computer and uses an I2C (2-wire data bus) to send and receive data to 6 separate 16 GPIO daughter boards (these give 16 general purpose I/O pins each) that I use to detect switches and control panel indicators. The 12C bus also sends data to the countdown LED timer. The hdmi output from the raspberry pi is connected to the VDT and basically is displaying a web page that shows the VDT or BAY overhead view. There are also two relays, one to mute / unmute the mission control microphone based on the intercom toggle switch and another for the power disconnect which removes the 24v power from the panels.

Whenever you press a physical button on the panel it sends an http request to the server in Dallas running the simulator much like when you interact with the web based simulator. There is a power supply which provides 24v (for the LED indicators), 5v (for logic boards and the raspberry Pi), and 12v for the intercom amplifiers. There is also a small mixing board that handles the intercom audio and gives a good side tone mix for the handset in the launch panel.

There are buzzers for the alarm and intercom paging as well. I also use an Arduino nano to control the alarm on / off cadence and intercom paging beep duration. The code on the raspberry pi is a mixture of Python (to send and receive data from the I2C bus), and php to send and receive data to the backend simulator in Dallas and the web browser to display the VDT.

Launch Panel

Launch Panel Interface showing Entrance, Exit, Emergency, Ride Stop, and Dispatch buttons

VDT (Video Display Terminal)

Video Display Terminal Interface showing log messages

This shows the VDT screen much like you would see in real life. Most messages are pretty accurate as to what you would actually see in real life. Naturally not every message will be exact especially during power up / down, but it pretty much follows what you would see. Currently the System Mode: will always show NORMAL even during power down / up. One day I'll fix that. The Load Time, Run Time, and MAC Speed are pretty accurate.

Mission Control Panel

Mission Control Panel showing Power Disconnect, Emergency Stop, and Tower Enable buttons

Overhead BAY View

Overhead BAY View showing 10 capsules

This shows the status of the simulator. You can see capsule doors, entrance, exit, and exit corridor doors. You can also see the status of the floors as they will appear darkened when lowered. You can also see the ride run time, current RPMs and total number of spins as the ride progresses.

Capsule Controls, ADA Door and Operator Present

Capsule Controls interface showing Door Open/Close, Seat Restraint, and ADA Door