This page describes using (and hopefully not abusing) the revised Moog platform. Originally (up until January 2014) the Moog was run using a set of physical motion and rendering libraries written for Linux. As of January 2014 the device now runs Unity and Matt’s motion libraries are being ported to the Unity framework.
The Moog Platform
The platform is a 6DOF2000E Moog Motion platform. There are two critical manuals for the machine.
- User’s Manual. It has a number of critical sections, mostly related to servicing the machine and lubricating it. The lubrication section is important. When the machine starts sounding like its grinding when it moves, it is, and it needs to be topped up. There are two copies of this in the lab. DO NOT TAKE THEM FROM THE MOOG ROOM.
- Programming Manual. There is an electronic copy of this, available here for local access only. You will hopefully never have to look at this at all.
Running the Moog. It should always be on. There is a monitor on the operator’s desk with a keyboard and a display. It should always be on and it should normally be displaying the error message ‘Need host communications’ if its not running. Don’t turn the Moog off. Don’t plug it into a non-protected power circuit. (Last time someone did that it took the device out of service for about six months.)
The Moog is protected by a number of emergency stop triggers and gates. You know that they are all engaged when the red light is on above the door. If you want the light on, and its off, check the following
- Key’d switch on the wall. It should be turned clockwise to about 2pm. Do not take the key out of the holder.
- Emergency stop button on the chair. It turns to release.
- Emergency stop on the desk It turns to releaseEmergency stop on the wall by the door
- The gate separating the unit from the operator.
Breaking any one of these circuits disables power to the Moog and it will slowly sink down to its default position.
Rendering/controlling PC (shakey.cse.yorku.ca)
This machine runs Windows 7. It is not backed up in any way. (Read that last line again so that you are not surprised when it crashes and you loose all of your local files.) It is not backed up in any way. Got it? good.
The machine runs behind a firewall that isolates it and the moog platform from the network. You can access the network from shakey.cse.yorku.ca but not vice versa. Do not try to change the network infrastructure. Bad things will happen.
Internally IP addresses are assigned statically. The critical ones are
- shakey.cse.yorku.ca – 192.168.91.59
- moog.cse.yorku.ca – 192.168.91.60
- router – 192.168.91.1
The router is only accessible from the lab and it has the default password/username which will one day be written on the device so you don’t have to reset it every time you want to change this.
Shakey is a DELL PC with four video outs. In order to have all four (you need three) it is absolutely essential that you disable CrossFire in the AMD catalyst control centre.