<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 12/17/2012 12:45 PM, Brian
Teitelbaum wrote:<br>
</div>
<blockquote
cite="mid:8961DF9D3453CF41A4A5B6E6BECA4C770D2B2C2B0A@VS-SJEXCH01.recsolar.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@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","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">MidNite
Solar is working on a unit that they are calling the
“Translator” that will allow the Classic controllers to
communicate with other brands of system controllers like the
MATE or the XW System Control Panel. I don’t know how far
along in the development process they are, but maybe boB can
chime in to let us know.</span></p>
</div>
</blockquote>
<br>
<br>
The general purpose "Interpreter" has been preempted by a couple of
other communications methodologies that<br>
should be much quicker to design. One is for the SMA products
because we are working with SMA on that one.<br>
<br>
As far as for OB interoperability, we are trying to see if we can
use their new AXS interface to talk back and forth.<br>
That might just work and ~shouldn't~ take too much time to get
going.<br>
<br>
boB<br>
<br>
<br>
<br>
<blockquote
cite="mid:8961DF9D3453CF41A4A5B6E6BECA4C770D2B2C2B0A@VS-SJEXCH01.recsolar.local"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Otherwise
I agree with Ray that using a MidNite Classic 200 will allow
you to use 4 modules in series. The max output amps on the
200 at 48VDC is 76A, so that limits you to about 4kW (76A x
52VDC = 3952A), but that will work fine with 16 of the 240W
modules. You can of course exceed this, but you may see some
clipping on clear cold days around noon.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Brian
Teitelbaum<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">AEE
Solar<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
<a class="moz-txt-link-abbreviated" href="mailto:re-wrenches-bounces@lists.re-wrenches.org">re-wrenches-bounces@lists.re-wrenches.org</a>
[<a class="moz-txt-link-freetext" href="mailto:re-wrenches-bounces@lists.re-wrenches.org">mailto:re-wrenches-bounces@lists.re-wrenches.org</a>] <b>On
Behalf Of </b>Ray Walters<br>
<b>Sent:</b> Monday, December 17, 2012 12:31 PM<br>
<b>To:</b> RE-wrenches<br>
<b>Subject:</b> Re: [RE-wrenches] Radian design
limitation - am I missing something?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">I second WIlliam's sentiment about having
all equipment communicate together, but Outback just ain't
there. I know Midnite's stuff will communicate with the
universal MODBUS language, and is not that silly proprietary
stuff that Outback does. I don't see any reason not to use
Midnite Classic lites and go to 4 modules in series. The
customer will also appreciate the computer interface on
MyMidnite, much more than suffering through the "MATE"
screen. Let the Outbacks sell independently, and I think
for 2012, that's as good as it gets.<br>
The idea of AC coupling as others noted is also a decent
option, but when I last looked, it is much more expensive.<br>
Charge controllers are much cheaper per watt than inverters
for a 48 vdc battery.<br>
<br>
Ray Walters<br>
<br>
<br>
On 12/17/2012 12:15 PM, William Miller wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><br>
<br>
Sure we'd all like to be able to purchase one system that
does everything: equipment that communicates between
chassis and the outside world<br>
<br>
<o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>