I second the comments copied below. <div><br></div><div>In addition to scattered documentation, I would also chime in on another difficulty that I found in getting started with the HPSDR.</div><div> </div><div>This regards the availability of the hardware. You can't order a complete set of kits that will get you started with HPSDR. If you want to get stated say, with a Atlas/Ozy/Janus set up or Atlas/Ozy/Mercury/Penelope configuration, you will find that some components are are available as a kit, some are available completed, some are available just as a board, some have to be ordered overseas. </div>
<div><br></div><div>If the process of simply obtaining the hardware parts is so convoluted, how can you expect DSP software experts to jump into it? They may not be hardware experts. They may not know how / want to / be equipped do SMT soldering. Even if they could do the soldering, just ordering all the individual components for a single project is quite a task (in the case were just a board is available). </div>
<div><br></div><div>As a result, people who are interested in the software side of SDR experimentation may be driven to working with other designs where the hardware is more readily available. </div><div><br></div><div>This, I also believe, is indicative of another problem that stymies collaboration. The hardware designs are not truly open and free. Much of it is available for use only on a non-commercial basis. This prevents for-profit entities from kitting the designs. Were they able to kit them or sell them complete, the kits would be readily available and the start up costs for an individual experimenter and DSP software developer would be significantly cheaper. This would allow the community to grow and would foster much more community collaboration, both on the software and hardware side. </div>
<div><br></div><div>While I am excited about working with SDR and have been researching it and thinking about it for a long time, I have not yet gotten started, partially on account of some of the issues that I mentioned above.</div>
<div><br></div><div>My $0.02</div><div><br></div><div>73,</div><div>Joseph KD1ZZ</div><div><br>
<br><div class="gmail_quote">On Sun, May 3, 2009 at 8:10 PM, Richard Ames <span dir="ltr"><<a href="mailto:richard@ames.id.au" target="_blank">richard@ames.id.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
***** High Performance Software Defined Radio Discussion List *****<br>
<br>
On Sat, 2009-05-02 at 09:56 -0500, xxxx wrote:<br>
<br>
<snip><br>
> What do you think needs to be done to encourage more<br>
> software development projects to go on top of the<br>
> hardware?<br>
> <cut><br>
<br>
A particularly germane article just appeared in Linux Magazine:<br>
<a href="http://www.linux-magazine.com/issues/2009/103/finding_coders" target="_blank">http://www.linux-magazine.com/issues/2009/103/finding_coders</a><br>
<br>
I am very newbie to this project but my observations so far:<br>
<br>
1. Need to be welcoming - if there is conflict in the project potential<br>
contributors will wait / go elsewhere. Conflict is normal but needs to<br>
be handled.<br>
<br>
2. It needs to be organised. How is not critical - Linus Torvolds uses<br>
GIT (see: <a href="http://git-scm.com/" target="_blank">http://git-scm.com/</a> and Linus talking on GIT:<br>
<a href="http://www.youtube.com/watch?v=4XpnKHJAok8" target="_blank">http://www.youtube.com/watch?v=4XpnKHJAok8</a>) and a mailing list - that's<br>
all! He can - because he is the benevolent dictator.<br>
<br>
HPSDR is confusing --- mailing list, web page, verilog web page, svn,<br>
tarballs, some documentation (some of which conflicts with other bits),<br>
hamsdr website and storage of bits, array of SW projects (not spoken of<br>
much in the HPSDR pages), etc.....<br>
<br>
One reason I have focused on the wiki: I see it as possibly an<br>
organising medium that all can contribute to.<br>
<br>
You can help me:<br>
<br>
Who is the benevolent dictator in the HPSDR project and who are his/her<br>
trusted lieutenants?<br>
<br>
Cheers,<br>
<br>
Richard.<br>
<br>
_______________________________________________<br>
HPSDR Discussion List<br>
To post msg: <a href="mailto:hpsdr@openhpsdr.org" target="_blank">hpsdr@openhpsdr.org</a><br>
Subscription help: <a href="http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org" target="_blank">http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org</a><br>
HPSDR web page: <a href="http://openhpsdr.org" target="_blank">http://openhpsdr.org</a><br>
Archives: <a href="http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/" target="_blank">http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/</a><br>
</blockquote></div><br></div>