Space Shuttle Ultra 1.25 Revision B development
- Thread starter Urwumpe
- Start date
Cras
Spring of Life!
- Joined
- Apr 13, 2011
- Messages
- 2,215
- Reaction score
- 0
- Points
- 36
- Location
- Los Angeles
- Website
- www.youtube.com
STS-Guidance is an old MFD that does not work anymore if I recall correctly.
Not quite! It's only 19 hours old: SSU SVN log for "Rendezvous test scenario.scn"
---------- Post added at 10:43 PM ---------- Previous post was at 10:41 PM ----------
Which is why the scenario description has me puzzled. It also assumes the main engines are in line with the c.g.
Yes. It was checked in along with the SPEC034 code. I'm a bit lost on where to proceed from the scenario starting point.
SiameseCat
Addon Developer
Ignore the description. I modified an old shuttle fleet scenario.
So were in the rendezvous timeline does it start?
SiameseCat
Addon Developer
It's supposed to be just before TI. The shuttle is in the same orbit as the ISS, but slightly behind it. The TI burn should be set up on the SPEC34 display.
Quick note: For course corrections, both the T1 TIG and the transfer time will have to be changed. IRL, the TGT NO would be changed, and this would update all the other variables; this hasn't been implemented yet, since it requires I-Loading data.
Quick note: For course corrections, both the T1 TIG and the transfer time will have to be changed. IRL, the TGT NO would be changed, and this would update all the other variables; this hasn't been implemented yet, since it requires I-Loading data.
Urwumpe
Not funny anymore
- Joined
- Feb 6, 2008
- Messages
- 38,965
- Reaction score
- 3,937
- Points
- 203
- Location
- Wolfsburg
- Preferred Pronouns
- Sire
Wouldn't it be better to finalize those features that are now there and prepare a next release? Couldn't harm to have a release from our chest before we go into the new features again.
Of course, only if all agree that the current state is playable.
Urwumpe
Not funny anymore
- Joined
- Feb 6, 2008
- Messages
- 38,965
- Reaction score
- 3,937
- Points
- 203
- Location
- Wolfsburg
- Preferred Pronouns
- Sire
Sounds like a good plan to me, if it is just these subsystems.
My personal favorite solution would be bringing all mechanic subsystems on the relay logic/motor assembly concept that I prefer (Based on the specifications of the real relays and powered switches, that the Space Shuttle used), but this could be a bit too time consuming for a release plan. If somebody would like a faster solution, I won't disagree there. I can't code the good solutions as fast, as I would like to, and who delivers is right.
About the Ku band radar - pointing the antenna and get proper data, including PRF effects on Doppler velocity and Range?
Donamy
Addon Developer
It would be nice to have another visual tool to use in the VC.
Donamy
Addon Developer
Agreed !!!
---------- Post added at 06:53 PM ---------- Previous post was at 06:52 PM ----------
Yes
Urwumpe
Not funny anymore
- Joined
- Feb 6, 2008
- Messages
- 38,965
- Reaction score
- 3,937
- Points
- 203
- Location
- Wolfsburg
- Preferred Pronouns
- Sire
I don't think we should include it now, because I feel like it would take a few weeks to implement. (Also we still have no PEG4 autopilot, which permits entering the data for a proper de-orbit burn)
Otherwise, I would suggest finally agreeing on a release manifest, in which we say definitely what has to be finished for the next release, and what means that all other features have to wait for a next release.
Found these documents on the Shuttle obiter Ku band radar/comm system: http://ntrs.nasa.gov/search.jsp?N=0&Ntk=All&Ntt=Shuttle%20orbiter%20Ku-band%20radar%2Fcommunications%20system&Ntx=mode%20matchallpartial%20
Urwumpe
Not funny anymore
- Joined
- Feb 6, 2008
- Messages
- 38,965
- Reaction score
- 3,937
- Points
- 203
- Location
- Wolfsburg
- Preferred Pronouns
- Sire
Yeah, I also have one from the IEEE, which describes the pulse repetition pattern of the radar, and how it changes depending on range. There are formulas in the internet that describe how the pulse patterns relate to range and velocity measurements. One kind of PRF gives you good range data, but poor velocity data, etc. Mixing the extremes reduces the errors.
