<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" 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 12 (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: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";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Tahoma","sans-serif";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:.5in .5in .5in .5in;}
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 lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Tony, <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'>I have not had time to look into your program much, but from
what it sounds like and what it could do are really cool. <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'>If you could create a way for me to upgrade a .pca file from say
a Omni (original) to an Omni Pro II, that I would pay you money for. I
have upgraded 7 HAI controllers this year, and it takes 1-3 hours to reprogram
a controller based on the one I replaced and then test and re-verify it.
I have yet to get a 100% upgrade without errors. I know the problem is
between the keyboard and the chair, but your program should be able to fix that!
Seems like this would be a simple task, and just use defaults when the new
panel has new settings the old one didn’t.<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'>Let me know your thoughts!<o:p></o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.5pt;font-family:"Arial","sans-serif";
color:#1F497D'>-- <br>
<b>Brett Griffin<br>
</b>Home Technology Designer</span><span style='font-size:10.0pt;font-family:
"Arial","sans-serif";color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.5pt;font-family:"Arial","sans-serif";
color:#1F497D'>P (206) 774.3622<br>
F (206) 260.7475<br>
<br>
<b>Archi</b></span><b><span style='font-size:8.5pt;font-family:"Arial","sans-serif";
color:#8CC62F'>tech</span></b><b><span style='font-size:8.5pt;font-family:"Arial","sans-serif";
color:#1F497D'>tronics, Inc<br>
</span></b><span style='font-size:8.5pt;font-family:"Arial","sans-serif";
color:#1F497D'><a href="http://www.architechtronics.com/">http://www.architechtronics.com</a><br>
Designing technology to fit your lifestyle.<br>
</span><b><span style='font-size:8.5pt;font-family:"Arial","sans-serif";
color:#8CC62F'><br>
Visit our blog!</span></b><b><span style='font-size:8.5pt;font-family:"Arial","sans-serif";
color:#CF5F23'> </span></b><span style='font-size:8.5pt;font-family:"Arial","sans-serif";
color:#1F497D'><a href="http://www.architechtronics.com/blog/">http://www.architechtronics.com/blog/</a></span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p>
</div>
<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"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Tom Williamson [mailto:Tom@DTSsoftware.com]
<br>
<b>Sent:</b> Wednesday, November 28, 2007 8:02 AM<br>
<b>To:</b> Tony Golden; hai-users@tssi.com<br>
<b>Subject:</b> RE: [Hai-users] Program compiler<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>They know it exists but I don't know if they want to take it over.</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>I did find a "bug" in there firmware when writing the
compiler. It had to do with setting temps up/down. They are going
to fix it in the next firmware release.</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>If they just had a way to import/export the programs in text form
then this would have been easier. I would just generate the
right text file and import it into pcaccess. Then pcaccess could download
the programs into the panel. But I had to actually generate the hex
program data, names, and voices. Then download the data to the panel.</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Tom</span> <o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> hai-users-bounces@tssi.com
[mailto:hai-users-bounces@tssi.com] <b>On Behalf Of </b>Tony Golden<br>
<b>Sent:</b> Wednesday, November 28, 2007 10:45 AM<br>
<b>To:</b> hai-users@tssi.com<br>
<b>Subject:</b> RE: [Hai-users] Program compiler</span><o:p></o:p></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:blue'>That does sound extra cool.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:blue'>However, I’m concerned about it “breaking” with
future firmware updates, or not being compatible with specific versions.
Have you discussed sharing your work with HAI, so they could officially support
it? I’ve heard they’ve had plans to update PC Access for a
long time, so hopefully they would be interested...<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:blue'>Thanks for sharing!<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:blue'> </span><span
style='font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
</div>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
hai-users-bounces@tssi.com [mailto:hai-users-bounces@tssi.com] <b>On Behalf Of </b>Tom
Williamson<br>
<b>Sent:</b> Wednesday, November 28, 2007 9:43 AM<br>
<b>To:</b> hai-users@tssi.com<br>
<b>Subject:</b> [Hai-users] Program compiler</span><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>I
have finished my first pass at a compiler for the HAI Programs. <br>
<br>
It can be downloaded at <a href="http://www.dtssoftware.com/haipc">http://www.dtssoftware.com/haipc</a>
(windows version). </span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>The
file 1701-1.haipc is a sample. <br>
<br>
It has the following advantages over the PCAccess program: <br>
<br>
1) You can add comments to your programs <br>
2) UNITS/ZONES… etc can be renumbered without changing your programs. The
HAI PCAccess program shows names of UNITS/ZONES but they are keep as UNIT/ZONE
numbers. If you move a name the program does not match the new name. <br>
3) You can use long names in your programs. The DEFINE statement allows any
length for a UNIT/ZONE name that can they be referenced in the program. The
name that gets downloaded into the panel is separate from this name <br>
4) The name/voice downloaded into the panel is also defined within the
compiler. If you change any UNIT/ZONE the panel name/voice will also change. <br>
5) You can use structured programming. The WHILE statement can have more than
one IF/ANDIF or DO statement under it. This means that you do not need to keep
repeating the same WHEN or IF statement over and over again. <br>
6) The normal BAT file used to invoke the compiler runs a macro preprocessor
first. This allows the source to have embedded macros or equates or INCLUDE
other files. <br>
7) The compiler accepts literals for device names. This allows the use of
device names within the program lines without actually defining the names. <br>
8) The compiler produces a list of the programs generated with a symbol
cross-reference. This makes it easy to see where a symbol is used. <br>
9) More than two IF statement allowed. You can use more than two if statements
(IF / ANDIF) and the compiler will automatically pick an unused button to chain
the Ifs together. See XANDIF <br>
<br>
Tom </span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>