[Discuss-gnuradio] ASRP-full-duplex-mimo-sdr-design-files-GERBER-PCB-LAYOUT- BILL OF MATERIALS-SCHEMATICS released

[Justin Bracken]

Hello Everyone,
   With great pride, we say to world that for better
research on SDR,we have decided to release all the *SCHEMATICS*,
*GERBER *files,
*PCB *files. With these files, any one with decent knowledge in hardware
domain can build a 2x2 mimo full duplex sdr on his/her own. This is
gnuradio 2x2 mimo full duplex sdr. The files uploaded are original design
files and they are working as a product. A brief explanation on its
capabilities

downloading links

click below link

https://code.google.com/p/asrp-full-duplex-mimo-sdr-design-files-gerber-pcb-schematics/source/browse/

you will find *ASRP1 assembly files, Bill of Materials, Board Schematics,
Gerber files* of the same. Happy sdr to world.

Full Duplex Software Defined Radio compatible with GNU Radio + allowing the
user flexibility in changing their radio through software.

A software radio is a wireless communications device that performs all of
its signal processing in portable, application level software. By simply
running a different program, a software radio can become a cell phone,
wireless LAN, cordless phones, garage door opener or walkie-talkie. The
flexibility enabled by software radio allows for faster technology
tracking, since standards upgrade are simple software downloads. Software
radio is a multi-disciplinary systems effort, bringing together research in
digital signal processing, communications, operating systems, software
engineering and algorithms.

ASRP MIMO is a daughtercardless 2x2 full duplex SDR transceiver complete
with RF and DAQ subsystems on a single board.

In radio , M*ultiple-Input and
Multiple-Output*, or *MIMO* (commonly pronounced my-moh or me-moh), is the
use of multiple antennas at both the transmitter and receiver to improve
communication performance.  It is one of several forms of smart
antenna
 technology.

Its architecture is designed for a true MIMO System. It meets the unique
architecture required for MIMO systems which are not part of traditional
MIMO hardware using common clock for RF subsystems where a continuous RF
phase tracking is required. Coupled with these benefits, it hosts onboard
RF transceiver subsystems capable of tuning frequencies from 400MHz to
4.4GHz.

*Supports: Windows / Linux
8MHz Realtime-IQ Streaming to PC
50MHz RF Bandwidth *
*Hardware Components:*

Altera Cyclone FPGA 12K

Cypress FX2 USB

***Quad 12-Bit 64 MSPS ADC

***( Backorder Est Avail: 2013-10-03)

Quad 14-bit 128 MSPS DAC

50MHz Lowpass filters for each channel at baseband

Dual 400MHz to 4.4GHz Quadrature Modulators with fine tuning resolution of
1Hz

Dual 400MHz to 4.4GHz Quadrature De-Modulators with fine tuning resolution
of 1Hz

LNA’s, Power amplifiers and attenuaors

Receiver Sensitivity: -115dBm upto 3.8GHz and -95dBm upto 4.4GHz

MAX RF Output Power: 17dBm with upto 25dB Output power control

Receiver Sensitivity: -115dBm upto 3.8GHz and -95dBm upto 4.4GHz

Receiver Noise figure: 6-8 dB
*SOFTWARE*

*AndroidSDRv1001* is a LiveDVD/USB image to support this SDR device without
configuration nightmares and when connected to appropriate SDR hardware,
allows for the creation of "Software Defined Radio GSM Mobile Phone
Networks", for example.

This includes Android Studio 0.1.1 Build 130.687321 Environment, as well as
contains:

*Asterisk 1.8  *http://www.asterisk.org/

*GCC 4.6.3  *gcc.gnu.org/ 

*GNU Radio 3.4.2 + GRC
*http://www/gnuradio.org/

*Java 1.7.0_21 *www.java.com/ 

*OpenBTS 2.8 *www.openbts.org/

*Ubuntu 12.04 LTS 32-bit  *http://releases.*ubuntu*.com/precise/

*Pre-configured to work with Google Voice: just add your Google Voice Email
Address & Password.
*https://www.google.com/voice

You should be able to boot off the LiveDVD / USB image and create an SDR
GSM Network in under 10 minutes cleanly.

***UHD Driver needs to be implemented to get the GNU Radio versions 3.4.2
through 3.7 applications to function

*If you are within the USA , Part 15 of the FCC Rules & Regulations allows
for utilizing SDR devices as Test Equipment.  Ettus Research, PerVices, &
other Software Defined Radio providers sell their products under the
following (Generally Speaking):*

Thanks
Ashton Martin

-- 


*It is better to remain silent and be thought a fool than to open one's
mouth and remove all doubt -- Abraham Lincoln*
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] ASRP-full-duplex-mimo-sdr-design-files-GERBER-PCB-LAYOUT- BILL OF MATERIALS-SCHEMATICS released

[Justin Bracken]

Hello Everyone,
   With great pride, we say to world that for better
research on SDR,we have decided to release all the *SCHEMATICS*,
*GERBER *files,
*PCB *files. With these files, any one with decent knowledge in hardware
domain can build a 2x2 mimo full duplex sdr on his/her own. This is
gnuradio 2x2 mimo full duplex sdr. The files uploaded are original design
files and they are working as a product. A brief explanation on its
capabilities

downloading links

click below link

https://code.google.com/p/asrp-full-duplex-mimo-sdr-design-files-gerber-pcb-schematics/source/browse/

you will find *ASRP1 assembly files, Bill of Materials, Board Schematics,
Gerber files* of the same. Happy sdr to world.

Full Duplex Software Defined Radio compatible with GNU Radio + allowing the
user flexibility in changing their radio through software.

A software radio is a wireless communications device that performs all of
its signal processing in portable, application level software. By simply
running a different program, a software radio can become a cell phone,
wireless LAN, cordless phones, garage door opener or walkie-talkie. The
flexibility enabled by software radio allows for faster technology
tracking, since standards upgrade are simple software downloads. Software
radio is a multi-disciplinary systems effort, bringing together research in
digital signal processing, communications, operating systems, software
engineering and algorithms.

ASRP MIMO is a daughtercardless 2x2 full duplex SDR transceiver complete
with RF and DAQ subsystems on a single board.

In radio , M*ultiple-Input and
Multiple-Output*, or *MIMO* (commonly pronounced my-moh or me-moh), is the
use of multiple antennas at both the transmitter and receiver to improve
communication performance.  It is one of several forms of smart
antenna
 technology.

Its architecture is designed for a true MIMO System. It meets the unique
architecture required for MIMO systems which are not part of traditional
MIMO hardware using common clock for RF subsystems where a continuous RF
phase tracking is required. Coupled with these benefits, it hosts onboard
RF transceiver subsystems capable of tuning frequencies from 400MHz to
4.4GHz.

*Supports: Windows / Linux
8MHz Realtime-IQ Streaming to PC
50MHz RF Bandwidth *
*Hardware Components:*

Altera Cyclone FPGA 12K

Cypress FX2 USB

***Quad 12-Bit 64 MSPS ADC

***( Backorder Est Avail: 2013-10-03)

Quad 14-bit 128 MSPS DAC

50MHz Lowpass filters for each channel at baseband

Dual 400MHz to 4.4GHz Quadrature Modulators with fine tuning resolution of
1Hz

Dual 400MHz to 4.4GHz Quadrature De-Modulators with fine tuning resolution
of 1Hz

LNA’s, Power amplifiers and attenuaors

Receiver Sensitivity: -115dBm upto 3.8GHz and -95dBm upto 4.4GHz

MAX RF Output Power: 17dBm with upto 25dB Output power control

Receiver Sensitivity: -115dBm upto 3.8GHz and -95dBm upto 4.4GHz

Receiver Noise figure: 6-8 dB
*SOFTWARE*

*AndroidSDRv1001* is a LiveDVD/USB image to support this SDR device without
configuration nightmares and when connected to appropriate SDR hardware,
allows for the creation of "Software Defined Radio GSM Mobile Phone
Networks", for example.

This includes Android Studio 0.1.1 Build 130.687321 Environment, as well as
contains:

*Asterisk 1.8  *http://www.asterisk.org/

*GCC 4.6.3  *gcc.gnu.org/ 

*GNU Radio 3.4.2 + GRC *http://www/gnuradio.org/

*Java 1.7.0_21 *www.java.com/ 

*OpenBTS 2.8 *www.openbts.org/

*Ubuntu 12.04 LTS 32-bit  *http://releases.*ubuntu*.com/precise/

*Pre-configured to work with Google Voice: just add your Google Voice Email
Address & Password.  *https://www.google.com/voice

You should be able to boot off the LiveDVD / USB image and create an SDR
GSM Network in under 10 minutes cleanly.

***UHD Driver needs to be implemented to get the GNU Radio versions 3.4.2
through 3.7 applications to function

*If you are within the USA , Part 15 of the FCC Rules & Regulations allows
for utilizing SDR devices as Test Equipment.  Ettus Research, PerVices, &
other Software Defined Radio providers sell their products under the
following (Generally Speaking):*

Thanks
Ashton Martin

-- 


*It is better to remain silent and be thought a fool than to open one's
mouth and remove all doubt -- Abraham Lincoln*
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] PyBOMBS: First impressions and optional dependencies

[Alexandru Csete]

On Fri, Jul 26, 2013 at 4:27 PM, Tom Rondeau  wrote:
> On Thu, Jul 25, 2013 at 7:28 AM, Alexandru Csete  wrote:
>> Greetings,
>>
>> Yesterday, I started playing with pybombs and fixed a few recipes
>> related to gr-osmosdr. During this process I made gr-osmosdr depend on
>> uhd, rtl-sdr, osmo-sdr, hackrf and gr-iqbal. I did this to ensure that
>> all supported input devices are made available to users. It should be
>> noted that all these packages are optional and gr-osmosdr would work
>> just fine with gnuradio as the only dependency still supporting
>> funcube dongles and I/Q file sources.
>
> Alex,
>
> Thanks for the report and all of the patches you submitted to PyBOMBS.
> It's a new project and will definitely need wide-spread testing and
> help to get working well on various systems and for various needs.
>
>> Later I will be adding a recipe for the gr-fcdproplus OOT source block
>> and add that as a gr-osmosdr dependency as well. This works well for
>> now since all these driver libraries are recent and well maintained.
>> However, as time goes this driver list will grow and the risk of
>> something breaking will increase. This made me think whether there may
>> be a need for a weaker dependency specification, something like the
>> "recommends" section in deb packages or the "variant" in macports?
>
> The 'recommends' is a very interesting idea. I'm not sure I like
> forcing the installation of all of the base drivers for gr-osmosdr,
> but if we have a menu-driven section if the dependencies are
> recommended and allow the user to select which, if any, to also
> install, that'd be great.
>
> Would you open a feature issue on the PyBOMBS Redmine page suggesting this?

Done.

>> As an alternate solution here & now, we could just remove all optional
>> dependencies from the gr-osmosdr recipe and instruct users to install
>> their preferred driver libraries prior to installing gr-osmosdr. Or
>> create meta-recipes that would provide the most common combinations. I
>> don't know what would be the best solution.
>
> I'm not sure, either. Until we figure out a concept like the
> recommendations, my preference is to not include them as dependencies,
> but I could be persuaded out of that thought. I'm guessing Philip
> would argue for a meta-layer :)

Maybe as compromise we can remove all optional dependencies except
rtl-sdr and uhd. That would provide a good default for 95% of the
users today and only require rtl-sdr as extra package since the
gnuradio recipe already depends on uhd.

Alex

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] new to GNUradio: AFSK and codec2 gmsk modem

[Kristoff Bonne]

Hi,


I'm still very new to GNUradio, so please excuse my (perhaps dump) 
question. I did look around at different places at the web but did not 
really find an answer:


- My first step with GNUradio was to learn a bit more about using it; so 
.. do some test.
I wanted to use GNUradio to determine the width of an AFSK signal; so I 
started looking for a AFSK modulator / demodulator; to come to the 
conclussion I didn't find one.


I looked in the GR source, on CGRAN, using several generic search 
engines without look.



Am I missing something here? I would be surprised there is no AFSK 
modulator / demodulator in GR as it would mean one cannot do packetradio 
or APRS with gnuradio.



- The main reason I am interested in gnuradio is because one of the 
projects I work on is "c2gsmk", a GMSK-based modem for VHF/UHF using the 
codec2 vocoder. Gnuradio looks to me like a very interesting platform to 
do simulation and work on the modem.
The modem is now rewriten as an API which can operate purely on 
bitstreams (i.e. all GMSK modulation / demodulation taken out of the 
code): 56 bits in (40 ms @ 1400 bps codec2), "n" times 96 or 192 Bits 
out (40 ms @ 2400 or 4800 bps c2gmsk).


I have been browsing the different documents on how to write a block and 
also looking in some code to find simular examples on how it is done. I 
have three things I kind-of do not understand.


- How does GNU radio deal with "sessions"? A c2gmsk session is not just 
a stream of bits; it has the notion of sessions. It has a beginning and 
a stream also ends; and it can end in a number of different ways.


I'm trying to understand how to fit the idea of "sessions" into GNUradio.

Or am I seeing it all wrong?



- How does GNUradio deal with information about events in the API.

The c2gmsk API does not only return a bitstream, but also information 
about events; like a change of state in the statemachine of the API, or 
an event like "a GMSK sync-pattern has been detected", or "the stream 
has terminated due to to many out-of-sync frames", or the versionid of 
the stream received, or statistics of the golay decoding process, etc.





- To get some idea of how a block is written. I have been looking at the 
codec2 encoder/decoder block. It is interesting as it is also "x bits 
in, y bits out".
However, c2gmsk is a bit different: there always is a fixed predefined 
number of bits in, but the number of bits "out" can vary. Sometimes just 
send in bits, but do not get anything back (e.g. in the decoder when the 
stream is not syncronised), sometimes one frame inbound results in one 
frame outbound, but sometimes one single frame in can result in (say) 5 
frames out. (e.g. when encodig the start of a stream).


Is this an issue for gnuradio?




Any information welcome.

Chrio!
Kr. Bonne.


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] new to GNUradio: AFSK and codec2 gmsk modem

[Marcus D. Leech]

On 07/28/2013 07:35 PM, Kristoff Bonne wrote:

Hi,


I'm still very new to GNUradio, so please excuse my (perhaps dump) 
question. I did look around at different places at the web but did not 
really find an answer:


- My first step with GNUradio was to learn a bit more about using it; 
so .. do some test.
I wanted to use GNUradio to determine the width of an AFSK signal; so 
I started looking for a AFSK modulator / demodulator; to come to the 
conclussion I didn't find one.


I looked in the GR source, on CGRAN, using several generic search 
engines without look.



Am I missing something here? I would be surprised there is no AFSK 
modulator / demodulator in GR as it would mean one cannot do 
packetradio or APRS with gnuradio.



- The main reason I am interested in gnuradio is because one of the 
projects I work on is "c2gsmk", a GMSK-based modem for VHF/UHF using 
the codec2 vocoder. Gnuradio looks to me like a very interesting 
platform to do simulation and work on the modem.
The modem is now rewriten as an API which can operate purely on 
bitstreams (i.e. all GMSK modulation / demodulation taken out of the 
code): 56 bits in (40 ms @ 1400 bps codec2), "n" times 96 or 192 Bits 
out (40 ms @ 2400 or 4800 bps c2gmsk).


I have been browsing the different documents on how to write a block 
and also looking in some code to find simular examples on how it is 
done. I have three things I kind-of do not understand.


- How does GNU radio deal with "sessions"? A c2gmsk session is not 
just a stream of bits; it has the notion of sessions. It has a 
beginning and a stream also ends; and it can end in a number of 
different ways.


I'm trying to understand how to fit the idea of "sessions" into GNUradio.

Or am I seeing it all wrong?



- How does GNUradio deal with information about events in the API.

The c2gmsk API does not only return a bitstream, but also information 
about events; like a change of state in the statemachine of the API, 
or an event like "a GMSK sync-pattern has been detected", or "the 
stream has terminated due to to many out-of-sync frames", or the 
versionid of the stream received, or statistics of the golay decoding 
process, etc.





- To get some idea of how a block is written. I have been looking at 
the codec2 encoder/decoder block. It is interesting as it is also "x 
bits in, y bits out".
However, c2gmsk is a bit different: there always is a fixed predefined 
number of bits in, but the number of bits "out" can vary. Sometimes 
just send in bits, but do not get anything back (e.g. in the decoder 
when the stream is not syncronised), sometimes one frame inbound 
results in one frame outbound, but sometimes one single frame in can 
result in (say) 5 frames out. (e.g. when encodig the start of a stream).


Is this an issue for gnuradio?




Any information welcome.

Chrio!
Kr. Bonne.


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Just found this, it might help:

https://github.com/dl1ksv/gr-afsk


Also, keep in mind that AFSK is a kind of "double modulation scheme".  
To demodulate it, first demodulate the FM-voice using a narrowband

  FM demodulator, then run that into a suitaby-configured FSK demod.

AFSK was always a "hack" to allow you to send data over narrowband 
FM-voice radios without having to do anything to the radio.  So, they chose
  Bell-202 synchronous modem tones, because they'd "fit" in most 
narrowband FM-voice radios.




___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio