From: Sauli Kiviranta <smksauli@gmail.com>
To: Dave Taht via Starlink <Starlink@lists.bufferbloat.net>
Subject: [Starlink] Testing airBaltic free Starlink in-flight WIFI for mining remote operations
Date: Fri, 6 Jun 2025 16:03:38 +0300 [thread overview]
Message-ID: <CAJbqEYCXBHr9XcdCpoz2SrxA6hOWzD=mm0DRJU+A1bfi0R0+bA@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1587 bytes --]
Last weekend I was flying from Austria to Riga, and got opportunity to test
Starlink enabled in-flight WIFI now freely available from AirBaltic. While
flying over Poland, I did a remote control "fuse check" test on a robotic
camera in a Finnish mine 400m underground, some 1300km away from the plane.
Scenario: I did remote operations test to control the camera in the mine,
with the control loop from XRTC client running through the plane WIFI
(along with the 150 other users!) to Starlink likely terminated in Poland,
then to our XRTC based RTSP relay server running on AWS in Sweden, all the
way to a Finnish mine 400m underground, where we have the mine WIFI
connected to a AXIS Q6135-LE PTZ camera that terminated the XRTC
acceleration for the TCP traffic. Then naturally the full signal loop is
returning back same path in reverse with the captured live video to be
shown on my laptop in the airplane (picture).
[image: XRTC-Starlink-airBaltic-6-2025s.jpg]
Check the video below. What this means is that I could very well be
operating a mining machine, drone, or any kind of robotic platform from
anywhere, anytime, around the globe. Even if the target is full autonomy,
there will be many cases where partial autonomy is the path in-between,
like I was now controlling the camera in the mine.
Video: https://x.com/sksauli/status/1929281402354147463
Pretty nice performance! Few hiccups in the beginning when opening the
connection, but after that it was quite smooth sailing... flying!
I do not think people fully comprehend what Starlink is enabling!
Best regards,
Sauli
[-- Attachment #1.2: Type: text/html, Size: 1782 bytes --]
[-- Attachment #2: XRTC-Starlink-airBaltic-6-2025s.jpg --]
[-- Type: image/jpeg, Size: 322191 bytes --]
next reply other threads:[~2025-06-06 13:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 13:03 Sauli Kiviranta [this message]
2025-06-06 14:36 ` J Pan
2025-06-06 14:43 ` Spencer Sevilla
2025-06-06 15:30 ` Nitinder Mohan
2025-06-06 16:03 ` J Pan
2025-06-06 16:59 ` contact
2025-06-06 17:47 ` David Collier-Brown
2025-06-07 12:26 ` Sauli Kiviranta
2025-06-07 14:17 ` J Pan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJbqEYCXBHr9XcdCpoz2SrxA6hOWzD=mm0DRJU+A1bfi0R0+bA@mail.gmail.com' \
--to=smksauli@gmail.com \
--cc=Starlink@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox