Sorry for delays with posts, I was away for 10 days. Now I’m back, and I’m gonna try to post on all things I did. First of all, I performed another space mission, XS9. Primary goal of this mission was to determine orbit pertubations and any errors that occur in X-Plane calculations, and as you will see later, it did find errors. A real lot of errors!
Now this mission is also the longest one – total duration was 4 days, 2 hours, and 30 minutes (which is 98 and a half hours). It’s been running live, realtime, for 4 days on my machine. Some fancy statistics for you number-fans:
- I had to restart simulator itself 3 times (the restarts were seamless, I made a special service which stores simulation state, and allows to restore it)
- Because of restarts, pauses and stuff like that the mission was appox 3 minutes longer than realtime. Not much if you compare to 98 hours.
- The spacecraft completed 60 orbits around the planet (or to be precise, it re-entered during 60th orbit)
- It traveled 1,490,800 miles in total (that’s 2,400,000 km)
- It gathered approx. 1.8 gigabytes of telemetry. Not that much, but more than plenty for X-Plane.
There was plenty of happenings during the mission, you can read full report here: http://xsag.wireos.com/~xmiss/xs9/mission/, but here are some key moments.
First of all, during take-off one of guidance computers failed, which automatically triggered safety mechanism, resulting in control transferred to second computer. I do not know why it did that, but most likely it was just some small software bug. It didn’t affect mission though, the ascent continued nominally (it was manual ascent). When I reached space I tried to restart first computer, and it did start up, although GDC CAUTION/WARNING alert was lit up.
I’m not exactly sure why it was lit up, but computers seemed to work fine, so I continued flight. It was later fixed after X-Plane restart, and I didn’t have any problems with computers until flight finished.
Also somewhere in middle of flight one of gyroscopes suddenly failed, but since I had two, I just altered software a bit, and it disabled the malfunctioning gyroscope.
That’s pretty much all, and for the mission goal: it turns out X-Plane fails at conserving kinetic energy, which results in orbit height growing with time, and that doesn’t allow to perform realistic flights (since amount of fuel to go back from space would be much higher than it should be).
Growth in orbit height is about 200km after 20 hours, as you can see here, on altitude graph. It covers timespan of over 2 days, which is about 35 orbits:

Interestingly enough during some times it decreased, or remained nearly stable. It is not autopilot or spacecraft issue, reaction control system was shut down, so were the primary engines. It’s just mistake in how X-Plane transfers space vehicle from one coordinate system to another. I might post about this in greater detail, but I’m thinking of overriding physics at these altitudes. I want to include own physics calculations into X-Space plugin, which concern two primary problems:
- Lack of one global coordinate system, lack of seamless transfer between local coordinate systems, lack of precision at high altitudes.
- Euler angles orientation representation, tied to local coordinate system is very very bad. I will use quaternions, or set of vectors (both really) for representing angles, which will help developing orbital autopilots.
Both of these will make X-Plane more spaceworthy, and in perspective will allow to bring it’s space part to same level as in orbiter (just without ability to travel between celestial bodies).
The only limitation for latter is lack of ability to change planets from plugin. And some problems with overriding certain rendering
Anyway, there’s plenty of telemetry for the flight, and you can download it here: http://xsag.wireos.com/~xmiss/xs9/telemetry/. It’s compressed in 7-zip archives, and split into three parts. There’s also some wrong data in beginning of each, just ignore it.
I’d post graphs, but there’s plenty of them.
Here are some pictures:
Continue reading ‘XS9′