[AR] Re: cubesat data rates question
- From: Jonathan Goff <jongoff@xxxxxxxxx>
- To: arocket@xxxxxxxxxxxxx
- Date: Thu, 28 Nov 2013 08:41:27 -0700
I know a company working on a concept for low-cost intersatellite links,
but first-gen concept is not cubesat-scale (though probably workable for
sats in the next size range up). They're planning on communicating with
some MEO satellites (I think the O3b Networks satellites up at around
8000km). They had some clever way of handling the doppler shifting and beam
steering issues. Altius is kind of interested in the technology, since we
want a low-latency comms arrangement for some long-term telerobotic
projects. The current ~1s round-trip latency you get through TDRS makes a
lot of telerobotic tasks a *lot* harder than if you could get down into the
100-200ms round-trip-latency range.
~Jon
On Thu, Nov 28, 2013 at 8:25 AM, Aplin Alexander T <ATAPLIN@xxxxxxxxxxxxxxxx
> wrote:
> Classification: Unclassified
>
> I wonder if a network of inter-linked cubsats providing a TDRS-like
> service to other cubesats is viable? The limited life in orbit of typical
> cubesats may be a problem, but continually refreshing the network with new
> satellites may be more cost effective than requiring higher orbits.
>
>
>
> Alex Aplin
>
> "Personal e-mail. This e-mail is personal. It is not authorised or sent on
> behalf of Dstl. This e-mail is the personal responsibility of the sender."
> "The remarks in this e-mail are personal and do not represent Dstl or
> Government policy."
>
>
> "This e-mail and any attachment(s) is intended for the recipient only.
> Its unauthorised use,
> disclosure, storage or copying is not permitted. Communications with Dstl
> are monitored and/or
> recorded for system efficiency and other lawful purposes, including
> business intelligence, business
> metrics and training. Any views or opinions expressed in this e-mail do
> not necessarily reflect Dstl policy."
>
> "If you are not the intended recipient, please remove it from your system
> and notify the author of
> the email and centralenq@xxxxxxxxxxx"
>
>
Other related posts:
