HPSDRwiki - User contributions [en]

HPSDRwiki:Community Portal

2011-02-08T06:18:57Z

AE5K: /* Software */

== [[FAQ]] - Frequently Asked Questions ==

This is a new section started to allow asking and hopefully answering questions about HPSDR.

== Documentation ==

*'''[[DOC]]''' This section contains links for downloading manuals for HPSDR Projects.

*'''[http://openhpsdr.org/support.html Support documentation]''' Build documents for users interested in building boards can be found here.

== Getting Started ==

*'''[[Hardware Introduction]]''' This is a guide for those new to HPSDR about exactly what hardware you need to be able to use the system.

== Software ==

*'''[[SVN]] Subversion code versioning software ''' Source code in the process of development.

*'''[[HPSDR_related_software|Software links and introduction to software components.]] '''

* Links to HPSDR software and resources can be found on the [http://openhpsdr.org/resources.html Resource] page.

*'''[[DOWNLOADS]] - Firmware and Software''' Links to old firmware and software.

* Links to the Verilog/FPGA programming course by Kirk, KD7IRS -- see the [[Verilog]] page.

== Microsoft Windows XP, Vista, and Windows 7 Software ==

*'''[http://www.g3ukb.co.uk/ Acorn-SDR]''' by Bob Cowdery

*'''[http://www.dxatlas.com/CwSkimmer/ CW Skimmer]''' From Alex, VE3NEA, has support for Mercury

*'''[[KISS Konsole]]''', Written in C# and intended as a simple introduction to PC DSP programming.

*'''[https://java-sdr.dev.java.net/ java-sdr]''' Platform independent Java by John G0ORX/N6LYT.

*'''ghpsdr3 [[How to set up on Windows]]''' server & dspserver allow for multiple receivers (jmonitor) on a single Mercury

====PowerSDR====
*'''[[PowerSDR]] Running on Microsoft Windows XP. Vista, or Windows 7'''

*'''PowerSDR [[Quick Startup Guide]]''' Documents to help users get HPSDR setup and working. Includes firmware upload instructions.

*'''[[HPSDR Digital Modes Operation using PowerSDR, Fldigi, VAC and com0com]]''' How to use additional programs to enable the digital modes using PowerSDR

*'''[[HPSDR Weak Signal Digital Modes Operation using PowerSDR with WSPR, WSJT9, JT65HF, VAC and VSP]]''' How to use additional programs to enable the weak signal digital modes using PowerSDR

*'''[[PowerSDR Keyboard Shortcut List ]]''' This page lists all the known PowerSDR keyboard shortcuts.

====USB drivers for Windows====

*'''[[libusb0 Notes]]''' used in Windows 32 and 64 bit systems

*'''[[WinUSB Notes]]''' used on Windows 32 and 64 bit systems

== Linux Software ==

*'''[[ghpsdr]]''', written in C with a [http://www.gtk.org/ GTK+] GUI by John G0ORX/N6LYT. http://javaguifordttsp.blogspot.com/

*'''[[ghpsdr3]]''', written in C with as a server/client or server/dspserver/client framework by John G0ORX/N6LYT. http://g0orx.blogspot.com/

*'''[https://java-sdr.dev.java.net/ java-sdr]''' Platform independent Java by John G0ORX/N6LYT.

====Linux USB Drivers====

*'''[[libusb1.0 Notes]]''' used in Linux 32 and 64 bit systems

====Linux System Integration====

*'''[[SYSTEM INTEGRATION]]''' This section contains information relative to "putting the pieces together".

== Mac OS-X Software ==

*'''[[ghpsdr]]''', written in C with a [http://www.gtk.org/ GTK+] GUI by John G0ORX/N6LYT. http://javaguifordttsp.blogspot.com/

*'''[[Mac-Ghpsdr]]''' is a version of ghpsdr v2 with changes to make it run acceptably on the Mac by Jeremy McDermond ([[User:NH6Z|NH6Z]]).

*'''[[MacHPSDR]]''' is a native Cocoa implementation of an HPSDR receiver. It uses currently John Melton's modified DttSP from ghpsdr to do the DSP work, but replaces out everything else with native Objective-C and Cocoa technologies. The current author and maintainer of the code is Jeremy McDermond ([[User:NH6Z|NH6Z]]).

*'''[https://java-sdr.dev.java.net/ java-sdr]''' Platform independent Java by John G0ORX/N6LYT.

==Cross Platform issues==

*'''[[USB Libraries]]''' Information of the various USB libraries used to access the [[OZY]] and [[MAGISTER]] interface boards.

==Multi-Receivers==

*'''[[Multi-Receiver]] How-to''' - This page explains the multi-receiver options and how-to set them up.

== Software Projects ==

* '''[[ATHENA]] - A software Server module''' - A project to build OS specific server code, module communication libraries and communication protocol documentation.

* '''[[KISS Konsole]] - Learning SDR Console''' - The KISS Konsole is a software project to provide a straightforward, well-commented User Interface to [[Mercury]] and other modules.

== HPSDR Radio Setup Examples ==

*'''[[A Basic HPSDR Transceiver in PANDORA]]''' provides another example of how a [[PANDORA|Pandora]] enclosure can be used for the amateur radio experimenter.

*'''[[A complete HPSDR transceiver in a Pandora Box]]''' provides an example of how to build a transceiver using HPSDR components in a [[PANDORA|Pandora]] enclosure, other available hardware and PowerSDR.

*'''[[A complete HPSDR transceiver]]''' provides an example of how to build your own transceiver using HPSDR components and other available hardware and software.

*'''[[The Antec P183 Solution]]''' an example of how to build your own transceiver using HPSDR components and other available hardware and software in a traditional a mid-tower PC enclosure.

*'''[[The Tokyo Hy-Power HL-45B Solution]]''' an example of how to add a commercial solid state 45 Watt Amplifier to your HPSDR rig.

*'''[[The Rino R-1 Solution]]''' a smaller PC case solution with an optical drive included.

*'''[[The Antec Minuet Solution]]''' the smallest PC case solution attempted so far.

==Hardware Configuration Cautions==

*'''[[Never Short a Penelope by AD9DP]]''' This short paper tells you why you should never operate Penelope into a shorted load.

*'''[[Using Penelope with a linear amplifier]]''' When using Penelope with a linear amplifier you need to ensure you use enough drive. This paper explains why.

== HPSDR Performance Tests ==

The purpose of these pages are to establish HPSDR performance measurement process standards.

==== Receiver Performance Tests ====
* Mercury: [[Receiver Performance Tests]]
* Active Antennas and HPSDR: [[Antenna Performance Tests]]

==== Transmitter Performance Tests ====

== Hardware Projects ==

=== Completed ===

==== Common ====

* '''[[ATLAS]] - Backplane''' - The Atlas is a passive backplane that all other modules plug into.

* '''[[LPU]] - Simple Linear Power Unit''' - The LPU unit takes power from a regulated power supply and steps it to the input needed by Atlas.

* '''[[METIS]] - (formerly called OzyII) - A high speed PC interface''' - High speed PC interface using Ethernet PHY.

==== Primarily Mercury and Penelope related ====

* '''[[Antenna Switch|ANTENNA SWITCH]] - by NT-Electronics''' - An antenna switch for use with Penelope and Mercury when Alex is not used, also has optional low Noise RX Amplifier for 6 meters

==== Primarily Phoenix and Janus related ====

* '''[[JANUS]] - ADC/DAC Board''' - The Janus module is a very high performance, dual, full duplex, A/D and D/A converter board.

==== Optional ====

* '''[[PANDORA]] - Enclosure''' - HPSDR enclosure.

* '''[[EXCALIBUR]] - Clock Reference board''' - A board to allow an external 10 MHz frequency reference interface.

* '''[[PINOCCHIO]] - Extender Card''' - Pinocchio is an extender card to allow measurements and troubleshooting of an active card in an ATLAS back-plane.

* '''[[HERCULES]] - By NT-Electronics''' - A 100 Watt amplifier designed to be compatible with current HPSDR hardware (Atlas, Penelope, Mercury, and Magister/Ozy).

* '''[[PENNYWHISTLE]] - 20 Watt RF Power Ampilfier''' - The PennyWhistle takes the RF output of Penelope and amplifies it to approximately 20 watts.

===Completed but unavailable===

* '''[[OZY]] - HPSDR Host Interface & Control''' - The OZY module is an FPGA based interface controller card providing input and output connections to the real world. Now replaced with the Magister module - see above.

* '''[[MAGISTER]] - USB 2.0 to Atlas Bus Interface''' - The Magister module is an alternative to OZY.

* '''[[MERCURY]] - 0-55 MHz Direct Sampling Receiver''' - Perhaps the most exciting of all modules, Mercury will enable direct sampling of the 0-55 MHz spectrum.

* '''[[PENELOPE]] - Companion Exciter to Mercury''' - A 1/2 watt DUC(k).

===Future hardware===
====Hardware nearing completion====

* '''[[ALEXIARES]] - RF Preselector''' - Alexiares (or Alex for short) is a set of RF Bandpass filters for use with Mercury and Penelope or any other SDR. Alex also contain an RX/TX antenna switch.

* '''[[HERMES]] - A DUC/DDC Transceiver''' - Merging the verilog code of Mercury and Penelope into a single FPGA, on a single board.

* '''[[APOLLO]] - 15W PA and Filter''' - A companion 15W PA and Low Pass Filter for [[HERMES|Hermes]].

* '''[[PHOENIX]] - QSD/QSE Receiver/Transmitter Module''' - QSD based HF Receiver, a QSE based HF Exciter and a supporting synthesizer.

====Proposed hardware====

* '''[[CYCLOPS]] - Spectrum Analyzer''' - Cyclops is a 0-1 GHz spectrum analyzer with tracking generator support.

* '''[[DEMETER]] - Power Supply''' - Power supply designed for HPSDR.

* '''[[GIBRALTAR]] - GPS-disciplined Frequency Standard''' - Gibraltar is a GPS-disciplined frequency standard board.

* '''[[ODYSSEY]] - Low Power Handheld SDR''' - Odyssey includes a low power SDR based on the QSD, QSE, and a dsPIC33 as the basic radio core.

* '''[[THOR]] - High Efficiency HF Power Amplifier''' - Thor is a high efficiency HF power amplifier using Envelope Elimination and Restoration (ERR) techniques.

* '''[[MUNIN]] - 100W HF Power Amplifier''' - Munin is a 100W HF power amplifier, This hardware is dependent on Alex filters.

* '''[[PENNYLANE]] - Two stage Penelope''' - This is a two stage penelope based on changes made in the Hermes boards.

* '''[[GRIFFIN]] - A Chirp-WSPR beacon board''' - This board is a stand alone beacon board.

====Other proposed/future hardware====

* '''[[ANICETUS]] (Anie) - Preselector''' - A few designs for narrow band preselectors.

* '''[[EPIMETHEUS]] - General Purpose I/O''' - Epi is a general purpose I/O board for the Atlas bus and includes relays, open collectors, IF switching, etc.

* '''[[HELIOS]] - Helios Small Transmitting Loop Antenna and Controller.

* '''[[HORTON]] - Receiver Module''' - A receiver module integrating the Janus ADC with a QSD on a board for a version of the HPSDR RX board.

* '''[[PROTEUS]] - Prototyping Board''' - This is the planned prototyping board.

* '''[[SASQUATCH]] - DSP back-end''' - The Sasquatch board is a hardware DSP back-end intended for use by constructors who would like to operate stand-alone rather than attached to a PC.

== [[Board Designer's Resources]] ==

== [[ANCILLARY]] - Additional "stuff" of interest to HPSDR ==
Some stuff like Norton Amplifier, FPGA VHDL/Verilog ...

== [[EXPERIMENTERS-CORNER]] - Ideas not yet projects ==

== [[ADMINISTRATION-NEWS]] - Messages about HPSDR web, wiki, discussion list ==
__NOTOC__

[[Category:Community| ]]
[[Category:Hardware| ]]
[[Category:Categories]]
[[Category:Developer resources| ]]

ANCILLARY

2011-02-08T06:16:22Z

AE5K: /* Verilog Resources */ added KD7IRS Kirk's link

== Architecture and Component Selection for SDR Applications ==

This is a "white paper" from Altera which may be of interest:
http://www.altera.com/literature/wp/wp-01026.pdf

== FPGA Programming: [[Verilog]] & VHDL ==

''' Which is best? Verilog or VHDL?'''

The question was asked recently on our HPSDR Discussion List about Verilog versus VHDL and which was more user friendly. In response to this query, Rick Eversole, N6RNO, gave this reply:

(Reprinted here by permission of the author)

Yet another answer from one who has used both languages for 17 years. I have worked for Cadence, Mentor Graphics and now Synopsys. I get paid to know both languages. I have written thousands of lines of
code in both. I know 29 programming languages (including Verilog and VHDL). I prefer Verilog and in recent years it appears that VHDL is finally falling behind.

While Verilog is being upgraded to "SystemVerilog", the VHDL camp is finding it hard to find funding to
update the latest LRM. "SystemVHDL" may not actually be needed but as it stands now I do not think it will ever happen.

Verilog is C-like (Prahbu Goel and Phil Morby [creators of the language] liked C). Not strongly typed. Subject to coded race conditions. But fastest to learn and tuned toward hardware better than VHDL. Verilog simulates faster than VHDL. Verilog has gate level primitives (AND, NAND, NOR etc) as part of the language. A useful value type system is part of base Verilog.

VHDL is based upon ADA (Many of the same people who specified the ADA language were involved in the creation of VHDL). It is a strongly typed language. It is very hard to code a race condition. It takes longer to learn. More typing is involved to accomplish the same task in VHDL as compared to Verilog. VHDL simulates slower than Verilog (2-4x slower is typical even for gate level simulations). VHDL does not have gate primitives. You have to code them in RTL style.

The "VITAL" specification provides a set of gate primitves that map to Verilog primitives. VHDL does not have a logic system that is useful for gate designs. You need the "standard logic 1164" package which ships with any real VHDL simulator. Like Vital this is a layer on top of the base language.

Over the years I have seen side by side test with "expert" VHDL users and Verilog users. In general the
Verilog users out perform the VHDL users. There are lots of issues with how these tests are constructed
but my experience shows that Verilog is fasest to get the design done but VHDL designs often are easier
to maintain and update.

Each language has advantages. The new SystemVerilog language will remove all but VHDL's strong typed
"advantage". Whether strongly typed is a real advantage is a debate for another time.

In practice, it is not possible to translate between the languages. Semantics are incompatible. You have to completely recode in a non-mechanical process. Translators can help but 30% recode is not uncommon.
(unless you have pure structural code then translation can be almost 100%).

--Rick "The Rhino" N6RNO

=== Verilog Resources ===

Example Verilog Code from Phil Covington N8VB: http://www.philcovington.com/FPGA/

Example Verilog Code from Bill Tracey KD5TFD: http://www.tracey.org/wjt/sdr1k/Xylo/9850Control.zip

Online lectures and course given by Kirk Weedman KD7IRS: http://openhpsdr.org/wiki/index.php?title=Verilog

Verilog Tutorials and Resources: 
http://www.see.ed.ac.uk/~gerard/Teach/Verilog/ 
http://www.asic-world.com/verilog/veritut.html 
http://www.ece.cmu.edu/~thomas/VSLIDES.pdf 
http://www.web-ee.com/primers/files/VlogIntro.pdf 
http://www.doulos.com/knowhow/verilog_designers_guide/ 
http://www.sutherland-hdl.com/on-line_ref_guide/vlog_ref_top.html 
http://www.eecs.harvard.edu/cs141/resources/verilog-tutorial.pdf 
http://www.doe.carleton.ca/~shams/97350/PetervrlK.pdf 
http://www.veripool.com/ 
http://www.verilog.com/VerilogBNF.html 

=== VHDL Resources ===

=== FPGA Resources ===

http://www.opencores.org/ 

== Surface Mount ==

=== Microscopes ===

Although a microscope may not be needed for most surface mount soldering, it comes in most useful when attempting to solder the very fine pitched IC parts.

Bill, KD5TFD, advises this is the scope he's been using for the past year or so:
http://www.bargainmicroscopes.com/10x-stereo-boom-arm-mounted-binocular-microscope/
-- got both 5x and 10x optics for it. The light that came with it was inadequate -- so use a goose neck desk lamp for illumination when working with it. He's been happy with it -- this $200 scope has made him fearless on working with surface mount stuff! 200+ pins at 1/2 mm spacing -- no problem!

Al, N0TVJ, says that he's been using one from the "The Microscope Store" http://www.microscope-store.com
The model he bought is a Stereo Boom Trinocular Microscope (OM2040TJW11) priced at $595.00 + $5 shipping at that time. He bought the Trinocular version in order to allow a video camera to be attached for a larger field of view while soldering or positioning parts on the solder mask prior to heating them. The view on a 21 inch flat screen can't be beat. The Microscope came with 20x-40x lenses which is too much magnification, so he bought some 5X and 10X which work much better for SMT work. He bought a natural light ring from a local model / craft store which fits right on the bottom of the Scope and works very well to light up every thing.

=== Soldering Hints ===

Al, N0TVJ found a set of test tweezers from MCM which allow you to pickup the SMT passive parts and verify the value before placing it very helpful. Of course you also need whatever soldering station you prefer. He uses a Hot Air rework station by Circuit Specialists together with a standard soldering iron most of time. If the board is one with a solder mask, he sometimes use Cash Olson's method.

=== Solder Paste ===

Cash Olson, KD5SSJ, has small syringes of solder paste available. http://www.kd5ssj.com/index.php?option=com_content&view=article&id=120&Itemid=54

== MISCELLANEOUS STUFF ==

'''Good Reading Link'''

GNU Radio has a nice page with a lot of good reference reading information on it. http://gnuradio.org/trac/wiki/SuggestedReading

'''Power Supply'''

Here's a link to one possible VERY SMALL power supply for the Atlas backplane: http://www.mini-box.com/s.nl/it.A/id.417/.f?sc=8&category=13

Please note that extensive testing has not been performed yet on this unit and as of this writing it is not in stock. The HPSDR group does not necessarily recommend this particular supply at this time.

'''HF Power Amplifiers'''

HFPROJECTS.com, operated by Virgil K5OOR, offers some interesting kits which might be suitable for HPSDR project transmitting when Phoenix or Penelope becomes available, or for other transmitters. The link is http://www.hfprojects.com/newsletter.htm
Two current offerings are a "pre-amp" (PA-100) for boosting a HF signal from the 100 mw range to the 5 watt or greater region, to be able to drive the SUPERPACKER PRO solid state amplifier -- a 100 watt continuous duty beast! Be aware that this is NOT an open source project, and
the one submitting this information has some serious reservations about the operation of the amplifier and the project.

'''A Novel Grounded Base Oscillator Design for VHF/UHF Frequencies'''

This is a PDF file submitted by Ulrich Rohde, N1UL, which can be downloaded (about 3 MBytes) from
http://openhpsdr.org/downloads/GBPhaseNoiseAnalysis4-20-07.pdf

== MODIFIED NORTON AMP ==

Submitted by Ulrich Rohde, N1UL:

This simulation using the Infineon BFP490 agrees with my test-circuit within about 0.2dB. Depending on the transformer, (2+2)/2, inductance, this works from 1 MHZ to 1 GHz max. The IP3 of about 38 dBm is excellent, the NF about 2dB. The reverse isolation can be more then 60dB, and a push-pull version has reduced IP2.

Click on the "media" link below each drawing if you want a PDF file with slightly higher resolution.

[[Image:Norton 2stage amp.jpg]] [[media:Norton 2stage amp2.pdf]]

[[Image:Norton 2tone test.jpg]] [[media:Norton 2Tone test2.pdf]]

[[Image:Norton sweep.jpg]] [[media:Norton Sweep2.pdf]]

[[Category:Developer resources]]

Board Designer's Resources

2010-04-12T03:04:42Z

AE5K: Added link and info on HPSDR logo

This page will provide links to parts used in deployed designs, such as [[JANUS|Janus]] and [[OZY|Ozy]]. The part information will include manufacturer (such as Texas Instruments) and at least one vendor source (such as Mouser or Digikey). It will also include schematic symbol and PCB footprint libraries for OrCAD and PADS as these are developed.

This page will also provide guidelines for PCB layout (such as necessary clearance for hardware at DIN connector mounting holes), trace minimum widths and apce minimum clearance for keeping PCB costs down, guidelines for PCB footprint creation, and so forth.

The intent is to make it easier for developers to be consistent across teams and projects, and to re-use parts where practical to keep manufacturing costs down for TAPR, which keeps the price down for all of us. -- de KK7P

'''Prototype PCB Suppliers: '''

I have used Protoexpress' "No Touch" service for more than 20 years. Never had a bad board. They are the lowest cost 4-layer prototypes I have found. Many Amateur and some commercial spacecraft in which I have designs are flying these same "No Touch" prototype boards, some since 1993. http://www.protoexpress.com -- de KK7P

[[Category:Developer resources]]

== HPSDR LOGO ==

There are several versions (file types) of the HPSDR Logo to be found at
http://openhpsdr.org/logo/

Note that the logo is copyrighted and has been used as a trademark for quite some time. The copyright, held by designer AE5K, has been licensed for use by OpenHPSDR.org.
If you wish to use the logo on a board or for display (such as a hamfest display), please try to use the artwork provided in order to maintain consistency.

ADMINISTRATION-NEWS

2009-11-29T01:24:44Z

AE5K: /* Some Old Stuff */

This page will be used for any current announcements regarding our HPSDR website http://openhpsdr.org/, this HPSDR Wiki, or the HPSDR Discussion List.

==HPSDR.ORG and OPENHPSDR.ORG==

The domain name "hpsdr.org" is no longer available to our group, so we've obtained "openhpsdr.org" to use for our internet activities.

==Got Unsubscribed?==

If you suddenly find yourself unsubscribed from the HPSDR Discussion List (reflector), chances are the email messages to your subscription address have been bouncing. Most often (if your subscription address is still current), it is due to your internet service provider (ISP) attempting to protect you from perceived spam. The worst ones are usually the largest ones (see notes about Comcast below).

In the case of our discussion list, the messages are sent out on one of our host's servers. There may be 10,000 other senders using this same server, and all it takes is just one to either send actual spam or have one of the big ISPs think it is spam -- and POW! the ISP puts this server on its black list. Once this is done, the ISP rejects email to YOUR address if it comes from this server.

The solution is not to fight a losing battle with the ISP, but to use an alternate emailbox such as gmail.com. If you insist on looking in your ISP emailbox only, the email from gmail.com can be automatically forwarded to it...of course, unless it too is blocked by your ISP.

==HAPPY BIRTHDAY HPSDR.ORG==

March 1, 2009 - It was three years ago today that we began our website and discussion list (reflector). Today, on our third anniversary of the domain, our reflector has over 900 subscribers! I'd like to remind all that if anyone is needing help in posting messages or subscribing to the list, your list administrator is available to help. All queries are normally answered within 24 hours, so check your spam folder if you don't find a reply within that period of time.

== Some Old Stuff ==

'''I DIDN'T DO IT! - Comcast Again'''

December 25, 2006 - Seems this past week that our Mailman software program which runs our HPSDR Discussion List has thrown in the towel and given up on those with comcast.net email addresses. Apparently after so many attempts and being disabled so many times, Mailman unsubscribes the offending address(es) automatically. Again, I would urge those with comcast.com addresses to get a free gmail or similar email account to either receive discussion list messages directly or to configure so that it forwards them to the comcast address. That should make everyone happy again! Sorry about the problems, but it is out of our hands.

November 9, 2006 - Comcast has been blocking once again and those with comcast.net email addresses are no longer receiving discussion list email delivery.

October 17, 2006 - On again, off again. Comcast removed the blockade last week once again. As of this date, it appears all is well. Remaining information is being left on this page for historical reasons and to serve as backgrounder if Comcast decides to block our HPSDR Discussion List email from reaching their customers once again.

September 30, 2006 - Comcast is "at it again" -- as of this morning, I believe all our list members with comcast.net email addresses have been BLOCKED BY COMCAST from receiving HPSDR discussion list email. Here is the "diagnostic message" we are receiving from Comcast:

host gateway-s.comcast.net[204.127.202.26] said:
550 66.33.206.23 blocked by ldap:ou=rblmx,dc=comcast,dc=net -> BL003
Blocked for spam. Please see
http://www.comcast.net/help/faq/index.jsp?faq=SecurityMail_Policy18627

September 14, 2006 - A spot check on several comcast.net subscriber records indicates no blacklisting our discussion list traffic for at least a week now. It appears all back to normal.

Sept. 11, 2006 -- About a week ago, Comcast apparently took our discussion list mail server off the blacklist (at least temporarily) and I restored delivery of HPSDR discussion list email to all those with comcast.net addresses.

Previous posting on this problem is left here for now:

As our subscribers to the discussion list who have "comcast.net" email addresses know by now, Comcast is currently blocking (rejecting) our discussion list email to comcast.net addresses. You can find out about Comcast's sea of upset customers by Googling "comcast blacklist". I'm also reproducing below part of a communication from our hosting provider "Dreamhost" (for the discussion list).

From Dreamhost:

Comcast blocks are atypical from the others that we?ve been having problems
with in that they last indefinitely until unblocked manually. Unlike AOL
blocks (which phase out automatically after 24 hours - though may reappear)
someone has to flip a switch over there for any future mail to go through.
The unfortunate part is that they have zero human availability and all we
get from their blacklist email address are auto-responses ? either the IP
is automatically unblocked, or the unblock is denied and the phone number
of their abuse/security department is given. Unfortunately, this phone
number is a completely unmanned voicemail drop-box. We?ve left no less
than six messages on their voicemail in the last couple months, and despite
numerous requests we have never received a phone call back or an email
response. We?re not even asking that they remove the blacklist ? we?re
simply asking for more information on why the IPs were blocked, and for a
sampling of the typical spam they are supposedly getting from us! In fact,
the only response we can get from them (if we get one at all) is an
automated form message saying that ?most of the email? received from our
IPs is spam, which we know, in fact, is false.

ADMINISTRATION-NEWS

2009-11-29T01:21:51Z

AE5K: /* HAPPY BIRTHDAY HPSDR.ORG */

This page will be used for any current announcements regarding our HPSDR website http://openhpsdr.org/, this HPSDR Wiki, or the HPSDR Discussion List.

==HPSDR.ORG and OPENHPSDR.ORG==

The domain name "hpsdr.org" is no longer available to our group, so we've obtained "openhpsdr.org" to use for our internet activities.

==Got Unsubscribed?==

If you suddenly find yourself unsubscribed from the HPSDR Discussion List (reflector), chances are the email messages to your subscription address have been bouncing. Most often (if your subscription address is still current), it is due to your internet service provider (ISP) attempting to protect you from perceived spam. The worst ones are usually the largest ones (see notes about Comcast below).

In the case of our discussion list, the messages are sent out on one of our host's servers. There may be 10,000 other senders using this same server, and all it takes is just one to either send actual spam or have one of the big ISPs think it is spam -- and POW! the ISP puts this server on its black list. Once this is done, the ISP rejects email to YOUR address if it comes from this server.

The solution is not to fight a losing battle with the ISP, but to use an alternate emailbox such as gmail.com. If you insist on looking in your ISP emailbox only, the email from gmail.com can be automatically forwarded to it...of course, unless it too is blocked by your ISP.

==HAPPY BIRTHDAY HPSDR.ORG==

March 1, 2009 - It was three years ago today that we began our website and discussion list (reflector). Today, on our third anniversary of the domain, our reflector has over 900 subscribers! I'd like to remind all that if anyone is needing help in posting messages or subscribing to the list, your list administrator is available to help. All queries are normally answered within 24 hours, so check your spam folder if you don't find a reply within that period of time.

== Some Old Stuff ==

'''I DIDN'T DO IT! - Comcast Again'''

December 25, 2006 - Seems this past week that our Mailman software program which runs our HPSDR Discussion List has thrown in the towel and given up on those with comcast.net email addresses. Apparently after so many attempts and being disabled so many times, Mailman unsubscribes the offending address(es) automatically. Again, I would urge those with comcast.com addresses to get a free gmail or similar email account to either receive discussion list messages directly or to configure so that it forwards them to the comcast address. That should make everyone happy again! Email me directly if you need a "gmail invite". Sorry about the problems, but it is out of my hands. -- AE5K.

'''COMCAST UPDATE'''

November 9, 2006 - Comcast has been blocking once again and those with comcast.net email addresses are no longer receiving discussion list email delivery.

October 17 - On again, off again. Comcast removed the blockade last week once again. As of this date, it appears all is well. Remaining information is being left on this page for historical reasons and to serve as backgrounder if Comcast decides to block our HPSDR Discussion List email from reaching their customers once again.

September 30 - Comcast is "at it again" -- as of this morning, I believe all our list members with comcast.net email addresses have been BLOCKED BY COMCAST from receiving HPSDR discussion list email. Here is the "diagnostic message" we are receiving from Comcast:

host gateway-s.comcast.net[204.127.202.26] said:
550 66.33.206.23 blocked by ldap:ou=rblmx,dc=comcast,dc=net -> BL003
Blocked for spam. Please see
http://www.comcast.net/help/faq/index.jsp?faq=SecurityMail_Policy18627

September 14 - A spot check on several comcast.net subscriber records indicates no blacklisting our discussion list traffic for at least a week now. It appears all back to normal.

Sept. 11 -- About a week ago, Comcast apparently took our discussion list mail server off the blacklist (at least temporarily) and I restored delivery of HPSDR discussion list email to all those with comcast.net addresses.

Previous posting on this problem is left here for now:

As our subscribers to the discussion list who have "comcast.net" email addresses know by now, Comcast is currently blocking (rejecting) our discussion list email to comcast.net addresses. You can find out about Comcast's sea of upset customers by Googling "comcast blacklist". I'm also reproducing below part of a communication from our hosting provider "Dreamhost" (for the discussion list).

From Dreamhost:

Comcast blocks are atypical from the others that we?ve been having problems
with in that they last indefinitely until unblocked manually. Unlike AOL
blocks (which phase out automatically after 24 hours - though may reappear)
someone has to flip a switch over there for any future mail to go through.
The unfortunate part is that they have zero human availability and all we
get from their blacklist email address are auto-responses ? either the IP
is automatically unblocked, or the unblock is denied and the phone number
of their abuse/security department is given. Unfortunately, this phone
number is a completely unmanned voicemail drop-box. We?ve left no less
than six messages on their voicemail in the last couple months, and despite
numerous requests we have never received a phone call back or an email
response. We?re not even asking that they remove the blacklist ? we?re
simply asking for more information on why the IPs were blocked, and for a
sampling of the typical spam they are supposedly getting from us! In fact,
the only response we can get from them (if we get one at all) is an
automated form message saying that ?most of the email? received from our
IPs is spam, which we know, in fact, is false.

ADMINISTRATION-NEWS

2009-11-29T01:19:07Z

AE5K:

This page will be used for any current announcements regarding our HPSDR website http://openhpsdr.org/, this HPSDR Wiki, or the HPSDR Discussion List.

==HPSDR.ORG and OPENHPSDR.ORG==

The domain name "hpsdr.org" is no longer available to our group, so we've obtained "openhpsdr.org" to use for our internet activities.

==Got Unsubscribed?==

If you suddenly find yourself unsubscribed from the HPSDR Discussion List (reflector), chances are the email messages to your subscription address have been bouncing. Most often (if your subscription address is still current), it is due to your internet service provider (ISP) attempting to protect you from perceived spam. The worst ones are usually the largest ones (see notes about Comcast below).

In the case of our discussion list, the messages are sent out on one of our host's servers. There may be 10,000 other senders using this same server, and all it takes is just one to either send actual spam or have one of the big ISPs think it is spam -- and POW! the ISP puts this server on its black list. Once this is done, the ISP rejects email to YOUR address if it comes from this server.

The solution is not to fight a losing battle with the ISP, but to use an alternate emailbox such as gmail.com. If you insist on looking in your ISP emailbox only, the email from gmail.com can be automatically forwarded to it...of course, unless it too is blocked by your ISP.

==HAPPY BIRTHDAY HPSDR.ORG==

March 1, 2009 - It was three years ago today that we began the website domain hpsdr.org and our discussion list (reflector). Today, on our third anniversary of the domain, our reflector has over 900 subscribers! I'd like to remind all that if anyone is needing help in posting messages or subscribing to the list, your list administrator is available to help. All queries are normally answered within 24 hours, so check your spam folder if you don't find a reply within that period of time.

== Some Old Stuff ==

'''I DIDN'T DO IT! - Comcast Again'''

December 25, 2006 - Seems this past week that our Mailman software program which runs our HPSDR Discussion List has thrown in the towel and given up on those with comcast.net email addresses. Apparently after so many attempts and being disabled so many times, Mailman unsubscribes the offending address(es) automatically. Again, I would urge those with comcast.com addresses to get a free gmail or similar email account to either receive discussion list messages directly or to configure so that it forwards them to the comcast address. That should make everyone happy again! Email me directly if you need a "gmail invite". Sorry about the problems, but it is out of my hands. -- AE5K.

'''COMCAST UPDATE'''

November 9, 2006 - Comcast has been blocking once again and those with comcast.net email addresses are no longer receiving discussion list email delivery.

October 17 - On again, off again. Comcast removed the blockade last week once again. As of this date, it appears all is well. Remaining information is being left on this page for historical reasons and to serve as backgrounder if Comcast decides to block our HPSDR Discussion List email from reaching their customers once again.

September 30 - Comcast is "at it again" -- as of this morning, I believe all our list members with comcast.net email addresses have been BLOCKED BY COMCAST from receiving HPSDR discussion list email. Here is the "diagnostic message" we are receiving from Comcast:

host gateway-s.comcast.net[204.127.202.26] said:
550 66.33.206.23 blocked by ldap:ou=rblmx,dc=comcast,dc=net -> BL003
Blocked for spam. Please see
http://www.comcast.net/help/faq/index.jsp?faq=SecurityMail_Policy18627

September 14 - A spot check on several comcast.net subscriber records indicates no blacklisting our discussion list traffic for at least a week now. It appears all back to normal.

Sept. 11 -- About a week ago, Comcast apparently took our discussion list mail server off the blacklist (at least temporarily) and I restored delivery of HPSDR discussion list email to all those with comcast.net addresses.

Previous posting on this problem is left here for now:

As our subscribers to the discussion list who have "comcast.net" email addresses know by now, Comcast is currently blocking (rejecting) our discussion list email to comcast.net addresses. You can find out about Comcast's sea of upset customers by Googling "comcast blacklist". I'm also reproducing below part of a communication from our hosting provider "Dreamhost" (for the discussion list).

From Dreamhost:

Comcast blocks are atypical from the others that we?ve been having problems
with in that they last indefinitely until unblocked manually. Unlike AOL
blocks (which phase out automatically after 24 hours - though may reappear)
someone has to flip a switch over there for any future mail to go through.
The unfortunate part is that they have zero human availability and all we
get from their blacklist email address are auto-responses ? either the IP
is automatically unblocked, or the unblock is denied and the phone number
of their abuse/security department is given. Unfortunately, this phone
number is a completely unmanned voicemail drop-box. We?ve left no less
than six messages on their voicemail in the last couple months, and despite
numerous requests we have never received a phone call back or an email
response. We?re not even asking that they remove the blacklist ? we?re
simply asking for more information on why the IPs were blocked, and for a
sampling of the typical spam they are supposedly getting from us! In fact,
the only response we can get from them (if we get one at all) is an
automated form message saying that ?most of the email? received from our
IPs is spam, which we know, in fact, is false.

ADMINISTRATION-NEWS

2009-11-29T01:18:08Z

AE5K: Updated domain name changeover info.

This page will be used for any current announcements regarding our HPSDR website http://hpsdr.info/, this HPSDR Wiki, or the HPSDR Discussion List.

==HPSDR.ORG and OPENHPSDR.ORG==

The domain name "hpsdr.org" is no longer available to our group, so we've obtained "openhpsdr.org" to use for our internet activities.

==Got Unsubscribed?==

If you suddenly find yourself unsubscribed from the HPSDR Discussion List (reflector), chances are the email messages to your subscription address have been bouncing. Most often (if your subscription address is still current), it is due to your internet service provider (ISP) attempting to protect you from perceived spam. The worst ones are usually the largest ones (see notes about Comcast below).

In the case of our discussion list, the messages are sent out on one of our host's servers. There may be 10,000 other senders using this same server, and all it takes is just one to either send actual spam or have one of the big ISPs think it is spam -- and POW! the ISP puts this server on its black list. Once this is done, the ISP rejects email to YOUR address if it comes from this server.

The solution is not to fight a losing battle with the ISP, but to use an alternate emailbox such as gmail.com. If you insist on looking in your ISP emailbox only, the email from gmail.com can be automatically forwarded to it...of course, unless it too is blocked by your ISP.

==HAPPY BIRTHDAY HPSDR.ORG==

March 1, 2009 - It was three years ago today that we began the website domain hpsdr.org and our discussion list (reflector). Today, on our third anniversary of the domain, our reflector has over 900 subscribers! I'd like to remind all that if anyone is needing help in posting messages or subscribing to the list, your list administrator is available to help. All queries are normally answered within 24 hours, so check your spam folder if you don't find a reply within that period of time.

== Some Old Stuff ==

'''I DIDN'T DO IT! - Comcast Again'''

December 25, 2006 - Seems this past week that our Mailman software program which runs our HPSDR Discussion List has thrown in the towel and given up on those with comcast.net email addresses. Apparently after so many attempts and being disabled so many times, Mailman unsubscribes the offending address(es) automatically. Again, I would urge those with comcast.com addresses to get a free gmail or similar email account to either receive discussion list messages directly or to configure so that it forwards them to the comcast address. That should make everyone happy again! Email me directly if you need a "gmail invite". Sorry about the problems, but it is out of my hands. -- AE5K.

'''COMCAST UPDATE'''

November 9, 2006 - Comcast has been blocking once again and those with comcast.net email addresses are no longer receiving discussion list email delivery.

October 17 - On again, off again. Comcast removed the blockade last week once again. As of this date, it appears all is well. Remaining information is being left on this page for historical reasons and to serve as backgrounder if Comcast decides to block our HPSDR Discussion List email from reaching their customers once again.

September 30 - Comcast is "at it again" -- as of this morning, I believe all our list members with comcast.net email addresses have been BLOCKED BY COMCAST from receiving HPSDR discussion list email. Here is the "diagnostic message" we are receiving from Comcast:

host gateway-s.comcast.net[204.127.202.26] said:
550 66.33.206.23 blocked by ldap:ou=rblmx,dc=comcast,dc=net -> BL003
Blocked for spam. Please see
http://www.comcast.net/help/faq/index.jsp?faq=SecurityMail_Policy18627

September 14 - A spot check on several comcast.net subscriber records indicates no blacklisting our discussion list traffic for at least a week now. It appears all back to normal.

Sept. 11 -- About a week ago, Comcast apparently took our discussion list mail server off the blacklist (at least temporarily) and I restored delivery of HPSDR discussion list email to all those with comcast.net addresses.

Previous posting on this problem is left here for now:

As our subscribers to the discussion list who have "comcast.net" email addresses know by now, Comcast is currently blocking (rejecting) our discussion list email to comcast.net addresses. You can find out about Comcast's sea of upset customers by Googling "comcast blacklist". I'm also reproducing below part of a communication from our hosting provider "Dreamhost" (for the discussion list).

From Dreamhost:

Comcast blocks are atypical from the others that we?ve been having problems
with in that they last indefinitely until unblocked manually. Unlike AOL
blocks (which phase out automatically after 24 hours - though may reappear)
someone has to flip a switch over there for any future mail to go through.
The unfortunate part is that they have zero human availability and all we
get from their blacklist email address are auto-responses ? either the IP
is automatically unblocked, or the unblock is denied and the phone number
of their abuse/security department is given. Unfortunately, this phone
number is a completely unmanned voicemail drop-box. We?ve left no less
than six messages on their voicemail in the last couple months, and despite
numerous requests we have never received a phone call back or an email
response. We?re not even asking that they remove the blacklist ? we?re
simply asking for more information on why the IPs were blocked, and for a
sampling of the typical spam they are supposedly getting from us! In fact,
the only response we can get from them (if we get one at all) is an
automated form message saying that ?most of the email? received from our
IPs is spam, which we know, in fact, is false.

Altera Cyclone FPGA

2009-05-03T12:43:59Z

AE5K: /* Soldering */

The '''[http://en.wikipedia.org/wiki/Altera Altera] Cyclone II FPGA''' is used in the HPSDR [[OZY|Ozy]], and [[PENELOPE|Penelope]] boards. The Altera Cyclone III FPGA is used in the [[MERCURY|Mercury]] board. Details on the devices are available at the [http://www.altera.com/products/devices/dev-index.jsp Altera site.].

== Soldering ==

Gerd Loch [http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/2009-May/009340.html contributed] the following advice:

<blockquote>"The device is mounted and bonded to a small pcb made of glass reinforced
epoxy which is also used for "normal" pcb's. This material is hygroscopic
and incorporates humidity from the ambient air.
During reflow soldering the incorporated humidity explodes and leads to
delamination of the carrier pcb and to discontinuities in traces and vias.
This effect is called "popcorn effect"
It is not so critical if you solder the device manually pin after pin and
not heating the complete device in a short time up to 250°C.
However you should keep the devices in the aluminized foil which contains
some drying material until you are going to solder the device to your board.
You will also find a humidity indicator in the foil which indicates if the
content of the package has seen too much humidity. If the indicator is still
blue you have not exceeded the acceptable level of humidity. If the
indicator shows a red colour you should bake the device at 120-130°C for 48
hours before reflow soldering."</blockquote>

LPU

2009-04-30T23:42:48Z

AE5K: /* Linear Power Unit (LPU) - HPSDR Simple Power Supply */

[[Image:LPU_TOP_sm.JPG|200px|thumb|left|LPU Prototype]]
'''
== Linear Power Unit (LPU) - HPSDR Simple Power Supply ==
'''

Project Leader: Scotty WA2DFI

"LPU" is the project-name for a simple HPSDR power supply. Although power supplies are widely available, the LPU will provide a convenient low-noise solution until the more complex Demeter power supply is completed. The LPU (as well as Demeter) are specifically designed for the HPSDR project. With the approaching release of Mercury, this is the last hardware part of a basic functional HPSDR transceiver.

The LPU will not take the place of Demeter; it is intended as an interim solution to power HPSDR boards until Demeter is completed.

Further information will be presented on this page as it becomes available.

73,
Scotty WA2DFI

'''Updated: (26th December 2008):'''

All 5 LPU prototypes assembled and tested. Added pictures. Updated schematic to XA4, which matches the prototype PCBs. Except for the capacitors in parallel with C3 and C7, it is accurate for a functional unit.

[[Image:LPU_BOT_sm.JPG|200px|thumb|left|LPU Bottom View]]
[[Image:LPU_Merc_Ozy_Atlas_sm.JPG|200px|thumb|left|LPU in Atlas backplane with Mercury and Ozy]]

'''Updated: (18th December 2008):'''

First LPU PCB assembled. +5V and +3.3V regulator outputs oscillate. Added additional capacitance to each output by adding 47uF 10V tantalum capacitors in parallel with C3 and C7. Outputs now stable.

'''Updated: (17th December 2008):'''

Received prototype PCBs. Parts previously ordered and all in stock. Many thanks to Lyle, KK7P for doing the PCB layout and edits.

'''Updated: (30th October 2008):'''

'''1 Physical'''

The LPU (Linear Power Unit) is a self-contained power supply board for HPSDR. It is mounted onto a 20-pin ATX connector that mates with the connector on the Atlas board.

'''2 Requirements'''

HPSDR boards require power outlined in the following table.

[[Image:Table1.png]]

'''3 Electrical'''

The LPU accepts a 12VDC regulated input and produced the following outputs:

[[Image:Table2.png]]

The LPU does not produce -5V or any standby voltages. It ignores the ATX power-on signal and
is always on. There is a jumper to shut off the -12V switching regulator when it is not needed in
order to eliminate RF noise.

'''4 LPU Feature List'''

Input power: 12.5V – 14.5V regulated DC input

Outputs: +12V@2A, +5V@2A, +3.3V@2A (opt), -12V@100mA

Poly fuse on each regulator input: +12, +5, +3.3V (opt), -12V regulators

Plugs into Atlas backplane ATX connector

Mounting holes allow direct mounting to Atlas backplane

Strap disable for -12V to reduce noise

Dual power-pole input connector

Internal dual power-pole output connector for PA or accessories

Estimated PCB size: (LxWxH): 119mm X 44mm X 40mm

Estimated overall size: (LxWxH): 137mm X 54mmX 60mm

Schematic: [[Media:LPU_XA4.pdf]]

ADMINISTRATION-NEWS

2009-04-23T14:54:39Z

AE5K:

This page will be used for any current announcements regarding our HPSDR website http://hpsdr.info/, this HPSDR Wiki, or the HPSDR Discussion List.

==HPSDR.ORG and HPSDR.INFO==

The domain name "hpsdr.org" is possibly no longer available to our group, so we've obtained "hpsdr.info" as a stop-gap measure. If you don't get our usual web page using http://hpsdr.org -- then try http://hpsdr.info

In addition, our discussion list (reflector) could be inoperative for an undetermined period if hpsdr.org domain becomes unavailable to us. We'll restore it or replace it as soon as possible -- and if replaced, all current subscribers will probably be asked to re-confirm their subscriptions (this would be because of our hosting provider's requirements to keep anyone from spamming those who do not wish to subscribe).

==Got Unsubscribed?==

If you suddenly find yourself unsubscribed from the HPSDR Discussion List (reflector), chances are the email messages to your subscription address have been bouncing. Most often (if your subscription address is still current), it is due to your internet service provider (ISP) attempting to protect you from perceived spam. The worst ones are usually the largest ones (see notes about Comcast below).

In the case of our discussion list, the messages are sent out on one of our host's servers. There may be 10,000 other senders using this same server, and all it takes is just one to either send actual spam or have one of the big ISPs think it is spam -- and POW! the ISP puts this server on its black list. Once this is done, the ISP rejects email to YOUR address if it comes from this server.

The solution is not to fight a losing battle with the ISP, but to use an alternate emailbox such as gmail.com. If you insist on looking in your ISP emailbox only, the email from gmail.com can be automatically forwarded to it...of course, unless it too is blocked by your ISP.

==HAPPY BIRTHDAY HPSDR.ORG==

March 1, 2009 - It was three years ago today that we began the website domain hpsdr.org and our discussion list (reflector). Today, on our third anniversary of the domain, our reflector has over 900 subscribers! I'd like to remind all that if anyone is needing help in posting messages or subscribing to the list, your list administrator is available to help. All queries are normally answered within 24 hours, so check your spam folder if you don't find a reply within that period of time.

== Some Old Stuff ==

'''I DIDN'T DO IT! - Comcast Again'''

December 25, 2006 - Seems this past week that our Mailman software program which runs our HPSDR Discussion List has thrown in the towel and given up on those with comcast.net email addresses. Apparently after so many attempts and being disabled so many times, Mailman unsubscribes the offending address(es) automatically. Again, I would urge those with comcast.com addresses to get a free gmail or similar email account to either receive discussion list messages directly or to configure so that it forwards them to the comcast address. That should make everyone happy again! Email me directly if you need a "gmail invite". Sorry about the problems, but it is out of my hands. -- AE5K.

'''COMCAST UPDATE'''

November 9, 2006 - Comcast has been blocking once again and those with comcast.net email addresses are no longer receiving discussion list email delivery.

October 17 - On again, off again. Comcast removed the blockade last week once again. As of this date, it appears all is well. Remaining information is being left on this page for historical reasons and to serve as backgrounder if Comcast decides to block our HPSDR Discussion List email from reaching their customers once again.

September 30 - Comcast is "at it again" -- as of this morning, I believe all our list members with comcast.net email addresses have been BLOCKED BY COMCAST from receiving HPSDR discussion list email. Here is the "diagnostic message" we are receiving from Comcast:

host gateway-s.comcast.net[204.127.202.26] said:
550 66.33.206.23 blocked by ldap:ou=rblmx,dc=comcast,dc=net -> BL003
Blocked for spam. Please see
http://www.comcast.net/help/faq/index.jsp?faq=SecurityMail_Policy18627

September 14 - A spot check on several comcast.net subscriber records indicates no blacklisting our discussion list traffic for at least a week now. It appears all back to normal.

Sept. 11 -- About a week ago, Comcast apparently took our discussion list mail server off the blacklist (at least temporarily) and I restored delivery of HPSDR discussion list email to all those with comcast.net addresses.

Previous posting on this problem is left here for now:

As our subscribers to the discussion list who have "comcast.net" email addresses know by now, Comcast is currently blocking (rejecting) our discussion list email to comcast.net addresses. You can find out about Comcast's sea of upset customers by Googling "comcast blacklist". I'm also reproducing below part of a communication from our hosting provider "Dreamhost" (for the discussion list).

From Dreamhost:

Comcast blocks are atypical from the others that we?ve been having problems
with in that they last indefinitely until unblocked manually. Unlike AOL
blocks (which phase out automatically after 24 hours - though may reappear)
someone has to flip a switch over there for any future mail to go through.
The unfortunate part is that they have zero human availability and all we
get from their blacklist email address are auto-responses ? either the IP
is automatically unblocked, or the unblock is denied and the phone number
of their abuse/security department is given. Unfortunately, this phone
number is a completely unmanned voicemail drop-box. We?ve left no less
than six messages on their voicemail in the last couple months, and despite
numerous requests we have never received a phone call back or an email
response. We?re not even asking that they remove the blacklist ? we?re
simply asking for more information on why the IPs were blocked, and for a
sampling of the typical spam they are supposedly getting from us! In fact,
the only response we can get from them (if we get one at all) is an
automated form message saying that ?most of the email? received from our
IPs is spam, which we know, in fact, is false.

FAQ

2009-04-14T03:21:56Z

AE5K: /* The HPSDR Project */

== The HPSDR Project ==

Q. '''I have a question that is not covered in this FAQ. How/who do I ask?'''

A. After searching for an answer and not finding it, usually the best way is to post your question on the HPSDR Discussion List (reflector).
This allows two things to happen: (1) it permits someone other than the very busy developers to answer he question if they can, and (2) it allows everyone on the list to gain the benefit of any reply.

----

Q. '''How do I get in direct email contact with project leaders?'''

A. The project leaders are active on the HPSDR Discussion List and you may contact them by posting a message to the list.

----

Q. '''What is the status of the various boards or modules?'''

A. Here's the scoop on some as of Jaunary 1, 2009:

ATLAS - in production, order through http://tapr.org
PINOCCHIO - in production, order through http://tapr.org
OZY - 1st production run - currently being shipped. Order through http://tapr.org
JANUS - 1st production run - currently being shipped. Order through http://tapr.org
MERCURY - 1st production Order through http://tapr.org
MERCURY-EU - alpha - see DJ8AY
PENELOPE - Sold Out http://tapr.org
ALEX - Pre-production

All others - in various stages of design/development -- see their wiki pages.

----

Q. '''What modules would I need to get a working HPSDR transceiver on the air?'''

A. It is important to remember the goals of HPSDR. All modules are not meant to be combined together to make a “single flavor” HPSDR transceiver. A number of different combinations will be possible (examples: Horton or Mercury for the receiver). How the modules are used and combined are in the hands of the experimenter/builder. Some users may not even wish to make an entire transceiver out of the modules (example: SDR1000 owners who only want to use Atlas, Ozy, and Janus to replace their sound cards).

In the words of Phil Covington, project leader for a number of the modules, “HPSDR was not formed to be a manufacturer of finished Ham Radio equipment. Its primary purpose is to develop a High Performance SDR in a modular fashion by experimentation with various methods.”

If your only goal is to get “on the air” with an SDR transceiver, there may be cheaper and/or easier routes to achieve this goal (Softrock or Flexradio).

If your goal is high performance software defined radio with a “roll your own” mentality, then the HPSDR modules should enable the creation of your own high performance SDR transceiver.

----

Q. '''Will the modules be offered in kit or assembled form, and what about cost?'''

A. Atlas and Pinocchio are offered as a bare board and kit of parts. Ozy and Janus are offered either bare board or
assembled and tested. A hard to get partial parts kit is being offered or Janus. Future module costs to be determined.

----

Q. '''Will Ozy and Janus "bare boards" be available?'''

A. Bare boards (not kits of parts) are available through TAPR.

----

Q. '''Why doesn't TAPR offer a kit of parts or at least the hard to obtain parts for Ozy or Janus?'''

A. A partial kit of harder to obtain parts is being offered for Janus. Potential users may certainly get together for a group buy on other parts needed to complete the boards. There are several reasons for TAPR (or HPSDR) not offering complete kits: (1) being an all-volunteer organization, it would take tremendous manpower to break the parts down to individual kits and package them, (2) there is a very large support problem for kit builders whose boards do not work when completed, and (3) the cost of a kit of parts would be about equal or may exceed the cost of an assembled and tested board.

----

Q. '''Will the Gerber files (PCB artwork) be available for anyone's use?'''

A. Yes. They are released under the new TAPR open source hardware license called OHL. The board designer may restrict to non-commercial use. The OHL license was finalized and approved in May 2007. See [http://tapr.org/OHL]

----

Q. '''Why not put OZY and JANUS on a single board?'''

A. The overall HPSDR project design philosophy has been to partition the design into modules small enough to allow experimentation
with part and design changes and to be able to put together a system meeting individual needs. Putting the ADC chip with associated
circuit on the Janus board allows a future (and hopefully better) chip to be used on a similar board, but keeping Ozy for the interface
and control. Flexibility is the goal.

----

Q. '''How much better will the Ozy-Janus combination be in terms of performance when used with the SDR-1000 in place of a sound card such as the Delta 44?'''

A. To be determined -- but of course, we expect better results. There are some preliminary results on the wiki and in the discussion list.

----

Q. '''Will a Ozy-Janus-Atlas combination work with my PowerSDR software used for my Flex Radio SDR-1000 in place of a sound card in my PC?'''

A. Yes, that was one of the early goals of the HPSDR group. Phil, VK6APH, did confirm with Gerald and Eric at the Flex-Radio meeting at the Dayton Hamvention 2007 that Ozy/Janus will be fully supported in future releases in their 'mainstream' releases of PowerSDR. Bill, KD5TFD, will be working with Eric from Flex to accomplish this. At this point it is not known exactly when, and what version the support will begin, but it will happen. Direct all questions regarding Janus/Ozy to the HPSDR Discussion List (and NOT the Flex-Radio list), as folks have been doing and admirably responding. The arrangement with Flex-Radio required the donation of a working Ozy/Janus to Flex-Radio and this has been accomplished after TAPR approved the expense.

----

Q. '''What will be an appropriate software for companions like Janus + Ozy + Phoenix + (Alex??) ?'''

A. These boards, and also with the addition of Mercury, will run using PowerSDR. --Phil VK6APH

----

Q. '''Is the HPSDR project going to use Windows or some flavor of Linux?'''

A. Yes! (Eventually both, that is...but, currently, the supported OS is WinXP). There is currently work being done for Linux and dttsp.

----
Q. '''What are the recommended minimum system requirements for the PC I will use for the HPSDR?'''

A. USB 2.0 is a requirement. Currently, the OS recommendation is WinXP. Windows 2000 is NOT recommended as the USB 2.0 stack on Windows 2000 is just too slow.

At this time, there are no solid recommendations for minimum CPU or RAM that are based on actual testing with HPSDR hardware of how low we can go.

FlexRadio does have Minimum Recommended PC Configurations for systems using the PowerSDR software. Since the HPSDR hardware may use PowerSDR, these specs are probably a good guide to what would be advisable for the HPSDR. FlexRadio's numbers from their website are as follows:

Processor: Min: 1.5GHz Recommended: 3.2GHz+ or greater

Memory: Min: 512MB Recommended: 1GB+ (use the fastest RAM available)

----

Q. '''What user name and password do I use to access the HPSDR svn repository?'''

A. None is required for reading the SVN, only required to place something in the repository. The IP address of the repository is shown on the resources page of the main HPSDR.org website.

----

Q. '''Will HPSDR be developed for higher frequencies like those used for satellite and space communications, e.g. VHF, UHF and Microwave?'''

A. There is a group doing SDR for microwave: [http://uwsdr.berlios.de/ ] Current HPSDR projects could certainly be used as an IF for a transverter, but there is nothing going on with HPSDR that is specifically aimed at microwave.

----

== The HPSDR Wiki ==

Q. '''Do I need to register for log in?'''

A. No! Only those who are active leaders, designers or documentors of various projects need login capability to edit their respective project pages. No login is needed to read any of the wiki.

----

Q. '''What if I find that a correction is needed in the wiki?'''

A. Reports such as this are welcomed by the WikiSysOp -- email ae5k at hpsdr dot com with details.

----

== ATLAS Backplane ==
Q. '''What is the recommended means of powering ATLAS?'''

A. Demeter. Until Demeter is available...

The ATX 20 pin power connector on the Atlas board enables the use of standard PC power supplies. (Please Note: There is no reason that you cannot utilize a non-PC power supply regulated and wired to provide the proper voltages to the 20pin connector. A non-PC power supply could also enable custom current limiting of the voltages going to the 20 pin connector, an advisable setup when testing or prototyping boards plugged into ATLAS. An analog power supply may be an attractive option for users particularly concerned about spurious emissions in the HF band which some low cost PC power supplies may produce.)

If you choose to use an ATX computer power supply care should be taken that the -12V current requirement is met. (Note of warning: some versions of the attractive picoPSU do not provide proper -12V current capacity. Check before you buy.)

As a reference for current requirements (reported by Bill Tracey May, 11, 2007), Ozy/Janus used by a SDR100 had the following current usage:

Ozy/Janus
+12v: 200 ma
+5v: 180 ma
-12v: 70 ma

Obviously additional boards connected to the Atlas board will increase these numbers.

Projections of current requirements for other boards are(as reported by Phil Harman, June 6, 2007):

Penelope
+12v: 200 ma
+5v: 300 ma

Mercury
+12v: 200 ma
+5v: 500 ma

Q. '''Will the Atlas be offered assembled?'''

A. Probably not. It is fairly easy to assemble with a very minimal amount of surface mount parts. There are quite a few solder pads due to the 96 pin connectors. If you are not able to do this work yourself, our advice is to ask on the HPSDR Discussion List (reflector) to see if you can pay someone to do the work for you.

----

Q. '''Can solder paste and a hot air heat gun (or oven) be used on Atlas for "all those connections" ?'''

A. It is possible, but at least one report indicates problems with the center row on the connectors. If considering doing this, we suggest you ask on the discussion list. If anyone has had success or failure, please report it to the wikisysop so we can update this reply.

----

Q. '''Will a larger (or smaller?) number of slots version be offered?'''

A. Possibly, if the need and demand warrant. Nothing is in the plans right now (as of May 2007).

----

Q. '''I don't see assignment of all the bus pins. Is there a list somewhere?'''

A. Some are not assigned a function yet, due to the developing nature of the HPSDR project and the use of the FPGA.

== PINOCCHIO Extender ==

Q. '''Availability?'''

A. The bare board and connectors are now available from TAPR http://tapr.org

== OZY ==

Q. '''Will the USB connection from Ozy to my PC require anything special in terms of USB port specification or drivers?'''

A. A USB 2 connection will be required on the PC. Most modern PCs have this as standard. With MS Windows, for the USB driver we are using the LibUsb-Win32 library which is a free download from http://libusb-win32.sourceforge.net/ A Linux version is also available, see http://www.linux-usb.org/ and http://libusb.sourceforge.net/ . Experience will tell us if there are any problems with certain types of USB2 ports.

----

Q. '''Why do we need a "configuration device" when the software can just load the FPGA via USB and the Cypress CY7C68013 (FX2) chip? The schematic shows the programming pins connected from FX2 GPIO pins to FPGA.'''

A. It does load via USB and this is how OZY is normally used. BUT, there will come a time when someone wants to use the OZY without PC attached and the configuraton device allows this possibility.

----

Q. '''Is the design of Ozy such that it can be used for other purposes than SDR?'''

A. We certainly hope so and expect that some will use it as a learning tool or development platform for other projects not even remotely related to SDR. It provides an inexpensive piece of hardware for many purposes.

----

== JANUS ==

Q. '''Is Janus a "sound card" ?'''

A. NO! The usual meaning of a sound card is one which plugs into a personal computer (ISA, PCI, or other bus). The Janus module plugs into our Atlas bus and contains some of the components of the usual sound card. It also requires the Ozy or similar interface to use it in applications which call for a PC sound card.

----

Q. '''Will I be able to use Janus for other non-SDR sound applications with my PC?'''

A. In theory, Yes! This will require a Windows or Linux driver; there is no reason one can't be written, we just need a volunteer!

----

== MERCURY ==

Q. '''Why are there no input RF filters on the Mercury PCB?'''

A. This is due to the multi-function nature of the Mercury board. Whilst primarily a high performance HF (and VHF/UHF in alias mode) receiver, Mercury can also be used for other functions. For example, it can be used as a high performance 0-55MHz spectrum analyzer, sampling oscilloscope and VNA (by using Penelope as the signal source for the VNA and also as a tracking generator). In these cases it is desirable not to have any RF filtering before the ADC on Mercury.

When used as a receiver the amount of filtering will vary depending on the antenna system the user has. For most situations with say an HF beam or dipoles the natural frequency response of the antenna may provide adequate filtering. For the user with a high performance broadband antenna e.g. a rhombic, or very strong local signals, then additional filtering may be required.

An external set of filters will be provided as part of the Alex project.

Additionally, HPDR is a journey and not a destination! We fully expect higher performance ADCs to be come available in the future. These newer devices will still require some form of input filtering. By using external filters the cost of replacing the ADC board is reduced.

== PENELOPE ==

Q. '''Why are there no output RF filters on the Penelope PCB?'''

A. This is due to a number of reasons. Firstly, whilst Penelope is primarily an HF ( and VHF/UHF on alias) exciter it can be used for other functions. For example, when used with Mercury it can form a low level signal source as a tracking generator or VNA. For these functions the lack of output filters is an advantage.

Secondly, Penelope generates RF directly at the desired output frequency by synthesizing the required RF waveform using a DAC. The lack of mixers, DDS, frequency synthesizer etc means the output spectrum of Penelope is particularly clean. In fact the spurious output at 0.5w meets the FCC requirements without additional filtering.

Thirdly, Penelope is an exciter. Whilst we expect it will be used by QRP operators as is we also expect it to be used to drive a higher power amplifier. In the latter case the user will most likely provided external filtering as part of this power amplification.

Fourthly, Penelope does provide a 55MHz LPF that can be placed in circuit after the DAC and prior to the 0.5W PA. If desired the user can add external bandpass filters here. Alternatively, the filter can be bypassed and/or an external VHF/UHF filter fitted such that the alias output of the DAC can be used on the higher bands.

Fifthly, if is desirable to use LPFs that may be also be used before Mercury. The IP3 performance of Mercury is very good and using small inductors, that are quite acceptable for removing the harmonics from Penelope, results in a significant degradation in IP3 performance.

An external set of filters will be provided as part of the Alex project.

Additionally, HPDR is a journey and not a destination! We fully expect higher performance DACs to be come available in the future. These newer devices will still require some form of output filtering. By using external filters the cost of replacing the exciter board is reduced.

== Miscellaneous ==

Project leaders, developers, documenters: feel free to contribute answers -- especially where it says "TBD" or "Answer pending." (email to AE6UJ).

General Readership: have a suggested question that should be here? Email AE6UJ specifically mentioning the wiki FAQ.
Email address is AE6UJ @ hpsdr.org (omit spaces).

HPSDRwiki:Community Portal

2009-04-14T03:15:09Z

AE5K: /* Introduction -- What's It All About? */

== HDSDR Project Overview ==

===The Discussion List and Archives will be down for a couple of days===

=== Introduction -- What's It All About? ===

The HPSDR is an open source (GNU type) hardware and software project intended as a "next generation" Software Defined Radio (SDR) for use by Radio Amateurs ("hams") and Short Wave Listeners (SWLs). It is being designed and developed by a group of SDR enthusiasts with representation from interested experimenters worldwide. The discussion list membership currently stands at over 900 and includes such SDR enthusiasts as Ray Anderson WB6TPU, Steve Bible N7HPR, Rick Hambly W2GPS, Phil Harman VK6APH, Lyle Johnson KK7P, Ulrich Rohde N1UL, and Bill Tracey KD5TFD to name a few.

The rationale behind the project 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 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 bandpass filters and input/output interfaces, to full blown DSP functions. Such variety enables experimenters with varying degrees of experience to contribute. If you wish to contribute your skills to this project, the best way is to advise your availability on the discussion list and communicate with project leaders -- or if you have a proposal for a new module, fly it on the discussion list and if feasible, become a project leader!

The modules have each been named for easier identification when talking or writing about them. On this wiki, each module has its own page, as noted by the links below. Some of the modules are being designed so that they can be either used in conjunction with others or stand-alone. Each module board size (except the backplane) will be 100 mm by 120 to 220 mm and use either a 64 pin or 96 pin DIN41612 type connector.

=== Milestone ===

[[image:MOPA1.jpg]]

Here is a photo of a complete Digital Up Conversion/Digital Down Conversion HPSDR transceiver by Phil Harman, VK6APH. The modules are, from left to right - prototype Mercury DDC based on an LT2208 evaluation board and Ozy board - V2 Penelope DUC - Ozy controller board - all sitting on the Atlas bus. Phil had the first QSO (2-way radio contact for the non-hams amongst us) with this on 7 October 2007 which coincided with his 40th anniversary of getting a Ham license!

=== Block Diagram ===

Here is a block diagram showing the Janus, Ozy, Mercury and Sasquatch modules and their functions.
[[image:HPSDR_Block_10_Dec_2006.jpg]]

=== Module/Board Availability ===

Completely assembled and tested, parts kits, and/or bare boards may be available for each of the HPSDR projects on a limited basis. See the FAQ section or individual wiki pages for what is available at the present time. Generally, the boards, kits, or assemblies will be available for purchase through TAPR [http://tapr.org] and an indication of pre-production interest is gaged by a sign-up process located
at website http://www.hamsdr.com where one must register, log in, and use the "Projects" tab to get to any list.

=== Future Modules ===

In order to provide a complete SDR transceiver other modules will be required. These include bandpass filters, a narrow band I/Q down converter to supplement the Mercury A/D converter, and low power transmitter functions etc.

There is still much to be done in bringing the HPSDR project to fruition. For those experimentally minded Amateurs, this may turn out to be the golden age of (software defined) radio!

=== Open source design ===

'''Brief definition of Open Source'''

In a "nutshell", open source is a term that is applied to a philosophy, in that the production and organization of a project or system is created through open and cooperative efforts.

Open source software refers to computer software available with its source code and under an "open source license" to study, change and improve its design and functionality.

There are many "Open source software" licenses, the most prominent being the GNU General Public License (GNU GPL or simply GPL), originally written by Richard Stallman. The GPL grants the recipients of a computer program the following rights, or freedoms:

* The freedom to run the program, for any purpose. 
* The freedom to study how the program works, and modify it. 
* The freedom to redistribute copies. 
* The freedom to improve the program, and release the improvements to the public. 

The users are treated like co-developers, are encouraged to submit additions to the software, code fixes, bug reports, documentation etc. Having more co-developers increases the rate at which the software evolves. Furthermore, each end user's machine provides an additional testing environment. This new testing environment offers the ability to find and fix a new bug quickly.

[Note: this definition does not go into the various obligations and legalities and is intended to be brief and non-exhaustive. The original was supplied by Kevin, M0KHZ and modified by the WikiSysOp.]

This GPL philosophy extends to the hardware for this HPSDR cooperative project. However it was felt by many that the software GPL and similar licenses would not adequately cover the hardware portion of this project, so an Open Hardware License (OHL) was devised. Also, another license referred to as the NCL - Non-Commercial License, was implemented to take care of situation where the project developers wish to reserve commercial licensing rights. The complete text of the two versions of the OHL/NCL licenses along with some explanation may be found on the TAPR website at http://www.tapr.org/ohl.html

=== TAPR Affiliation ===

In early June (2006) it was announced that agreement had been reached with TAPR http://tapr.org for TAPR to provide assistance and a "storefront" for the "products" of the HPSDR group. TAPR has a long history of supporting various digital amateur radio related ventures. We would encourage our members to become TAPR members, not only to support a worthy organization, but also to receive a member discount (usually around 10%) on their HPSDR and other purchases from them.

Assistance in project development is in the form of partial funding for alpha and beta runs of boards upon application to and approval by TAPR's Board of Directors, and then in guiding the manufacturing process. It is not the intention of TAPR to profit from providing this assistance or the manufacture of projects.

It should be emphasized that TAPR and HPSDR are independent organizations or communities and that any TAPR reproduction of HPSDR developed projects is through licensing agreements.

TAPR will be most likely the only source for HPSDR boards due to short runs and the investment required. This does not preclude '''individuals''' having their '''own''' PCB boards made in keeping with the open-source philosophy. Commercial reproduction may be restricted depending on the license granted by the board developers. Visit the TAPR website http://tapr.org for current availability.

=== AMSAT Affiliation ===

In July (2006) the following announcement was made by Rick Hambly W2GPS, AMSAT President:

AMSAT will immediately initiate support for The High Performance Software
Defined Radio (HPSDR) project, an independent team that is dedicated to
bringing high performance software defined radio devices within the reach of
amateurs in terms of access to the hardware and software and at manageable
prices.

This is a rare opportunity for AMSAT to easily join a major technological
development and have a positive impact on both that development and AMSAT's
own primary interests. The High Performance Software Defined Radio (HPSDR)
project is a completely open source software (GNU Public License) and open
hardware design. It has an extremely capable group of core designers, many
of whom are also key AMSAT design team members, supported by a cast of
hundreds.

AMSAT will support HPSDR with a modest amount of financial, personnel and
other resources. Financial resources will be under AMSAT control and will be
used to support activities such as joint HPSDR and Eagle design meetings.
AMSAT's Engineering team will submit a 2007 budget for the AMSAT Board's
approval at the annual meeting in October. The modest resources that are
needed in 2006 can be provided by the Eagle team project.

=== Resources ===

Please be aware that we have a website with pages devoted to each sub-project plus other information and resources. The website will not necessarily contain the latest information (that's the reason we have this wiki) but is a good starting place for a little less technical overview of the project and its parts. The website is at http://hpsdr.org -- and the website also contains other information and links to many other references and resources of interest to the topics of Software Defined Radio, FPGA's, etc.

'''''For the very latest scoop, join the HPSDR discussion list (reflector). You'll find information on the http://hpsdr.org/reflector.html webpage on how to subscribe to this email list.'''''

We now also offer an alternative notification list (an announcement list) for those potential users not wanting the daily discussion list traffic. Information on this HPSDR-announce list may also be found on the http://hpsdr.org/reflector.html webpage.

To contact the webmaster/wikisysop/list-administrator, email ae5k at hpsdr dot com.

== [[FAQ]] - Frequently Asked Questions ==

This is a new section started to allow asking and hopefully answering questions about HPSDR.

== [[DOC]] - Documentation ==

Summary of current documentation available.

=== [[Quick Startup Guide]] ===

Documents to help users get HPSDR setup and working.

== [[DOWNLOADS]] - Firmware and Software ==

Links to current firmware and software available.

== [[SYSTEM INTEGRATION]] ==

This section contains information relative to "putting the pieces together".

----

== Individual Project Wiki Pages ==

Click on the NAME of the project to get to its page!

=== [[ALEXIARES]] - RF Preselector ===

Alexiares (or Alex for short) is a set of RF Bandpass filters for use with Mercury or any other SDR.

=== [[ANICETUS]] (Anie) - Preselector ===

A few designs for narrow band preselectors

=== [[ATLAS]] - Backplane ===

The Atlas is a passive backplane that all other modules plug into.

=== [[CYCLOPS]] - Spectrum Analyzer ===

Cyclops is a 0-1 GHz spectrum analyzer with tracking generator support.

=== [[DEMETER]] - Power Supply ===

=== [[EPIMETHEUS]] - General Purpose I/O ===

Epi is a general purpose I/O board for the Atlas bus and includes relays, open collectors, IF switching, etc.

=== [[EXCALIBUR]] - Clock Reference board ===

=== [[GIBRALTAR]] - GPS-disciplined Frequency Standard ===

Gibraltar is a GPS-disciplined frequency standard board.

=== [[HELIOS]] - Helios Small Transmitting Loop Antenna and Controller ===

=== [[HERMES]] - A DUC/DDC Transceiver. ===

=== [[HORTON]] - Receiver Module ===

A receiver module integrating the Janus ADC with a QSD on a board for a version of the HPSDR RX board.

=== [[JANUS]] - ADC/DAC Board ===

The Janus module is a very high performance, dual, full duplex, A/D and D/A converter board.

=== [[LPU]] - Simple Linear Power Unit ===

The LPU unit takes power from a regulated power supply and steps it to the input needed by Atlas

=== [[MERCURY]] - 0-55 MHz Direct Sampling Receiver ===

Perhaps the most exciting of all modules, Mercury will enable direct sampling of the 0-55 MHz spectrum.

=== [[ODYSSEY]] - Low Power Handheld SDR ===

Odyssey includes a low power SDR based on the QSD, QSE, and a dsPIC33 as the basic radio core.

=== [[OZY]] - HPSDR Host Interface & Control ===

The OZY module is an FPGA based interface controller card providing input and output connections to the real world.

=== [[OZYII]] - (AussieII) - A high speed PC interface. ===

=== [[PANDORA]] - Enclosure ===

=== [[PENELOPE]] - Companion Exciter to Mercury ===

A 1/2 watt DUC(k).

=== [[PENNYWHISTLE]] - 20 Watt RF Power Ampilfier ===

The PennyWhistle takes the RF out put of Penelope and ampilifes it to approximately 20 watts.

=== [[PHOENIX]] - QSD/QSE Receiver/Transmitter Module ===

QSD based HF Receiver, a QSE based HF Exciter and a supporting synthesizer.

=== [[PINOCCHIO]] - Extender Card ===

Pinocchio is an extender card to allow measurements and troubleshooting of an active card in an ATLAS backplane.

=== [[PROTEUS]] - Prototyping Board ===

This is the planned prototyping board.

=== [[SASQUATCH]] - DSP back-end ===

The Sasquatch board is a hardware DSP back-end intended for use by constructors who would like to operate
stand-alone rather than attached to a PC.

=== [[THOR]] - High Efficiency HF Power Amplifier ===

Thor is a high efficiency HF power amplifier using Envelope Elimination and Restoration (ERR) techniques.

== [[Board Designer's Resources]] ==

== [[ANCILLARY]] - Additional "stuff" of interest to HPSDR ==
Some stuff like Norton Amplifier, FPGA VHDL/Verilog ...

== [[EXPERIMENTERS-CORNER]] - Ideas not yet projects ==

== [[ADMINISTRATION-NEWS]] - Messages about HPSDR web, wiki, discussion list ==

ADMINISTRATION-NEWS

2009-04-14T02:59:14Z

AE5K: Updated to hpsdr.info, took out ae5k email address

This page will be used for any current announcements regarding our HPSDR website http://hpsdr.info/, this HPSDR Wiki, or the HPSDR Discussion List.

==HPSDR.ORG and HPSDR.INFO==

The domain name "hpsdr.org" is no longer available to our group, so we've changed to "hpsdr.info"

In addition, our discussion list (reflector) is inoperative for an undetermined period.

'''Got Unsubscribed?'''

If you suddenly find yourself unsubscribed from the HPSDR Discussion List (reflector), chances are the email messages to your subscription address have been bouncing. Most often (if your subscription address is still current), it is due to your internet service provider (ISP) attempting to protect you from perceived spam. The worst ones are usually the largest ones (see notes about Comcast below).

In the case of our discussion list, the messages are sent out on one of our host servers. There may be 10,000 other senders using this same server, and all it takes is just one to either send actual spam or have one of the big ISPs think it is spam -- and POW! the ISP puts this server on its black list. Once this is done, the ISP rejects email to YOUR address if it comes from this server.

The solution is not to fight a losing battle with the ISP, but to use an alternate emailbox such as gmail.com. If you insist on looking in your ISP emailbox only, the email from gmail.com can be automatically forwarded to it...of course, unless it too is blocked by your ISP.

'''HAPPY BIRTHDAY HPSDR.ORG'''

March 1, 2008 - It was two years ago today that we began the website domain hpsdr.org and our discussion list (reflector). Today, on our second anniversary of the domain, our reflector has over 700 subscribers! I'd like to remind all that if anyone is needing help in posting messages or subscribing to the list, your list administrator is available to help. All queries are normally answered within 24 hours, so check your spam folder if you don't find a reply within that period of time.

== Some Old Stuff ==

'''I DIDN'T DO IT! - Comcast Again'''

December 25, 2006 - Seems this past week that our Mailman software program which runs our HPSDR Discussion List has thrown in the towel and given up on those with comcast.net email addresses. Apparently after so many attempts and being disabled so many times, Mailman unsubscribes the offending address(es) automatically. Again, I would urge those with comcast.com addresses to get a free gmail or similar email account to either receive discussion list messages directly or to configure so that it forwards them to the comcast address. That should make everyone happy again! Email me directly if you need a "gmail invite". Sorry about the problems, but it is out of my hands. -- AE5K.

'''COMCAST UPDATE'''

November 9, 2006 - Comcast has been blocking once again and those with comcast.net email addresses are no longer receiving discussion list email delivery.

October 17 - On again, off again. Comcast removed the blockade last week once again. As of this date, it appears all is well. Remaining information is being left on this page for historical reasons and to serve as backgrounder if Comcast decides to block our HPSDR Discussion List email from reaching their customers once again.

September 30 - Comcast is "at it again" -- as of this morning, I believe all our list members with comcast.net email addresses have been BLOCKED BY COMCAST from receiving HPSDR discussion list email. Here is the "diagnostic message" we are receiving from Comcast:

host gateway-s.comcast.net[204.127.202.26] said:
550 66.33.206.23 blocked by ldap:ou=rblmx,dc=comcast,dc=net -> BL003
Blocked for spam. Please see
http://www.comcast.net/help/faq/index.jsp?faq=SecurityMail_Policy18627

September 14 - A spot check on several comcast.net subscriber records indicates no blacklisting our discussion list traffic for at least a week now. It appears all back to normal.

Sept. 11 -- About a week ago, Comcast apparently took our discussion list mail server off the blacklist (at least temporarily) and I restored delivery of HPSDR discussion list email to all those with comcast.net addresses.

Previous posting on this problem is left here for now:

As our subscribers to the discussion list who have "comcast.net" email addresses know by now, Comcast is currently blocking (rejecting) our discussion list email to comcast.net addresses. You can find out about Comcast's sea of upset customers by Googling "comcast blacklist". I'm also reproducing below part of a communication from our hosting provider "Dreamhost" (for the discussion list).

From Dreamhost:

Comcast blocks are atypical from the others that we?ve been having problems
with in that they last indefinitely until unblocked manually. Unlike AOL
blocks (which phase out automatically after 24 hours - though may reappear)
someone has to flip a switch over there for any future mail to go through.
The unfortunate part is that they have zero human availability and all we
get from their blacklist email address are auto-responses ? either the IP
is automatically unblocked, or the unblock is denied and the phone number
of their abuse/security department is given. Unfortunately, this phone
number is a completely unmanned voicemail drop-box. We?ve left no less
than six messages on their voicemail in the last couple months, and despite
numerous requests we have never received a phone call back or an email
response. We?re not even asking that they remove the blacklist ? we?re
simply asking for more information on why the IPs were blocked, and for a
sampling of the typical spam they are supposedly getting from us! In fact,
the only response we can get from them (if we get one at all) is an
automated form message saying that ?most of the email? received from our
IPs is spam, which we know, in fact, is false.

ADMINISTRATION-NEWS

2008-11-26T22:47:43Z

AE5K:

This page will be used for any current announcements regarding our HPSDR website http://hpsdr.org/, this HPSDR Wiki, or the HPSDR Discussion List http://hpsdr.org/reflector.html.

'''Got Unsubscribed?'''

If you suddenly find yourself unsubscribed from the HPSDR Discussion List (reflector), chances are the email messages to your subscription address have been bouncing. Most often (if your subscription address is still current), it is due to your internet service provider (ISP) attempting to protect you from perceived spam. The worst ones are usually the largest ones (see notes about Comcast below).

In the case of our discussion list, the messages are sent out on one of our host servers. There may be 10,000 other senders using this same server, and all it takes is just one to either send actual spam or have one of the big ISPs think it is spam -- and POW! the ISP puts this server on its black list. Once this is done, the ISP rejects email to YOUR address if it comes from this server.

The solution is not to fight a losing battle with the ISP, but to use an alternate emailbox such as gmail.com. If you insist on looking in your ISP emailbox only, the email from gmail.com can be automatically forwarded to it...of course, unless it too is blocked by your ISP.

'''HAPPY BIRTHDAY HPSDR.ORG'''

March 1, 2008 - It was two years ago today that we began the website domain hpsdr.org and our discussion list (reflector). Today, on our second anniversary of the domain, our reflector has over 700 subscribers! I'd like to remind all that if anyone is needing help in posting messages or subscribing to the list, your list administrator is available to help. Easiest email address to use is AE5K (at) HPSDR (dot) ORG -- all queries are normally answered within 24 hours, so check your spam folder if you don't find a reply within that period of time.

== Some Old Stuff ==

'''I DIDN'T DO IT! - Comcast Again'''

December 25, 2006 - Seems this past week that our Mailman software program which runs our HPSDR Discussion List has thrown in the towel and given up on those with comcast.net email addresses. Apparently after so many attempts and being disabled so many times, Mailman unsubscribes the offending address(es) automatically. Again, I would urge those with comcast.com addresses to get a free gmail or similar email account to either receive discussion list messages directly or to configure so that it forwards them to the comcast address. That should make everyone happy again! Email me directly if you need a "gmail invite". Sorry about the problems, but it is out of my hands. -- AE5K.

'''COMCAST UPDATE'''

November 9, 2006 - Comcast has been blocking once again and those with comcast.net email addresses are no longer receiving discussion list email delivery.

October 17 - On again, off again. Comcast removed the blockade last week once again. As of this date, it appears all is well. Remaining information is being left on this page for historical reasons and to serve as backgrounder if Comcast decides to block our HPSDR Discussion List email from reaching their customers once again.

September 30 - Comcast is "at it again" -- as of this morning, I believe all our list members with comcast.net email addresses have been BLOCKED BY COMCAST from receiving HPSDR discussion list email. Here is the "diagnostic message" we are receiving from Comcast:

host gateway-s.comcast.net[204.127.202.26] said:
550 66.33.206.23 blocked by ldap:ou=rblmx,dc=comcast,dc=net -> BL003
Blocked for spam. Please see
http://www.comcast.net/help/faq/index.jsp?faq=SecurityMail_Policy18627

September 14 - A spot check on several comcast.net subscriber records indicates no blacklisting our discussion list traffic for at least a week now. It appears all back to normal.

Sept. 11 -- About a week ago, Comcast apparently took our discussion list mail server off the blacklist (at least temporarily) and I restored delivery of HPSDR discussion list email to all those with comcast.net addresses.

Previous posting on this problem is left here for now:

As our subscribers to the discussion list who have "comcast.net" email addresses know by now, Comcast is currently blocking (rejecting) our discussion list email to comcast.net addresses. You can find out about Comcast's sea of upset customers by Googling "comcast blacklist". I'm also reproducing below part of a communication from our hosting provider "Dreamhost" (for the discussion list).

From Dreamhost:

Comcast blocks are atypical from the others that we?ve been having problems
with in that they last indefinitely until unblocked manually. Unlike AOL
blocks (which phase out automatically after 24 hours - though may reappear)
someone has to flip a switch over there for any future mail to go through.
The unfortunate part is that they have zero human availability and all we
get from their blacklist email address are auto-responses ? either the IP
is automatically unblocked, or the unblock is denied and the phone number
of their abuse/security department is given. Unfortunately, this phone
number is a completely unmanned voicemail drop-box. We?ve left no less
than six messages on their voicemail in the last couple months, and despite
numerous requests we have never received a phone call back or an email
response. We?re not even asking that they remove the blacklist ? we?re
simply asking for more information on why the IPs were blocked, and for a
sampling of the typical spam they are supposedly getting from us! In fact,
the only response we can get from them (if we get one at all) is an
automated form message saying that ?most of the email? received from our
IPs is spam, which we know, in fact, is false.