From: David Lang <david@lang.hm>
To: Eric Johansson <esj@eggo.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] LimeSDR: Flexible, Next-generation, Open Source Software Defined Radio
Date: Thu, 28 Apr 2016 14:13:02 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1604281411280.4027@nftneq.ynat.uz> (raw)
In-Reply-To: <alpine.DEB.2.02.1604281355300.4027@nftneq.ynat.uz>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2236 bytes --]
found it
https://www.crowdsupply.com/lime-micro/limesdr
early bird price $199 100Khz-3.8GHz, >60MHz bandwidth at 12 bit sample depth
4 transmit and 6 receive antennas, two separate transmitters and two separate
receivers.
USB 3 interface.
looks intereting
David Lang
On Thu, 28 Apr 2016, David Lang wrote:
> Date: Thu, 28 Apr 2016 13:58:47 -0700 (PDT)
> From: David Lang <david@lang.hm>
> To: Eric Johansson <esj@eggo.org>
> Cc: "cerowrt-devel@lists.bufferbloat.net"
> <cerowrt-devel@lists.bufferbloat.net>
> Subject: Re: [Cerowrt-devel] LimeSDR: Flexible, Next-generation,
> Open Source Software Defined Radio
>
> so what are the technical specs, costs, and expected shipping date?
>
> a 10 antenna SDR system with a FPGA opens up some very interesting
> possibilities.
>
> David Lang
>
> On Thu, 28 Apr 2016, Eric Johansson wrote:
>
>> Date: Thu, 28 Apr 2016 16:39:35 -0400
>> From: Eric Johansson <esj@eggo.org>
>> To: "cerowrt-devel@lists.bufferbloat.net"
>> <cerowrt-devel@lists.bufferbloat.net>
>> Subject: [Cerowrt-devel] LimeSDR: Flexible, Next-generation,
>> Open Source Software Defined Radio
>>
>> http://qrznow.com/limesdr-flexible-next-generation-open-source-software-defined-radio
>>
>> from the advertising copy:
>>
>> A Software Defined Radio for Everyone
>> LimeSDR is a low cost, open source, apps-enabled (more on that later)
>> software defined radio (SDR) platform that can be used to support just
>> about any type of wireless communication standard, including UMTS, LTE,
>> GSM, LoRa, Bluetooth, Zigbee, RFID, and Digital Broadcasting, to name but a
>> few.
>>
>> While most SDRs have remained the domain of RF and protocol experts,
>> LimeSDR is usable by anyone familiar with the idea of an app store –
>> LimeSDR is the first SDR to integrate with Snappy Ubuntu Core. This means
>> you can easily download new LimeSDR apps from developers around the world.
>> If you’re a developer yourself, then you can share and/or sell your LimeSDR
>> apps through Snappy Ubuntu Core as well.
>>
>>
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: TEXT/PLAIN, Size: 164 bytes --]
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2016-04-28 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 20:39 Eric Johansson
2016-04-28 20:58 ` David Lang
2016-04-28 21:13 ` David Lang [this message]
2016-04-28 22:54 ` Eric Johansson
2016-04-29 1:27 ` Outback Dingo
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1604281411280.4027@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=esj@eggo.org \
/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