How (the heck) did NASA get the video camera on the Moon to track the LM ascent stage, considering the...
The Moon's distance can be as much as about 406,000 km from Earth. That's a round trip light time of roughly 2 x 406,000 / 300,000 = 2.7 seconds or more, depending on how the signal was relayed to mission control, plus any response time.
When the ascent module launched and accelerated vertically, how (the heck) did NASA get the video camera on the Moon to track it correctly several seconds in the future? Were clocks on the Moon and on the ground synchronized, or were they just anticipating based on verbal countdowns from the astronauts perhaps?
Or maybe they recruited Marvin the Martian to do the camera word?
apollo-program camera spacecraft-cameras lunar-module
asked 5 hours ago
uhoh
34.8k18120432
add a comment |
The Moon's distance can be as much as about 406,000 km from Earth. That's a round trip light time of roughly 2 x 406,000 / 300,000 = 2.7 seconds or more, depending on how the signal was relayed to mission control, plus any response time.
When the ascent module launched and accelerated vertically, how (the heck) did NASA get the video camera on the Moon to track it correctly several seconds in the future? Were clocks on the Moon and on the ground synchronized, or were they just anticipating based on verbal countdowns from the astronauts perhaps?
Or maybe they recruited Marvin the Martian to do the camera word?
apollo-program camera spacecraft-cameras lunar-module
asked 5 hours ago
uhoh
34.8k18120432
I've added random videos from a quick search, if there are better ones feel free to make suggestions or replace these with higher quality or more internet-stable versions of them. Thanks!
– uhoh
5 hours ago
1
Looking at the first video, the camera only starts panning upwards 2-3 seconds after liftoff. So it seems plausible to me that the operator only sent the command to start panning at liftoff, or just a little before. And it's not like they didn't have a nice countdown leading up to it. In general, the tracking really doesn't seem all that accurate; the ascent module barely stays within the frame. I suspect that, with a bit of simulated practice, it wouldn't be hard to manage that level of accuracy even with a 2.7 second delay.
– Ilmari Karonen
5 hours ago
@AlexHajnal No. That question is being closed, and does not ask about managing the delay. Further, answers there do not address the tracking or the delay. I've focused my question here specifically on managing the substantial delay, and the answer here does that as well. People interested in learning about delay management would not be served well by directing them to a page where the question is not answered.
– uhoh
4 hours ago
OK, I'm going to stay hands of on this one though. (I've muddied things enough already, I think)
– Alex Hajnal
4 hours ago
@AlexHajnal Stack Exchange is a strange animal and takes a while to get used to (I'm still not used to it). That's why my user profile says something like "Let Stack Exchange be Stack Exchange" ;-) In this case, the main idea is to get the most eyes to the best answers more than judging the details of the questions. update: However, I've just added "considering the substantial delay" to the title based on your concerns. Like (at)Hobbes says, SE is a collaboration. Thanks!
– uhoh
4 hours ago
add a comment |
The Moon's distance can be as much as about 406,000 km from Earth. That's a round trip light time of roughly 2 x 406,000 / 300,000 = 2.7 seconds or more, depending on how the signal was relayed to mission control, plus any response time.
When the ascent module launched and accelerated vertically, how (the heck) did NASA get the video camera on the Moon to track it correctly several seconds in the future? Were clocks on the Moon and on the ground synchronized, or were they just anticipating based on verbal countdowns from the astronauts perhaps?
Or maybe they recruited Marvin the Martian to do the camera word?
apollo-program camera spacecraft-cameras lunar-module
asked 5 hours ago
uhoh
34.8k18120432
The Moon's distance can be as much as about 406,000 km from Earth. That's a round trip light time of roughly 2 x 406,000 / 300,000 = 2.7 seconds or more, depending on how the signal was relayed to mission control, plus any response time.
When the ascent module launched and accelerated vertically, how (the heck) did NASA get the video camera on the Moon to track it correctly several seconds in the future? Were clocks on the Moon and on the ground synchronized, or were they just anticipating based on verbal countdowns from the astronauts perhaps?
Or maybe they recruited Marvin the Martian to do the camera word?
apollo-program camera spacecraft-cameras lunar-module
apollo-program camera spacecraft-cameras lunar-module
asked 5 hours ago
uhoh
34.8k18120432
asked 5 hours ago
uhoh
34.8k18120432
edited 4 hours ago
asked 5 hours ago
uhoh
34.8k18120432
asked 5 hours ago
uhoh
34.8k18120432
asked 5 hours ago
uhoh
34.8k18120432
34.8k18120432
I've added random videos from a quick search, if there are better ones feel free to make suggestions or replace these with higher quality or more internet-stable versions of them. Thanks!
– uhoh
5 hours ago
1
Looking at the first video, the camera only starts panning upwards 2-3 seconds after liftoff. So it seems plausible to me that the operator only sent the command to start panning at liftoff, or just a little before. And it's not like they didn't have a nice countdown leading up to it. In general, the tracking really doesn't seem all that accurate; the ascent module barely stays within the frame. I suspect that, with a bit of simulated practice, it wouldn't be hard to manage that level of accuracy even with a 2.7 second delay.
– Ilmari Karonen
5 hours ago
@AlexHajnal No. That question is being closed, and does not ask about managing the delay. Further, answers there do not address the tracking or the delay. I've focused my question here specifically on managing the substantial delay, and the answer here does that as well. People interested in learning about delay management would not be served well by directing them to a page where the question is not answered.
– uhoh
4 hours ago
OK, I'm going to stay hands of on this one though. (I've muddied things enough already, I think)
– Alex Hajnal
4 hours ago
@AlexHajnal Stack Exchange is a strange animal and takes a while to get used to (I'm still not used to it). That's why my user profile says something like "Let Stack Exchange be Stack Exchange" ;-) In this case, the main idea is to get the most eyes to the best answers more than judging the details of the questions. update: However, I've just added "considering the substantial delay" to the title based on your concerns. Like (at)Hobbes says, SE is a collaboration. Thanks!
– uhoh
4 hours ago
add a comment |
I've added random videos from a quick search, if there are better ones feel free to make suggestions or replace these with higher quality or more internet-stable versions of them. Thanks!
– uhoh
5 hours ago
1
Looking at the first video, the camera only starts panning upwards 2-3 seconds after liftoff. So it seems plausible to me that the operator only sent the command to start panning at liftoff, or just a little before. And it's not like they didn't have a nice countdown leading up to it. In general, the tracking really doesn't seem all that accurate; the ascent module barely stays within the frame. I suspect that, with a bit of simulated practice, it wouldn't be hard to manage that level of accuracy even with a 2.7 second delay.
– Ilmari Karonen
5 hours ago
@AlexHajnal No. That question is being closed, and does not ask about managing the delay. Further, answers there do not address the tracking or the delay. I've focused my question here specifically on managing the substantial delay, and the answer here does that as well. People interested in learning about delay management would not be served well by directing them to a page where the question is not answered.
– uhoh
4 hours ago
OK, I'm going to stay hands of on this one though. (I've muddied things enough already, I think)
– Alex Hajnal
4 hours ago
@AlexHajnal Stack Exchange is a strange animal and takes a while to get used to (I'm still not used to it). That's why my user profile says something like "Let Stack Exchange be Stack Exchange" ;-) In this case, the main idea is to get the most eyes to the best answers more than judging the details of the questions. update: However, I've just added "considering the substantial delay" to the title based on your concerns. Like (at)Hobbes says, SE is a collaboration. Thanks!
– uhoh
4 hours ago
I've added random videos from a quick search, if there are better ones feel free to make suggestions or replace these with higher quality or more internet-stable versions of them. Thanks!
– uhoh
5 hours ago
I've added random videos from a quick search, if there are better ones feel free to make suggestions or replace these with higher quality or more internet-stable versions of them. Thanks!
– uhoh
5 hours ago
1
1
Looking at the first video, the camera only starts panning upwards 2-3 seconds after liftoff. So it seems plausible to me that the operator only sent the command to start panning at liftoff, or just a little before. And it's not like they didn't have a nice countdown leading up to it. In general, the tracking really doesn't seem all that accurate; the ascent module barely stays within the frame. I suspect that, with a bit of simulated practice, it wouldn't be hard to manage that level of accuracy even with a 2.7 second delay.
– Ilmari Karonen
5 hours ago
Looking at the first video, the camera only starts panning upwards 2-3 seconds after liftoff. So it seems plausible to me that the operator only sent the command to start panning at liftoff, or just a little before. And it's not like they didn't have a nice countdown leading up to it. In general, the tracking really doesn't seem all that accurate; the ascent module barely stays within the frame. I suspect that, with a bit of simulated practice, it wouldn't be hard to manage that level of accuracy even with a 2.7 second delay.
– Ilmari Karonen
5 hours ago
@AlexHajnal No. That question is being closed, and does not ask about managing the delay. Further, answers there do not address the tracking or the delay. I've focused my question here specifically on managing the substantial delay, and the answer here does that as well. People interested in learning about delay management would not be served well by directing them to a page where the question is not answered.
– uhoh
4 hours ago
@AlexHajnal No. That question is being closed, and does not ask about managing the delay. Further, answers there do not address the tracking or the delay. I've focused my question here specifically on managing the substantial delay, and the answer here does that as well. People interested in learning about delay management would not be served well by directing them to a page where the question is not answered.
– uhoh
4 hours ago
OK, I'm going to stay hands of on this one though. (I've muddied things enough already, I think)
– Alex Hajnal
4 hours ago
OK, I'm going to stay hands of on this one though. (I've muddied things enough already, I think)
– Alex Hajnal
4 hours ago
@AlexHajnal Stack Exchange is a strange animal and takes a while to get used to (I'm still not used to it). That's why my user profile says something like "Let Stack Exchange be Stack Exchange" ;-) In this case, the main idea is to get the most eyes to the best answers more than judging the details of the questions. update: However, I've just added "considering the substantial delay" to the title based on your concerns. Like (at)Hobbes says, SE is a collaboration. Thanks!
– uhoh
4 hours ago
@AlexHajnal Stack Exchange is a strange animal and takes a while to get used to (I'm still not used to it). That's why my user profile says something like "Let Stack Exchange be Stack Exchange" ;-) In this case, the main idea is to get the most eyes to the best answers more than judging the details of the questions. update: However, I've just added "considering the substantial delay" to the title based on your concerns. Like (at)Hobbes says, SE is a collaboration. Thanks!
– uhoh
4 hours ago
add a comment |
1 Answer
1
active
oldest
votes
A controller on Earth, Ed Fendell, manually operated the camera by radio control, knowing the time of liftoff and the ascent trajectory expected and referring to a time-and-angle chart without watching the video feed in real time! According to Fendell:
Now, the way that worked was this. Harley Weyer, who worked for me, sat down and figured what the trajectory would be and where the lunar rover would be each second as it moved out, and what your settings would go to. That picture you see was taken without looking at it [the liftoff] at all. There was no watching it and doing anything with that picture. As the crew counted down, that's a [Apollo] 17 picture you see, as [Eugene] Cernan counted down and he knew he had to park in the right place because I was going to kill him, he didn't — and Gene and I are good friends, he'll tell you that — I actually sent the first command at liftoff minus three seconds. And each command was scripted, and all I was doing was looking at a clock, sending commands. I was not looking at the television. I really didn't see it until it was over with and played back. Those were just pre-set commands that were just punched out via time. That's the way it was followed.
The camera was mounted on the Lunar Roving Vehicle and was used during the EVAs to look at interesting things here and there -- essentially a third set of eyes in the field!
The LRV and its remote-controlled camera was flown on the last three Apollo missions, and only the third really got a satisfactory video of the ascent.
No attempt was made to track the ascent on Apollo 15 due to a mechanical problem with the camera.
On Apollo 16, it was difficult to pan fast enough to catch the ascent because the LRV was parked closer to the LM than on 17.
answered 5 hours ago
Russell Borogove
82.7k2276358
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
return StackExchange.using("mathjaxEditing", function () {
StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["$", "$"], ["\\(","\\)"]]);
});
});
}, "mathjax-editing");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "508"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fspace.stackexchange.com%2fquestions%2f33233%2fhow-the-heck-did-nasa-get-the-video-camera-on-the-moon-to-track-the-lm-ascent%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
A controller on Earth, Ed Fendell, manually operated the camera by radio control, knowing the time of liftoff and the ascent trajectory expected and referring to a time-and-angle chart without watching the video feed in real time! According to Fendell:
Now, the way that worked was this. Harley Weyer, who worked for me, sat down and figured what the trajectory would be and where the lunar rover would be each second as it moved out, and what your settings would go to. That picture you see was taken without looking at it [the liftoff] at all. There was no watching it and doing anything with that picture. As the crew counted down, that's a [Apollo] 17 picture you see, as [Eugene] Cernan counted down and he knew he had to park in the right place because I was going to kill him, he didn't — and Gene and I are good friends, he'll tell you that — I actually sent the first command at liftoff minus three seconds. And each command was scripted, and all I was doing was looking at a clock, sending commands. I was not looking at the television. I really didn't see it until it was over with and played back. Those were just pre-set commands that were just punched out via time. That's the way it was followed.
The camera was mounted on the Lunar Roving Vehicle and was used during the EVAs to look at interesting things here and there -- essentially a third set of eyes in the field!
The LRV and its remote-controlled camera was flown on the last three Apollo missions, and only the third really got a satisfactory video of the ascent.
No attempt was made to track the ascent on Apollo 15 due to a mechanical problem with the camera.
On Apollo 16, it was difficult to pan fast enough to catch the ascent because the LRV was parked closer to the LM than on 17.
answered 5 hours ago
Russell Borogove
82.7k2276358
add a comment |
A controller on Earth, Ed Fendell, manually operated the camera by radio control, knowing the time of liftoff and the ascent trajectory expected and referring to a time-and-angle chart without watching the video feed in real time! According to Fendell:
Now, the way that worked was this. Harley Weyer, who worked for me, sat down and figured what the trajectory would be and where the lunar rover would be each second as it moved out, and what your settings would go to. That picture you see was taken without looking at it [the liftoff] at all. There was no watching it and doing anything with that picture. As the crew counted down, that's a [Apollo] 17 picture you see, as [Eugene] Cernan counted down and he knew he had to park in the right place because I was going to kill him, he didn't — and Gene and I are good friends, he'll tell you that — I actually sent the first command at liftoff minus three seconds. And each command was scripted, and all I was doing was looking at a clock, sending commands. I was not looking at the television. I really didn't see it until it was over with and played back. Those were just pre-set commands that were just punched out via time. That's the way it was followed.
The camera was mounted on the Lunar Roving Vehicle and was used during the EVAs to look at interesting things here and there -- essentially a third set of eyes in the field!
The LRV and its remote-controlled camera was flown on the last three Apollo missions, and only the third really got a satisfactory video of the ascent.
No attempt was made to track the ascent on Apollo 15 due to a mechanical problem with the camera.
On Apollo 16, it was difficult to pan fast enough to catch the ascent because the LRV was parked closer to the LM than on 17.
answered 5 hours ago
Russell Borogove
82.7k2276358
add a comment |
A controller on Earth, Ed Fendell, manually operated the camera by radio control, knowing the time of liftoff and the ascent trajectory expected and referring to a time-and-angle chart without watching the video feed in real time! According to Fendell:
Now, the way that worked was this. Harley Weyer, who worked for me, sat down and figured what the trajectory would be and where the lunar rover would be each second as it moved out, and what your settings would go to. That picture you see was taken without looking at it [the liftoff] at all. There was no watching it and doing anything with that picture. As the crew counted down, that's a [Apollo] 17 picture you see, as [Eugene] Cernan counted down and he knew he had to park in the right place because I was going to kill him, he didn't — and Gene and I are good friends, he'll tell you that — I actually sent the first command at liftoff minus three seconds. And each command was scripted, and all I was doing was looking at a clock, sending commands. I was not looking at the television. I really didn't see it until it was over with and played back. Those were just pre-set commands that were just punched out via time. That's the way it was followed.
The camera was mounted on the Lunar Roving Vehicle and was used during the EVAs to look at interesting things here and there -- essentially a third set of eyes in the field!
The LRV and its remote-controlled camera was flown on the last three Apollo missions, and only the third really got a satisfactory video of the ascent.
No attempt was made to track the ascent on Apollo 15 due to a mechanical problem with the camera.
On Apollo 16, it was difficult to pan fast enough to catch the ascent because the LRV was parked closer to the LM than on 17.
answered 5 hours ago
Russell Borogove
82.7k2276358
A controller on Earth, Ed Fendell, manually operated the camera by radio control, knowing the time of liftoff and the ascent trajectory expected and referring to a time-and-angle chart without watching the video feed in real time! According to Fendell:
Now, the way that worked was this. Harley Weyer, who worked for me, sat down and figured what the trajectory would be and where the lunar rover would be each second as it moved out, and what your settings would go to. That picture you see was taken without looking at it [the liftoff] at all. There was no watching it and doing anything with that picture. As the crew counted down, that's a [Apollo] 17 picture you see, as [Eugene] Cernan counted down and he knew he had to park in the right place because I was going to kill him, he didn't — and Gene and I are good friends, he'll tell you that — I actually sent the first command at liftoff minus three seconds. And each command was scripted, and all I was doing was looking at a clock, sending commands. I was not looking at the television. I really didn't see it until it was over with and played back. Those were just pre-set commands that were just punched out via time. That's the way it was followed.
The camera was mounted on the Lunar Roving Vehicle and was used during the EVAs to look at interesting things here and there -- essentially a third set of eyes in the field!
The LRV and its remote-controlled camera was flown on the last three Apollo missions, and only the third really got a satisfactory video of the ascent.
No attempt was made to track the ascent on Apollo 15 due to a mechanical problem with the camera.
On Apollo 16, it was difficult to pan fast enough to catch the ascent because the LRV was parked closer to the LM than on 17.
answered 5 hours ago
Russell Borogove
82.7k2276358
edited 3 hours ago
answered 5 hours ago
Russell Borogove
82.7k2276358
answered 5 hours ago
Russell Borogove
82.7k2276358
answered 5 hours ago
Russell Borogove
82.7k2276358
82.7k2276358
add a comment |
add a comment |
Thanks for contributing an answer to Space Exploration Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
Use MathJax to format equations. MathJax reference.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fspace.stackexchange.com%2fquestions%2f33233%2fhow-the-heck-did-nasa-get-the-video-camera-on-the-moon-to-track-the-lm-ascent%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I've added random videos from a quick search, if there are better ones feel free to make suggestions or replace these with higher quality or more internet-stable versions of them. Thanks!
– uhoh
5 hours ago
1
Looking at the first video, the camera only starts panning upwards 2-3 seconds after liftoff. So it seems plausible to me that the operator only sent the command to start panning at liftoff, or just a little before. And it's not like they didn't have a nice countdown leading up to it. In general, the tracking really doesn't seem all that accurate; the ascent module barely stays within the frame. I suspect that, with a bit of simulated practice, it wouldn't be hard to manage that level of accuracy even with a 2.7 second delay.
– Ilmari Karonen
5 hours ago
@AlexHajnal No. That question is being closed, and does not ask about managing the delay. Further, answers there do not address the tracking or the delay. I've focused my question here specifically on managing the substantial delay, and the answer here does that as well. People interested in learning about delay management would not be served well by directing them to a page where the question is not answered.
– uhoh
4 hours ago
OK, I'm going to stay hands of on this one though. (I've muddied things enough already, I think)
– Alex Hajnal
4 hours ago
@AlexHajnal Stack Exchange is a strange animal and takes a while to get used to (I'm still not used to it). That's why my user profile says something like "Let Stack Exchange be Stack Exchange" ;-) In this case, the main idea is to get the most eyes to the best answers more than judging the details of the questions. update: However, I've just added "considering the substantial delay" to the title based on your concerns. Like (at)Hobbes says, SE is a collaboration. Thanks!
– uhoh
4 hours ago