From: Dotzero <dotzero@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>,
"Dave Taht via Starlink" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] the real state of "smart agriculture"?
Date: Mon, 13 Nov 2023 16:10:10 -0500 [thread overview]
Message-ID: <CAJ4XoYehFjMvNjrFRT2c-M7r8iuLHzss4Gc1sD=_SiCMn9=E0Q@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6eGLzkTSNPkxYsDafF_246-sn+qheVFQxbYYB2qK-5dw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 4092 bytes --]
On Mon, Nov 13, 2023 at 7:45 AM Dave Taht via Starlink <
starlink@lists.bufferbloat.net> wrote:
> (I am hoping others on this list with real-world AG experience can
> chime in? I enjoy realworld stories about present solutions and pain
> points[2])
>
I'm a security techie who happens to own a farm. We run a small grass
fed/finished Angus freezer beef operation in Central East Ohio. I
intentionally keep the operation fairly low tech. Security is a huge pain
point in the AG sector even if most farmers don't recognize the problem. I
first became interested in AG sector security in 2011 when a friend at
defcon introduced me to someone who hacked a 3pt corn planter remotely.
If you are interested in the use of sensors and tech in AG then you should
go to something like Farm Science Review (https://fsr.osu.edu/). Ass my
wife puts it, just the vendor area is 100+ acres of agricultural porn. A
lot of the sensing is being done using satellites, aircraft and drones
rather than sensors on the ground. You'll more likely see sensors "on the
ground" in greenhouse operations, milkining operations, etc. I'm attaching
a photo of a combine with multiple antennas. Not sure if it will make it
through the listserv.
>
> I have often been dubious of the 5g hope to dominate any major
> component of a smart ag architecture except perhaps FWA, (where
> starlink is poised and people also want to run fiber) to give it a
> good run for the money- 5g chips are too big, too hard to power, and
> too complex, and come with a monthly billing model and other
> centralized requirements that make organic evolution and solid support
> in remote environments dicy and expensive.
>
The other issue with 5g is the range.
>
> I freely concede that I may be wrong, that with sufficient subsidies,
> we will end up hanging the equivalent of a cellphone off of every
> suitably large piece of gear and ship all the data up to the cloud,
> rather than pre-process locally. Certainly the benefits of gps and
> drones are being shown every day, along with satellite weather and
> other forms of satellite analysis. [1]
>
> But the 5g sensor market? No. Nowadays smart sensors are easily
> constructed out of wifi devices such as these which cost 5 dollars or
> less:
>
>
> https://www.amazon.com/DORHEA-Development-Microcontroller-NodeMCU-32S-ESP-WROOM-32/dp/B086MJGFVV/ref=asc_df_B086MJGFVV/
>
> And the more meshy LoRA stuff now has much better range (4 miles), at
> low complexity and power also.
>
I haven't seen muh LoRA stuff in the field (yet).
>
> then there are things like amazon sidewalk:
> https://www.amazon.com/Amazon-Sidewalk/b?ie=UTF8&node=21328123011
>
> And airtags.
>
> [1] On the other hand rigorous analysis of the food we produce has
> recently discovered a marked decline in the percentage of nutritious
> minerals over the past 100 years. Please see:
>
> https://www.tandfonline.com/doi/full/10.1080/09637486.2021.1981831
>
> How smart is that?
>
> [2] Massive subsidy and diversion of river resources to the water
> hungry california almond industry during the last 7 years of drought
> led to the cancellation of the salmon fishing season last year.
>
> You should hear some of the invective that I used to hear aimed at
> "the f-ing vegetarians" along the docks I frequent in half moon bay.
> That I used to hear, anyway, The docks are eerily silent, the workers
> at other jobs, the boats not going out for anything except crab and
> squid.
>
> How smart is that? The California water table is a disaster, too. I
> vastly prefer salmon to almonds personally....
>
> I guess a meta point is easily gathering tactical data is one thing,
> sharing it sanely another, deciding on how to use it strategically,
> another.
>
> --
> :( My old R&D campus is up for sale: https://tinyurl.com/yurtlab
> Dave Täht CSO, LibreQos
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
[-- Attachment #1.2: Type: text/html, Size: 5736 bytes --]
[-- Attachment #2: Resized_20230921_101451.jpeg --]
[-- Type: image/jpeg, Size: 430020 bytes --]
next prev parent reply other threads:[~2023-11-13 21:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 12:44 Dave Taht
2023-11-13 13:10 ` [Starlink] [NNagain] " Frantisek Borsik
2023-11-13 13:31 ` [Starlink] " Nathan Owens
2023-11-13 18:19 ` dan
2023-11-13 23:22 ` [Starlink] bluetooth occupancy sensing Dave Taht
2023-11-13 23:50 ` dan
2023-11-13 21:10 ` Dotzero [this message]
[not found] ` <CAEp6xi4Ufjm9uxJ8Nv6MajSw=7SaDB5ucPadKLigV7+PPzi1Xw@mail.gmail.com>
2023-11-16 18:11 ` [Starlink] [NNagain] the real state of "smart agriculture"? Frantisek Borsik
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='CAJ4XoYehFjMvNjrFRT2c-M7r8iuLHzss4Gc1sD=_SiCMn9=E0Q@mail.gmail.com' \
--to=dotzero@gmail.com \
--cc=dave.taht@gmail.com \
--cc=nnagain@lists.bufferbloat.net \
--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