Range 3 km as seen from ISS.800 mm lens used from window 9 on ISS, Progress seen as a dot from that vantage point.
Progress is in safe distance of about 3 km.Docking cancelled for todayEDIT: another picture from ISS, Progress flying near the complex
When was the last time that happened?
Quote from: Chris Bergin on 07/02/2010 05:17 pmWhen was the last time that happened?According to Wikipedia, the last time a Progress docking was aborted was in August 1994 (that was to Mir).
Quote from: aquarius on 07/02/2010 05:37 pmQuote from: Chris Bergin on 07/02/2010 05:17 pmWhen was the last time that happened?According to Wikipedia, the last time a Progress docking was aborted was in August 1994 (that was to Mir).but the other abort was the collision to Mir in 1997, this event was a abort or just a fail during docking?
Sorry, that's the moon, not Progress.
Quote from: lcs on 07/02/2010 05:48 pmSorry, that's the moon, not Progress.I don't think so, is not a good view because was during a zoom, if I am wrong, plis forgive me
Lastly, AFAIK, Progress does not have to be over a Russian ground station for TsUP to control Progress during dockings, the Russian segment can communicate with TsUP via TDRS.
Quote from: Danderman on 07/02/2010 05:48 pmLastly, AFAIK, Progress does not have to be over a Russian ground station for TsUP to control Progress during dockings, the Russian segment can communicate with TsUP via TDRS.I don't think so. I think that TDRS allows only voice transmission for Russian Segment, and that they have to fly over RGS to send telemetry.
But from the TORU screen it looks like the vehicle had a 7-9 m/sec approach rate and never nulled it -- kept right on going in, missing the station -- but by how much?
I'm trying to reconstruct the relative motion of this abort and some things are bothering me. TsUP-M says the abort was declared at a range of 2 km, which is short of the 'stop' point where the vehicle then makes a constant-range fly-around to align with the docking port approach vector.Press reports also state that the crew tried to engage TORU but were unable to achieve control -- the vehicle never acknowledged their commands. I seem to recall that the automated approach emergency modes included stopping the approach and initiating a backaway if no commands are received. But from the TORU screen it looks like the vehicle had a 7-9 m/sec approach rate and never nulled it -- kept right on going in, missing the station -- but by how much?
The Progress was flying about half a minute preceding the ISS.
Russian and US ISS program managers will meet the morning of Saturday, July 3 to assess the next docking opportunity, preliminarily identified as approximately 4:17 PM GMT on Sunday, July 4. The Progress will conduct two engine firings tonight and another tomorrow to be in position for the potential docking Sunday.
What would be the last-last-last measure to be taken if a Progress happened to deviate from its "safe" approach trajectory in just such a manner that it pointed straight at the ISS, and all on-board and remote control efforts failed?
Boosting the ISS orbit to take evasive action?
a one-burn ISS reboost was conducted last night at 11:20pm EDT using SM main propulsion, i.e., its two main engines. Performance was nominal. Burn duration: 4 min 7 sec; delta-V: 4.5 m/s
What would be the inpact on Exp-24 if this Progress can not dock ??I'm sure there is plenty of food, but what would happen with the EVA's or other planned launches ??
carries 2230 kg (4916 lbs) of cargo, specifically: 870 kg (1918 lbs) propellants, 50 kg (110 lbs) oxygen & air, 100 kg (220 lbs) water and 1210 kg (2667 lbs) spare parts & experiment hardware.
Quote from: jacqmans on 07/03/2010 09:24 amWhat would be the inpact on Exp-24 if this Progress can not dock ??I'm sure there is plenty of food, but what would happen with the EVA's or other planned launches ??I haven't been able to find a detailed cargo manifest for this latest Progress. As a starting point, from a recent ISS On-Orbit Status Report, the Progress M-06M vehicle:Quotecarries 2230 kg (4916 lbs) of cargo, specifically: 870 kg (1918 lbs) propellants, 50 kg (110 lbs) oxygen & air, 100 kg (220 lbs) water and 1210 kg (2667 lbs) spare parts & experiment hardware.
* 877 kg of fuel for the Zvezdá module. * 250 kg of fuel for reboost maneuvers for ISS. * 51 kg of oxygen. * 300 kg of water for the Rodnik system. * 1152 kg in the pressurized compartment (GrO). * 266 kg of food and drinks. * 426 kg of cargo for the USOS (including food supplies). * 79 kg for scientific equipment. * 4 kg of fire-preventing equipment. * 42 kg of medicines and hygiene products. * 52 kg of photographic and video materials. * 77 kg of equipment for the Zaryá module. * 2 kg of equipment for the Poisk module. * 4 kg of equipment for the Rassvet module.
Spaceweather site gave this detail:-".....The unexpected docking problem was related to the rocket's KURS automated docking system. Russian ground teams are analyzing the data and hope to come up with a solution soon. Tentatively, mission controllers expect to try again on Sunday, July 4th, around 12:17 pm EDT...."
From www.nasa.gov/station:QuoteRussian and US ISS program managers will meet the morning of Saturday, July 3 to assess the next docking opportunity, preliminarily identified as approximately 4:17 PM GMT on Sunday, July 4. The Progress will conduct two engine firings tonight and another tomorrow to be in position for the potential docking Sunday.
International Space Station Program officials from NASA and Roscosmos met Saturday morning and agreed to proceed toward a second docking attempt for the ISS Progress 38 cargo ship on Sunday, July 4, at approximately 12:10 PM EDT/4:10 PM GMT. They will meet again Sunday morning to reconfirm the status of the space station and spacecraft systems. NASA TV coverage of the second docking attempt for the Progress 38 cargo ship to the station will begin Sunday at 11:30 AM GMT/3:30 PM GMT.The Progress 38 conducted two successful firings of its engines Friday night to put the craft in a parking orbit around 300 kilometers from the space station. Another engine firing is being conducted Saturday morning to start the process of returning the spacecraft back to the station for Sunday’s docking attempt.Russian specialists told program officials the cause of Friday's aborted docking was what they termed a "cancel dynamic operations" command that instructed Progress' computers to fly the vehicle past the station on its final approach for docking, as it is intended to do if the internal guidance system receives conflicting commands or commands that do not comply with its pre-programmed commands.The Russian flight controllers said the command to cancel was caused by the activation of the TV transmitter for the TORU manual rendezvous system in the Zvezda Service Module, which interefered with the Kurs automated rendezvous system. TORU is used to override Kurs, which Progress normally uses for docking, in the event Kurs experiences a problem. The TORU TV system is designed to provide a view of Zvezda's docking target to station Commander Alexander Skvorstov, if he had to operate a joystick in the service module to dock Progress manually.The Russian flight control team has confirmed the Kurs system operated normally and did not fail, as was initially believed. Kurs uses radio beacon signals beamed back and forth between the approaching spacecraft and the space station to measure distance between the two vehicles and the rate of closure by Progress to Zvezda.Russian officials said the TORU system will not be activated Sunday for the second docking attempt as a precautionary measure and expressed full confidence Sunday’s docking can be conducted without any further issue.Overnight, Russian specialists conducted a successful test with both the prime and backup strings of the Kurs automated rendezvous system on both the Progress and Zvezda. Another test of both strings will be conducted Saturday night. A final test of the Kurs system, as is always conducted during the terminal phase of the rendezvous, will be performed about 50 minutes prior to docking when Progress is 15 kilometers from the station.In the unlikely event the prime Kurs string of telemetry fails late in the rendezvous sequence on final approach, Kurs' backup string will take over through docking. If the second string should fail, an automatic abort would be triggered, and Progress would immediately halt its approach and back away from the station to a safe distance. Multiple docking attempts could be made if needed.The Expedition 24 crew members onboard the space station were notified by the team in Mission Control in Houston that another docking attempt will be made Sunday. They have an off-duty day Saturday and will adjust their workday schedule to monitor the docking activities Sunday.
So far as I can tell, the chronological order of events that caused the abort was as follows:• The TORU TV transmitter in the SM was activated by the crew, which interfered with the data being sent between the KURS-A on Progress and the KURS-P in the SM.• The KURS-A on Progress interpreted this interference as conflicting commands to its pre-programmed commands, and so initiated the "cancel dynamic operations" command that instructed Progress to fly past the ISS.The only question that remains is: Who turned on the TORU TV transmitter?
The only question that remains is: Who turned on the TORU TV transmitter?
