Difference between revisions of "Main Page"

From HPSDRwiki
Jump to: navigation, search
(The HPSDR (High Performance Software Defined Radio) Wiki)
(HPSDR History)
Line 12: Line 12:
 
TAPR/HPSDR ordering page: http://tapr.org/kits.html
 
TAPR/HPSDR ordering page: http://tapr.org/kits.html
  
== HPSDR History ==
+
== HPSDR History and Philosophy ==
  
Here is a link to Phil Covington's website: http://pcovington.blogspot.com/2007/10/history-of-hpsdr-mercury-and-quick.html that explains some the the development history of HPSDR and Mercury and it relationship to Quick Silver. Phil is one the founding members of the HPSDR group and has very nice receiver and software based on his experiences in HPSDR.
+
The High Performance SDR project was started in October, 2005
 +
by Phil Covington (N8VB) as the OpenHPSDR Yahoo group. In
 +
November, 2005 another small group, based on the Xylo board
 +
product (an FPGA experimenter's board) with SDR applications in
 +
mind, evolved and the Xylo-SDR discussion list was formed. On
 +
March 1, 2006 the two groups merged to form HPSDR and the two
 +
discussion lists were replaced with the present HPSDR list.
 +
 
 +
Initially a small group of developers, HPSDR has grown to over
 +
800 members, including hardware, software and firmware
 +
developers; system architects; analog and digital designers; RF
 +
engineers; planners, executers and users; testers, documenters
 +
and technicians; bank presidents and sanitation engineers. While
 +
the last two are dubious, the point is that HPSDR is a diverse
 +
group. Everyone has something to contribute and all are
 +
encouraged to participate.
 +
 
 +
The rationale behind HPSDR is to break the overall design up into
 +
a number of modules. Each module is designed by an individual or
 +
group and connects to other modules using a pre-defined and
 +
common bus -- rather like plugging boards into a PC motherboard.
 +
 
 +
This modular approach enables prospective users to incorporate
 +
just the modules that interest them as well as designing their own
 +
variants if desired. The approach also enables new ideas and
 +
circuits to be tested by replacing an existing module. Since the
 +
majority of modules will be retained, such experimentation can be
 +
done with minimum disruption to an existing, working system.
 +
 
 +
The modules vary in complexity from simple band-pass filters and
 +
input/output interfaces to full blown DSP functions. Such variety
 +
enables experimenters with varying degrees of experience to
 +
contribute. If you are interested in contributing, you are invited to
 +
join in new or ongoing design, development and documentation
 +
efforts.
 +
 
 +
The modules have each been named for easier identification when
 +
talking or writing about them. On the HPSDR website, each module
 +
has its own web page. Some of the modules are being designed
 +
so that they can be either used in conjunction with others or standalone.
 +
Each module board size (except the Atlas backplane) is
 +
typically 100mm by 120mm (optionally up to 220mm) and uses
 +
either a 64 pin or 96 pin DIN41612 type connector.
  
 
== Wiki Sysop ==
 
== Wiki Sysop ==

Revision as of 20:57, 4 May 2009

The HPSDR (High Performance Software Defined Radio) Wiki

NOTICE: You do NOT need to log in to this wiki in order to read it! Only if you need to edit the material (project leaders, documentors, etc.) do you need the authorization which a login gives.

Our Internet Resources

Web pages for more stable and general information: http://openhpsdr.org

Discussion email list (reflector): http://openhpsdr.org/reflector

TAPR/HPSDR ordering page: http://tapr.org/kits.html

HPSDR History and Philosophy

The High Performance SDR project was started in October, 2005 by Phil Covington (N8VB) as the OpenHPSDR Yahoo group. In November, 2005 another small group, based on the Xylo board product (an FPGA experimenter's board) with SDR applications in mind, evolved and the Xylo-SDR discussion list was formed. On March 1, 2006 the two groups merged to form HPSDR and the two discussion lists were replaced with the present HPSDR list.

Initially a small group of developers, HPSDR has grown to over 800 members, including hardware, software and firmware developers; system architects; analog and digital designers; RF engineers; planners, executers and users; testers, documenters and technicians; bank presidents and sanitation engineers. While the last two are dubious, the point is that HPSDR is a diverse group. Everyone has something to contribute and all are encouraged to participate.

The rationale behind HPSDR is to break the overall design up into a number of modules. Each module is designed by an individual or group and connects to other modules using a pre-defined and common bus -- rather like plugging boards into a PC motherboard.

This modular approach enables prospective users to incorporate just the modules that interest them as well as designing their own variants if desired. The approach also enables new ideas and circuits to be tested by replacing an existing module. Since the majority of modules will be retained, such experimentation can be done with minimum disruption to an existing, working system.

The modules vary in complexity from simple band-pass filters and input/output interfaces to full blown DSP functions. Such variety enables experimenters with varying degrees of experience to contribute. If you are interested in contributing, you are invited to join in new or ongoing design, development and documentation efforts.

The modules have each been named for easier identification when talking or writing about them. On the HPSDR website, each module has its own web page. Some of the modules are being designed so that they can be either used in conjunction with others or standalone. Each module board size (except the Atlas backplane) is typically 100mm by 120mm (optionally up to 220mm) and uses either a 64 pin or 96 pin DIN41612 type connector.

Wiki Sysop

Please contact KV0S (the "Wiki Sysop") for information or help. Contact may be made via email: "kv0s" at "openhpsdr" dot "org".

All who wish to edit this Wiki must be authorized by the Sysop. This is done to prevent vandalism of our wiki. To obtain a log in account, please email the Sysop with a request.

Do not submit copyrighted work without permission. All submittals, unless otherwise arranged will be considered in public domain.

Go to the Community Portal for project information

Community Portal