NASA Creating Laser Communication System For Mars 104
techtribune writes "NASA is in the process of developing a new technology under project Laser Communications Relay Demonstration or LCRD which will allow them to provide faster means of communications from Mars. The Mars Reconnaissance Orbiter (MRO) currently can only send at speeds of around 6 Mbps or about like a DSL modem here on Earth. At this rate, it can take upwards to 90 minutes to transmit a single high resolution image to Earth from Mars. With the MRO outfitted with the new technology it would be able to transmit the same high resolution image back to Earth at over 100 Mbps and only taking about 5 minutes to do so."
Just don't mis-aim! (Score:2)
Just don't mis-aim the laser. I'd hate for my city to blow up like in Sim City 2000 when the orbiting solar plant's beam goes off-kilter...
Re: (Score:1)
Those mis-aimed beams in Sim City 2000 were microwave, actually. Which is what we use today for such interplanetary communications. So I daresay this will only make us safer!
Re: (Score:2)
Re: (Score:2)
Hey, you need a solar filter to look at the sun, now you'll just have to buy a Mars-laser filter to safely look at Mars! It's a business opportunity!
But (Score:2)
What if it's cloudy?
Re:But (Score:4, Funny)
Well then I would suspect that the orbit is dangerously low and the last message would likely read: "Ack!"
but why? (Score:3)
why would they want a probe orbiting Mars to communicate with sharks?
6 mbps on Mars? (Score:1)
Re: (Score:2)
Re: (Score:2)
Re: (Score:3)
Yeah, but the whole planet has to share 6 Mbps.
Re: (Score:2)
Technically it's undefined.
90 minutes: partially due to speed of light limit (Score:2)
From the summary:
At this rate, it can take upwards to 90 minutes to transmit a single high resolution image to Earth from Mars
At least part of this 90 minute transmission time is due to the maximum speed of light, not the date rate. According to NASA, it takes 10 to 20 minutes [nasa.gov] to get a signal from Mars to Earth:
How long does it take for a signal to be sent from Earth to Mars?
Signals to/from Mars travel at the speed of light (186,000 miles per second, or 300,000 kilometers per second). It takes between 10 and 20 minutes for a signal to travel from Earth to Mars, depending on the relative position of the planets at that time.
Re: (Score:1)
Math is hard, please help me.
6Mbps ~ 600KBs
600KB/s * 60 seconds/min * 90 minutes == ~3.2GB
So if the image is a raw 32 bit TIFF we're looking at at image of 28k x 28k pixels. Me thinks someone should introduce them to JPG compression.
Possible that JPEG compression too much to handle (Score:2)
I'm just speculating, but a risk-averse JPL may be concerned about using a JPEG because the extra work of compressing the raw image to a JPEG would be one more failure item on already very-complicated space probes.
Like I said, that's just my theory -- a quick google of "space probe image compression" didn't turn up anything for me; maybe others would have luck.
Discrediting my theory is a note on the Galileo Wikipedia entry [wikipedia.org] regarding the use of data compression to improve throughput after the high-gain anten
Re:90 minutes: partially due to speed of light lim (Score:5, Informative)
Science images are NEVER EVER compressed in JPEG. In fact they probably don't even use the TIFF format either. Almost all science images in astronomy are done in the FITS [wikipedia.org] format which I think was developed by NASA. This is because not only does the image need to be lossless raw data in order to be used for proper scientific measurements, but also much metadata must be included with the frame for some kinds of science observations.
Common metadata will include the position of the camera (where the orbiter was when the picture was taken), the camera's orientation (which way it was looking at the time), the exact time when the image was taken, the image exposure time, the camera's CCD temperature, whether on-chip binning has been carried out, the camera's readout noise, the camera's gain, etc. All of this information is necessary for some kinds of science and therefore NASA doesn't want to lose any of this information.
-Buck
Re:90 minutes: partially due to speed of light lim (Score:5, Informative)
. This is because not only does the image need to be lossless raw data in order to be used for proper scientific measurements, but also much metadata must be included with the frame for some kinds of science observations.
Pedantically speaking, TIFF also allows for arbitrary metadata. And all sorts of other bizarre crap. FITS is a much older format and part of the reason it is used is historical.
The main reason it is used is that it is a format specifically designed for archival use. It is a very simple format and one can easily write an image parser and writer from scratch which will happily accept and be accepted by most systems (so that ignores the more obscure non image options). I have done so.
NASA quite rightly expect FITS images to be readable in 100 years time. This is reasonable since you could probably write that parser in a couple of days without even having access to the spec. TIFF by comparison is not a simple file format.
t's also not a bad format. Lossless compression will get you at most 3x on a natural image with 8 bits per channel, but more like 1.5-2, and often is not worth the bother, especially as support for TIFF compression is somewhat spotty once it moves into more than 8 bits per channel.
one marginally irritating thing about FITS is that it is in column-major format (yay @ fortran) rather than row major, where as most capture hardware and other image formats are row-major. So, loaading/saving FITS images often requires a quadrupal for-loop (endian/channels/rows/cols) to rearrange the data.
But back on topic: 6mpbs over 400e6 km is amazing!
Re: (Score:2)
Re: (Score:1)
Re: (Score:2)
Yeah, let's decide a compression algorithm what's an important detail on extraterrestrial pictures.
Re: (Score:1)
Wrong. The 10 to 20 minutes you speak of is the latency, however this 90 minute figure is probably arrived at by taking the size of the image and dividing by the 6mbps transfer rate. It will take 10-20 minutes after the first bits leave Mars and arrive at Earth, however after Earth sees the first bit they will still have to wait 90 minutes to see the last bit.
-Buck
Don't you mean "probably wrong"? (Score:2)
Wrong.
Hmm...okay, why?
however this 90 minute figure is probably arrived at by taking the size of the image and dividing by the 6mbps transfer rate.
So let me correct that for you:
Probably Wrong.
Re: (Score:2)
Delay, not latency.
Re: (Score:2)
Re: (Score:2)
Re: (Score:3)
Your point is valid, except that the HIRISE imager on the MRO [wikipedia.org] only produces images of 16.4Gb (2.05 GB) before compression, 5Gb (630MB) after compression in red, and 1/5 of that for blue/green channels. It's only a 3 channel device. The CTX camera is lower resolution with only a single channel. MARCI operates in 7 channels, but it's also low resolution.
The MCS spectrometer operates in 9 channels, but is very low resolution.
That leaves the CRISM spectrometer as the only imager on MRO with a large number of ch
Re: (Score:2)
Um, Unless you were kidding, the transit time is a measure of LAG, not transfer speed. The original statement, that it can take 90 minutes to transmit an image to Earth, is a measure of the transfer speed, IE, when the message finishes leaving the orbiter. When Earth actually receives it is a different question. So the 10 to 20 minute speed of light lag would be in addition to the the 90 minute estimate.
Re: (Score:2)
Not speed, latency. (Score:2)
The speed isn't the issue. A sufficiently well focused and powerful laser (or multiple lasers) could probably push as much bandwidth as you need. The problem is the latency.
The distance between Earth and Mars varies from between roughly 56 and 399 million kilometres. That's a minimum round-trip time of ~374,000ms and a maximum round trip time of ~2,600,000ms, ignoring the speed of light in atmosphere. Somebody's going to make a killing selling Squid boxes when we get around to colonizing the place.
Re: (Score:3)
Re: (Score:2)
Actually, I think the bandwidth is pretty darn high. 6mbps is pretty impressive given the distance. I had no idea they could pump data that fast between planets.
Re: (Score:2)
Re: (Score:2)
I meant that while the new system makes a big improvement in bandwidth, it can't do anything about the latency due to the speed of light.
Re: (Score:2)
Bandwidth is an issue. Telemetry is extremely tightly budgeted on a mission like this, and being able to get more back would vastly increase the available science data as well as simplify operations.
And a high-powered laser is not a trivial task. First, all the power comes from solar cells, which are themselves heavy and they try to keep them minimized. Second, when you're pumping a lot of energy through a laser, you end up with a lot of heat that is difficult to discard. You can't bleed it off through
Re: (Score:1)
Somebody's going to make a killing selling Squid boxes when we get around to colonizing the place.
Not Squid on Linux - net/ipv4/tcp_timer.c
* we do not increase the rtt estimate. rto is initialized
* from rtt, but increases here. Jacobson (SIGCOMM 88) suggests
* that doubling rto each time is the least we can get away with.
* In KA9Q, Karn uses this for the first few times, and then
* goes to quadratic. netBSD doubles, but only goes up to *64,
* and clamps at 1 to 64 sec afterwards. Note that 120 sec is
* defined in the protocol as the maximum pos
Re: (Score:2)
FTP would be a bad protocol for file transfer to Mars with so much talk back and forth.
I figure they'd use HTTP POST or something similar.
Perpetual Funding (Score:2)
What about dropped packets? (Score:1)
Re: (Score:2)
I think it's safe to use UDP on this one. They're pictures. Mostly. A bit lost here. A bit lost there. No worse than a few dropped pixels. Sorta like Rick Perry or Palin. Just a little fuzzy around the edges.
Re: (Score:3)
Lose a bit here, a few dropped pixels there and you end up with the "Face On Mars." [sciencemaster.com]
I'd like us to get as much non-corrupted data as possible. Helps keep the kookie insane theory folks from getting any traction.
Re: (Score:2)
Helps keep the kookie insane theory folks from getting any traction.
Ha ha ha! Yeah right! Okay, maybe a little bit, but it's kinda like dropping a single sandbag of rationality on your front porch as the tsunami of crazy comes barreling towards shore.
At least that's how I felt once I saw that there were some theories going around that the SDO had proven that there were alien spaceships shootin' lazors at the sun, and Jupiter-sized comets in the inner solar system, based on the noise in single images.
Re: (Score:2)
Well there's no point is using IP at all, IP is designed to allow for four billion addresses. What you need in this case is a point-to-point, like a serial cable, not a network stack. Having a network stack would seriously add to the overhead.
And you certainly don't need UDP, or FTP running inside it. Dropped data is a no-no, I believe, but there's no reason you can't just send commands and return data in the raw, then ask for corrupted blocks from the data to be sent again.
It would look like this:
E: Send m
Re: (Score:2)
Re: (Score:2)
Cool, I've never heard of that before. Thanks!
Re: (Score:1)
Re: (Score:2)
Well yes, sort of, but the 'receive window' is the size of the data to be transmitted. TCP is designed to give reliability in near real-time, this kind of application needs nothing like that.
Re: (Score:2)
You calculated the expected noice and simply add enough error correcting redundancy to deal with it. You can use this for example:
https://secure.wikimedia.org/wikipedia/en/wiki/Reed%E2%80%93Solomon_error_correction
Re:What about dropped packets? (Score:4, Interesting)
eeek.
I expect that they use LDPCC, not Reed-Solomon error correction these days. Good LPCCCs get amazingly close to the shannon limit. Just crank down the rate a bit and watch the BER disappear.
GigE and greater also use LDPCC.
YMMV (Score:3)
LOLOMGWTFBBQ
Re: (Score:2)
Not "faster" but "higher data volume per second." (Score:2)
If they can make it faster, I'd be pretty impressed. That dang light speed limit really bugs me.
Chicken meets egg.Y (Score:4)
Nice planning on the communication system. Nice to see good solid planning, development and R&D. It's what NASA is good at. They also design pretty good rockets, rockets that used to take us places. Now that we have a better network, lets build the SLS and quit relying vaporcraft to get us there. Let,s quit cutting funding, and make it a priority to travel to are causing a brai Mars. We put a human on the moon and can do it again. The SLS can get us there.. we still have the brain power to go to Mars, but our politicians and misguided and overly hopeful privatization plans.... Less than one tenth of one percent of our budget is spent on space... For all of you wanting to save money, if privatizing space makes sense, why not privatize our national security, epa, and social security?? We need a heavy lifter!
Re: (Score:2)
Pecked this out on a motorola android with a broken screen.. sue me for the errors.
Re: (Score:1)
Re: (Score:2)
At least we don't have to deal with1,200,000ms latency.
SETI implications (Score:1)
So we have finally realized that lasers make sense for long-distance communications. Isn't this likely to have been realized by aliens a long time ago? I think this is why SETI hasn't found alien signals. The aliens use laser or possibly something better. We are unlikely to detect any civilizations more advanced than our own over radio.
Re: (Score:2)
Not faster (Score:2)
Higher bandwidth doesn't mean faster, it means more data over the same time. Both means are still limited by the speed of light.
Re: (Score:2)
So you don't say that your network is "faster" or "slower" when it has more or less bandwidth? Most people do. Faster means it takes less time to communicate the same amount of data. Lag/ping time is important to, and you are right that this doesn't help those numbers, but I think it can still be called faster.
A little premature, don't you think? (Score:2)
We don't even know if the Martians use big-endian encodings yet.
What's new here? (Score:2)
I'm not sure what the big deal is. I've seen this decades ago.
Granted the end points were stationary relative to each other and the distances were slightly shorter.
But all you'd really need is a 50MW laser and a phase-conjugate tracking system.
Re: (Score:2)
When you work out where to get 50MW from when you are solar powered and in orbit around Mars let me know. I'd love some of that action for my roof :)
Re: (Score:2)
Tsk tsk, it was a 5 MW laser. And the energy comes in chemical form, but it's a one shot thing. Put simply, in deference to you, it's like lasing a stick of dynamite.
Re: (Score:2)
The thing about space (besides that its big) is that it makes almost everything harder. Every spacecraft is power starved, so simply adding power is not usually a possibility -- the key is going to be getting a higher data rate for the same amount of energy, mass and operational complexity compared to radio comm.
Even more importantly: high powered lasers put off a lot of heat. On Earth, we've gotten pretty good at disposing of heat -- convection or conduction work great. Unfortunately, in space, you can
Money-making opportunity? (Score:3)
Any possibility of licensing spectrum to the Russians, the Chinese, or other countries that want to send probes to Mars? Fractional T-1 to Mars in exchange for a Soyuz ride or something...
Re: (Score:2)
You dont need a license to transmit laser light for data transmission.
Re: (Score:1)
You dont need a license to transmit laser light for data transmission
You do need a license to relay weaker signals from the surface of the planet up to an orbital platform controlled by a 3rd party.
If your probe can send signals up to an orbital platform you don't need as much power (lasers do attenuate over distance). There might be a significant weight penalty for a direct Earth-Mars laser with each probe. If you save the weight, you can send more probes to different locations instead of launching you
Re: (Score:2)
For all intensive purposes
Sigh. Did you mean "For all intents and purposes"?
Re: (Score:2)
Re: (Score:2)
That's not a bad idea, actually. Put one transmitter on Earth and one relay around Mars* and pool the resources of the transmitting nations on improving bandwidth and reliability. Then the Mars relay switches to high-bandwidth (relatively) short-range radio for the last leg.
*Realistically, a redundant set
Sounds fast! (Score:2)
Link to the Engineering? (Score:2)
Anyone have a link to the details? I'd love to see how they solved problems like atmospheric disturbances and dispersion. A cartoon of a satellite doesn't tell us jack shit about how it works.
Re: (Score:1)
The details in the proposal are probably
a) still proprietary, until the task order is issued
b) probably, to a certain extent, subject to export controls
But, in general, Space Laser Comm has been around quite a while (Lincoln Labs at MIT has done a lot of work for USAF on this).
They use pulse position modulation and avalanche/single photon kinds of detectors. It doesn't take a very big telescope on either end (and especially for Dave's project, where they're in LEO)
Think of the astronauts! (Score:2)
Nuts (Score:2)
ping (Score:1)
latency will suck though
Relativity (Score:2)
I haven't read the article, but I'm pretty sure the 5 minutes only refers to how long it will take the data to be be sent, not received. Latency on interplanetary communications is a bitch.
Average distance between Earth and Mars: 230 * 10^6 km (from Wikipedia)
230 * 10^6 km / c = 12.78 minutes (via Google)
The jargon already shows the suits have taken over (Score:2)
OIC, they've hired an M
Mars' Internet (Score:1)
asteroids! (Score:2)
Who would have figured that packet collisions will likely be caused by asteroids and meteorites.