<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>One of my problems with this idea is that
the Atlas board then becomes strictly a development board; the design _<i><span
style='font-style:italic'>must</span></i>_ be redone for any end-product that
might come out of this project. It seems as though the board would have a much
larger market if it could be used as-is for end-user products as well. That’s
also why I’d like it if the board didn’t _<i><span
style='font-style:italic'>require</span></i>_ a heavy and relatively expensive
computer case, just _<i><span style='font-style:italic'>allowed</span></i>_ it
for the much smaller developer customer group, and why the size shouldn’t
get too big..<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> Chris
–AE6VK<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=3 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Phil Harman
[mailto:pvharman@arach.net.au] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Sunday, March 05, 2006 3:46
AM<br>
<b><span style='font-weight:bold'>To:</span></b> 'High Performance Software
Defined Radio Discussion List'<br>
<b><span style='font-weight:bold'>Subject:</span></b> [hpsdr] ATX connector on
Atlas bus</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>Second take on the ATX
connector.<br>
<br>
The boards that we attach to the Atlas bus are in many cases going to be <br>
prototypes and development boards. There is the inevitable chance that <br>
there will be circuit and operator errors. With a full blown ATX power <br>
supply connected to the bus - that can provide may 10's of amps - such <br>
errors can be 'interesting' to say the least. ATX power supplies are <br>
intended to power production designs that are not subject to tinkering. If <br>
we use a small Molex header then connecting up regulated and current limited<br>
power supplies during the testing and development phases is very simple.<br>
<br>
Since I don't see a high power PA being on of the six boards we don't need <br>
10's of amps anyway. I'm not suggesting that we don't use ATX power <br>
supplies for a final and proven design - just not during the development <br>
phases.<br>
<br>
I still support the case for a simple, small, Molex connector on the Atlas <br>
bus.<br>
<br>
Phil...VK6APH<o:p></o:p></span></font></p>
</div>
</div>
</body>
</html>