<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" 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"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16546" name=GENERATOR><!--[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-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: .5in .5in .5in .5in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
FONT-WEIGHT: normal; COLOR: blue; FONT-STYLE: normal; FONT-FAMILY: "Tahoma","sans-serif"; TEXT-DECORATION: none; mso-style-type: personal
}
SPAN.EmailStyle18 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
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 vLink=blue link=blue>
<DIV dir=ltr align=left>
<DIV dir=ltr align=left><SPAN class=677214216-28112007><FONT face=Arial
color=#0000ff size=2>I don't know the internal format of the pca
file. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=677214216-28112007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=677214216-28112007><FONT face=Arial
color=#0000ff size=2>When redoing my programs using the compiler I use the GUI
pgm to auto generate the DEFINE cards using the panels current names. The
GUI does not convert any existing programs, just names. <SPAN
class=330464416-28112007>T</SPAN>hen I rewrite the programs <SPAN
class=330464416-28112007>using</SPAN> structured techniques and macros so I did
not see any advantage in converting the old programs.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=677214216-28112007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=677214216-28112007><FONT face=Arial
color=#0000ff size=2>Tom</FONT></SPAN></DIV><BR></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Brett Griffin
[mailto:brett@architechtronics.com] <BR><B>Sent:</B> Wednesday, November 28,
2007 11:28 AM<BR><B>To:</B> Tom Williamson; 'Tony Golden';
hai-users@tssi.com<BR><B>Subject:</B> RE: [Hai-users] Program
compiler<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Tony,
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">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: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">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: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Let
me know your thoughts!<o:p></o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Arial','sans-serif'"> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 8.5pt; COLOR: #1f497d; FONT-FAMILY: 'Arial','sans-serif'">--
<BR><B>Brett Griffin<BR></B>Home Technology Designer</SPAN><SPAN
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Arial','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 8.5pt; COLOR: #1f497d; FONT-FAMILY: 'Arial','sans-serif'">P
(206) 774.3622<BR>F (206)
260.7475<BR><BR><B>Archi</B></SPAN><B><SPAN
style="FONT-SIZE: 8.5pt; COLOR: #8cc62f; FONT-FAMILY: 'Arial','sans-serif'">tech</SPAN></B><B><SPAN
style="FONT-SIZE: 8.5pt; COLOR: #1f497d; FONT-FAMILY: 'Arial','sans-serif'">tronics,
Inc<BR></SPAN></B><SPAN
style="FONT-SIZE: 8.5pt; COLOR: #1f497d; FONT-FAMILY: 'Arial','sans-serif'"><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; COLOR: #8cc62f; FONT-FAMILY: 'Arial','sans-serif'"><BR>Visit
our blog!</SPAN></B><B><SPAN
style="FONT-SIZE: 8.5pt; COLOR: #cf5f23; FONT-FAMILY: 'Arial','sans-serif'">
</SPAN></B><SPAN
style="FONT-SIZE: 8.5pt; COLOR: #1f497d; FONT-FAMILY: 'Arial','sans-serif'"><A
href="http://www.architechtronics.com/blog/">http://www.architechtronics.com/blog/</A></SPAN><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; 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: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">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: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">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: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">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: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">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 style="TEXT-ALIGN: center" align=center>
<HR align=center width="100%" SIZE=2>
</DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; 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: 10pt; COLOR: blue; FONT-FAMILY: 'Tahoma','sans-serif'">That
does sound extra cool.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Tahoma','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Tahoma','sans-serif'">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: 10pt; COLOR: blue; FONT-FAMILY: 'Tahoma','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Tahoma','sans-serif'">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-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center>
<HR align=center width="100%" SIZE=2>
</DIV>
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; 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: 10pt; 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: 10pt; 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>