The Desktop Orbinaut
- Oct 14, 2016
- Reaction score
- San Jose Del Monte, Bulacan
Strange, Zak seems to think it didn't. But the Soyuz book does mention it kept them since it was already built, makes sense. Contradicting sources, soviet space history in a nutshell.The first 7K-T mission, Cosmos 496, had solar arrays. Had not those been installed, that test flight would not last that long
1) when you need to set the orbital period in the "globe" ... i saw that in the pdf manual you can control/set also the decimals after the minutes (the 2 red digits), but both using the english / russian text i don't get these two digits to appear ...is a my computer graphic issues? maybe screen resolution?
2) about setting the "globe" once in orbit...not sure if i am doing correctly: once in orbit i open mapMFD and i read off the lat/long position, than i move the globe with the inner/outer knob to have the crossair to the same approx lat/ong (=as written in the globe chart (the grating...)) .... and i also see if they coincide with the values displayed on the globe lat / long indicators (left/top) ... is ok doing like that?
3) didn't get how to engage "orientation to the sun" via M-16 command: basically once in orbit i enter into prograde attitude, once the orientation is established i get sensors errors 1 deg, than i switch the mode off via K-2, i wait to be in day light to see the sun and i do: K-4 to activate the BDUS and then M-16, in the HUD i got the message that the soyuz is rotating to acquire the sun but it seems never enter into the attitude, it keep slowly spinning and i never see the "45K aligned" message ... do i need to be in free drift with all rates to 0-0-0 deg/sec before to engage this mode? or am i not engaging the program K-4 correctly?
3) how to use P-6? when i am suppose to use it? you didn't mention it in the manual as well as in the flight doc but i saw you add it in your command matrix...
5) about the rendezvous ... i am practicing using the scenario you provided at approx. 100km distance ... at 30 km i engage the igla for approach ... i saw it fires thrusters and it Chage orientation but i arrived at approx. 5-6 km with still more than 20 m/s velocity and it didn't null it, basically i just miss the salyut .... the breaking burn (to null the relative velocity) was supposed to be done by the igla ? of should i fire the SKDU manually ? if so, when? (i guess it may also be a my computer issues, as i saw that with the vizor implemented i now have very low fps ... ) .... i loaded that scenario with the two vessel docked, i undock and go away few kms than i engage the igla and try the approach again and this time it docked. So maybe i am missing a manually activate SKDU burn , after the one done to intercept the salyut with transX?
I actually haven't seen any direct references to the counter decreasing during a manual burn, but maybe I missed/forgot something. It would make sense that it did and I think that's the case, but the info I've seen is more along the lines of knowing how long a burn should take. In any case, it was also used by the automatic burns, in that case they would input the delta-v and the program would use it for the burn. It's also likely they could have a semi-auto SKDU burn: since there's a "SKDU impulse" command on the KSU, and the separate "SKDU on/off" buttons on the main panel, I'm thinking through the buttons it was fully manual, but through the KSU it would start when you commanded it but turn off when the input Delta-V is reached. The idea with the main programs (as in Manoeuvre and Descent) is they consist of several "subprograms" (like orbital orientation) and commands (like activating the accelerometer), which are turned on sequentially on a time scale. The crew was supposed to be able to command each step manually in case the timing unit failed to, so it makes sense that option would be available.A side question about SKD DV burns …. I saw that once you know how much DV you need to burn, say 30 m/s, by activating the accelerometer and firing the SKD when the accumulated DV in the HUD get to 30 m/s you may cut off the engine; but all this is done looking at the HUD … how this “cut off” was supposed to be performed by the crew? Using the programs that you were mentioning you are going to implement?
Or were you suppose to set the DV in the DV counter next to the reserve DV counter (i saw that it is set to 50.5 but the number can be changed with the knob below, but it never change upon firing the SKD) and upon ignition it was supposed to count down to zero, signaling the crew when to cut off the engine? or the engine was automatically cut off?
Sure, no problem.I would like to discuss with you some others Soyuz issues, general topic not specific to this project of your, can I send you a PM to avoid cluttering this post?
That has to do with how the distance is calculated. Angles and speeds are calculated based on distance to Salyut's centre of mass, but for the displayed distance I adjust to distance to docking port. But the docking port is some 7 m away from the centre of mass of Salyut, plus it's not very well tuned. But even at small distances it shouldn't have a big impact.while the target distance on the hud is almost the same as the distance in the dokcing mfd, why the target range rate is very different from the CVEL ?
Only when paused, right? That has to do with the camera resetting. On HUD mode, I'm forcing it to the Vzor's point of view on every frame, because if you switch to VC, the camera position changes and it needs resetting when you come back to HUD view, I might be missing a way to separate both cameras. So it looks through the BO, since it's still located near where the seats are. But yeah, Orbiter only updates the position when you unpause.next, if you see my screenshots, sometimes you see over imposed to the main hud some weird imagines of the soyuz external green parts ... well when i was taking the screenshot i paused orbiter, than go to VC view to see the ELS display and than back to HUD view ... and upon coming back the double imagine was there, upon unpausing orbiter the superimposed imagine disappeared almost instaneusly ... (just in case you noticed and were thinking why i saved such weird imagines) ... sometime is not there as i save the screenshot immidiatly (withoug hitting F8), but sometime i forgot and i saved once back to hud view and the double imagine was there.