<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
I just looked at the website and see the following in regard to what
you are talking about.<br>
<br>
"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"<br>
<br>
Maybe this statement should change if Hermes is going to be a project.
Hermes an interesting idea as you say, as some people might like having
a Mercury/Penelope/Ozy all on one board. As stated above, I would
agree that Hermes doesn't really fit the Project Description listed on
the website home page.<br>
<br>
However, I dont think this new board will slow down the work being done
on Penelope, Mercury, and Ozy as I have been concentrating on changing
the Verilog for these boards and teaching others how they can get
involved and work on them too. Maybe some of those I have been
teaching are wanting to get involved in a new board like this. I will
stay focused on Mercury, Penelope and Ozy (1 and 2) for the immediate
future so I don't think they will suffer from this new introduction
which I haven't even looked at.<br>
<br>
Kirk Weedman KD7IRS<br>
<br>
<br>
Philip Covington wrote:
<pre wrap="">***** High Performance Software Defined Radio Discussion List *****
On Sun, Apr 12, 2009 at 12:35 PM, Kevin Wheatley <a
class="moz-txt-link-rfc2396E" href="mailto:m0khz@tiscali.co.uk"><m0khz@tiscali.co.uk></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">***** High Performance Software Defined Radio Discussion List *****
Following the outstanding success of Mercury and Penelope, and while investigating the verilog code for both, I had the insane idea of merging the verilog code of Mercury and Penelope into a single fpga! I played around with this idea for a while and the more I thought about it the more I liked the idea.
So here is the proposal, to develop a single board HPSDR based on the hardware of Mercury and Penelope and a single large fpga.
This board would have PC connectivity by USB. I’m planning to squeeze this all onto Euro Card sized PCB (100 x 160 mm), and if I utilize both sides I might even have room for a Pennywhistle type PA :).
Basic specs so far (nothing cast in stone)
Fpga EP3C25Q240C (I think this is the largest without BGA pin out)
Mercury receive chain
Penelope transmit chain
USB2 to PC data transfer
Pennywhistle PA (if there’s room)
10Mhz on board with ext an option
Alex filter switching header
13.5V supply
I’ll post a provisional block diagram on the Wiki this week, and lastly, why the name?
Following the tradition of the HPSDR naming convention, I thought Hermes was appropriate as he was known for his invention and theft!
All comments welcome.
Kevin – M0KHZ
</pre>
</blockquote>
<pre wrap=""><!---->
While interesting, this proposal does not fit in with the rest of the
HPSDR projects. It does nothing to advance HPSDR because it is a
rehashing of boards that have already been produced. The idea behind
HPSDR was to break the projects up into modules that could work on a
common bus (ATLAS). By breaking it up into modules, multiple people
could work toward a common goal. There is also a (project leaderless)
proposal for an Ethernet based OZYII board now - how does that jive
with your stand alone board proposal?
The other issue is that this will necessarily require different
firmware, software, and FPGA HDL than the individual modules it
combines. What about those who have invested in Atlas, OZY, Mercury,
Penelope, etc..? Will development be slowed or stopped for those
people if favor of the this new board that combines all the work of
these individual projects into one?
Phil N8VB</pre>
<br>
</body>
</html>